On Tue, 2015-05-12 at 07:23 -0700, Ioannis Moutsatsos wrote:
> Although I'm a bit confused by your question, if you want to exchange
> data between two jobs the answer is 'Yes'.
>
>
> The job that requires data from a previous build should have a Run
> type parameter, that you users can point to the required data of a
> previous job.
> A Run Type parameter is essentially a reference into a previous build.
>
>
> Your build script (I use Groovy fro this a lot) can use this
> parameter (translated internally to the build URL) to retrieve
> archived data from the indicated build.
> This approach has worked well for me.
I use comparable same way by copying file as parent job but cannot say
that it's useful. In chain of 5 jobs this workflow means 5 file copies
or 5 levels of parent searching.
Also it is not clear how to use it under MultiJob workflow. Looks like
it will ask to go from subjob to the multijob and find previous subjob
step?
And it doesn't help with providing parameters from build step to post
build step or email generation step.
--
Thanks,
Roman
>
> On Monday, May 11, 2015 at 12:55:47 PM UTC-4, Roman wrote:
> Hi,
>
> Does Jenkins has any kind of common storage which I could use
> for data
> exchange?
> samples:
> - set options for next step from groovy system step script
> (or every
> set options to groovy post build script from shell)
> - set options for other job which is executed on other node
>
> Currently I do it via files(and have hardcoded somehow files
> names) or
> jobs parameters. I think it will be very nice to have any kind
> of daemon
> which
> could be used via simple network interface for
> setting/getting/creating/deleting variables.
>
> --
> Thanks,
> Roman
>
> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/f4428e25-83fc-4463-9b3f-b4194505ae21%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/1431442720.3389.28.camel%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
