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.

Sign up for GitHub

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

Jump to bottom

gitlab: allow configuring custom alternative path to reana.yaml #510

Open
tiborsimko opened this issue Jul 5, 2022 · 0 comments
Open

gitlab: allow configuring custom alternative path to reana.yaml #510

tiborsimko opened this issue Jul 5, 2022 · 0 comments
Labels
community/eoscfuture integration/gitlab REANA-GitLab integration issues.

Comments

@tiborsimko
Copy link
Member

Current behaviour

Currently, when using REANA as a CI in the GitLab <-> REANA integration, the workflow expects reana.yaml in the root directory of the repository. It does not seem possible to specify an alternative file, for example reana-snakemake.yaml in case of RooFit demo.

Expected behaviour

It would be useful to allow specifying alternative file location to reana.yaml in the root of the repository. This would be akin to to specifying custom CI/CD configuration file that GitLab offers.
@tiborsimko tiborsimko added community/eoscfuture integration/gitlab REANA-GitLab integration issues. labels Jul 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
community/eoscfuture integration/gitlab REANA-GitLab integration issues.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tiborsimko