db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <kristian.waa...@oracle.com>
Subject Re: Build failed in Jenkins: Derby-branch-10.5 #185
Date Wed, 06 Jul 2011 20:46:11 GMT
On 05.07.11 23:26, Kathey Marsden wrote:
> On 7/4/2011 12:38 AM, Kristian Waagan wrote:
>>> I tried to log into builds.apache.org but got permission denied. I am
>>> not sure what else to do to follow up on the Jenkins issue.
>> Infra is limiting shell access to the Jenkins slaves as much as
>> possible for security reasons.
>> The ASF Jenkins installation has some stability issues at the moment
>> (I don't know the exact reasons why), and the best initial thing to do
>> is usually to rerun the failed job.
> Thank you Kristian,
> I may have asked and you may have answered this question before, but I
> was wondering is rerunning a failed job something that I can do myself
> or should I just request it on the list when needed?

There are several options:
  o committers can ask to become Hudson job-admins [1] if they want to 
help with Derby jobs
  o you can make, or wait for, a commit to trigger the build
  o ask on the list to have an admin start the build manually

There are some other mechanisms that can be used too, but using them 
will probably incur a certain overhead (like distributing a token, 
keeping a file somewhere where a certain group of people can access it etc).

If things go awry, builds at apache is the place to ask for help.


[1] http://wiki.apache.org/general/Hudson

> Thanks
> KAthey

View raw message