Hi Ulli,
I have published plugin source in my github
account: https://github.com/mkemme/sladiator-plugin
It can be forked from there now.
Cheers,
Martinsch
pirmdiena, 2012. gada 16. aprīlis 16:24:53 UTC+3, Ulli Hafner rakstīja:
Hi Martins,
do you already have your plug-in in your GitHub
Created https://github.com/jenkinsci/sladiator-plugin
Welcome aboard!
Ulli
On 04/17/2012 08:44 AM, Martins Kemme wrote:
Hi Ulli,
I have published plugin source in my github
account: https://github.com/mkemme/sladiator-plugin
It can be forked from there now.
Cheers,
Martinsch
Thanks Domi, thanks Jesse,
I followed your instructions and got into some trouble with authenticating
against github and jenkins-ci.org, since I have different usernames and
passwords but if I specified them on the command line as suggested no this
page
fyi, also created the corresponding job on
https://jenkins.ci.cloudbees.com/job/plugins/job/sladiator , waiting for
approval to migrate plugins job there
2012/4/17 Jesse Farinacci jie...@gmail.com
Greetings,
On Tue, Apr 17, 2012 at 3:15 AM, Ullrich Hafner
ullrich.haf...@gmail.com wrote:
Hi guys,
I am new to this group, so Hi, everyone.
I wrote a little plugin over the weekend and would like to host it on
the jenkins-ci.org as I read on the wiki, that that is the place to go
for.
Here is a link to the source-code and the short documentation I got so
far. I will update on that
Hi Domi,
thanks for the quick reply. It looks quite similar, but there are some
differences.
The repository connector downloads the artifact, while mine just sets
environment variables to the location of the artifacts and lets the build
steps decide what to do with that. And in my case I am
Thanks for the quick responses. I have just a few more question.
How do I release the plugin and make it discoverable by installed jenkins
servers?
Is there a template for the Wiki plugin page I can clone from?
Thanks,
Gesh
On Monday, April 16, 2012 10:07:07 AM UTC+2, Gesh Markov wrote:
Hi
As your plugin is based on Jenkins 1.447 - you should be fine by
updating/adding the scm info in the pom.xml and just doing a maven release.
(example pom:
https://github.com/jenkinsci/managed-scripts-plugin/blob/master/pom.xml)
This will publish the artifacts to 'http://repo.jenkins-ci.org'.