Job 1_openmq-build-and-stage uses grep to determine existence of release branch

[pzygielo]

https://ci.eclipse.org/openmq/job/1_openmq-build-and-stage/64/:

+ echo 'Current version: 6.0.0-SNAPSHOT'
Current version: 6.0.0-SNAPSHOT
+ echo 'Release version: 6.0.0'
Release version: 6.0.0
+ echo 'Next version:    6.0.1-SNAPSHOT'
Next version:    6.0.1-SNAPSHOT
+ echo 'Release tag:     6.0.0-RELEASE'
Release tag:     6.0.0-RELEASE
+ '[' -z 6.0.0-SNAPSHOT -o -z 6.0.0 -o -z 6.0.1-SNAPSHOT ']'
+ '[' false = true ']'
+ MVN_DEPLOY_ARGS=nexus-staging:deploy
++ git remote
+ GIT_ORIGIN=origin
+ echo '-[ Prepare branch ]-------------------------------------------------------------'
-[ Prepare branch ]-------------------------------------------------------------
++ git branch -r
++ grep origin/6.0.0
+ [[ -n   origin/6.0.0-RC3 ]]
+ '[' false = true ']'
+ echo 'Error: origin/6.0.0 branch already exists'
Error: origin/6.0.0 branch already exists
+ exit 1

Unfortunately - 6.0.0-RC3 matches and causes failure.

[arjantijms]

Hmmm, indeed, it should be a line by line comparison of the lines returned by git branch -r.

There's a few more of those greps in the standard scripts that at some points must cause issues (like grepping the entire pom etc).

[pzygielo]

I hope one day we'll find cycles to update them as well 😄
For now - I've just deleted the offending branch.

[arjantijms]

Best for now, thx!