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
We have the OnPrem Azure DevOps server and try to use the semantic release in Azure Pipelines. Our Azure DevOps server work over http (not https).
I've tried to create semantic-release step based on this article: https://www.eriklieben.com/posts/semantic-release-nuget/ and semantic-release-ado plugin description: https://github.com/lluchmk/semantic-release-ado. For authentication I've used the GIT_CREDENTIALS environment variable with $(System.AccessToken) value and custom generated PAT (and without any GIT_CREDENTIALS variable). In any case I've got the authentication error: fatal: Authentication failed (full log provided bellow in this post)
Semanti-release step in Azure DevOps pipeline definition:
at async run (E:\build-agent4\_work\35\s\node_modules\semantic-release\index.js:55:27)
at async module.exports (E:\build-agent4\_work\35\s\node_modules\semantic-release\index.js:257:22)
at async module.exports (E:\build-agent4\_work\35\s\node_modules\semantic-release\cli.js:55:5)
[11:14:15] [semantic-release] » × An error occurred while running semantic-release: Error: Command failed with exit code 128: git ls-remote --heads [http://[secure]@my_repo_url](http://%5Bsecure%5D@my_repo_url)
fatal: Authentication failed for 'http://my_repo_url/'
at makeError (E:\build-agent4\_work\35\s\node_modules\semantic-release\node_modules\execa\lib\error.js:59:11)
at handlePromise (E:\build-agent4\_work\35\s\node_modules\semantic-release\node_modules\execa\index.js:114:26)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async getBranches (E:\build-agent4\_work\35\s\node_modules\semantic-release\lib\git.js:66:11)
at async module.exports (E:\build-agent4\_work\35\s\node_modules\semantic-release\lib\branches\expand.js:6:23)
at async module.exports (E:\build-agent4\_work\35\s\node_modules\semantic-release\lib\branches\index.js:14:26)
at async run (E:\build-agent4\_work\35\s\node_modules\semantic-release\index.js:56:22)
at async module.exports (E:\build-agent4\_work\35\s\node_modules\semantic-release\index.js:257:22)
at async module.exports (E:\build-agent4\_work\35\s\node_modules\semantic-release\cli.js:55:5) {
shortMessage: 'Command failed with exit code 128: git ls-remote --heads [http://[secure]@my_repo_url',](http://%5Bsecure%5D@my_repo_url',)
command: 'git ls-remote --heads [http://[secure]@my_repo_url',](http://%5Bsecure%5D@my_repo_url',)
exitCode: 128,
signal: undefined,
signalDescription: undefined,
stdout: '',
stderr: "fatal: Authentication failed for '[http://my_repo_url/'",](http://my_repo_url/'%22,)
failed: true,
timedOut: false,
isCanceled: false,
killed: false
}
Error: Command failed with exit code 128: git ls-remote --heads [http://[secure]@my_repo_url](http://%5Bsecure%5D@my_repo_url)
fatal: Authentication failed for 'http://my_repo_url/'
at makeError (E:\build-agent4\_work\35\s\node_modules\semantic-release\node_modules\execa\lib\error.js:59:11)
at handlePromise (E:\build-agent4\_work\35\s\node_modules\semantic-release\node_modules\execa\index.js:114:26)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async getBranches (E:\build-agent4\_work\35\s\node_modules\semantic-release\lib\git.js:66:11)
at async module.exports (E:\build-agent4\_work\35\s\node_modules\semantic-release\lib\branches\expand.js:6:23)
at async module.exports (E:\build-agent4\_work\35\s\node_modules\semantic-release\lib\branches\index.js:14:26)
at async run (E:\build-agent4\_work\35\s\node_modules\semantic-release\index.js:56:22)
at async module.exports (E:\build-agent4\_work\35\s\node_modules\semantic-release\index.js:257:22)
at async module.exports (E:\build-agent4\_work\35\s\node_modules\semantic-release\cli.js:55:5) {
shortMessage: 'Command failed with exit code 128: git ls-remote --heads [http://[secure]@my_repo_url'](http://%5Bsecure%5D@my_repo_url'),
command: 'git ls-remote --heads [http://[secure]@my_repo_url'](http://%5Bsecure%5D@my_repo_url'),
exitCode: 128,
signal: undefined,
signalDescription: undefined,
stdout: '',
stderr: "fatal: Authentication failed for '[http://my_repo_url/'"](http://my_repo_url/'%22),
failed: true,
timedOut: false,
isCanceled: false,
killed: false
The text was updated successfully, but these errors were encountered:
andy-mishechkin
changed the title
Symantic-Release can't access to Azure DevOps OnPrem server Git - fatal: Authentication failed
Semantic-Release can't access to Azure DevOps OnPrem server Git - fatal: Authentication failed
Mar 1, 2024
Current behavior
We have the OnPrem Azure DevOps server and try to use the semantic release in Azure Pipelines. Our Azure DevOps server work over http (not https).
I've tried to create semantic-release step based on this article: https://www.eriklieben.com/posts/semantic-release-nuget/ and semantic-release-ado plugin description: https://github.com/lluchmk/semantic-release-ado. For authentication I've used the GIT_CREDENTIALS environment variable with $(System.AccessToken) value and custom generated PAT (and without any GIT_CREDENTIALS variable). In any case I've got the authentication error: fatal: Authentication failed (full log provided bellow in this post)
Semanti-release step in Azure DevOps pipeline definition:
package.json of our project:
Expected behavior
Semantic-release step should be successfully authenticated on Azure DevOps Server Git
semantic-release
version20.1.0
CI environment
Azure DevOps Server 2020 Update 1.1 OnPrem
Plugins used
@semantic-release/commit-analyzer
@semantic-release/npm
@semantic-release/git
semantic-release
configurationWe use the .releaserc.yaml for semantic-release parameters definition:
CI logs
The text was updated successfully, but these errors were encountered: