Summary: | make sure we can *re* do post build processing and publishing | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | David Williams <david_williams> |
Component: | Releng | Assignee: | Platform-Releng-Inbox <platform-releng-inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | daniel_megert |
Version: | 4.6 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
David Williams
2016-05-04 01:02:30 EDT
One other complication to remember, sometimes we have a "zip" of the "production files" we need, named with the hash of their version at the time of the build. Often that is what we want to use if we "re-do" things but, occasionally, such as if I just made a syntax error in a bash script, it would be helpful to be able to correct the file it Git and then use the new "master" version of the tools ... not the "saved hash" version of the scripts. One thing that accomplished most of what we need -- that we have run into lately with "connection problems", etc. has been codified in a bash script named "republish.sh" in the production directory. There are several ways to use it, but it removes some stuff, updates some values, and calls "publish-eclipse.sh". It has not been widely tested, but locally it "does the basics". But, some warning, a fair knowledge of what is going on is required to make the best use of it -- it is not something that "cures all ills" nor would it be "completely safe" for just anyone to use. (Well, it would not really harm anything, but may overwrite things not intended to be overwritten). |