[BUILD-505] Test and document the code done in the PoC Created: 25/Aug/21  Updated: 25/Oct/21  Resolved: 25/Oct/21

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Maxime Michel Assignee: Maxime Michel
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
BUILD-520 Implement a Spring idiomatic test setup Sub-task Closed Maxime Michel  
BUILD-521 Tests & Javadoc for BitbucketService Sub-task Closed Maxime Michel  
BUILD-522 Tests & Javadoc for NexusService Sub-task Closed Maxime Michel  
BUILD-523 Tests & Javadoc for JenkinsService Sub-task Closed Maxime Michel  
BUILD-524 Tests & Javadoc for JiraService Sub-task Closed Maxime Michel  
BUILD-525 Tests & Javadoc for MagnoliaDependenc... Sub-task Closed Maxime Michel  
BUILD-526 Tests & Javadoc for preflight checks Sub-task Closed Maxime Michel  
Template:
Acceptance criteria:
Empty
Epic Link: Release automation

 Description   

Tests and documentation are an ongoing effort, but it would be nice that somebody else than me takes a look at what I've done in the PoC and handle the technical debt I left behind.

For instance, one problem that a test will be able to highlight is the fact that main is not detected as part of the changelog, even though it clearly is.


Generated at Sun Feb 11 23:42:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.