Open ermshiperete opened 1 year ago
Yes we still need to be able to build the ChorusHub installer.
Per this article, it should be straightforward: https://drumcoder.co.uk/blog/2022/jun/18/wix-installer-from-github-action/
Well, the Chorus Hub installer builds, but when I try to send to it, it fails to get the remote project.
Exception: The internet server reported that it is having problems. There isn't anything you can do about that except try again later.
at Chorus.VcsDrivers.Mercurial.HgRepolitory.PullFromTarget(String targetLabel, String targetUri)
When we moved the build to GitHub Actions building the ChorusMergeModule and ChorusHubInstaller was accidentally left out.
We should add building the ChorusMergeModule to
dotnet.yml
and save it as an artifact.Also check if the ChorusHubInstaller is still needed - in a discussion on slack it was noted:
However, it seems that
ChorusMergeModule.msm
andChorusHubInstaller.msi
got build as part of the regular builds (targetsInstaller ChorusHubInstaller
).Check
build/Chorus.proj
prior to commit e7ab5bcca7ae571374eb9c8d742a1975aec453f3 and TC for how it was done in the past.ToDo
dotnet.yml
dotnet.yml
dotnet.yml
) where ChorusMergeModule (and ChorusHubInstaller) is used (in FieldWorks and FLEx Bridge installers)