-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Run .NET Standard tests in CI #2353
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
@dotnet-bot test ci please |
yes, we will have 2, and those are not the names... this is a meta PR, I'm testing changes to Jenkins at the same time, so it looks weird. Please do not merge yet as I'm playing with Jenkins still |
No probs, you're assigned to this so you can merge when you're happy with it |
BTW, now the new builds kicked off. Those are the final names:
|
LOL, I assigned myself because I needed to manually tweak things in Jenkins to make sure it runs correctly. That's done and it works well. It's ready to merge. There is currently a BVT failing in vNext... I think it makes sense to fix that one first and then merge, otherwise people will start to see that the new build in their PRs fail, and assume they broke it. |
Yes, as I mentioned there is some weirdness because this is a meta PR that affects how PRs would build. We will have only 2 builds later |
Create an additional build in Jenkins to run .NET Standard tests
Added scripts to run vNext tests from command line
Created an additional build in Jenkins to run .NET Standard tests