Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-1289

Internal nightly operator "pipeline"

XMLWordPrintable

    • Internal nightly operator "pipeline"
    • False
    • False
    • Done
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined

      Goal

      We want to be able to integrate upstream and test current "work-in-progress" as much as possible and as soon as possible. Being able to build and provide a nightly operator (on pre-stage? elsewhere ?) is a must and would allow us to tests things early.

      In addition, this would help teams depending on OSP (devconsole, shipwright, …) integrate with the upcoming feature earlier and thus should make the promotion from preview to stable channels smoother.

      Why is it important ?

      It will enhance our velocity in terms of testing and releasing as we test the operator continuously and early. It will also allow depending team to drive their feature closer to ours.

      Acceptance criteria ?

      • An operator is published every day (somewhere) and available for the team and depending teams to run on
      • A small amount of tests are run in order to validate the operator
      • The process to publish this every day is automated (at least for the "master") : get upstream sources, merge them downstream, run build, run simple tests and publish

        1. osp-nigtly.png
          114 kB
          Vincent Demeester

              vdemeest Vincent Demeester
              vdemeest Vincent Demeester
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: