[
https://issues.jboss.org/browse/JBIDE-10437?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-10437:
----------------------------------------
When someone's API changes, you'll break all the downstream
components.
It will always be the case. I'm more wondering how fast we want feedback on this.
Immediate feedback by cascading builds (what we have now) consume a lot of resources and
time; a longer feedback (no cascading, SVN poll every 5 minutes + weekly schedule of all
components) would make component build more reactive to changes inside component without
adding so much meaningless builds.
Also, as for static linkage of API, the continuous build already guarantees that.
redo swimlanes / intrabuild linkages using new Jenkins plugins: Join,
Parameterized Trigger, Up/Down Column
-----------------------------------------------------------------------------------------------------------
Key: JBIDE-10437
URL:
https://issues.jboss.org/browse/JBIDE-10437
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.Beta3
I asked that three new plugins be installed into JBoss Jenkins instance:
* Join ::
https://wiki.jenkins-ci.org/display/JENKINS/Join+Plugin
* Parameterized Trigger ::
http://wiki.hudson-ci.org/display/HUDSON/Parameterized+Trigger+Plugin
* Up/Down Column ::
http://wiki.hudson-ci.org/display/HUDSON/Upstream+Downstream+Column+Plugin
After next restart, they'll be there. So... time to play w/ them and see if we can
improve the workflow a little.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira