e dev list…
>
> ** **
>
> /James
>
> ** **
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *nicolas de loof
> *Sent:* 30 August 2013 15:52
>
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: Bu
this should be moved to the dev list...
/James
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
Sent: 30 August 2013 15:52
To: jenkinsci-users@googlegroups.com
Subject: Re: Build flow plugin: How to copy results from downstream jobs
I
I don't want to follow this direction, as I know people won't consider the
warning on documentation.
AggregatedTestResultPublisher can be configured with a set of jobs, maybe
this require some tweaks on UI, not sure (sorry, don't have much time to
investigate on this topic today)
2013/8/30 John
I see the class javadoc for that class but how would I use that to actually
aggregate the junit tests to report in the build-flow plugin?
Is it also possible to discourage people in the documentation and yet leave
the workspace there so its possible?
On Fri, Aug 30, 2013 at 9:22 AM, nicolas de l
I indeed removed workspace support especially to discourage such a "write
some custom jenkins code using DSL" approach.
build-flow is about orchestrating jobs, not creating custom plugins
junit aggregator is using the original location for junit results, and
dynamically aggregating. It doesn't cop
Teilo, When did build flow stop having a workspace? I finally got this to
work by archiving all of the junit files from the downstream jobs onto the
master, running build-flow on the master, and directly copying the files
from the archive of the downstream build to build flow and running the
ju
jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
Sent: 30 August 2013 09:28
To: jenkinsci-users@googlegroups.com
Subject: Re: Build flow plugin: How to copy results from downstream jobs
AggregatedTestResultPublisher should work with build-fl
AggregatedTestResultPublisher should work with build-flow, passing the list
of jobs to aggregate. I'm not sure it could automatically support the
downstream mode, need to setup a test instance to check what prevent this,
but can image few reasons.
2013/8/30 teilo
> The BuildFlow doesn't use a w
The BuildFlow doesn't use a workspace anymore[1] - so your workaround most
likely won't work as you expect.
I'm not convinced that this is a good thing as like you I would like to
show test results in the main flow job - not have another job that is just
aggregate & report.
On Monday, 12 Augus
I have a very similar problem: I'm looking for a way to get the aggregated
test results which are published by some of my jobs. However, the main
Build Flow job does not seem to correctly identify the downstream tasks it
needs to collect the test results from, even though the fingerprinting of
Do you guys have any idea how to pull files, specifically test results,
from the jobs started in a build flow up to the build flow job itself so it
can be the one that presents all of the test results?
I presume that if I can copy them from the slaves up to the workspace of
the build flow build
sure, rescue handle whatever happens in gard block, that has no restriction
on nested content
2013/1/3 Patrick van der Velde
> Thanks for that suggestion. One question about the guard statement. Can it
> handle multiple statements? i.e. is the following allowed?
>
> guard {
> build("job1")
>
Thanks for that suggestion. One question about the guard statement. Can it
handle multiple statements? i.e. is the following allowed?
guard {
build("job1")
build("job2")
} rescue {
build("finaljob")
}
or even this
guard {
parallel(
{ build("job1a") },
{ build("job
use gard+rescue so you can execute a post-job even when some jobs are
unstable
2013/1/2 Patrick
> 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 so
Guard + rescue
Le 2 janv. 2013 02:11, "Patrick" a écrit :
> 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 mea
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
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
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
Hi All
I've started using the Build Flow plugin to simplify my build pipeline.
I've gotten it to work just fine (all the jobs get triggered at the right
stage) but I can't seem to copy the generated build results from the
downstream jobs. For instance my build produces a CCM log (an XML file) a
19 matches
Mail list logo
