We are migrating from Jenkins to Gitlab CI. The main pain point that we encounter is the build outcome notification. We don't want to use emails and we are used to CCMenu for years now. It is non intrusive and gives a feedback very fast.
I would think about using api/v4. You are mostly interested in Pipelines I guess. So you are probably looking at: /api/v4/projects/2/pipelines/cc.xml, not at single pipeline.
I'm one of the founders of Nevergreen, it is compatible with cctray formatted xml (cc.xml in your case) outputs so any as long as you provide it a link to the file it should work. If you have any questions or need any help we have a slack channel here: https://nevergreen.slack.com
Hi, I'm very happy to announce the first stable release of gitlab-panorama.
The project aims to provide an overview of the latest gitlab pipeline states in different output formats.
Available output formats are:
ccmenu (Most important for this thread)
html
shell
prometheus
The open-sourced repository can be found here, along with a full documentation of the usage, configuration and available endpoints:
https://github.com/joblift/gitlab-panorama
GitLab is moving all development for both GitLab Community Edition
and Enterprise Edition into a single codebase. The current
gitlab-ce repository will become a read-only mirror, without any
proprietary code. All development is moved to the current
gitlab-ee repository, which we will rename to just gitlab in the
coming weeks. As part of this migration, issues will be moved to the
current gitlab-ee project.
If you have any questions about all of this, please ask them in our
dedicated FAQ issue.
Using "gitlab" and "gitlab-ce" would be confusing, so we decided to
rename gitlab-ce to gitlab-foss to make the purpose of this FOSS
repository more clear
I created a merge requests for CE, and this got closed. What do I
need to do?
Everything in the ee/ directory is proprietary. Everything else is
free and open source software. If your merge request does not change
anything in the ee/ directory, the process of contributing changes
is the same as when using the gitlab-ce repository.
Will you accept merge requests on the gitlab-ce/gitlab-foss project
after it has been renamed?
No. Merge requests submitted to this project will be closed automatically.
Will I still be able to view old issues and merge requests in
gitlab-ce/gitlab-foss?
Yes.
How will this affect users of GitLab CE using Omnibus?
No changes will be necessary, as the packages built remain the same.
How will this affect users of GitLab CE that build from source?
Once the project has been renamed, you will need to change your Git
remotes to use this new URL. GitLab will take care of redirecting Git
operations so there is no hard deadline, but we recommend doing this
as soon as the projects have been renamed.
Where can I see a timeline of the remaining steps?