Igniters,

Currently we have a TeamCity trigger only on Run All aggregating project:
https://ci.ignite.apache.org/admin/editTriggers.html?id=buildType:IgniteTests24Java8_RunAll

Each change triggers it's own full run. If new changes are added while some
builds are queued,
these changes are not picked up, and a separate run is scheduled.

At this very moment I see over 600 queued builds, all on master branch from
some trigger.
Previously we had a trigger per-project, which seems to be more efficient.

Thoughts?

Pavel

Reply via email to