-
Notifications
You must be signed in to change notification settings - Fork 43
fix gh artifacts upload with the latest action version #2605
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
base: main
Are you sure you want to change the base?
Conversation
2b4d400
to
e660e1b
Compare
📊 Allure Report - 💚 No failures were reported.
|
33bfd20
to
3141051
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why backport to 8.15?
@oren-zohar because currently the |
b768b00
to
89046cb
Compare
89046cb
to
367b406
Compare
@moukoublen With the last push 4 months ago, is this still pertinent, or can we close? |
This pull request is now in conflicts. Could you fix it? 🙏
|
Summary of your changes
It seems that after a version update of upload-artifact something is wrong when we give a folder as a path to upload.
In our CI, we upload the produced Docker images as artifacts, which are later downloaded and used for kspm testing.
I didn't investigate the action code to find out why, but as a workaround, I changed the upload path from folder to wildcard pattern, and it works.
Screenshot/Data
https://github.com/elastic/cloudbeat/actions/runs/11340902754?pr=2605
Related Issues
Checklist
Introducing a new rule?