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

Combine artifacts from two workflows (in Github and Gitlab) #457

Merged
merged 3 commits into from
Jul 4, 2024

Conversation

jakob-fritz
Copy link
Collaborator

This means, that now coverage-reports can now be aggregated for runs on Github-Runners and on HPC machines (via Gitlab)

And start a third workflow afterwards. This third workflow takes care of the post-processing and generation of the website. The website is only uploaded when triggered as push from the master-branch (as before). However, the yaml-file for the workflow is always read from the master branch. Therefore, updates to that file take effect only after merging into master. This is a limitation by Github; not a personal choice.

@jakob-fritz jakob-fritz requested a review from pancetta July 4, 2024 08:53
@jakob-fritz jakob-fritz self-assigned this Jul 4, 2024
@pancetta
Copy link
Member

pancetta commented Jul 4, 2024

Hm. So, the composition of the artifacts now happens on Gitlab, yes? Are there any drawbacks?

@jakob-fritz
Copy link
Collaborator Author

No, the composition of artifacts happens in Github, but in the workflow, that takes care of the syncing with Gitlab.

@pancetta pancetta merged commit ab53b51 into master Jul 4, 2024
168 of 170 checks passed
@jakob-fritz jakob-fritz deleted the combine_artifacts branch July 4, 2024 11:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants