-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run libraries package testing on build agent #53905
Conversation
instead of on Helix as with recent changes the entire package testing doesn't take more than 2 minutes. Helix created a work item per package test even though it only took seconds and the average wait time for a client was 10-15min. Also cleaning up how the generated package test projects are restored and incorporating a fix from Eric St John to not hard code the package feeds.
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue Detailsinstead of on Helix as with recent changes the entire package testing Also cleaning up how the generated package test projects are restored Superseding #53837
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great! Thanks for working on this, with the current improvements I agree that it no longer makes sense to use helix for this.
Let's cleanup helix-queues-setup
as well and remove instances of allConfigurations
there:
runtime/eng/pipelines/libraries/helix-queues-setup.yml
Lines 155 to 157 in 3ead4ac
# AllConfigurations | |
- ${{ if eq(parameters.jobParameters.framework, 'allConfigurations') }}: | |
- Windows.10.Amd64.Server19H1.Open |
- ${{ if notIn(parameters.jobParameters.framework, 'allConfigurations', 'net48') }}: |
- ${{ if notIn(parameters.jobParameters.framework, 'allConfigurations', 'net48') }}: |
It seems like you need to adjust the build command for the all configurations leg? I don't see the tests running on the build log. |
Wooosh, finally it's working but I still need an approval :)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thank you for improving this! Love to see a 20 min all configurations build.
Kudos to @ericstj who contributed a great deal to achieving that goal. |
I feel like our CI build times are out of control. Waiting more than two hours for libraries tests (normal, non-mobile) to complete isn't great... |
Failures are:
|
instead of on Helix as with recent changes the entire package testing
doesn't take more than 2 minutes. Helix created a work item per package
test even though it only took seconds and the average wait time for
a client was 10-15min. This should save some machine cycles as we don't
depend on Helix clients anymore.
Also cleaning up how the generated package test projects are restored
and incorporating a fix from Eric St John to not hard code the package
feeds.
Superseding #53837