Updating bucket references from O11y to Ingest path

[rowlandgeoff]

Updating bucket references from obs-ci-cache to ingest-buildkite-ci

Closes: https://github.com/elastic/ingest-dev/issues/3751

[mergify]

This pull request does not have a backport label. Could you fix it @rowlandgeoff? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d is the label to automatically backport to the 1./d branch. /d is the digit
  NOTE: backport-skip has been added to this pull request.

[rowlandgeoff]

Hmm, all staging steps are failing with:

go: downloading golang.org/x/mod v0.16.0
--  | 🚨 Error: The command exited with status 1

[rowlandgeoff]

I'm no golang dependency expert, but with several version bumps being dealt with in other open PRs, feels like this should wait until those are resolved.

[v1v]

I've just added the label for all the existing branches, so the same mechanism can be enabled in each branch even if they reached EOL, so we don't have any references to the former bucket.

[rowlandgeoff]

Alright, guess I'll just use this messy PR with long list of commits rather than opening a fresh one. They're all going to get squashed anyway.

[v1v]

LGTM with just a couple of minor nits

[v1v]

Do you think 10.11 could be replaced with a similar arg ${SDK_VERSION}? However, it's not defined in the ARG section above, but it's already defined in go/darwin/Dockerfile.tmpl

[rowlandgeoff]

Oh good catch! It looks like through my copy/paste that I changed which SDK version was getting used here. Will fix.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 46617a2

History

• 💚 Build #559 succeeded 6b2b78d
• 💚 Build #558 succeeded e2fd8e2
• 💚 Build #551 succeeded 4901395
• 💚 Build #550 succeeded eb05571
• 💚 Build #549 succeeded 52afa62
• 💚 Build #548 succeeded 8074083

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 46617a2

History

• 💚 Build #559 succeeded 6b2b78d
• 💚 Build #558 succeeded e2fd8e2
• 💚 Build #551 succeeded 4901395
• 💚 Build #550 succeeded eb05571
• 💚 Build #549 succeeded 52afa62
• 💚 Build #548 succeeded 8074083

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 46617a2

History

• 💚 Build #660 succeeded 6b2b78d
• 💚 Build #659 succeeded e2fd8e2
• 💚 Build #652 succeeded 4901395
• 💔 Build #651 failed eb05571
• 💔 Build #650 failed 52afa62
• 💔 Build #648 failed 1f26f78

[rowlandgeoff]

@v1v I see you closed the 1.16 backport, 1.17-1.19 don't seem to have backport PRs, and 1.20/1.21 are failing. Which versions do we need to support on this repo?

[v1v]

@v1v I see you closed the 1.16 backport, 1.17-1.19 don't seem to have backport PRs, and 1.20/1.21 are failing. Which versions do we need to support on this repo?

I saw 1.17-1.19 were not created but I didn't investigate the reason why mergify didn't create them.

I think old branches might be affected by #444 and those branches are already EOL.

For Golang, we only support the latest minor and previous minor, so 1.23 and 1.22 are the currently supported branches, and 1.23 is the one in main.

I initially wanted to replace the Google bucket reference in the old branches, but I think we have never needed to build an EOL branch.

Because backporting and fixing EOL branches is of little value, I think we are good with the current backports. We can close 1.20 and 1.21.

[v1v]

I see you closed the 1.16 backport

BTW, sorry If I was too enthusiastic and unclear about the rationale 🙇

[rowlandgeoff]

Thanks very much. I closed 1.20 & 1.21. Appreciate the help. 🙇