G'Day Sven,
Martin asked me to set you up! I'm not really in the loop to
answer the 3 questions, but I'll take a stab at it:
* keep the buildbot running so that when problems arise they are found
quickly.
* how much time: I doubt it's much, Martin put a ton of time at the
beginning to get it all running, and then muks on top of that.
* There is always help for those that ask!
I suspect changing to use a different system would be a lot of work.
I'm on holidays, but I'll set you up when I get back on Tuesday.
Cameron
FlamingText.com
cc:muks,sven,martin
On 09/25/2012 05:34 AM, scl wrote:
Hi Mukund,
On 22.09.12 at 7:52 pm Mukund Sivaraman wrote:
We have a buildbot (Jenkins based) that we use to check that our
commits to GIMP, GEGL, babl, etc. build ok and tests run properly. It
needs a new maintainer. If nobody steps up, then it will have to be
abandoned.
can you tell us a bit more about this job, please?
- Which tasks have to be done?
- How much time does this take per week?
- Does the former maintainer support the incorporation for a while?
If anyone with Jenkins experience is willing to step up to the task of
maintaining it, please respond on the list.
Which experience do you expect? I'm a bit used to build management,
but not to Jenkins (yet).
Are there any alternatives, for instance the Gnome Build Brigade,
which can take this job, too?
Kind regards,
Sven
_______________________________________________
gimp-developer-list mailing list
gimp-developer-list@xxxxxxxxx
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
_______________________________________________
gimp-developer-list mailing list
gimp-developer-list@xxxxxxxxx
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
