Skip to content

Commit

Permalink
Merge pull request #1883 from bugsnag/expo-47
Browse files Browse the repository at this point in the history
Update @bugsnag/expo versions in the pipeline
  • Loading branch information
imjoehaines authored Dec 8, 2022
2 parents 38dc658 + 76f21d0 commit 4e04545
Showing 1 changed file with 7 additions and 6 deletions.
13 changes: 7 additions & 6 deletions .buildkite/pipeline.yml
Original file line number Diff line number Diff line change
Expand Up @@ -136,33 +136,34 @@ steps:
commands:
- buildkite-agent pipeline upload .buildkite/react-native-cli-pipeline.yml

- label: ":large_blue_circle: :large_blue_circle: :large_blue_circle: EXPO 46 PIPELINE :large_blue_circle: :large_blue_circle: :large_blue_circle:"
- label: "@bugsnag/expo latest"
depends_on: "publish-js"
trigger: "bugsnag-expo"
build:
branch: v46-next
# don't specify 'branch' here so we build the default branch in the expo
# repo, which should be the most up-to-date @bugsnag/expo version
env:
BUGSNAG_JS_BRANCH: "${BUILDKITE_BRANCH}"
BUGSNAG_JS_COMMIT: "${BUILDKITE_COMMIT}"
# a branch name that's safe to use as a docker cache identifier
BUGSNAG_JS_CACHE_SAFE_BRANCH_NAME: "${BRANCH_NAME}"

- label: ":large_blue_circle: :large_blue_circle: :large_blue_circle: EXPO 45 PIPELINE :large_blue_circle: :large_blue_circle: :large_blue_circle:"
- label: "@bugsnag/expo v46-next"
depends_on: "publish-js"
trigger: "bugsnag-expo"
build:
branch: v45-next
branch: "v46-next"
env:
BUGSNAG_JS_BRANCH: "${BUILDKITE_BRANCH}"
BUGSNAG_JS_COMMIT: "${BUILDKITE_COMMIT}"
# a branch name that's safe to use as a docker cache identifier
BUGSNAG_JS_CACHE_SAFE_BRANCH_NAME: "${BRANCH_NAME}"

- label: ":large_blue_circle: :large_blue_circle: :large_blue_circle: EXPO 44 PIPELINE :large_blue_circle: :large_blue_circle: :large_blue_circle:"
- label: "@bugsnag/expo v45-next"
depends_on: "publish-js"
trigger: "bugsnag-expo"
build:
branch: v44-next
branch: "v45-next"
env:
BUGSNAG_JS_BRANCH: "${BUILDKITE_BRANCH}"
BUGSNAG_JS_COMMIT: "${BUILDKITE_COMMIT}"
Expand Down

0 comments on commit 4e04545

Please sign in to comment.