• Create pipelines.yml, add to top level of IGB directory

features: uses custom Docker image as build environment; obtains private assets from private repository; uses sed to edit files in build environment as required; signs installers

• Modify main project pom.xml to include Install4J process

• Create Dockerfile and Docker container w/ build environment.

• Docker image contains: Mac, Windows, Linux JRE for packaging with IGB installer (required by Install4J)

• Deploy as private (for now) docker image at https://hub.docker.com/u/lorainelab/

• Build optional plug-ins

Test:

• Create fork
• Configure environment variables (passphrase for jar-signing key, Install4J license key)
• Download, install, check it runs
• Deploy on BioViz in new folder named for release (e.g., 9.0.1); test again
• Check functionality with optional plugins

Deploy:

• Update releases symbolic link

I was able to spend some time testing the IGB Installers deployed by Bitbucket Pipelines and have verified that IGB installs properly on Windows, Mac, and Linux, using the installation files available here: https://bitbucket.org/aloraine/integrated-genome-browser-sanket-patil/downloads/

When installing IGB on Windows, a warning from the OS does trigger. However, I always see this warning when installing any version of IGB other than the live version (from Bioviz.org). I wanted to mention this, though, because this warning says the publisher is "Unknown" (see attached screenshot). After I select to "Run Anyway" the installer begins, but then another pop-up appears asking me if I'd like to allow the app to make changes to my device. In this pop-up, the publisher listed is "University of North Carolina at Charlotte". The lack of an identified publisher in the first warning may be an issue we want to discuss, but I do not believe this has anything to do with the switch to Pipelines. Also, I believe that users will never see the initial warning, as they do not see it now when installing from Bioviz.org even though I see it when installing the Development branch.

I also checked to verify that IGB is functioning as expected, and it seems to be, but I would like to continue testing in this area to see if any of IGB's subsystems are affected by the switch to Pipelines. If there is anything else you would like me to look into or focus on during my testing, please let me know.

Code review and functional review both pass.
Please issue pull request to master branch on team repo.

Attaching mail conversation related to warning 'Unknown Publisher' for future references.

While testing the 9.0.1 release candidate's zip file, I noticed that it contained an unnecessary folder structure when unzipped:

"opt/atlassian/pipelines/agent/build/content"

The file structure for the current live version of the IGB zip file (9.0.0) is "IGB/content", which is more user-friendly.

I am re-assigning this issue to Sanket and moving to the To-Do column so he can take a look.

Please note:

The installers are now being built on the IGB master branch.

I have not yet made a release candidate fork.

Mason, do switch to testing installers from:

https://bitbucket.org/lorainelab/integrated-genome-browser/

(Click Downloads link to obtain installers built from the master branch.)

Hello Ann,

https://bitbucket.org/lorainelab/integrated-genome-browser/ is where I am testing the installers from.

I guess I used the term "release candidate" inappropriately. I was just calling this the "release candidate" because I was under the impression that this is what would be released if there were no issues to fix.

My comment above is actually specific to the IGB.zip file available from Bitbucket Pipelines, here: https://bitbucket.org/lorainelab/integrated-genome-browser/downloads/

Because of this, I thought we might want to look into why there are so many extra folders now when the IGB.zip file is unarchived.

Hello Mason and Ann,
I have created a new issues IGBF-1191 and IGBF-1192.
IGBF-1191 deals with introducing two new bitbucket pipelines environment variables
IGBF-1192 deals with igb.zip issue.

Both issue are linked to IGBF-1178

With this new change, I can successfully install IGB on Linux, Mac, and Windows using the builds available from Bitbucket Pipelines. The available IGB Zip file contains the correct hierarchy (see IGBF-1192) and the Bitbucket Downloads page contains appropriate files (see screenshot). I have been testing various aspects of IGB to ensure stability after this change and at this point, everything seems to be functioning as expected in relation to the migration of IGB CI from Jenkins to Bitbucket Pipelines. I will continue to monitor this as I perform pre and post-release testing, but as of now I am marking this issue as resolved.