Parameterise slaves launched in a cloud [workflow ?]

I'm thinking out loud here, but I wonder if it would be nice to be able to support the following scenarios in Jenkins (and docker plugin users have been asking for similar features). I use docker to launch slaves on a variety of boxes. This works very nicely. You can tell docker to attach a 'data

Re: New plugin: Git Tag Message

I think most people are keen to curb the proliferation of advanced settings in the Git plugin which are only used by a minority of people. Also, as far as I can remember, it was Kohsuke who pointed me towards GitSCMExtension at JUC Berlin and suggested that this doesn't need to be in the main

Re: Write access to jenkinsci/hockeyapp-plugin

Oleg, yes, I wrote email to Oliver Hoeltke (*ohoeltke ). * He did not answer. The author of *https://github.com/jenkinsci/hockeyapp-plugin/pull/20* MichaelRocks is my colleague. He is still waiting when ohoeltke pull in this pull request. The last message from oh

Re: PollSCM plugin

Can we merge this into core? I think Poll button has the same weight as Build button and this should be part of core. On Wednesday, March 27, 2013 6:32:50 PM UTC+3, Robert Sandell wrote: > > Done > > > > /B > > > > *From:* jenkin...@googlegroups.com [mailto: > jenkin...@googlegroups.com ] *

Re: Write access to jenkinsci/hockeyapp-plugin

Denis, I've added you to committers. Please don't forget to review (and probably merge) other changes. See release guidelines here: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins Best regards, Oleg Nenashev 2014-10-22 13:14 GMT+04:00 Denis Kochetkov : > Oleg, > yes, I wrote email

new plugin - groovy matrix execution strategy

Hi I put together a matrix execution strategy which allows greater control than the default strategy. It will run either a groovy script, as entered or a script from an absolute path or from the workspace. This is probably best suited to dynamically built axis. There are a couple of problems

Re: Write access to jenkinsci/hockeyapp-plugin

Oleg, Thank you! Best regards, Denis Kochetkov. On Wednesday, October 22, 2014 1:59:04 PM UTC+4, Oleg Nenashev wrote: > > Denis, > > I've added you to committers. > Please don't forget to review (and probably merge) other changes. > > See release guidelines here: > https://wiki.jenkins-ci.org

Re: New plugin: Git Tag Message

I prefer Christopher's technique of placing it in a separate plugin. The git plugin supports many complicated workflows and doesn't have tests to verify all those complicated workflows are still functioning. Using a separate plugin avoids modifying the git plugin and allows users to selectively c

RE: Just pushed a release, now what?

It looks like our plugin is still not showing up in the list of available plugins. And our wiki page is not pulling the dynamic content (stats, etc…). We would appreciate any help. Thank you. Anthony From: Anthony DeMartini Sent: Monday, October 13, 2014 11:12 AM To: 'Kanstantsin Shautsou';

Re: Just pushed a release, now what?

It's only a snapshot in the repository. Use maven-release-plugin 2.5 as described here: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues On 22.10.2014, at 17:29, Anthony DeMartini wrote: > It looks like our plugin is still not showing up in th

Re: new plugin - groovy matrix execution strategy

I think the plugin can be forked, but it's better to agree on the plugin name before forking. - What about using http://groovy-sandbox.kohsuke.org/ to run Groovy scripts? Just to avoid new security holes... - > "I think the name could be better " - Definitely. Actually, you don't

Re: jna-posix updating to JNA 4.1

On Tue, Oct 21, 2014 at 8:50 PM, Craig Rodrigues wrote: > How should I fork it? Similar to how this library was forked for Jenkins? > > https://github.com/jenkinsci/jna/commit/d127057b76ba221ac983d50d4f588bff2bd7abf7 Yes, something like that. -- You received this message because you are subscr

Re: Parameterise slaves launched in a cloud [workflow ?]

On Wed, Oct 22, 2014 at 4:55 AM, Nigel Magnay wrote: > it may be useful to be able to say "only launch downstream slaves > on the same physical node as the upstream job". This at least is possible, if your Cloud honors a request for a label which was actually a previously used Slave.name. There i

Re: jna-posix updating to JNA 4.1

On Wed, Oct 22, 2014 at 12:01 PM, Jesse Glick wrote: > On Tue, Oct 21, 2014 at 8:50 PM, Craig Rodrigues > wrote: > > How should I fork it? Similar to how this library was forked for > Jenkins? > > > > > https://github.com/jenkinsci/jna/commit/d127057b76ba221ac983d50d4f588bff2bd7abf7 > > Yes, so

RE: Just pushed a release, now what?

Thanks so much Daniel. Using 2.5 seems to have worked better. I now see my files here: http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/codedx/1.1/ I guess now there is a manual process involved? -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@g

Re: Just pushed a release, now what?

Just a periodic one: https://ci.jenkins-ci.org/job/infra_update_center/ This should detect the release, and publish to http://updates.jenkins-ci.org/update-center.json Then all instances using the regular update center (not LTS or experimental, they have their own Jenkins jobs) should pick it u

Re: Just pushed a release, now what?

Hi Daniel, do we have FAQ with answer for this question somewhere on wiki? On Wednesday, October 22, 2014 11:56:36 PM UTC+3, Daniel Beck wrote: > > Just a periodic one: > https://ci.jenkins-ci.org/job/infra_update_center/ > > This should detect the release, and publish to > http://updates.jenki

Re: Just pushed a release, now what?

https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins does say "The released plugin will show up in the update center in half a day or so." - that *kind of* answers it. Richard. On Thu, Oct 23, 2014 at 10:00 AM, Kanstantsin Shautsou < kanstantsin@gmail.com> wrote: > Hi Daniel, do we ha

Re: Just pushed a release, now what?

https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Help%5C%21Mypluginisnotshowingupintheupdatecenter. :) On Thursday, October 23, 2014 12:03:14 AM UTC+3, Richard Bywater wrote: > > https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins does say "The > released plugi

Re: jna-posix updating to JNA 4.1

Hi, How do I release jenkinsci/jna-posix to jenkins-ci.org? I did the following: git clone https://github.com/jenkinsci/jna-posix cd jna-posix mvn clean install mvn -e release:prepare release:perform But then I got this error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-relea

Re: jna-posix updating to JNA 4.1

On Wed, Oct 22, 2014 at 6:31 PM, Craig Rodrigues wrote: > I am following the pattern of the jenkinsci/jna plugin which never had > SNAPSHOT appended to its version name. Ah, well do not follow that pattern. :-) That is for experts and/or fools. I would start with 1.0.3-jenkins-1-SNAPSHOT commit

Re: jna-posix updating to JNA 4.1

On Wed, Oct 22, 2014 at 4:36 PM, Jesse Glick wrote: > > 1.0.3-jenkins-1-SNAPSHOT > > commit and then run the release, which ought to work the way you expect. > OK, I did that. I got further along. [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (de

Re: jna-posix updating to JNA 4.1

Huh, should not be trying to deploy a SNAPSHOT version. Make sure you are running at least version 2.5 of maven-release-plugin: mvn -B org.apache.maven.plugins:maven-release-plugin:2.5:prepare org.apache.maven.plugins:maven-release-plugin:2.5:perform Also your ~/.m2/settings.xml is going to need

Re: Just pushed a release, now what?

Errr yeah - good spotting/updating :) Richard. On Thu, Oct 23, 2014 at 10:10 AM, Kanstantsin Shautsou < kanstantsin@gmail.com> wrote: > > https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Help%5C%21Mypluginisnotshowingupintheupdatecenter. > :) > > On Thursday, Octobe

Re: jna-posix updating to JNA 4.1

You need to provide your jenkins credentials in settings.xml as described here: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org /B On Wed, Oct 22, 2014 at 5:49 PM, Craig Rodrigues wrote: > On Wed, Oct 22, 2014 at 4:36 PM, Jesse Glick wrote: >

Re: ElOyente-plugin needs a new maintainer

Hi Ulli, Sorry for my late reply but i haven't been in the office for the last 2 days. Regarding my github names are 'dnnsjcbs' and 'dejakke'. The first one is the one i use for company works, while the latter is used at home. I would apprreciate it, if you could give them both write acces. So

Re: ElOyente-plugin needs a new maintainer

Oleg, That's exactly my problem! I can create a pull request, but the person who is owner of the master repo has passed away. So i don't see him performing any pull requests in the future. Regards, Dennis Jacobs. On Wednesday, October 22, 2014 6:35:06 AM UTC+2, Oleg Nenashev wrote: > > Dennis,