[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
Wed Jan 30 12:28:51 EST 2013
[ https://issues.jboss.org/browse/JBIDE-12850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751438#comment-12751438 ]
Nick Boldt commented on JBIDE-12850:
------------------------------------
Decision is that Pipeline view is pretty but not that helpful when there's only a single Flow job in it.
So... to merge the usefulness of both Pipeline and Flow, suggest we create 5 new Flow jobs:
Base
\-> Forge|Freemarker|GWT (parallel)
\-> Server>(WS|OS) (server first, WS/OS in parallel)
\-> Hibernate>BIRT>Xulrunner>VPE>JST (series)
\-> JavaEE>Portlet>Central (series)
> 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