Re: Backporting for 1.554.2 started

[Kohsuke Kawaguchi]

1.554.2 RC posted.


2014-05-14 5:39 GMT-07:00 oliver gondža :

> Backporting is finished. There are 12 fixes only, no critical or blocker
> issues. No fix was rejected.
>
>
> https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?
> reset=true&jqlQuery=labels+%3D+%221.554.2-fixed%22
>
> --
> oliver
>
> --
> 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/d/optout.
>



-- 
Kohsuke Kawaguchi

-- 
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/d/optout.

Re: Feedback on my tutorial.. please?

[Doron Shai]

Your tutorial is Great! still I am not able to make the myPlugin work

For some reason i am not able to see the plugin working on 1.554.1.

In addition, the class-path that was created was missing lot of stuff.

I used the class-path that was generated using 

mvn -U org.jenkins-ci.tools:maven-hpi-plugin:create
but still nothing is wokring.


On Friday, October 28, 2011 11:43:32 AM UTC+3, martinO wrote:
>
> Can you guys give me some constructive feedback on my tutorial? I bet lots 
> of stuff in it is not correct, so any corrections or pointers would be nice!
>
> The tutorial is for noobs, I'm trying to give some insight on the process 
> of creating a plug-in.
>
>
> https://wiki.jenkins-ci.org/display/~martino/2011/10/27/The+JenkinsPluginTotallySimpelGuide
>
> //Thanks! MartinO
> --
>

-- 
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/d/optout.

Jenkins - Koji plugin released

[Václav Tunka]

Hi,

this newly released plugin enables integration with 
Koji build 
system which is providing a clean-room environment for production builds. 
Main focus of Koji is on reproducibility, auditability and isolation of 
build executors which are freshly provisioned each time.

I created a wiki page about this newly released plugin, please have a look:
https://wiki.jenkins-ci.org/display/JENKINS/Koji+Plugin

Previous call for features on this list:
https://groups.google.com/forum/#!msg/jenkinsci-dev/HT8k6ODJPwk/8shnSMSFcXIJ


Cheers,
Vaclav

-- 
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/d/optout.

Fwd: html plugin

[Richard Bywater]

Can someone with Google Group admin rights please drop this automated bot
out of the list?

Richard.

-- Forwarded message --
From: Coinbase Support 
Date: Thu, May 15, 2014 at 4:59 AM
Subject: Re: html plugin
To: jenkinsci-us...@googlegroups.com


__
 Type your response ABOVE THIS LINE to reply Re: html plugin
*Coinbase* |  May
14, 2014 09:59AM PDT
Thank you for submitting your request. We have received your request and
are working on responding to you as soon as possible. If you have any
additional information to add to this case, please reply to this email.

Thanks in advance for your patience and support.
This message was sent to jenkinsci-us...@googlegroups.com in reference to
Case #330685.
 [[26dd16b4e7e70b4f324a082dea7725fe9dc84433-238049030]]

-- 
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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/d/optout.

Pitfalls in acceptance test harness

[Kohsuke Kawaguchi]

I've wasted some time today around selenium and browser issues, so I 
thought I'd share it in the hope that others will avoid the same issue.


- Chrome driver on Linux (2.10.267518) wasn't able to enter space
  character into the input field. (Chrome 31.0.1650.63)
  This is reported in [1] since Aug 2013.

- Firefox webdriver was unable to set text to .
  This is discussed in [2], and the suggestion was to downgrade
  to Firefox 28.


I'm currently working around this by using Firefox 28. I run Ubuntu 
12.04 LTS.




[1] http://code.google.com/p/chromedriver/issues/detail?id=467
[2] 
http://stackoverflow.com/questions/23412912/selenium-send-keys-doesnt-work-if-input-type-number

--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins

--
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/d/optout.

Re: Backporting for 1.554.2 started

[Christopher Orr]

Hmm.. are there still problems with the JIRA bot?

I pushed several [FIXED JENKINS-xxx] commits today, and over 24 hours 
ago to android-emulator-plugin, but JIRA still hasn't updated at all.


Thanks,
Chris


On 05/14/2014 02:51 PM, Stephen Connolly wrote:

Only not resolved because the bot has been slow to pick up the
[FIXED...] commit comment


On 14 May 2014 13:31, ogondza mailto:ogon...@gmail.com>> wrote:

On Wednesday, May 14, 2014 11:20:27 AM UTC+2, Stephen Connolly wrote:



https://github.com/jenkinsci/jenkins/commit/7c620e9fd321029e05f7cc994d3da1dde48411f7

But I also understand if this is too late in the day and we need
to wait for 1.554.3...


Yes, we will. Note the issue is not resolved.

--
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/d/optout.


--
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/d/optout.


--
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/d/optout.

Problem with Discard Old Builds removing the last stable build

[William Roberts]

Hi,

I'm having a problem with Discard Old Builds, both the built-in version and 
the plugin.
I use the Jenkins Text Finder plugin to downgrade "Successful" builds to 
"Unstable" if particular things show up in the logs, but if there is a run 
of unstable builds then eventually the oldest trully successful build will 
get deleted.

Is there an ordering problem here? Does the decision about what to discard 
get taken betfore the Text Finder plugin has been allowed to properly 
downgrade the status to Unstable? If so, how do I can the order in which 
the post build steps happen, or fix the plugin if it needs to take extra 
steps to publish the revised status more forcefully?

Thanks,
William

-- 
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/d/optout.

Re: JIRA Emails

[Oleg Nenashev]

