Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-3830

improvements to ghira bot / release notes automation

XMLWordPrintable

    • False
    • None
    • False

      Fix 400 error (token expiry) : DONE

      $➔ ./ghira 
      Check for new&noteworthy issues closed in the last 2 weeks
      INFO: Sync https://github.com/eclipse/che/issues/21803 to JIRA
      Traceback (most recent call last):
        File "/home/nboldt/5-Che/1.github_upstream__manual-sync_to_pkgs.devel/devspaces/product/ghira/./ghira", line 248, in <module>
          new_jira_issue = j.create_issue(fields=new_jira)
        File "/home/nboldt/5-Che/1.github_upstream__manual-sync_to_pkgs.devel/devspaces/product/ghira/lib64/python3.10/site-packages/jira/client.py", line 1518, in create_issue
          r = self._session.post(url, data=json.dumps(data))
        File "/home/nboldt/5-Che/1.github_upstream__manual-sync_to_pkgs.devel/devspaces/product/ghira/lib64/python3.10/site-packages/requests/sessions.py", line 635, in post
          return self.request("POST", url, data=data, json=json, **kwargs)
        File "/home/nboldt/5-Che/1.github_upstream__manual-sync_to_pkgs.devel/devspaces/product/ghira/lib64/python3.10/site-packages/jira/resilientsession.py", line 223, in request
          elif raise_on_error(response, **processed_kwargs):
        File "/home/nboldt/5-Che/1.github_upstream__manual-sync_to_pkgs.devel/devspaces/product/ghira/lib64/python3.10/site-packages/jira/resilientsession.py", line 69, in raise_on_error
          raise JIRAError(
      jira.exceptions.JIRAError: JiraError HTTP 400 url: https://issues.redhat.com/rest/api/2/issue
      	
      	response headers = {'x-arequestid': '1007x70735223x16', 'x-anodeid': 'rh1-jira-prod-0', 'referrer-policy': 'strict-origin-when-cross-origin', 'x-xss-protection': '1; mode=block', 'x-content-type-options': 'nosniff', 'x-frame-options': 'SAMEORIGIN', 'Content-Security-Policy': 'sandbox', 'strict-transport-security': 'max-age=31536000', 'x-ausername': 'anonymous', 'Content-Encoding': 'gzip', 'Vary': 'User-Agent, Accept-Encoding', 'Content-Type': 'application/json;charset=UTF-8', 'Content-Length': '189', 'Expires': 'Thu, 12 Jan 2023 16:47:47 GMT', 'Cache-Control': 'max-age=0, no-cache, no-store', 'Pragma': 'no-cache', 'Date': 'Thu, 12 Jan 2023 16:47:47 GMT', 'Connection': 'close', 'x-rh-edge-request-id': '257f98f5', 'x-rh-edge-reference-id': '0.24ee2117.1673542067.257f98f5', 'x-rh-edge-cache-status': 'Miss from child, Miss from parent'}
      	response text = {"errorMessages":[],"errors":{"summary":"Field 'summary' cannot be set. It is not on the appropriate screen, or unknown.","components":"Field 'components' cannot be set. It is not on the appropriate screen, or unknown.","versions":"Field 'versions' cannot be set. It is not on the appropriate screen, or unknown.","description":"Field 'description' cannot be set. It is not on the appropriate screen, or unknown.","fixVersions":"Field 'fixVersions' cannot be set. It is not on the appropriate screen, or unknown.","labels":"Field 'labels' cannot be set. It is not on the appropriate screen, or unknown."}}
      

      If the RN text field is updated in GitHub, does ghira update the field in jira, too? Not currently.

      • instead of skipping the JIRA when processing, check for changes to the GH issue description and comment on the JIRA with new information posted upstream
        • DONE

      Ignore processing of Che-only items: https://github.com/eclipse/che/issues?q=label%3Anew%26noteworthy%2Fche-only

      • filter out `new&noteworthy/che-only` items (even if they ALSO have ` new&noteworthy` label)
        • DONE

      Figure out this error:

      • Issue not synced to JIRA because milestone field is invalid (7.60) for Issue URL: https://github.com/eclipse/che/issues/21927
        • YES, because 7.60 isn't released yet and because 7.60 aligns to 3.x (3.x fixversion is not valid for RNs)
        • DONE

      Provide links to the relevant upstream RN PRs in JIRA

      • query for PRs related to the upstream issue, and link them to the downstream JIRA
        • DONE

      Create new bot that's compliant with IPA rules (or reuse the devspaces-build@IPA bot?)

      Update mapping logic to not use theia (deprecated and will be removed)

      Update json mappings between GH and JIRA labels/components once we finalize the team reorg plans :: DONE

      -----------------

      Bucket lists / JIRA labels

      • add labels to issues that are simply an add/remove of devfile, update of UDI container (newer versions of rpms/tools), other Bucket of related RN
      • not sure this is feasible since devfiles and UDI are forks downstream so any related issues/PRs upstream are not likely N&N downstream. Won't do.

      Notifications?

      • emails containing the console log when # of processes issues >0 (send email to Jana/Nick)
      • emails containing the console log if a failure occurs (send email to Nick/Sam)
      • WIP, but emails not arrving...

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: