TL;DR: Read Highlights

pyRevit CI/CD

I have recently completed the first draft of a Continuous Integration/Continuous Deployment workflow for pyRevit on Github Actions.

• From now on, on every pyRevit change, the CI/CD system will automatically build and release installers for the most recent pyRevit
• pyRevit contributors no longer have to wait for a long time for the PRs to get merged into a public release

Versioning

pyRevit releases are going to continue the semantic versioning (major.minor.patch e.g. 4.8.8) as before. But from now on, version numbers are going to include build markers as well.

For example in:

4 . 8 . 9 . 21273+0456

4.8.9 is the pyRevit version and the 21273+0456 part is the build number in the format <year><day of year>+<hour><minute>.

The example pyRevit was built on 04:56 UTC of the 273rd day of 2021 (September 30th)

Installers

The CI/CD will automatically generate installers and publish to Github Releases section. There are a few important notes about the new installers:

• There are separate Admin (admin in exe name) and User installers. The Admin installer installs under %PROGRAMDATA% and User installer under %APPDATA% by default

• These installers are built using InnoSetup with a different set of command line arguments. See the link for /DIR= (There are /ALLUSERS and /CURRENTUSER availabe but use the Admin installer if you want to install for all users instead)

• pyRevit Installer now has optional components. You do not need to clone the full repo just to get the pyRevitDev extension anymore

  

Work-In-Progress (WIP) Installers

On every commit to pyRevit develop branch, the CI/CD system will build a new version of pyRevit WIP.

• The version numbers end in -wip for the WIP builds e.g. v4.8.9.21361+0320-wip
• All installers include -wip in their name e.g. pyRevit_4.8.9.21361+0320-wip_signed.exe