[jbosstools-issues] [JBoss JIRA] (JBIDE-12850) Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Fri Jan 25 15:12:47 EST 2013
[ https://issues.jboss.org/browse/JBIDE-12850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750643#comment-12750643 ]
Nick Boldt edited comment on JBIDE-12850 at 1/25/13 3:11 PM:
-------------------------------------------------------------
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk_Pipeline/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno_Pipeline/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk_Pipeline/job/jbosstools-4.1_trunk.buildflow/4/console
So, it looks like we can EITHER:
a) define a workflow that sets up the linkages between jobs in one place...
!buildflow.png!
... which makes the pipeline view rather useless, as it only contains a single entry:
!pipeline_buildflow.png!
or
b) continue to have jobs defined w/ upstream/downstream linkages, and then use the pipeline view:
!pipeline_40.png!
was (Author: nickboldt):
So, it looks like we can EITHER:
a) define a workflow that sets up the linkages between jobs in one place...
!buildflow.png!
... which makes the pipeline view rather useless, as it only contains a single entry:
!pipeline_buildflow.png!
or
b) continue to have jobs defined w/ upstream/downstream linkages, and then use the pipeline view:
!pipeline_40.png!
> Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-12850
> URL: https://issues.jboss.org/browse/JBIDE-12850
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Labels: f2f2012
> Fix For: 4.1.x
>
> Attachments: buildflow.png, pipeline_40.png, pipeline_buildflow.png
>
>
> In order to build the whole JBoss Tools in one click, we could try to use the https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin plugin to -orchestrate- display the whole build workflow, and the https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin plugin to orchestrate it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list