Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Build Enhancements"
(→Other Priority [1.0 required]) |
(→Eclipse Developer Builds) |
||
Line 26: | Line 26: | ||
== Eclipse Developer Builds == | == Eclipse Developer Builds == | ||
− | For | + | *Configure target in build.xml that would fetch the dependencies for a project. For any given component: |
− | * Pull down and build in IDE (recursively). | + | ** Pull down dependencies and build in IDE (recursively). |
− | * | + | ** Pull in all required 3rd party unapproved libs [Alexandra] |
− | + | ||
== Non-Eclipse Developer Builds == | == Non-Eclipse Developer Builds == |
Revision as of 18:06, 18 November 2007
Contents
Nightly Builds
Done
- Tagged nightly builds 208429 [DONE]
- Optional tag name parameter: The build script is given a tag string as a new parameter. It tags all modules with this tag prior to building
- Optional branch name parameter: The build script checks out code from this branch if present, HEAD if not. Motivation: In order to generate 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
- Motivation: If build succeeds, and if the tagging was enabled, (especially 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.
- Note: the script needs to operate as a committer --not an anonymous user
- Add colored LED icons to Components page in status column 208421 [DONE]
Urgent
- Set permissions on files and folders
- 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
- Tagged stable builds 208430
Other Priority
- 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
- Configure target in build.xml that would fetch the dependencies for a project. For any given component:
- Pull down dependencies and build in IDE (recursively).
- Pull in all required 3rd party unapproved libs [Alexandra]
Non-Eclipse Developer Builds
- tbd others...