Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-1337

Test the IGB release & Install4J update process

        Details

        • Story Points:
          0.5
        • Sprint:
          B - Summer 2018

          Description

          Document and test IGB release/update process for IGB installers.

          IGB installer wrapper installed with any version of IGB should detect new versions of IGB and ask the user to update.

          Testing process:

          • Deploy BioViz Web content on test site. See https://bitbucket.org/lorainelab/bioviz
          • Fork https://bitbucket.org/lorainelab/integrated-genome-browser, set up BitBucket pipelines to build installers
          • Create branch, edit codeBaseUrl setting in Install4J configuration file on branch (e.g., distribution/igb_7.install4j) to point to the test server
          • Run release pipeline on testing branch of IGB
          • Deploy artifacts on test site (see instructions in igb/release directory of BioViz test site)
          • Create dummy folders with mock next version of IGB (e.g., 9.0.2 if testing 9.0.1 installer). Edit updates.xml as required for the mock next version.
          • Download and run the installer you are testing. Run this version of IGB, then quit.
          • Log back into test site and update the symbolic link to point to the mock next version of IGB.
          • Run IGB.
          • Observe that the installer asks you if you would like to update IGB. Make sure the new version is installed and runs.

            Attachments

              Activity

              Hide
              Permalink
              ann.loraine Ann Loraine added a comment - - edited

              Notes and gotchas:

              • When we upgraded to a newer version of Install4J, we failed to migrated the old applicationId from previous releases to the new Install4J configuration file. The installer then refused to over-write IGB 9.0.0 with IGB 9.0.1 because it appeared to be a different application.
              • Install4J-installed application directories contain hidden directory .install4J with settings. Use this to determine how updates are configured for a deployed application, e.g., its applicationId.
              • IGB 9.0.0 installation updater referenced a no longer existent Web page on the BioViz.org Web site. We configured BioViz.org to redirect to the correct page.
              Show
              ann.loraine Ann Loraine added a comment - - edited Notes and gotchas: When we upgraded to a newer version of Install4J, we failed to migrated the old applicationId from previous releases to the new Install4J configuration file. The installer then refused to over-write IGB 9.0.0 with IGB 9.0.1 because it appeared to be a different application. Install4J-installed application directories contain hidden directory .install4J with settings. Use this to determine how updates are configured for a deployed application, e.g., its applicationId. IGB 9.0.0 installation updater referenced a no longer existent Web page on the BioViz.org Web site. We configured BioViz.org to redirect to the correct page.

                People

                • Assignee:
                  ann.loraine Ann Loraine
                  Reporter:
                  ann.loraine Ann Loraine
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: