It's not linked to any account, users are managed on grandcentral.cloudbees.com there's indeed such a role, mostly unused at this stage. With templates used to create jobs, the only parameter for a job is the plugin name builds and console output is publicly visible, so that you should not need an account created for general purpose CI usage
2012/10/19 teilo <[email protected]> > Hi Nicolas, > > What accounts is this linked to? > > **** > I tried my github auth and grandcentral tells my my password is wrong > (rather than my email is not recognised) - so I know I'm at least half > registered... > > **** > > ** I 'm of course assuming that I haven't at some point used my personal > email to register with CB, and I should be able to log in as there is a > role "plugin-maintainers" :-)** > > /James**** > > On Thursday, 18 October 2012 19:04:13 UTC+1, nicolas de loof wrote: >> >> Hi folks, >> >> I eventually completed setup https://jenkins.ci.** >> cloudbees.com/job/plugins/<https://jenkins.ci.cloudbees.com/job/plugins/>with >> a job for all plugins on jenkinsci github. They all have been created >> as maven jobs, so this won't make sense for ruby or gradle ones, just ping >> me if you want to reconfigure with other build tools/rules. >> >> github hooks are set to trigger a build on commit to master >> >
