fwiw, gradle-jpi-plugin, throttle-concurrent-builds-plugin, jclouds-plugin and associated-files-plugin are all up to date now.
On Mon, Nov 11, 2013 at 12:23 PM, Kohsuke Kawaguchi < [email protected]> wrote: > > Yes, I was thinking about the same. The last run of this is Nov 9, 11:24pm > in EST. > > I really hope this is before the incident. But I'll find out soon. > > > On 11/11/2013 12:15 AM, Vojtech Juranek wrote: > >> On Sunday 10 November 2013 21:40:28 Luca Milanesio wrote: >> >>> That's really pitty :-( ... force push are dangerous, especially if you >>> don't have control over the Git Server. >>> >> >> I wonder if we can use our all.git [1] somehow (in the worst case scenario >> that github doesn't help us). When it try to clone it, it fails with >> remote >> error and when looking into web UI the changes are already synchronized >> with >> github. But IMHO still worth to investigate, orphan commits could still be >> there >> >> [1] http://git.jenkins-ci.org/?p=all.git;a=summary >> >> > > -- > Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ > Try Jenkins Enterprise, our professional version of Jenkins > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
