Process: Cloudsmith repositories

[rgleason]

Cloudsmith Deployment Process.

2. From a subbranch For Collaborators and me a normal commit and push is to CS-[plugin]-alpha.
3. From a subbranch For Collaborators and me a normal commit with a version number and tagged push is to CS[plugin]-beta
4. From the master branch for me a normal commit with a version number and tagged push is to CS[plugin]-prod. The metadata files are then copied into plugins catalog and published. The corresponding tarballs must be in CS[plugin]-prod

Cloudsmith Download Links

Using celestial_navigation_pi as an example

Current Incremented Version 2.4.48.0
https://cloudsmith.io/~opencpn/repos/celestial-navigation-beta/packages/?q=2.4.48+tarball

Cloudsmith celestial-navigation-alpha

First place to look
Normal deployments from CircleCI from any "non-master" branches, from Stelian's merges of commits (only works for a limited time period after rgleason commits - we think)
https://cloudsmith.io/~opencpn/repos/celestial-navigation-alpha/packages/
In the upper right search bar do a search with [version][space][tarball]
Pick your version of OS carefully to download and install using Options>PI "Import Plugin Tarball"

Cloudsmith celestial-navigation-beta

Use If the "improve" branch has had version incremented. Also can be published to Plugin Beta Catalog
Normal deployments from CircleCI from "master" branch.
Version Incremented deployments from CircleCI from "non-master" branches.
https://cloudsmith.io/~opencpn/repos/celestial-navigation-beta/packages/
In the upper right search bar do a search with [version][space][tarball]
Pick your version of OS carefully to download and install using Options>PI "Import Plugin Tarball"

Cloudsmith celestial-navigation-prod

When published to the plugin master catalog with new version, from the master branch
Version Incremented deployments from CircleCI from "master" branch only.
https://cloudsmith.io/~opencpn/repos/celestial-navigation-prod/packages/
In the upper right search bar do a search with [version][space][tarball]
Pick your version of OS carefully to download and install using Options>PI "Import Plugin Tarball"

Published Plugin "Beta" Catalog (new version numbers)

Because we are using the "improve" branch, a "non-master" branch, I can publish the incremented version builds to the Plugin Beta Catalog, which is accessible from within OpenCPN. However access to the Plugin Beta Catalog is only possible after you have enabled "catalogexpert" by editing your opencpn.ini or opencpn.conf file. Enable catalogexpert.

Then in Opencpn>Options > Plugins you need to set the catalog to "Beta" and then "Update the Beta Catalog". Then install the plugin normally.

These published plugins require me to push metadata files to opencpn/plugins and then Dave reviews and "publishes" the new version, so it may take awhile after the build. Using Cloudsmith tarballs is faster.

[jongough]

There is one more build process, a merge into master will create a CS-[plugin]-beta set of installables. It is only when a tag is created does it end up in CS-[plugin]-prod.

This issue with using the alpha repository is the amount of churn in it. If you are going to have a few people generating for it you may need to increase the number of files that are kept in the repository or the length of time they can exist there. Another good reason to comment out any environments you do not NEED to build for.

My process normally goes through alpha->beta->prod. In each of these environments when I think I have it stabilised enough I will update the plugins catalog so that the version is easily installable without having to do a manual download.

The main thing is to make sure you have new, incrementing, version numbers for most changes that are built. In alpha it is a bit of a free for all, so could get messy, but for beta and prod care would need to be taken that the version number does increase with each push/merge so that the latest version is easily found. If this proves difficult then create user specific cloudsmith repositories and change the 'CLOUDSMITH_BASE_REPOSITORY' or 'CLOUDSMITH_USER' in the CMakeLists.txt file to reflect where you want the uploads to go.