Create runtime staging clone to manually kick off full test runs

[steveisok]

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-manual will do the trick

[ghost]

Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

---

null

Author:	steveisok
Assignees:	-
Labels:	area-Infrastructure-libraries
Milestone:	-

[safern]

/azp run manual-runtime-staging

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[steveisok]

/azp run manual-runtime-staging

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[steveisok]

/azp run manual-runtime-staging

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[steveisok]

/azp run manual-runtime-staging

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[steveisok]

/azp run manual-runtime-staging

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines failed to run 1 pipeline(s).

[steveisok]

@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.

- ${{ if not(eq(variables['Build.DefinitionName'], 'runtime-staging-manual')) }}:
  schedules:
    - cron: "0 7,19 * * *" # run at 7:00 and 19:00 (UTC) which is 23:00 and 11:00 (PST).
      displayName: Runtime-staging default schedule
      branches:
        include:
        - main
      always: false # run only if there were changes since the last successful scheduled run.

[akoeplinger]

/azp run runtime-staging-manual

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[safern]

now that we have a template, maybe we can use parameters to turn on/off legs rather than checking based on pipeline name?

[radical]

Like platform!

[akoeplinger]

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.

[safern]

That one also has a schedule trigger, so it will limit us as well and we will need the template anyway?

[steveisok]

I think this is a good first step. I think we can get more custom in a follow up PR.