Thanks!
On 7 Nov 2014 10:46, "Dan Haywood" wrote:
> ok, done; added "jcvanderwal" [3]
>
>
> [3] http://people.apache.org/committer-index.html#J
>
>
> On 7 November 2014 08:26, Jeroen van der Wal wrote:
>
> > Your action is still required: " ... PMC chairs can grant access to
> Jenkins
> > to any
ok, done; added "jcvanderwal" [3]
[3] http://people.apache.org/committer-index.html#J
On 7 November 2014 08:26, Jeroen van der Wal wrote:
> Your action is still required: " ... PMC chairs can grant access to Jenkins
> to any committer (see below for instructions) to get an administrative
> ac
Your action is still required: " ... PMC chairs can grant access to Jenkins
to any committer (see below for instructions) to get an administrative
account ..." [1]
Cheers,
Jeroen
On Fri, Nov 7, 2014 at 6:58 AM, Dan Haywood
wrote:
> You just use your normal LDAP apache user Id (as used for comm
Meanwhile, I've updated the job. It was set to use "mvn3 (latest)", which
I would've thought was the right thing; but since it clearly isn't, I've
changed to use "mvn 3.2.1" explicitly.
Have kicked off a build, will see what happens...
Dan
On 7 November 2014 05:58, Dan Haywood wrote:
> You ju
You just use your normal LDAP apache user Id (as used for committing, for
updating the site etc) ... at least that's what works for me.
Once logged onto Jenkins (http://builds.apache.org) there is no additional
authorization ... any committer can change any job. I guess we all must
trust each oth
The build of Isis [1] is failing because it requires a more recent version
of Maven. I wanted to change the configuration and are able to log in on
Jenkins but am not able to change the configuration.
Dear PMC (eg Dan): can you grant me access? [2]
Cheers,
Jeroen
[1] http://support.citrix.com/
