RE: How to hook pre-build?

[Sandell, Robert]

>From the doc of BuildStepCompatibilityLayer [1]

/**
 * @deprecated
 *  Use {@link #prebuild(AbstractBuild, BuildListener)} instead.
 */
public boolean prebuild(Build build, BuildListener listener) {


[1] 
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/tasks/BuildStepCompatibilityLayer.java




Robert Sandell
Sony Mobile Communications
Tel: +46 10 80 12721
sonymobile.com

From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On 
Behalf Of Christopher Ambler
Sent: den 24 april 2014 18:43
To: jenkinsci-dev@googlegroups.com
Subject: How to hook pre-build?

Greetings!

I am using the hue-light plugin. One thing it does is hook the prebuild() event 
to turn a light blue when a build kicks off. Not only does this appear to not 
work with Maven projects, but it also has a compilation error with the latest 
libraries. I'm told it's a deprecated interface, which would explain all of 
that.

What I can't seem to find is the appropriate way to get code executed when a 
project's build is kicked off.

I'd like to fix this bug.

Can anyone point me to the docs for this?

The plugin turns a light blue when a build starts, and then hooks the results 
to turn the light green/yellow/red based on the status of the build. The latter 
part works fine. It's the "hey, a build is starting, go blue" part that I need 
to rework.

Many thanks in advance!

Christopher
--
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 (TestFairy) Hosting and Repository Request

[Daniel Beck]

On 25.04.2014, at 06:06, Christopher Orr  wrote:

> Stupid question: if a plugin is relying on a fix or feature that was 
> backported to 1.509.3, what happens to users running 1.510 which, presumably, 
> does not have that fix/feature?

Not a stupid question. I don't think there's a way to make this work properly 
(e.g. define a version requirement of "must have 1.509.3 or 1.519").

>From my POV there are a few mitigating factors though:

- Only important (to LTS use) API is backported, so it should be a rare enough 
occurrence.
- It only affects the versions between an LTS release and a weekly before the 
next LTS -- 6 versions in the worst case (assuming the new 12 week LTS cycle).
- If you're not on LTS, chances are you're updating more frequently than once a 
quarter, making use of old non-LTS versions unlikely. There are fewer 
installations on 1.510-1.518 (missing RunAction2) than are using the latest 
weekly version within a week of its release.
- Updating your regular release after encountering an error after a plugin 
installation or update (likely on startup) will fix it.
- It'll take a while for your use of new API in a new plugin (in the case of 
the archetype) to reach users.

-- 
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: How to hook pre-build?

[Mads Nielsen]

Alternatively, you could check out the BuildWrapper extension point:
http://javadoc.jenkins-ci.org/hudson/tasks/BuildWrapper.html

and use the *setUp(AbstractBuild, Launcher, BuildListener)
 method.*


On Thu, Apr 24, 2014 at 6:42 PM, Christopher Ambler
wrote:

> Greetings!
>
> I am using the hue-light plugin. One thing it does is hook the prebuild()
> event to turn a light blue when a build kicks off. Not only does this
> appear to not work with Maven projects, but it also has a compilation error
> with the latest libraries. I'm told it's a deprecated interface, which
> would explain all of that.
>
> What I can't seem to find is the appropriate way to get code executed when
> a project's build is kicked off.
>
> I'd like to fix this bug.
>
> Can anyone point me to the docs for this?
>
> The plugin turns a light blue when a build starts, and then hooks the
> results to turn the light green/yellow/red based on the status of the
> build. The latter part works fine. It's the "hey, a build is starting, go
> blue" part that I need to rework.
>
> Many thanks in advance!
>
> Christopher
>
> --
> 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.
>



-- 




*Mads NielsenConsultantPraqma A/S*



*Tel: +45 50 98 18 09Mail: m...@praqma.net
web: www.praqma.net *

-- 
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.

New plugin request: send-to-eclipse