The issue has been fixed yesterday.
BTW, all notifications during the outage period seem to be lost...

BR, Oleg Nenashev

среда, 7 мая 2014 г., 21:31:59 UTC+4 пользователь Larry Shatzer, Jr. 
написал:
>
> It's been since April 27th since the last email from JIRA was sent. Can 
> someone look into this?
>
> Thanks
>
> -- Larry
>

-- 
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/d/optout.

Re: Jenkins plugin for Microsoft Lync messenger

[Oleg Nenashev]

Probably, the links below could help you.

   - 
http://blogs.technet.com/b/lync/archive/2013/05/23/lync-skype-connectivity-available-today.aspx
 
   
   - 
https://supportforums.cisco.com/discussion/11617476/jabber-and-lync-integration 
   
   
I suppose it is possible to use existing plugins together with such wrappers
Previously I've used the "e-mail to Lync" approach, but I have no idea how 
it has been implemented.

среда, 7 мая 2014 г., 22:43:26 UTC+4 пользователь R Tyler Croy написал:
>
> (replies inline) 
>
> On Mon, 05 May 2014, Venkat Prasad wrote: 
>
> > Hi Team, 
> > 
> > Can you please let us know if there a Jenkins plugin for Microsoft Lync 
> > messenger? 
>
>  
>
>
> Doesn't look like it. 
>
>
> - R. Tyler Croy 
>
> -- 
>  Code:  
>   Chatter:  
>
>   % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F 
> -- 
>

-- 
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/d/optout.

Re: Problem releasing git-parameter-plugin. Banned? Or problem pushing tag?

[Niklaus Giger]

Hi Björn

After researching more in this list, I remarked that I am not the only one 
having problems.

Updating the pom.xml to allow  mvn-release-plugin:2.5 did not help.

After burning version 0.3 and 0.3.1 I was able to push using 
mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare (killed when 
taking too long)
mvn deploy

Now I just have to update the version in my pom.xml to SNAPSHOT if the 
plugin really shows up in a few hours.

Best regards

Niklaus

Am Mittwoch, 14. Mai 2014 19:40:56 UTC+2 schrieb Niklaus Giger:
>
> Hi Björn
>
> Thanks for your tip. This did not resolve my problem.
>
> But as suggested in 
> https://groups.google.com/forum/#!msg/jenkinsci-dev/OvWw0zqJI_E/-1PvLg_DeYkJI 
> switched from using ssh/git to https. 
>
> And now pushing to github works.
>
> mvn release:prepare release:perform  reports now success (after several 
> hours) but my build does not show up. Will report this problem in separate 
> thread.
>
> Thanks for your help!
>
> Best regards
>
> Niklaus
>
> Am Montag, 12. Mai 2014 22:34:52 UTC+2 schrieb Björn Berg:
>>
>> Hi Niklaus,
>>
>> I had the same problem months ago. You cannot use the environment 
>> variables -Dusername and -Dpassword any longer while releasing a plugin.
>>
>> Edit your Maven settings.xml and add a new server section to it:
>> 
>> maven.jenkins-ci.org
>>  niklaus_giger
>>  cleartext_pw
>>  
>>
>> See https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins (section 
>> Releasing to jenkins-ci.org) for more details on how to modify your 
>> settings.xml.
>>
>> Kind regards
>> Björn
>>
>> Am 11.05.2014 um 17:14 schrieb Niklaus Giger :
>>
>> Hi
>>
>> I am trying to release my first jenkins plugin. I successfully pushed all 
>> my changes to https://github.com/jenkinsci/git-parameter-plugin
>>
>> Calling 
>> mvn release:prepare release:perform -Dusername=niklaus_giger 
>> -Dpassword=cleartext_pw
>> always resulted in 
>> [INFO] Scanning for projects...
>> [INFO]   
>>   
>>
>> [INFO] 
>> 
>> [INFO] Building Git Parameter Plug-In 0.3
>> [INFO] 
>> 
>> [INFO] 
>> [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ 
>> git-parameter ---
>> [INFO] Resuming release from phase 'scm-tag'
>> [INFO] Tagging release with the label git-parameter-0.3...
>> [INFO] Executing: /bin/sh -c cd /opt/src/git-parameter.jenkins.ci && git 
>> tag -F /tmp/maven-scm-790953102.commit git-parameter-0.3
>> [INFO] Working directory: /opt/src/git-parameter.jenkins.ci
>> [INFO] Executing: /bin/sh -c cd /opt/src/git-parameter.jenkins.ci && git 
>> push 
>> ssh://niklaus_giger:cleartext...@github.com:jenkinsci/git-parameter-plugin.gitgit-parameter-0.3
>> [INFO] Working directory: /opt/src/git-parameter.jenkins.ci
>> [INFO]   
>>   
>>
>> [INFO] 
>> 
>> [INFO] Skipping Git Parameter Plug-In
>> [INFO] This project has been banned from the build due to previous 
>> failures.
>> [INFO] 
>> 
>>
>> Can anybody tell me why this plugin is banned or whether I must (and then 
>> how) resolve the push problem.
>>
>> Best regards in advance.
>>
>> Niklaus Giger
>>
>> P.S. The pom.xml already defines 0.3 (instead of 0.3-SNAPSHOT) as 
>> version, as I corrected a few things in the pom.xml.
>>
>>
>> -- 
>> 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/d/optout.
>>
>>
>>

-- 
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/d/optout.

Re: Problem releasing git-parameter-plugin. Banned? Or problem pushing tag?

[Niklaus Giger]

Hi Björn

Thanks for your tip. This did not resolve my problem.

But as suggested in 
https://groups.google.com/forum/#!msg/jenkinsci-dev/OvWw0zqJI_E/-1PvLg_DeYkJ 
I switched from using ssh/git to https. 

And now pushing to github works.

mvn release:prepare release:perform  reports now success (after several 
hours) but my build does not show up. Will report this problem in separate 
thread.

Thanks for your help!

Best regards

Niklaus

Am Montag, 12. Mai 2014 22:34:52 UTC+2 schrieb Björn Berg:
>
> Hi Niklaus,
>
> I had the same problem months ago. You cannot use the environment 
> variables -Dusername and -Dpassword any longer while releasing a plugin.
>
> Edit your Maven settings.xml and add a new server section to it:
> 
> maven.jenkins-ci.org
>  niklaus_giger
>  cleartext_pw
>  
>
> See https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins (section 
> Releasing to jenkins-ci.org) for more details on how to modify your 
> settings.xml.
>
> Kind regards
> Björn
>
> Am 11.05.2014 um 17:14 schrieb Niklaus Giger 
> >:
>
> Hi
>
> I am trying to release my first jenkins plugin. I successfully pushed all 
> my changes to https://github.com/jenkinsci/git-parameter-plugin
>
> Calling 
> mvn release:prepare release:perform -Dusername=niklaus_giger 
> -Dpassword=cleartext_pw
> always resulted in 
> [INFO] Scanning for projects...
> [INFO]
>  
>
> [INFO] 
> 
> [INFO] Building Git Parameter Plug-In 0.3
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ 
> git-parameter ---
> [INFO] Resuming release from phase 'scm-tag'
> [INFO] Tagging release with the label git-parameter-0.3...
> [INFO] Executing: /bin/sh -c cd /opt/src/git-parameter.jenkins.ci && git 
> tag -F /tmp/maven-scm-790953102.commit git-parameter-0.3
> [INFO] Working directory: /opt/src/git-parameter.jenkins.ci
> [INFO] Executing: /bin/sh -c cd /opt/src/git-parameter.jenkins.ci && git 
> push 
> ssh://niklaus_giger:cleartext...@github.com:jenkinsci/git-parameter-plugin.gitgit-parameter-0.3
> [INFO] Working directory: /opt/src/git-parameter.jenkins.ci
> [INFO]
>  
>
> [INFO] 
> 
> [INFO] Skipping Git Parameter Plug-In
> [INFO] This project has been banned from the build due to previous 
> failures.
> [INFO] 
> 
>
> Can anybody tell me why this plugin is banned or whether I must (and then 
> how) resolve the push problem.
>
> Best regards in advance.
>
> Niklaus Giger
>
> P.S. The pom.xml already defines 0.3 (instead of 0.3-SNAPSHOT) as version, 
> as I corrected a few things in the pom.xml.
>
>
> -- 
> 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/d/optout.
>
>
>

-- 
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/d/optout.

Re: [ANN] Open-sourcing workflow plugin

[Jesse Glick]

On Wed, May 14, 2014 at 5:17 AM, James Nord (jnord)  wrote:
> According to the agendas this looks like it is only the Boston JUG?
>   "Workflow in Jenkins   Jesse Glick, CloudBees, Inc."

Yes, sorry, I cannot come to Berlin JUC.

-- 
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/d/optout.

Re: [ANN] Open-sourcing workflow plugin

[Kohsuke Kawaguchi]

Yes, James, you are famous now, at least inside CloudBees!


2014-05-14 2:14 GMT-07:00 James Nord (jnord) :

> "The James Nord operator" :-)
>
> /James
>
> > -Original Message-
> > From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-
> > d...@googlegroups.com] On Behalf Of Kohsuke Kawaguchi
> > Sent: 13 May 2014 23:08
> > To: jenkinsci-dev@googlegroups.com
> > Subject: [ANN] Open-sourcing workflow plugin
> >
> >
> > Jesse and I have been working on the "workflow" plugin, and we think it
> got
> > the point that we can open-source it.
> >
> > We've talked about the workflow plugin several occasions mainly offline.
> > Put simply, it's a new job type where we aim to solve a number of pain
> points
> > --- such as job sprawl, long-running tasks, jobs that span multiple
> computers,
> > etc.
> >
> > Slide deck [4] talks a bit more about the motivation and what it aims to
> solve.
> > And we've talked some more about this in the last Scalability Summit
> [5]. But
> > we've been spending more time coding than documenting, so if you are
> > interested in this, you'd have to come to Jenkins User Conference [6]
> where
> > we plan to spend some quality time talking about this plugin.
> >
> >
> > The code is at [1], the issue tracker component is at [2], and if you
> want to
> > help us hack on this, Jesse and I track our TODOs in [3]. Trello tracks
> short-
> > term tasks while JIRA should be used for bug reports and "nice to have"
> > backlogs.
> >
> > This series of plugins are still very much a work in progress, and we
> don't
> > recommend you to deploy this in your production Jenkins instance just
> yet.
> >
> > But we've been seeing great interest from users about this feature, and
> we
> > think this is a nice moment in that we have enough meat to show you what
> > we are trying to do, at the same time things are in flux enough that we
> can
> > make significant breaking changes based on feedback.
> >
> > To play with this, see readme of [1].
> >
> >
> > [1] https://github.com/jenkinsci/workflow-plugin
> > [2] https://issues.jenkins-ci.org/browse/JENKINS/component/18820
> > [3] https://trello.com/b/u2fJQnDX/workflow
> > [4]
> > https://docs.google.com/a/cloudbees.com/presentation/d/1wwqp2x4kwZk
> > etpoLzrn85IUOULmj9zFtcm1o1XepgbE/edit#slide=id.g2c4c22109_028
> > [5]
> > https://docs.google.com/document/d/1GqkWPnp-
> > bvuObGlSe7t3k76ZOD2a8Z2M1avggWoYKEs/edit#heading=h.593939myiof9
> > [6] http://www.cloudbees.com/jenkins/juc-2014
> > --
> > Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Jenkins
> > Enterprise, our professional version of Jenkins
> >
> > --
> > 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/d/optout.
>
> --
> 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/d/optout.
>



-- 
Kohsuke Kawaguchi

-- 
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/d/optout.

Re: [ANN] Open-sourcing workflow plugin

[Kohsuke Kawaguchi]

In Berlin, I think I'll spend considerable part of my talk to discuss
workflow.


2014-05-14 2:17 GMT-07:00 James Nord (jnord) :

> > if you are
> > interested in this, you'd have to come to Jenkins User Conference [6]
> where
> > we plan to spend some quality time talking about this plugin.
>
> According to the agendas this looks like it is only the Boston JUG?
>   "Workflow in Jenkins   Jesse Glick, CloudBees, Inc."
>
> Is there anything planned for berlin that I've missed / has not been
> announced?
>
> /James
>
> --
> 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/d/optout.
>



-- 
Kohsuke Kawaguchi

-- 
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/d/optout.

Re: I want to maintain a plugin...

[Satinder Singh]

I have added Vladimir as collaborator on github for this plugin. i hope
this would enable him.

On Wednesday, May 14, 2014, Ulli Hafner  wrote:
> I forked the repository to
https://github.com/jenkinsci/scripted-cloud-plugin
> and added you and the original author as committers.
> So you can already integrate your changes while we are waiting for an
answer of the original author to see if it is ok to take over the ownership…
> Am 13.05.2014 um 23:58 schrieb Vladimir Fedorov :
>
> Yeap, I'll try.
> The plugin wasn't changed for 2 years so I doubt the maintainer will
respond.
>
>
> 2014-05-14 1:55 GMT+04:00 Richard Bywater :
>>
>> I'd say the first best step (and I could be wrong here) is to try
contacting the existing maintainer to see if they still want to maintain
that plugin.
>> Currently I see that the source isn't under the jenkinsci org in Github
which probably complicates things a bit as well but I'd start with making
contact and take it from there.
>> Richard.
>>
>> On Wed, May 14, 2014 at 9:15 AM, Fedorov Vladimir 
wrote:
>>>
>>> Hi everyone,
>>>
>>> I want to maintain a plugin.
>>> It has not been changed for a while but I find it useful
>>> https://wiki.jenkins-ci.org/display/JENKINS/Scripted+Cloud+plugin
>>>
>>> What should I do to become a maintainer?
>>>
>>> I've already forked the code and make some minor fixes:
>>> https://github.com/feoff3/scripted-cloud-plugin
>>>
>>> Thanks in advance,
>>> Vladimir Fedorov
>>>
>>> --
>>> 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/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-dev/giY06oHGvf8/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
jenkinsci-dev+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> 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/d/optout.
>
>

-- 
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/d/optout.

Re: git-parameter plugin

[Łukasz Miłkowski]

Hello

Sorry that I was unavailable for such a long time, but I've changed 
workpace and no longer needed this plugin on daily basis, and because of 
new workplace, don't have much time to configure jenkins on my local to 
make releases.
Niklaus have contacted me and I don't have any problem with that kind of 
collaboration. Although I know that in the mean of upcomming few month I 
know I would like to use it again and add come features to it then. 
So I would be happy if we will both maintain this plugin. Also it will be 
best for a plugin to merge this branch as master.

Cheers, and once again sorry for inconvenience
Łukasz Miłkowski

W dniu sobota, 3 maja 2014 23:11:24 UTC+2 użytkownik Niklaus Giger napisał:
>
> I pushed the most important changes to 
> https://github.com/jenkinsci/git-parameter-plugin/tree/preview_0_3 and 
> found via the git commits the email of the old maintainer (cc this message, 
> too). I will give him a few days (lets say till next Friday) to answer. If 
> not I will merge the branch preview_0_3 into master and release it.
>
> I have not yet found a solution to the problem that no tags are shown when 
> there is no (or not yet) a workspace available.
>
> Best regards
>
> Niklaus
>
> Am Samstag, 3. Mai 2014 11:52:25 UTC+2 schrieb Ullrich Hafner:
>>
>>
>> Am 02.05.2014 um 16:59 schrieb Niklaus Giger :
>>
>> Hi Ulli
>>
>> Thanks for your confidence in me. On wiki.jenkins-ci.org I added myself 
>> some time ago as niklaus_giger.
>>
>> I did not find an email for the maintainer (lukanus) neither.
>>
>> Thanks for the access rights. I would appreciate if you could answer the 
>> following questions for which I could not
>> find an answer in 
>> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins.
>>
>> * Did you review my changes? I would really appreciate if somebody could 
>> review the plugin. Specially a some days later before publishing.
>>
>>
>> I do not. You can ask for feedback on the dev-list, maybe someone else 
>> will. But normally the spare time of the developers is quite limited so 
>> they focus on their own work...
>>
>> * Shall I push my changes directly to the master branch of 
>> jenkins-ci/git-parameter or open a branch there?
>>
>>
>> This is your decision. Some developers always use feature branches, some 
>> others commit directly to master… 
>>
>> * Is it a good idea to change the connection developerConnection elements 
>> in pom.xml to use jenkinsci instead of lukanus?
>>
>>
>> Yes, please update the pom
>>
>> * Should I copy the description of the 
>> https://wiki.jenkins-ci.org/display/JENKINS/Git+Parameter+Plugin to the 
>> Readme of the code?
>>
>>
>> Yes, a README would be good that contains some more information…
>>
>> Ulli
>>
>> Thanks in advance
>>
>> Niklaus Giger
>>
>> Am Donnerstag, 1. Mai 2014 22:14:17 UTC+2 schrieb Ullrich Hafner:
>>>
>>> I also think this plugin is not maintained anymore… So feel free to 
>>> integrate your changes and take over the development. 
>>> I did not find an email of the maintainer so if he is reading this list 
>>> he still can object to taking over the plugin development.
>>>
>>> Your access rights are all set. Welcome aboard!
>>>
>>> Should I also set your name as default assignee in Jira? What is your 
>>> Jenkins ID?
>>>
>>> Ulli 
>>>
>>> Am 01.05.2014 um 21:59 schrieb Niklaus Giger :
>>>
>>> Hi everybody
>>>
>>> I am long-time and happy user of Jenkins. Since a few years Jenkins (and 
>>> before Hudson) is a tool I use
>>> almost daily. I almost always found the plugins I needed and investing 
>>> once 100US$ via 
>>> freedomsponsors.org fixed a memory problem for me.
>>>
>>> Lately I needed for paid work the features provided by git-parameter. I 
>>> had to invest half a day to
>>> made it work and I would be willing to take over this (almost) dormant 
>>> plugin.
>>>
>>> I collected the following interesting points about it:
>>>
>>>- The 
>>>https://wiki.jenkins-ci.org/display/JENKINS/Git+Parameter+Plugin has 
>>>> 3500 installations.
>>>- Last version was 0.2 as of December 2012
>>>- Old (> 2 years) open pull requests under 
>>>https://github.com/lukanus/git-parameter/pulls
>>>- 2 commits in 2014 under 
>>>https://github.com/lukanus/git-parameter/commits/master
>>>- 34 forks
>>>- about 5 people having pushed back changes in their fork
>>>- But no new version
>>>- Sorting/filtering in via 
>>>
>>> https://github.com/graeme-hill/git-parameter/commit/92af536d617cc88684dfa48dd19ea354db2a136f
>>>- My work is under https://github.com/ngiger/git-parameter
>>>
>>> I am willing to work on this plugin and would appreciate any comments on 
>>> how I can achieve it. A simple pull
>>> request will not suffice, as also under 
>>> https://github.com/jenkinsci/git-parameter-plugin/pulls you severals 
>>> which are
>>> open for over 2 years.
>>>
>>> Best regards
>>>
>>> Niklaus
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 

Re: Backporting for 1.554.2 started

[Stephen Connolly]

Only not resolved because the bot has been slow to pick up the [FIXED...]
commit comment


On 14 May 2014 13:31, ogondza  wrote:

> On Wednesday, May 14, 2014 11:20:27 AM UTC+2, Stephen Connolly wrote:
>>
>>
>>
>> https://github.com/jenkinsci/jenkins/commit/7c620e9fd321029e05f7cc994d3da1dde48411f7
>>
>> But I also understand if this is too late in the day and we need to wait
>> for 1.554.3...
>>
>
> Yes, we will. Note the issue is not resolved.
>
> --
> 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/d/optout.
>

-- 
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/d/optout.

Re: Backporting for 1.554.2 started

[oliver gondža]

Backporting is finished. There are 12 fixes only, no critical or blocker  
issues. No fix was rejected.


https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+%221.554.2-fixed%22

--
oliver

--
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/d/optout.

RE: [ANN] Open-sourcing workflow plugin

[Sandell, Robert]

My thoughts as well when I read it :D

The workflow plugin(s) seems like a truly awesome concept btw, It seems to be 
able to do almost everything we’ve discussed over the years, except brew my 
coffee while I wait for the build finish, but I guess I could write a plugin 
for that ;)

/B

From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On 
Behalf Of Emanuele Zattin
Sent: den 14 maj 2014 11:15
To: jenkinsci-dev@googlegroups.com
Subject: RE: [ANN] Open-sourcing workflow plugin


That should totally appear on your resume James :-)
On May 14, 2014 11:14 AM, "James Nord (jnord)" 
mailto:jn...@cisco.com>> wrote:
"The James Nord operator" :-)

/James

> -Original Message-
> From: jenkinsci-dev@googlegroups.com 
> [mailto:jenkinsci-
> d...@googlegroups.com] On Behalf Of Kohsuke 
> Kawaguchi
> Sent: 13 May 2014 23:08
> To: jenkinsci-dev@googlegroups.com
> Subject: [ANN] Open-sourcing workflow plugin
>
>
> Jesse and I have been working on the "workflow" plugin, and we think it got
> the point that we can open-source it.
>
> We've talked about the workflow plugin several occasions mainly offline.
> Put simply, it's a new job type where we aim to solve a number of pain points
> --- such as job sprawl, long-running tasks, jobs that span multiple computers,
> etc.
>
> Slide deck [4] talks a bit more about the motivation and what it aims to 
> solve.
> And we've talked some more about this in the last Scalability Summit [5]. But
> we've been spending more time coding than documenting, so if you are
> interested in this, you'd have to come to Jenkins User Conference [6] where
> we plan to spend some quality time talking about this plugin.
>
>
> The code is at [1], the issue tracker component is at [2], and if you want to
> help us hack on this, Jesse and I track our TODOs in [3]. Trello tracks short-
> term tasks while JIRA should be used for bug reports and "nice to have"
> backlogs.
>
> This series of plugins are still very much a work in progress, and we don't
> recommend you to deploy this in your production Jenkins instance just yet.
>
> But we've been seeing great interest from users about this feature, and we
> think this is a nice moment in that we have enough meat to show you what
> we are trying to do, at the same time things are in flux enough that we can
> make significant breaking changes based on feedback.
>
> To play with this, see readme of [1].
>
>
> [1] https://github.com/jenkinsci/workflow-plugin
> [2] https://issues.jenkins-ci.org/browse/JENKINS/component/18820
> [3] https://trello.com/b/u2fJQnDX/workflow
> [4]
> https://docs.google.com/a/cloudbees.com/presentation/d/1wwqp2x4kwZk
> etpoLzrn85IUOULmj9zFtcm1o1XepgbE/edit#slide=id.g2c4c22109_028
> [5]
> https://docs.google.com/document/d/1GqkWPnp-
> bvuObGlSe7t3k76ZOD2a8Z2M1avggWoYKEs/edit#heading=h.593939myiof9
> [6] http://www.cloudbees.com/jenkins/juc-2014
> --
> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Jenkins
> Enterprise, our professional version of Jenkins
>
> --
> 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/d/optout.

--
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/d/optout.
--
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/d/optout.

-- 
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/d/optout.

Re: Backporting for 1.554.2 started

[ogondza]

On Wednesday, May 14, 2014 11:20:27 AM UTC+2, Stephen Connolly wrote:
>
>
>
> https://github.com/jenkinsci/jenkins/commit/7c620e9fd321029e05f7cc994d3da1dde48411f7
>
> But I also understand if this is too late in the day and we need to wait 
> for 1.554.3...
>

Yes, we will. Note the issue is not resolved.

-- 
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/d/optout.

Re: mvn release does not work, only publishes SNAPSHOT releases

[Stephen Connolly]

Well I have long maintained that Jenkins's pom structure "does it all
wrong" but any time I have wanted to try and fix it *and* had a time window
to try, KK puts too much of a barrier with regard to people getting
confused.

I guess it doesn't help that to fix it, I need to redo the hpi plugin so
that it actually works the Maven way... but then if the people who wrote
the original hpi plugin understood the Maven way they would never have
written the Maven project type in Jenkins the way they did and it would not
be evil!


On 13 May 2014 23:46, Ivan Kalinin  wrote:

> Has similar problem recently and your fix did help. But latest parent (
> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/jenkins/1.33/)
> still uses 2.2.2 -- is there any plan to fix that?
>
>
> On Saturday, March 8, 2014 11:05:15 PM UTC+4, Stephen Connolly wrote:
>
>> mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare
>>
>> And if that tags correctly then same with perform. Should fix the
>> -SNAPSHOT issue... The other issue could be a different story
>>
>> On Saturday, 8 March 2014, Ulli Hafner  wrote:
>>
>>> git version is 1.8.5.3
>>>
>>> The dependency hack does only work if the plugin is top-level. I’m
>>> releasing in a sub-folder.
>>>
>>> Am 08.03.2014 um 12:36 schrieb Stephen Connolly <
>>> stephen.alan.conno...@gmail.com>:
>>>
>>> What version of git are you using?
>>>
>>> Anything after 1.8.4 needs m-r-p 2.5 or the dependency hack
>>>
>>> On Saturday, 8 March 2014, Ulli Hafner  wrote:
>>>
>>> Has someone a workaround for that problem if the plugin/libray to
>>> release is not in the top-level folder of a git project?
>>>
>>> My findbugs plugin is divided into
>>> - findbugs-plugin/library shaded findbugs library
>>> - findbugs-plugin/plugin actual findbugs plugin
>>>
>>> When I try to release maven does only publish a SNAPSHOT.
>>>
>>>
>>> Am 11.02.2014 um 18:52 schrieb Ulli Hafner :
>>>
>>> That would be helpful, yes.
>>>
>>> BTW: This fix does only work if the project is not in a sub-folder :-(
>>>
>>> Ulli
>>>
>>> Am 10.02.2014 um 23:16 schrieb Stefan Wolf :
>>>
>>> Should we pull a new release of 
>>> https://github.com/jenkinsci/pomincoporating the changes to the release 
>>> plugin configuration?
>>>
>>> Am Dienstag, 14. Januar 2014 17:47:35 UTC+1 schrieb Vincent Latombe:
>>>
>>> I hit that problem recently, adding
>>>
>>> 
>>>   maven-release-plugin
>>>   ${maven-release-plugin.version}
>>>   
>>> 
>>>   org.apache.maven.scm
>>>   maven-scm-provider-gitexe
>>>   1.9
>>> 
>>>   
>>> 
>>>
>>> was enough to work with latest git (1.8.5.2).
>>>
>>> HTH,
>>>
>>> Vincent
>>>
>>>
>>> 2014/1/13 Dominik Bartholdi 
>>>
>>> ;-)
>>>
>>> I’ll try to take a look at the m-r-p, but I currently can’t promise any
>>> time - sorry :(
>>> /Domi
>>>
>>>
>>> On 13.01.2014, at 09:21, Stephen Connolly 
>>> wrote:
>>>
>>>
>>>
>>> On Sunday, 12 January 2014, Dominik Bartholdi wrote:
>>>
>>> The maven team
>>>
>>>
>>> Nice dodge of self promotion there
>>>
>>> ;-)
>>>
>>> Btw do you want to take a run at m-r-p?
>>>
>>>
>>> has just release a git provider based on jgit, if you configure the
>>> release plugin to use this one, then you don’t have to downgrade git.
>>>
>>> http://maven.apache.org/scm/maven-scm-providers/maven-scm-pr
>>> oviders-git/maven-scm-provider-jgit/index.html
>>>
>>> /Domi
>>>
>>> On 12.01.2014, at 11:52, Nigel Magnay  wrote:
>>>
>>> I've just had this problem too, with two separate plugins.
>>>
>>> maven-release-plugin is just total crapola. Just do a manual mvn
>>> versions:set and deploy.
>>>
>>>
>>>
>>> On Sat, Jan 4, 2014 at 4:17 PM, ogondza  wrote:
>>>
>>>  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/d/optout.
>>>
>>>
>>>
>>
>> --
>> Sent from my phone
>>
>  --
> 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/d/optout.
>

