Oh, I see. Yes, I’ll change the 3.6 build to go to luna/maintenance.
Greg
I guess that both tm-3.6-maintenance and tm-3.7-maintenance Hudson jobs write to the same /luna/nightly location, and the 3.6 one happened to run later … The simrel.luna.aggregator job ran successfully with my fix so it looks like we’re good for now, but it looks like the target location of the tm-3.6-maintenance should perhaps be fixed. Thanks, Martin -- Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6 From: Greg Watson [mailto:g.watson@xxxxxxxxxxxx] Sent: Tuesday, February 17, 2015 1:17 AM To: Oberhuber, Martin Cc: TM project developer discussions; Stieber, Uwe Subject: Re: Need TM 3.7milestones published for Luna SR2 Strange, because according to the pom.xml, the latest build should be in tm/builds/luna/nightly, which is the one I copied over. I’ll poke around a bit more. Greg Actually it turned out that the simrel.luna.aggregator job failed, most likely due to this issue. So I went ahead and fixed the problem myself – Greg you may want to double check what I did on Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6 Thanks for the quick action, but when double checking the result I found that it’s still not quite correct. org.eclipse.tm.terminal_3.2.400.201409230946.jar org.eclipse.tm.terminal_3.2.400.201409230946.jar.pack.gz But expected version for 3.7 is o.e.tm.terminal_3.3.0 !!! Looking closer, it turns out there’s no build qualifier newer than 20140923 !! It looks like the /tm/builds/luna/nightly is populated from Hudson tm-3.6-maintenance , but we really want tm-3.7-maintenance . è Greg: As a stop-gap measure, could you populate the /tm/updates/3.7milestones from Hudson https://hudson.eclipse.org/tm/job/tm-3.7-maintenance/lastSuccessfulBuild/artifact/releng/org.eclipse.tm.repo/target/org.eclipse.tm.repo.zip è Greg / Uwe: It looks like we’ll need /tm/builds/3.7/nightly created from 3.7maintenance and auto-populated ? It looks like without this, we’d essentially contribute TM 3.6 to Luna SR2 rather than TM3.7 – build qualifiers seem to indicate we’d be missing any commit after 20140923 !! Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6 From: Greg Watson [mailto:g.watson@xxxxxxxxxxxx] Sent: Monday, February 16, 2015 3:33 PM To: Oberhuber, Martin Cc: TM project developer discussions Subject: Re: Need TM 3.7milestones published for Luna SR2 Importance: High I just noticed that some important bugfixes in the Terminal have not been published for Luna SR2 yet – the 4 top commits here: are missing in the 3.7milestones repo, which was last published on Jan8: -rw-rw-r-- 1 gwatson common 5787 Jan 8 11:08 artifacts.jar Can you please publish the respective “Luna Nightly” such that these important bug fixes get picked up by Luna SR2 ? -rw-rw-r-- 1 genie.tm tools.tm 5920 Feb 16 03:40 artifacts.jar Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6
|