There are four version available:
InstallerCreatorV1
- Currently used for GSA and AdSec.
- Doesn't use the SP number in builds.
- The version numbers are obtained by looking at the source path of the build.
InstallerCreatorV2
- Currently used for all of the Geo programs.
- Does use the SP number in builds.
- The version numbers are obtained by looking at the properties of the program executable.
InstallerCreatorV3
- An update to
InstallerCreatorV2
. The programs64.txt list of files required to build an installer is now referenced directly from the oasys-combined repo rather than from the oasys-windows-installer one. This ensures that the list of files required to build an installer for a program is versioned alongside the code for that program.
- An update to
InstallerCreatorV4
- An update to
InstallerCreatorV3
. Code signing now needs to be done with a certificate which is stored in an HSM. Here, we've added the ability to pass aClientId
and aClientSecret
which are required to access the Azure Key Vault where the cert is kept. The values are added as arguments to themake clean all
call which invokes the Wix3 installer building process.
- An update to
After making changes, it's important to update the task version in the relevant task.json
file. For example:
"version": {
"Major": 2,
"Minor": 1,
"Patch": 0
}
If you change the Major
version number, then you'll have to update any task entries in the build pipelines in order to use the new version.
If you change the Minor
or Patch
version numbers, then the new version of the task will be picked up automatically by any new runs of the build pipelines.
Check that the task has been updated in Azure Devops. Go to Organization -> Extensions
and make sure that you can see the updated version of the Oasys Installer Create Task
.
Any re-runs of existing jobs will continue to use the old task. Instigate a new run if you want to use the new task.