Setup infrastructure to make an automated release

niclas86 commented 1 year ago

We have done a small change, the pull request #66 We want to give Mangala and Vadim a try to release with the information provided by @peturv

niclas86 commented 1 year ago

@peturv will make a release soon with 1.0.2

niclas86 commented 11 months ago

The PR has been released, @claudiaehr will do the release

niclas86 commented 6 months ago

We want to be able to do a deployment from an action when a valid tag has been created

vadi2 commented 5 months ago

In addition to building when a tag has been created, we need to deploy the output to https://commonprofiles.care using SFTP.

Actions to do:

[x] create a new job to build when a semver tag in master has been created that will both validate the tag format and create output.zip with the IG: https://github.com/commonprofiles-care/fhir/issues/103
[x] create SFTP credentials for the upload job: https://github.com/commonprofiles-care/fhir/issues/104
[ ] create a separate job to deploy the IG output to https://commonprofiles.care using SFTP: https://github.com/commonprofiles-care/fhir/issues/105
[ ] update build job to generate new package-list.json and history.html: https://github.com/commonprofiles-care/fhir/issues/113
[ ] test the upload solution with a sample release: https://github.com/commonprofiles-care/fhir/issues/106
[ ] document release automation at a high level: https://github.com/commonprofiles-care/fhir/issues/107

https://commonprofiles.care is a wordpress website run by Niclas and Petur.

vadi2 commented 3 months ago

We missed a step in planning, package-list.json and history.html need to be dynamically updated for the new release. Created a ticket for this.

commonprofiles-care / fhir