On Thu, Dec 15, 2011 at 1:41 AM, Alon Bar-Lev <alon.bar...@gmail.com> wrote: > On Wed, Dec 14, 2011 at 8:41 PM, Martin Paljak <mar...@martinpaljak.net> > wrote: >> On 12/14/11 5:13 , Alon Bar-Lev wrote: >>> This is great!!!! >>> >>> I succeed in login to gerrit using google account. >>> How do I login to jenkins? >> Actually there is no similar SSO readily available for Jenkins, nor >> should it be necessary. Jenkins should work semi-automatically by >> building the branches/trees/changes it has to, like pre-building Gerrit >> changes or any other trees. >> >> The setup is manual, any repository is polled every X minutes, and >> builds created and uploaded as needed. Jenkins must be publicly >> available to see the status (green/red button) and any output (Gerrit >> can nicely cross-reference builds and Jenkins build results) >> >> Given that I have remotely "recovered" access to an otherwise >> disconnected linux host running the Windows VM-s (SSH tunneling) through >> a custom job on the Windows guest.... I'd prefer to keep the >> configurations under close inspection. If you have >> > > This is just great! > I could not believe it! > I posted pull request, automatically transfered to gerrit, and to > jenkins to build, while result is reported back!!! > Great work! > And I thought I need to push to gerrit and handle the cycle...
Oh... I was so excited I missed some important issue. When submitting a patchset it should be tested for build as atomic unit. Currently the system tries to compile each changeset by it-self. Many times this will not work, as patchset is divided into logical sections suited for review not for build. Alon. _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
