We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Getting the following error: at repo-mr resource:
repo-mr
resource script '/opt/resource/check []' failed: exit status 5 stderr: jq: error (at <stdin>:1): Cannot index object with number
I am setting the following pipeline. The pipeline gets created successfully.
resource_types: - name: merge-request type: docker-image source: repository: mastertinner/gitlab-merge-request-resource resources: - name: repo-mr type: merge-request source: uri: ((repo-uri)) private_token: ((repo-private-token)) username: ((username)) password: ((password)) jobs: - name: test-merge-request plan: - get: repo resource: repo-mr trigger: false - put: repo-mr params: repository: repo status: running on_failure: put: repo-mr params: repository: repo status: failed on_success: put: repo-mr params: repository: repo status: success
A few notes:
uri
username
password
https://git.mycompany.com/username/project.git
private_key
Are there any especial configuration needed on the gitlab side? Would appreciate any help.
The text was updated successfully, but these errors were encountered:
Looks like v3 api is not supported in GitLab v>9.5 according to this
Sorry, something went wrong.
This issue happens to me when there are 0 merge requests on the repo
No branches or pull requests
Getting the following error: at
repo-mr
resource:I am setting the following pipeline. The pipeline gets created successfully.
A few notes:
uri
,username
andpassword
works fine in a separate pipeline with a git resource.uri
format ishttps://git.mycompany.com/username/project.git
password
deliberately and got the same errorprivate_key
either.Are there any especial configuration needed on the gitlab side? Would appreciate any help.
The text was updated successfully, but these errors were encountered: