Ability to Map Quality Gates to One or More Branches

[kirkpabk (Brian Kirkpatrick)]

Looking for options to apply Quality Gates to specific branches. It appears that this feature might be available, how do we implement for this structure:

$master
/prd - ProdQualityGate
/tst - TestQualityGate
/dev - DevQualityGate

Best Regards,
BK

[ganncamp (G Ann Campbell)]

Hi BK,

This is an interesting use case, but not one we support. Would you mind sharing how those Quality Gates differ?

 
Ann

[kirkpabk (Brian Kirkpatrick)]

Hey Ann,

Yeah, so our automation platform deploys based on branch. In some branches, we may not want a branch to halt deployment to enable us to manage certain process like helping us to test and work through controls and risk limiting options. As it is, I cannot find a way to have tiered Quality Gates for different branches.

Does this make sense?

[ganncamp (G Ann Campbell)]

Hi,

Thanks for getting back to me & sorry for the delay in responding.

@kirkpabk

In some branches, we may not want a branch to halt deployment to enable us to manage certain process like helping us to test and work through controls and risk limiting options.

I understand wanting to take different actions in different situations, but I’m not understanding wanting to apply different criteria. Wouldn’t this just be a question of failing - or not - the pipeline for a failing Quality Gate?

 
Ann

[Rebse (Gilbert Rebhan)]

Hi,

your question is similar to this posting

Quality gates for different branch In a project

Hi, I’m using sonarqube developer edition version 8.1 I was just wondering if there is a way to configure different quality gates for each branch in a specific project ? We’re now using the sonarqube recommended quality gate for all of our projects. Thank you

And i think the recommendation of @OlivierK is reasonable.
Another somewhat ‘quirky’ approach would be to wrap the Sonarqube analysis in try / catch
for special pipelines, i.e. the Jenkins pipeline step waitForQualityGate() continuing the pipeline
even if quality gate fails. That way you’ll get all issues if any but your pipeline goes on.

Gilbert

[kirkpabk (Brian Kirkpatrick)]

So, based on the input here, we’ll leave the quality gates as they are and set failures as warnings in the pipeline with notifications/alerts. That way there surprises up the chain. Thanks all!