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

Adding a new CI leg for netframework #2018

Merged
merged 4 commits into from
Jan 10, 2019
Merged

Adding a new CI leg for netframework #2018

merged 4 commits into from
Jan 10, 2019

Conversation

Anipik
Copy link
Contributor

@Anipik Anipik commented Jan 4, 2019

Fixes #1933
We are currently not running or building our tests on netframework.
However we are going to support netframework when we release 1.0 , so just adding a new ci leg to consistently build and test stuff on netframework

@artidoro
Copy link
Contributor

artidoro commented Jan 4, 2019

Since you are working on this could you order the CI legs alphabetically?

build/ci/phase-template.yml Outdated Show resolved Hide resolved
test/Directory.Build.props Outdated Show resolved Hide resolved
@Anipik Anipik changed the title Adding a new CI leg for netframework [WIP] Adding a new CI leg for netframework Jan 8, 2019
config.json Outdated Show resolved Hide resolved
config.json Outdated Show resolved Hide resolved
Directory.Build.props Outdated Show resolved Hide resolved
test/Directory.Build.props Outdated Show resolved Hide resolved
@Anipik Anipik changed the title [WIP] Adding a new CI leg for netframework Adding a new CI leg for netframework Jan 10, 2019
config.json Show resolved Hide resolved
test/Directory.Build.props Outdated Show resolved Hide resolved
.vsts-dotnet-ci.yml Outdated Show resolved Hide resolved
Copy link
Member

@safern safern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather than 2 comments, LGTM.

This looks way better and it also enables people building for netfx from VS. Did you test that choosing that configuration worked fine? Intellisense and all the VS features?

Co-Authored-By: Anipik <anirudhagnihotry098@gmail.com>
Copy link
Member

@safern safern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're building the netfx matrix against netcoreapp2.1

.vsts-dotnet-ci.yml Outdated Show resolved Hide resolved
.vsts-dotnet-ci.yml Outdated Show resolved Hide resolved
@Anipik
Copy link
Contributor Author

Anipik commented Jan 10, 2019

This looks way better and it also enables people building for netfx from VS. Did you test that choosing that configuration worked fine? Intellisense and all the VS features?

The build from VS is working fine. the test explorer is giving some trouble. I will try to give it another try. (could be becuase of my VS as VS2019 is not working smoothly for me)

Copy link
Member

@safern safern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Copy link
Member

@eerhardt eerhardt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@Anipik
Copy link
Contributor Author

Anipik commented Jan 10, 2019

Thanks to @safern and @eerhardt for both feedback and help

@Anipik Anipik merged commit 64b60d2 into dotnet:master Jan 10, 2019
@Anipik Anipik deleted the netfxCi branch January 10, 2019 17:33
@shauheen
Copy link
Contributor

#2104 #2106 need to be addressed.

@ghost ghost locked as resolved and limited conversation to collaborators Mar 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants