On Tue, 16 Aug 2011 20:47:33 +0530, Deepti Kalakeri <deepti.kalakeri@linaro.org> wrote:
> On Tue, Aug 16, 2011 at 8:15 PM, James Westby <james.westby@linaro.org>wrote:
>
> > On Tue, 16 Aug 2011 18:02:02 +0530, Deepti Kalakeri <
> > deepti.kalakeri@linaro.org> wrote:
> > > Hello,
> > >
> > > I am using jenkins for continuous integration work.
> > > I have a requirement where I need to trigger a job as part of the post
> > build
> > > step of a job.
> > > For example I have a job to build a source and I would like to trigger
> > the
> > > job that tests the binaries as part of the post build step.
> > > Although I am aware how to trigger a job in the post build step I am
> > failing
> > > to understand how to pass
> > > certain parameters[ information that the next job needs to know to
> > execute]
> > > to the next job.
> > > I came across the "Parameterized Trigger Plugin"
> > > <
> > https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin
> > >but
> > > it does not explain how to access the parameters passed in the new job.
> > >
> > > Can someone help me with this ?
> >
> > Hi,
> >
> >
> > https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin?focusedCommentId=47087758#comment-47087758
> >
> > states that the downstream job just sees the values as environment
> > variables.
> >
> > What do you want to do with parameters that are passed?
> >
>
> I need to capture the name of the new hardware pack that is built to be used
> further down for testing.
> Right now I am using a file to write this information and then in the
> testing job I read this file.
>
> Any suggestion or alternative?

I think the "Parameters from properties file" option might be what you
want?  It seems to me that your first job should create a file in its
workspace that contains

TEST_HWPACK_NAME=<new hwpack name>

and then if you point the plugin at that in the job configuration, the
triggered job should be passed TEST_HWPACK_NAME as a parameter.

Cheers,
mwh