Re: [Gimp-developer] Updating the website for all the broken download links?

[Sam Gleske <sam mxracer gmail com>]

On Sun, Apr 27, 2014 at 11:28 PM, scl <scl gplus gmail com> wrote:

> On  28.4.2014 at 3:59 AM Sam Gleske wrote:
>
>  As I mentioned in the past the offer is still open for me to QA the GIMP
> > website frontend for dead links and generate a report.  I didn't ever get
> > approval from any of the core devs so I didn't run any front end tests.
> >
> > SAM
>
> Hi Sam,
>
> yes, we lately had this topic and somehow it went out of sight.
> I'm not the webmaster, but I think it's useful.
> If we should/can integrate something into our Jenkins job set,
> then let me know.
>
> Greetings,
>
> Sven

As Jehan suggested I'll clone the website.  I wasn't aware of the website
git repo.  As far as the bot goes the source for the crawler is out there.
In general, the requirements for a Jenkins node would be the following...

1. Git for cloning and Python 2 for the robot.
2. A simple HTTP server such as nginx.  Or if the website is simply static
pages something like python -m SimpleHTTPServer would suffice.
3. A copy of Firefox which would be run for the actual tests.
4. Xvfb - X Virtual Frame Buffer which would be used to provide a "headless
GUI" for Firefox to run within.
5. And the requirements for selenium.

In general, I have all of the requirements in the setup process detailed
for the testing crawler [1].  It integrates fairly well with Jenkins as far
as output.  If all of the tests pass then it will exit with a POSIX exit
code 0 (success).  If any of the unit tests fail then it will exit
non-zero.  So to integrate it with Jenkins one would need to simply add it
as a build step in Jenkins.  Minimum software requirements are basically
what runs Firefox well.

As Jehan pointed out the git repository I'll clone it and see what I can
come up with.  I can get Jenkins up and running java -jar jenkins.war and
create a job which I can contribute to you.  Though, it will essentially
only be a single step job with a shell script executing the robot testing
because I don't know what other build steps are involved with the website.
That should be enough for you to figure out how to integrate it into your
Jenkins build.

I'll start with the git repository and go from there.  Thanks for pointing
it out Jehan.

SAM

[1]: https://github.com/sag47/chewbotkah