Skip to content

Conversation

@fabioseel
Copy link
Contributor

I need this PR for dev already to see if the pull workflow now works

@fabioseel fabioseel linked an issue Nov 5, 2025 that may be closed by this pull request
2 tasks
@fabioseel fabioseel force-pushed the 88-fix-ci-pipeline-cache-for-singularity-container branch from 6e90122 to 4ff0282 Compare November 5, 2025 20:04
@fabioseel
Copy link
Contributor Author

fabioseel commented Nov 5, 2025

Ok, seems like this fixes #88
minor issue: seems to rebuild now in case of cache miss. But that should happen rarely enough, so i don't mind for now
edit: also fixed

@fabioseel fabioseel merged commit 192f3a6 into master Nov 5, 2025
5 checks passed
@fabioseel fabioseel deleted the 88-fix-ci-pipeline-cache-for-singularity-container branch November 5, 2025 20:18
fabioseel added a commit that referenced this pull request Nov 29, 2025
…93)

* fix: ensure container should always run, but not necessarily rebuild

* fix: rebuild only if needed
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.

Fix CI Pipeline / Cache for Singularity container

2 participants