Convert remaining packages which necessitate 1es-templates/esrp release #8460
Conversation
…osable yml. time to see how this thing performs
…e. I'm thinking the 1es templates cant quite hack it
scbedd
changed the title
scbedd
requested review from
a team,
MaryGao,
catalinaperalta,
maririos,
praveenkuttappan,
qiaozha,
raych1,
tadelesh and
weshaggard
as code owners
|
/check-enforcer override The |
weshaggard
left a comment
weshaggard
left a comment
There was a problem hiding this comment.
Looks reasonable assuming test pipelines work.
|
Ray recently deleted |
|
Will do so. Needed to get in here to make the SemVer changes anyway. |
…ument passed to the publish stage
|
My claim is that
Just going to merge this and then deal with the fallout. |
|
/check-enforcer overrde |
|
For help using check enforcer, see https://aka.ms/azsdk/checkenforcer Available commands:
If you are initializing a new service, follow the new service docs. If no Azure Pipelines are desired, run |
|
|
||
| - task: PowerShell@2 | ||
| inputs: | ||
| filePath: '$(Build.SourcesDirectory)/eng/scripts/determine-release-tag.ps1' |
There was a problem hiding this comment.
This file doesnt match the new one being added in the PR. Seems like the file name should be determine-js-release-tag.ps1
The following yml are associated with projects that need to publish to npmjs.org. This PR simply removes each's individual
releasestage in favor of a single added stage. After walking each package withinazure-sdk-tools, I believe these are the only remaining builds that must become 1es compliant.tools/sdk-generation-pipeline/ci.ymlDeleted inmaintools/apiview/parsers/js-api-parser/ci.ymlOnly publishes to internal feedeng/pipelines/templates/stages/archetype-autorest-preview.ymlThis yml is referenced nowhere that I can tell. Not from another template and not direct from a build definition.FOR REVIEWERS I advise disabling whitespace diffs it massively simplifies looking at what this PR does. Much more re-use than code deletion.
Related to #7941