reading DSL script from file for BUILD FLOW PLUGIN

[Muhammad Faizan-Ul-Haq]

Hi,

I have started using BUILD FLOW PLUGIN for job orchestration. 

Now the DSL in my job configuration has become quite lengthy and it is becoming difficult to maintain it there.

I want to move it to my repository (SVN) and read it from file. 

I understood that it is possible to read it form file but I am missing the syntax ?

What should be the file extension and how to invoke it.

any help would be appreciated and sorry for posting such a naive question.

Faizan

[Baptiste Mathus]

Build flow is on the way to deprecation. The workflow plugin is the one to use. It's standard with this one to use a scm URL for your workflow declaration (through combobox+textfield for your scm url and you're done).

Cheers

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ed6dc25c-b90b-4ae5-bcaf-e00743998c07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Slide]

I'm actually pretty sad about this, the build flow plugin is pretty simple to use, especially for orchestrating multiple jobs which I don't want to pull into a single job.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS69_8kMndkebHt_TyN3VPDeaD4O4t6_0KvMQ0-W8-zPVw%40mail.gmail.com.

[Baptiste Mathus]

Why would you be sad? I know more the workflow plugin than the build flow, but seems to me you should be able to do the same things as easily with the workflow plugin, but it's just designed to be able to do much much more. With the workflow plugin you can also trigger another build.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVcO8u%2ByG-hThcCKPUK1FxGfWkkwBxQyR%2B_eh%2B-ONnFRAQ%40mail.gmail.com.

[Ginga, Dick]

I know that this thread is wandering but I too and a little worried about the Build Flow plugin being replaced. I hope that I can just drop my Build Flow statements into a workflow step and they will run unaltered.  

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS5oqpZrep9z000Co_yUJoxC0N_Bt2jkdvR1nvf7Sn5b9Q%40mail.gmail.com.

[Les Mikesell]

On Thu, Feb 12, 2015 at 6:35 AM, Baptiste Mathus <m...@batmat.net> wrote:
> Why would you be sad? I know more the workflow plugin than the build flow,
> but seems to me you should be able to do the same things as easily with the
> workflow plugin, but it's just designed to be able to do much much more.
> With the workflow plugin you can also trigger another build.

With workflow, if you trigger another build, how do you access that
other build object? For example to find the build number so you can
copy its artifacts into the workflow job. Or find the SVN_REVISION
so you can trigger other builds of that same revision?

--
Les Mikesell
lesmi...@gmail.com

[Muhammad Faizan-Ul-Haq]

Ahan,

I am going to look into workflow plugin after upgrading my jenkins to latest version

Thanks for answering guys.

Regards,

[Jesse Glick]

On Thursday, February 12, 2015 at 10:43:28 AM UTC-5, LesMikesell wrote:

With workflow, if you trigger another build, how do you access that
other build object?  For example to find the build number so you can
copy its artifacts into the workflow job.    Or find the SVN_REVISION
so you can trigger other builds of that same revision?

This area is still relatively weak in Workflow, so I plan to add more features here.

https://issues.jenkins-ci.org/browse/JENKINS-26100

https://issues.jenkins-ci.org/browse/JENKINS-25851

[Les Mikesell]

Is there some reason workflow isn't just a superset of build flow,
adding control of workspaces and inlining? What's the point of
having open source if everyone starts over from scratch whenever they
have a new idea anyway? Or, why aren't both of these just class
libraries for the groovy plugin with an easy way to add new ones for
common high-level operations?

--
Les Mikesell
lesmi...@gmail.com

[Baptiste Mathus]

2015-02-26 17:09 GMT+01:00 Les Mikesell <lesmi...@gmail.com>:

On Thu, Feb 26, 2015 at 8:41 AM, Jesse Glick <jgl...@cloudbees.com> wrote:
> On Thursday, February 12, 2015 at 10:43:28 AM UTC-5, LesMikesell wrote:
>>
>> With workflow, if you trigger another build, how do you access that
>> other build object?  For example to find the build number so you can
>> copy its artifacts into the workflow job.    Or find the SVN_REVISION
>> so you can trigger other builds of that same revision?
>
>
> This area is still relatively weak in Workflow, so I plan to add more
> features here.
>
> https://issues.jenkins-ci.org/browse/JENKINS-26100
> https://issues.jenkins-ci.org/browse/JENKINS-25851
>

Is there some reason workflow isn't just a superset of build flow,

The explanation you ask for has already been given here and there on the ML.

IIRC, Build flow plugin has been deemed a dead-end by its creator (Nicolas De Loof, IIRC). That always happens in our field.

But that experience has somehow also served as another feedback to create a far broader-scoped plugin.

 

adding control of workspaces and inlining?   What's the point of
having open source if everyone starts over from scratch whenever they
have a new idea anyway?   Or, why aren't both of these just class
libraries for the groovy plugin with an easy way to add new ones for
common high-level operations?

Many reasons already given I guess (suspendable, etc.)

[Jesse Glick]

On Thursday, February 26, 2015 at 2:55:17 PM UTC-5, Baptiste Mathus wrote:

why aren't both of these just class
libraries for the groovy plugin with an easy way to add new ones for
common high-level operations?

Many reasons already given I guess (suspendable, etc.)

Right, the requirement for durability alone totally precluded use of any Build Flow code.