Right now I can’t see a way to do this but my knowledge on this topic is very 
limited. I also have to work on it soon so I’ll let you know if I find a way 
(and if you still don’t have the answer).

Please share your progress, if any 

Good luck !

Thomas


> Le 1 juin 2016 à 20:35, François Genois <frankgenera...@gmail.com> a écrit :
> 
> Hello Thomas,
> 
> Thank you very much for your answer.
> The promoted builds plugin is indeed a extension point.
> 
> I added the following line to my dependencies "testCompile 
> 'org.jenkins-ci.plugins:promoted-builds:2.27@jar'" and my 'gradlew test' 
> command now succeeds.
> 
> I just tried applying the same logic to the 'debugXml' gradle task (I use the 
> XML to verify if I haven't done any regression during refactoring), but I 
> can't figure out how to make this code run in a context running an instance 
> of the promoted-builds plugin.
> 
> Do you have an idea of how I could get the XML generated from the scripts?
> 
> Thank you again and have a nice day!
> 
> - Frank
> 
> 
> On Wednesday, June 1, 2016 at 12:20:01 PM UTC-4, Thomas Zoratto wrote:
> Hello Frank, 
> 
> I guess the promoted builds plugin is not directly compatible with the job 
> DSL plugin. I mean you can’t find DSL methods relative to the promoted builds 
> plugin in the online API 
> https://github.com/franknarf8/job-dsl-gradle-example/commit/f15b7fbf698d7be29b8527043d8649ab15559842
>  
> <https://github.com/franknarf8/job-dsl-gradle-example/commit/f15b7fbf698d7be29b8527043d8649ab15559842>.
>  
> 
> I think the job DSL plugin must use the extension point when in the context 
> of a running instance with the promoted builds plugin installed.
> 
> Though, I suppose you can test it locally thanks to the last updates of 
> sheehan's github repo. See 
> https://github.com/sheehan/job-dsl-gradle-example/commit/9d6260b44cefdd832ee3f854f107b24f15881ea7
>  
> <https://github.com/sheehan/job-dsl-gradle-example/commit/9d6260b44cefdd832ee3f854f107b24f15881ea7>.
>  You’ll have to specify the plugins you have in your running instance in 
> order to simulate a similar environment for your local tests.
> 
> sorry for my poor English !
> 
> Thomas
> 
>> Le 1 juin 2016 à 16:36, François Genois <frankge...@gmail.com <javascript:>> 
>> a écrit :
>> 
>> Good morning everyone,
>> 
>> I'm currently using a project based on 
>> https://github.com/sheehan/job-dsl-gradle-example 
>> <https://github.com/sheehan/job-dsl-gradle-example> and I am trying to get 
>> the promoted-builds plugin to work with this project 
>> (https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin 
>> <https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin>).
>> 
>> Everything works fine on my Jenkins server (with the plugin installed), but 
>> I can't figure out a way to make my code work on this local project. I use 
>> this project to work locally, to debug and to test; instead of sending it to 
>> the server for every single modifications.
>> 
>> Here is an example project that reproduces my problem :
>> https://github.com/franknarf8/job-dsl-gradle-example/commit/f15b7fbf698d7be29b8527043d8649ab15559842
>>  
>> <https://github.com/franknarf8/job-dsl-gradle-example/commit/f15b7fbf698d7be29b8527043d8649ab15559842>
>> 
>> And here one of the ways I run it locally :
>> gradlew debugXml -Dpattern=jobs/example1Jobs.groovy
>> 
>> I'm not quite sure if this is a limitation/bug/feature_request or if it is 
>> simply me having a hard time to make it work.
>> 
>> Please help me and I wish you a nice day!
>> 
>> - Frank
>> 
>> -- 
>> 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-use...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/596540e7-63dc-49c2-9532-be154aafd98d%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/596540e7-63dc-49c2-9532-be154aafd98d%40googlegroups.com?utm_medium=email&utm_source=footer>.
>> For more options, visit https://groups.google.com/d/optout 
>> <https://groups.google.com/d/optout>.
> 
> 
> -- 
> 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 
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/c5fbe124-2007-4d58-9daa-35bf41cbf1ea%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/c5fbe124-2007-4d58-9daa-35bf41cbf1ea%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4E2786B1-62C5-47CB-A595-463E41CC491F%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to