You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm facing an issue when i get a 404 error whenever i try to create a new scm plugin entry.
The plugin only works with "simple" urls but don't want to work when the repo si within a subgroup in gitlab.
The plugin currently can only handle urls like these : protocol / host / username / repo seeing the algorithm in the method parseGithubUrl.
But a url like this is a perfectly valid gitlab url : protocol / host / group1/ subgroup1 / subgroup2/ repo
The code could be fixed to try to account for that but why can't we just provide the project id as an additional parameter considering that the Gitlab api client can handle it and that that information is readily available in the gitlab interface ?
I don't know the full consequences of replacing the project url parameter but i think it would be less intrusive to add an optional parameter with the project id.
If i want to make a contribution is there some documentation i could follow since the issue is quite pressing for me?
The text was updated successfully, but these errors were encountered:
Hi,
I'm facing an issue when i get a 404 error whenever i try to create a new scm plugin entry.
The plugin only works with "simple" urls but don't want to work when the repo si within a subgroup in gitlab.
After reviewing the code of https://github.com/ashwanthkumar/gocd-build-github-pull-requests/blob/master/src/main/java/in/ashwanthkumar/gocd/github/provider/gitlab/GitLabProvider.java and
gocd-build-github-pull-requests/src/main/java/in/ashwanthkumar/gocd/github/provider/github/GHUtils.java
Line 24 in 12df905
The plugin currently can only handle urls like these : protocol / host / username / repo seeing the algorithm in the method parseGithubUrl.
But a url like this is a perfectly valid gitlab url : protocol / host / group1/ subgroup1 / subgroup2/ repo
The code could be fixed to try to account for that but why can't we just provide the project id as an additional parameter considering that the Gitlab api client can handle it and that that information is readily available in the gitlab interface ?
I don't know the full consequences of replacing the project url parameter but i think it would be less intrusive to add an optional parameter with the project id.
If i want to make a contribution is there some documentation i could follow since the issue is quite pressing for me?
The text was updated successfully, but these errors were encountered: