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.

Sign up for GitHub

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

Jump to bottom

Need to update Full framework CI machines with new NuGet #1327

Closed
livarcocc opened this issue Jun 9, 2017 · 3 comments
Closed

Need to update Full framework CI machines with new NuGet #1327

livarcocc opened this issue Jun 9, 2017 · 3 comments
Milestone
3.0.1xx

Comments

@livarcocc
Copy link
Contributor

We need the new NuGet in the full framework boxes to be able to test ATF, NuGet Config Properties and Warning As Errors in the Full framework CI legs.
@livarcocc livarcocc modified the milestone: 2.1.0 Jun 15, 2017
johnbeisner added a commit to johnbeisner/sdk that referenced this issue Sep 11, 2017
@johnbeisner
Resolving: dotnet#1327
de14e01
@johnbeisner johnbeisner mentioned this issue Sep 11, 2017
Merged
@johnbeisner johnbeisner reopened this Sep 11, 2017
@johnbeisner johnbeisner self-assigned this Sep 11, 2017
johnbeisner added a commit to johnbeisner/sdk that referenced this issue Sep 11, 2017
@johnbeisner
Backing out change for dotnet#1327 due to Jenkins failures
a452ea5
johnbeisner added a commit that referenced this issue Sep 12, 2017
@johnbeisner
Adding the OptIn test matrix for NuGet references (#1578)
8127c13 
* Adding the OptIn test matrix for NuGet references - #1066

* Resolving: #1327

* Put the constructor back...

* Backing out change for #1327 due to Jenkins failures
johnbeisner pushed a commit to johnbeisner/sdk that referenced this issue Oct 17, 2017
Resolving: dotnet#1327
ec1e5f4
@johnbeisner johnbeisner mentioned this issue Jan 4, 2018
Merged
@livarcocc livarcocc modified the milestones: 2.1.3xx, 2.1.4xx Mar 30, 2018
@livarcocc
Copy link
Contributor Author

I believe there is a chance that this has also been done already. @johnbeisner please double check and close if appropriate.

johnbeisner pushed a commit to johnbeisner/sdk that referenced this issue Apr 18, 2018
Resolving dotnet#1327
b8968f4
@johnbeisner johnbeisner mentioned this issue Apr 18, 2018
Closed
@tannergooding
Copy link
Member

@johnbeisner can this be closed, or is it still pending?

@johnbeisner
Copy link
Contributor

@tannergooding
The PR failed to resolve the test errors - although it appeared that the errors were now of a 'violation of max path' type.

@livarcocc livarcocc modified the milestones: 2.1.4xx, 2.2.1xx Jun 27, 2018
johnbeisner pushed a commit to johnbeisner/sdk that referenced this issue Aug 6, 2018
Resolving: dotnet#1327
76faf46
@johnbeisner johnbeisner mentioned this issue Aug 6, 2018
Closed
@livarcocc livarcocc modified the milestones: 2.2.1xx, 3.0.1xx Jun 12, 2019
@johnbeisner johnbeisner removed their assignment Dec 23, 2019
GangWang01 pushed a commit to GangWang01/sdk that referenced this issue Jun 7, 2022
@seancpeters
Merge pull request dotnet#1327 from dotnet/rel/2.1.0-preview1
8aaa9c1 
Merge 2.1.0 into master
GangWang01 pushed a commit to GangWang01/sdk that referenced this issue Jun 27, 2022
@seancpeters
Merge pull request dotnet#1327 from dotnet/rel/2.1.0-preview1
9a68e09 
Merge 2.1.0 into master
GangWang01 pushed a commit to GangWang01/sdk that referenced this issue Jul 11, 2022
@seancpeters
Merge pull request dotnet#1327 from dotnet/rel/2.1.0-preview1
9ed5d5c 
Merge 2.1.0 into master
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
3.0.1xx
Development

No branches or pull requests
4 participants
@livarcocc @tannergooding @marcpopMSFT @johnbeisner