Bugzilla – Full Text Bug Listing
| Summary: | Add Linux Tools to Helios build | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Andrew Overholt <overholt> | ||||
| Component: | Cross-Project | Assignee: | David Williams <david_williams> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | david_williams | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Andrew Overholt
Created attachment 156170 [details]
patch to add Linux Tools to Helios build
Add linuxtools.build and modify helios.build to include Linux Tools features.
I ran a local Helios build and while it failed, it didn't appear to be Linux Tools-related :) Its been failing a lot lately :( I'll take a look soon. You have commit rights to that callisto directory, right? (In reply to comment #3) > You have commit rights to that callisto directory, right? I'm not sure, but I didn't want to commit anything in case I broke it :) I looked, and you do have membership in calliso-dev. I was going to look at/commit the patch, but it doesn't apply cleanly any longer. Guess someone else changed some files already. So, can you re-attach a new patch against current head ... or, commit the changes your self? Its ok if you break a build ... as long as you fix it :) But seriously, I will be attending to this today and this weekend. I've already fixed one error and its running now. Not sure what else we might hit. But, do feel free to try ... or, new patch if you'd prefer. Committed. I trust I'll be notified if it breaks the build :) Should I leave this open until our stuff ends up in a successful build? (In reply to comment #6) > Committed. I trust I'll be notified if it breaks the build :) Success or failure, I think? > Should I leave > this open until our stuff ends up in a successful build? Most the projects I work on mark a bug as fixed, as soon as "release for a build" ... but its still polite to confirm is it really fixed :) The build triggered by your change may not complete due to the "zest problem" ... which I heard "should be fixed this weekend". Ah, seeing the results reminds me ... not on success. Often not even on failure. There's some "blame" heuristics built in, so it sends email only to those "responsible". Its fairly accurate .... and so far, its not blaming you. :) There's a dependency problem between two other components. So, once that's fixed, you might still get a "fail" notice over the weekend (or, whenever current break is fixed). The latest build succeeded so I promoted what ever we have to 'staging'. You can verify your stuff is actually there by testing against http://download.eclipse.org/releases/staging/ |