Skip to content

Latest commit

 

History

History
188 lines (123 loc) · 6.11 KB

README-MAINTAINER.md

File metadata and controls

188 lines (123 loc) · 6.11 KB

Maintainer info

Development workflow

The plug-ins are published on the Eclipse download servers both as update sites and as archives.

Development builds are published as p2 sub-folders like:

When the content is stable, it is promoted as a pre-release and published as:

The final release is published in the main update site:

For archiving purposes, the release is also published in a separate folder for each version, with the archive in the top folder and the p2 repo as a sub-folder

Packages are published at:

The official download page is

How to fix issues

Normally all changes should be done as a result of a ticket registered as a GitHub Issue.

Create a new milestone

If not already done, create a new milestone.

Fix issues

  • be sure the develop branch is selected
  • scan the plug-ins issues list, and fix them. The commit message should be prefixed with the issue number, like [#122];
  • mark all fixed issues as part of the new milestone;
  • add a message like fixed on 2020-01-10;
  • close the issues

Build locally

After fixing issues, run the maven build locally:

$ mvn clean verify

Start a Debug/Run session and try the result in a child Eclipse.

Push to GitHub

Be sure the repo is clean and push the develop branch to GitHub.

This will also trigger a CI job that will run a maven build.

Trigger the Jenkins development build

Install on a separate Eclipse

Test if the new build can be used as an update site, by installing it on a separate Eclipse (not the one used for development); use the URL:

  • https://download.eclipse.org/embed-cdt/builds/develop/p2

How to make a new release

Merge to master

When ready, merge the develop branch into master, and push them to GitHub.

Wait for the CI to confirm that the build passed.

Trigger the Jenkins master build

Publish the pre-release

  • go to https://ci.eclipse.org/embed-cdt/job/build-plug-ins/
  • login (otherwise the next link is not visible!)
  • use the make-pre-release-from-master Jenkins job to copy the files from builds/master to updates/neon-test, which is the public location for the pre-release.

Beta testers can install the pre-release from:

  • https://download.eclipse.org/embed-cdt/updates/neon-test

Publish the release

The updates/neon includes only the expanded p2 repository.

The releases folder includes both the release archives and the expanded p2 repository.

Both can be used in Eclipse to Install New Software.

The public update URLs are:

  • https://download.eclipse.org/embed-cdt/updates/neon
  • https://download.eclipse.org/embed-cdt/releases/<version>/p2

Create a release record

In the official iot.embed-cdt page, click the Create a new release link in the right sidebar.

Copy/paste content from the previous release.

To get the list oc changes, scan the Git log and add new entries, grouped by days.

$ git log --pretty='%cd * %h - %s' --date=short

To get the release content, download the archive and do a ls -L features plugins.

Update the Eclipse Marketplace records

Create a package

TODO: explain how to edit/update the EPP project.

The direct download URL is

  • https://download.eclipse.org/embed-cdt/packages

Share on Twitter

  • go to the new post and follow the Tweet link
  • copy the content to the clipboard
  • DO NOT click the Tweet button here, it'll not use the right account
  • in a separate browser windows, open TweetDeck
  • using the @gnu_mcu_eclipse account, paste the content
  • click the Tweet button