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 <[email protected]> wrote: > 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 other! > > Cheers > Dan > > > On 4 November 2014 14:59, Jeroen van der Wal <[email protected]> wrote: > >> 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/article/CTX123676 >> [2] http://wiki.apache.org/general/Jenkins >> > >
