[
https://issues.jboss.org/browse/JBIDE-13308?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-13308:
------------------------------------
Just be aware that by unlinking jobs, the Build Pipeline plugin is no longer a useful
option for us. Without upstream/downstream jobs, there's no pipeline. (The
upstream/downstream columns in our views will also become useless.
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/por...
I would argue that we still want:
{quote}
change to (parent) --> triggers rebuild of target platforms
change to central/maven/examples --> triggers JBT aggregate
change to JBT target platform --> triggers matching JBDS target platform
change to (JBT aggregate or JBDS target platform) --> triggers JBDS
change to (Base or Server) --> triggers JBT webtools aggregate
change to JBT aggregate --> triggers JBT coretests aggregate
{quote}
Remove cascading
----------------
Key: JBIDE-13308
URL:
https://issues.jboss.org/browse/JBIDE-13308
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.1.0.Alpha1
Unlink job by disabling cascading/blocked by upstream. That will make us able to het
faster feedback and consume/depend on less Jenkins resources.
--
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