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

[Sascha Scholz <sascha.scholz@xxxxxxxxx>]

On Tue, Jan 18, 2011 at 8:22 PM, Steffen Pingel
<steffen.pingel@xxxxxxxxxxx> wrote:
>> - 'Use private Maven repository' to start with an empty Maven
>> repository for every build and to avoid concurrency effects because of
>> shared repository usage
>
> That seems like it would use  lot of resources and make builds take
> much longer. I would prefer if the nightly build ran frequently and
> fast.

I'll check how long the build takes and keep an eye on it. For builds
that run after every check-in I support that it should be as fast as
possible to give early feedback, but for a nightly jobs I find longer
build times acceptable.

> How about we setup another job for releases that does more thorough
> checking and runs against all supported target platforms (3.5, 3.6 and
> 3.7)?

Sounds good. I propose to run them every night to have an early
feedback regarding possible issues (i.e. we would have 3 nightly jobs
which perform a clean build and do extensive checking)

Besides the nightly jobs I would love to see a fast job that runs
after every check-in and (once a Gerrit instance is in place) a voting
job that checks if proposed changes have a green build.

Do you know whether my proposal are compliant with Eclipse build
infrastructure rules?

Sascha

>
>> - Publish findbugs results?
>
> Sounds good.
>
>> If that's ok, can I get admin rights to implement the changes?
>
> I have updated your permissions so you can modify the build.
>
> We should also enable repository polling or run the job on a schedule.
>
> Steffen
>
>
> --
> Steffen Pingel
> Committer, http://eclipse.org/mylyn
> Senior Developer, http://tasktop.com
> _______________________________________________
> mylyn-reviews-dev mailing list
> mylyn-reviews-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-reviews-dev
>