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

website generation is failing

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: Resolved
    • Blocker
    • Resolution: Fixed
    • None
    • 2.0.0-beta-2, 2.0.0
    • website
    • None

    Description

      website generation has been failing since Feb 20th

      Checking out files: 100% (68971/68971), done.
      Usage: grep [OPTION]... PATTERN [FILE]...
      Try 'grep --help' for more information.
      PUSHED is 2
       is not yet mentioned in the hbase-site commit log. Assuming we don't have it yet. 2
      Building HBase
      Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
      Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
      Failure: mvn clean site
      Build step 'Execute shell' marked build as failure
      

      The status email says

      Build status: Still Failing
      
      The HBase website has not been updated to incorporate HBase commit ${CURRENT_HBASE_COMMIT}.
      

      Looking at the code where that grep happens, it looks like the env variable CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm guessing the version of git changed on the build hosts and upended our assumptions.

      we should fix this to 1) rely on git's porcelain interface, and 2) fail as soon as that git command fails

      Attachments

        Issue Links

        Activity

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

          People

            busbey Sean Busbey Assign to me
            busbey Sean Busbey
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment