CCMenu shows the status of builds on CI/CD servers in the menu bar.
It started as part of the CruiseControl project that built the first CI server.
Get a summary of the status of all builds with a quick glance to the menu bar. Notice when a build is running or is broken.
See the status of individual build pipelines in the menu. Arrange items in your preferred order. Display extra information.
Open the build's web page on the server by clicking the menu item.
CCMenu works with GitHub Actions and servers that provide a feed in the CCTray format. Add your voice to this discussion about which other servers should be supported in the future.
Clicking on a pipeline in the menu opens the link given to CCMenu by the server. Problems like the wrong page opening, port missing, or incorrect URL scheme must be fixed on the server.
Get more detailed information about the last build and commit, and edit the list of pipelines in the pipeline window.
Receive notifications when a build starts and finishes. Check estimated time remaining for running builds.
The estimated build time is based on the last build. If that failed quickly, the estimate won't be accurate.
Feeds in CCTray format don't contain build duration information. For these feeds CCMenu times the builds as they occur, and only displays a timer once it has seen a complete build.
The status of the pipelines is shown with the following icons:
Most recent build was successful.
Most recent build failed.
Currently building. Previous build was successful.
Currently building. Build was broken before.
Pipeline is disabled or waiting for a build agent or waiting for approval.
Status unavailable
In the menu bar running builds are shown with highest priority, broken builds with second highest.
Add workflows by owner (user or organisation) and repository. You can choose to monitor all branches or a specific one.
Sign in at GitHub to access private repositories. CCMenu will start a flow so that you can authorise it as an OAuth app on GitHub.
Unfortunately, the scopes for OAuth apps are broad, as discussed here. CCMenu only performs read operations. You can see its full use of the GitHub API in this class.
The authentication token is stored securely in the macOS keychain.
Add projects from a CCTray feed. In most cases you only have to enter the hostname and port and CCMenu will discover the full feed URL. If this doesn't work you have to provide the full URL.
You can enter credentials for HTTP Basic auth if the feed is protected in this way. Currently, no other authentication mechanisms are supported.
Passwords are stored securely in the macOS keychain.