Uploaded image for project: 'Automation Hub'
  1. Automation Hub
  2. AAH-1884

Update galaxy-importer ansible-test call to not use docker build

Details

    • Task
    • Resolution: Unresolved
    • Normal
    • None
    • None
    • Backend
    • False
    • Hide

      None

      Show
      None
    • False

    Description

      Problem Description:

      galaxy-importer calls `ansible-test sanity` in 3 ways

      1. Use galaxy-importer's image on quay via openshift job in CRC
      2. Use galaxy-importer's image built in real-time when calling importer from the command line
      3. Use image provided by ansible-test by calling`ansible-test sanity --docker`

      With #2 using `docker build` this is more complex to maintain, not normally expected of a tool like galaxy-importer, and when we update galaxy-importer's image it requires more time for each update. We also use a slightly modified Dockerfile so the images used are not consistent in #1 and #2.

      Proposed Solution:

      Use galaxy-importer's image on quay when calling importer from the command line. First the quay repository quay.io/cloudservices/automation-hub-ansible-test will need to be made public.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              awcrosby5 Andrew Crosby (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: