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 "Triquetrum/Releng/Milestone Builds"
< Triquetrum | Releng
(Update targetDir after release so that we avoid overwriting.) |
(Updates for 0.3.0M1 and Jenkins.) |
||
Line 2: | Line 2: | ||
To create a Triquetrum Milestone Build, follow these steps: | To create a Triquetrum Milestone Build, follow these steps: | ||
# See [https://www.eclipse.org/projects/dev_process/development_process.php#6_4_Releases Eclipse Development Process > Releases] and [[Version Numbering]] for how to select a version number. | # See [https://www.eclipse.org/projects/dev_process/development_process.php#6_4_Releases Eclipse Development Process > Releases] and [[Version Numbering]] for how to select a version number. | ||
− | # Update the version number using <code>mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=0. | + | # Update the version number using <code>mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=0.3.0</code>. Note that we don't use the Mi |
## See [https://stackoverflow.com/questions/11521839/how-to-automate-version-number-update-process-for-my-eclipse-plugin-built-with-m How to automate version number update process for my Eclipse plugin built with Maven] | ## See [https://stackoverflow.com/questions/11521839/how-to-automate-version-number-update-process-for-my-eclipse-plugin-built-with-m How to automate version number update process for my Eclipse plugin built with Maven] | ||
## See [https://www.eclipse.org/tycho/sitedocs/tycho-release/tycho-versions-plugin/set-version-mojo.html tycho-versions:set-version] | ## See [https://www.eclipse.org/tycho/sitedocs/tycho-release/tycho-versions-plugin/set-version-mojo.html tycho-versions:set-version] | ||
Line 10: | Line 10: | ||
## Run <code>mvn clean verify</code> and edit the <code>pom.xml</code> and <code>Triquetrum.product</code> until the files that are created have the correct names. | ## Run <code>mvn clean verify</code> and edit the <code>pom.xml</code> and <code>Triquetrum.product</code> until the files that are created have the correct names. | ||
# The [https://github.com/eclipse/triquetrum/blob/master/releng/org.eclipse.triquetrum.repository/publish.xml org.eclipse.triquetrum.repository/publish.xml] file contains a copyZips target that is invoked by the triquetrum.milestone build. | # The [https://github.com/eclipse/triquetrum/blob/master/releng/org.eclipse.triquetrum.repository/publish.xml org.eclipse.triquetrum.repository/publish.xml] file contains a copyZips target that is invoked by the triquetrum.milestone build. | ||
− | ## Update the milestone directory: configure the [https:// | + | ## Update the milestone directory: configure the [https://ci.eclipse.org/triquetrum/job/triquetrum.milestone/configure Jenkins triquetrum.milestone build], under Invoke Ant click on Advanced Properties and update <code>targetDir=/home/data/httpd/download.eclipse.org/triquetrum/0.3.0M1/</code>, make the same edit in the '''second''' Invoke Ant area, then save the change [[File:TriquetrumHudsonMilestoneScreenshot.png|900px|Hudson triquetrum.milestone screenshot showing the Build -> Ant Task section]] |
− | # | + | # Invoke the Milestone build by going to [https://ci.eclipse.org/triquetrum/job/triquetrum.milestone/configure Jenkins triquetrum.milestone build] noting the Build Trigger Token and replacing TOKEN_NAME in the fullowing URL: /job/triquetrum.milestone/build?token=TOKEN_NAME |
− | # To see what files are created, see http://download.eclipse.org/triquetrum/0. | + | # To see what files are created, see http://download.eclipse.org/triquetrum/0.3.0M1/?d |
− | # When you are satisfied with the output, in the [https:// | + | # When you are satisfied with the output, in the [https://ci.eclipse.org/triquetrum/job/triquetrum.milestone/configure Jenkins triquetrum.milestone build]: |
− | ## Update the | + | ## Update the targetDir to the next milestone release so that we don't accidentally overwrite the current release |
− | + | ||
# Edit [[Triquetrum/Downloads | Triquetrum Downloads]]. | # Edit [[Triquetrum/Downloads | Triquetrum Downloads]]. | ||
− | # | + | # Eventually: update the version number of the master branch to the next version using <code>mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=0.3.1</code> |
== See Also == | == See Also == | ||
* [[Milestone and Release Builds]] | * [[Milestone and Release Builds]] | ||
* [[Triquetrum/Releng/New Eclipse Version | Triquetrum -> Releng -> New Eclipse Version]] | * [[Triquetrum/Releng/New Eclipse Version | Triquetrum -> Releng -> New Eclipse Version]] |
Revision as of 12:43, 24 August 2019
Create a Triquetrum Milestone Build
To create a Triquetrum Milestone Build, follow these steps:
- See Eclipse Development Process > Releases and Version Numbering for how to select a version number.
- Update the version number using
mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=0.3.0
. Note that we don't use the Mi - Update the version numbers by hand:
- Edit releng/org.eclipse.triquetrum.repository/pom.xml and update the version by removing
qualifier
from theid
. - Edit org.eclipse.triquetrum.repository/Triquetrum.product] and remove
qualifier
from theproduct uid
. - Run
mvn clean verify
and edit thepom.xml
andTriquetrum.product
until the files that are created have the correct names.
- Edit releng/org.eclipse.triquetrum.repository/pom.xml and update the version by removing
- The org.eclipse.triquetrum.repository/publish.xml file contains a copyZips target that is invoked by the triquetrum.milestone build.
- Update the milestone directory: configure the Jenkins triquetrum.milestone build, under Invoke Ant click on Advanced Properties and update
targetDir=/home/data/httpd/download.eclipse.org/triquetrum/0.3.0M1/
, make the same edit in the second Invoke Ant area, then save the change
- Update the milestone directory: configure the Jenkins triquetrum.milestone build, under Invoke Ant click on Advanced Properties and update
- Invoke the Milestone build by going to Jenkins triquetrum.milestone build noting the Build Trigger Token and replacing TOKEN_NAME in the fullowing URL: /job/triquetrum.milestone/build?token=TOKEN_NAME
- To see what files are created, see http://download.eclipse.org/triquetrum/0.3.0M1/?d
- When you are satisfied with the output, in the Jenkins triquetrum.milestone build:
- Update the targetDir to the next milestone release so that we don't accidentally overwrite the current release
- Edit Triquetrum Downloads.
- Eventually: update the version number of the master branch to the next version using
mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=0.3.1