Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
小 白蛋
Vault
Commits
c706ca2c
Unverified
Commit
c706ca2c
authored
4 years ago
by
Nick Cabatoff
Committed by
GitHub
4 years ago
Browse files
Options
Download
Email Patches
Plain Diff
Put go_test.yml back how it was (on ent) re licensing (#11736)
parent
e5b6515e
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
.circleci/config.yml
+40
-15
.circleci/config.yml
.circleci/config/commands/go_test.yml
+8
-3
.circleci/config/commands/go_test.yml
with
48 additions
and
18 deletions
+48
-18
.circleci/config.yml
+
40
-
15
View file @
c706ca2c
...
...
@@ -933,9 +933,14 @@ jobs:
make prep
mkdir -p test-results/go-test
# Don't tempt fate by having the license env var populated: tests should
# have to use it explicitly (via env var VAULT_LICENSE_CI) rather than
# depending on an implicit behaviour.
# We don't want VAULT_LICENSE set when running Go tests, because that's
# not what developers have in their environments and it could break some
# tests; it would be like setting VAULT_TOKEN. However some non-Go
# CI commands, like the UI tests, shouldn't have to worry about licensing.
# So we set VAULT_LICENSE in CI, and here we unset it. Instead of
# VAULT_LICENSE, we populate VAULT_LICENSE_CI, so that tests which want
# an externally supplied license can opt-in to using it.
export VAULT_LICENSE_CI="$VAULT_LICENSE"
VAULT_LICENSE=
# Create a docker network for our testcontainer
...
...
@@ -1155,9 +1160,14 @@ jobs:
make prep
mkdir -p test-results/go-test
# Don't tempt fate by having the license env var populated: tests should
# have to use it explicitly (via env var VAULT_LICENSE_CI) rather than
# depending on an implicit behaviour.
# We don't want VAULT_LICENSE set when running Go tests, because that's
# not what developers have in their environments and it could break some
# tests; it would be like setting VAULT_TOKEN. However some non-Go
# CI commands, like the UI tests, shouldn't have to worry about licensing.
# So we set VAULT_LICENSE in CI, and here we unset it. Instead of
# VAULT_LICENSE, we populate VAULT_LICENSE_CI, so that tests which want
# an externally supplied license can opt-in to using it.
export VAULT_LICENSE_CI="$VAULT_LICENSE"
VAULT_LICENSE=
# Create a docker network for our testcontainer
...
...
@@ -1628,9 +1638,14 @@ jobs:
make prep
mkdir -p test-results/go-test
# Don't tempt fate by having the license env var populated: tests should
# have to use it explicitly (via env var VAULT_LICENSE_CI) rather than
# depending on an implicit behaviour.
# We don't want VAULT_LICENSE set when running Go tests, because that's
# not what developers have in their environments and it could break some
# tests; it would be like setting VAULT_TOKEN. However some non-Go
# CI commands, like the UI tests, shouldn't have to worry about licensing.
# So we set VAULT_LICENSE in CI, and here we unset it. Instead of
# VAULT_LICENSE, we populate VAULT_LICENSE_CI, so that tests which want
# an externally supplied license can opt-in to using it.
export VAULT_LICENSE_CI="$VAULT_LICENSE"
VAULT_LICENSE=
# Create a docker network for our testcontainer
...
...
@@ -1781,9 +1796,14 @@ jobs:
make prep
mkdir -p test-results/go-test
# Don't tempt fate by having the license env var populated: tests should
# have to use it explicitly (via env var VAULT_LICENSE_CI) rather than
# depending on an implicit behaviour.
# We don't want VAULT_LICENSE set when running Go tests, because that's
# not what developers have in their environments and it could break some
# tests; it would be like setting VAULT_TOKEN. However some non-Go
# CI commands, like the UI tests, shouldn't have to worry about licensing.
# So we set VAULT_LICENSE in CI, and here we unset it. Instead of
# VAULT_LICENSE, we populate VAULT_LICENSE_CI, so that tests which want
# an externally supplied license can opt-in to using it.
export VAULT_LICENSE_CI="$VAULT_LICENSE"
VAULT_LICENSE=
# Create a docker network for our testcontainer
...
...
@@ -2385,9 +2405,14 @@ jobs:
make prep
mkdir -p test-results/go-test
# Don't tempt fate by having the license env var populated: tests should
# have to use it explicitly (via env var VAULT_LICENSE_CI) rather than
# depending on an implicit behaviour.
# We don't want VAULT_LICENSE set when running Go tests, because that's
# not what developers have in their environments and it could break some
# tests; it would be like setting VAULT_TOKEN. However some non-Go
# CI commands, like the UI tests, shouldn't have to worry about licensing.
# So we set VAULT_LICENSE in CI, and here we unset it. Instead of
# VAULT_LICENSE, we populate VAULT_LICENSE_CI, so that tests which want
# an externally supplied license can opt-in to using it.
export VAULT_LICENSE_CI="$VAULT_LICENSE"
VAULT_LICENSE=
# Create a docker network for our testcontainer
...
...
This diff is collapsed.
Click to expand it.
.circleci/config/commands/go_test.yml
+
8
-
3
View file @
c706ca2c
...
...
@@ -76,9 +76,14 @@ steps:
make prep
mkdir -p test-results/go-test
# Don't tempt fate by having the license env var populated: tests should
# have to use it explicitly (via env var VAULT_LICENSE_CI) rather than
# depending on an implicit behaviour.
# We don't want VAULT_LICENSE set when running Go tests, because that's
# not what developers have in their environments and it could break some
# tests; it would be like setting VAULT_TOKEN. However some non-Go
# CI commands, like the UI tests, shouldn't have to worry about licensing.
# So we set VAULT_LICENSE in CI, and here we unset it. Instead of
# VAULT_LICENSE, we populate VAULT_LICENSE_CI, so that tests which want
# an externally supplied license can opt-in to using it.
export VAULT_LICENSE_CI="$VAULT_LICENSE"
VAULT_LICENSE=
# Create a docker network for our testcontainer
...
...
This diff is collapsed.
Click to expand it.
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment