Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:
-
Story Points:0.5
-
Epic Link:
-
Sprint:Fall 2019 Sprint 3, Fall 4 : 30 Sep to 11 Oct
Description
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 (Ann Loraine) have observed this.)
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link | IGBF-1531 [ 17617 ] |
| Rank | Ranked higher |
| Status | Open [ 1 ] | To-Do [ 10305 ] |
| Description |
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., 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 [~stiwari8] and myself ([~aloraine]) have observed this.) |
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., 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 [~stiwari8] and myself ([~aloraine]) have observed this.) |
| Assignee | Ann Loraine [ aloraine ] | Prutha Kulkarni [ prutha ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Sprint | Fall 2019 Sprint 3 [ 74 ] | Fall 2019 Sprint 3, Fall 2019 Sprint 4 [ 74, 75 ] |
| Rank | Ranked higher |
| Status | In Progress [ 3 ] | To-Do [ 10305 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Prutha Kulkarni [ prutha ] |
| Assignee | Ann Loraine [ aloraine ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Assignee | Ann Loraine [ aloraine ] | Prutha Kulkarni [ prutha ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
| Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
| Assignee | Prutha Kulkarni [ prutha ] |
| Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
| Status | Reviewing Pull Request [ 10303 ] | To-Do [ 10305 ] |
| Assignee | Prutha Kulkarni [ prutha ] |
| Status | To-Do [ 10305 ] | Pull Request Submitted [ 10101 ] |
| Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
| Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
| Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
| Resolution | Done [ 10000 ] | |
| Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
| Workflow | Fall 2019 Workflow Update [ 20784 ] | Revised Fall 2019 Workflow Update [ 22523 ] |