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 "Eclipse 4diac Wiki/Development/4diac Releng"
(add section on archieving, moving the feature freeze tasks into own section) |
|||
| Line 15: | Line 15: | ||
#* For Major and bug fix releases merge release branch to master | #* For Major and bug fix releases merge release branch to master | ||
#* Tag commit with release (e.g., 1.9.0.M1, 1.10.1) | #* Tag commit with release (e.g., 1.9.0.M1, 1.10.1) | ||
| + | # Create the Jenkins Jobs for the branches, for 4diac IDE and FORTE, for Gerrit and for the branch itself (example just shows FORTE fro gerrit, you'll need 4 in total). | ||
| + | #* Go to [https://hudson.eclipse.org/4diac/] and create an element (top of left menu) | ||
| + | #* Select "Copy from", normally the last option, and select the the previous version. Don't use blank spaces in the name | ||
| + | #* In the new element change the branch name in the following sections where available (or just look for the name of old branch and replace with the new one): | ||
| + | #** General -> Description | ||
| + | #** General -> This Build is parametrized -> Text-Parameter -> Default (or Vorgabewert) | ||
| + | #** Source-Code-Management -> Git -> Branches to build | ||
| + | #** Gerrit Trigger -> Gerrit Project -> Branches -> Pattern | ||
# Build 4diac-ide | # Build 4diac-ide | ||
#* Trigger build in 4diac JIPP instance. job 4diac IDE release | #* Trigger build in 4diac JIPP instance. job 4diac IDE release | ||
Revision as of 11:43, 7 October 2019
Short checklist for 4diac releases:
- if minor/major release update version information
- Update main version info (Manifest, pom):
- org.eclipse.fordiac.ide
- org.eclipse.fordiac.product
- org.eclipse.master
- For minor releases
- update any plugins to new version numbers if needed
- update according features
- Update main version info (Manifest, pom):
- prepare branding
- Update splash screen
- Update update version number in VM Arguments: -Declipse.buildId= (this is needed for AERI)
- Prepare git repositories
- For Major and bug fix releases merge release branch to master
- Tag commit with release (e.g., 1.9.0.M1, 1.10.1)
- Create the Jenkins Jobs for the branches, for 4diac IDE and FORTE, for Gerrit and for the branch itself (example just shows FORTE fro gerrit, you'll need 4 in total).
- Go to [1] and create an element (top of left menu)
- Select "Copy from", normally the last option, and select the the previous version. Don't use blank spaces in the name
- In the new element change the branch name in the following sections where available (or just look for the name of old branch and replace with the new one):
- General -> Description
- General -> This Build is parametrized -> Text-Parameter -> Default (or Vorgabewert)
- Source-Code-Management -> Git -> Branches to build
- Gerrit Trigger -> Gerrit Project -> Branches -> Pattern
- Build 4diac-ide
- Trigger build in 4diac JIPP instance. job 4diac IDE release
- Assemble FORTE
- clone anonymous git :
- change to release branch
- zip forte and name it forte-incubation_version.zip
- Put it onto eclipse download site
- Connect to build.eclipse.org (sftp username@build.eclipse.org)
- go into release dir (e.g., /home/data/httpd/download.eclipse.org/4diac/...)
- Update release specific update sites
- Update download page
- Move files from previouse release to http://archive.eclipse.org
- For more information see IT Infrastructure Doc#Move files to archive.eclipse.org?
- As we are using the mirror link script in our download page no changes to the download page are needed
- Prepare news for:
- 4diac web page, mirror on sourceforge
- Announce it on
- Google+
- Researchgate
- Freshcode
Start the Feature Freeze Phase
- Create dedicated branches for the maintenance of the release (e.g., 1.15.x)
- Create CI jobs both for the 4diac-IDE and FORTE. Each component needs 2 jobs, one triggered at each commit, and the other for the nightly build. The procedure is similar so only the 4diac-IDE will be shown as an example.
- Go to Jenkins
- On the left menu, click on New Item, and then select the option "Copy from" and type the name of the previous version (for example "4diac IDE 1.10.x", and "4diac IDE 1.11.x Gerrit")
- On the new job, you need to change the last version to the current one (for example 1.10.x to 1.11.x) in the following places:
- General -> Description
- Source-Code-Management -> Branches to build
- And for the gerrit one, also the following:
- General -> This Build is parametrized -> Text-Parameter -> Default Value (Vorgabewert)
- Gerrit Trigger -> Dynamic Trigger Configuration -> Branches -> Pattern