[ https://issues.jboss.org/browse/JBIDE-13307?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13307: ------------------------------------ AFAICT the Build Pipeline Plugin is simply a view -- it doesn't do anything in terms of sequencing or triggering builds. It just shows you how you have your jobs interconnected (via other plugins/job config), and which build #s were used within a given flow. I admit seeing which build # triggered which downstream build # is handy, but you can find that information other ways (admittedly w/ more clicks). So +1 for single-view usability. It also adds the option to block and wait for a manually triggered build, eg., if you wanted to script the workflow that every successful JBDS build would wait for user input before publishing to production server. That might be handy for pushing bits to QE via a job instead of a semi-manual workflow; OTOH, do we want builds being pushed to QE via a single button? or via a gatekeeper? +0 for this feature. ----- I'm also not convinced that we should be building all the source in a single operation (with tests!) because some jobs already take 4hrs+; combining them all into a single one could take >8hrs and could also be more failure prone due to memory overload or git checkout failure. If 1 build in 15 fails because of Jenkins snafu (memory, bandwidth, nfs, http://, git://), the other 15 might succeed and it's only a 30 min job that needs to be kicked again. If the ALL-IN-ONE-UBER-BUILD fails, you need to wait another 8hrs for a respin. Having lived through JBDS 4, I never want to be beholden to a process that takes so long and could potentially fail in so many time-wasting ways. So, -100 for the effort required to set this up, since it will duplicate what we'd have w/ the 15 component jobs, probably be more failure-prone, and produce something we wouldn't want to publish anyway. -- 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