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 "Orion/Releng Builds"
< Orion
| Line 1: | Line 1: | ||
The Orion builds follow many of the same practices used by the [[Platform-releng|Eclipse Platform Project]]. The builds are based on [[PDE/Build]] and run automatically on build.eclipse.org via cron job. | The Orion builds follow many of the same practices used by the [[Platform-releng|Eclipse Platform Project]]. The builds are based on [[PDE/Build]] and run automatically on build.eclipse.org via cron job. | ||
| − | There | + | There is only one kind of build. Integration builds run daily from tagged repository versions. [http://help.eclipse.org/topic//org.eclipse.pde.doc.user/tasks/pde_fetch_phase.htm Map files] are used to specify where a project is located in the repository and what version of that project to use in the build. The map files are located in the [http://git.eclipse.org/c/e4/org.eclipse.orion.server.git/tree/releng/org.eclipse.orion.releng/maps/orion.map org.eclipse.orion.releng] project. The builder itself performs the tagging so all the latest changes in "master" stream are picked up by every build. No manual tagging by committers is required. |
== Contributing changes to the build == | == Contributing changes to the build == | ||
| − | Contributing to a | + | Contributing to a build is easy, just commit your code to the master stream of the Orion repository and it will be included in the next integration build. |
| − | + | ||
| − | + | ||
=== Setting up your workspace === | === Setting up your workspace === | ||
| Line 23: | Line 21: | ||
git push #push local commits to the master | git push #push local commits to the master | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
= FAQ = | = FAQ = | ||
| Line 58: | Line 26: | ||
You don't need to tag every commit. Changes only need to be tagged when a build is scheduled. I-builds are scheduled to run Monday Night/early Tuesday morning, changes should be tagged and map files updated at the end of day Monday. For high-traffic projects that many people are working on, it is good to coordinate who will tag those projects. For low-traffic bundles that rarely get changed, sometimes it is good to tag right away when a change is made so that you don't forget later. | You don't need to tag every commit. Changes only need to be tagged when a build is scheduled. I-builds are scheduled to run Monday Night/early Tuesday morning, changes should be tagged and map files updated at the end of day Monday. For high-traffic projects that many people are working on, it is good to coordinate who will tag those projects. For low-traffic bundles that rarely get changed, sometimes it is good to tag right away when a change is made so that you don't forget later. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category:Orion|Releng Builds]] | [[Category:Orion|Releng Builds]] | ||
Revision as of 14:31, 11 January 2012
The Orion builds follow many of the same practices used by the Eclipse Platform Project. The builds are based on PDE/Build and run automatically on build.eclipse.org via cron job.
There is only one kind of build. Integration builds run daily from tagged repository versions. Map files are used to specify where a project is located in the repository and what version of that project to use in the build. The map files are located in the org.eclipse.orion.releng project. The builder itself performs the tagging so all the latest changes in "master" stream are picked up by every build. No manual tagging by committers is required.
Contents
Contributing changes to the build
Contributing to a build is easy, just commit your code to the master stream of the Orion repository and it will be included in the next integration build.
Setting up your workspace
- See Orion/Getting the source for instructions on how to set up your workspace to work with Orion source code.
- Import 'org.eclipse.orion.releng' into your workspace. It is located in the org.eclipse.orion.server.git repository under the releng folder.
Contributing your changes
Once you have made code changes, you can contribute them to the Integration build as follows:
- Commit your changes to the local repository and push them to the master
git commit -a -m "fix lots of bugs" #commits all changes git push #push local commits to the master
FAQ
How often do I need to tag?
You don't need to tag every commit. Changes only need to be tagged when a build is scheduled. I-builds are scheduled to run Monday Night/early Tuesday morning, changes should be tagged and map files updated at the end of day Monday. For high-traffic projects that many people are working on, it is good to coordinate who will tag those projects. For low-traffic bundles that rarely get changed, sometimes it is good to tag right away when a change is made so that you don't forget later.