[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.

sharing the data between two plugins

[supraja]

I have developed two jenkins plugins. one is build plugin and other is post 
build plugin. Now my requirement is the output of build plugin should be 
passed as the input of post build plugin. I dint have any idea on how can i 
do this. Can any one help me how can i share data between the plugins.

Thanks in advance

-- 
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: sharing the data between two plugins

[Mads Nielsen]

We usually use actions to svare data. There is an InvisibleAction just for
that purpose.
Den 25/04/2014 12.12 skrev :

> I have developed two jenkins plugins. one is build plugin and other is
> post build plugin. Now my requirement is the output of build plugin should
> be passed as the input of post build plugin. I dint have any idea on how
> can i do this. Can any one help me how can i share data between the plugins.
>
> Thanks in advance
>
> --
> 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: sharing the data between two plugins

[supraja]

Hi, if it is possible can you please share some examples on InvisibleAction.

Thanks

On Friday, April 25, 2014 3:44:55 PM UTC+5:30, Mads Nielsen wrote:
>
> We usually use actions to svare data. There is an Invisible.Action just 
> for that purpose.
> Den 25/04/2014 12.12 skrev >:
>
>> I have developed two jenkins plugins. one is build plugin and other is 
>> post build plugin. Now my requirement is the output of build plugin should 
>> be passed as the input of post build plugin. I dint have any idea on how 
>> can i do this. Can any one help me how can i share data between the plugins.
>>
>> Thanks in advance
>>
>> -- 
>> 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: Contributing fixes to plugins (perforce)

[Niksan]

Nevermind, I decided to give Intellij CE a go, and I don't know what kind 
of voodoo magic it does, but it makes things a lot simpler. :)

-- 
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 Xtreme Feedback Utility

[Stefan Wolf]

 

Hi,

I build a small standalone application which polls the Jenkins RSS-Feed in 
order to control a few Feedback devices. Currently supported are the Dream 
Cheeky Missile Launcher, the Cleware USB Traffic Light and the Google 
text-to-speech API. For more Information see the read me on github: 
https://github.com/wolfs/jenkins-rss-retaliation

I would like to host the repository and the binaries within the jenkins 
infrastructure. Could you please fork the repository into the jenkinsci 
github organization? I would then release the binaries into the Jenkins 
repositories, if this would be OK.

Best regards,

Stefan Wolf

-- 
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: Request for review of pull request for Ivy Plugin, JENKINS-22447

[Kevin Formsma]

Bump, if no one is able to give this a look, is it possible to give me 
commit access to ivy-plugin? I've been running this patch for several weeks 
without issue :)

On Wednesday, April 23, 2014 2:09:23 PM UTC-4, Kevin Formsma wrote:
>
> Hello!
>
> I've submitted a pull request here 
> https://github.com/jenkinsci/ivy-plugin/pull/14 which should fix 
> JENKINS-22447 . It 
> looks like the maintainers of the Ivy plugin are not super active.
>
> Can someone give this a quick review?
>

-- 
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: Request for review of pull request for Ivy Plugin, JENKINS-22447

[Ulli Hafner]

What is your user name?

Am 25.04.2014 um 17:06 schrieb Kevin Formsma :

> Bump, if no one is able to give this a look, is it possible to give me commit 
> access to ivy-plugin? I've been running this patch for several weeks without 
> issue :)
> 
> On Wednesday, April 23, 2014 2:09:23 PM UTC-4, Kevin Formsma wrote:
> Hello!
> 
> I've submitted a pull request here 
> https://github.com/jenkinsci/ivy-plugin/pull/14 which should fix 
> JENKINS-22447. It looks like the maintainers of the Ivy plugin are not super 
> active.
> 
> Can someone give this a quick review?
> 
> -- 
> 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

Re: sharing the data between two plugins

[Ulli Hafner]

plugin1: build.addAction(new YourInvisibleAction())
plugin2: build.getAction(YourInvisibleAction.class)

Am 25.04.2014 um 12:30 schrieb supr...@horoppa.com:

