Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-rt-dev] Gerrit build
We need to provide two new environment variables when running the build.  This should have been required for builds last night also -- I wasn't sure why the build was not failing.  I guess that the Gerrit server has been incorrectly bundling an old version of the RTS into the RTS feature.

I'll try to update the build for this.

Do you have advice on setting environment variables in Hudson?  On Jenkins I used the EnvInject plugin, but that doesn't seem possible here.  On Hudson I think that I have to add parameters to the Job and then set the default values appropriately.

-Andrew

On 15-06-10 07:57 AM, LETAVERNIER Camille wrote:

By the way, my second test commit [1] failed while it was supposed to work, but the error seems unrelated to the commit. I suspect the current master branch is broken

 

[1] 49899: [Gerrit Test] Clean build [I62cda32a]

https://git.eclipse.org/r/#/c/49899/

 

Camille

 

De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de LETAVERNIER Camille
Envoyé : mercredi 10 juin 2015 13:54
À : papyrus-rt developer discussions
Objet : [PROVENANCE INTERNET] Re: [papyrus-rt-dev] Gerrit build

 

Hi Andrew,




We simply applied the standard Gerrit build configuration:

 

https://wiki.eclipse.org/Gerrit#Verifying_Changes_on_Hudson_using_Gerrit_Trigger_Plugin

 

The refspec and branch specifier didn’t match (Refspec was refs/changes/*:refs/changes/* instead of $GERRIT_REFSPEC, and the branch was $GERRIT_REFSPEC instead of **)

 

Additionally, we replaced the Git repository URI, from git://git.eclipse.org/gitroot/papyrus-rt/org.eclipse.papyrus-rt.git to /gitroot/papyrus-rt/org.eclipse.papyrus-rt.git, which is semantically identical but bypasses the Git server (The filesystem is accessed directly). That’s a recommendation from Eclipse to reduce the load on the git server, but that’s minor.

 

 

Regards,
Camille

 

De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de Andrew Eidsness
Envoyé : mercredi 10 juin 2015 13:17
À : papyrus-rt-dev@xxxxxxxxxxx
Objet : Re: [papyrus-rt-dev] Gerrit build

 

Good.  I'm a bit curious about it though, could you summarize the problem and solution?

-Andrew

On 15-06-10 05:18 AM, LETAVERNIER Camille wrote:

Hi all,

 

The Gerrit build is now fixed and pulls the proper commit. Enjoy :)

 

Regards,
Camille

 

De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de LETAVERNIER Camille
Envoyé : mercredi 10 juin 2015 09:46
À : papyrus-rt developer discussions
Objet : [PROVENANCE INTERNET] Re: [papyrus-rt-dev] Gerrit build

 

Hi Andrew,

 

I’ve checked with Rémi, and it is not just a display issue. The Gerrit workspace still represents the state of commit 120dd53, so I think there’s something wrong with the branch configuration (Maybe the Gerrit branch is fetched but not checked out)

 

I’ve noticed some differences with the Papyrus build configuration, so we’ll have a deeper look at this today

 

Regards,
Camille

 

De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de Andrew Eidsness
Envoyé : mercredi 10 juin 2015 02:09
À : papyrus-rt-dev@xxxxxxxxxxx
Objet : Re: [papyrus-rt-dev] Gerrit build

 

Ernesto and I have been wondering about that as well.  This shows up (incorrectly) in the "Changes" section on the Hudson build info page.  As you mention the builds seem to work properly, however it would be nice to fix anyhow.

The change that it has picked doesn't seem to be special in anyway.  I'm guessing it was just the current tip when Ernesto created this build.  However, I don't see it listed anywhere in the build configuration.  Do you know where Hudson gets that information from?

-Andrew

On 15-06-09 07:21 AM, LETAVERNIER Camille wrote:

Hi all,

 

 

I’ve pushed two contributions to the Papyrus-RT Gerrit server. This properly starts a build, but I wonder if it properly configured:

 

Last Built Revision: Revision 120dd53dda9c27586c516f36e8452cfb7bb791c5 (refs/changes/46/49746/1)

Checkout:workspace / /home/hudson/genie.papyrus-rt/.hudson/jobs/papyrusrt_gerrit_patch_triggered_build/workspace - hudson.remoting.LocalChannel@35cd27f3

Fetching changes from the remote Git repository

Fetching upstream changes from git://git.eclipse.org/gitroot/papyrus-rt/org.eclipse.papyrus-rt.git

Commencing build of Revision 120dd53dda9c27586c516f36e8452cfb7bb791c5 (refs/changes/55/49755/1)

 

Commit 120dd53 is 3 weeks old. Also, when I look at the Gerrit build history (“Recent changes”), it seems that all Gerrit builds pick the same commit:

 

https://hudson.eclipse.org/papyrus-rt/job/papyrusrt_gerrit_patch_triggered_build/changes

 

Did I miss anything, or should the Gerrit Job configuration be fixed?

 

 

Regards,
Camille







_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

 





_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

 



_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

Back to the top