* add publish task
* move template out of steps and into jobs
* get rid of pool
* dont pass 1es pool
* add depends on chain
* use vsce latest
* run package on publi
* add approval step:
* vsixs are stored in the root, so don't check in the extension folder
* Switch to MI instead of a PAT
* Fix ps1 issue
* Only deploy on internal
* Use pool vs vmimage
* Try to fix pool condition
* Use a different pool
* Condition the name of the build based on OS
Why is windows the bomb emoji and not the windows emoji?
And why did I do this:
The windows build goes last because its in alphabetical order based on the behavior of how devops works. This is bad because it should go first and makes the other steps take longer as they depend on only the windows task. The bomb emoji is one of the first emojis thats not an emoticon before the penguin emoji so I picked that one..
* It's pretty silly you cant define a variable in a template but here we are
* Maybe it has to be in plaintext
* The deployment step is not necessary
* wait for wait job
* Set the emoji
* Move windows to the top
* Set 'use 1es pool' to true
* Switch to a different ordering so windows runs first, then linux
* try to fix bug where version is not passed and publish args is wrong
* Try to pass var into another job since we cant have a template in the jobs
* Revert "Try to pass var into another job since we cant have a template in the jobs"
This reverts commit 7bdf2dfec9.
* Try to condition the yamls omewhere else
* is yaml failing
* Revert "is yaml failing"
This reverts commit b014dd042f.
* Revert "Try to condition the yamls omewhere else"
This reverts commit 7ccb36f01c.
* Revert "try to fix bug where version is not passed and publish args is wrong"
This reverts commit 592349be71.
* Get version again
We cant return a value from a template
We cant make a template callable with jobs in another job
We cant pass a variable from one job to another if its a job in a job
We cant do so many things in yaml
* yaml indentation
* Don't skip checking out the repo, we kinda need that to get the version
* move signing prep into another template so we can not push microbuild to staging directory
* condition the signing prep
* fix the cond since yaml has dumbest syntax ever
* fix whitespace i hate yaml
* remove junk:
* succeded doesnt work
* Add fake MSBuild project to allow signing VSIX and JS
* Sign JS
* Add step to pipeline
* Restrict signing package version
* Add scripts to install signing tool locally
* only go up 1 directory
* fix display name
* fix whitespace -__-
* add build step for installing microbuild
* add sign type parameter
* dont produce alpha package in official drop
* add sign type parameter to default pipeline
* dont publish package in another directory as this causes other issues, instead copy the artifact
* acknowledge the existence of a document explaining the release and other maintenance processes
this information is more suited for internal repo changes.
* change internal stream to a different signing stream
* add dotnet public for notargets sdk
* reduce to 1 feed
* use a different feed
* Use dotnet team
* use explicit feed source
* add feed auth
* fix comment
* rename unsigned vsix so both can get dropped
* use the other type of slash for REN -__-
* try to fix path
* add packages folder with empty gitignore
* figure out dir
* fix rename command
* Fix rename
the 'unsigned' one is actually the signed one
* Fix JS File Sign
dist is at the root of each but this runs in a segregated folder
* produce binlogs and try to fix the path
* Publish SDK Extension Logs
* fix signing
* remove bad slash in path that gets parsed incorrectly
* remove \
* fix microbuild to be installed b5 js signing
* update gitignore
* fix gitignore again
* [REVERT THIS] Add a file A.ts to see if files are signed alphabetical or only non minified JS is signed
* [REVERT THIS] Add content to js to see if minify changes signing
* sign js after webpack
maybe we can sign it after the bundle is created and it will still be able to edit the bundle vsix internals? I thought not but perhaps extension.js is getting replaced by the webpack, so lets see if this works.
* Revert "[REVERT THIS] Add content to js to see if minify changes signing"
This reverts commit ecacc6830b.
* Revert "[REVERT THIS] Add a file A.ts to see if files are signed alphabetical or only non minified JS is signed"
This reverts commit 1ab6ea1873.
* Update name of incorrect task.
The migration tool and doc examples all use the unofficial one ecks dee
Also create a dupe of the PR pipeline so we can migrate main to that file once it is checked in and then delete the other one to rename it to a more descriptive name.