Skip to content
Snippets Groups Projects

(chore): use pipeline id vs commit id

Merged (chore): use pipeline id vs commit id
fix/use-pipeline-id-vs-commit into master
Merged Mark Harding requested to merge fix/use-pipeline-id-vs-commit into master

As demonstrated via 357faf4a, using $CI_BUILD_REF is DANGEROUS and can lead to conflicts. Making use of $CI_PIPELINE_ID keeps all the jobs in pipeline isolated.

Merge request reports

Checking pipeline status.

Approved by
Ben Juan Manuel Solaro

Merged by Mark HardingMark Harding 5 years ago (Aug 27, 2019 1:18pm UTC)

Merge details

  • Changes merged into master with 5ed6e576 (commits were squashed).
  • Deleted the source branch.

Pipeline #78624251 passed with warnings

Stage: test:unit
Stage: build
Stage: prepare
Stage: deploy:staging
Stage: test:e2e
Stage: deploy:canary
Stage: deploy:production

Pipeline passed with warnings for 5ed6e576 on master

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
Please register or sign in to reply