Re: [Gimp-developer] Jenkins tutorial

2014-02-23 Thread scl

Hi Sam,

thank you for sharing your thoughts!
As they are more related to infrastructure I've started a new thread
'Jenkins infrastructure (Was: Jenkins tutorial)'.
Let's continue there.

Greetings,

Sven


___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


Re: [Gimp-developer] Jenkins tutorial

2014-02-23 Thread scl

Hi Mukund,

On  22.2.2014 at 10:40 AM Mukund Sivaraman wrote:
> It would be nice to have docs on how to setup such a Jenkins instance
> (after the other tutorials are written).

Ok, your arguments are convincing. I'll regard this.

> * Such docs would enable others to maintain/reconfigure the Jenkins
>instance when you are busy and unable to do so.

I also thought it would be nice to have a co-admin for these cases.
If anybody volunteers, why not.

Kind regards,

Sven


___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


Re: [Gimp-developer] Jenkins tutorial

2014-02-22 Thread Sam Gleske
On Sat, Feb 22, 2014 at 4:40 AM, Mukund Sivaraman  wrote:

> It would be nice to have docs on how to setup such a Jenkins instance
> (after the other tutorials are written).
>
> * Many bits in GIMP's source code are like a reference for "how to do X"
>   which other free software projects can use as examples. In the same
>   way, "How to setup a Jenkins instance for GIMP" would help others
>   setup one for their project too.
>
> * Such docs would enable others to maintain/reconfigure the Jenkins
>   instance when you are busy and unable to do so.


That being said... would it be useful to have a vagrant instance of the
development environment including Jenkins for Job testing?  With a vagrant
file it can be as easy as a single program executing to pull down virtual
box, the image, all of the requirements for gimp building and testing.
This is something which could also be tweaked.  Also, Jenkins really isn't
hard.  It's pretty intuitive IMO (java -jar jenkins.jar and you have a
local web server) but a turn key dev environment would certainly lower the
barrier to entry.
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


Re: [Gimp-developer] Jenkins tutorial

2014-02-22 Thread Sam Gleske
Also, something you might be interested in is front end web testing for bad
links, etc.  Recently I've been working on a project to facilitate that
testing.

https://github.com/sag47/frontend_qa

This can easily be used in a Jenkins job to arbitrarily launch and crawl
gimp.org and test all the links in it checking for dead links, etc.
Currently it's a work in progress but it's a place that one can easily
start for frontend testing the Gimp website.


On Sat, Feb 22, 2014 at 4:40 AM, Mukund Sivaraman  wrote:

> Hi Sven
>
> On Sat, Feb 22, 2014 at 06:03:35AM +0100, scl wrote:
> > Hi,
> >
> > now that we have our continuous integration server
> > Jenkins for babl, GEGL and GIMP at an easy memorable address
> > (https://build.gimp.org) I'm going to write a tutorial
> > for developers and testers on how to use it.
> > Are there any particular questions you want to have
> > answered there?
>
> It would be nice to have docs on how to setup such a Jenkins instance
> (after the other tutorials are written).
>
> * Many bits in GIMP's source code are like a reference for "how to do X"
>   which other free software projects can use as examples. In the same
>   way, "How to setup a Jenkins instance for GIMP" would help others
>   setup one for their project too.
>
> * Such docs would enable others to maintain/reconfigure the Jenkins
>   instance when you are busy and unable to do so.
>
> Mukund
>
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


Re: [Gimp-developer] Jenkins tutorial

2014-02-22 Thread Mukund Sivaraman
Hi Sven

On Sat, Feb 22, 2014 at 06:03:35AM +0100, scl wrote:
> Hi,
> 
> now that we have our continuous integration server
> Jenkins for babl, GEGL and GIMP at an easy memorable address
> (https://build.gimp.org) I'm going to write a tutorial
> for developers and testers on how to use it.
> Are there any particular questions you want to have
> answered there?

It would be nice to have docs on how to setup such a Jenkins instance
(after the other tutorials are written).

* Many bits in GIMP's source code are like a reference for "how to do X"
  which other free software projects can use as examples. In the same
  way, "How to setup a Jenkins instance for GIMP" would help others
  setup one for their project too.

* Such docs would enable others to maintain/reconfigure the Jenkins
  instance when you are busy and unable to do so.

Mukund


pgpW8ANhrwXUZ.pgp
Description: PGP signature
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


[Gimp-developer] Jenkins tutorial

2014-02-21 Thread scl

Hi,

now that we have our continuous integration server
Jenkins for babl, GEGL and GIMP at an easy memorable address
(https://build.gimp.org) I'm going to write a tutorial
for developers and testers on how to use it.
Are there any particular questions you want to have
answered there?

Kind regards,

Sven

(Yes I know, cross-posting is bad. I did it anyway because
I think not all GIMP people will be on the GEGL dev. list and
vice versa.)
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list