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

🔧 Migrate GithubAction actions/upload-artifact@v3 from v3 to v4 #181

Closed
Nicoretti opened this issue May 16, 2024 · 0 comments · Fixed by #245
Closed

🔧 Migrate GithubAction actions/upload-artifact@v3 from v3 to v4 #181

Nicoretti opened this issue May 16, 2024 · 0 comments · Fixed by #245
Assignees
Labels
bug Unwanted / harmful behavior refactoring Code improvement without behavior change
Milestone

Comments

@Nicoretti
Copy link
Member

Summary

Migrate the use of GithubAction actions/upload-artifact@v3 from v3 to v4. This process will entail addressing significant semantic changes.

Details

It's important to note that there are considerable semantic differences between these versions. The same file/artifact name, for example, cannot be uploaded multiple times without triggering an error in v4. This e.g. is an issue with the current matrix build setup. Even if the overwrite option is set to true, behaviors still seem to vary. It looks like each uploaded file gets individual download URLs that can get mixed up, causing errors when trying to download the artifact.

In order to perform the migration, two alternatives are recommended. Firstly, we could run a job solely for collecting metrics, which also handles the single-time upload. Secondly, we could integrate a check before uploading the artifact(s) in the runs.

References

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unwanted / harmful behavior refactoring Code improvement without behavior change
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant