Plug-in components are installable features that are deployed online as P2 repositories for general availability. Products are deployed as ZIP files and made available online in designated locations on simantics.org.
Core components of the release train:
-* External third party library dependencies required by the platform - [simantics/third-party.git](https://www.simantics.org:8088/r/gitweb?p=simantics/third-party.git;a=summary)\r
-* The Simantics Platform - [simantics/platform.git](https://www.simantics.org:8088/r/gitweb?p=simantics/platform.git;a=summary)\r
+* External third party library dependencies required by the platform - [simantics/third-party.git](https://gerrit.simantics.org/r/gitweb?p=simantics/third-party.git;a=summary)\r
+* The Simantics Platform - [simantics/platform.git](https://gerrit.simantics.org/r/gitweb?p=simantics/platform.git;a=summary)\r
Plug-in components that are part of the release train:
-* Simupedia - [members/simupedia.git](https://www.simantics.org:8088/r/gitweb?p=members/simupedia.git;a=summary)
-* FMIL - [simantics/fmil.git](https://www.simantics.org:8088/r/gitweb?p=simantics/fmil.git;a=summary)
-* FMI Studio - [members/fmi.git](https://www.simantics.org:8088/r/gitweb?p=members/fmi.git;a=summary)
-* Interoperability components - [simantics/interop.git](https://www.simantics.org:8088/r/gitweb?p=simantics/interop.git;a=summary)
-* Simantics R binding - [simantics/r.git](https://www.simantics.org:8088/r/gitweb?p=simantics/r.git;a=summary)
-* Matlab SCL binding - [simantics/matlab.git](https://www.simantics.org:8088/r/gitweb?p=simantics/matlab.git;a=summary)
-* Python SCL binding - [simantics/python.git](https://www.simantics.org:8088/r/gitweb?p=simantics/python.git;a=summary)
-* Simantics System Dynamics - [simantics/sysdyn.git](https://www.simantics.org:8088/r/gitweb?p=simantics/sysdyn.git;a=summary)
-* Simantics District modelling components - [simantics/district.git](https://www.simantics.org:8088/r/gitweb?p=simantics/district.git;a=summary)
-* Simantics 3D modelling components - [simantics/3d.git](https://www.simantics.org:8088/r/gitweb?p=simantics/3d.git;a=summary)
-* Simantics Proteus toolset - [gold-members/proteus.git](https://www.simantics.org:8088/r/gitweb?p=gold-members/proteus.git;a=summary)
+* Simupedia - [members/simupedia.git](https://gerrit.simantics.org/r/gitweb?p=members/simupedia.git;a=summary)
+* FMIL - [simantics/fmil.git](https://gerrit.simantics.org/r/gitweb?p=simantics/fmil.git;a=summary)
+* FMI Studio - [members/fmi.git](https://gerrit.simantics.org/r/gitweb?p=members/fmi.git;a=summary)
+* Interoperability components - [simantics/interop.git](https://gerrit.simantics.org/r/gitweb?p=simantics/interop.git;a=summary)
+* Simantics R binding - [simantics/r.git](https://gerrit.simantics.org/r/gitweb?p=simantics/r.git;a=summary)
+* Matlab SCL binding - [simantics/matlab.git](https://gerrit.simantics.org/r/gitweb?p=simantics/matlab.git;a=summary)
+* Python SCL binding - [simantics/python.git](https://gerrit.simantics.org/r/gitweb?p=simantics/python.git;a=summary)
+* Simantics System Dynamics - [simantics/sysdyn.git](https://gerrit.simantics.org/r/gitweb?p=simantics/sysdyn.git;a=summary)
+* Simantics District modelling components - [simantics/district.git](https://gerrit.simantics.org/r/gitweb?p=simantics/district.git;a=summary)
+* Simantics 3D modelling components - [simantics/3d.git](https://gerrit.simantics.org/r/gitweb?p=simantics/3d.git;a=summary)
+* Simantics Proteus toolset - [gold-members/proteus.git](https://gerrit.simantics.org/r/gitweb?p=gold-members/proteus.git;a=summary)
Products that are part of the release train:
* Simantics Desktop
When release stabilisation starts, branch all relevant repositories like this:
- git clone ssh://<user>@www.simantics.org:29418/simantics/platform.git
+ git clone ssh://<user>@gerrit.simantics.org:29418/simantics/platform.git
cd platform
git branch release/x.y.z[.w] <commit>
git push origin release/x.y.z[.w]
When creating major/minor releases `<commit>` is usually a commit in the `master` branch.
With service releases, branch from an existing `release/*` branch instead.
-Use of the included `release-helper.sh` shell script is highly encouraged to perform this mechanical work. The script supports many useful basic git commands which all perform the requested operation on all the release train repositories. The operations can be seen from the help text printed by the script when given no arguments:
+Instead of doing this clone+branch+push sequence for every SDK repository separately,
+please use the included `release-helper.sh` shell script to perform this mechanical work. The script supports many useful basic git commands which all perform the requested operation on all the release train repositories. The operations can be seen from the help text printed by the script when given no arguments:
Usage: release-helper.sh <version> <branch-name> <user-name> clone|branch|checkout|fetch|list-tags|pull|push|push-tags|remove-tag|status|tag
-First, begin by cloning all the repositories:
+Always begin by cloning all the repositories for working on
./release-helper.sh x.y.z release/x.y.z your-git-username clone
-This will create a directory called `x.y.z` under the current working directory and clone all the repositories under it.
+This will create a directory called `x.y.z` under the current working directory and clone all the repositories under it. The first `<version>` argument is only used for the base working directory `x.y.z`. The second `<branch-name>` argument tells what branch to specify to the action, i.e. `branch`, `checkout`, etc.
Branching and pushing the branches to remote happens as follows:
./release-helper.sh x.y.z release/x.y.z your-git-username branch
+ ./release-helper.sh x.y.z release/x.y.z your-git-username checkout
./release-helper.sh x.y.z release/x.y.z your-git-username push
+If you're creating a service release `x.y.w` from `x.y.z` where `w > z`, do this:
+
+ ./release-helper.sh x.y.w release/x.y.z your-git-username clone
+ ./release-helper.sh x.y.w release/x.y.z your-git-username checkout
+ ./release-helper.sh x.y.w release/x.y.w your-git-username branch
+ ./release-helper.sh x.y.w release/x.y.w your-git-username checkout
+ # Perhaps make modifications to the branch here and commit to each project separately
+ ./release-helper.sh x.y.w release/x.y.w your-git-username push
+
## Prepare release branch for use
-In release 1.31.0 Simantics started using uses the wonderful tool from Obeo ([https://github.com/mbarbero/fr.obeo.releng.targetplatform](https://github.com/mbarbero/fr.obeo.releng.targetplatform)) to generate `.target` files from `.tpd` files which allow much simpler specification of the target contents and also composition of .tpd files via inclusion.
+In release 1.31.0 Simantics started using the wonderful tool from Obeo ([https://github.com/mbarbero/fr.obeo.releng.targetplatform](https://github.com/mbarbero/fr.obeo.releng.targetplatform)) to generate `.target` files from `.tpd` files which allow much simpler specification of the target contents and also composition of .tpd files via inclusion.
In the following steps, it is recommended to ensure every `.target` file is up-to-date by regenerating them from `.tpd` files. While doing so, take care to use up-to-date online contents to perform the generation.
-### Prepare `.tpd` files
+### Prepare `.tpd` files in platform repository
+
+0. Ensure you've ran\r
+
+ ./release-helper.sh x.y.z release/x.y.z your-git-username checkout
-1. Retrieve release branch of the platform repository
+ to make sure you're working on the release branch before doing anything.
- git clone ssh://<user>@www.simantics.org:29418/simantics/platform.git
- cd platform
- git branch release/x.y.z[.w] remotes/origin/release/x.y.z[.w]
- git checkout release/x.y.z[.w]
+1. Go into the cloned platform repository at `x.y.z/platform`\r
2. Edit all target platform files in `releng/org.simantics.sdk.build.targetdefinition/`, i.e.
* `org.simantics.sdk.build.targetdefinition.tpd`
location "http://www.simantics.org/download/release/x.y.z[.w]/sdk" {
~~~
-3. Edit version number of `org.simantics.sdk` feature in `features/org.simantics.sdk.feature/feature.xml` to `x.y.z[.w]`.
+3. Edit version number of `org.simantics.sdk` feature in `features/org.simantics.sdk.feature/feature.xml` to `x.y.z`.
~~~
<feature
id="org.simantics.sdk"
provider-name="VTT Technical Research Centre of Finland">
~~~
- An example of these changes can be seen in [gitweb](https://www.simantics.org:8088/r/gitweb?p=simantics%2Fplatform.git;a=commit;h=5271b0faa98303225d00e6cd838d3fc52488545c) or [review 1361](https://www.simantics.org:8088/r/#/c/1361/).
+ If the release branch you're setting up is a hotfix-release `x.y.z.w`,
+ don't include the `.w` part in this version.
+
+ An example of these changes can be seen in
+ [gitweb](https://gerrit.simantics.org/r/gitweb?p=simantics%2Fplatform.git;a=commit;h=5271b0faa98303225d00e6cd838d3fc52488545c)
+ or [review 1361](https://gerrit.simantics.org/r/#/c/1361/).
+
+4. Ensure that Gitlab has a release engineering issue for the branched release,
+ such as [Simantics 1.34.0 release engineering](https://gitlab.simantics.org/simantics/platform/issues/16)
+ * Make a new release issue with title `$version release engineering`.
+ * Add a link to the previous previous release's issue in the new issue description, e.g. `simantics/platform#16`.
+ * Add labels `releng` and `$version` to the new issue
-4. Ensure that Redmine has a release engineering issue for the branched release, such as [Simantics 1.30.0 release engineering](https://www.simantics.org/redmine/issues/7263). Make a copy of the previous release issue to create the new one. Include link to original issue while copying.
5. Commit the changes made
Configured release/x.y.z[.w] branch for SDK builds.
- refs #xxxx
+ gitlab #xxxx
where `#xxxx` is the number of the x.y.z[.w] release engineering issue and push them to remote
git push origin release/x.y.z[.w]
6. If you are branching from `master`, bump the revision of master right now to start the next release cycle in master.
- An example of these changes can be seen in [gitweb](https://www.simantics.org:8088/r/gitweb?p=simantics%2Fplatform.git;a=commit;h=564ac84a2949b19ce5c1c7c838b575527ec42b09) or in [review 1362](https://www.simantics.org:8088/r/#/c/1362). The changes include:
+ An example of these changes can be seen in [gitweb](https://gerrit.simantics.org/r/gitweb?p=simantics%2Fplatform.git;a=commit;h=564ac84a2949b19ce5c1c7c838b575527ec42b09) or in [review 1362](https://gerrit.simantics.org/r/#/c/1362). The changes include:
* Simantics Desktop splash screen update (version number)
* Simantics target platform name to state correct development version
* org.simantics.sdk feature version bump
Bumped master target and org.simantics.sdk feature versions to x.y.z[.w].
- refs #yyyy
+ gitlab #yyyy
where `#yyyy` is the number of the next release's release engineering issue.
-### Initialize release branch distribution web site
-
-* Run [SDK/Deploy External Components to Web](https://www.simantics.org/jenkins/job/SDK/job/Deploy%20External%20Components%20to%20Web/) build with parameters:
- * **GERRIT_REFNAME:** `release/x.y.z[.w]`
- * **PUBLISH_ARTIFACTS:** `true`
-* Run the [SDK/Simantics SDK](https://www.simantics.org/jenkins/job/SDK/job/Simantics%20SDK/) build with parameters:
- * **GERRIT_REFNAME:** `release/x.y.z[.w]`
- * **PUBLISH_ARTIFACTS:** `true`
-
-Running these two builds will ensure that both the external components required to build the SDK and the Simantics SDK for the new release branch are published online at `http://www.simantics.org/download/release/x.y.z[.w]/`.
-
-After this, whenever changes are pushed/merged to `release/x.y.z[.w]` branch in Gerrit, new **SDK/Simantics SDK** builds are triggered automatically and they will publish the results at the same location online.
-
-This means that one does not have to do any tricks after this to build and publish the SDK as a P2 repository online. It is an automated process that is performed by the [SDK/Simantics SDK](https://www.simantics.org/jenkins/job/SDK/job/Simantics%20SDK/) Jenkins job.
-
-### Update release-branch `.target` files
-
-Next, we want to change the `.tpd` and `.target` files to point to the correct P2 repository locations in the release-branch. This happens by opening the previously edited `.tpd` files in Obeo's editor and regenerating the `.target` files by pressing Alt+R.
-
-Push the changed files to remote again with commit message:
-
- Configured release/x.y.z[.w] branch .target files.
-
- refs #xxxx
-
-See [review 1361](https://www.simantics.org:8088/r/#/c/1361) for an example.
+7. Do the same for simupedia target platform files as was done in task 6.\r
+ for platform target definitions.
### Test Release Train build
Trigger an execution of the [simantics-release-train](https://www.simantics.org/jenkins/job/simantics-release-train/) Jenkins job with parameters
-* GERRIT_REFNAME: `release/x.y.z[.w]`\r
-* PUBLISH_ARTIFACTS: `true`\r
+* GERRIT_REFNAME: `release/x.y.z[.w]`
+* PUBLISH_ARTIFACTS: `true`
to ensure that all components of the release train build fine and to publish first versions of P2 repositories of everything online.
+The release train build is currently never ran automatically.
+However, after following all these steps, whenever changes are pushed/merged to `release/x.y.z[.w]` branch in Gerrit, new Jenkins builds are triggered automatically and they will publish the results (P2 repositories/products) at their designated locations online.
+
+#### [Optional reading] Release train build details
+
+The release train build does two very important steps as the first things,
+i.e. build the external dependency P2 repositories for both the
+Platform SDK and Simupedia:
+~~~
+stage('External Dependencies') {
+ node {
+ build job: 'SDK/Deploy External Components to Web', parameters: params1
+ build job: 'Member Components/Simupedia/fi.semantum.simupedia.build.p2.site', parameters: params1
+ }
+}
+~~~
+After that it builds the Platform SDK and Simupedia before building anything else:
+~~~
+stage('SDK') {
+ node {
+ build job: 'SDK/Simantics SDK', parameters: params1
+ // Note that Simantics SDK builds simupedia-git as well
+ }
+}
+~~~
+
## Review documentation
Documentation to review:
When the release branches are ready for the release, tag them with the tag `vx.y.z[.w]`:
- git clone ssh://<user>@www.simantics.org:29418/simantics/platform.git
- cd platform
- git checkout release/x.y.z[.w]
- git tag vx.y.z[.w] -m "Simantics x.y.z[.w] simultaneous release"
- git push origin --tags
-
- git clone ssh://<user>@www.simantics.org:29418/simantics/third-party.git
- cd third-party
- git checkout release/x.y.z[.w]
- git tag vx.y.z[.w] -m "Simantics x.y.z[.w] simultaneous release"
- git push origin --tags
+ ./release-helper.sh x.y.z release/x.y.z your-git-username checkout
+ ./release-helper.sh x.y.z release/x.y.z your-git-username pull
+ ./release-helper.sh x.y.z release/x.y.z your-git-username tag
+ ./release-helper.sh x.y.z release/x.y.z your-git-username push-tags
-> Note The -m argument must be supplied to create an [annotated tag](https://git-scm.com/book/en/v2/Git-Basics-Tagging).
+> Note: release-helper.sh will supply the -m argument to git tag to create an [annotated tag](https://git-scm.com/book/en/v2/Git-Basics-Tagging).
> Only annotated or signed tags can be pushed to Gerrit.
## Backup documentation wiki databases
Code Review / simantics / platform.git / blobdiff