Uploaded image for project: 'AeroGear'
  1. AeroGear
  2. AEROGEAR-5712

A separate repository for each Digger image

    Details

    • Type: Task
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Why

      In Aerogear mailing list, we were talking about pushing Digger related images to Docker Hub automatically.: http://lists.jboss.org/pipermail/aerogear-dev/2017-June/012875.html

      We want to be able to publish images to Docker hub on push, and the simplest way to do that is to have each image in a separate repository. We also discussed the other options like using some scripts to watch sub folders or having a public Jenkins instance. These didn't seem feasible.

      What

      The final idea is that we divide the things in https://github.com/aerogear/digger-jenkins and have a separate repo for each image.

      Setting up Docker Hub configuration is also part of this task.

      Please don't delete the old repo entirely. Just send a commit which deletes all files and have an index file which has links to new repos.
      We have some code references all around in Github, Jira etc. which we want them to still work. Also note something like this index : "This repository may be deleted soon."

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                weil Wei Li
                Reporter:
                aliok2 Ali Ok
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: