generated from dotnet/new-repo
-
Notifications
You must be signed in to change notification settings - Fork 18
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Migrate from SignClient to
sign
tool and specify SDK in global.json (…
…#43) Fixes #42 Switch to the newer dotnet/sign CLI tool. As part of the switch I refactored the YAML file slightly: 1. Add a minimum SDK version in global.json. This helps prevent "works on my machine" issues by ensuring that CI is running a reasonable SDK version. I'm open to suggestions on the rollforward strategy; currently being as permissive as possible 2. Switch the YAML from using a deployment to a regular job; deployments aren't used very commonly and behave a bit differently (i.e. don't clone, automatically download all artifacts, etc.) so using a regular job to be "less magical" 3. Rather than install the sign tool in the CI pipeline, I add it as a dotnet tool; this makes it easier to discover / upgrade versions since that tool is stored with the others
- Loading branch information
1 parent
77837a3
commit 97f3184
Showing
5 changed files
with
52 additions
and
50 deletions.
There are no files selected for viewing
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
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
This file was deleted.
Oops, something went wrong.
Empty file.
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