Hello,
We have Continua CI free server(Version: 1.5.1.23) at our project. Each build configuration has it dropdown list with build priority, but they are not working at all, not in the all projects scope, neither in single project scope. Builds just running in the same sequence it was queued. For example: During some configuration building I have queued 3 more builds before this config finished, in next sequence: Low priority, Normal and High. After current configuration was built these queued 3 builds executes in the same order(Low, Normal, High). If they was queued in vice versa order(High, Normal, Low) they also completes in this order(High, Normal, Low)
Is this known issue? If yes, was it fixed in latest release? Or I just missed something to configure?
OS: Windows Server 2012 Datacenter
Attached Continua CI about page info
Please let me know if you need more details.
Thanks,
Vova
Hi Vova,
Thank you for reporting this issue.
Currently the build priority is only taken into account up until the point where a build is waiting for an agent or license to run a stage. After that point each build runs in the order that it detects that an agent or license is available.
As you are running the free version which only allows one concurrent build, it is very likely that multiple builds will end up waiting for a license. The build priority therefore does not really work at all in your case.
We are planning to rework our build queue design so that build priority in taken into account in all places where the build is waiting. This is however a significant task and we cannot provide a timescale at the moment for when this will be completed.
Hi Dave,
Would purchasing a licence help us to improve this priority issue somehow?
Thanks,
Vova
Hi Vova,
It would improve it to a certain extent, but it depends on your scenario. If there are multiple builds waiting for the repository to be checked and added to the cache then the highest priority build will move on to start a stage first if one is available.
We admit that the current build priority implementation is not very useful and we will get on to fixing it eventually.
Can I ask what your use case is? Are you just trying to get one build to run quicker while other builds are still queuing or are you hoping to achieve something else?
Hi Dave,
We have approximately 18 unit test configs in 3 projects. 3 another configs triggers them to build on repository changes submit, triggers starts them all with low priority and they slowly are built one-by-one, another just waiting with “Stage Awaiting Agent” status(or “Stage Awaiting License” that should disappear after licensing and change to “Stage Awaiting Agent” as I assume, yes?). When someone triggers another build in 4-th project manually with high priority - it just waiting to be built after all the pending “Stage Awaiting Agent” builds. As workaround we currently just stopping automatically triggered unit tests and queue build that we need.
May licensing improve somehow this process?
Thanks,
Vova
Hi Vova,
Having licences will means that you can run more than one build concurrently. Providing the number of builds that start at the same time is less than the number of licences, this will mean that the builds will skip the “Stage awaiting agent” status altogether and run immediately after the repository has been checked and the repository cahce updated.
Hi Dave,
Thanks for the answer.
Haven’t noticed feature of agent’s concurrent stages, probably we will buy the license.
Thanks for help again,
Vova