The idea of the envinject plugin is really nice, but It sounds more and more
like not a good idea to use it - it seems very unstable and soon it will have
more releases then jenkins core… :(
On 01.01.2013, at 01:32, "glsilver...@pssd.com" wrote:
> Correction from my original post: The first p
I recommend to avoid such scripting in the flow DSL, that is only designed
to manage orchestration, not to replace plugins/job logic
use copy-artifact plugin to get last build / upstream / fingerprint file
from upstream job
Future version of build-flow may implement some helper methods to pass
fin
Generally, a plugin that has more releases than a core component, this
does not sound too bad for me.
Am Dienstag, den 01.01.2013, 10:59 +0100 schrieb domi
:
The idea of the envinject plugin is really nice, but It sounds more
and more like not a good idea to use it - it seems very unstable a
Hi
Mmm ok, I guess I could create a separate job to gather all the test
results. Thanks for the advice :)
Regards
Petrik
On Tue, Jan 1, 2013 at 11:08 PM, nicolas de loof
wrote:
> I recommend to avoid such scripting in the flow DSL, that is only designed
> to manage orchestration, not to repla
Ok I'm going to have to amend this answer. My idea of having a separate job
at the end to gather the results would work if it wasn't for the fact that
the build flow plugin kills the build as soon as one of the jobs fails.
That means I only can get the results if the build works which is not wha
Hi All
We have a chained job (job with 4 subjobs).
Is there a way to pass SVN revision number of the update checkout from
the 1st subjob to the next subsequent subjob among the build subjobs,
so that all the subjobs run on the latest revision number of the 1st
subjob after the 1st job started? If
As a stop-gap solution, I've created a generic job that executes a windows
script to rename the 'workspace.tar.gz' to 'workspace.zip'
Once the "Archive Workspace" post-build action is complete, this script job
can then be triggered using "Parameterized Trigger Build" with the "current
job name"