In a situation where the Cluster Manager is configured so that builds regularly are queued, waiting for the minAgents to be available, how is the build duration reported separate from the queue time?
Does the time given for the duration at the end of each build include the queue time or is that just the actual build duration from the time it got agents until it finished?
The wait time is reported in the Cluster Manager along with a Duration. Does the Duration reported include the wait time or is it separate?
The concern is that developers who are submitting builds only really care about the total build time, regardless of whether the build queued for some of that time or not. If the time reported at the end of the build is total time since it was launched, that's fine. If not, then how would developers know or find the total time that the build took. In this case, I don't think that developers regularly look at the CM Web UI. Is there another way that the total build is reported?
Answer by matthew kwong · Nov 02, 2012 at 08:15 PM
Answer by bfredrickson · Nov 05, 2012 at 06:39 PM
Electric Cloud powers Continuous Delivery, helping organizations developing deliver better software faster by automating and accelerating build, test, and deployment processes at scale. Industry leaders like Qualcomm, SpaceX, Cisco, GE, Gap, and E*TRADE use Electric Cloud solutions to boost DevOps productivity and Agile throughput.