Closed af8 closed 4 years ago
Or perhaps @pditommaso a new variable (group or path or subpath ...) can be created in scm gitlab config :
providers {
gitlab_au_v2 {
server = 'https://gitlab.com'
group = 'auragen/dev'
platform = 'gitlab'
user = 'af8'
password = 'xxxxxxxxxxxx'
token = 'xxxxxxxxxxxx'
}
}
Then group
value can be used to correctly build the endpoint path.
In this case I would run :
nextflow run -hub gitlab_au_v2 pipelines/testlab-nf
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I just ran into this problem as well. Can the issue be re-opened please? I wanted to run
nextflow pull https://gitlab.com/<org>/<project>/<repo>
and then get an error
Remote resource not found: https://gitlab.com/api/v4/projects/<org>%2F<project>%2F<repo>
Hi @Midnighter ,
Could you please make sure that the both password
and token
fields are specified correctly?
If this doesn't work, could you please tell us which version of Nextflow are you using. Output of nextflow info
would be ideal :)
Hi,
Thanks for the message. I have changed my ~/.nextflow/scm
config to contain:
providers {
gitlab {
user = 'Midnighter'
password = '<token>'
token = '<token>'
}
}
and now it works 🎉
For future me: I used the same API access token in both fields.
Bug report
I would like to use something like :
nextflow run -hub gitlab auragen/dev/pipelines/testlab-nf ...
to run private nextflow repotestlab-nf
.First I can actually run it successfully if I use the full http address :
But if I try :
I get an error because the code only tolerates two levels of directories, from
AssetManager.groovy
:To try to escape that problem, I have created a scm configuration file containing this :
And then I run :
You see here that the problem is that the end point is not correctly built =>
https://gitlab.com/auragen/dev/api/v4/projects/pipelines%2Ftestlab-nf
So I did not find an easy solution to allow
nextflow run
to work with several subdirs when pulling from gitlab.I think that relaxing a bit the condition in
isValidProjectName
to authorize several levels could be the simple way to go ?Thanks, Anthony
Environment