When I try to access the cloudbee's build of my plugin, I don't see any option to build it, and my checkins don't seem to force a build.
If I try to login, I get this message: "You are not authorized to use this Jenkins instance. If you think this is an error please contact CloudBees support." Searching wiki doesn't give much details about the cloudbees integration. What account is needed? Is jenkins.ci.cloudbees.com using the same logins as jenkins-ci.org/account/? Are all jobs moved to jenkins.ci.cloudbees.com? Why aren't commits causing this job to run? I've used cloudbees for my other github projects, and have loved the integration. On Wed, Jul 25, 2012 at 12:19 PM, nicolas de loof <[email protected]>wrote: > repo forked, but failed to create the members team (I'm asking KK to check > the bot log for advice) > ci job on https://jenkins.ci.cloudbees.com/job/plugins/job/job-dsl/ > > > 2012/7/25 Justin Ryan <[email protected]> > >> I'd like to move development and ci of a new plugin to jenkin-ci.org: >> >> Can someone add us to the GitHub org? My id is quidryan, and my >> co-conspirator andrewharmellaw >> Can someone fork the project? It's current at >> https://github.com/JavaPosseRoundup/job-dsl-plugin >> Can someone create a ci.jenkins-ci.org build for it? It's using gradle >> (gradle-jpi-plugin) and I couldn't find another existing plugin to mimic. >> But it should do a simple "gradlew build". And I could use help on how to >> publish from a gradle build in lieu of the Maven release plugin. >> >> After that's done, I'll be adding >> https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin (do I need >> special permissions to add/edit wiki pages?) >> >> For reference this DSL primarily runs inside Jenkins as a plugin, and >> it's used to generated jobs in a programatic way. E.g. >> >> def gitUrl = 'git://github.com/JavaPosseRoundup/job-dsl-plugin.git' >> job { >> name 'PROJ-release' >> scm { >> git(gitUrl) >> } >> triggers { >> scm('*/15 * * * *') >> } >> authorization { >> permission(Permissions.ItemBuild, 'jill') >> permission(Permissions.ItemBuild, 'jack') >> } >> steps { >> maven('release deploy') >> shell('cleanup.sh') >> } >> } >> >> >> Some notable features: >> >> - DSL >> - Scriptable via Groovy >> - Direct control of XML, so that anything possible in a config.xml >> is possible via the DSL >> - Helper methods for common job configurations, e.g. scm, >> triggers, build steps >> - Plugin >> - DSL can be put directly in a job >> - DSL can be put into SCM and polled using standard SCM triggering >> - Multiple DSLs can be referenced as a time >> - Tracks Templates used, will update derivative jobs when template >> is changed >> >> A lot more details can be found on the wiki: >> https://github.com/JavaPosseRoundup/job-dsl-plugin/wiki >> > >
