You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
is there a possability to configure clover via a bamboo yaml file?
something like:
jobs:
- key: PACKAGE
name: Packages the software
miscellaneous:
cleanWorkingDirectoryAfterEachBuild: true
buildHungOptions:
buildTimeMultiplier: 2.5
logQuietTimeInMinutes: 10
buildQueueTimeoutInMinutes: 60
nCoverOutput:
nCoverXmlDirectory: a/b/c
cloverCodeCoverage:
cloverLicense: 'LICENSE'
cloverOptions:
generateCloverHistoricalReport: true
generateJSONReport: false
integrationOptions: !integration AUTOMATICALLY_INTEGRATE_CLOVER_INTO_BUILD
patternMatchLabelling:
regexPattern: [a-z]+
labels: test
customSettings:
custom.xxx.list: test
custom.xxx.filename: test.groovy
but not for the manual recognition not the automatic one.
We created our clover report from an gcov output and would like to integrate this into the yaml plan spec.
but it is implemented for the automatic integration?
like mentioned in API Docs | Plan DSL for Bamboo Reference (mibexsoftware.github.io)
extract of this page:
jobs:
- key: PACKAGE
name: Packages the software
miscellaneous:
cleanWorkingDirectoryAfterEachBuild: true
buildHungOptions:
buildTimeMultiplier: 2.5
logQuietTimeInMinutes: 10
buildQueueTimeoutInMinutes: 60
nCoverOutput:
nCoverXmlDirectory: a/b/c
cloverCodeCoverage:
cloverLicense: 'LICENSE'
cloverOptions:
generateCloverHistoricalReport: true
generateJSONReport: false
integrationOptions: !integration AUTOMATICALLY_INTEGRATE_CLOVER_INTO_BUILD
patternMatchLabelling:
regexPattern: [a-z]+
labels: test
customSettings:
custom.xxx.list: test
custom.xxx.filename: test.groovy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.