There are times when devs notice a build failure, they create a ticket for the issue causing the failure and work on it instantly only to realize later that their fix is no longer necessary because normally the dev that broke the build made a follow up commit to fix it before they could issue their pull request, i for one i feel bad for these devs because their efforts go wasted and i think it can be avoided going forward. My suggestion is and it’s what we recommend even though i think it’s not documented anywhere is when you notice a build failure, as opposed to creating and working on a ticket to fix it immediately, you can do the following:
- Try to reach out to the dev via IRC or email that made the commit that broke the build, each bamboo build normally has details about the committer(s) and link(s) to the commit(s) or parent bamboo plan that triggered the build.
- Alternatively you can bring it up on talk
My view is that we shouldn’t be creating tickets for building failures just like that, chances are normally the dev that broke the build is addressing the failure even though it’s not always the case but I believe from the discussions that go on when you try the options above, either you would find out if there is someone else addressing the issue or if it needs to be ticketed. I think this would minimize the chances of devs concurrently working on the same issue and wasting their time duplicating work.
Another thing is, when you create a ticket, it’s good to allow sometime before you actually work on it for others to give their views, in theory a ticket needs to be assessed before it’s made ready for work. Otherwise this could also lead to wasting a dev’s time because the issue being reporting could be possibly already fixed, non re produce-able, or specific to a single installation may be due to mis-configuration or misuse.
What do others think?