> > Oh, and I had a question: since my personal repo was forked to the > Jenkins-CI repo, is there a "recommended" ? Should I make the changes on my > repo then "sync up" with the Jenkins-CI one, or should I just ditch my repo > all together and work only on the Jenkins one?
Ignore that... I answered my own question as I went through the publishing process :-p On Saturday, November 30, 2013 12:11:10 PM UTC-5, Maurice Williams wrote: > > Thanks Dominik, > > You're right, there is no "pure" credentials authentication just yet. The > closest thing to it using the API Token Jenkins generates for each user. It > was the easiest thing to get implemented :-p > > I also saw your comments on my last commit - this is my first Jenkins > plugin, so they are greatly appreciated! I'll make sure to review them > before publishing. > > Oh, and I had a question: since my personal repo was forked to the > Jenkins-CI repo, is there a "recommended" ? Should I make the changes on my > repo then "sync up" with the Jenkins-CI one, or should I just ditch my repo > all together and work only on the Jenkins one? > > > On Saturday, November 30, 2013 6:02:49 AM UTC-5, Dominik Bartholdi wrote: >> >> Hey, this is really cool, been waiting for something like this! >> The only thing I think is missing: support for the credentials plugin. >> >> Your repo is forked: >> https://github.com/jenkinsci/parameterized-remote-trigger-plugin >> A component in JIRA is created 'parameterized-remote-trigger’ and your >> the lead of it. >> The CI Jobs will be created by someone else (Nicolas/ndeloof?) >> >> /Domi >> >> >> On 30.11.2013, at 04:14, Maurice Williams <morf...@gmail.com> wrote: >> >> Hello there, >> >> I've created a new plugin to easily trigger a (parametrized or >> non-parametrized) job on a remote Jenkins host, with multiple >> authentication options (build token, API token or using the "build token >> root" plugin) and I would love to share this with the community. >> >> My GitHub ID is morficus <http://github.com/morficus> and the plugin >> already exists here: >> https://github.com/morficus/Parameterized-Remote-Trigger-Plugin, so you >> can just fork it. >> >> The one thing that's missing from it write now is automated test cases >> (either unit or functional). But I should have time to work on those come >> mid-December. >> >> I'm currently reading through the "Hosting Plugins" wiki page and should >> be ready to release the plugin soon. >> Let me know if there is anything I'm missing. >> >> -- >> 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 jenkinsci-de...@googlegroups.com. >> 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 jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
