undefined | Better HN

0 pointsyellow_lead3y ago0 comments

At my old company, they had two annoying jira workflows management wanted to tie in to the dev process

1) When the user wants to merge to master, at least one of the commit messages must reference a valid Jira ticket.

2) A Jira plugin was installed such that when tests were run in CI, a jira ticket was created to record the result (pass/fail). This somehow ticks a SOC compliance box

0 comments

wizofaus3y ago

1) sounds pretty reasonable and standard to me, though a backdoor is usually necessary for PRs that are just to fix a build-blocking issue due a bad merge e.g. Agree 2) is stupid, why would you need a ticket for a passing build? And unless you have a super stable CI system a decent % of failures are transitory and don't need tracking - but if your master branch fails to build on retry an auto created blocker ticket makes sense.

j / k navigate · click thread line to collapse

0 pointsyellow_lead3y ago0 comments

At my old company, they had two annoying jira workflows management wanted to tie in to the dev process

1) When the user wants to merge to master, at least one of the commit messages must reference a valid Jira ticket.

2) A Jira plugin was installed such that when tests were run in CI, a jira ticket was created to record the result (pass/fail). This somehow ticks a SOC compliance box

0 comments

wizofaus3y ago

j / k navigate · click thread line to collapse