Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-53811

Enable Sentry Release Tracking feature

XMLWordPrintable

    • Evergreen - Milestone 2

      Problem statement

      In Sentry, we sometimes mark issues as resolved after we pushed a new UL that fixes something. But then it can happen that this issue is marked as a regression by an instance that has not updated yet to that UL (for whatever reason).

      Proposal

      Sentry has a nice release tracking feature. It seems easy enough to enable, and would answer a few problems we currently have.

      For a given Sentry issue, the main pros for this is that we would then be able to mark it not just "Resolved", but "Resolved for UL-nn".

      Also, once we enable this, Sentry automatically enables a few more dashboard to help us have a better view of the issues associated to a given UL and what has likely introduced it.

        1. sentry sample dashboard.png
          sentry sample dashboard.png
          370 kB

          [JENKINS-53811] Enable Sentry Release Tracking feature

          Baptiste Mathus created issue -
          Baptiste Mathus made changes -
          Attachment New: sentry sample dashboard.png [ 44610 ]
          Baptiste Mathus made changes -
          Description Original: h3. Problem statement

          In Sentry, we sometimes mark issues as resolved after we pushed a new UL that fixes something. But then it can happen that this issue is marked as a regression by an instance that has not updated yet to that UL (for whatever reason).

          h3. Proposal

          Sentry has a nice [release tracking|https://docs.sentry.io/learn/releases/?platform=node] feature. It seems easy enough to enable, and would answer a few problems we currently have.

          For a given Sentry issue, the main pros for this is that we would then be able to mark it not just "Resolved", but "Resolved for UL-nn".

          Also, once we enable this, Sentry automatically enables a few more dashboard to help us have a better view of the issues associated to a given UL and what has likely introduced it.           		New: h3. Problem statement

          In Sentry, we sometimes mark issues as resolved after we pushed a new UL that fixes something. But then it can happen that this issue is marked as a regression by an instance that has not updated yet to that UL (for whatever reason).

          h3. Proposal

          Sentry has a nice [release tracking|https://docs.sentry.io/learn/releases/?platform=node] feature. It seems easy enough to enable, and would answer a few problems we currently have.

          For a given Sentry issue, the main pros for this is that we would then be able to mark it not just "Resolved", but "Resolved for UL-nn".

          Also, once we enable this, Sentry automatically enables a few more dashboard to help us have a better view of the issues associated to a given UL and what has likely introduced it.
           !sentry sample dashboard.png!
          Baptiste Mathus made changes -
          Description Original: h3. Problem statement

          In Sentry, we sometimes mark issues as resolved after we pushed a new UL that fixes something. But then it can happen that this issue is marked as a regression by an instance that has not updated yet to that UL (for whatever reason).

          h3. Proposal

          Sentry has a nice [release tracking|https://docs.sentry.io/learn/releases/?platform=node] feature. It seems easy enough to enable, and would answer a few problems we currently have.

          For a given Sentry issue, the main pros for this is that we would then be able to mark it not just "Resolved", but "Resolved for UL-nn".

          Also, once we enable this, Sentry automatically enables a few more dashboard to help us have a better view of the issues associated to a given UL and what has likely introduced it.
           !sentry sample dashboard.png!           		New: h3. Problem statement

          In Sentry, we sometimes mark issues as resolved after we pushed a new UL that fixes something. But then it can happen that this issue is marked as a regression by an instance that has not updated yet to that UL (for whatever reason).

          h3. Proposal

          Sentry has a nice [release tracking|https://docs.sentry.io/learn/releases/?platform=node] feature. It seems easy enough to enable, and would answer a few problems we currently have.

          For a given Sentry issue, the main pros for this is that we would then be able to mark it not just "Resolved", but "Resolved for UL-nn".

          Also, once we enable this, Sentry automatically enables a few more dashboard to help us have a better view of the issues associated to a given UL and what has likely introduced it.
           !sentry sample dashboard.png|thumb!
          Baptiste Mathus made changes -
          Description Original: h3. Problem statement

          In Sentry, we sometimes mark issues as resolved after we pushed a new UL that fixes something. But then it can happen that this issue is marked as a regression by an instance that has not updated yet to that UL (for whatever reason).

          h3. Proposal

          Sentry has a nice [release tracking|https://docs.sentry.io/learn/releases/?platform=node] feature. It seems easy enough to enable, and would answer a few problems we currently have.

          For a given Sentry issue, the main pros for this is that we would then be able to mark it not just "Resolved", but "Resolved for UL-nn".

          Also, once we enable this, Sentry automatically enables a few more dashboard to help us have a better view of the issues associated to a given UL and what has likely introduced it.
           !sentry sample dashboard.png|thumb!           		New: h3. Problem statement

          In Sentry, we sometimes mark issues as resolved after we pushed a new UL that fixes something. But then it can happen that this issue is marked as a regression by an instance that has not updated yet to that UL (for whatever reason).

          h3. Proposal

          Sentry has a nice [release tracking|https://docs.sentry.io/learn/releases/?platform=node] feature. It seems easy enough to enable, and would answer a few problems we currently have.

          For a given Sentry issue, the main pros for this is that we would then be able to mark it not just "Resolved", but "Resolved for UL-nn".

          Also, once we enable this, Sentry automatically enables a few more dashboard to help us have a better view of the issues associated to a given UL and what has likely introduced it.
           !sentry sample dashboard.png|thumbnail!
          Baptiste Mathus made changes -
          Labels Original: evergreen-triggered sentry New: evergreen-triggered newbie-friendly sentry
          Baptiste Mathus made changes -
          Labels Original: evergreen-triggered newbie-friendly sentry New: evergreen-triggered sentry
          R. Tyler Croy made changes -
          Assignee Original: R. Tyler Croy [ rtyler ]

          Baptiste Mathus added a comment -

          Loosely related, quickly filed https://github.com/jenkins-infra/evergreen/pull/314 to push the current UL along with logs to help diagnosing Sentry issues.

          Baptiste Mathus added a comment - Loosely related, quickly filed https://github.com/jenkins-infra/evergreen/pull/314 to push the current UL along with logs to help diagnosing Sentry issues.
          Mark Waite made changes -
          Resolution New: Won't Do [ 10001 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            batmat Baptiste Mathus
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: