[IGBF-3945] Deploy release candidate branch release-10.1.0 to early access section - JIRA UNCC

Details

Type: Task
Status: Closed (View Workflow)
Priority: Major
Resolution: Done
Affects Version/s: None
Fix Version/s: None
Labels:
None

Story Points:
0.25
Epic Link:
Release IGB 10.1.0
Sprint:
Fall 4, Fall 5

Description

Update early access version available on the bioviz.org website to be from branch release-10.1.0 instead of branch main.

For this, need to provide a new parameter in the inventory file being used to update the web site.

Attachments

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Ann Loraine added a comment - 21/Oct/24 9:48 AM - edited

Revised inventory file by adding a new parameter early_access_branch - see below:

[targets]
ubuntubioviz2 ansible_host=52.207.108.150 domain=bioviz.org stack=Prod igb_branch=release-10.0.1 igb_version=10.0.1 igb_major_version=10 igb_repository=https://bitbucket.org/lorainelab/integrated-genome-browser bioviz_repo=https://bitbucket.org/lorainelab/bioviz.git bioviz_version=main hub_facade_domain=translate.bioviz.org maven_domain=maven.bioviz.org early_access_branch=release-10.1.0

[targets:vars]
ansible_ssh_common_args="-o StrictHostKeyChecking=no"
ansible_ssh_user=ubuntu

Updated security group to include a rule allowing ssh from my local machine's IP address.

Then, ran the playbooks with:

ansible-playbook -i inventory.ini setup.yml

with setup variables defined:

#
# Define the following variables to provision and update
# a BioViz host.
#

#
# certificate authority chain file, e.g., Digicert.crt
# put it in files directory
#
ssl_chain_file: STAR_bioviz_org.ca-bundle

#
# domain private key, e.g., star_mydomain.key
# put it in files directory
#
ssl_cert_key_file: bioviz.org.key

#
# domain certificate, e.g., star_mydomain.crt
# put it in files directory
#
ssl_cert_file: STAR_bioviz_org.crt

#
# e.g., 1.1.9
#
# See: https://bitbucket.org/lorainelab/genoviz-sdk
#
genoviz_version: 1.1.9

Show

Ann Loraine added a comment - 21/Oct/24 9:48 AM - edited Revised inventory file by adding a new parameter early_access_branch - see below: [targets] ubuntubioviz2 ansible_host=52.207.108.150 domain=bioviz.org stack=Prod igb_branch=release-10.0.1 igb_version=10.0.1 igb_major_version=10 igb_repository=https: //bitbucket.org/lorainelab/integrated-genome-browser bioviz_repo=https://bitbucket.org/lorainelab/bioviz.git bioviz_version=main hub_facade_domain=translate.bioviz.org maven_domain=maven.bioviz.org early_access_branch=release-10.1.0 [targets:vars] ansible_ssh_common_args= "-o StrictHostKeyChecking=no" ansible_ssh_user=ubuntu Updated security group to include a rule allowing ssh from my local machine's IP address. Then, ran the playbooks with: ansible-playbook -i inventory.ini setup.yml with setup variables defined: # # Define the following variables to provision and update # a BioViz host. # # # certificate authority chain file, e.g., Digicert.crt # put it in files directory # ssl_chain_file: STAR_bioviz_org.ca-bundle # # domain private key, e.g., star_mydomain.key # put it in files directory # ssl_cert_key_file: bioviz.org.key # # domain certificate, e.g., star_mydomain.crt # put it in files directory # ssl_cert_file: STAR_bioviz_org.crt # # e.g., 1.1.9 # # See: https: //bitbucket.org/lorainelab/genoviz-sdk # genoviz_version: 1.1.9

4 older comments

Hide

Permalink

Ann Loraine added a comment - 01/Nov/24 9:24 AM - edited

Thanks for letting me know about the missing commit.

Update:

Running the "build installers for dev" pipeline on branch release-10.1.0
Also running the "release" pipeline on branch release-10.1.0

Probably I should not have run both pipelines. Pipeline "release" does exactly the same thing as "build installers for dev" pipeline plus makes a couple extra files

Show

Ann Loraine added a comment - 01/Nov/24 9:24 AM - edited Thanks for letting me know about the missing commit. Update: Running the "build installers for dev" pipeline on branch release-10.1.0 Also running the "release" pipeline on branch release-10.1.0 Probably I should not have run both pipelines. Pipeline "release" does exactly the same thing as "build installers for dev" pipeline plus makes a couple extra files

Hide

Permalink

Ann Loraine added a comment - 01/Nov/24 10:02 AM

I have deployed the newly built installer to bioviz.org. Please check now. Also, it is now notarized.

Show

Ann Loraine added a comment - 01/Nov/24 10:02 AM I have deployed the newly built installer to bioviz.org. Please check now. Also, it is now notarized.

Hide

Permalink

Nowlan Freese added a comment - 01/Nov/24 1:43 PM

Ann Loraine - Both Windows and Mac on the early access site are throwing security errors as if they are not signed/notarized. The name of the Windows file is not the same as the file I signed in ~~IGBF-3964~~, can you check that the new files have been deployed to early access?

Show

Nowlan Freese added a comment - 01/Nov/24 1:43 PM Ann Loraine - Both Windows and Mac on the early access site are throwing security errors as if they are not signed/notarized. The name of the Windows file is not the same as the file I signed in IGBF-3964 , can you check that the new files have been deployed to early access?

Hide

Permalink

Ann Loraine added a comment - 12/Nov/24 11:32 PM - edited

The problem was in how I specified the early access release branch. Our release branch pipeline includes only the version of IGB in the file name, not the branch name. I was able to fix the problem by re-running the playbooks with early accession branch variable set to 10.1.0 instead of release-10.1.0.

I downloaded the early access file for Mac and was able to install it without observing any warnings about an un-notarized application.

I don't understand how I missed this! Very bad

Show

Ann Loraine added a comment - 12/Nov/24 11:32 PM - edited The problem was in how I specified the early access release branch. Our release branch pipeline includes only the version of IGB in the file name, not the branch name. I was able to fix the problem by re-running the playbooks with early accession branch variable set to 10.1.0 instead of release-10.1.0. I downloaded the early access file for Mac and was able to install it without observing any warnings about an un-notarized application. I don't understand how I missed this! Very bad

Hide

Permalink

Nowlan Freese added a comment - 15/Nov/24 4:35 PM

Early access is now pointing at main branch 10.2.0. I assume this is correct as we have now released 10.1.0. Tested on Mac and Windows.

Closing ticket.

Show

Nowlan Freese added a comment - 15/Nov/24 4:35 PM Early access is now pointing at main branch 10.2.0. I assume this is correct as we have now released 10.1.0. Tested on Mac and Windows. Closing ticket.

People

Assignee:

Ann Loraine

Reporter:

Ann Loraine

Votes:

0 Vote for this issue

Watchers:

2 Start watching this issue

Dates

Created:

21/Oct/24 9:47 AM

Updated:

15/Nov/24 4:35 PM

Resolved:

15/Nov/24 4:35 PM