Skip to main content

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.

Jump to: navigation, search

Papyrus/Papyrus Developer Guide/Release Process: How To

< Papyrus‎ | Papyrus Developer Guide
Revision as of 05:31, 4 May 2016 by Cletavernier.eclipsesource.com (Talk | contribs) (→‎Before starting a build)

The Papyrus project is built using Tycho with this releng project: Releng


Hudson Jobs

The Papyrus builds are started from Hudson. The following jobs on the Mars branch exist currently. There should always be the following jobs on each release branch:

  • papyrus-Master : builds the main plug-ins of Papyrus
  • papyrus-Master-Analysis : static analysis of the code, i.e. findBugs, sonar...
  • papyrus-Master-Tests : builds the tests for the main plugins of Papyrus
  • papyrus-Master-Tests-Failures : tests identified as failed, not regressions, kept to keep the main tests clean and without spams
  • papyrus-Master-Developer : developer tools, such as debug views in eclipse, papyrus diagram code generator and building tools
  • papyrus-Master-Extra : builds the "extra" plug-ins of Papyrus
  • papyrus-Master-Extra-Tests : builds the tests for the "extra" plug-ins

See all the currently defined Papyrus jobs on the page : https://hudson.eclipse.org/papyrus/view/<Eclipse version> You can add the name of the eclipse release to find the associated jobs, i.e. Mars, Luna...

Before starting a build

Unlike Nightlies, Milestone builds are publicly available to anyone downloading the latest Developer Build of Eclipse. This implies a few differences in terms of quality of the release:

  • All artifacts must be signed, using the Eclipse Certificate
  • The build must be as stable as possible. Especially, any Blocker or Critical bug must be fixed before the release
  • All License files must be available and up-to-date
  • All plug-in metadata must be defined (Especially, bundle name, bundle vendor and feature description)
  • The Papyrus update site must contain everything that is not already contained in the Eclipse Simrel repository (i.e. any plug-in from an Eclipse Project that is not in the release train)

It is also very important to follow the discussion on the Eclipse cross-project-issues-dev Mailing List

What is built?

Taking the example of "papyrus-Master", we use the releng's pom.xml files.

A good/nice practice is to also update Oomph's papyrus.setup (just select it as well) while we are at it.

These files must include all features, plugins and update sites that must be built, either directly or indirectly.

The releng's pom.xml files also specifies how to get the plug-ins and features that are to be built and specifies the update sites from which to retrieve the binary dependencies from the dependent projects.


Updating the releng's pom.xml

The file reflects the dependencies on the other projects. So, it must be updated at least before each milestone, to make sure that the code that is built works with the latest versions of all the dependencies.

The easiest way to update the dependencies is to copy them from the aggregation build model, which all projects must fill in with the correct reference to their update site(s) and feature(s).

This model is in a project with the release name on the Eclipse Git:

Clone the simrel repository


Import the simrel project


First: Verify that the branch is up to date (fetch and rebase or a pull).


update the local repository


Update the dependencies of the selected poms


Second: Be on the correct branch of the simrel repository before selecting the aggregation model in order to have the correct addresses of the papyrus' version dependencies (master or <Eclipse version>_maintenance, e.g. Luna_maintenance) as the models will differ from one another and result in erroneous updates.


The branches corresponding to the different <Eclipse version>


Choose the build model from the simrel project


The simrel model used to update the dependencies


A few dependencies are not in the aggregation build model though, so they must be updated manually:

Get all the occurrences of this case and their context


Inside the releng's pom.xml

As a reminder:

  • find . -name "pom.xml" searches from the current (.) folder all the pom.xml files
  • | passes the output of one command to another for further processing
  • xargs constructs a command from a standard input and prints it in the command window
  • grep searches for the occurrence of the name in the found file
  • -n -ai shows the line number (-n) of the occurrence and the i next lines (the i lines after the occurrence)
  • {} placeholder for the found file


Finding dependencies

If you don't know where a particular plug-in or feature is located, the easiest way to find it is to search the Eclipse download area using "find" on the ssh of build.eclipse.org. For example, using the ssh connection to the eclipse repository, to look for "org.eclipse.emf.compare" : 

find /home/data/httpd/download.eclipse.org/modeling/emf/ -name 'org.eclipse.emf.compare_*'


Updating the versions (optional)

During a release you can have to update the plugin versions and their linked features and categories as the API and other contents of the plug-in change, in accordance with the Eclipse Versioning Guidelines. The PDE API Tooling builders help to identify version number changes that are required by flagging problems on the bundle manifests. Also, if enabled, the Oomph Version Management builders perform additional checks, including;

  • consistency of POM version number with plug-in/feature manifest
  • ripple effect of bundle version number changes up to features that include tham

Also, be aware that some version number changes also require updates to other metadata, such as the category.xml and the *.product definition files for any RCP packages (especially for feature version changes).

As of the Neon release, Papyrus plug-in and feature versions are not bulk updated to the "next" version number as they were in previous releases. Accordingly, BundleTestUtils.java (tests>junit>plugins>developer>org.eclipse.papyrus.bundle.tests) no longer tracks the expected current version number of bundles. Correct versions are enforced by PDE and Oomph tooling.

Push

When pushing to the papyrus' gerrit you should use the standardized message :

  • [Releng] Update dependencies for <Eclipse Version> <Milestone> (e.g.: [Releng] Update dependencies for Mars M7)

