Skip to content
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

Rewrite image tests to not use ginkgo #36

Merged
merged 3 commits into from
Oct 11, 2018
Merged

Rewrite image tests to not use ginkgo #36

merged 3 commits into from
Oct 11, 2018

Conversation

molepigeon
Copy link
Member

... and actually make them run!

... and actually make them run
ContentTrustErr: false,
// TODO the previous ginkgo test was testing for port 443, but the code returns 4443. Need to verify which is correct.
// ContentTrustURL: "https://quay.io:443",
ContentTrustURL: "https://quay.io:4443",
Copy link
Member Author

Choose a reason for hiding this comment

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

I'm not sure which URL is correct for Quay's notary server. https://quay.io:4443 gives connection refused, and https://quay.io:443 is the same as the registry URL.

The old test said port 443 (although the test never ran), and the code returns 4443.

@ecordell @ericavonb please could one of you confirm which port is the one that we should be using for notary information about images from Quay?

Choose a reason for hiding this comment

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

Quay.io is configured similarly to dockerhub, so the trust url is on the same url as the registry.

@liamawhite liamawhite merged commit 46e9cd5 into master Oct 11, 2018
@sjhx sjhx deleted the imagetests branch September 4, 2020 08:59
tim-gp pushed a commit to tim-gp/portieris that referenced this pull request Oct 1, 2020
* Rewrite image tests to not use ginkgo

... and actually make them run

* Correct quay.io port to 443

* Update golint location to use golang.org link
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.

3 participants