yes, by intention, as the real world CD scenario I've considered aren't
static and can involve various steps depending on runtime context

start a new pipeline is just about re-trigger the initial step (which I
expect to be a git push)
re-run a build could make sense, but then you can just enable retry plugin
on the adequate jobs
manual steps aren't considered by build flow plugin (but fully supported by
workflow)


2015-07-21 17:02 GMT+02:00 Christoph Kutzinski <[email protected]>:

> Am I right when saying the the buildgraphview-plugin is a king of 'after
> the fact' view of a pipeline run?
> *I.e. I can see the results of a pipeline afterwards, but I can not
> actively control a pipeline (lie in the Build Pipeline pluing):*
> *- starting a new pipeline run*
> *- re-running a build*
> *- triggering manul steps*
>
> *Gesendet:* Dienstag, 21. Juli 2015 um 14:45 Uhr
> *Von:* "nicolas de loof" <[email protected]>
> *An:* "[email protected]" <[email protected]
> >
> *Betreff:* Re: Re: Build Pipeline plugin and Build Flow plugin
>  build graph view do rely on upstreamCause so should handle most
> relations between builds
> and for the others (including build-flow) do offer an extension point to
> discover other relations
>
> 2015-07-21 16:44 GMT+02:00 Christoph Kutzinski <[email protected]>:
>>
>>   Thanks!
>> I didn't know about
>> https://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin
>>
>> Can I also define manual triggered steps in a setup of the Build-Flow
>> plugin and the build-graphview-plugin like you can do with the build
>> pipeline plugin?
>>
>> *Gesendet:* Dienstag, 21. Juli 2015 um 14:37 Uhr
>> *Von:* "nicolas de loof" <[email protected]>
>> *An:* "[email protected]" <
>> [email protected]>
>>
>> *Betreff:* Re: Build Pipeline plugin and Build Flow plugin
>>  build flow did introduce buildgraphview-plugin for this exact use case
>>
>>  build pipeline only can rendre static and mostly sequential pipelines
>>
>> 2015-07-21 16:19 GMT+02:00 Christoph Kutzinski <[email protected]>:
>>>
>>>  Hi,
>>>
>>> I'm trying to set up a CD pipeline with Jenkins where I can
>>>
>>> I) concisely define the relationship (triggers) between the single
>>> pipeline steps (jobs)
>>> II) have a nice visualisation of the full pipeline
>>>
>>> The Build Flow plugin is a good fit for I, while the Build Pipeline
>>> plugin is a nice fit for II.
>>> However, the Build Pipeline plugin doesn't seem to understand the job
>>> dependencies defined via the Build Flow plugin.
>>>
>>> Does someone have experiences with similar setups? What is your solution
>>> for this?
>>>
>>>
>>> cheers
>>> Christoph
>>>
>>>
>>>
>>> --
>>> 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 [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
>>> <https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> 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 [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> 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 [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41
>> <https://groups.google.com/d/msgid/jenkinsci-users/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41?utm_medium=email&utm_source=footer>.
>>
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzm6OBmC7pgunTgTjFX8qmdjAjQWxwaw-QHpsNbyoPRX4A%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzm6OBmC7pgunTgTjFX8qmdjAjQWxwaw-QHpsNbyoPRX4A%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/trinity-6e98f37c-ab18-4f08-9ac4-6db9b3071625-1437490941266%403capp-gmx-bs41
> <https://groups.google.com/d/msgid/jenkinsci-users/trinity-6e98f37c-ab18-4f08-9ac4-6db9b3071625-1437490941266%403capp-gmx-bs41?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzn9wHbwVQMAxA5y%2B%3D7GKn9vFfqqWB4PH27Atq7kFPhemQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to