Skip to content
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

[Azure Pipelines] Differentiate manual triggers for Edge Dev/Canary #18445

Merged
merged 2 commits into from Aug 16, 2019

Conversation

@foolip
Copy link
Member

foolip commented Aug 15, 2019

As it is, it's only possible to run both of them:
#17342 (comment)

As it is, it's only possible to run both of them:
#17342 (comment)
@wpt-pr-bot wpt-pr-bot added the infra label Aug 15, 2019
@wpt-pr-bot wpt-pr-bot requested a review from jgraham Aug 15, 2019
@foolip foolip requested review from mustjab and thejohnjansen and removed request for jgraham Aug 15, 2019
@thejohnjansen
Copy link
Contributor

thejohnjansen commented Aug 15, 2019

This implies a subsequent change to add "Dev" and then "Stable" I presume?

@wpt-pr-bot wpt-pr-bot requested a review from jgraham Aug 15, 2019
@foolip
Copy link
Member Author

foolip commented Aug 15, 2019

Yeah, when Edge stable is added, I'd suggest adding -dev/_dev to the Edge Dev configuration. I could do that now though, if you prefer.

@thejohnjansen
Copy link
Contributor

thejohnjansen commented Aug 15, 2019

It would be awesome if you could add that now for dev just so we continue running both. We will add stable when that time comes.

…Canary

This also renames the Edge Dev job and artifacts so that Edge stable can
later be added without further renaming.
@foolip
Copy link
Member Author

foolip commented Aug 16, 2019

They would both have kept running every 6 hours per the eq(variables['Build.Reason'], 'Schedule') part of the condition, but I've now renamed the Edge Dev job and artifacts so that Edge stable can later be added without further renaming.

@foolip foolip merged commit c1e8936 into master Aug 16, 2019
12 checks passed
12 checks passed
website-build-and-publish
Details
manifest-build-and-tag
Details
update-pr-preview
Details
Azure Pipelines Build #20190816.36 succeeded
Details
Azure Pipelines (./wpt test-jobs) ./wpt test-jobs succeeded
Details
Azure Pipelines (affected tests without changes: Safari Technology Preview) affected tests without changes: Safari Technology Preview succeeded
Details
Azure Pipelines (affected tests: Safari Technology Preview) affected tests: Safari Technology Preview succeeded
Details
Azure Pipelines (wpt.fyi hook: safari-preview-affected-tests) wpt.fyi hook: safari-preview-affected-tests succeeded
Details
Azure Pipelines (wpt.fyi hook: safari-preview-affected-tests-without-changes) wpt.fyi hook: safari-preview-affected-tests-without-changes succeeded
Details
Taskcluster (pull_request) TaskGroup: success
Details
staging.wpt.fyi - safari[experimental] Safari results
Details
wpt.fyi - safari[experimental] Safari results
Details
@foolip foolip deleted the foolip/azure-manual-edge-canary branch Aug 16, 2019
natechapin added a commit to natechapin/wpt that referenced this pull request Aug 23, 2019
…eb-platform-tests#18445)

As it is, it's only possible to run both of them:
web-platform-tests#17342 (comment)

This also renames the Edge Dev job and artifacts so that Edge stable can
later be added without further renaming.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.