Post commit is nice but is not convenient for us as we have stash hosted
in the cloud and jenkins behind the firewall (due to some specialized
build slaves). We'd need to expose jenkins. Doable but should not be
required IMHO.
We have a multi-stage build, some parallel stuff as well and build flow
seemed like a great wrapper to encapsulate everything together.
I'm not sure about abusing the DSL, that seems more like a feature to
me ;-)
Anyway thanks for the info. I appreciate the explanation.
Greg
On Fri, 2014-05-02 at 07:45 +0200, nicolas de loof wrote:
> Issue with workspace is people are abusing the DSL and start to "code"
> build custom steps into build flow, not delegating to jobs.
> build flow was designed to orchestrate ("flow") jobs together. The
> fact jenkins needs a workspace to poll scm is another story. I prefer
> post-commit notification anyway
>
>
> 2014-05-01 16:05 GMT+02:00 Greg Dickie <g...@justaguy.ca>:
>
>
> Hi Nicolas,
>
>
> I would like to understand the reason for that design.
> Maybe I'm using it incorrectly but it was doing what we
> needed. Why wouldn't you want SCM polling, artifacts, etc.? Is
> the intention that we create build steps to handle that stuff
> or is build flow not the right way to go for this?
>
>
> Thanks,
> Grg
>
>
> On Thursday, May 1, 2014 1:42:11 AM UTC-4, Nicolas De loof
> wrote:
> yes, build-flow is desgined for orchestration, not as
> a regular job with SCM workspace and all
>
>
> that being said, as I can't find spare time to invest
> on this plugin, feel free to take leadership on it and
> make it evolve your way
>
>
> 2014-05-01 0:13 GMT+02:00 Les Mikesell
> <lesmi...@gmail.com>:
> On Wed, Apr 30, 2014 at 5:05 PM, Tim Jackson
> <lost...@gmail.com> wrote:
> > I agree that .11 is a huge step backwards
> for me. As far as I can tell, the
> > build flow plugin no longer triggers the
> failure event of the email-ext
> > plugin. So I am no longer getting failure
> mails for the overall job.
> > Setting up a new job to handle the failure
> mail is redundant and can fail
> > itself, thus changing the results. I am
> more apt to just dump the build
> > flow plugin and find a more suitable method.
> >
> > It is very disappointing to have
> functionality removed. A lot of us have
> > based large amounts of work on what it did.
>
>
> I think the only way to make it do anything is
> to set up one job that
> just polls the SCM and triggers the build-flow
> job, then pass all your
> build parameters around to a final job
> executed by the flow that uses
> the copy artifacts plugin to gather up the
> results of whatever the
> other elements did. Seems like a lot of
> clutter and a confusing
> process to have to start one job but end up
> with the results in
> another.
>
>
> --
> Les Mikesell
> lesmi...@gmail.com
>
> --
> You received this message because you are
> subscribed to the Google Groups "Jenkins
> Users" group.
>
> To unsubscribe from this group and stop
> receiving emails from it, send an email to
> jenkinsci-use...@googlegroups.com.
>
> For more options, visit
> https://groups.google.com/d/optout.
>
>
>
>
>
>
--
Greg Dickie
514-983-5400
just a guy
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
