search

bcgov / orgbook-configurations

Build and Deployment Configurations for the Indy-Catalyst version of the OrgBook
Apache License 2.0
3 stars 11 forks source link

Deploy to production the latest OrgBook BC Code #105

Closed swcurran closed 2 years ago

swcurran commented 3 years ago

Please prepare a release of OrgBook BC and push it to production. This is mostly done as the latest code is on Dev and Test. Things that I'm not aware are done:

  1. Tag Aries VCR with a release tag for what is being deployed, so that we have visibility into what has changed since the last deployment (OCP 4 launch).
  2. Likewise, tag the OrgBook BC Client. This is the first release, so we won't be able to see what's changed, although some of it was done in both AVCR and OrgBook BC Client, so we should have some visibility.
  3. Decide with the team on a deployment date, so I can notify those interested.

Please provide enough time between the tagging and the deployment so I can get a notification out.

Thanks

@WadeBarnes @amanji @ianco @CharlesMacpherson

WadeBarnes commented 3 years ago

The initial release of the bcgov/orgbook-bc-client was just completed. The PR for removing the client code from bcgov/aries-vcr id here; Client extraction

I'll generate the tags/release once we're certain what revision of code is going to prod.

swcurran commented 3 years ago

@amanji @ianco -- Please let Wade know what code is going to prod. He's waiting on that, per above.

WadeBarnes commented 3 years ago

I'm hoping for latest of both bcgov/aries-vcr and bcgov/orgbook-bc-client once we get the Client extraction PR merged. That way we have all our significant project reorg/refactor out of the way.

WadeBarnes commented 3 years ago

@amanji, Is this release going to require a Solr re-indexing?

amanji commented 3 years ago

There shouldn't be a reindex required. The main branch for both repos should have the latest changes that are in production. There is a branch that is relevant for the Issuer Agency called issuer-agency which will add support for some 2.0 protocol handling but that will likely get merged a bit later.

WadeBarnes commented 3 years ago

@ianco, @amanji, and I had a quick meeting to review the changes between prod and the latest code. We've confirmed none of the changes will require a re-indexing, and there are no issues that need to be addressed before release to prod. I'm going to deploy the latest code to test for a smoke test.

WadeBarnes commented 3 years ago

@swcurran, @ianco and @amanji have smoke tested everything in the test environment. As for release tags, are you happy with 1.7.0 for bcgov/aries-vcr, and 1.0.0 for bcgov/orgbook-bc-client? Additionally we can release anytime. Would the morning of 2021.06.03 (this Thursday) give you enough time to notify everyone?

swcurran commented 3 years ago

That sounds good. To confirm -- everything since 0.6.0 in Aries VCR is going to be added -- 83 commits. Is that right?

WadeBarnes commented 3 years ago

That sounds good. To confirm -- everything since 0.6.0 in Aries VCR is going to be added -- 83 commits. Is that right?

Everything since the Aries VCR 1.6.0 release, which is what is currently in prod.

WadeBarnes commented 3 years ago

@amanji, @ianco, Could you add details on any additional relevant changes to these release notes please:

amanji commented 3 years ago

Looks like @swcurran covered the major changes in his email notification.