Yes, good point.
In the current implementation, the way you do this is you have a short
DSL in the job definition whose sole purpose is to call SCM step to get
the code checked out, then load the real DSL script from the checked out
copy.
It's akin to define a shell script build step that just says "./build.sh"
I think a better way to do this is to use the FlowDefinition extension
point and come up with an implementation that asks the user to configure
an SCM through GUI just like you do in a freestyle project.
Then the said FlowDefinition could load DSL script from the checked out
source tree and proceed like normal.
There's also a separate task to investigate integration with the
branch-api plugin, which could end up looking similar.
On 06/04/2014 07:25 AM, Nicolas De Loof wrote:
Hi KK,
I wonder the workflow DSL could be used to implement a travis-like
approach, storing the DSL script in SCM and getting jenkins just know
about the SCM.
wdyt ?
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
