With dual monitors its sometimes hard to see when a notification pops up in the corner, I'm like a horse with blinds on sometimes and I would love to be able to have a bigger notification or be able to turn the entire screen red, for just a second or two when the build fails that way I can jump right on it instead of having to check the corner.
When giving Catlight it's own desktop to use in full screen dashboard view, the dashboard will move to it's own space after clicking on a toolbar notification.
Logging back into Macbook Pro from sleep mode, the full screen dashboard & Catlight in general freezes; It requires activity monitor manual forced exit to correct. I've tested just stretching the Catlight window til almost to full screen & no freezing.
In the dashboard, there are no difference between disabled build def's with last build broken, and active build def's with last build broken, which Means, we cannot distinguish between the failed builds to work on, and which to not work on.
We have about 10 out of 50 build definitions that are disabled due to old legacy-issues, and which we do not want to remove, because of future need to activate them.
We had a developer that broke a number of builds and kept trying (without investigating). Because they shouldn't have even created the CI builds directly, I removed them in the VSTS build page but now Catlight still shows them all as broken and attempts to refresh are not removing them. Seems Catlight should remove build status for builds that no longer exist.
If you have a problem with the app, you can inspect application logs. They will often provide a detailed description of the problem, and can also point to the specific project or build that is causing trouble.
Logs are written in two groups of files:
Log.txt - this is the log file of background process that contains most of the app logic. It is usually most useful, check it first
TrayLog.txt - this is a log file of UI process. If the application does not start, this log can contain details about the problem.
If your build server is using self-signed certificate, CatLight may not be able to connect and will show a message like "SSL connect error". This happens because 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.
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