Continuous integrations jobs for SWTBot are available here https://hudson.eclipse.org/swtbot . Here is a quick description of available jobs:

−

* https://hudson.eclipse.org/hudson/job/swtbot-tycho/

+

* ''swtbot-tycho'' is the main CI job. It builds and run tests against an Eclipse Indigo platform and publishes output p2 repository to http://download.eclipse.org/technology/swtbot/snapshots

−

* https://hudson.eclipse.org/hudson/job/swtbot-tycho-e4.2/

+

* ''swtbot-tycho-e4.2'' compiles and runs tests against the last release of Eclipse 4.x branch. It guarantees compatibility with a wide range of Eclipse versions

−

+

* ''swtbot-gerrit'' compiles and runs tests against any Gerrit contribution, and then add a vote to the contribution: +1 if everything is fine, -1 in case of a compile error, build error, or failed test

−

A view also exists, it contains also older build configurations: https://hudson.eclipse.org/hudson/view/SWTBot/

+

* ''SWTBot-Sonar'' runs (weekly) build and tests against last commit of master branch and generates Sonar reports. See [[#Sonar]]

+

* Other ''swtbot-*'' are legacy jobs, prior to usage of Maven (2.0.5 and older).

# First, make sure you have agreed and signed the [http://www.eclipse.org/legal/clafaq.php Eclipse Contribution CLA].

# First, make sure you have agreed and signed the [http://www.eclipse.org/legal/clafaq.php Eclipse Contribution CLA].

−

# Then, read '''carefully''' this documents: [[Gerrit]] to set up commit hooks and other things. We recommand using the [[Gerrit#Using_Gerrit_with_EGit: | EGit-Gerrit connector]].

+

# Then, read '''carefully''' this documents: [[Gerrit]] to set up commit hooks and other things. We recommand using the [[Gerrit#Using_Gerrit_with_EGit: | EGit-Gerrit connector]]. Make sure that the options ''Add Signed-off by'' and ''Compute Change-Id for Gerrit Code-Review'' are selected in the commit dialog.

In case you work without EGit Gerrit connector:

In case you work without EGit Gerrit connector:

# Make your change locally, and ''git commit'' them in your local repo. Commit message must contain Bug Number.

# Make your change locally, and ''git commit'' them in your local repo. Commit message must contain Bug Number.

Line 103:

Line 104:

== Release process ==

== Release process ==

+

# Make sure upcoming release is listed in http://projects.eclipse.org/projects/technology.swtbot/releases

# Announce wish to release on swtbot-dev mailing-list, and wait for approval of committers

# Announce wish to release on swtbot-dev mailing-list, and wait for approval of committers

# Run all builds on Hudson (swtbot-tycho, swtbot-tycho-e42, swtbot-sonar).

# Run all builds on Hudson (swtbot-tycho, swtbot-tycho-e42, swtbot-sonar).

−

# Tag the builds with the version of the release

+

# Keep the build and Tag then with the version of the release using Hudson UI.

# Tag source

# Tag source

<source lang="bash">

<source lang="bash">

Line 123:

Line 125:

# Change all pom.xml, MANIFEST.MF and feature.xml to use the version of next release, git commit and push

# Change all pom.xml, MANIFEST.MF and feature.xml to use the version of next release, git commit and push

# Change bugzilla milestones (from portal.eclipse.org) to create a new release (2.1.1) and a new milestone (2.1.2)

# Change bugzilla milestones (from portal.eclipse.org) to create a new release (2.1.1) and a new milestone (2.1.2)

Target Platforms

You can find some ready-to-use target platforms for development in the devtools/target-platforms folder. Each target-platform basically target a version of the Eclipse release train. It's recommended to use one of these target-platform since it contains all SWTBot dependencie. These target-platforms are also used at build time, so your dependencies in IDE will be consistent with dependencies during build. Enable the selected target-platform by opening it in IDE with the target definition editor, and click Set As Target Platform.

Provide a contribution using Gerrit

Then, read carefully this documents: Gerrit to set up commit hooks and other things. We recommand using the EGit-Gerrit connector. Make sure that the options Add Signed-off by and Compute Change-Id for Gerrit Code-Review are selected in the commit dialog.

In case you work without EGit Gerrit connector:

Make your change locally, and git commit them in your local repo. Commit message must contain Bug Number.

Hi all,
We're happy to announce you the release of SWTBot 2.1.1.
Main changes are:
* Compatibility with Eclipse 4.3 (and backward compatibility with previous releases)
* Improvement on code recorder and generator
The full list of changes can be found here: https://bugs.eclipse.org/bugs/buglist.cgi?list_id=6242414&classification=Technology&query_format=advanced&target_milestone=2.1.1&product=SWTBot
Git tag can be found here: http://git.eclipse.org/c/swtbot/org.eclipse.swtbot.git/tag/?id=2.1.1
And release p2 repository can be found here http://download.eclipse.org/technology/swtbot/releases/2.1.1 (and http://download.eclipse.org/technology/swtbot/releases/latest ).
Enjoy!