If I understand correctly you actually have two independent jobs. You
shouldn't use flow plugin just to monitor repository and then start
downstream jobs. Each job should be configured independently with different
SCM trigger.
--
You received this message because you are subscribed to the Goog
I don't have such a sample, need to duplicate some way the exclusion filter
used by SCM plugin
build flow don't us SCM triggers, so can't benefit advanced feature they
provide
2013/7/14 Thomas Fields
> Thanks for the reply.
>
> >> is you have to exclude some jobs based on scm commit, do it BEFO
Thanks for the reply.
>> is you have to exclude some jobs based on scm commit, do it BEFORE you call
>> build("job")
How would I do that - any ideas? Can you give me an example?
Cheers
Tom
Sent from my iPhone
On 13 Jul 2013, at 21:32, Thomas Fields wrote:
> Hi there,
>
> The build flow pl
build flow orchestrate job execution, it don't handle scm-triggers. When
flow is started, all builds involved will run
is you have to exclude some jobs based on scm commit, do it BEFORE you call
build("job")
2013/7/13 Thomas Fields
> Hi there,
>
> The build flow plugin looks really powerful but
Hi there,
The build flow plugin looks really powerful but it appears to be lacking
the ability to only trigger sub jobs when there are scm changes. I have a
simple build flow setup like so:
def tomjob = parallel ([
first: { build("tomflow1") },
second: { build("tomflow2") }
])
Each of sub jobs,
