Re: Hosting request for LeastLoad Plugin

[Brendan Nolan]

Hi,

Just once again wondering if I am missing some information to get my plugin 
hosted.

https://github.com/bstick12/jenkins-ci-leastload

GitHub and Jenkins ids are 'bstick12'

Thanks,

Brendan

On Tuesday, May 28, 2013 1:49:30 PM UTC+1, Brendan Nolan wrote:
>
> Hi,
>
> I've started a new plugin that replaces the default Load Balancer with one 
> that prefers nodes that currently have the least load
>
> https://github.com/bstick12/jenkins-ci-leastload
>
> My GitHub username is "bstick12"
>
> Thanks
>
> Brendan
>
>

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

Re:Job Configuration form data before apply or save

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

The data, at that point, exists only in memory in the user's browser. Any 
validation prior to form submission would need to be done by JavaScript 
(presumably) running in the web page, although it could make separate calls 
back to code on the server if it wished to.

- Original Message -
From: jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com
At: Jun  3 2013 16:05:00

Hi All,

I was thinking of a plugin that would review some a job config before
submission.  We see a lot of the same configuration errors and I was
thinking we could be proactive about developers getting the jobs configured
correctly.  So, I was wondering if someone could point me in the direction
of a way to access the information (form data maybe) that is typed into the
job configuration before the save or apply button is pushed.   The idea
being we can make sure the config is correct.  Just looking for a nudge in
the right direction as I don't even know if this is a good idea yet :)

Thanks,
Bernie 


--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Job-Configuration-form-data-before-apply-or-save-tp4668295.html
Sent from the Jenkins dev mailing list archive at Nabble.com.

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


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

Job Configuration form data before apply or save

[bbonn]

Hi All,

I was thinking of a plugin that would review some a job config before
submission.  We see a lot of the same configuration errors and I was
thinking we could be proactive about developers getting the jobs configured
correctly.  So, I was wondering if someone could point me in the direction
of a way to access the information (form data maybe) that is typed into the
job configuration before the save or apply button is pushed.   The idea
being we can make sure the config is correct.  Just looking for a nudge in
the right direction as I don't even know if this is a good idea yet :)

Thanks,
Bernie 



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Job-Configuration-form-data-before-apply-or-save-tp4668295.html
Sent from the Jenkins dev mailing list archive at Nabble.com.

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

jenkins builds and stapler versions

[Paul Mendelson]

I am building a small jenkins plugin that is based off of stable release 
1.480.3.

I was a bit surprised by the number of different versions of stapler that 
was downloaded by maven to do the build.  Does (should) a stable jenkins 
release standardize some dependency versions?  

My maven output had the following downloads

 /public/org/kohsuke/stapler/stapler/1.100/stapler-1.100.jar   
