Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Aggregator not picking up the latest from the Kepler branch

Yes, it is a known problem. (That seems to be getting worse? ... as if parts of the infrastructure is getting busier  ... or, you all are just making a lot more rapid changes! :)   A delay of "a minute or two" is not unusual ... if people see delays of "hours", please comment in bug.

It is on my "hot list".

From:        Steffen Pingel <steffen.pingel@xxxxxxxxxxx>
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        09/18/2013 06:59 AM
Subject:        [cross-project-issues-dev] Aggregator not picking up the latest        from the Kepler branch
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx


when I updated the Mylyn aggregator files for Kepler today I made
mistake which I fixed right away in another commit. The aggregator
Hudson job however kept building the broken file and hence failed.

When I check on the build server
/shared/simrel/kepler/ was
indeed not the latest revision that was in Git or showing in Hudson

The build only fixed itself after we made another change to the
mylyn.b3aggrcon file which apparently caused an update to the the file
in /shared/simrel. Is that a known problem?

It worries me a bit that the aggregator appears to not always use the
same revision that is checked out in Hudson so it may build something
else than what the casual observer might assume.



---------- Forwarded message ----------
Date: Wed, Sep 18, 2013 at 12:21 PM
Subject: [keplerAggregation] Failed for build 2013-09-18_06-21-35

The following errors occured when building Kepler:

Software being installed: validationSet_main 1.0.0

Missing requirement:
1.0.0 requires '
[1.1.1,1.2.0)' but it could not be found

Cannot satisfy dependency: validationSet_main 1.0.0 depends on:

Check the log file for more information:

Steffen Pingel
Principal Software Engineer, Eclipse Mylyn
Mylyn Tasks Lead
cross-project-issues-dev mailing list

Back to the top