Hi,
today we updated to 1.8.1.108 in order to fix the ‘npm install’ bug. It now appears that something affected the operation of our build triggers and most of them seem to work incorrectly. When a build is triggered by a repository source change, a build is queued but stays in ‘build initializing’ state indefinitely.
Manually triggering builds seems to work fine and the build immediately moves further (e.g. initializing agent, executing, etc.)
Since this affects almost all our CI builds this kind a become a showstopper. Hope you can help us out here.
(Btw, I noticed all source code triggers have changed to quiet period 1min, as far I can remember that has always been 0 by default, or am I wrong?)
Kind regards,
Remko Seelig
Hi Remko,
Thank you for reporting this. We are working on a fix and will get a new version out soon.
Fix confirmed as of 1.8.1.112. Thank you very much for your quick response and hotfix release!
Regards,
Remko Seelig