Difference between revisions of "Continuous Integration"
Jump to navigation
Jump to search
(Created page with "= Continuous Integration and Deployment = == Release == It is recommended that a release be made when the project is passed testing, to do this create a GitHub release for the...") |
|||
| Line 1: | Line 1: | ||
| − | + | = Release = | |
| − | |||
It is recommended that a release be made when the project is passed testing, to do this create a GitHub release for the repository giving a tag name a valid semantic version (e.g. this would usually be <code>v1.0.0</code> for the first version). Doing this triggers the automatic deployment pipeline which creates a package of the files required for users to run your simulation, this package follows the standard package form and can be uploaded to the [[RailOS]] website. | It is recommended that a release be made when the project is passed testing, to do this create a GitHub release for the repository giving a tag name a valid semantic version (e.g. this would usually be <code>v1.0.0</code> for the first version). Doing this triggers the automatic deployment pipeline which creates a package of the files required for users to run your simulation, this package follows the standard package form and can be uploaded to the [[RailOS]] website. | ||
Latest revision as of 21:42, 3 December 2022
Release
It is recommended that a release be made when the project is passed testing, to do this create a GitHub release for the repository giving a tag name a valid semantic version (e.g. this would usually be v1.0.0 for the first version). Doing this triggers the automatic deployment pipeline which creates a package of the files required for users to run your simulation, this package follows the standard package form and can be uploaded to the RailOS website.