[Automation] - Cypress install force revert #11197
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
izaac
added
the
QA/dev-automation
izaac
force-pushed
the
cypress_install_force
branch
4 times, most recently
from
3eaa235
to
e22f714
Compare
izaac
force-pushed
the
cypress_install_force
branch
from
e22f714
to
6462609
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Removing the forced cypress install
Occurred changes and/or fixed issues
Forcing the cypress install didn't fix the cache issue on 2.7 runs.
Bumping the version worked. https://github.com/rancherlabs/jenkins-job-builder/pull/455
Areas or cases that should be tested
Jenkins
A run in Jenkins was done to check the 2.7 pipelines