CI for plugins

[nicolas de loof-2]

Hi folks,

I eventually completed setup 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

[Baptiste MATHUS-3]

Thanks for the work, Nicolas, great improvement.

2012/10/18 nicolas de loof <[hidden email]>

Hi folks,

I eventually completed setup 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

--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

[Jesse Farinacci]

Bravo!

On Thu, Oct 18, 2012 at 2:03 PM, nicolas de loof
<[hidden email]> wrote:
> I eventually completed setup https://jenkins.ci.cloudbees.com/job/plugins/
> with a job for all plugins on jenkinsci github.
> github hooks are set to trigger a build on commit to master

Very helpful for everyone,

-Jesse

--
There are 10 types of people in this world, those
that can read binary and those that can not.

[teilo-3]

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/ 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

[nicolas de loof-2]

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 <[hidden email]>

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/ 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