Our build process for integrated genome browser project is supposed to automatically build topic-branch specific installers for each major platform whenever a developer pushes a commit to a topic branch on their fork. Specifically, if a developer pushes a commit to a branch with a name that includes the string "IGBF" (e.g., IGBF-3001-Make-Me-A-Sandwich), a new installer named for the branch is supposed to get built and copied to the fork's Downloads section.

This is configured using the file "bitbucket_pipelines.yml" at the top-level of the IGB repository.

A few months ago, we made some improvements to the build process - see commit history on this file for details.

However, something about those improvements has broken the installer build. When something gets pushed, installers are indeed getting built, but the branch-specific pipeline does not appear to be getting triggered.

For this task, please look into why the topic branch build pipeline is not running as expected. First, confirm that this bug can be reproduced by creating an "IGBF" branch and pushing to your fork.

(Both Srishti Tiwari and myself ([~aloraine]) have observed this.)