[JBIDE-22644] Unable to perform oc binary actions because of insecure flag #180
Conversation
This file contains hidden or 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
openshift-bot
added
the
needs-rebase
jcantrill
force-pushed
the
jbide_22644_clear_env_for_oc_binary
branch
from
b81d5cc to
3a97974
Compare
Contributor
Author
|
[test] |
openshift-bot
removed
the
needs-rebase
jcantrill
force-pushed
the
jbide_22644_clear_env_for_oc_binary
branch
from
3a97974 to
a821fd5
Compare
Contributor
Author
|
[merge] |
Contributor
|
Java Client Merge Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test-openshift-restclient-java/192/) |
Contributor
|
Evaluated for javaclient merge up to a821fd5 |
Contributor
|
Evaluated for javaclient test up to a821fd5 |
Contributor
|
Java Client Test Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test-openshift-restclient-java/193/) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
CC @fbricon
blocked by #179