Skip to content
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

ci: use more descriptive names for published build artifacts #33957

Closed
wants to merge 1 commit into from

Conversation

gkalpak
Copy link
Member

@gkalpak gkalpak commented Nov 21, 2019

In efbbae5, the publish_packages_as_artifacts CircleCI job was created to publish the build artifacts of PR builds on CI. In a8f4f14, its scope was expanded to also publish build artifacts on non-PR builds.

The published artifacts names are constructed based on the PR number (e.g. include -pr12345-), so on non-PR builds the names do not reflect the source branch (instead, they include -prfalse-).

This commit fixes this by using the current branch name. For example, artifact names for the master or 9.0.x branch will include -master- and -9.0.x- respectively (instead of -prfalse-).
(NOTE: For PRs, where branch name is pull/12345, the branch name is transformed to pr12345.)

In efbbae5, the `publish_packages_as_artifacts` CircleCI job was
created to publish the build artifacts of PR builds on CI. In a8f4f14,
its scope was expanded to also publish build artifacts on non-PR builds.

The published artifacts names are constructed based on the PR number
(e.g. include `-pr12345-`), so on non-PR builds the names do not reflect
the source branch (instead, they include `-prfalse-`).

This commit fixes this by using the current branch name. For example,
artifact names for the `master` or `9.0.x` branch will include
`-master-` and `-9.0.x-` respectively (instead of `-prfalse-`).
(NOTE: For PRs, where branch name is `pull/12345`, the branch name is
transformed to `pr12345`.)
@gkalpak gkalpak added type: bug/fix action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: patch This PR is targeted for the next patch release labels Nov 21, 2019
@gkalpak gkalpak requested a review from a team as a code owner November 21, 2019 12:07
@ngbot ngbot bot added this to the needsTriage milestone Nov 21, 2019
@gkalpak gkalpak added the merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note label Nov 21, 2019
@gkalpak
Copy link
Member Author

gkalpak commented Nov 21, 2019

merge-assistance: The integration_test failure is unrelated. (Will be fixed by #33955.)

@IgorMinar IgorMinar removed the merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note label Nov 22, 2019
@IgorMinar
Copy link
Contributor

removing the merge-assistance label, as the caretaker can't merge PRs when CI is failing.

@gkalpak is right the issue has been fixed upstream, but the caretaker can't know this for sure.

rebasing the PR or restarting the CI (the entire workflow, not just failed job - this causes an automatic rebase on CI), should green up this PR

matsko pushed a commit that referenced this pull request Nov 22, 2019
In efbbae5, the `publish_packages_as_artifacts` CircleCI job was
created to publish the build artifacts of PR builds on CI. In a8f4f14,
its scope was expanded to also publish build artifacts on non-PR builds.

The published artifacts names are constructed based on the PR number
(e.g. include `-pr12345-`), so on non-PR builds the names do not reflect
the source branch (instead, they include `-prfalse-`).

This commit fixes this by using the current branch name. For example,
artifact names for the `master` or `9.0.x` branch will include
`-master-` and `-9.0.x-` respectively (instead of `-prfalse-`).
(NOTE: For PRs, where branch name is `pull/12345`, the branch name is
transformed to `pr12345`.)

PR Close #33957
@matsko matsko closed this in 485ce64 Nov 22, 2019
@gkalpak gkalpak deleted the ci-fix-artifact-names branch November 22, 2019 19:08
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Dec 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project cla: yes target: patch This PR is targeted for the next patch release type: bug/fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants