Hi Mike, jenkins.ci.cloudbees.com instance is indeed designed to support plugin development and other community jobs (to reduce load on ci.jenkins-ci.org)
This instance was set > 1 year ago, just got buildhive active as a duplicate CI, I just disabled it this morning (see imod mail earlier on jenkins-dev list) https://jenkins.ci.cloudbees.com/job/plugins/job/ironmq-notifier-plugin/ is stable, so I think there's nothing much required here, isn't it ? 2013/10/14 Mike Caspar <[email protected]> > Hi there, > > I'm hoping someone can help. > > The other day, the builds got moved to https://jenkins.ci.cloudbees.com > > My project ironmq-notifier got moved as part of that. > > A few things are going on and I'm looking for some help. > > 1 - I cannot login at https://jenkins.ci.cloudbees.com with my github > account (or my email address)... > > 2 - The buildhive project that I've been using is completely gone (it has > effected the WIKI page Logos and badges).. > > Can someone please allow me to authenticate to the plugin I'm maintaining. > I want to be able to fix up what's wrong now. > > Also, I'd like to know, do we need to change the CI section of our POMs > now ? > > Can someone please help me out here ? > > Mike Caspar > > > -- > 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.
