Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

Papyrus Developer Guide/Release Process: How To/Publish Papyrus Artifacts

Publish a build

Successful Nightly builds are automatically published to :

Before Publishing

Stable builds are not automatically published. They should be first tested internally before publishing.


To publish a milestone or release from a build, you have to use the specific jobs on the project's Jenkins instance.

You should verify that what you have pushed is there :

  • ~/downloads/modeling/mdt/papyrus/downloads/drops/<versionNumber>
  • ~/downloads/modeling/mdt/papyrus/updates/<milestones/releases>/<releaseName>

Once you have verified that what you have pushed is there , all you have left to do is to:

  • Tag the last commit: Releases should have a tag like 1.1.0, and milestones like 1.1.0_M6
    • git tag -a 2.0.1_RC4 -m "Create the tag 2.0.1_RC4" d4c28a3b7c1c46cf5407bbfae2eda602eb4480c7
    • git push origin 2.0.1_RC4

Builds can be hidden from this page before a release by modifying downloads-scripts.php in /downloads/ on git://

Simultaneous Release

If the build must be part of the simultaneous release, you must also:

  • Use the B3 Aggregator (or a text editor if the modification is trivial) and push to the simrel's gerrit which path is :

Usually, the only thing to change is the location (for example "milestones/1.1/M6/main"):

<repositories location="" description="Papyrus">
Previous composite address

Updated composite address

Tip: You can check the status of the contribution at simrel's gerrit page

Back to the top