We also ended up generally saving all metadata (system/environment
variables, jenkins parameters, and build properties etc) into properties
file and archieve them. This approach simplifies/works around many problems
we had. Now every build has its metadata archived, for downstream jobs or
later references, we can get all necessary information from this one file,
no extra parameters needed to be pass around. Furthermore, if anything went
wrong, the metadata is very helpful for the investigation. I would also
recommend this simple strategy.
Am 11.01.2013 21:05 schrieb "Stanley, Jason" <jason.stan...@tekelec.com>:
> I ran into this very same problem.****
>
> ** **
>
> It appears (at least with my experience) the only variables passed from
> Job A -> Job B are the variables predefined by Jenkins.****
>
> ** **
>
> To work around the issue, in my build shell for Job A, I wrote the
> variable=value into a file and used the “Parameters from properties file”
> Parameter in the “Trigger parameterized build on other projects” when
> running Job B.****
>
> ** **
>
> Jason****
>
> ** **
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *zw
> *Sent:* Friday, January 11, 2013 2:50 PM
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* How to pass parameters between jobs - quick question****
>
> ** **
>
> Hi All****
>
> ** **
>
> We have job A to kick off Job B****
>
> Job A uses in build section execute shell to get a svn revision number and
> sets SVN_REVISION. ****
>
> (We understand that there's the option to use "This build is
> parameterized" String Parameter and set SVN_REVISION value as HEAD, but we
> have our reasons to not use that)****
>
> echo ${SVN_REVISION_NUM}****
>
> export SVN_REVISION=${SVN_REVISION_NUM}****
>
> echo ${SVN_REVISION}****
>
> ** **
>
> output****
>
> + SVN_REVISION_NUM=47337****
>
> :****
>
> + echo 47337****
>
> 47337****
>
> + export SVN_REVISION=47337****
>
> + SVN_REVISION=47337****
>
> ** **
>
> In *Post-build Actions section*****
>
> we have Trigger parameterized build on other projects, and predefined
> parameter set to SVN_REVISION=${SVN_REVISION_NUM}****
>
> ** **
>
> But in Job B console, it dosent see the revision number and Job B's SCM could
> retrieve the revision number****
>
> Location 'https://jobBhost.com/svn/src@${SVN_REVISION_NUM}' does not exist****
>
> ** **
>
> What did we do wrong ?****
>
> ** **
>
> Thanks****
>
> ** **
>
>
