Skip to content

Ignore beats artifacts when resolving all artifact dependencies #88960

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

Merged
merged 1 commit into from
Jul 29, 2022

Conversation

mark-vieira
Copy link
Contributor

After version bumps due to releases or feature freeze, snapshot versions of beats artifacts may not be published for some time. During that time attempts to run resolveAllDependencies to seed our CI worker images will fail, meaning they'll be out of date. We don't really need to seed these images with snapshot dependencies that are likely to change anyhow so let's just ignore them.

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-delivery (Team:Delivery)

@mark-vieira
Copy link
Contributor Author

@elasticmachine run elasticsearch-ci/packaging-tests-unix-sample

@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
7.17
8.3
8.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure >non-issue Team:Delivery Meta label for Delivery team v7.17.6 v8.3.4 v8.4.0 v8.5.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants