How can I handle over an environment variable within a build flow?

179 views
Skip to first unread message

tps800

unread,
May 19, 2015, 10:12:22 AM5/19/15
to jenkins...@googlegroups.com
Hi!

I've set up a build flow using the "Build Flow Plugin":
guard {
    build( "job1" )
    build( "job2" )
    build( "job3" )
    build( "job4" )
} rescue {
    build( "job_cleanup" )
}

Now I want two things:
1. All these jobs shall share one Workspace or if this isn't possible: how can I handle a variable holding the workspace down to all jobs?

Job1 sets up a workspace, job2 and job3 work on it, job4 does too. They are different jobs, but all work with the same workspace. How can I accomplish this?

2. How can I assure all these jobs are done in sequence until the last one ends. All using one slot, without being interrupted?

At the moment it may be job1 runs, then job2 is queued, but has to wait until an other job releases a slot, because an other job occupied the slot job1 had used. I'd like to have something like job1 finishes, job2 is assigned the now free slot, job2 finishes, job3 is assigned the now free slot and so on until job5 finishes and the flow ends. Or in other words: how can I assign the next free slot to the flow job to handle it to the build jobs?

Ginga, Dick

unread,
May 19, 2015, 10:26:40 AM5/19/15
to jenkins...@googlegroups.com

Let’s see,,,

 

1.       What SCM are you using? I use Perforce and can tell the Perforce Plugin “not” to manage “client views” and create one in a fixed location AND set the Use custom workspace in Advanced Project Options to tell each job to use the same workspace. Therefore, Jenkins will not create a workspace with the job name. you do this in each of job1, job2, job,3 etc

2.       The example guarantees that sequence for this flow. If the entire flow is triggered again, it will pend until the current flow execution completes.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2232cf8e-12b5-461a-a276-10f136166d02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

tps800

unread,
May 21, 2015, 4:21:44 AM5/21/15
to jenkins...@googlegroups.com
On Tuesday, May 19, 2015 at 4:26:40 PM UTC+2, rginga wrote:

Let’s see,,,

 

1.       What SCM are you using? I use Perforce and can tell the Perforce Plugin “not” to manage “client views” and create one in a fixed location AND set the Use custom workspace in Advanced Project Options to tell each job to use the same workspace. Therefore, Jenkins will not create a workspace with the job name. you do this in each of job1, job2, job,3 etc

My question was, "How can I handle an environment variable set for one build to an other build?". What does this have to do with the used SCM???

build( "linux-3.10.y.prep", PARENT_WORKSPACE:build.workspace, PARENT_JOB_NAME:build.job_name)
[...]

Is there a list available listing all properties for "build.*" I can use?
The property "build.job_name" just doesn't exist. I've tried "build.job.name" and "build.jobname" but all with no success:
{
groovy.lang.MissingPropertyException: No such property: jobname for class: com.cloudbees.plugins.flow.FlowRun
	at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50)


	at org.codehaus.groovy.runtime.callsite.GetEffectivePojoPropertySite.getProperty(GetEffectivePojoPropertySite.java:63)


	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:227)


	at Script1.run(Script1.groovy:1)


	at Script1$run.call(Unknown Source)


	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)


	at Script1$run.call(Unknown Source)


	at com.cloudbees.plugins.flow.FlowDSL.executeFlowScript(FlowDSL.groovy:84)


	at com.cloudbees.plugins.flow.FlowRun$BuildWithWorkspaceRunnerImpl.doRun(FlowRun.java:180)


	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)


	at hudson.model.Run.execute(Run.java:1744)


	at hudson.model.Run.run(Run.java:1682)


	at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:153)


	at hudson.model.ResourceController.execute(ResourceController.java:98)


	at hudson.model.Executor.run(Executor.java:374)


FATAL: No such property: jobname for class: com.cloudbees.plugins.flow.FlowRun


groovy.lang.MissingPropertyException: No such property: jobname for class: com.cloudbees.plugins.flow.FlowRun


	at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50)


	at org.codehaus.groovy.runtime.callsite.GetEffectivePojoPropertySite.getProperty(GetEffectivePojoPropertySite.java:63)


	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:227)


	at Script1.run(Script1.groovy:1)


	at Script1$run.call(Unknown Source)


	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)


	at Script1$run.call(Unknown Source)


	at com.cloudbees.plugins.flow.FlowDSL.executeFlowScript(FlowDSL.groovy:84)


	at com.cloudbees.plugins.flow.FlowRun$BuildWithWorkspaceRunnerImpl.doRun(FlowRun.java:180)


	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)


	at hudson.model.Run.execute(Run.java:1744)


	at hudson.model.Run.run(Run.java:1682)


	at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:153)


	at hudson.model.ResourceController.execute(ResourceController.java:98)


	at hudson.model.Executor.run(Executor.java:374)


Finished: FAILURE
}

Ginga, Dick

unread,
May 21, 2015, 7:49:56 AM5/21/15
to jenkins...@googlegroups.com

Getting jobs to share the same workspace can be done by “AND set the Use custom workspace in Advanced Project Options to tell each job to use the same workspace”. I must have mistakenly assumed that that workspace contains source code to be built ?????

 

You never asked How can I handle an environment variable set for one build to an other build?" in your original message ????

 

To access environment tokens in Build-flow I have used :

 

build.properties["environment"]["JOB_NAME"]

build.number

 

the first can be used to get ANY environment variable either defined by Jenkins or injected/defined in your job.

 

Use this groovy to get all the properties of a build:

 

out.println 'Build Object Properties:'

build.properties.each { out.println "$it.key -> $it.value" }

--

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.

tps800

unread,
May 21, 2015, 4:19:01 PM5/21/15
to jenkins...@googlegroups.com


On Thursday, May 21, 2015 at 1:49:56 PM UTC+2, rginga wrote:

Getting jobs to share the same workspace can be done by “AND set the Use custom workspace in Advanced Project Options to tell each job to use the same workspace”. I must have mistakenly assumed that that workspace contains source code to be built ?????

 

You never asked How can I handle an environment variable set for one build to an other build?" in your original message ????

 

To access environment tokens in Build-flow I have used :

 

build.properties["environment"]["JOB_NAME"]

This was what I was seaching for. It does work now as expected.
Reply all
Reply to author
Forward
0 new messages