Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Blocker
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:
-
Story Points:2
-
Epic Link:
-
Sprint:Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Winter 4 Feb 8 - Feb 19, Winter 5 Feb 22 - Mar 5, Spring 4 2021 May 3 - May 14, Summer 1 2023 May 15, Summer 2 2023 May 29, Fall 3 2023 Oct 2, Spring 5
Description
Read modules 2 and 3 the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers.
To build IGB installers:
- Log in to bitbucket using your bitbucket user account.
- Check your account has been added to the Developers group by confirming that you can open and see private (as denoted by a "padlock" icon) IGB project repositories and their files under
https://bitbucket.org/account/user/lorainelab/projects/IGB - Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers.
- Next, trigger the master branch pipeline. (See Canvas course module Building IGB for how to do this.)
- Check that files master.dmg, master-32bit.exe, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork.
If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are:
- You need to run the branch pipeline “branches: IGBF-* ” on Bitbucket to create installers, rather than the “default” pipeline which creates the IGB jar file.
- Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available.
- Your user account does not have access to the installer private content repository. Make sure that you can see the files in the private repository when logged in to bitbucket.
- Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined.
- Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes.
- Double-check that your Bitbucket username is correct by selecting Settings > Personal Bitbucket settings > Account settings > Username.
Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review.
Reviewers should check that:
- This ticket has a comment with a link to the developer's fork
- The master branch installers are present in the fork's Downloads section
- When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present.
Attachments
Issue Links
- blocks
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- relates to
-
-
- To-Do
-
-
IGBF-2404 Suggest improvements to pipelines on-boarding tickets using insights from RW and JW
-
- Closed
-
Show 1 more links (1 relates to)
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link | IGBF-1762 [ 17852 ] |
| Rank | Ranked higher |
| Summary | On-boarding: Fork IGB team repository and set up bitbucket pipelines | On-boarding: Step Two - Fork IGB team repository and set up bitbucket pipelines |
| Summary | On-boarding: Step Two - Fork IGB team repository and set up bitbucket pipelines | On-boarding: Step Two - fork IGB team repository and set up bitbucket pipelines |
| Description |
Log in to bitbucket using your bitbucket user account that Dr. Loraine has added to the Loraine Lab team.
Review the IGB project repositories in the Loraine Lab account. Next, create a fork of the Integrated Genome Browser repository: * https://bitbucket.org/lorainelab/integrated-genome-browser Set up bitbucket pipelines following the instructions. Then set up bitbucket pipelines, following the instructions in |
Log in to bitbucket using your bitbucket user account that Dr. Loraine has added to the Loraine Lab team.
To check that your account got added to the team properly, review the IGB project repositories: https://bitbucket.org/account/user/lorainelab/projects/IGB Make sure you can see the private repositories. Next, create a fork of the Integrated Genome Browser repository: * https://bitbucket.org/lorainelab/integrated-genome-browser Set up bitbucket pipelines following the instructions in the private installer repository. Test that the pipeline is working by triggering the master branch pipeline. If you set things up properly, the master branch installers will be built and copied to the Downloads section of your fork. |
| Summary | On-boarding: Step Two - fork IGB team repository and set up bitbucket pipelines | On-boarding: Step 2 - fork IGB team repository and set up bitbucket pipelines |
| Description |
Log in to bitbucket using your bitbucket user account that Dr. Loraine has added to the Loraine Lab team.
To check that your account got added to the team properly, review the IGB project repositories: https://bitbucket.org/account/user/lorainelab/projects/IGB Make sure you can see the private repositories. Next, create a fork of the Integrated Genome Browser repository: * https://bitbucket.org/lorainelab/integrated-genome-browser Set up bitbucket pipelines following the instructions in the private installer repository. Test that the pipeline is working by triggering the master branch pipeline. If you set things up properly, the master branch installers will be built and copied to the Downloads section of your fork. |
Log in to bitbucket using your bitbucket user account that Dr. Loraine has added to the Loraine Lab team.
To check that your account got added to the team properly, review the IGB project repositories: https://bitbucket.org/account/user/lorainelab/projects/IGB Make sure you can see the private repositories. Next, create a fork of the Integrated Genome Browser repository: * https://bitbucket.org/lorainelab/integrated-genome-browser Set up bitbucket pipelines following the instructions in the private installer repository. Test that the pipeline is working by triggering the master branch pipeline. If you set things up properly, the master branch installers will be built and copied to the Downloads section of your fork. If you do not see the installers, then you need to work on the configuration. |
| Workflow | Loraine Lab Workflow [ 18486 ] | Fall 2019 Workflow Update [ 18977 ] |
| Workflow | Fall 2019 Workflow Update [ 18977 ] | Revised Fall 2019 Workflow Update [ 21097 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | To-Do [ 10305 ] |
| Sprint | Fall 5 : 14 Oct to 25 Oct [ 76 ] | |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Assignee | Ann Loraine [ aloraine ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Assignee | Ann Loraine [ aloraine ] | Philip Badzuh [ pbadzuh ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| 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 ] |
| 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 ] |
| Resolution | Done [ 10000 ] | |
| Status | Closed [ 6 ] | To-Do [ 10305 ] |
| Sprint | Fall 5 : 14 Oct to 25 Oct [ 76 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov [ 76, 77 ] |
| 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 ] |
| 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 ] |
| Resolution | Done [ 10000 ] | |
| Status | Closed [ 6 ] | To-Do [ 10305 ] |
| Description |
Log in to bitbucket using your bitbucket user account that Dr. Loraine has added to the Loraine Lab team.
To check that your account got added to the team properly, review the IGB project repositories: https://bitbucket.org/account/user/lorainelab/projects/IGB Make sure you can see the private repositories. Next, create a fork of the Integrated Genome Browser repository: * https://bitbucket.org/lorainelab/integrated-genome-browser Set up bitbucket pipelines following the instructions in the private installer repository. Test that the pipeline is working by triggering the master branch pipeline. If you set things up properly, the master branch installers will be built and copied to the Downloads section of your fork. If you do not see the installers, then you need to work on the configuration. |
Log in to bitbucket using your bitbucket user account that Dr. Loraine has added to the Loraine Lab team.
To check that your account got added to the team properly, review the IGB project repositories: https://bitbucket.org/account/user/lorainelab/projects/IGB Make sure you can see the private repositories. Next, create a fork of the Integrated Genome Browser repository: * https://bitbucket.org/lorainelab/integrated-genome-browser Set up bitbucket pipelines following the instructions in the private installer repository. Test that the pipeline is working by triggering the master branch pipeline. If you set things up properly, the master branch installers will be built and copied to the Downloads section of your fork. If you do not see the installers, then you need to work on the configuration. |
| Sprint | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov [ 76, 77 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun [ 76, 77, 95 ] |
| 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 ] |
| 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 ] |
| Description |
Log in to bitbucket using your bitbucket user account that Dr. Loraine has added to the Loraine Lab team.
To check that your account got added to the team properly, review the IGB project repositories: https://bitbucket.org/account/user/lorainelab/projects/IGB Make sure you can see the private repositories. Next, create a fork of the Integrated Genome Browser repository: * https://bitbucket.org/lorainelab/integrated-genome-browser Set up bitbucket pipelines following the instructions in the private installer repository. Test that the pipeline is working by triggering the master branch pipeline. If you set things up properly, the master branch installers will be built and copied to the Downloads section of your fork. If you do not see the installers, then you need to work on the configuration. |
Review:
https://canvas.instructure.com/courses/1164217 Focus on the section titled "Building IGB". Follow the instructions for setting up Bitbucket pipelines. Once that is done, make sure you can build the IGB installers. Only members of the Loraine Lab Developers group in Bitbucket can do this. To build IGB installers: * Log in to bitbucket using your bitbucket user account that Dr. Loraine has added to the Loraine Lab team. * To check that your account got added to the team properly, review the IGB project repositories: https://bitbucket.org/account/user/lorainelab/projects/IGB * Make sure you can see the private repositories. * Trigger the master branch pipeline. * Check that the installers were copied to your Downloads section. If you do not see the installers, then you need to work on the configuration. |
| Description |
Review:
https://canvas.instructure.com/courses/1164217 Focus on the section titled "Building IGB". Follow the instructions for setting up Bitbucket pipelines. Once that is done, make sure you can build the IGB installers. Only members of the Loraine Lab Developers group in Bitbucket can do this. To build IGB installers: * Log in to bitbucket using your bitbucket user account that Dr. Loraine has added to the Loraine Lab team. * To check that your account got added to the team properly, review the IGB project repositories: https://bitbucket.org/account/user/lorainelab/projects/IGB * Make sure you can see the private repositories. * Trigger the master branch pipeline. * Check that the installers were copied to your Downloads section. If you do not see the installers, then you need to work on the configuration. |
Enroll in this free Canvas course:
https://canvas.instructure.com/courses/1164217 Read and study all the modules. Study the section titled "Building IGB". Follow the instructions for setting up Bitbucket pipelines. Once that is done, make sure you can build the IGB installers. Only members of the Loraine Lab Developers group in Bitbucket can do this. To build IGB installers: * Log in to bitbucket using your bitbucket user account that Dr. Loraine has added to the Loraine Lab team. * To check that your account got added to the team properly, review the IGB project repositories: https://bitbucket.org/account/user/lorainelab/projects/IGB * Make sure you can see the private repositories. * Trigger the master branch pipeline. * Check that the installers were copied to your Downloads section. If you do not see the installers, then you need to work on the configuration. |
| Description |
Enroll in this free Canvas course:
https://canvas.instructure.com/courses/1164217 Read and study all the modules. Study the section titled "Building IGB". Follow the instructions for setting up Bitbucket pipelines. Once that is done, make sure you can build the IGB installers. Only members of the Loraine Lab Developers group in Bitbucket can do this. To build IGB installers: * Log in to bitbucket using your bitbucket user account that Dr. Loraine has added to the Loraine Lab team. * To check that your account got added to the team properly, review the IGB project repositories: https://bitbucket.org/account/user/lorainelab/projects/IGB * Make sure you can see the private repositories. * Trigger the master branch pipeline. * Check that the installers were copied to your Downloads section. If you do not see the installers, then you need to work on the configuration. |
Enroll in this free Canvas course:
https://canvas.instructure.com/courses/1164217 Read and study Modules Study the section titled "Building IGB". Follow the instructions for setting up Bitbucket pipelines. Once that is done, make sure you can build the IGB installers. Only members of the Loraine Lab Developers group in Bitbucket can do this. To build IGB installers: * Log in to bitbucket using your bitbucket user account that Dr. Loraine has added to the Loraine Lab team. * To check that your account got added to the team properly, review the IGB project repositories: https://bitbucket.org/account/user/lorainelab/projects/IGB * Make sure you can see the private repositories. * Trigger the master branch pipeline. * Check that the installers were copied to your Downloads section. If you do not see the installers, then you need to work on the configuration. |
| Story Points | 0.5 | 3 |
| Description |
Enroll in this free Canvas course:
https://canvas.instructure.com/courses/1164217 Read and study Modules Study the section titled "Building IGB". Follow the instructions for setting up Bitbucket pipelines. Once that is done, make sure you can build the IGB installers. Only members of the Loraine Lab Developers group in Bitbucket can do this. To build IGB installers: * Log in to bitbucket using your bitbucket user account that Dr. Loraine has added to the Loraine Lab team. * To check that your account got added to the team properly, review the IGB project repositories: https://bitbucket.org/account/user/lorainelab/projects/IGB * Make sure you can see the private repositories. * Trigger the master branch pipeline. * Check that the installers were copied to your Downloads section. If you do not see the installers, then you need to work on the configuration. |
Enroll in this free Canvas course:
https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, for the IGB repository and configure your fork to build the IGB installers for the main development branch. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your repository environment variable BB_AUTH_STRING is not properly configured. * Your repository |
| Summary | On-boarding: Step 2 - fork IGB team repository and set up bitbucket pipelines | On-boarding: Step 2 - fork IGB team repository and set up bitbucket pipelines to build installers |
| Description |
Enroll in this free Canvas course:
https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, for the IGB repository and configure your fork to build the IGB installers for the main development branch. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your repository environment variable BB_AUTH_STRING is not properly configured. * Your repository |
Enroll in this free Canvas course:
https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, for the IGB repository and configure your fork to build the IGB installers for the main development branch. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. |
| Description |
Enroll in this free Canvas course:
https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, for the IGB repository and configure your fork to build the IGB installers for the main development branch. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. |
*Note*: Completing this on-boarding task will likely take 3 full days or more, depending on your experience level.
Enroll in this free Canvas course: https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, for the IGB repository and configure your fork to build the IGB installers for the main development branch. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. |
| Description |
*Note*: Completing this on-boarding task will likely take 3 full days or more, depending on your experience level.
Enroll in this free Canvas course: https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, for the IGB repository and configure your fork to build the IGB installers for the main development branch. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. |
*Note*: Completing this on-boarding task will likely take 3 full days or more, depending on your experience level. That is fine! Go slow and take your time.
Instructions: Enroll in this free Canvas course: https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, for the IGB repository and configure your fork to build the IGB installers for the main development branch. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. |
| Description |
*Note*: Completing this on-boarding task will likely take 3 full days or more, depending on your experience level. That is fine! Go slow and take your time.
Instructions: Enroll in this free Canvas course: https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, for the IGB repository and configure your fork to build the IGB installers for the main development branch. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. |
*Note*: Completing this on-boarding task will likely take 3 full days or more, depending on your experience level. That is fine! Go slow and take your time.
Instructions: Enroll in this free Canvas course: https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, fork the IGB repository and configure your fork to build the IGB installers for the main development branch. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. |
| Description |
*Note*: Completing this on-boarding task will likely take 3 full days or more, depending on your experience level. That is fine! Go slow and take your time.
Instructions: Enroll in this free Canvas course: https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, fork the IGB repository and configure your fork to build the IGB installers for the main development branch. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. |
*Note*: Completing this on-boarding task will likely take 3 full days or more, depending on your experience level. That is fine! Go slow and take your time.
Instructions: Enroll in this free Canvas course: https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. |
| Description |
*Note*: Completing this on-boarding task will likely take 3 full days or more, depending on your experience level. That is fine! Go slow and take your time.
Instructions: Enroll in this free Canvas course: https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. |
*Note*: Completing this on-boarding task will likely take 3 full days or more, depending on your experience level. That is fine! Go slow and take your time.
Instructions: Enroll in this free Canvas course: https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that your master branch installers got built. |
| Resolution | Done [ 10000 ] | |
| Status | Closed [ 6 ] | To-Do [ 10305 ] |
| Sprint | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun [ 76, 77, 95 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul [ 76, 77, 95, 98 ] |
| Assignee | Chirag Chandrahas Shetty [ chirag24 ] |
| Description |
*Note*: Completing this on-boarding task will likely take 3 full days or more, depending on your experience level. That is fine! Go slow and take your time.
Instructions: Enroll in this free Canvas course: https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that your master branch installers got built. |
*Note*: Completing this on-boarding task will likely take 3 full days or more, depending on your experience level. That is fine! Go slow and take your time.
Instructions: Enroll in this free Canvas course: https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
| 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 ] |
| 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 ] |
| Assignee | Chirag Chandrahas Shetty [ chirag24 ] | Chester Dias [ cdias1 ] |
| Resolution | Done [ 10000 ] | |
| Status | Closed [ 6 ] | To-Do [ 10305 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Sprint | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul [ 76, 77, 95, 98 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul [ 76, 77, 95, 98, 99 ] |
| Rank | Ranked higher |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Chester Dias [ cdias1 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Assignee | Philip Badzuh [ pbadzuh ] | Chester Dias [ cdias1 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Assignee | Chester Dias [ cdias1 ] | Philip Badzuh [ pbadzuh ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Link | This issue is cloned by IGBF-2483 [ IGBF-2483 ] |
| 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 ] |
| 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 ] |
| Assignee | Philip Badzuh [ pbadzuh ] | Chester Dias [ cdias1 ] |
| Resolution | Done [ 10000 ] | |
| Status | Closed [ 6 ] | To-Do [ 10305 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Assignee | Chester Dias [ cdias1 ] |
| Status | In Progress [ 3 ] | To-Do [ 10305 ] |
| Description |
*Note*: Completing this on-boarding task will likely take 3 full days or more, depending on your experience level. That is fine! Go slow and take your time.
Instructions: Enroll in this free Canvas course: https://canvas.instructure.com/courses/1164217 Review Modules 1 through 4, focusing special attention to "Building IGB". Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
*Note*: Completing this on-boarding task will likely take 3 full days or more, depending on your experience level. That is fine! Go slow and take your time.
Instructions: Enroll in this free Canvas course: https://canvas.instructure.com/courses/1164217 Carefully read modules 1 through 4. Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
| Description |
*Note*: Completing this on-boarding task will likely take 3 full days or more, depending on your experience level. That is fine! Go slow and take your time.
Instructions: Enroll in this free Canvas course: https://canvas.instructure.com/courses/1164217 Carefully read modules 1 through 4. Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
Carefully read modules 2, 3, and 4 of the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
| Story Points | 3 | 2 |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Assignee | Sai Supreeth Segu [ ssegu ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Sprint | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul [ 76, 77, 95, 98, 99 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug [ 76, 77, 95, 98, 99, 101 ] |
| Assignee | Sai Supreeth Segu [ ssegu ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Assignee | Shamika Gajanan Kulkarni [ shamika ] |
| Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
| Status | Ready for Pull Request [ 10304 ] | 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 ] |
| Assignee | Shamika Gajanan Kulkarni [ shamika ] | Sai Supreeth Segu [ ssegu ] |
| Assignee | Sai Supreeth Segu [ ssegu ] | Irvin Naylor [ inaylor ] |
| Resolution | Done [ 10000 ] | |
| Status | Closed [ 6 ] | To-Do [ 10305 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Irvin Naylor [ inaylor ] |
| Description |
Carefully read modules 2, 3, and 4 of the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
Carefully read modules 2, 3, and 4 of the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section (they have extensions .exe, .dmg, and .sh) * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
| Description |
Carefully read modules 2, 3, and 4 of the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the master branch pipeline. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section (they have extensions .exe, .dmg, and .sh) * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
Carefully read modules 2, 3, and 4 of the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the *master branch pipeline*. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master-32bit.exe, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
| Assignee | Irvin Naylor [ inaylor ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Sprint | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug [ 76, 77, 95, 98, 99, 101 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep [ 76, 77, 95, 98, 99, 101, 102 ] |
| Rank | Ranked higher |
| Sprint | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep [ 76, 77, 95, 98, 99, 101, 102 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Fall 1: 14 Sep - 25 Sep [ 76, 77, 95, 98, 99, 101, 102, 103 ] |
| Rank | Ranked higher |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Assignee | Irvin Naylor [ inaylor ] |
| Sprint | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Fall 1: 14 Sep - 25 Sep [ 76, 77, 95, 98, 99, 101, 102, 103 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep [ 76, 77, 95, 98, 99, 101, 102 ] |
| Description |
Carefully read modules 2, 3, and 4 of the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can see private IGB project repositories under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the *master branch pipeline*. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master-32bit.exe, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
Carefully read modules 2, 3, and 4 of the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can open and see private (as denoted by a "padlock" icon) IGB project repositories and their files under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the *master branch pipeline*. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master-32bit.exe, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * You need to run the branch pipeline “Branches - IGBF*” on Bitbucket to create installers, rather than the “default” pipeline which creates the IGB jar file. * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the files in the private repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
| Description |
Carefully read modules 2, 3, and 4 of the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can open and see private (as denoted by a "padlock" icon) IGB project repositories and their files under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the *master branch pipeline*. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master-32bit.exe, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * You need to run the branch pipeline “Branches - IGBF*” on Bitbucket to create installers, rather than the “default” pipeline which creates the IGB jar file. * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the files in the private repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
Carefully read modules 2, 3, and 4 of the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can open and see private (as denoted by a "padlock" icon) IGB project repositories and their files under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the *master branch pipeline*. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master-32bit.exe, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * You need to run the branch pipeline “branches: IGBF-* ” on Bitbucket to create installers, rather than the “default” pipeline which creates the IGB jar file. * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the files in the private repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
| Assignee | Irvin Naylor [ inaylor ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Description |
Carefully read modules 2, 3, and 4 of the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can open and see private (as denoted by a "padlock" icon) IGB project repositories and their files under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the *master branch pipeline*. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master-32bit.exe, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * You need to run the branch pipeline “branches: IGBF-* ” on Bitbucket to create installers, rather than the “default” pipeline which creates the IGB jar file. * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the files in the private repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
Read modules 2 and 3 the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can open and see private (as denoted by a "padlock" icon) IGB project repositories and their files under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the *master branch pipeline*. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master-32bit.exe, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * You need to run the branch pipeline “branches: IGBF-* ” on Bitbucket to create installers, rather than the “default” pipeline which creates the IGB jar file. * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the files in the private repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
| 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 ] |
| 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 ] |
| Resolution | Done [ 10000 ] | |
| Status | Closed [ 6 ] | To-Do [ 10305 ] |
| Assignee | Irvin Naylor [ inaylor ] | Omkar Marne [ omarne ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Sprint | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep [ 76, 77, 95, 98, 99, 101, 102 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Winter 4 Feb 8 - Feb 19 [ 76, 77, 95, 98, 99, 101, 102, 114 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Omkar Marne [ omarne ] |
| Sprint | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Winter 4 Feb 8 - Feb 19 [ 76, 77, 95, 98, 99, 101, 102, 114 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Winter 4 Feb 8 - Feb 19, Winter 5 Feb 22 - Mar 5 [ 76, 77, 95, 98, 99, 101, 102, 114, 115 ] |
| Rank | Ranked higher |
| 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 ] |
| 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 ] |
| Assignee | Jay Ostwal [ jayostwal ] |
| Resolution | Done [ 10000 ] | |
| Status | Closed [ 6 ] | To-Do [ 10305 ] |
| Sprint | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Winter 4 Feb 8 - Feb 19, Winter 5 Feb 22 - Mar 5 [ 76, 77, 95, 98, 99, 101, 102, 114, 115 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Winter 4 Feb 8 - Feb 19, Winter 5 Feb 22 - Mar 5, Spring 4 2021 May 3 - May 14 [ 76, 77, 95, 98, 99, 101, 102, 114, 115, 120 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Jay Ostwal [ jayostwal ] | Irvin Naylor [ inaylor ] |
| 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 ] |
| 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 ] |
| Assignee | Irvin Naylor [ inaylor ] | Jay Ostwal [ jayostwal ] |
| Assignee | Jay Ostwal [ jayostwal ] |
| Resolution | Done [ 10000 ] | |
| Status | Closed [ 6 ] | To-Do [ 10305 ] |
| Sprint | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Winter 4 Feb 8 - Feb 19, Winter 5 Feb 22 - Mar 5, Spring 4 2021 May 3 - May 14 [ 76, 77, 95, 98, 99, 101, 102, 114, 115, 120 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Winter 4 Feb 8 - Feb 19, Winter 5 Feb 22 - Mar 5, Spring 4 2021 May 3 - May 14, Summer 1 2023 May 15 [ 76, 77, 95, 98, 99, 101, 102, 114, 115, 120, 170 ] |
| Assignee | Kaushik Gopu [ kgopu ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Sprint | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Winter 4 Feb 8 - Feb 19, Winter 5 Feb 22 - Mar 5, Spring 4 2021 May 3 - May 14, Summer 1 2023 May 15 [ 76, 77, 95, 98, 99, 101, 102, 114, 115, 120, 170 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Winter 4 Feb 8 - Feb 19, Winter 5 Feb 22 - Mar 5, Spring 4 2021 May 3 - May 14, Summer 1 2023 May 15, Summer 2 2023 May 29 [ 76, 77, 95, 98, 99, 101, 102, 114, 115, 120, 170, 171 ] |
| Rank | Ranked higher |
| Description |
Read modules 2 and 3 the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can open and see private (as denoted by a "padlock" icon) IGB project repositories and their files under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the *master branch pipeline*. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master-32bit.exe, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * You need to run the branch pipeline “branches: IGBF-* ” on Bitbucket to create installers, rather than the “default” pipeline which creates the IGB jar file. * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the files in the private repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
Read modules 2 and 3 the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can open and see private (as denoted by a "padlock" icon) IGB project repositories and their files under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the *master branch pipeline*. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master-32bit.exe, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * You need to run the branch pipeline “branches: IGBF-* ” on Bitbucket to create installers, rather than the “default” pipeline which creates the IGB jar file. * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the files in the private repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. * Double-check that your Bitbucket username is correct in BB_AUTH_STRING by selecting Settings > Personal Bitbucket settings > Account settings > Username. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Description |
Read modules 2 and 3 the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can open and see private (as denoted by a "padlock" icon) IGB project repositories and their files under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the *master branch pipeline*. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master-32bit.exe, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * You need to run the branch pipeline “branches: IGBF-* ” on Bitbucket to create installers, rather than the “default” pipeline which creates the IGB jar file. * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the files in the private repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. * Double-check that your Bitbucket username is correct in BB_AUTH_STRING by selecting Settings > Personal Bitbucket settings > Account settings > Username. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
Read modules 2 and 3 the on-line course "Open source programming with IGB."
Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers. To build IGB installers: * Log in to bitbucket using your bitbucket user account. * Check your account has been added to the Developers group by confirming that you can open and see private (as denoted by a "padlock" icon) IGB project repositories and their files under https://bitbucket.org/account/user/lorainelab/projects/IGB * Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers. * Next, trigger the *master branch pipeline*. (See Canvas course module *Building IGB* for how to do this.) * Check that files master.dmg, master-32bit.exe, master.exe, master.sh, and master.jar got copied to the Downloads section of your fork. If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are: * You need to run the branch pipeline “branches: IGBF-* ” on Bitbucket to create installers, rather than the “default” pipeline which creates the IGB jar file. * Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available. * Your user account does not have access to the installer private content repository. Make sure that you can see the files in the private repository when logged in to bitbucket. * Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined. * Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes. * Double-check that your Bitbucket username is correct by selecting Settings > Personal Bitbucket settings > Account settings > Username. Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review. Reviewers should check that: * This ticket has a comment with a link to the developer's fork * The master branch installers are present in the fork's Downloads section * When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present. |
| Assignee | Kaushik Gopu [ kgopu ] |
| 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 ] |
| 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 ] |
| Resolution | Done [ 10000 ] | |
| Status | Closed [ 6 ] | To-Do [ 10305 ] |
| Sprint | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Winter 4 Feb 8 - Feb 19, Winter 5 Feb 22 - Mar 5, Spring 4 2021 May 3 - May 14, Summer 1 2023 May 15, Summer 2 2023 May 29 [ 76, 77, 95, 98, 99, 101, 102, 114, 115, 120, 170, 171 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Winter 4 Feb 8 - Feb 19, Winter 5 Feb 22 - Mar 5, Spring 4 2021 May 3 - May 14, Summer 1 2023 May 15, Summer 2 2023 May 29, Fall 3 2023 Oct 2 [ 76, 77, 95, 98, 99, 101, 102, 114, 115, 120, 170, 171, 179 ] |
| Assignee | Jaya Sravani Sirigineedi [ jsirigin ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Jaya Sravani Sirigineedi [ jsirigin ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Assignee | Ann Loraine [ aloraine ] |
| Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
| Status | Ready for Pull Request [ 10304 ] | 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 ] |
| Assignee | Ann Loraine [ aloraine ] | Jaya Sravani Sirigineedi [ jsirigin ] |
| Sprint | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Winter 4 Feb 8 - Feb 19, Winter 5 Feb 22 - Mar 5, Spring 4 2021 May 3 - May 14, Summer 1 2023 May 15, Summer 2 2023 May 29, Fall 3 2023 Oct 2 [ 76, 77, 95, 98, 99, 101, 102, 114, 115, 120, 170, 171, 179 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Winter 4 Feb 8 - Feb 19, Winter 5 Feb 22 - Mar 5, Spring 4 2021 May 3 - May 14, Summer 1 2023 May 15, Summer 2 2023 May 29, Fall 3 2023 Oct 2, Spring 5 [ 76, 77, 95, 98, 99, 101, 102, 114, 115, 120, 170, 171, 179, 189 ] |
| Assignee | Jaya Sravani Sirigineedi [ jsirigin ] | Dylan Marrotte [ dmarrott ] |
| Resolution | Done [ 10000 ] | |
| Status | Closed [ 6 ] | To-Do [ 10305 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | To-Do [ 10305 ] |
| 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 ] |
| 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 ] |
| Assignee | Dylan Marrotte [ dmarrott ] |