every member should have the access - you included - indeed was me on setting up all initial jobs, unfortunately I have no clue about the deploy issue :(
best, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Fri, Dec 7, 2012 at 1:30 PM, Christian Grobmeier <[email protected]> wrote: > On Fri, Dec 7, 2012 at 1:28 PM, Simone Tripodi > <[email protected]>wrote: > >> No clue as well, hopefully Olivier knows how to set the jobs in order >> to allow jenkins deploying our artifacts,,, >> >> Who - besides Olivier - does have access to Jenkins? > I mean, just in case something wents wrong and our Guru is not available? > > >> -Simo >> >> http://people.apache.org/~simonetripodi/ >> http://simonetripodi.livejournal.com/ >> http://twitter.com/simonetripodi >> http://www.99soft.org/ >> >> >> On Fri, Dec 7, 2012 at 12:55 PM, Christian Grobmeier >> <[email protected]> wrote: >> > On Fri, Dec 7, 2012 at 12:50 PM, Daniel Manzke < >> [email protected] >> >> wrote: >> > >> >> hey guys, >> >> >> >> is still not able to be build on jenkins, through the relative path to >> the >> >> parent. locally everything is fine. >> >> >> >> >> > sure it is the relative path? >> > For me it looks like the deployment to snapshots does not work: >> > https://builds.apache.org/job/Onami-Logging/20/console >> > >> > Its a 401, which means not authorization. >> > >> > Not sure about how to fix it further :-) >> > >> > Cheers >> > >> > >> > >> >> I'm not the maven guru to know what to do. :) >> >> >> >> -- >> >> Viele Grüße/Best Regards >> >> >> >> Daniel Manzke >> >> >> > >> > >> > >> > -- >> > http://www.grobmeier.de >> > https://www.timeandbill.de >> > > > > -- > http://www.grobmeier.de > https://www.timeandbill.de
