[BUILD-1213] When using a feature branch versioning, Docker Selenium version isn't resolved Created: 22/Jan/24  Updated: 25/Jan/24  Resolved: 25/Jan/24

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

Type: Task Priority: Neutral
Reporter: Maxime Michel Assignee: Harshini Pola
Resolution: Resolved Votes: 0
Labels: TAE
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to BUILD-1183 pipeline-templates supporting seleniu... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Team: Foundation
Work Started:
Approved:
Yes

 Description   

This affects both the moduleUiTestsPipeline and the integrationTestsPipeline. When a build runs those pipelines and uses a feature branch name, the 'Build Docker Image' will attempt to resolve a Selenium version. However, the code doing this:

def seleniumVersionVariable = new Configuration(currentBuild.fullProjectName, readMavenPom().version, libraryResource('info/magnolia/testFramework-versions.json'), libraryResource('info/magnolia/pipeline-configurations.json')).retrieveFlag("seleniumVersionVariable") 

Will fail because Configuration expects versions to be +/- valid SemVer versions.

In such cases we need to map the feature branch version to the equivalent canonical version so that the pipeline can carry on. See the linked PR.



 Comments   
Comment by Harshini Pola [ 25/Jan/24 ]

Updated, reviewed and merged

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