Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
K
k3s
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jacklull
k3s
Commits
cb28ed1f
Commit
cb28ed1f
authored
Jun 02, 2017
by
Ke Wu
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Let COS docker validation node tests against gci-next-canary
We plan to use family gci-next-canary in container-vm-image-staging for future Docker upgration and validation.
parent
dcf19e88
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
cos-docker-validation.properties
...enkins/docker_validation/cos-docker-validation.properties
+2
-2
No files found.
test/e2e_node/jenkins/docker_validation/cos-docker-validation.properties
View file @
cb28ed1f
GCI_IMAGE_PROJECT
=
co
s-docker-validation
GCI_IMAGE_FAMILY
=
validation-test
GCI_IMAGE_PROJECT
=
co
ntainer-vm-image-staging
GCI_IMAGE_FAMILY
=
gci-next-canary
GCI_IMAGE
=
$(gcloud compute images describe-from-family ${GCI_IMAGE_FAMILY} --project=${GCI_IMAGE_PROJECT} --format="value(name)")
GCI_CLOUD_INIT
=
test/e2e_node/jenkins/gci-init.yaml
...
...
Write
Preview
Markdown
is supported
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