-
Notifications
You must be signed in to change notification settings - Fork 204
[Do Not Review] Adding back in the deprecation pipeline #2684
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.
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
base: main
Are you sure you want to change the base?
Changes from 12 commits
7840b15
0e63ccf
521b734
793c039
a30024f
a17d3d1
e0d0a4d
efeb31c
6a4b89c
83590eb
b27d5d6
81fe9ec
3792495
1d5b80f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,68 @@ | ||||||
trigger: none | ||||||
resources: | ||||||
repositories: | ||||||
- repository: GovernedTemplates | ||||||
type: git | ||||||
name: OneBranch.Pipelines/GovernedTemplates | ||||||
ref: refs/heads/main | ||||||
pipelines: | ||||||
- pipeline: microsoft-teams-library-js-pipeline | ||||||
source: 'microsoft-teams-library-js/M365 Platform/App SDK/OfficeDev.microsoft-teams-library-js' | ||||||
project: ISS | ||||||
variables: | ||||||
- name: System.Debug | ||||||
value: true | ||||||
extends: | ||||||
template: v2/Microsoft.Official.yml@GovernedTemplates | ||||||
parameters: | ||||||
platform: | ||||||
name: m365 | ||||||
workload: Substrate | ||||||
serviceTreeId: $(serviceTreeId) | ||||||
serviceGroupName: Platform | ||||||
stages: | ||||||
- stage: Prod_Lockbox_Approval_Deployment | ||||||
displayName: Lockbox Approval/Deployment | ||||||
dependsOn: [] | ||||||
variables: | ||||||
stage_type: deployment | ||||||
azure_subscription_ids: $(subscriptionId) | ||||||
jobs: | ||||||
- job: Agent_job | ||||||
pool: | ||||||
type: release | ||||||
steps: | ||||||
- download: microsoft-teams-library-js-pipeline | ||||||
- task: prepare-deployment@1 | ||||||
displayName: | ||||||
inputs: | ||||||
taskType: credentialFetchTaskAzureRM | ||||||
armserviceconnection: $(serviceConnectionId) | ||||||
subscriptionid: $(subscriptionId) | ||||||
- task: AssetRetention@3 | ||||||
displayName: ARtifact Retention Orchestrator Workflow (ARROW) | ||||||
inputs: | ||||||
ArrowServiceConnection: $(arrowServiceConnectionId) | ||||||
IsShipped: true | ||||||
- task: AzureKeyVault@2 | ||||||
displayName: 'Azure Key Vault: $(keyVaultName)' | ||||||
inputs: | ||||||
ConnectedServiceName: $(serviceConnectionId) | ||||||
KeyVaultName: $(keyVaultName) | ||||||
SecretsFilter: $(keyVaultSecretsFilter) | ||||||
- task: NodeTool@0 | ||||||
displayName: Use Node 18.x | ||||||
inputs: | ||||||
versionSpec: 18.x | ||||||
- task: PowerShell@2 | ||||||
displayName: Update npmrc with NPM-TOKEN | ||||||
inputs: | ||||||
targetType: 'inline' | ||||||
script: Set-Content -Path $(PIPELINE.WORKSPACE)/microsoft-teams-library-js-pipeline/NPMFeed/.npmrc -Value "//registry.npmjs.org/:_authToken=$(NPM-TOKEN)" | ||||||
- task: Npm@1 | ||||||
displayName: Publish to npm (tag beta) KV | ||||||
inputs: | ||||||
command: custom | ||||||
workingDir: $(PIPELINE.WORKSPACE)/microsoft-teams-library-js-pipeline/NPMFeed | ||||||
verbose: false | ||||||
customCommand: deprecate @microsoft/teams-js@3.0.* "Package no longer supported. Use at your own risk" | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I feel like rather than needing to check in a PR each time you want to deprecate a version; it would make more sense to make the version a pipeline variable so we can edit it in ADO each time we run the pipeline.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yup the plan was to make the version/versions plummed in as a pipeline resource instead of a single version. Only had it as the above since I was intending for this PR to actually just be a draft to see if it gets added to ADO correctly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you say more about how this pipeline works? This looks like every time the pipeline runs, it deprecates all 3.0.* packages. Is that how it's supposed to work? Or is the person who runs the pipeline supposed to be able to specify what version they want to deprecate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry this was just meant to be a draft PR to see if the new pipeline would be added into ADO. Will be modifying this so that we can specify the version/versions we wish to deprecate as a Pipeline resource going forward.