semantic-release / semantic-release/gitlab
[Question] semantic release GitLab error when self signed certificates are used.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 344
- Forks
- 89
- Avg merge
- 16h 11m
- Merged PRs (30d)
- 4
Description
I am not able to use self-signed certificates using this plugin.
Version: "@semantic-release/gitlab": "13.1.0",
Error:
UNABLE_TO_GET_ISSUER_CERT
I have tried to set next variables:
variables:
GIT_SSL_NO_VERIFY: 1
NODE_OPTION: --use-openssl-ca
NODE_EXTRA_CA_CERTS: /etc/ssl/certs/ca-certificates.crt
NODE_TLS_REJECT_UNAUTHORIZED: 0
NO_PROXY: {my.gitlab.com}
Certs are installed in the container
COPY *.crt /usr/local/share/ca-certificates/
RUN update-ca-certificates
Error:
[3:45:01 PM] [semantic-release] › ℹ Start step "verifyConditions" of plugin "@semantic-release/gitlab"
[3:45:01 PM] [semantic-release] [@semantic-release/gitlab] › ℹ Verify GitLab authentication (/api/v4)
[3:45:01 PM] [semantic-release] › ✘ Failed step "verifyConditions" of plugin "@semantic-release/gitlab"
[3:45:01 PM] [semantic-release] › ✘ An error occurred while running semantic-release: RequestError: unable to get issuer certificate
at ClientRequest.<anonymous> (node_modules/got/dist/source/core/index.js:670:107)
at Object.onceWrapper (node:events:633:26)
at ClientRequest.emit (node:events:530:35)
at TLSSocket.socketErrorListener (node:_http_client:500:9)
at TLSSocket.emit (node:events:518:28)
at emitErrorNT (node:internal/streams/destroy:169:8)
at emitErrorCloseNT (node:internal/streams/destroy:128:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
at TLSSocket.onConnectSecure (node:_tls_wrap:1674:34)
... 2 lines matching cause stack trace ...
at ssl.onhandshakedone (node:_tls_wrap:871:12) {
input: undefined,
code: '**UNABLE_TO_GET_ISSUER_CERT**',
I would appreciate any suggestion how to use self-signed certificates.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the @semantic-release/gitlab 13.1.0 verifyConditions step that requests the GitLab /api/v4 endpoint, then reproduce the UNABLE_TO_GET_ISSUER_CERT error with the reported container certificate setup. Done means determining whether self-signed certificates are supported and documenting or addressing the required configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, javascript, nodejs
- Domain
- devops, release, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100