• False
    • Hide

      None

      Show
      None
    • False

      Goals:

      To port the existing agent plugin into a generic agent that can be used on any person/teams cluster(s) and/or Gitlab pipelines:

      • Agent does NOT have an opinion on how the cluster should be configured
      • Agent is NOT expecting specific identifiers in either the cluster identity or the Gitlab pipelines (job names or logged output).
      • Agent CAN describe the current state of a cluster
      • Agent CAN describe available pipeline stages/jobs and API features, regardless of where the project lives in Gitlab.com (stretch, or gitlabe.cee).
      • Agent CAN describe the available pipeline stages and jobs in a given Gitlab project, or inform the user that no CI stages/jobs are defined if a pipeline is not defined.

      Acceptance Criteria:
      Once installed, the Ikari DevOps agent does not expect team-specific details and can provide the user with all generic actions available on Gitlab projects and OpenShift AI clusters.

              wspinks@redhat.com Wesley Spinks
              wspinks@redhat.com Wesley Spinks
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: