On Mon, Jun 24, 2013 at 09:49:24AM -0700, Toshio Kuratomi wrote:
On Mon, Jun 24, 2013 at 09:11:01AM +1000, Róman Joost wrote:
I see that Patrick solved your problem by enabling anonymous access.
There's no problem with that but I would like to caution you about making
jenkins a necessary part of building docs.gimp.org
or anything else
I know it's easy as a user of the the service to think of this as "we'll
it now and cross that bridge when we get to it". That's fine but please do
everything you can to document and let the rest of your team/people concerned with
know about this caveat to the service. That way if you move
on and someone else is in charge of building docs.gimp.org
they won't be
surprised and upset with us if we remove the service without warning.
the reminder. At the moment it is not used for any release
critical functionality. The Jenkins service at the moment extends our
ability to manually update our docs and helps us by a great extend. No
harm done, if you can not provide the service anymore.
I'll note it for our team so everyone is on the same page.
Software Engineer, HSS - Infrastructure Engineering & Development (Brisbane)
email: rjoost(a)redhat.com | tz: UTC+10
irc: rjoost #bugzilla