[jbosstools-issues] [JBoss JIRA] (JBIDE-10437) redo swimlanes / intrabuild linkages using new Jenkins plugins: Join, Parameterized Trigger, Up/Down Column

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682361#comment-12682361 ] 

Nick Boldt commented on JBIDE-10437:
------------------------------------

6hrs is far from ideal, I agree, but we have limited resources.

> How often are project affected by updatream change. Do we want "immediate" trigger in that case? These triggers introduce a lot of new builds which have the same results, This builds are part of what make Hudson so slow.

Why wouldn't you want to react immediately when upstream changes? If common or tests change, it could affect the whole stack. The builds won't have the same results if the upstream API changes. That's the whole point of this type of integration testing by virtue of respinning to verify compilation and tests still work. Often, it does not and we catch problems. (Which, admittedly, would be caught if more devs ran builds locally.)

What about immediate (~every 5 minutes) check of SVN to trigger jobs + 1 fixed time scheduled job daily, and no upstream triggering. So we have a 5 min + build time feedback loop for commit, and we have daily check for dependencies being compatible between them and with the code in SVN.
This would create daily: As many builds as checkins (actually less, because checkins that happen during a running build create a single next build + As many builds as components.
Daily, it would be about ~20 builds consequence of commits + ~20 builds consequence of scheduling.

That's too many builds. We'd be monopolizing the whole cluster. 20 builds a day x 40 jobs = 800. We don't have enough hours in the day, or slaves, to accomodate that. If we want more builds per day, we need to look at solving JBIDE-11155 first, or splitting compilation and testing into separate jobs.
                
> 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