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

Use slough artifactory in CI Part 2 #162

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

HenrikPoulsen
Copy link

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:

  • UTR script downloads from IT artifactory have been replaced with slough artifactory.

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.

@HenrikPoulsen HenrikPoulsen requested a review from a team as a code owner April 4, 2024 18:25
@unity-cla-assistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Sourcegraph seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@RikuTheFuffs
Copy link
Contributor

@HenrikPoulsen I approved the PR but it seems you need to sign the contributor license agreement ("CLA"), can you please do it? -> #162 (comment)

@HenrikPoulsen
Copy link
Author

I have signed it now. A bit odd I need to do that since we work at the same company, but oh well 🙂

@RikuTheFuffs
Copy link
Contributor

Hey @HenrikPoulsen , Github still flags the CLA as not signed. Are you sure you went through the entire process?

Also, is this PR still relevant?

image

@HenrikPoulsen
Copy link
Author

When I click on the CLA link it brings me to the form with all the information I entered last time already filled in and the entire form is read-only.
I imagine that means that the CLA has been submitted. So guess there's some issues with the form in general.
Perhaps it doesn't like that I'm an employee or something 🤷

The changes are not critical, but will give you better CI stability.
It feels like you are going to have to land these changes yourself if you are interested, since the CLA process isn't behaving for me

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