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 addre
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 Jenk
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 a
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 link
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 th
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
