skills/angular__angular
1
0
Fork 0
mirror of https://github.com/angular/angular.git synced 2026-09-14 13:54:52 +08:00
Code Issues Packages Projects Releases Wiki Activity

build: force push publish artifacts script (#14489)

Browse Source 
* Similarly to `angular/angular`, we should publish our artifacts using `git push --force`. This avoids the race condition where another CI job pushes to the builds repository before we try to push with our outdated `HEAD`.
This commit is contained in:
Paul Gschwendtner
2018-12-18 05:19:38 +01:00
committed by Jeremy Elbourn
parent 88523c37ae
commit 7ade500e7f
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/deploy/publish-build-artifacts.sh
+1 -1
View File
@@ -106,7 +106,7 @@ publishPackage() {
git add -A
git commit --allow-empty -m "${buildCommitMessage}"
git tag "${buildTagName}"
git push origin ${branchName} --tags
git push origin ${branchName} --tags --force
echo "Published package artifacts for ${packageName}#${buildVersionName} into ${branchName}"
}
scripts/deploy/publish-docs-content.sh
+1 -1
View File
@@ -124,6 +124,6 @@ echo "Credentials for docs-content repository are now set up. Publishing.."
git add -A
git commit --allow-empty -m "${buildCommitMessage}"
git tag "${buildTagName}"
git push origin ${branchName} --tags
git push origin ${branchName} --tags --force
echo "Published docs-content for ${buildVersionName} into ${branchName} successfully"