-- 
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/d/optout.

Re: Backporting for 1.554.2 started

[Stephen Connolly]

I am strongly inclined to advocate for the inclusion of:

https://github.com/jenkinsci/jenkins/commit/7c620e9fd321029e05f7cc994d3da1dde48411f7

But I also understand if this is too late in the day and we need to wait
for 1.554.3...


On 5 May 2014 22:13, oliver gondža  wrote:

> Backporting window for 1.554.2 is opened since April 30th. You can expect
> RC at May 14th.
>
> https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?
> reset=true&jqlQuery=labels+%3D+%221.554.2-fixed%22
>
> --
> oliver
>
> --
> 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/d/optout.
>

-- 
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/d/optout.

Re: New plugin request: send-to-eclipse

[Cees Bos]

Hi Ulli,

Thanks a lot!
I will upload the sources and create the wiki page for the plugin.

Regards,
Cees


On Mon, May 12, 2014 at 10:14 AM, Ulli Hafner wrote:

> https://github.com/jenkinsci/send-stacktrace-to-eclipse-plugin
>
> Welcome aboard!
>
> Ulli
>
> Am 08.05.2014 um 21:19 schrieb Cees Bos :
>
> Hi Ulli,
>
> Thanks for the reply.
> It is not on Github yet. I read on the wiki page (
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins) that is not
> necessary.
> If that is easier for you I can create a repo and push it to there, so you
> can clone it.
>
> I don't know what is easier to do for you?
>
> Regards,
> Cees
>
>
>
>
> On Wed, May 7, 2014 at 10:11 PM, Ulli Hafner wrote:
>
>> Is your plugin already in GitHub so we can fork it?
>>
>> Am 25.04.2014 um 11:00 schrieb Cees Bos :
>>
>> We have developed a plugin which can send a stacktrace of a failing
>> testcase to Eclipse.
>> In Eclipse you need a plugin, which can receive the request.
>> The Eclipse plugin can be found here:
>> http://cbos.github.io/OpenFromExternalEvent/
>>
>>
>> *Jenkins Plugin Name:* send-to-eclipse-plugin
>> 
>> *Github User:* cbos
>> *Jenkins-ci org account:* cbos
>>
>> Regards,
>> Cees
>>
>> --
>> 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/d/optout.
>>
>>
>>
>
> --
> 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/d/optout.
>
>
>

-- 
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/d/optout.

RE: [ANN] Open-sourcing workflow plugin

[James Nord (jnord)]

> if you are
> interested in this, you'd have to come to Jenkins User Conference [6] where
> we plan to spend some quality time talking about this plugin.

According to the agendas this looks like it is only the Boston JUG?
  "Workflow in Jenkins   Jesse Glick, CloudBees, Inc."

Is there anything planned for berlin that I've missed / has not been announced?

/James

-- 
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/d/optout.

RE: [ANN] Open-sourcing workflow plugin

[Emanuele Zattin]

That should totally appear on your resume James :-)
On May 14, 2014 11:14 AM, "James Nord (jnord)"  wrote:

