Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-19855

investigate deduplicating "Release Note" field

    XMLWordPrintableJSON

    Details

    • Type: Task
    • Status: Waiting for Infra
    • Priority: Major
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: JIRA
    • Labels:
      None
    • Project:
      HBase

      Description

      Apache HBase makes use of a tool from Apache Yetus for creating our release notes from jira issues. We’ve been using it for ... 2-ish years maybe?

      Apache Yetus uses the JIRA API to pull fields and look for one named “Release Notes” to get snippets of info relevant to making release notes.

      In our latest round of release candidate generation things have started failing. Apparently the AFS jira now defines two custom fields that are both named “Release Notes”.

      Our Duo Z figured this out by looking at [REST API output|https://issues.apache.org/jira/rest/api/2/field]. It returns both
        - Release Note => customfield_12310192
        - Release Note => customfield_12314133

      I brought this up in slack and [~cml] thought it was likely a side effect of INFRA-18944. He said further investigation would be needed to look into the duplicate.

      We'd like that investigation to happen and if possible the newer field to be merged with the older one. I believe this same issue should be impacting at least also Hadoop, since they both use the field HBase uses and rely on Apache Yetus Release Doc Maker.

        Attachments

          Activity

            People

            • Assignee:
              gmcdonald Gavin McDonald
              Reporter:
              busbey Sean Busbey
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: