On Fri, May 2, 2014 at 12:45 AM, nicolas de loof
<nicolas.del...@gmail.com> 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
>
Why is it a problem to be able to do convenient standard jenkins
operations without needing other jobs or passing a lot of extra
parameters around? Is there a way to require a 'quiet time' with
post-commit notifications on some of the jobs? We have many where we
only do nightly builds after changes and the original design looked
useful for doing some complex testing. Or if another job is used for
polling, can you keep that job from doing a checkout that won't be
used?
--
Les Mikesell
lesmikes...@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-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
