Skip to content

bug(ci): uploaded artefacts not pinned to specific GCC version #1044

@gnikit

Description

@gnikit

With the introduction of multiple GCC versions in our CI/CD pipelines we ended up in a situation where the upload/download artefacts have the same name and consequently the upload/download (v3) GitHub Actions would pick the last created artefact as the one to be listed in our CD and Release Notes. Which artefact is generated last varies from run to run.

This currently works because there are no (major?!) ABI changes between GFortran 10 through 12, however we can't expect this to always be the case.

This issue was originally uncovered as part of the dependabot PR #985, where now upload artefacts must have unique names.

I propose that for the time being the artefacts that we provide as part of our CD are based on the oldest supported version of GFortran, in this case GFortran-10. @awvwgk and @perazz any thoughts on this?

This should get fixed as part of #985.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions