Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:
-
Story Points:2
-
Epic Link:
-
Sprint:Winter 2018 Sprint 2, Winter 2018 Sprint 3, Summer 2019 Sprint 10, Summer 2019 Sprint 11
Description
Whenever we do a release of IGB, we have to hard-code the IGB version string.
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings with value parsed from root POM.xml version string.
For an example, see how this is being done for Genoviz SDK build process.
Note: the most complicated aspect of this will probably be figuring out how to create the version string used in the IGB installer names, which use underscore characters instead of periods.
Note: Srishti Tiwari worked on this previously. The issue description previously recommend testing the build environment and process using Docker image running on a local host. See comments.
Attachments
Issue Links
Activity
| Field | Original Value | New Value |
|---|---|---|
| Sprint | Early Fall 2017 [ 47 ] |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Description | Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings (e.g., 9.0.1 in curl command) with references to IGB_VERSION environment variable. |
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings (e.g., 9.0.1 in curl command) with placeholder to allow editing of this variable during the build process. Options: 1) Insert value from a bitbucket pipeline environment variable, added manually by developer 2) Parse version string from IGB code files (pom.xml or properties file?) Alternatively, parse IGB version string from IGB project directly. |
| Description |
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings (e.g., 9.0.1 in curl command) with placeholder to allow editing of this variable during the build process. Options: 1) Insert value from a bitbucket pipeline environment variable, added manually by developer 2) Parse version string from IGB code files (pom.xml or properties file?) Alternatively, parse IGB version string from IGB project directly. |
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings (e.g., 9.0.1 in curl command) with placeholder to allow editing of this variable during the build process. Options: 1) Insert value from a bitbucket pipeline environment variable, added manually by developer 2) Parse version string from IGB code files (pom.xml or properties file?) |
| Assignee | Sanket Patil [ spatil26 ] |
| Assignee | Ann Loraine [ aloraine ] |
| Fix Version/s | 9.0.2 [ 10600 ] | |
| Story Points | 0.25 | 1 |
| Description |
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings (e.g., 9.0.1 in curl command) with placeholder to allow editing of this variable during the build process. Options: 1) Insert value from a bitbucket pipeline environment variable, added manually by developer 2) Parse version string from IGB code files (pom.xml or properties file?) |
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings (e.g., 9.0.1 in curl command) with placeholder to allow editing of this variable during the build process.
Options: 1) Insert value from a bitbucket pipeline environment variable, added manually by developer 2) Parse version string from IGB code files (pom.xml or properties file?) PREFERRED |
| Rank | Ranked higher |
| Assignee | Ann Loraine [ aloraine ] |
| Summary | replace IGB version strings with IGB_VERSION environment variable references | Replace IGB version strings with IGB_VERSION environment variable references |
| Summary | Replace IGB version strings with IGB_VERSION environment variable references | Get IGB version strings from POM instead of hard-coding |
| Description |
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings (e.g., 9.0.1 in curl command) with placeholder to allow editing of this variable during the build process.
Options: 1) Insert value from a bitbucket pipeline environment variable, added manually by developer 2) Parse version string from IGB code files (pom.xml or properties file?) PREFERRED |
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings with value parsed from POM.xml
|
| Labels | Beginner |
| Description |
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings with value parsed from POM.xml
|
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings with value parsed from root POM.xml version string.
In addition, change name of release build artifacts IGB-[platform]-[version].[dmg|exe|sh] where "version" is version string obtained from POM. Don't assume anything about what "version" will be. For an example, see how this is being done for Genoviz SDK build process. This will likely require understanding and editing the Install4J configuration file. *Tip*: do as much editing and testing as possible using our Dockerized build environment on an EC2 or on your own machine, not bitbucket. It will probably take less effort. This is tagged as beginner because the process and tooling are well-documented. Requires understanding how multiple systems interact. After this you will have a deeper knowledge of how we build the project. |
| Rank | Ranked higher |
| Fix Version/s | 9.0.2 Minor Release [ 10600 ] |
| Labels | Beginner | Intermediate |
| Description |
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings with value parsed from root POM.xml version string.
In addition, change name of release build artifacts IGB-[platform]-[version].[dmg|exe|sh] where "version" is version string obtained from POM. Don't assume anything about what "version" will be. For an example, see how this is being done for Genoviz SDK build process. This will likely require understanding and editing the Install4J configuration file. *Tip*: do as much editing and testing as possible using our Dockerized build environment on an EC2 or on your own machine, not bitbucket. It will probably take less effort. This is tagged as beginner because the process and tooling are well-documented. Requires understanding how multiple systems interact. After this you will have a deeper knowledge of how we build the project. |
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings with value parsed from root POM.xml version string.
In addition, change name of release build artifacts IGB-[platform]-[version].[dmg|exe|sh] where "version" is version string obtained from POM. Don't assume anything about what "version" will be. For an example, see how this is being done for Genoviz SDK build process. This will likely require understanding and editing the Install4J configuration file. *Tip*: do as much editing and testing as possible using our Dockerized build environment on an EC2 or on your own machine, not bitbucket. It will probably take less effort. This is tagged as Intermediate because the process and tooling are well-documented but requires understanding how multiple systems interact. After this you will have a deeper knowledge of how we build the project. |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Sprint | Winter 2018 Sprint 2 [ 57 ] |
| Rank | Ranked higher |
| Assignee | Srishti Tiwari [ stiwari8 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Rank | Ranked higher |
| Sprint | Winter 2018 Sprint 2 [ 57 ] | Winter 2018 Sprint 2, Winter 2018 Sprint 3 [ 57, 58 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Srishti Tiwari [ stiwari8 ] | Ann Loraine [ aloraine ] |
| Assignee | Ann Loraine [ aloraine ] |
| Assignee | Ann Loraine [ aloraine ] |
| Status | Needs 1st Level Review [ 10005 ] | Reviewing [ 10301 ] |
| Status | Reviewing [ 10301 ] | Open [ 1 ] |
| Assignee | Ann Loraine [ aloraine ] | Srishti Tiwari [ stiwari8 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Status | Needs 1st Level Review [ 10005 ] | Reviewing [ 10301 ] |
| Assignee | Srishti Tiwari [ stiwari8 ] | Ann Loraine [ aloraine ] |
| Assignee | Ann Loraine [ aloraine ] | Srishti Tiwari [ stiwari8 ] |
| Status | Reviewing [ 10301 ] | Open [ 1 ] |
| Rank | Ranked higher |
| Sprint | Winter 2018 Sprint 2, Winter 2018 Sprint 3 [ 57, 58 ] | Winter 2018 Sprint 2, Winter 2018 Sprint 3, Spring 2019 Sprint 1 [ 57, 58, 59 ] |
| Rank | Ranked higher |
| Assignee | Srishti Tiwari [ stiwari8 ] | Ann Loraine [ aloraine ] |
| Sprint | Winter 2018 Sprint 2, Winter 2018 Sprint 3, Spring 2019 Sprint 1 [ 57, 58, 59 ] | Winter 2018 Sprint 2, Winter 2018 Sprint 3 [ 57, 58 ] |
| Rank | Ranked higher |
| Sprint | Winter 2018 Sprint 2, Winter 2018 Sprint 3 [ 57, 58 ] | Winter 2018 Sprint 2, Winter 2018 Sprint 3, Spring 2019 Sprint 2 [ 57, 58, 60 ] |
| Rank | Ranked higher |
| Sprint | Winter 2018 Sprint 2, Winter 2018 Sprint 3, Spring 2019 Sprint 2 [ 57, 58, 60 ] | Winter 2018 Sprint 2, Winter 2018 Sprint 3 [ 57, 58 ] |
| Rank | Ranked lower |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Assignee | Ann Loraine [ aloraine ] |
| Rank | Ranked higher |
| Sprint | Winter 2018 Sprint 2, Winter 2018 Sprint 3 [ 57, 58 ] | Winter 2018 Sprint 2, Winter 2018 Sprint 3, Summer 2019 Sprint 9 [ 57, 58, 68 ] |
| Rank | Ranked lower |
| Sprint | Winter 2018 Sprint 2, Winter 2018 Sprint 3, Summer 2019 Sprint 9 [ 57, 58, 68 ] | Winter 2018 Sprint 2, Winter 2018 Sprint 3 [ 57, 58 ] |
| Rank | Ranked higher |
| Sprint | Winter 2018 Sprint 2, Winter 2018 Sprint 3 [ 57, 58 ] | Winter 2018 Sprint 2, Winter 2018 Sprint 3, Summer 2019 Sprint 10 [ 57, 58, 69 ] |
| Rank | Ranked higher |
| Description |
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings with value parsed from root POM.xml version string.
In addition, change name of release build artifacts IGB-[platform]-[version].[dmg|exe|sh] where "version" is version string obtained from POM. Don't assume anything about what "version" will be. For an example, see how this is being done for Genoviz SDK build process. This will likely require understanding and editing the Install4J configuration file. *Tip*: do as much editing and testing as possible using our Dockerized build environment on an EC2 or on your own machine, not bitbucket. It will probably take less effort. This is tagged as Intermediate because the process and tooling are well-documented but requires understanding how multiple systems interact. After this you will have a deeper knowledge of how we build the project. |
Whenever we do a release of IGB, we have to hard-code the IGB version string.
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings with value parsed from root POM.xml version string. For an example, see how this is being done for Genoviz SDK build process. Note: the most complicated aspect of this will probably be figuring out how to create the version string used in the IGB installer names, which use underscore characters instead of periods. |
| Description |
Whenever we do a release of IGB, we have to hard-code the IGB version string.
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings with value parsed from root POM.xml version string. For an example, see how this is being done for Genoviz SDK build process. Note: the most complicated aspect of this will probably be figuring out how to create the version string used in the IGB installer names, which use underscore characters instead of periods. |
Whenever we do a release of IGB, we have to hard-code the IGB version string.
Review bitbucket-pipelines.yml file and replace hard-coded IGB version strings with value parsed from root POM.xml version string. For an example, see how this is being done for Genoviz SDK build process. Note: the most complicated aspect of this will probably be figuring out how to create the version string used in the IGB installer names, which use underscore characters instead of periods. Note: [~stiwari8] worked on this previously. The issue description previously recommend testing the build environment and process using Docker image running on a local host. See comments. |
| Comment | [ Note: This may be a two-person job. We can ask another developer to take over for the next steps as you have made a good foundation on this. ] |
| Status | Open [ 1 ] | Open [ 1 ] |
| Epic Link | IGBF-1531 [ 17617 ] |
| Story Points | 1 | 2 |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Assignee | Ann Loraine [ aloraine ] |
| Sprint | Winter 2018 Sprint 2, Winter 2018 Sprint 3, Summer 2019 Sprint 10 [ 57, 58, 69 ] | Winter 2018 Sprint 2, Winter 2018 Sprint 3, Summer 2019 Sprint 10, Summer 2019 Sprint 11 [ 57, 58, 69, 70 ] |
| Rank | Ranked higher |
| Status | In Progress [ 3 ] | Needs Testing [ 10002 ] |
| Assignee | Ann Loraine [ aloraine ] |
| Assignee | Srishti Tiwari [ stiwari8 ] |
| Status | Needs Testing [ 10002 ] | Testing In Progress [ 10003 ] |
| Resolution | Done [ 10000 ] | |
| Status | Testing In Progress [ 10003 ] | Closed [ 6 ] |
| Workflow | Loraine Lab Workflow [ 17872 ] | Fall 2019 Workflow Update [ 19824 ] |
| Workflow | Fall 2019 Workflow Update [ 19824 ] | Revised Fall 2019 Workflow Update [ 21943 ] |