Skip to content

WIP: Test PushSecretName via extended tests #1515

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 2, 2015

Conversation

mfojtik
Copy link
Contributor

@mfojtik mfojtik commented Mar 31, 2015

This PR is:

  • Removing existing Docker strategy test (as this strategy is exercised by PushSecret test)
  • Add DEBUG=1 ./hack/test-extended.sh which allows you to re-run tests (I can't work without this ;-)
  • Refactoring in fixture names / namespaces / etc.

@mfojtik
Copy link
Contributor Author

mfojtik commented Mar 31, 2015

@soltysh @bparees still in progress BUT at least the test pass :-)

@mfojtik mfojtik force-pushed the build_secret_extended branch 2 times, most recently from f2ff992 to 867e146 Compare March 31, 2015 14:34
local image=$1
local registry=$2
echo "[INFO] Caching $image to $registry"
( docker pull $image && \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure we want to do this pull because IIRC we build those images locally when doing full test inside jenkins. So this might overwrite them, which is not what we'd expect. The same might be true for local as well. In all other cases where you'd actually wanted to pull them I'd would add flag to those tests to do so.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, should probably just tag+push without doing the pull, if these are images that are part of the build.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like it's being used for images that aren't part of the origin build, so it should be ok.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually openshift/origin-custom-docker-builder is part of that build and openshift/ruby-20-centos7 should be already inside the image, so IMHO it's safer not to pull them.

@soltysh
Copy link
Contributor

soltysh commented Apr 1, 2015

I like the overall structure of the tests, they are clean and easily understandable. Good work @mfojtik!

@mfojtik mfojtik force-pushed the build_secret_extended branch 2 times, most recently from 7361f4f to ac7f2aa Compare April 1, 2015 17:25
@mfojtik
Copy link
Contributor Author

mfojtik commented Apr 1, 2015

@soltysh @bparees removed pull

@soltysh
Copy link
Contributor

soltysh commented Apr 2, 2015

LGTM

@mfojtik mfojtik force-pushed the build_secret_extended branch from ac7f2aa to c7d6009 Compare April 2, 2015 09:20
@mfojtik
Copy link
Contributor Author

mfojtik commented Apr 2, 2015

[merge]

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_openshift3/1657/) (Image: devenv-fedora_1188)

@openshift-bot
Copy link
Contributor

[Test]ing while waiting on the merge queue

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_openshift3/1657/)

@openshift-bot
Copy link
Contributor

Evaluated for origin up to c7d6009

@mfojtik
Copy link
Contributor Author

mfojtik commented Apr 2, 2015

[merge] again

openshift-bot pushed a commit that referenced this pull request Apr 2, 2015
@openshift-bot openshift-bot merged commit 599ff6a into openshift:master Apr 2, 2015
@mfojtik mfojtik deleted the build_secret_extended branch August 25, 2015 09:39
jboyd01 pushed a commit to jboyd01/origin that referenced this pull request Nov 3, 2017
…service-catalog/' changes from 892b0368f0..3064247d05

3064247d05 origin build: add origin tooling
48ecff1 Chart changes for 0.1.2 (openshift#1527)
8727247 Fix change validator to look up serviceclass properly (openshift#1518)
b0b138b Broker Reconciliation occurs too frequently (openshift#1514)
cc816eb When a SI is unbindable, mark the binding request failed. (openshift#1522)
41290e9 Clarify semantics around RelistDuration (openshift#1516)
6bcb593 Send Context with UpdateInstanceRequest (openshift#1517)
c3b72d8 Enforce stricly increasing broker relistRequests (openshift#1515)
01d81e5 Follow up from openshift#1450 and openshift#1444 (openshift#1504)
5e77882 Retry failed deprovision requests (openshift#1505)
f6c891d Allow updates of instances that failed a previous update. (openshift#1502)
5107086 Use Plan ID from ExternalProperties when deprovisioning instance (openshift#1501)
d897c60 Adding message builder for expected event strings  (openshift#1465)
9f6152e update osb client and freeze gorilla context (openshift#1496)
c63277e Add unit tests verifying deleting a resource with an on-going operation or in orphan mitigation. (openshift#1490)
4ecca16 Pretty logging for controller_instance.go (openshift#1472)
c232db4 Register qemu statics when building non-amd64 images (openshift#1494)
0e54c57 fix 'Spring Cloud Services -> Configuring with Vault' link in docs (openshift#1495)
REVERT: 892b0368f0 origin build: add origin tooling

git-subtree-dir: cmd/service-catalog/go/src/github.com/kubernetes-incubator/service-catalog
git-subtree-split: 3064247d0544aa43f976d93caea0a11771434ef7
jpeeler pushed a commit to jpeeler/origin that referenced this pull request Feb 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants