ci: Update funcparserlib version (PROJQUAY-2520) #893
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
kleesc
force-pushed
the
pin-github-ci-setuptools
branch
5 times, most recently
from
69dfa07
to
ea9cd6a
Compare
crozzy
previously approved these changes
Sep 17, 2021
kleesc
force-pushed
the
pin-github-ci-setuptools
branch
3 times, most recently
from
371c297
to
11269e9
Compare
kleesc
changed the title
kleesc
force-pushed
the
pin-github-ci-setuptools
branch
from
11269e9
to
1183a52
Compare
crozzy
previously approved these changes
Sep 17, 2021
Updating funcparserlib to 1.0.0a0 fixes the issue initially addressed in d3809b2.
kleesc
force-pushed
the
pin-github-ci-setuptools
branch
from
1183a52
to
24f27ca
Compare
crozzy
approved these changes
Sep 17, 2021
crozzy
pushed a commit
to crozzy/quay
that referenced
this pull request
Sep 17, 2021
Updating funcparserlib to 1.0.0a0 fixes the issue initially addressed in d3809b2.
crozzy
pushed a commit
to crozzy/quay
that referenced
this pull request
Sep 17, 2021
Updating funcparserlib to 1.0.0a0 fixes the issue initially addressed in d3809b2.
crozzy
added a commit
that referenced
this pull request
Sep 20, 2021
* secscan: continue iterating after failure (PROJQUAY-2563) If Clair returns an error the current behaviour is to error out, thus not indexing any subsequent manifests. This change allows the worker to continue indexing subsequent manifests after one failure. Signed-off-by: crozzy <joseph.crosland@gmail.com> * secscan: fix secscan api ApiRequestFailure test (PROJQUAY-2563) (#896) Follow-up to 694fa2a. Correctly set the expected value for the pagination token when not blocking on a failed API request. * ci: Update funcparserlib version (PROJQUAY-2520) (#893) Updating funcparserlib to 1.0.0a0 fixes the issue initially addressed in d3809b2. Co-authored-by: Kenny Lee Sin Cheong <2530351+kleesc@users.noreply.github.com>
kleesc
added a commit
to kleesc/quay
that referenced
this pull request
Sep 22, 2021
Updating funcparserlib to 1.0.0a0 fixes the issue initially addressed in d3809b2.
kleesc
added a commit
that referenced
this pull request
Sep 22, 2021
…900) * notification: check certs exists for webhooks (PROJQUAY-2424) (#886) Make sure the Quay key/cert pair (ssl.key + ssl.cert) have been mounted/exists whenever it tries sending a webhook request with client cert. If that's not the case, then the webhook is sent without client cert. This can happen when TLS is not handled by the Quay container, in which case these certs are not required by default in the Quay container. * ci: Update funcparserlib version (PROJQUAY-2520) (#893) Updating funcparserlib to 1.0.0a0 fixes the issue initially addressed in d3809b2. * ci: pin oci test to a specific sha (PROJQUAY-2570) This pins the distribution-spec repo to a specific sha to prevent failing CI because of a change in the source test Signed-off-by: harishsurf <hgovinda@redhat.com> Co-authored-by: Harish Govindarajulu <hgovinda@redhat.com>
flavianmissi
pushed a commit
that referenced
this pull request
Oct 27, 2021
* secscan: continue iterating after failure (PROJQUAY-2563) If Clair returns an error the current behaviour is to error out, thus not indexing any subsequent manifests. This change allows the worker to continue indexing subsequent manifests after one failure. Signed-off-by: crozzy <joseph.crosland@gmail.com> * secscan: fix secscan api ApiRequestFailure test (PROJQUAY-2563) (#896) Follow-up to 694fa2a. Correctly set the expected value for the pagination token when not blocking on a failed API request. * ci: Update funcparserlib version (PROJQUAY-2520) (#893) Updating funcparserlib to 1.0.0a0 fixes the issue initially addressed in d3809b2. Co-authored-by: Kenny Lee Sin Cheong <2530351+kleesc@users.noreply.github.com>
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.
No description provided.