-
Notifications
You must be signed in to change notification settings - Fork 604
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
Create Dedicated Pipeline to Create Tarball Packages #4891
base: main
Are you sure you want to change the base?
Create Dedicated Pipeline to Create Tarball Packages #4891
Conversation
- output: pipelineArtifact | ||
targetPath: $(Build.ArtifactStagingDirectory)/published-versions | ||
artifactName: published-versions |
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.
This is how you publish a pipeline artifact. There should be another entry like this pointing to the output folder from the rush publish --pack
command; that will produce your artifact for consumption in the separate publish pipeline.
- name: Publish | ||
${{ if eq(parameters.TestRun, false) }}: | ||
value: '--publish' | ||
${{ else }}: | ||
value: '' |
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.
- name: Publish | |
${{ if eq(parameters.TestRun, false) }}: | |
value: '--publish' | |
${{ else }}: | |
value: '' |
parameters: | ||
Publish: $(Publish) |
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.
parameters: | |
Publish: $(Publish) |
default: '' | ||
|
||
steps: | ||
- script: 'node common/scripts/install-run-rush.js publish $(Publish) --pack --include-all --release-folder esrp-release' |
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.
The folder specified under --release-folder
should correspond to an output
entry in templateContext.outputs
.
@@ -0,0 +1,59 @@ | |||
parameters: | |||
- name: TestRun | |||
displayName: 'Test Run (Will Not Create Tar Files for Rushstack)' |
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.
Considering that publishing the artifact does not have any direct consequences, there's no reason to have a dryRun option for this pipeline.
artifactName: published-versions | ||
- output: pipelineArtifact | ||
targetPath: $(Build.ArtifactStagingDirectory)/packages | ||
artifactNames: packages |
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.
artifactNames: packages | |
artifactName: packages |
- bash: > | ||
mkdir -p $(Build.ArtifactStagingDirectory)/packages | ||
displyName: 'Create Folder for Packages File' | ||
|
||
- script: 'node common/scripts/install-run-rush.js publish --publish --pack --include-all --release-folder esrp-release' | ||
displayName: 'Create TarBallz folder for Rush packages' |
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.
- bash: > | |
mkdir -p $(Build.ArtifactStagingDirectory)/packages | |
displyName: 'Create Folder for Packages File' | |
- script: 'node common/scripts/install-run-rush.js publish --publish --pack --include-all --release-folder esrp-release' | |
displayName: 'Create TarBallz folder for Rush packages' | |
- script: | | |
mkdir -p $(Build.ArtifactStagingDirectory)/packages | |
node common/scripts/install-run-rush.js publish --publish --pack --include-all --release-folder "$(Build.ArtifactStagingDirectory)/packages" | |
displayName: 'Pack tarballs' |
Summary
Creates a pipeline dedicated to packaging rushstack packges as tarballs.
Details
Creating a separate pipeline would not interfere with normal npm packaging.
How it was tested
Tested by running the
rush publish
command use to create tarballs locally.Impacted documentation
NA