You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
[Build] Create 2nd Stage/Job for Smoke Tests #3560
I also thought we had discussed before, but could we split the smoke test part into a 2nd job/stage? That'd make the build report and publish to the PR feed as a separate check from the smoke test itself which could run after, eh?
Basically showing up as a third line, so in this last case, we'd have seen the build and the release to our feed succeed, but then the smoke test line (not here) fail?
All the work for the smoke tests are done, this should just be some YAML configuration for splitting the step out into it's own stage or something to get it to appear as a new line item after the build.
Also see for reference what PowerToys is planning to adopt from Terminal: microsoft/PowerToys#7162 (Edit: ah misunderstood this is for releases not pipelines, so probably not useful as we have a simpler release pipe.)
Activity
michael-hawker commentedon Nov 10, 2020
All the work for the smoke tests are done, this should just be some YAML configuration for splitting the step out into it's own stage or something to get it to appear as a new line item after the build.
michael-hawker commentedon Dec 4, 2020
Also see for reference what PowerToys is planning to adopt from Terminal: microsoft/PowerToys#7162 (Edit: ah misunderstood this is for releases not pipelines, so probably not useful as we have a simpler release pipe.)
Split out Unit Tests and Smoke Tests as separate Jobs in the Pipeline…
Split out Unit Tests and Smoke Tests as separate Jobs in the Pipeline…
Split out Smoke Tests and Unit Tests into a separate Jobs (#3617)