Use slough artifactory in CI Part 2 #162
Open
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.
There's an ongoing incident in #incident-2024-03-25-1 that is causing timeouts for IT Artifactory.
This PR is part of a series of updates where we try to reduce the load on artifactory as well as lowering the risk of Yamato jobs timing out by relying on it less.
Slough artifactory is useful because it is an artifactory instance in the same datacenter as the vms the Yamato jobs run on.
This PR specifically addresses:
This PR is auto generated so the results is probably pretty dumb.
If something looks strange then please help it along by correcting anything that is incorrect or missing.
Created by Sourcegraph batch change
henrikp/utr-slough-artifactory
.