Closed ctlong closed 1 year ago
Looking through the git history, it appears that the job was added so that the team in charge of the project would manually go update the bbl version in the Dockerfile. This was because that team apparently removed auto-bumping for the bbl version in that Dockerfile at some point.
See this tracker story for more information.
My thought is that we should remove this job and go back to auto-bumping the bbl version. I've made a PR to do so and linked back to this issue.
Currently the job tries to post a new chore to a tracker project whenever it recognizes that there's a new
bbl
version. This working group does not use a tracker, so arguably this job is currently useless and could be removed.It might be worth going back through git history to try and determine why this job exists though. Maybe there's a valid reason that the working group should be notified about a new
bbl
version?