> "The James Nord operator" :-)
>
> /James
>
> > -Original Message-
> > From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-
> > d...@googlegroups.com] On Behalf Of Kohsuke Kawaguchi
> > Sent: 13 May 2014 23:08
> > To: jenkinsci-dev@googlegroups.com
> > Subject: [ANN] Open-sourcing workflow plugin
> >
> >
> > Jesse and I have been working on the "workflow" plugin, and we think it
> got
> > the point that we can open-source it.
> >
> > We've talked about the workflow plugin several occasions mainly offline.
> > Put simply, it's a new job type where we aim to solve a number of pain
> points
> > --- such as job sprawl, long-running tasks, jobs that span multiple
> computers,
> > etc.
> >
> > Slide deck [4] talks a bit more about the motivation and what it aims to
> solve.
> > And we've talked some more about this in the last Scalability Summit
> [5]. But
> > we've been spending more time coding than documenting, so if you are
> > interested in this, you'd have to come to Jenkins User Conference [6]
> where
> > we plan to spend some quality time talking about this plugin.
> >
> >
> > The code is at [1], the issue tracker component is at [2], and if you
> want to
> > help us hack on this, Jesse and I track our TODOs in [3]. Trello tracks
> short-
> > term tasks while JIRA should be used for bug reports and "nice to have"
> > backlogs.
> >
> > This series of plugins are still very much a work in progress, and we
> don't
> > recommend you to deploy this in your production Jenkins instance just
> yet.
> >
> > But we've been seeing great interest from users about this feature, and
> we
> > think this is a nice moment in that we have enough meat to show you what
> > we are trying to do, at the same time things are in flux enough that we
> can
> > make significant breaking changes based on feedback.
> >
> > To play with this, see readme of [1].
> >
> >
> > [1] https://github.com/jenkinsci/workflow-plugin
> > [2] https://issues.jenkins-ci.org/browse/JENKINS/component/18820
> > [3] https://trello.com/b/u2fJQnDX/workflow
> > [4]
> > https://docs.google.com/a/cloudbees.com/presentation/d/1wwqp2x4kwZk
> > etpoLzrn85IUOULmj9zFtcm1o1XepgbE/edit#slide=id.g2c4c22109_028
> > [5]
> > https://docs.google.com/document/d/1GqkWPnp-
> > bvuObGlSe7t3k76ZOD2a8Z2M1avggWoYKEs/edit#heading=h.593939myiof9
> > [6] http://www.cloudbees.com/jenkins/juc-2014
> > --
> > Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Jenkins
> > Enterprise, our professional version of Jenkins
> >
> > --
> > 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/d/optout.
>
> --
> 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/d/optout.
>

-- 
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/d/optout.

RE: [ANN] Open-sourcing workflow plugin

[James Nord (jnord)]

"The James Nord operator" :-)

/James

> -Original Message-
> From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-
> d...@googlegroups.com] On Behalf Of Kohsuke Kawaguchi
> Sent: 13 May 2014 23:08
> To: jenkinsci-dev@googlegroups.com
> Subject: [ANN] Open-sourcing workflow plugin
> 
> 
> Jesse and I have been working on the "workflow" plugin, and we think it got
> the point that we can open-source it.
> 
> We've talked about the workflow plugin several occasions mainly offline.
> Put simply, it's a new job type where we aim to solve a number of pain points
> --- such as job sprawl, long-running tasks, jobs that span multiple computers,
> etc.
> 
> Slide deck [4] talks a bit more about the motivation and what it aims to 
> solve.
> And we've talked some more about this in the last Scalability Summit [5]. But
> we've been spending more time coding than documenting, so if you are
> interested in this, you'd have to come to Jenkins User Conference [6] where
> we plan to spend some quality time talking about this plugin.
> 
> 
> The code is at [1], the issue tracker component is at [2], and if you want to
> help us hack on this, Jesse and I track our TODOs in [3]. Trello tracks short-
> term tasks while JIRA should be used for bug reports and "nice to have"
> backlogs.
> 
> This series of plugins are still very much a work in progress, and we don't
> recommend you to deploy this in your production Jenkins instance just yet.
> 
> But we've been seeing great interest from users about this feature, and we
> think this is a nice moment in that we have enough meat to show you what
> we are trying to do, at the same time things are in flux enough that we can
> make significant breaking changes based on feedback.
> 
> To play with this, see readme of [1].
> 
> 
> [1] https://github.com/jenkinsci/workflow-plugin
> [2] https://issues.jenkins-ci.org/browse/JENKINS/component/18820
> [3] https://trello.com/b/u2fJQnDX/workflow
> [4]
> https://docs.google.com/a/cloudbees.com/presentation/d/1wwqp2x4kwZk
> etpoLzrn85IUOULmj9zFtcm1o1XepgbE/edit#slide=id.g2c4c22109_028
> [5]
> https://docs.google.com/document/d/1GqkWPnp-
> bvuObGlSe7t3k76ZOD2a8Z2M1avggWoYKEs/edit#heading=h.593939myiof9
> [6] http://www.cloudbees.com/jenkins/juc-2014
> --
> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Jenkins
> Enterprise, our professional version of Jenkins
> 
> --
> 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/d/optout.

-- 
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/d/optout.

Re: I want to maintain a plugin...

[Ulli Hafner]

I forked the repository to https://github.com/jenkinsci/scripted-cloud-plugin
and added you and the original author as committers.

So you can already integrate your changes while we are waiting for an answer of 
the original author to see if it is ok to take over the ownership…

Am 13.05.2014 um 23:58 schrieb Vladimir Fedorov :

> Yeap, I'll try. 
> The plugin wasn't changed for 2 years so I doubt the maintainer will respond.
> 
> 
> 2014-05-14 1:55 GMT+04:00 Richard Bywater :
> I'd say the first best step (and I could be wrong here) is to try contacting 
> the existing maintainer to see if they still want to maintain that plugin.
> 
> Currently I see that the source isn't under the jenkinsci org in Github which 
> probably complicates things a bit as well but I'd start with making contact 
> and take it from there.
> 
> Richard.
> 
> 
> On Wed, May 14, 2014 at 9:15 AM, Fedorov Vladimir  wrote:
> Hi everyone,
> 
> I want to maintain a plugin. 
> It has not been changed for a while but I find it useful
> https://wiki.jenkins-ci.org/display/JENKINS/Scripted+Cloud+plugin
> 
> What should I do to become a maintainer?
> 
> I've already forked the code and make some minor fixes:
> https://github.com/feoff3/scripted-cloud-plugin
> 
> Thanks in advance,
> Vladimir Fedorov
> 
> -- 
> 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/d/optout.
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/giY06oHGvf8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> -- 
> 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/d/optout.



signature.asc
Description: Message signed with OpenPGP using GPGMail