> Hi, if it is possible can you please share some examples on InvisibleAction.
> 
> Thanks
> 
> On Friday, April 25, 2014 3:44:55 PM UTC+5:30, Mads Nielsen wrote:
> We usually use actions to svare data. There is an Invisible.Action just for 
> that purpose.
> 
> Den 25/04/2014 12.12 skrev :
> I have developed two jenkins plugins. one is build plugin and other is post 
> build plugin. Now my requirement is the output of build plugin should be 
> passed as the input of post build plugin. I dint have any idea on how can i 
> do this. Can any one help me how can i share data between the plugins.
> 
> Thanks in advance
> 
> -- 
> 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.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Request for review of pull request for Ivy Plugin, JENKINS-22447

[Kevin Formsma]

Github username is arothian.

Thanks!


On Friday, April 25, 2014 11:29:46 AM UTC-4, Ullrich Hafner wrote:
>
> What is your user name?
>
> Am 25.04.2014 um 17:06 schrieb Kevin Formsma 
> >:
>
> Bump, if no one is able to give this a look, is it possible to give me 
> commit access to ivy-plugin? I've been running this patch for several weeks 
> without issue :)
>
> On Wednesday, April 23, 2014 2:09:23 PM UTC-4, Kevin Formsma wrote:
>>
>> Hello!
>>
>> I've submitted a pull request here 
>> https://github.com/jenkinsci/ivy-plugin/pull/14 which should fix 
>> JENKINS-22447 . It 
>> looks like the maintainers of the Ivy plugin are not super active.
>>
>> Can someone give this a quick review?
>>
>
> -- 
> 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.

Publish DigitalOcean slave plugin

[Robert Gründler]

Hi all.

i’d like to publish my digitalocean slave plugin:

https://github.com/pulse00/digitalocean-plugin 

That’s my first jenkins plugin - if you need anything else please let me know.



regards


-robert



-- 
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: Advice on debugging deadlocks Queue.getItems()

[Surya Gaddipati]

Thank you for the suggestions , I was able to take threaddumps this time 

Here are the threads in question 

http://pastebin.com/K6n9YXKV 

Can someone clue me in as to what is going on.

On Thursday, April 24, 2014 7:05:32 AM UTC-5, evernat wrote:
>
> Hi,
>
> I confirm that when the "/monitoring" page says that some threads are 
> deadlocked, the deadlock is really true. And it is the JVM which gives the 
> deadlocked threads with this method: 
> http://docs.oracle.com/javase/7/docs/api/java/lang/management/ThreadMXBean.html#findDeadlockedThreads%28%29
>
> To find the cause and which code is doing something wrong, the 
> stack-traces of those threads is a first step.
> (The "/monitoring" page does not include locks in the stack-traces, but 
> you can get stack-traces with locks in the "/threadDump" page or with the 
> jstack tool.)
>
> bye,
> Emeric
>
>
> Le mercredi 23 avril 2014 21:47:39 UTC+2, Jesse Glick a écrit :
>>
>> On Wed, Apr 23, 2014 at 2:11 PM, Surya Gaddipati 
>>  wrote: 
>> > There are tons of threads queued up trying to get into the synchronized 
>> > method Queue.getItems() 
>> > 
>> > appreciate any advice on how to go about debugging this. 
>>
>> You would have to determine which thread holds the lock on Queue, and 
>> why it is not releasing it. If there is a true deadlock, it would be 
>> because that thread is waiting for another lock which is held by one 
>> of the threads waiting for Queue. At least one of those two threads 
>> involves some (core or plugin) code which is doing something wrong. 
>>
>

-- 
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: Advice on debugging deadlocks Queue.getItems()

[Jesse Glick]

On Fri, Apr 25, 2014 at 12:47 PM, Surya Gaddipati
 wrote:
> Can someone clue me in as to what is going on.

You would have to determine which threads hold which locks. Normally
jstack includes this information but your thread dump does not. Can be
reconstructed by examining source code for every line in the stack
traces, just tedious.

-- 
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: Liquibase Runner

[Keith Collison]

The repository was indeed created (I gather that this was done perhaps by a 
bot).

However, the repository name seems a little funky, having two dashes at the 
end of it ("liquibase-runner-plugin--").

While I'm sure this is merely cosmetic, if there's a way to lop off those 
two dashes, I'd be pleased.

In addition (and no doubt more importantly), I don't seem to be able to 
push to this repository.  Running "git push" yields:

Push failed: fatal: unable to access 
'https://github.com/jenkinsci/liquibase-runner-plugin--.git/': The 
requested URL returned error: 403

Let me know if I'm doing something bone-headed.

Thank you.

~ Keith


On Thursday, April 24, 2014 1:46:26 PM UTC-7, Dominik Bartholdi wrote:
>
> At least the repo exists - don't know if someone else created it...
>
> Am 24.04.2014 um 21:01 schrieb Ulli Hafner 
> >:
>
> Ah, did it actually work? The bot didn’t actually send a response…
>
> Am 24.04.2014 um 20:49 schrieb Dominik Bartholdi 
> 
> >:
>
> This seems already to be forked…
> Domi
>
> On 24.04.2014, at 00:10, Keith Collison > 
> wrote:
>
> Greetings esteemed Jenkinists:
>
> I have created a Jenkins Plugin and, per instructions on the wiki, I am 
> notifying this mailing list as to its existence.  
>
> Details:
>
> *Jenkins Plugin Name:* liquibase-runner
> *Current Location:* 
> https://github.com/prospero238/liquibase-runner
> *Github User:* prospero238
> *Jenkins-ci org account:* prospero238 (yes, same name as my github user).
>
> My understanding is that my current repo will be forked.  Further, I can 
> looked forward to its inclusion in the Cloudbees CI environment.  I'll be 
> happy to create a wiki page once this is done (or, if it standard to this 
> beforehand, happy to do that as well).
>
> As this is my first plugin, I welcome comments and suggestions about the 
> code, as well as my conduct.
>
> Let me know what is required of me to move forward.
>
> Kind Regards,
>
> Keith
>
>
> -- 
> 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-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: Request for review of pull request for Ivy Plugin, JENKINS-22447

[Ulli Hafner]

Done. Welcome aboard!

Ulli

Am 25.04.2014 um 17:56 schrieb Kevin Formsma :

> Github username is arothian.
> 
> Thanks!
> 
> 
> On Friday, April 25, 2014 11:29:46 AM UTC-4, Ullrich Hafner wrote:
> What is your user name?
> 
> Am 25.04.2014 um 17:06 schrieb Kevin Formsma :
> 
>> Bump, if no one is able to give this a look, is it possible to give me 
>> commit access to ivy-plugin? I've been running this patch for several weeks 
>> without issue :)
>> 
>> On Wednesday, April 23, 2014 2:09:23 PM UTC-4, Kevin Formsma wrote:
>> Hello!
>> 
>> I've submitted a pull request here 
>> https://github.com/jenkinsci/ivy-plugin/pull/14 which should fix 
>> JENKINS-22447. It looks like the maintainers of the Ivy plugin are not super 
>> active.
>> 
>> Can someone give this a quick review?
>> 
>> -- 
>> 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.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Publish DigitalOcean slave plugin

[Ulli Hafner]

https://github.com/jenkinsci/digitalocean-plugin

Welcome aboard!

Ulli

Am 25.04.2014 um 18:36 schrieb Robert Gründler :

> Hi all.
> 
> i’d like to publish my digitalocean slave plugin:
> 
> https://github.com/pulse00/digitalocean-plugin 
> 
> That’s my first jenkins plugin - if you need anything else please let me know.
> 
> 
> 
> regards
> 
> 
> -robert
> 
> 
> 
> 
> -- 
> 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

Re: New Plugin: Liquibase Runner

[Ulli Hafner]

Done: https://github.com/jenkinsci/liquibase-runner-plugin/

Am 25.04.2014 um 20:21 schrieb Keith Collison :

