-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Create runtime staging clone to manually kick off full test runs #61443
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
Conversation
|
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue Detailsnull
|
|
/azp run manual-runtime-staging |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run manual-runtime-staging |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Co-authored-by: Santiago Fernandez Madero <[email protected]>
|
/azp run manual-runtime-staging |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…g' into stpfiste/manual-runtime-staging
c97977a to
3ebaa8c
Compare
|
/azp run manual-runtime-staging |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run manual-runtime-staging |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-staging-manual |
|
Azure Pipelines failed to run 1 pipeline(s). |
71b05ee to
5267f76
Compare
5267f76 to
44e7023
Compare
|
@safern @akoeplinger conditioning the schedule based on pipeline name doesn't seem to work. Any suggestions? I think this might be where we actually need a separate yml. |
f13eacb to
10b3299
Compare
10b3299 to
b497b31
Compare
|
/azp run runtime-staging-manual |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| trigger: none | ||
|
|
||
| extends: | ||
| template: runtime-staging-template.yml |
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.
now that we have a template, maybe we can use parameters to turn on/off legs rather than checking based on pipeline name?
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.
Like platform!
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.
that works for runtime-staging but we still have runtime.yml, so I'd need to move that to template as well which I'm not sure is desired.
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.
That one also has a schedule trigger, so it will limit us as well and we will need the template anyway?
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.
I think this is a good first step. I think we can get more custom in a follow up PR.
This change allows devs to manually kick off full test runs on the configurations that only execute smoke tests per PR.
/azp run runtime-staging-manualwill do the trick