added method to update nuget via Azure DevOps #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[skip ci]
manuallly specifying vresion
trying to specify in a different spot
pulling license file into my own repo
test push to nuget.org
Removed github actions test, there seems to be a bug in the existing nuget build samples (link will be added to PR) Reverted CIS4Azure.Tests.Pester.nuspec to be more similar to existing one in mark repo. Updated schema version, added license, etc. This should be the initial version of the azure pipeline spec. Instructions on how to add to AzDO will be added to PR.
|
I added this to the issue comments, and it is showing a reference, but I'm not sure how we actually mark it ahead of time... |
markgar
approved these changes
Oct 29, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@markgar Slight deviation from standard semantic versioning... I think I mostly captured what you were thinking, but feel free to modify the yml pipeline (specifically this line: Version: '$(Major).$(Minor).$(Patch).$(Build)-preview') if you wanted it to be slightly different.
You should be able to get this to work as is by merging in and then configuring a new service connection to Nuget.org with an API Key. You will then need to modify line 39 of azure-pipelines-preview.yml to have the name of the service connection (publishFeedCredentials: 'nuget.org'). If you name it nuget.org, it should just straight up work.
I started looking at github actions for this, and I think it will be doable eventually, but there are currently some bugs that I would like to see worked out first. I've subscribed to this thread to keep my eye on it: NuGet/Home#8580 (comment)