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

Show who broke the build (via <Messages/>) #296

Open
gpaul-idexx opened this issue Nov 8, 2019 · 1 comment
Open

Show who broke the build (via <Messages/>) #296

gpaul-idexx opened this issue Nov 8, 2019 · 1 comment
Labels
ci specific Changes related to a specific CI server, please specify which in the issue description new feature A new feature

Comments

@gpaul-idexx
Copy link

Feature Request

What would you like to be able to do?
I'd like to be able to display who broke the build. Our team is friendly, and we'd like to add a little blame and shame to the mix for whoever broke the build.

What problem would it solve?
It's often helpful to know who broke the build to know who should be most focused on fixing it, and who likely knows best why it's broken.

We're using GoCD. My understanding is that GoCD includes a message in the cctray with a "breakers" attribute to identify who caused the breakage.

@gpaul-idexx gpaul-idexx added the new feature A new feature label Nov 8, 2019
@GentlemanHal GentlemanHal added the ci specific Changes related to a specific CI server, please specify which in the issue description label Nov 9, 2019
@GentlemanHal
Copy link
Member

Hi @gpaul-idexx, thanks for raising this feature request!

Messages are a non standard feature that was never defined in the CCTray XML spec and I've only ever seen GoCD use it. This is why we haven't prioritised showing them up until now.

We'll have to have a think about how we want to handle CI specific settings.

@GentlemanHal GentlemanHal changed the title Show who broke the build Show who broke the build (via <Messages/>) Nov 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci specific Changes related to a specific CI server, please specify which in the issue description new feature A new feature
Projects
None yet
Development

No branches or pull requests

2 participants