Feedback wanted: Would you use this?

[armenzg]

This project has originally been written for internal use in order to answer questions about getsentry's Github CI usage.

We would like to know if there's enough external interest to use this app. If you would like more investment for this project, please vote this issue.

[BYK]

I want this so badly so 👍🏻

[armenzg]

I want this so badly so 👍🏻

Super! Let me know if the installations works for you.
There's also instructions on how to set up the app locally. Let me know if you ever try them.

[BYK]

The installation has been great so far (~24h)!. Haven't tried local dev but will do when I'll take a stab at #61

[gunta]

Yes! It's something needed for improving DevOps four keys
https://github.com/dora-team/fourkeys

[armenzg]

Yes! It's something needed for improving DevOps four keys https://github.com/dora-team/fourkeys

Let me know how well it works for you!

[JonasBa]

I was thinking about a similar app like this for the upcoming hackweek. Have we thought about parsing logs to find error stack traces and creating sentry errors for them?

[ChrisCarini]

Would you use this?

Yes! Absolutely! ❤️ I just installed the app on several of my OSS repos. I'm an author and maintainer of a handful of plugins for JetBrains IDEs (IntelliJ, PyCharm, etc etc), as well as several other related, and those projects are the repos I'm particularly interested in using Sentry.io (and this GitHub app) with - finding this app is what caused me to sign up for Sentry! 🎉

(Note, I opened #67 for a small README.md doc improvement. In pursuit of starting out with just a few of my repos, I opted to select "Only Selected Repositories" - I initially did not give the app access to the .sentry repo I had created, and no telemetry was getting sent! 🤦 oops! Once I granted the app access to my private .sentry repo, everything worked as-expected! 🎉 )

I have a handful of questions/suggestions/feedback - would you prefer I open separate issues for each, or would you rather discuss here? Just so I don't forget them, I'll list them here, but let me know if separate issues is preferred and I'll happily open them!

1. Is there a way to have the app map to different projects in Sentry? (custom sentry_config.ini on a per-GH-repo basis? a unique configuration in .sentry repository's sentry_config.ini? something else?)
2. I noticed the docs (README.md) say that this project's best value comes from "Discover" and "Dashboards" access, and then states that these two features are only available with "Business or Trial" and "Team" (respectively) - is that still the case? I believe I signed up for a "Developer" account, so once 14 days passes, I won't have access to this anymore? (Note, I saw Sentry gives free accounts for OSS projects, and was considering applying for that - would the OSS account provide the ability for me to leverage the benefits of this app?)
3. After installing the GitHub app, it landed me on the GithubAppPostInstall.md page, which states "Currently the Github App is only meant to be used for internal use." - is that still the case? If not, I'm happy to submit a PR for this file to remove that, and add a few 'tips/suggestions' from myself from a 'newcomer' to Sentry/the GitHub app if you're open to it!

Best,
Chris Carini

[fbarbare]

That app is great! I would really love to see this being maintained and maybe expended to other CI tools ❤

[vipulgupta2048]

I was thinking about a similar app like this for the upcoming hackweek. Have we thought about parsing logs to find error stack traces and creating sentry errors for them?

Very interested in Sentry being a CI/CD observability tool. Especially this. At first glance, it doesn't seem you can't do that with the current GitHub app not sending errors into Sentry and from the definition of issues in Sentry. It seems that Sentry creates issues automatically for errors that are present often. But, if everything gets sent on the info level, then Sentry is probably not recognizing any errors to create these issues. Would love to explore how we can send errors to Sentry.

[armenzg]

My apologies to everyone who commented on this ticket!! I had the wrong notification settings for this repo.

I have brought up this project back to the attention of my team and see if we can agree how it can fit with Sentry's priorities (this project was one of my hackweek projects for when I worked for the dev-infra team at Sentry).

[armenzg]

I was thinking about a similar app like this for the upcoming hackweek. Have we thought about parsing logs to find error stack traces and creating sentry errors for them?

I have thought about it. I was part of the team that maintained the same idea for Mozilla's CI.

[cobyeastwood183]

https://sentry.zendesk.com/agent/tickets/147280

[ChrisCarini]

My apologies to everyone who commented on this ticket!!

Don't sweat it! I'm personally just glad to get a response! :) Please keep us posted - it would be super cool to be able to leverage Sentry for GHA CI!