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 main branch pipeline. (See Canvas course module Building IGB for how to do this.)
• Check that files IGB-macos-universal-main.dmg, IGB-windows-amd64-main.exe, IGB-linux-amd64-main.sh, and main.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 pipeline “custom: build-installers-for-dev ” on Bitbucket to create installers, rather than the “custom: manual-build” 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 main 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.