environment variables - Jenkins Perforce Label Sharing across jobs -


is there way 1 can share variables across jenkins jobs ?

job1 collects required source code , labels them using perl scripts. number of other jobs compiles code since there many versions. of have made other jobs depend on job1 same code collected head since labelled before in job1, not case during release since codes going in repository @ odd hours had no control, thought nice if find way sync code using perforce label created in job1. did not find way sync particular label got created in different job. thought if set environment variable , use same following jobs, codes can in perfect sync. seems environment variables cannot shared across jobs.

i appreciate ideas , help.

can use "use upstream project revision" option? allows sync changeset of project.

if want stick label idea, think it's doable. haven't tried this, think first have first job create new label based on job name , build number; both available in create label post-build action.

if launch downstream job using paramaterized trigger plugin have access upstream job name , build number environment variables. 'p4 label' field in downstream job can use parameter substitution specify correct label name sync to.


Comments

Popular posts from this blog

javascript - Count length of each class -

What design pattern is this code in Javascript? -

hadoop - Restrict secondarynamenode to be installed and run on any other node in the cluster -