ods-jenkins-shared-library icon indicating copy to clipboard operation
ods-jenkins-shared-library copied to clipboard

EDP RM - Jira plugin workflow for release status

Open clemensutschig opened this issue 3 years ago • 2 comments

After bringing a release live - here is what we learned.

a) Being every time sent back to WIP with a failed DEV assembly run does not help, I should be able to re-run WIP and DEV as often as I want b) If a deployment to Q fails (and only then), I should be able to deploy again to Q - the key here is a fully working discrepency log. c) One should be able to set the status of a run in JIRA to success - it's a cautious human choice - that needs to be documented then - alternatively, we need to provide some mean in the shared lib? to declare a jenkins run (which is the foundation for this) to be successfull - similarely to the deviation I have built

@metmajer fyi

clemensutschig avatar Feb 20 '22 07:02 clemensutschig

related to #830 and Boehringer-Ingelheim/toscaci/issues/56

clemensutschig avatar Feb 20 '22 07:02 clemensutschig

@clemensutschig I was looking into using release-manager against an existing Jira Server instance and was wondering if you provisioned your Jira instance using the ods-infra scripts or re-used an existing one? Can't seem to find any documentation on what needs to be added to a Jira Project when using an existing instance.

regicsolutions avatar Mar 23 '22 07:03 regicsolutions