/public/org/kohsuke/stapler/stapler/1.100/stapler-1.100.pom   
/public/org/kohsuke/stapler/stapler/1.140/stapler-1.140.pom   
/public/org/kohsuke/stapler/stapler/1.141/stapler-1.141.pom   
/public/org/kohsuke/stapler/stapler/1.142/stapler-1.142.pom   
/public/org/kohsuke/stapler/stapler/1.143/stapler-1.143.pom   
/public/org/kohsuke/stapler/stapler/1.144/stapler-1.144.pom   
/public/org/kohsuke/stapler/stapler/1.145/stapler-1.145.pom   
/public/org/kohsuke/stapler/stapler/1.146/stapler-1.146.pom   
/public/org/kohsuke/stapler/stapler/1.147/stapler-1.147.pom   
/public/org/kohsuke/stapler/stapler/1.148/stapler-1.148.pom   
/public/org/kohsuke/stapler/stapler/1.149/stapler-1.149.pom   
/public/org/kohsuke/stapler/stapler/1.150/stapler-1.150.pom   
/public/org/kohsuke/stapler/stapler/1.151/stapler-1.151.pom   
/public/org/kohsuke/stapler/stapler/1.152/stapler-1.152.pom   
/public/org/kohsuke/stapler/stapler/1.153/stapler-1.153.pom   
/public/org/kohsuke/stapler/stapler/1.154/stapler-1.154.pom   
/public/org/kohsuke/stapler/stapler/1.155/stapler-1.155.pom   
/public/org/kohsuke/stapler/stapler/1.156/stapler-1.156.pom   
/public/org/kohsuke/stapler/stapler/1.157/stapler-1.157.pom   
/public/org/kohsuke/stapler/stapler/1.158/stapler-1.158.pom   
/public/org/kohsuke/stapler/stapler/1.159/stapler-1.159.pom   
/public/org/kohsuke/stapler/stapler/1.160/stapler-1.160.pom   
/public/org/kohsuke/stapler/stapler/1.161/stapler-1.161.pom   
/public/org/kohsuke/stapler/stapler/1.162/stapler-1.162.pom   
/public/org/kohsuke/stapler/stapler/1.163/stapler-1.163.pom   
/public/org/kohsuke/stapler/stapler/1.164/stapler-1.164.pom   
/public/org/kohsuke/stapler/stapler/1.165/stapler-1.165.pom   
/public/org/kohsuke/stapler/stapler/1.166/stapler-1.166.pom   
/public/org/kohsuke/stapler/stapler/1.167/stapler-1.167.pom   
/public/org/kohsuke/stapler/stapler/1.168/stapler-1.168.pom   
/public/org/kohsuke/stapler/stapler/1.169/stapler-1.169.pom   
/public/org/kohsuke/stapler/stapler/1.170/stapler-1.170.pom   
/public/org/kohsuke/stapler/stapler/1.171/stapler-1.171.pom   
/public/org/kohsuke/stapler/stapler/1.172/stapler-1.172.pom   
/public/org/kohsuke/stapler/stapler/1.173/stapler-1.173.pom   
/public/org/kohsuke/stapler/stapler/1.174/stapler-1.174.pom   
/public/org/kohsuke/stapler/stapler/1.175/stapler-1.175.pom   
/public/org/kohsuke/stapler/stapler/1.176/stapler-1.176.pom   
/public/org/kohsuke/stapler/stapler/1.177/stapler-1.177.pom   
/public/org/kohsuke/stapler/stapler/1.178/stapler-1.178.pom   
/public/org/kohsuke/stapler/stapler/1.179/stapler-1.179.pom   
/public/org/kohsuke/stapler/stapler/1.180/stapler-1.180.pom   
/public/org/kohsuke/stapler/stapler/1.181/stapler-1.181.pom   
/public/org/kohsuke/stapler/stapler/1.182/stapler-1.182.pom   
/public/org/kohsuke/stapler/stapler/1.183/stapler-1.183.pom   
/public/org/kohsuke/stapler/stapler/1.185/stapler-1.185.pom   
/public/org/kohsuke/stapler/stapler/1.186/stapler-1.186.pom   
/public/org/kohsuke/stapler/stapler/1.187/stapler-1.187.pom   
/public/org/kohsuke/stapler/stapler/1.188/stapler-1.188.pom   
/public/org/kohsuke/stapler/stapler/1.189/stapler-1.189.pom   
/public/org/kohsuke/stapler/stapler/1.190/stapler-1.190.pom   
/public/org/kohsuke/stapler/stapler/1.191/stapler-1.191.pom   
/public/org/kohsuke/stapler/stapler/1.192/stapler-1.192.pom   
/public/org/kohsuke/stapler/stapler/1.195/stapler-1.195.pom   
/public/org/kohsuke/stapler/stapler/1.196/stapler-1.196.pom   
/public/org/kohsuke/stapler/stapler/1.197/stapler-1.197.pom   
/public/org/kohsuke/stapler/stapler/1.198/stapler-1.198.jar   
/public/org/kohsuke/stapler/stapler/1.198/stapler-1.198.pom   
/public/org/kohsuke/stapler/stapler/1.199/stapler-1.199.pom   
/public/org/kohsuke/stapler/stapler/1.200/stapler-1.200.pom   
/public/org/kohsuke/stapler/stapler/1.201/stapler-1.201.pom   
/public/org/kohsuke/stapler/stapler/1.202/stapler-1.202.pom   
/public/org/kohsuke/stapler/stapler/1.203/stapler-1.203.pom   
/public/org/kohsuke/stapler/stapler/1.204/stapler-1.204.pom   
/public/org/kohsuke/stapler/stapler/1.205/stapler-1.205.pom   
/public/org/kohsuke/stapler/stapler/1.206/stapler-1.206.pom   
/public/org/kohsuke/stapler/stapler/1.207/stapler-1.207.pom   
/public/org/kohsuke/stapler/stapler/1.209/stapler-1.209.pom  

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

Re: plugin maven groupId

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

Ahh... makes sense.

- Original Message -
From: jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com
At: Jun  3 2013 13:41:17

On 06/03/2013 01:27 PM, Kevin Fleming (BLOOMBERG/ 731 LEXIN) wrote:
> Any configuration data persisted under the old class names would need to be 
> converted, though, right?

I was not suggesting changing package/class names.

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


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

Re: plugin maven groupId

[Jesse Glick]

On 06/03/2013 01:27 PM, Kevin Fleming (BLOOMBERG/ 731 LEXIN) wrote:

Any configuration data persisted under the old class names would need to be 
converted, though, right?


I was not suggesting changing package/class names.

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

Re: plugin maven groupId

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

Any configuration data persisted under the old class names would need to be 
converted, though, right? The EC2 plugin has an example of migrating data from 
an old class name to a new one (EC2Cloud -> AmazonEC2Cloud), if that is useful.

- Original Message -
From: jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com
At: Jun  3 2013 12:45:17

On 06/03/2013 12:24 PM, James Nord (jnord) wrote:
> The plugin is still using the old org.jvnet.hudson.plugins Maven groupId – so 
> I was considering changing this at the same time.
>
> However I wasn’t sure if this is required to stay the same for plugin updates 
> (or any other reason).

Plugin updates only consider the artifactId, so if you are dropping Hudson 
compatibility then you can and should switch to org.jenkins-ci.plugins for the 
groupId (which 
will be the default when you use the Jenkins plugin parent POM).

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


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

Re: jenkins debugging with eclipse (Windows)

[Jesse Glick]

On 06/03/2013 12:51 PM, Zhengyuan Shen wrote:

I click on the manage plugins and I can't find my plugin there


Under /pluginManager/installed?

Maybe the problem is Eclipse. Try just ‘mvn hpi:run’ from a shell.

Or from NetBeans, if you install the Jenkins development support plugin, you can use File » New Project to create a new plugin, and Debug » Debug Project to debug it 
(using hpi:run with the right debugger parameters predefined).


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

Re: jenkins debugging with eclipse (Windows)

[Zhengyuan Shen]

Hi,

I have checked the POM.xml file and it says the version is 1.95 and I have 
also checked the console it says all plugins are listed and prepared and 
started and the Jenkins is fully up and running then I go to 
localhost:8080, and I click on the manage plugins and I can't find my 
plugin there so it is not uploaded at all. My plugin is just a hello world 
plugin it change "Hello" to French. It works when I simply import the hpi 
file manually from the Jenkins UI and I just found no way to debug it. What 
do you think?

Thanks,


On Monday, June 3, 2013 9:43:09 AM UTC-7, Jesse Glick wrote:
>
> On 06/03/2013 11:59 AM, Zhengyuan Shen wrote: 
> > when I go to http://localhost:8080/ I can see the Jenkins instance but 
> I can not find my plugin that I need to debug 
>
> Then check the console to see if the plugin failed to start for some 
> reason. One possible reason is that the version of the maven-hpi-plugin 
> specified in your parent POM 
> is too old (buggy). You need at least 1.95. 
>

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

Re: plugin maven groupId

[Jesse Glick]

On 06/03/2013 12:24 PM, James Nord (jnord) wrote:

The plugin is still using the old org.jvnet.hudson.plugins Maven groupId – so I 
was considering changing this at the same time.

However I wasn’t sure if this is required to stay the same for plugin updates 
(or any other reason).


Plugin updates only consider the artifactId, so if you are dropping Hudson compatibility then you can and should switch to org.jenkins-ci.plugins for the groupId (which 
will be the default when you use the Jenkins plugin parent POM).


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

Re: jenkins debugging with eclipse (Windows)

[Jesse Glick]

On 06/03/2013 11:59 AM, Zhengyuan Shen wrote:

when I go to http://localhost:8080/ I can see the Jenkins instance but I can 
not find my plugin that I need to debug


Then check the console to see if the plugin failed to start for some reason. One possible reason is that the version of the maven-hpi-plugin specified in your parent POM 
is too old (buggy). You need at least 1.95.


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

plugin maven groupId

[James Nord (jnord)]

Hi all,

I am biting the bullet and dropping support for Hudson from my plugin (the 
Hudson community have forked it anyway).

The plugin is still using the old org.jvnet.hudson.plugins Maven groupId - so I 
was considering changing this at the same time.

However I wasn't sure if this is required to stay the same for plugin updates 
(or any other reason).

So before I make the change to the groupId is there any reason not to?

/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/groups/opt_out.

Re: jenkins debugging with eclipse (Windows)

[Zhengyuan Shen]

Thanks, when I got to http://localhost:8080/ I can see the Jenkins instance 
but I can not find my plugin that I need to debug, how can I debug my hello 
world plugin? Thanks.

Regards,


On Monday, June 3, 2013 8:52:54 AM UTC-7, Jesse Glick wrote:
>
> On 05/31/2013 04:25 PM, Zhengyuan Shen wrote: 
> > I can see a started SSHD at port 53119 and JNLP slave agent listener 
> started on TCP port 53120. So they are not the HTTP port that I need? I see 
> no other ports during the 
> > startup except the 8080 and 8000. 
>
> Go to: http://localhost:8080/ 
>

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

Re: jenkins debugging with eclipse (Windows)

[Jesse Glick]

On 05/31/2013 04:25 PM, Zhengyuan Shen wrote:

I can see a started SSHD at port 53119 and JNLP slave agent listener started on 
TCP port 53120. So they are not the HTTP port that I need? I see no other ports 
during the
startup except the 8080 and 8000.


Go to: http://localhost:8080/

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

Re: jenkins debugging with eclipse (Windows)

[Zhengyuan Shen]

Can anybody help me on this please? I still can not see the jenkins 
instance for debugging through a browser.

Regards,


On Friday, May 31, 2013 1:14:26 PM UTC-7, Kevin Fleming wrote:
>
> There are multiple port numbers emitted during the Jenkins startup (HTTP, 
> JNLP, maybe others). You need to be sure you are connecting to the HTTP 
> port.
>
> - Original Message -
> From: jenkin...@googlegroups.com 
> To: jenkin...@googlegroups.com 
> Cc: Kevin Fleming (BLOOMBERG/ 731 LEXIN) 
> At: May 31 2013 16:07:22
>
> Thanks!
>
> I see the port number is 52614 and then I connect the browser to 
> localhost:52614, is that correct thing to do?
>
> After I tried to connect using the browser, I get warning says that 
> connection #1 and #2 are both failed. for java.io.EOFException. Do you know 
> why does this happen? Thanks.
>
>
>
> On Friday, May 31, 2013 12:57:48 PM UTC-7, Kevin Fleming wrote:
>>
>> No, it does not upload the plugin anywhere. It launches a local Jenkins 
>> instance and loads the plugin into that instance; during the launch process 
>> it outputs the port number it is listening on, for you to connect with your 
>> browser.
>>
>> - Original Message -
>> From: jenkin...@googlegroups.com 
>> To: jenkin...@googlegroups.com 
>> At: May 31 2013 15:45:47
>>
>> Can you be a little bit more specific please? I am just wondering if the 
>> mvnDebug phi:run command will upload the new plugin onto jenkins server or 
>> not. I can see from the terminal that the plugin is found and implemented 
>> while I still can not see the plugin in the browser at localhost:8080.
>>
>> Thanks
>>
>> On Friday, May 31, 2013 12:00:19 PM UTC-7, Jesse Glick wrote:
>>>
>>> On 05/31/2013 02:09 PM, Zhengyuan Shen wrote: 
>>> > Then I go to localhost:8080 to see the plugin but I found nothing 
>>> there. 
>>>
>>> Try using the latest version of maven-hpi-plugin. 
>>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>>  -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-de...@googlegroups.com .
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
>
>

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

Re: Build flow plugin extension

[nicolas de loof]

you can extend the DSL by invoking methods from custom plugin, so can run
you custom code to check a build is required before invoking the DSL
"build()" method.


2013/6/3 BELLUS Stefan 

>  Thanks for reply. 
>
> Can you describe me roughly how can I archive my goal by “extension points
> ”.
>
> ** **
>
> Br
>
> Stevo
>
> ** **
>
> *From:* jenkinsci-dev@googlegroups.com [mailto:
> jenkinsci-dev@googlegroups.com] *On Behalf Of *nicolas de loof
> *Sent:* Monday, June 03, 2013 4:14 PM
> *To:* jenkinsci-dev@googlegroups.com
> *Subject:* Re: Build flow plugin extension
>
> ** **
>
> ** **
>
> ** **
>
> 2013/6/3 BELLUS Stefan 
>
> Hi all
>
>  
>
> I want to extend build flow plugin.
>
> I want to achieve that build flow plugin will not trigger build when it is
> not necessary from user point of view. E.g. when there are no changes in
> scm of job or in my scenario when there are no changes in dependencies of
> job, calculated by my build system.
>
>  
>
> I want to add execution of user groovy script (configured on project
> configuration page) before each build defined in project configuration.***
> *
>
>  
>
> The input to user groovy script will be reference to job that has to be
> build.
>
> The return of script should be null or reference to existing build. 
>
> When null is returned build flow plugin will trigger new build.
>
> When reference to existing build is returned then build flow plugin will
> not trigger new build and will use data from returned build.
>
>  
>
> I’m new in Java/Groovy/Maven…..
>
>  
>
> I briefly check sources of build flow plugin and find place where to call
> user groovy script. I want to call it before 
> “project.scheduleBuild2(project.getQuietPeriod(),
> cause, actions);” and check its return value.
>
> /* package */ JobInvocation run(Cause cause, List actions) {**
> **
>
> future = project.scheduleBuild2(project.getQuietPeriod(), cause,
> actions);
>
> if (future == null) {
>
> throw new CouldNotScheduleJobException("Could not schedule job
> "
>
> + project.getName() +", ensure its not already
> enqueued with same parameters", e);
>
> }
>
> return this;
>
> in file
> https://github.com/sbellus/build-flow-plugin/blob/master/src/main/groovy/com/cloudbees/plugins/flow/JobInvocation.groovy
> 
>
>  
>
> I briefly checks groovy script plugin to find out how to execute groovy
> script. I’m lost in sources up to now J.
>
>  
>
> In general:
>
> **1.   **Did you think that it is good way to extend existing plugin
> by groovy script (make some kind of plugin in plugin)?
>
> ** **
>
> build-flow plugin is extensible, you just need to create a custom plugin
> to expose the adequate additional methods.
>
> see https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin"extension 
> points"
> 
>
>  
>
>  **1.   **Did you think that I should re-implement groovy script
> invocation in this plugin or I can somehow use groovy plugin in build flow
> plugin?
>
>  ** **
>
> I don't recommend deep integration within build-flow as I still need to
> investigate various option to make is safer/asynchronous, that probably
> will significantly change implementation
>
>  
>
>  **1.   **Does anybody implement such functionality (don’t trigger
> build when not necessary)? Similar functionality is requested in
> https://issues.jenkins-ci.org/browse/JENKINS-11455.
>
> Best regards
>
> Stevo
>
>  
>
>  
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>  
>
>  ** **
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>  
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

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

RE: Build flow plugin extension

[BELLUS Stefan]

Thanks for reply.
Can you describe me roughly how can I archive my goal by "extension points".

Br
Stevo

From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On 
Behalf Of nicolas de loof
Sent: Monday, June 03, 2013 4:14 PM
To: jenkinsci-dev@googlegroups.com
Subject: Re: Build flow plugin extension



2013/6/3 BELLUS Stefan 
mailto:stefan.bel...@frequentis.com>>
Hi all

I want to extend build flow plugin.
I want to achieve that build flow plugin will not trigger build when it is not 
necessary from user point of view. E.g. when there are no changes in scm of job 
or in my scenario when there are no changes in dependencies of job, calculated 
by my build system.

I want to add execution of user groovy script (configured on project 
configuration page) before each build defined in project configuration.

The input to user groovy script will be reference to job that has to be build.
The return of script should be null or reference to existing build.
When null is returned build flow plugin will trigger new build.
When reference to existing build is returned then build flow plugin will not 
trigger new build and will use data from returned build.

I'm new in Java/Groovy/Maven.

I briefly check sources of build flow plugin and find place where to call user 
groovy script. I want to call it before 
"project.scheduleBuild2(project.getQuietPeriod(), cause, actions);" and check 
its return value.
/* package */ JobInvocation run(Cause cause, List actions) {
future = project.scheduleBuild2(project.getQuietPeriod(), cause, 
actions);
if (future == null) {
throw new CouldNotScheduleJobException("Could not schedule job "
+ project.getName() +", ensure its not already enqueued 
with same parameters", e);
}
return this;
in file 
https://github.com/sbellus/build-flow-plugin/blob/master/src/main/groovy/com/cloudbees/plugins/flow/JobInvocation.groovy

I briefly checks groovy script plugin to find out how to execute groovy script. 
I'm lost in sources up to now :).

In general:
1.   Did you think that it is good way to extend existing plugin by groovy 
script (make some kind of plugin in plugin)?

build-flow plugin is extensible, you just need to create a custom plugin to 
expose the adequate additional methods.
see https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin "extension 
points"

1.   Did you think that I should re-implement groovy script invocation in 
this plugin or I can somehow use groovy plugin in build flow plugin?

I don't recommend deep integration within build-flow as I still need to 
investigate various option to make is safer/asynchronous, that probably will 
significantly change implementation

1.   Does anybody implement such functionality (don't trigger build when 
not necessary)? Similar functionality is requested in 
https://issues.jenkins-ci.org/browse/JENKINS-11455.
Best regards
Stevo


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



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


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

Re: Build flow plugin extension

[nicolas de loof]

2013/6/3 BELLUS Stefan 

>  Hi all
>
> I want to extend build flow plugin.
> I want to achieve that build flow plugin will not trigger build when it is
> not necessary from user point of view. E.g. when there are no changes in
> scm of job or in my scenario when there are no changes in dependencies of
> job, calculated by my build system.
>
> I want to add execution of user groovy script (configured on project
> configuration page) before each build defined in project configuration.
>
> The input to user groovy script will be reference to job that has to be
> build.
> The return of script should be null or reference to existing build.
> When null is returned build flow plugin will trigger new build.
> When reference to existing build is returned then build flow plugin will
> not trigger new build and will use data from returned build.
>
> I’m new in Java/Groovy/Maven…..
>
> I briefly check sources of build flow plugin and find place where to call
> user groovy script. I want to call it before 
> “project.scheduleBuild2(project.getQuietPeriod(),
> cause, actions);” and check its return value.
> /* package */ JobInvocation run(Cause cause, List actions) {
> future = project.scheduleBuild2(project.getQuietPeriod(), cause,
> actions);
> if (future == null) {
> throw new CouldNotScheduleJobException("Could not schedule job
> "
> + project.getName() +", ensure its not already
> enqueued with same parameters", e);
> }
> return this;
> in file *
> https://github.com/sbellus/build-flow-plugin/blob/master/src/main/groovy/com/cloudbees/plugins/flow/JobInvocation.groovy
> *
>
> I briefly checks groovy script plugin to find out how to execute groovy
> script. I’m lost in sources up to now J.
>
> In general:
>
> 1. Did you think that it is good way to extend existing plugin by
>groovy script (make some kind of plugin in plugin)?
>
>
build-flow plugin is extensible, you just need to create a custom plugin to
expose the adequate additional methods.
see https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin"extension
points"


>
>1. Did you think that I should re-implement groovy script invocation
>in this plugin or I can somehow use groovy plugin in build flow plugin?
>
>
I don't recommend deep integration within build-flow as I still need to
investigate various option to make is safer/asynchronous, that probably
will significantly change implementation


>
>1. Does anybody implement such functionality (don’t trigger build when
>not necessary)? Similar functionality is requested in *
>
> https://issues.jenkins-ci.org/browse/JENKINS-11455*
>.
>
> Best regards
> Stevo
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

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

Build flow plugin extension

[BELLUS Stefan]

Hi all

I want to extend build flow plugin.
I want to achieve that build flow plugin will not trigger build when it is not 
necessary from user point of view. E.g. when there are no changes in scm of job 
or in my scenario when there are no changes in dependencies of job, calculated 
by my build system.

I want to add execution of user groovy script (configured on project 
configuration page) before each build defined in project configuration.

The input to user groovy script will be reference to job that has to be build.
The return of script should be null or reference to existing build.
   When null is returned build flow plugin will trigger new build.
   When reference to existing build is returned then build flow plugin will not 
trigger new build and will use data from returned build.

I'm new in Java/Groovy/Maven.

I briefly check sources of build flow plugin and find place where to call user 
groovy script. I want to call it before 
"project.scheduleBuild2(project.getQuietPeriod(), cause, actions);" and check 
its return value.
/* package */ JobInvocation run(Cause cause, List actions) {
future = project.scheduleBuild2(project.getQuietPeriod(), cause, 
actions);
if (future == null) {
throw new CouldNotScheduleJobException("Could not schedule job "
+ project.getName() +", ensure its not already enqueued 
with same parameters", e);
}
return this;
in file 
https://github.com/sbellus/build-flow-plugin/blob/master/src/main/groovy/com/cloudbees/plugins/flow/JobInvocation.groovy

I briefly checks groovy script plugin to find out how to execute groovy script. 
I'm lost in sources up to now :).

In general:
1.  Did you think that it is good way to extend existing plugin by groovy 
script (make some kind of plugin in plugin)?
2.  Did you think that I should re-implement groovy script invocation in 
this plugin or I can somehow use groovy plugin in build flow plugin?
3.  Does anybody implement such functionality (don't trigger build when not 
necessary)? Similar functionality is requested in 
https://issues.jenkins-ci.org/browse/JENKINS-11455.

Best regards
Stevo


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