Skip to content

smoke: update latest version scripts to use snapshots.elastic.co #17377

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

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

Conversation

isaacaflores2
Copy link
Contributor

Motivation/summary

Updating scripts to migrate away fromartifacs-api.elastic.co. This should Improve smoke test reliability since artifacts-api.elastic.co is not always available

Note there are two alternate APIs we can use:

  1. https://artifacts-snapshot.elastic.co/ is used for the DRA artifacts and manifests produced by developments team
    • This one seems to be updated more frequently
  2. https://snapshots.elastic.co/ is used for the daily unified-release-snapshot builds

Since the smoke test runs once a day, I think both are fine. I opted for snapshots.elastic.co since it used for the snapshot builds. Please let me know if you think we should use artifacts-snapshot.elastic.co instead.

Checklist

For functional changes, consider:

  • Is it observable through the addition of either logging or metrics?
  • Is its use being published in telemetry to enable product improvement?
  • Have system tests been added to avoid regression?

How to test these changes

  1. Ran the both scripts locally
  2. Ran the smoke test workflow against the updated branch
image

Related issues

Closes #17071

…s-api.elastic.co`to get the apm-server and elastic agent download urls

Improve smoke test reliability since `artifacts-api.elastic.co` is not always available
@isaacaflores2 isaacaflores2 requested a review from a team as a code owner June 25, 2025 21:42
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

Copy link
Contributor

mergify bot commented Jun 25, 2025

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

  • backport-7.17 is the label to automatically backport to the 7.17 branch.
  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
  • backport-9./d is the label to automatically backport to the 9./d branch. /d is the digit.
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@isaacaflores2 isaacaflores2 added backport-8.17 Automated backport with mergify backport-8.18 Automated backport to the 8.18 branch backport-9.0 Automated backport to the 9.0 branch backport-8.19 Automated backport to the 8.19 branch labels Jun 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.17 Automated backport with mergify backport-8.18 Automated backport to the 8.18 branch backport-8.19 Automated backport to the 8.19 branch backport-9.0 Automated backport to the 9.0 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

smoke: Get elastic agent and apm version scripts failing
1 participant