Then wait for a committer to merge the changes brought by this commit.

How to start a build?

Builds, master and maintenance, are run automatically every night, every day and each hour if there has been a commit. When a build following specific changes is required, wait for the gerrit contribution to be merged and launch the main build and the the extras (both will launch their associated tests upon completion). Then once both are successful launch a signed build for each of them.

Note that the tests depend on the xxx-Developer build. Therefore don't forget to launch this one before or you will have an error (in case of a version update for example as the tests will only find the old version).


Manually

Only committers or release engineers in the Papyrus project can launch Papyrus build jobs from Hudson.

Go to the wanted page if you want to launch a selected build (e.g.: Mars page)


Enter the build parameters


Then:

  • In Hudson, click on Build Now, change the #Build parameters as needed, and click on Build.
  • You can then click on the job name in the Build History section in the left column, and then on Console Output, to follow build progress in real time.

Build parameters

Hudson builds expect these parameters:

  • BUILD_ALIAS : the name of the release (0.9.0, 1.1.0M6, etc.); leave it blank for nightly and integration builds
  • SIGN : whether to sign the update site (can take up to an hour on the Eclipse build server); mandatory for all builds except nightlies


Warning: Don't forget to do the same manipulation for the Master-Extra.

Tip: As the signing of the build can take quite a long time, it is recommended to launch a non-signed build first as the tests are automatically launched at the end of a master branch build. As the tests roughly take the same amount of time you can see if the current build passes the tests without having to wait the extra time needed by the signing step.

How to publish a build?

Successful Nightly builds are automatically published to :


With the script

To publish a milestone or release from a build, you can use the manualPromote.sh for Luna, and manualPromote-mars.sh for Mars, script on: /opt/public/modeling/mdt/papyrus/manualPromote.sh Start this script, and fill in the parameters in the interactive script:

  • the signed builds numbers
  • the corresponding version
  • the update site in which to publish it

Be careful however as Hudson does not make, as of yet, a zip for the tests and the current script will crash if a build number is provided and it does not find any corresponding zip. This may lead to some, fixable but annoying, access permissions problems.


For example:

example


In the previous example, the script will:

  • publish the main Papyrus plug-ins from Papyrus-Master build #1600 to the Papyrus download in "drops/1.1.0" and the update site in "milestones/1.1/RC3/main"
  • publish the extra plug-ins from Papyrus-Master-Extra build #1237 to the Papyrus download in "drops/1.1.0" in the same build folder as the main build, and the update site in "milestones/1.1/RC3/extra"
  • do not publish the test results from Papyrus-Master-Tests build
  • make "milestones/1.1/RC3" a composite update site, which contains "milestones/1.1/RC3/main" and "milestones/1.1/RC3/extra"
  • enable p2 download statistics both on "milestones/1.1/RC3/main" and "milestones/1.1/RC3/extra"
  • set the correct linux access rights on the new folders


Once the script is done, all you have left to do is to:

  • Tag the build: Releases should have a tag like 1.1.0, and milestones like 1.1.0_M6
  • update the aggregation model if this build must be part of the simultaneous release

Milestones / Release Candidate

Stable builds are not automatically published. They should be first tested internally before publishing. For example, to publish the 1.1.0M6 milestone build:


Add a new update site with the new build to the parent composite (~/downloads/modeling/mdt/papyrus/updates/milestones/1.1/):

  • update both the compositeContent.xml and compositeArtifacts.xml files of the update site (that are located in the parent of the folder to which you extracted the update site) to add a reference to your newly added update site
    • set the value of p2.timestamp to the result of "date +%s000"
    • increase the "size" attribute of the children element
    • add a "child" element inside the "children" element with a "location" set to the name of the folder (e.g "M6")


The values to edit


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

Simultaneous Release

Install the b3Aggregator plugin by selecting the wanted version from the directory.

Aggregator tools


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

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

<repositories location="http://download.eclipse.org/modeling/mdt/papyrus/updates/milestones/1.1/M6/main" description="Papyrus">
Previous composite address


Updated composite address


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

Tagging

Releases should have a tag like 1.1.0, and milestones should have a tag like 1.1.0_M6.

Finalizing the Release

When the release is complete and has been tagged in the repository, it is time to prepare the next release's development branch for continued version management. One aspect of this is ensuring that the Oomph Version Management tool's reference baseline for the next release completely and correctly describes the release just completed.

Oomph maintains a description of the release in the release.* files in the Papyrus release bundles in the plugins/developer tree. So far, these are:

  • oep.releng.main.release for the Papyrus Main product bundles and features
  • oep.releng.dev.release for the Papyrus Developer Tools bundles and features

The release.xml file is a manifest of all of the features and bundles, with their versions and the relationships between them, that comprise the Papyrus Release and the release.digest is a more efficient binary representation of the same that is loaded by Oomph tooling when needed. The Oomph Version Management builder creates these automatically from the current workspace and PDE target configuration, so long as all of the Papyrus feature projects are in the workspace. To rebuild the release description, simply delete the release.xml and release.digest files and they will be rebuilt with all of the requisite metadata to describe what is now the "previous release" reference baseline for the next release.

Checking

Check simrel reports

After the simrel build, you can check the reports at :


Check installations

Check installation from the simrel/staging update site at :

Retrieved from "https://wiki.eclipse.org/index.php?title=Papyrus/Papyrus_Developer_Guide/Release_Process:_How_To&oldid=404913"

Back to the top