Hi Igniters,


Most of us at least once have faced with situation that we have important
fix to be tested, but TeamCity is busy and queue is too long. Ignite 2.0
test introduction helped to reduce time to wait, but still there is
potential to get results for your PR tests faster.



Contribution itself is tested under PR and TC ‘Run All’ started manually.
Second test will be performed later: all test suites will be started for
after merge into master (ignite 2.0).



I offer to change VSC trigger to schedule trigger for master and 2.0
branches. Schedule trigger will be launched daily at period of low activity
(TC queue is empty), for example at 2am GMT.



This solution help to get results faster for each PR. Solution still
protects master from merge problems. If master tests are required due to
high risk, committer will be still able run start RunAll For master.



Any thoughts or comments? I would like apply this change by the end of next
week.



Sincerely,

Dmitriy Pavlov

Reply via email to