Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-6765

Retry with newer commits after timeout

XMLWordPrintable

    • GitOps Tangerine Sprint 15, GitOps Tangerine Sprint 16, GitOps Tangerine Sprint 17, GitOps Tangerine Sprint 18, GitOps Tangerine Sprint 19, GitOps Tangerine Sprint 20, GitOps Tangerine Sprint 21, GitOps Tangerine Sprint 22, GitOps Tangerine Sprint 23

      Story (Required)

      • Check for new commits when retrying a sync that have timed out.
      • As an application developer trying to manage resources in GitOps way, I want to fix failed syncs with new commits.

      Background and Approach (Required)

      Out of Scope

      • Not known

      Dependencies

      • Not known

      Acceptance Criteria (Mandatory)

      • The feature is accepted in master branch, albeit as an alpha.

      Definition of Done

      • Code Complete:
        • All code has been written, reviewed, and approved.
      • Tested:
        • Unit tests have been written and passed.
        • Ensure code coverage is not reduced with the changes.
        • Integration tests have been automated.
        • System tests have been conducted, and all critical bugs have been fixed.
        • Tested and merged on OpenShift either upstream or downstream on a local build.
      • Documentation:
        • User documentation or release notes have been written (if applicable).
      • Build:
        • Code has been successfully built and integrated into the main repository / project.
        • Midstream changes (if applicable) are done, reviewed, approved and merged.
      • Review:
        • Code has been peer-reviewed and meets coding standards.
        • All acceptance criteria defined in the user story have been met.
        • Tested by reviewer on OpenShift.
      • Deployment:
        • The feature has been deployed on OpenShift cluster for testing.

              ogondza@redhat.com Oliver Gondza
              ogondza@redhat.com Oliver Gondza
              Tangerine
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: