Pipelines generated by the release process

[BraisVQ]

Describe the bug Once we start a release using the release manager, we select a version (1.0 for example) and we successfully promote to dev. Now during the release a new branch was created and commits were done in this branch. This makes new pipelines beeing generated that does not do anything due to the ci skip in the commit message. For each new version a new set of pipelines will be created for each component in the release.

To Reproduce Steps to reproduce the behavior:

1. Run Release manager pipeline with a new version.
2. See the new pipelines after a successfull release.
3. For each new version you will see new pipelines after a successfull release into dev.

Expected behavior This pipelines not being generated.

Affected version:

• OpenShift: 3.11 & 4.9
• OpenDevStack 3.x & 4.x

Additional context This pipelines does not contribute to the users and it may cause performance issues in Openshift API if there are too many BC in the cluster.

@metmajer