This repository has been archived by the owner on May 6, 2022. It is now read-only.
re-enable Jenkins to run e2e #2018
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
cncf-cla: yes
|
/retest |
4 similar comments
|
/retest |
|
/retest |
|
/retest |
|
/retest |
This was referenced May 8, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR re-enables e2e in the Jenkins job. I ran jenkins tests a total of 6 times with this PR with no issues. This depends on
#2010 or#2016 first being merged and then I'll need to rebase to pick up those changes to pass Jenkins.Re-enabling e2e looks to add no more then 3-5 minutes max with prep, running the tests, and then teardown and collection of logs. Total runs of the Jenkins job comes in around 33-36 minutes.