Skip to content

Commit 95c7edd

Browse files
Using acceptance builder for downloading in e2e tests
Signed-off-by: Abhijit Gadgil <agadgil@progress.com>
1 parent ccb59e3 commit 95c7edd

2 files changed

Lines changed: 6 additions & 0 deletions

File tree

.expeditor/end_to_end.pipeline.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,9 @@ expeditor:
33
HAB_AUTH_TOKEN:
44
path: account/static/habitat/chef-ci
55
field: auth_token # Production Builder
6+
ACCEPTANCE_HAB_AUTH_TOKEN:
7+
path: account/static/habitat/chef-ci
8+
field: acceptance_auth_token # Acceptance Builder
69
accounts:
710
- aws/chef-cd
811
defaults:

.expeditor/scripts/end_to_end/setup_environment_darwin.sh

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,9 @@ channel=${1:?You must specify a channel value}
1616
# Note: We should always have a `hab` binary installed in our CI
1717
# Anka VMs.
1818

19+
HAB_BLDR_URL="https://bldr.acceptance.habitat.sh"
20+
HAB_AUTH_TOKEN="${ACCEPTANCE_HAB_AUTH_TOKEN}"
21+
1922
# On macOS, /usr/bin is SIP-protected so we use /usr/local/bin.
2023
HAB_BINLINK_DIR="/usr/local/bin"
2124
hab_binary="$(command -v hab)"

0 commit comments

Comments
 (0)