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
808209de
Commit
808209de
authored
Feb 10, 2016
by
k8s-merge-robot
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #20839 from spxtr/clone-soak
Auto commit by PR queue bot
parents
96822276
94b08128
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
33 additions
and
0 deletions
+33
-0
e2e.sh
hack/jenkins/e2e.sh
+29
-0
kubernetes-soak.yaml
hack/jenkins/job-configs/kubernetes-soak.yaml
+4
-0
No files found.
hack/jenkins/e2e.sh
View file @
808209de
...
@@ -632,6 +632,35 @@ case ${JOB_NAME} in
...
@@ -632,6 +632,35 @@ case ${JOB_NAME} in
:
${
PROJECT
:
=
"kubernetes-jenkins"
}
:
${
PROJECT
:
=
"kubernetes-jenkins"
}
;;
;;
# Clone of kubernetes-soak-weekly-deploy-gce. Issue #20832.
kubernetes-soak-weekly-deploy-gce-2
)
:
${
E2E_CLUSTER_NAME
:
=
"gce-soak-weekly-2"
}
:
${
E2E_DOWN
:
=
"false"
}
:
${
E2E_NETWORK
:
=
"gce-soak-weekly-2"
}
:
${
E2E_TEST
:
=
"false"
}
:
${
E2E_UP
:
=
"true"
}
:
${
KUBE_GCE_INSTANCE_PREFIX
:
=
"gce-soak-weekly-2"
}
:
${
PROJECT
:
=
"kubernetes-jenkins"
}
;;
# Clone of kubernetes-soak-continuous-e2e-gce. Issue #20832.
kubernetes-soak-continuous-e2e-gce-2
)
:
${
E2E_CLUSTER_NAME
:
=
"gce-soak-weekly-2"
}
:
${
E2E_DOWN
:
=
"false"
}
:
${
E2E_NETWORK
:
=
"gce-soak-weekly-2"
}
:
${
E2E_UP
:
=
"false"
}
# Clear out any orphaned namespaces in case previous run was interrupted.
:
${
E2E_CLEAN_START
:
=
"true"
}
# We should be testing the reliability of a long-running cluster. The
# [Disruptive] tests kill/restart components or nodes in the cluster,
# defeating the purpose of a soak cluster. (#15722)
#
# TODO(ihmccreery) remove [Skipped] once tests are relabeled
:
${
GINKGO_TEST_ARGS
:
=
"--ginkgo.skip=
\[
Disruptive
\]
|
\[
Flaky
\]
|
\[
Feature:.+
\]
|
\[
Skipped
\]
"
}
:
${
KUBE_GCE_INSTANCE_PREFIX
:
=
"gce-soak-weekly-2"
}
:
${
PROJECT
:
=
"kubernetes-jenkins"
}
;;
# Sets up the GKE soak cluster weekly using the latest CI release.
# Sets up the GKE soak cluster weekly using the latest CI release.
kubernetes-soak-weekly-deploy-gke
)
kubernetes-soak-weekly-deploy-gke
)
:
${
E2E_CLUSTER_NAME
:
=
"jenkins-gke-soak-weekly"
}
:
${
E2E_CLUSTER_NAME
:
=
"jenkins-gke-soak-weekly"
}
...
...
hack/jenkins/job-configs/kubernetes-soak.yaml
View file @
808209de
...
@@ -70,6 +70,10 @@
...
@@ -70,6 +70,10 @@
builds will be blocked and remain in the queue until the
builds will be blocked and remain in the queue until the
deployment is complete.<br>
deployment is complete.<br>
branch
:
'
master'
branch
:
'
master'
-
'
gce-2'
:
deploy-description
:
Clone of kubernetes-soak-weekly-deploy-gce.
e2e-description
:
Clone of kubernetes-soak-continuous-e2e-gce.
branch
:
'
master'
-
'
gce-1.1'
:
-
'
gce-1.1'
:
deploy-description
:
|
deploy-description
:
|
Deploy Kubernetes to soak cluster using the latest successful
Deploy Kubernetes to soak cluster using the latest successful
...
...
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