| Re: [cross-project-issues-dev] Status and outlook for RC1 ... its going to be a late night! |
|
Hi Greg, [1] shows that the build was triggered by only one SCM change with the comment: “For ptp, add org.eclipse.ptp.debug.sdm feature”. Before of this
change the build was working. So IMO it suggests itself that this commit was breaking the build. BTW: This is exactly the way how I was checking that my change for Kepler RC1 was not breaking the build (because it was my first commit into the
simrel repo), that was obviously not that case [2] ;) In general I would vote to use Gerrit and CI a little bit closer together how it is mentioned in [3]. But IMO this is not acceptable for such a
“build sprint”. [1]
https://hudson.eclipse.org/hudson/job/simrel.kepler.runaggregator/476/ [2]
https://hudson.eclipse.org/hudson/job/simrel.kepler.runaggregator/472/ [3]
http://blogs.collab.net/teamforge/teamforge-git-gerrit-integration-with-jenkins-ci
Cheers, Sven Von: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Greg Watson On May 22, 2013, at 11:43 PM, David M Williams <david_williams@xxxxxxxxxx> wrote:
There's no change in policy. Projects choose to be in the (our) common repo. Part of that is to provide valid input to the build. Normally the tools work well to send out notifications
for problems. Occasionally the contributed input is so bad that the tool can't even read it well enough to find the email addresses. You can wait until someone tells you that, if you'd like. But, as tonight, sometimes that takes 3 or 4 hours (or longer) for
someone else to notice. As you said, you were "waiting for a build" ... how long would you wait before you looked at
I looked at it and the error was "exec returned: 13". How am I supposed to know that this is related to ptp? Is your expectation that I should dig into how it works to determine what is causing this problem? I don't think so.
Come on David, you said that "it was ptp breaking the builds..." and you "...spent an extra hour of my time fixing that". So you obviously knew there was a problem, but chose not to inform anyone about it.
Actually the change was made using the b3 aggregation editor. I was going to make the change by hand because the editor doesn't appear to work for me in kepler, but Beth insisted on using it. So whatever went wrong was caused by your own
tools.
Although the fix has zero chance of affecting anyone, I don't think it's worth the chance that there will be build problems at this late stage.
|