Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-893

Automation to build, test, and push containers to quay

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Major
    • None
    • None
    • Maistra
    • None
    • Sprint 54, Sprint 55, Sprint 56, Sprint 57

    Description

      Automation scripts should:

      • Should build the entire stack: maistra/istio, maistra/istio-operator, maistra/grafana, maistra/prometheus
      • Work on various branches (currently, 2.2)
      • Be able to produce nightly builds or release builds (i.e. specify container tags)
      • Should be easy to clone process for new branches

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OSSM-743 Have community daily builds

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is blocked by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OSSM-742 Get rid of RPM's in the community build process

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OSSM-892 Create scripts to create maistra containers

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. OSSM-1926 Add a linter job to istio-images-centos repo

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          mentioned on

          GitLab Merge request - Updated 2 upstream sources

          Activity

            People

              _bmangoen Brian Mangoenpawiro
              rcernich1 Rob Cernich
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: