I want to thank everyone for their input. At this time we have decided to
pursue the workflow plug-in and its "load" step as the best way forward.
Given that we are dealing with trying to configure complex build flows,
the workflow plugins other features should prove useful well beyond the
sc
On Tuesday, December 2, 2014, Kenneth Baltrinic
wrote:
> Gentlemen,
>
> Thank you all for your responses. Here are my thoughts on the combination
> of replies.
>
> The literate build plugin is closest in concept to what we are looking for
> but it seems too limited in capabilities for what we ne
Maybe check out the YAML Project Plugin? It should be available on the
experimental update center.
On 02.12.2014, at 19:13, Kenneth Baltrinic wrote:
> Gentlemen,
>
> Thank you all for your responses. Here are my thoughts on the combination of
> replies.
>
> The literate build plugin is cl
Gentlemen,
Thank you all for your responses. Here are my thoughts on the combination
of replies.
The literate build plugin is closest in concept to what we are looking for
but it seems too limited in capabilities for what we need. If it could
handle a full DSL such as the JobDSL, BuildFlow
> We have a working prototype right now that manages this with two
separate jobs. One to watch the SMC and rebuild the downstream job
based on the build.yml and a separate downstream job that kicks off when
the first completes successfully. (Given the first might fail if the
yaml files is invalid
Your effort might be best placed helping us beef up the (stub) travis.yaml
parser to one that is more useable.
On Tuesday, December 2, 2014, James Nord wrote:
> Hi
>
> What you are attempting sounds like the litterate job type - have you
> looked at this plugin?
>
> /James
>
>
>
> On 2 December
Hi
What you are attempting sounds like the litterate job type - have you looked at
this plugin?
/James
On 2 December 2014 13:31:19 GMT+00:00, Kenneth Baltrinic
wrote:
>I have been tasked to look at how we can set up a self service CI
>system
>for a large development shop, much along the l
I have been tasked to look at how we can set up a self service CI system
for a large development shop, much along the lines of how travis CI works.
There are big differences between what we need and what Travis CI provides
but the basic idea of having a yaml file within the repository itself
s
