Skip to content

Conversation

@ColmBhandal
Copy link
Owner

Description

Updated the build workflow:

  1. The YML file now controls the build in a CI flow, without repetition of tasks (hopefully). Prior to this it looks like there was repetition because of subsequent build tasks including previous ones e.g. dotnet build includes a restore. Looks like there was also repetition due to the fact that the build.sh file was being called to do the build & pack, which seemed to repeat the build that the YML file just did.
  2. The YML file is now set up to build on new tags. This will allow for the new release strategy: a new build should be triggered when a new release & tag are created.
  3. The build.sh file was removed, as it is no longer used. The YML is now the controller of the build logic.

Hopefully this triggers build when new tag is created for release through GitHub
Prior to this, the workflow was a mix between YML and using the .sh file
The YML workflow now does those steps
@ColmBhandal ColmBhandal linked an issue Dec 14, 2021 that may be closed by this pull request
@ColmBhandal
Copy link
Owner Author

@ColmBhandal ColmBhandal linked an issue Dec 15, 2021 that may be closed by this pull request
@ColmBhandal ColmBhandal merged commit 8d163f8 into develop Dec 15, 2021
@ColmBhandal ColmBhandal deleted the feature/update-build-and-release-strategy branch December 15, 2021 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Write a Wiki Page Defining our Breaking Changes Practices Formalise Semantic Versioning & Release Strategy

3 participants