[
https://issues.jboss.org/browse/JBIDE-10437?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-10437:
----------------------------------------
Why schedule a build if the component is inactive?
Scheduling ensures the API compatibility with latest build of its dependencies.
And why 3 days, if it's that slow? Why not weekly?
I'd be OK with weekly. We'll just need to adapt that to the requirements of devs
and the frequency of API change.
As to API changes that break downstream, it happens. Especially in
these stacks: common/tests, jsf/vpe/jst, maven/seam/hibernate.
Sure, but how often? Is it so often that we need to build stacks to valdate it on each
commit? I think a 1-week-max (scheduled build for each component) delay is ok. The only
use-case is like "VPE is built, common as an API change that will prevent VPE to
work, I want to know it". Is it necessary to have this feedback
"immediatly" (immediate meaning several hours when Hudson is busy) ?
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