Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Build Enhancements"
(→URGENT PRIORITY [1.0M9 required]) |
(→URGENT PRIORITY [1.0M9 required]) |
||
Line 1: | Line 1: | ||
== Nightly Builds == | == Nightly Builds == | ||
=== URGENT PRIORITY [1.0M9 required] === | === URGENT PRIORITY [1.0M9 required] === | ||
− | # Add red and green radio LED's on [[Components]] page that notifies everyone as to the latest build status. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=208421] | + | # Add red and green radio LED's on [[Components]] page that notifies everyone as to the latest build status. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=208421 208421] |
#* We're waiting on Denis at Eclipse Foundation for access rights change | #* We're waiting on Denis at Eclipse Foundation for access rights change | ||
# Set permissions on files and folders [Paul] | # Set permissions on files and folders [Paul] |
Revision as of 10:38, 1 November 2007
Contents
Nightly Builds
URGENT PRIORITY [1.0M9 required]
- Add red and green radio LED's on Components page that notifies everyone as to the latest build status. 208421
- We're waiting on Denis at Eclipse Foundation for access rights change
- Set permissions on files and folders [Paul]
- The build script that uploads files to the Eclipse download servers should set the files "world readable" and the directories world r-x upon uploading them to the servers
- Option: tag all components just before building [Paul]
- This is an optional part of the nightly build process
- If build succeeds, and if the tagging was enabled, and if it was a candidate stable build, then having the source tagged will make it easy for us to check out this tag, and create a branch so that further tweaks to the stable build can be done on this branch.
- In order to generated the latest build on a stable build branch, we'll also need to be able to specify the branch for the script to use when checking out the code
- The script needs to operate as a committer --not an anonymous user
OTHER PRIORITY [1.0 required]
- Add "build" links\icons on Components page that allows authorized individuals to kick off a build of desired components. [Tom]
- No regeneration of build.xml after changing a project's dependencies. [Jim]
- Each project's build should ideally do whatever it takes to work before and after changes to that project's dependency list.
- Dependencies are versioned. [Jim]
- We should be able at worst to cause a build to use a specified CVS tag for all dependencies, and ideally, we should be able to specify a cvs tag for each dependency.
- Single place for dependencies. [Jim]
- Right now, we've decided to list them in manifest.mf. Because this file doesn't allow us to control its contents, we're restricted from doing things like #2 above. Moreover, it sounds like build.properties must also in some cases be updated with dependencies when there's a need to differentiate between build libs and runtime libs. I think we should be updating our own dependencies.xml file, and that should be used to auto-gen, or update the manifest.mf as appropriate.
- Any automated process should mirror manual processes. [Jim]
- If I pull down a project into a fresh work area and run it's build (which automates the process of gathering dependencies), the result should look the same as if I had manually gathered all those dependencies. Also, the fetched dependencies should remain in place and be usable at a later time.
Eclipse Developer Builds
For each component:
- Pull down and build in IDE (recursively).
- Have scripts to pull in all required 3rd party approved and unapproved libs [Alexandra]
- tbd others...
Non-Eclipse Developer Builds
- tbd others...