Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-986

Build API Scheduler Options

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • shipwright
    • None

      Story (Required)

      <Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

      As a developer trying to control where builds run on OpenShift I want to be able to tune the build's node selector, tolerations, and choice of pod scheduler.

      Background (Required)

      <Describes the context or background related to this story>

      See SHIP-0039 for a fuller description of the context.

      Out of scope

      <Defines what is not included in this story>

      • CLI support
      • Hardening guideline

      Approach (Required)

      <Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

      Dependencies

      <Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

      • Tekton PodTemplate API

      Acceptance Criteria (Mandatory)

      <Describe edge cases to consider when implementing the story and defining tests>

      <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

      • Builds can steer workloads to a node with node selectors
      • Builds can tolerate a node taint
      • Builds can use a custom pod scheduler
      • CI verifies (to the furthest extent possible) this behavior with OpenShift Pipelines.
      • Upstream and downstream documentation describes how these new fields work.

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

              Unassigned Unassigned
              adkaplan@redhat.com Adam Kaplan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: