Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Support Github Actions #109

Open
fjcaetano opened this issue Nov 5, 2019 · 5 comments
Open

[Feature Request] Support Github Actions #109

fjcaetano opened this issue Nov 5, 2019 · 5 comments

Comments

@fjcaetano
Copy link

Considering Github Actions are publicly available now, it'd be interesting to support it.

@paulz
Copy link

paulz commented Jun 3, 2020

Please add support for GitHub Actions, thank you!

@egpbos
Copy link

egpbos commented Jun 29, 2020

Do you see any available options for including this support? Does Actions have any suitable API for this?

@paulz
Copy link

paulz commented Jun 29, 2020

There are couple of GitHub API: statuses and checks.

Another available option is to use badge svg, which is essentially XML file:
For example our project badge:

https://github.com/sparta-science/connect/workflows/self-hosted-test/badge.svg

is in a text format looks like:

<tspan x="4" y="14">passing</tspan>

which contains status, in this case: passing
or could be failing, running, etc

@erikdoe
Copy link
Member

erikdoe commented Jun 30, 2020

There have been several requests over the years to support CI systems that don't provide their build status in cctray format. At the same time, CCMenu is written around this format and it would take some effort to support other APIs.

My argument is that I'd rather see the organisations and teams behind the CI systems put in the effort to provide their build status in cctray format, which has been a documented, simple-to-implement de-facto standard for almost 20 years. That way other tools that understand the cctray format would benefit, too. And, to be honest, I'm looking after CCMenu in my spare time and I'm not super excited about spending time to write code to consume a number of similar but subtlely different APIs. Sometimes this isn't even an option because there might not be publicly accessible test system. And, last but not least, based on my experience, these APIs tend to change and when that happens I'd have a bunch of unhappy users who'd want me to implement the required changes in a timely manner, which is something I can't promise.

I guess the way forward (other than lobbying the teams behind the CI systems to support the cctray format) is to make CCMenu more modular so it becomes easy for outside contributers to create plug-ins for different APIs. Not sure how feasible that would be with the existing codebase, and how many people would really provide plug-ins for other CI servers.

@ahvigil
Copy link

ahvigil commented Dec 9, 2020

there is a feature request with github to support cctray formatted statuses
https://github.community/t/feature-request-publish-workflow-status-in-cctray-format-xml/16815

@ccmenu ccmenu deleted a comment from ospfranco May 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants