Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-14930

check_compatibility.sh needs smarter exit codes

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.2.0, 1.3.0, 1.0.3, 1.1.3, 0.98.17, 2.0.0
    • None
    • None
    • Reviewed

    Description

      The check_compatibility.sh tool in dev_support uses the Java API Compliance Checker to do static analysis of source/binary incompatibilties between two HBase branches. One problem, though, is that the script has a few instances where it may return an exit code of 1 (e.g. if Maven steps fail), but this is the same exit code that the Java ACC tool itself uses to denote that the tool succeeded, but found incompatibilities.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            dimaspivak Dima Spivak Assign to me
            dimaspivak Dima Spivak
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment