Live data from Hacker News

Analytics Solution for GitHub Actions. No Need to Run CI in the Dark

blog.trunk.io

1–10 of 15 posts

Re: Analytics Solution for GitHub Actions. No Need to Run CI in the Dark

#3
Trunk employee here - we're super excited about this launch!

We've got a few companies using it, and had other users in our community tell us "It's a very helpful tool that I didn't even know I needed". Even we ourselves have made a number of surprising discoveries about how often some of our hourly/nightly workflows have been failing by dogfooding this.

Let us know what you think! :)

Re: Analytics Solution for GitHub Actions. No Need to Run CI in the Dark

#4
GH actions has been great for us for CI but incredibly opaque when you're trying to diagnose problems. Simple jobs running on the gh hosted runners are fine, but we have a large pool of self-hosted runners running more complex workflows, and whenever things go sideways the answer is usually "did you try restarting all of them?" Hopefully this is helpful, at least someone is investing in making gh actions work for larger organizations.

Re: Analytics Solution for GitHub Actions. No Need to Run CI in the Dark

#7
post #6

Datadog already does this, how does this compare? Genuinely interested.

I would say that broadly the ergonomics of the product are where it is most differentiated. Datadog's solution - feels very much like a datadog product - in that it's a giant dump of data you have to craft to tell a story. Not all pipelines are the same, their execution patterns are different and expectations for Pass/Fail/Cancel differ as well.

Re: Analytics Solution for GitHub Actions. No Need to Run CI in the Dark

#9
post #6

Datadog already does this, how does this compare? Genuinely interested.

I would say that broadly the ergonomics of the product are where it is most differentiated. Datadog's solution - feels very much like a datadog product - in that it's a giant dump of data you have to craft to tell a story. Not all pipelines are the same, their execution patterns are different and expectations for Pass/Fail/Cancel differ as well.

Tbh it looks the same as Datadog’s solution.
Post reply on HN