> The repository was indeed created (I gather that this was done perhaps by a 
> bot).
> 
> However, the repository name seems a little funky, having two dashes at the 
> end of it ("liquibase-runner-plugin--").
> 
> While I'm sure this is merely cosmetic, if there's a way to lop off those two 
> dashes, I'd be pleased.
> 
> In addition (and no doubt more importantly), I don't seem to be able to push 
> to this repository.  Running "git push" yields:
> 
> Push failed: fatal: unable to access 
> 'https://github.com/jenkinsci/liquibase-runner-plugin--.git/': The requested 
> URL returned error: 403
> 
> Let me know if I'm doing something bone-headed.
> 
> Thank you.
> 
> ~ Keith
> 
> 
> On Thursday, April 24, 2014 1:46:26 PM UTC-7, Dominik Bartholdi wrote:
> At least the repo exists - don't know if someone else created it...
> 
> Am 24.04.2014 um 21:01 schrieb Ulli Hafner :
> 
>> Ah, did it actually work? The bot didn’t actually send a response…
>> 
>> Am 24.04.2014 um 20:49 schrieb Dominik Bartholdi :
>> 
>>> This seems already to be forked…
>>> Domi
>>> 
>>> On 24.04.2014, at 00:10, Keith Collison  wrote:
>>> 
 Greetings esteemed Jenkinists:
 
 I have created a Jenkins Plugin and, per instructions on the wiki, I am 
 notifying this mailing list as to its existence.  
 
 Details:
 
 Jenkins Plugin Name: liquibase-runner
 Current Location: https://github.com/prospero238/liquibase-runner
 Github User: prospero238
 Jenkins-ci org account: prospero238 (yes, same name as my github user).
 
 My understanding is that my current repo will be forked.  Further, I can 
 looked forward to its inclusion in the Cloudbees CI environment.  I'll be 
 happy to create a wiki page once this is done (or, if it standard to this 
 beforehand, happy to do that as well).
 
 As this is my first plugin, I welcome comments and suggestions about the 
 code, as well as my conduct.
 
 Let me know what is required of me to move forward.
 
 Kind Regards,
 
 Keith
 
 
 -- 
 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-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.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Request for review of pull request for Ivy Plugin, JENKINS-22447

[Kevin Formsma]

Thanks Ulli, but it looks like you added me to the wrong team :) I'll need 
access to https://github.com/jenkinsci/ivy-plugin, 
not https://github.com/jenkinsci/redmine-plugin.

On Friday, April 25, 2014 2:32:45 PM UTC-4, Ullrich Hafner wrote:
>
> Done. Welcome aboard!
>
> Ulli
>
> Am 25.04.2014 um 17:56 schrieb Kevin Formsma 
> >:
>
> Github username is arothian.
>
> Thanks!
>
>
> On Friday, April 25, 2014 11:29:46 AM UTC-4, Ullrich Hafner wrote:
>>
>> What is your user name?
>>
>> Am 25.04.2014 um 17:06 schrieb Kevin Formsma :
>>
>> Bump, if no one is able to give this a look, is it possible to give me 
>> commit access to ivy-plugin? I've been running this patch for several weeks 
>> without issue :)
>>
>> On Wednesday, April 23, 2014 2:09:23 PM UTC-4, Kevin Formsma wrote:
>>>
>>> Hello!
>>>
>>> I've submitted a pull request here 
>>> https://github.com/jenkinsci/ivy-plugin/pull/14 which should fix 
>>> JENKINS-22447 . It 
>>> looks like the maintainers of the Ivy plugin are not super active.
>>>
>>> Can someone give this a quick review?
>>>
>>
>> -- 
>> 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-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: Request for review of pull request for Ivy Plugin, JENKINS-22447

[Ulli Hafner]

Sorry… Now you should have access.

Am 25.04.2014 um 20:58 schrieb Kevin Formsma :

