-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Refactor Library Being Used for Bitbucket Server REST API in Pipelines as Code
-
8
-
False
-
None
-
False
-
67% To Do, 33% In Progress, 0% Done
-
-
-
Pipelines Sprint Crookshank 21, Pipelines Sprint Crookshank 22
Story (Required)
The current go library for Bitbucket Server REST API is buggy, old and not maitained, so we're refactoring it with new [jenkins-x/go-scm|https://github.com/jenkins-x/go-scm] This story is created to track the process of refactoring.
Background (Required)
<Describes the context or background related to this story>
Out of scope
<Defines what is not included in this story>
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.>
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>
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