SCANDOCKER-3 Update release pipeline to support new versioning

[csaba-feher-sonarsource]

Please be aware that we are not actively looking for feature contributions. The truth is that it's extremely difficult for someone outside SonarSource to comply with our roadmap and expectations. Therefore, we typically only accept minor cosmetic changes and typo fixes. If you would like to see a new feature, please create a new thread in the forum "Suggest new features".

With that in mind, if you would like to submit a code contribution, make sure that you adhere to the following guidelines and all tests are passing:

• Please explain your motives to contribute this change: what problem you are trying to fix, what improvement you are trying to make
• Use the following formatting style: SonarSource/sonar-developer-toolset
• If there is a JIRA ticket available, please make your commits and pull request start with the ticket ID (SQSCANNER-XXXX)

We will try to give you feedback on your contribution as quickly as possible.

Thank You!
The SonarSource Team

[csaba-feher-sonarsource]

I have tested building a dummy release pipeline.

• The push part was not tested
• Also, this line, whether it gets the right value from the tag name, was not tested. I did not have a tag for that . full_image_tag=${{GitHub.event.release.tag_name }}

[henryju]

LGTM, we will test a release on Monday

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[robross0606]

I'm confused by these changes. If this project is going to deviate from Sonar's regular versions, where and how do we log issues referencing the image version?

[henryju]

As for all Sonar products, our community entry point (for reporting issues, asking for help or feature requests) is our community forum. Then we will create appropriate issues in JIRA accordingly.