GitLab Pipeline Monitor
This extension monitors your GitLab Pipelines
(Fork and fusion of balazs4/gitlab-pipeline-monitor and Jameswain/gitlab-pipelines)
Features
Status bar item showing the latest pipeline state:
Tree view showing multiple recent pipelines in the Explorer view
Clickable pipelines - opens in browser when clicked
Requirements
The extension gets activated only if the workspace contains a .gitlab-ci.yml file.
Extension Settings
if you are using the previous config format, it is highly recommended to manually migrate it to the new format. The old config should work, but it is not supported anymore.
You can configure the settings per gitlab deployment.
There is only one mandatory parameter in each section: token.
Any other parameter has a default/fallback value if you do not define it.
"gitlabPipelineMonitor": {
"<origin-domain>": {
"token": "<my-private-token>", // MANDATORY
"notifyOnFailed": false, // optional, default: false
"apiUrl": "https://<origin-domain>/api/v4", // optional, default: https://<origin-domain>/api/v4
"interval": 10000, // optional, default: 10000 milliseconds
"forcedBranch": null, // optional, default: null - override branch for API requests
"maxPipelines": 20 // optional, default: 20 - number of pipelines to show in tree view
},
"gitlab.com" : {
"token": "gitlab-private-token"
},
"my.internal.gitlab.instance.com:29418": {
"token": "my-internal-token",
"apiUrl": "https://my.internal.gitlab.instance.com/api/v4"
}
},
how to create Gitlab Personal Access Token with api scope
Hint: If you are using private gitlab deployment with self-signed cert, you should set the http.proxyStrictSSL to false. More details: https://gitlab.com/vbtheory/gitlab-pipeline-monitor-advanced/issues/3
Author
vbtheory
Release Notes
https://gitlab.com/vbtheory/gitlab-pipeline-monitor-advanced/tags
License
MIT
