Re: [mylyn-reviews-dev] Nightly build job configuration enhancements

[Steffen Pingel <steffen.pingel@xxxxxxxxxxx>]

On Wed, Jan 19, 2011 at 5:13 AM, Sascha Scholz <sascha.scholz@xxxxxxxxx> wrote:
> I configured the build job to run from scratch (takes about 15min,
> most of the time resolving target platform). The job checks every 10
> minutes if there are new commits. With Gerrit in place this shouldn't
> be so frequent.

Given that a build that uses cached artifacts takes 2.5 minutes which
is about 5x faster and consumes a magnitude less resources I would
prefer if we reverted that change.

> For the other target platform I would like to see two additional jobs
> which could run as downstream jobs (i.e. only run if the build for one
> target platform is green). Should I request them? What I didn't
> understand is what's the difference between "nightly" and "release"
> build mentioned in the Eclipse Hudson wiki. Any idea?

Release builds would probably execute additional steps such as tagging
or signing.

Essentially every Mylyn sub-project will have these requirements:
* A build job that executes frequently and completes quickly to
provide feedback on (proposed) changes.
* A nightly build that tests on all supported targets and possibly
several platforms.

To reduce maintenance overhead for everyone, would it work if we setup
three nightly jobs that built all Mylyn projects in one go and run all
tests against Eclipse 3.5, 3. 6 and 3.7?

Steffen

-- 
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com