| Summary: | builders should be tagged during build or when changed | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | David Williams <david_williams> |
| Component: | Releng | Assignee: | Platform-Releng-Inbox <platform-releng-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P4 | CC: | daniel_megert |
| Version: | 4.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
|
Description
David Williams
What the heck, trying it now. (Still using R4_2_primary) which will have to change to "master" once we fix that. Note sure what to do here. Didn't work as expected, but more I think about it, not sure of best approach .... we already have the eclipsebuilder checked out for the build ... we could just tag it. ... and ... not sure it's right to automatically tag when changed. Seems for reproducibility we might want to tag "manually" and then pull that particular version for a particular build. FYI, when I tried to tag using "autotagging" besides adding line to repositories.txt .... after seeing that alone didn't cause tagging .... added a "fake" map entry. but, was getting a "hung up" message: So, obviously, something not specifiedf right? (Or, maybe impossible with a "root project"? /shared/eclipse/eclipse4/build/supportDir/gitCache/eclipse.platform.releng.eclipsebuilder /shared/eclipse/eclipse4/build/supportDir/gitCache fatal: The remote end hung up unexpectedly Doing a mass "reset to default assignee" of 52 bugs to help make clear it will (very likely) not be me working on things I had previously planned to work on. I hope this will help prevent the bugs from "getting lost" in other people's queries. Feel free to "take" a bug if appropriate. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |