Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.8.0
    • Fix Version/s: 1.0.0
    • Component/s: build
    • Labels:
      None

      Description

      Same reason with BIGTOP-1898, we'll need to build new set of bigtop/slaves images for those supported OSs. A simple way to do this is to setup a CI job which spin up containers and runs bigtop_toolchain in side containers to have packages installed. Then we can manually commit and push images up to dockerhub.
      This is also blocking 1.0 release since the build process requires build/slaves images.

        Activity

        Hide
        evans_ye Evans Ye added a comment -

        This is fixed. I've pushed all the 1.0 supported OS images on bigtop dockerhub.
        The images are built by the CI job and pushed to dockerhub manually.
        We might need to have better naming in the future, but so far it works fine for all the CI use cases.

        Show
        evans_ye Evans Ye added a comment - This is fixed. I've pushed all the 1.0 supported OS images on bigtop dockerhub . The images are built by the CI job and pushed to dockerhub manually. We might need to have better naming in the future, but so far it works fine for all the CI use cases.

          People

          • Assignee:
            evans_ye Evans Ye
            Reporter:
            evans_ye Evans Ye
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development