Re: Build Flow Plugin and artifacts management in the DSL

2013-09-18 Thread nicolas de loof
I removed workspace in HEAD, previous version of plugin extend a classic job 2013/9/18 Les Mikesell > On Wed, Sep 18, 2013 at 3:06 PM, nicolas de loof > wrote: > > build flow don't have a workspace, so no place to store child artifacts. > > you could trigger a final job to collect other ones a

How do I discover the available API interfaces?

2013-09-18 Thread lfast
I found out that each Jenkins object type has it's own API documentation. Root, Folder, Job, Build, etc. Is there any way to somehow "search the tree" for API interfaces? With the API I can navigate around the JSON/XML hierarchy but I can't quite see how to gather info aboutthe API xpaths.

Reading HTTP request body from triggered parameterized job

2013-09-18 Thread Alex Kira
Hi, Is there a way to read the request body from a triggered job? I am trying to integrate with another service that posts the request parameters as JSON in the raw body. This is a curl request that generates a similar request: curl -X POST -H "Content-Type: application/json" -d '{"commit

Re: Jenkins failure when no tests failed [solved]

2013-09-18 Thread Farrukh Najmi
I have identified the source of my problem to be a failure of a copy command run via maven-antrun-plugin. No error message was logged but copy had failed as there were files owned by a different user than jenkins user in the target directory of the copy. I was focusing on test failures (there

Re: Build Flow Plugin and artifacts management in the DSL

2013-09-18 Thread Les Mikesell
On Wed, Sep 18, 2013 at 3:06 PM, nicolas de loof wrote: > build flow don't have a workspace, so no place to store child artifacts. > you could trigger a final job to collect other ones artifacts using > copy-artifact That's, ummm, interesting... I see a workspace in the jenkins job view contain

Re: Build Flow Plugin and artifacts management in the DSL

2013-09-18 Thread nicolas de loof
build flow don't have a workspace, so no place to store child artifacts. you could trigger a final job to collect other ones artifacts using copy-artifact 2013/9/18 Les Mikesell > On Wed, Sep 18, 2013 at 2:37 PM, nicolas de loof > wrote: > > not inside the flow DSL, but inside jobs. build-flow

Re: Build Flow Plugin and artifacts management in the DSL

2013-09-18 Thread Les Mikesell
On Wed, Sep 18, 2013 at 2:37 PM, nicolas de loof wrote: > not inside the flow DSL, but inside jobs. build-flow is an orchestrator, > it's not here to replace jenkins classic way to share artifacts between > builds (fingerprints, copyartifact plugin, build number parameter, etc) > > collect execute

Perforce Plugin

2013-09-18 Thread Fisher, Allen
I just noticed that if you use the workspace cleanup plugin (or just go to the build box and delete the workspace) to delete your workspace before the build starts, the Perforce plugin thinks you have everything you need to build and tries to build anyway. Shouldn't it do a sync -f to put the fi

Re: Build Flow Plugin and artifacts management in the DSL

2013-09-18 Thread nicolas de loof
not inside the flow DSL, but inside jobs. build-flow is an orchestrator, it's not here to replace jenkins classic way to share artifacts between builds (fingerprints, copyartifact plugin, build number parameter, etc) collect executed jobs build object def b = build( "foo" ) then pass build numbe

Re: Build Flow Plugin and artifacts management in the DSL

2013-09-18 Thread Les Mikesell
On Wed, Sep 18, 2013 at 12:38 PM, nicolas de loof wrote: > this is a voluntary limitation. Even flow uses groovy, it's supposed to be a > DSL, not a system groovy script. Use scriptler/groovy plugin/etc if you want > to do such thing OK, but how? I don't see the option to do another build step w

Re: Build Flow Plugin and artifacts management in the DSL

2013-09-18 Thread nicolas de loof
this is a voluntary limitation. Even flow uses groovy, it's supposed to be a DSL, not a system groovy script. Use scriptler/groovy plugin/etc if you want to do such thing 2013/9/18 Schalk Cronjé > With Build Flow Plugin you can only access Groovy modues that Jenkins > System Groovy has access t

Re: Build Flow Plugin and artifacts management in the DSL

2013-09-18 Thread Schalk Cronjé
With Build Flow Plugin you can only access Groovy modues that Jenkins System Groovy has access to. You cannot use @Grab to pull in extra modules. This is a limitation of Build Flow Plugin IMHO, but Nicolas does not agree - https://groups.google.com/forum/#!topic/jenkinsci-users/2XFDB5g7O7A). Th

Maven repository used by Jenkins

2013-09-18 Thread Thomas Vestergaard Trolle
Hi, As one of our Jenkins slaves were running out of disc space, I realised, that it used two separate Maven-repositories, the default ~/m2/repository, and an additional (c:\tools\localrepository). I have searched through Jenkins management pages to find this second path, but without any luck.(The

Re: append arbitrary versioning to the generated war file

2013-09-18 Thread Michaël Pailloncy
I think the best way to do this is using Maven. But if you want to keep this way, you can add another step "Execute shell" to the job (or "Execute Windows batch command" depending of your OS) that rename your generated WAR manually. You can use $BUILD_NUMBER and $SVN_REVISION to rename your war fi