> Thanks Ulli, but it looks like you added me to the wrong team :) I'll need 
> access to https://github.com/jenkinsci/ivy-plugin, not 
> https://github.com/jenkinsci/redmine-plugin.
> 
> On Friday, April 25, 2014 2:32:45 PM UTC-4, Ullrich Hafner wrote:
> Done. Welcome aboard!
> 
> Ulli
> 
> Am 25.04.2014 um 17:56 schrieb Kevin Formsma :
> 
>> Github username is arothian.
>> 
>> Thanks!
>> 
>> 
>> On Friday, April 25, 2014 11:29:46 AM UTC-4, Ullrich Hafner wrote:
>> What is your user name?
>> 
>> Am 25.04.2014 um 17:06 schrieb Kevin Formsma :
>> 
>>> Bump, if no one is able to give this a look, is it possible to give me 
>>> commit access to ivy-plugin? I've been running this patch for several weeks 
>>> without issue :)
>>> 
>>> On Wednesday, April 23, 2014 2:09:23 PM UTC-4, Kevin Formsma wrote:
>>> Hello!
>>> 
>>> I've submitted a pull request here 
>>> https://github.com/jenkinsci/ivy-plugin/pull/14 which should fix 
>>> JENKINS-22447. It looks like the maintainers of the Ivy plugin are not 
>>> super active.
>>> 
>>> Can someone give this a quick review?
>>> 
>>> -- 
>>> 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-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.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: New Plugin: Liquibase Runner

[Keith Collison]

Perhaps I'm missing something, but I don't seem to be able to commit to 
this repository:

remote: Permission to jenkinsci/liquibase-runner-plugin.git denied to 
prospero238.
fatal: unable to access 
'https://github.com/jenkinsci/liquibase-runner-plugin.git/': The requested 
URL returned error: 403

Please advise.  Thank you in advance!

~ Keith




On Friday, April 25, 2014 11:40:20 AM UTC-7, Ullrich Hafner wrote:
>
> Done: https://github.com/jenkinsci/liquibase-runner-plugin/
>
> Am 25.04.2014 um 20:21 schrieb Keith Collison 
> >:
>
> The repository was indeed created (I gather that this was done perhaps by 
> a bot).
>
> However, the repository name seems a little funky, having two dashes at 
> the end of it ("liquibase-runner-plugin--").
>
> While I'm sure this is merely cosmetic, if there's a way to lop off those 
> two dashes, I'd be pleased.
>
> In addition (and no doubt more importantly), I don't seem to be able to 
> push to this repository.  Running "git push" yields:
>
> Push failed: fatal: unable to access '
> https://github.com/jenkinsci/liquibase-runner-plugin--.git/': The 
> requested URL returned error: 403
>
> Let me know if I'm doing something bone-headed.
>
> Thank you.
>
> ~ Keith
>
>
> On Thursday, April 24, 2014 1:46:26 PM UTC-7, Dominik Bartholdi wrote:
>>
>> At least the repo exists - don't know if someone else created it...
>>
>> Am 24.04.2014 um 21:01 schrieb Ulli Hafner :
>>
>> Ah, did it actually work? The bot didn’t actually send a response…
>>
>> Am 24.04.2014 um 20:49 schrieb Dominik Bartholdi :
>>
>> This seems already to be forked…
>> Domi
>>
>> On 24.04.2014, at 00:10, Keith Collison  wrote:
>>
>> Greetings esteemed Jenkinists:
>>
>> I have created a Jenkins Plugin and, per instructions on the wiki, I am 
>> notifying this mailing list as to its existence.  
>>
>> Details:
>>
>> *Jenkins Plugin Name:* liquibase-runner
>> *Current Location:* 
>> https://github.com/prospero238/liquibase-runner
>> *Github User:* prospero238
>> *Jenkins-ci org account:* prospero238 (yes, same name as my github user).
>>
>> My understanding is that my current repo will be forked.  Further, I can 
>> looked forward to its inclusion in the Cloudbees CI environment.  I'll be 
>> happy to create a wiki page once this is done (or, if it standard to this 
>> beforehand, happy to do that as well).
>>
>> As this is my first plugin, I welcome comments and suggestions about the 
>> code, as well as my conduct.
>>
>> Let me know what is required of me to move forward.
>>
>> Kind Regards,
>>
>> Keith
>>
>>
>> -- 
>> 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-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-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.

Check if plugin is running on master node

[Steve Springett]

Is there a way to reliably check if a plugin is running on the master node?

Currently I'm doing this:
boolean isMaster = abstractBuild.getBuiltOn().getNodeName().equals("");

But this seems like a bit of a hack to me. Is there a better way?

-- 
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.