Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Have the Github integrations been updated?

I noticed when I added Github repository addresses to some of my components that new metric fields (i.e. Build Success Rates) are now being displayed.

Are these new features? If so, is there any documentation surrounding them and how they are populated? Currently, the numbers being returned are unusual (i.e. the build success rates are always 100%, which contrasts with my own results on my Github Workflows).

These features are exactly what I've been looking for and would love to integrate them properly into my work.

1 answer

1 accepted

1 vote
Answer accepted

Hey @John Medina 👋 You've spotted some changes with the GitHub integration that are so fresh we haven't even documented them yet! In recent days we've added some additional metrics that get automatically calculated for components that have a GitHub repository linked. The full list of metrics we calculate for GitHub are:

Metric   How it's calculated When it's calculated 
Open pull requests  Current value Each time a PR is merged to the default branch
PR cycle time  Averaged over the last 10 pull requests Each time a PR is merged to the default branch
Build success rate Averaged over the last 25 builds Each time a build is completed on the default branch
Build time Averaged over the last 10 builds Each time a build is completed on the default branch
Deployment frequency Weekly average for the last 4 weeks Each time a deployment is completed to the production environment

We'd like to help you diagnose what's going on with your build success rate. Just click the "Give feedback" button in the top right navigation of Compass, and we can follow up to help you figure it out.

Glad you are finding these metrics useful!

Hi @Dave Parrish _Atlassian_, I think I figured it out. The failing builds in our workflow all exist in the feature branches, as opposed to our default `master` branch.

I do have a question as to what classifies as a `build` being completed though. Is this tied to the workflow actions being run on the repository's default branch?

Hi @John Medina - Regarding your question about what classifies as a "build" - Yes, you've got it right. Specifically, we're listening for GitHub's workflow_run event, which occurs when a workflow finishes. We only listen to this event on the default branch of the repository. When that happens, we register a build event in Compass.

Hope this helps!

Like # people like this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events