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

SDK PR Validation CI and Signed Build CI should use same OS's #885

Closed
TheRealPiotrP opened this issue Feb 17, 2017 · 3 comments
Closed

SDK PR Validation CI and Signed Build CI should use same OS's #885

TheRealPiotrP opened this issue Feb 17, 2017 · 3 comments
Labels
Milestone

Comments

@TheRealPiotrP
Copy link
Contributor

Now that we have RID-specific tests it's important to have RID consistency across both sets of CI's. Otherwise, PR's which are green on the front-end CI may still cause build failures on the back-end CI. This affected #696

@dsplaisted
Copy link
Member

Is this still an issue? Do front-end and back-end refer to Jenkins and VSO, or to the SDK and CLI repo, or what?

@dsplaisted dsplaisted added this to the Unknown milestone May 16, 2017
mmitche pushed a commit to mmitche/sdk that referenced this issue Jun 5, 2020
…819.12 (dotnet#885)

- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19419.12
Copy link
Contributor

Due to lack of recent activity, this issue has been labeled as 'stale'. It will be closed if no further activity occurs within 30 more days. Any new comment will remove the label.

@github-actions github-actions bot added the stale label Apr 25, 2024
Copy link
Contributor

This issue will now be closed since it has been labeled 'stale' without activity for 30 days.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants