If your build server is using a self-signed certificate, CatLight may not be able to connect and will show a message like "SSL connect error". This happens because the SSL certificate of your server is not trusted by your operating system. 

Add this certificate as trusted to resolve the problem, and try connecting again.

Instructions for Windows: https://blogs.technet.microsoft.com/sbs/2008/05/08/installing-a-self-signed-certificate-as-a-trusted-root-ca-in-windows-vista/ 

For OS X: http://www.robpeck.com/2010/10/google-chrome-mac-os-x-and-self-signed-ssl-certificates 

For Linux: http://askubuntu.com/questions/530056/install-root-certificate-on-ubuntu-14-04-64-bit 

I want to put this on a huge screen in my office.   With big text and big green/red squares.  How do I do that?   How can I zoom?

Sometimes the build is going to be red or yellow for a while. In CatLight 2.8, you can acknowledge it in context menu and focus on other builds.

You can use this feature to see up-to date status of other builds in a tray icon. When all broken builds are acknowledged, tray icon will show a yellow outline cat. If new build breaks down, tray icon will turn a solid yellow or red. This will remind you that you have new things to fix.

Other changes in this release:

• Performance optimizations for Work Item monitoring in

CatLight notifier works with the following servers:

• TFS 2022+, 2020, 2019, 2017, 2015, 2013. Azure DevOps Server. Work item monitoring is available only for TFS 2015+
• Azure DevOps / VSTS
• Jenkins 1.644 (released in early 2016) and newer. Jenkins 2.x is also supported
• TeamCity 8 and newer
• Travis CI (open source and pro). For enterprise - vote on this idea.
• Appveyor (open source, pro and premium)
• GitLab
• GitHub Enterprise and public GitHub
• Jira (on-prem and cloud version)

You can also create an extension for your favorite server using this open protocol, and CatLight will work with it too.

By default, CatLight can show you a lot of notifications, so that you can see how the app works.

To change this, go to the edit menu/settings.

For long-term use you can make the following changes

• Notifications
  • Choose "My Builds" to see less notifications. You can still see the statuses of all monitored builds in the  tray.
  • Uncheck "Show notifications when I change a work item"
• Dashboard
  • Check "Don't show work item changes that I made myself"
• Branches
  • Choose "Track My Branches"

CatLight works with GIT branches. It will show a separate build history for each branch and pull request.

 We divide branches in four categories:

• Primary - they will be always visible on the dashboard. They include branches like master, develop, trunk, etc.
• Short-lived - those are branches for pull requests. CatLight will show them for one day on the dashboard.
• Other - this is a category for feature, bugfix and release branches. They will be tracked while they are active, and had at least one build in the past week.
• Ignored - those branches will not be monitored. You can

CatLight can monitor work items (tasks & bugs) in a TFS/VSTS project. It will notify you about the changes and show the current status in tray.

You can use existing work item queries to select tasks and bugs that you want to monitor. Choose one of two modes:

• Show all - use this for queries that should return empty result when everything is OK, and for queues of short-term work. For example: “Important open bugs”, “Urgent tasks”, “Bugs to verify today”, “Bugs to review”.
• Show changes - use this to track changes in long-term queues of work, like “My tasks”,

CatLight Protocol 1.0 is an open standard for continuous delivery servers. The CatLight app can now connect to any server that implements this protocol.

The new protocol is a replacement for the obsolete cc.xml format that was created over a decade ago, and no longer meets the feature set of modern build systems.

CatLight protocol has native support for branches, folders, consistent build history, authentication, caching and selective loading. It provides enough information for CatLight app features like build investigations, automatic branch tracking and personalized build dashboard.

We invite developers of continuous delivery servers to implement this protocol to get an amazing

When a build is broken, all team members will see a button inviting them to investigate the build and fix it.

When the build is being investigated, the tray icon will change to its acknowledged state for the whole team.

  =>  

Build investigation status is displayed on the dashboard.

After the build is fixed, the investigation will be automatically removed.

Build investigations expire in 24 hours. So, if someone pressed the button and forgot about it, CatLight will raise an alarm on the next day.

This feature is available for all continuous integration servers that we support. User need

Show them with a separate build record, like a branch

The jobs are listed correctly in the interface but when I click on a job link, I'm redirected to the slave URL instead.

Expected URL destination: http://master-server/jenkins/job/myjob/56 (using nginx reverse proxy)

I got instead: http://myslave-server:8080/job/myjob/56 which doesn't exist (error 404)

Thanks.

We have a new Jenkins adapter implementation in CatLight 2.7. It has several improvements:

• Faster polling times when only small number of jobs is monitored.
• Reduced server load on Jenkins server that has hundreds of jobs.
• Better integration with Multibranch Pipeline and GitHub organization plugins. CatLight will now show branch-jobs as branches. You can select top-level job in monitoring settings, and CatLight will automatically monitor child jobs for active branches. You can fine-tune branch monitoring in global app settings.

It would be nice if CatLight opened Blue Ocean view of the Jenkins build. It could be a configuration option (when creating a Jenkins connection) whether one wants to use Blue Ocean or Classic view.

When work item query is acknowledged, CatLight marks all work items as read and remembers their state. If you use "show changes" mode, the app will hide all acknowledged work items. If you use "show all" mode, they will no longer be bold. 

When work item changes in TFS, it will be marked as new and it will re-appear on the dashboard.

Work item is acknowledged automatically when you click on it.

When all work items are acknowledged, and there are no more alerts, tray icon will change from a solid cat to an outline.

All those changes happen in the

Is it possible to make UI better visible from distance? Tiny green or red squares are only visible on close-up inspection, and not appropriate for display in a wider area.

Introducing CatLight Protocol 1.0 - an open standard for continuous delivery servers. CatLight app can now connect to any server that implements this protocol.

New protocol is a replacement for obsolete cc.xml format that was created over a decade ago, and no longer meets the feature set of modern build systems.

CatLight protocol has native support for branches, folders, consistent build history, authentication, caching and selective loading. It provides enough information for CatLight app features like build investigations, automatic branch tracking and personalized build dashboard.

We invite developers of continuous delivery servers to implement this protocol to

Hello, 

I love your product, but when opening the dashboard it is very difficult to see the short history represented by Red and Green boxes. It would be extremely helpful if the colors could be modified in the dashboard so we could use something custom, for example a blue/red combo (like jenkins) to be able to see clearly.

Thanks for your consideration,

Craig 

Hi there!

Would it be possible that CatLight adds new builds jobs from a Jenkins folder automatically?

We are using the Jenkins "Pipeline Multibranch Plugin" (https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Multibranch+Plugin) to build various git branches, which adds every branch build to a folder

Christian

CatLight 2.5 now works with Git branches, and will show a separate build history for each branch.

We divide branches in four categories:

• Primary - they will be always visible on the dashboard. They include branches like master, develop, trunk, etc.
• Short-lived - those are branches for pull requests. CatLight will show them for one day on the dashboard.
• Other - this is a category for feature, bugfix and release branches. They will be tracked while they are active, and had at least one build in the past week.
• Ignored - those branches will not be monitored. You can hide