Steps for deploying a component to the TA3 testbed
Create a PR into the master/main branch with the necessary changes. Also, if there is a file like
version.sbtthat contains the version number, bump the version number in it appropriately.
Bugfixes will increment the patch version number (e.g. 3.0.1 to 3.0.2).
New backwards-compatible features and improvements will update the minor version number (e.g. 3.0.1 to 3.1.0). Here, backwards-compatible means that the format of the JSON messages either does not change or changes in a way that code that could process the previous format can also process the new format. For example, adding a key in the
datapart of the message would be backwards-compatible, while removing an existing key would not.
Backwards-incompatible changes should bump the major version number (e.g. 3.0.1 –> 4.0.0)
Once the CI tests pass, merge the PR into the main branch.
Create a release on Github.
Switch to the main/master branch, run
git pullto make sure you have the latest code, then run
Go into the TA3 testbed repo
Switch to the
git pullto make sure you have the latest code from the
Make a new branch off of
Update the agent version number in the
.envfile if you are using that to set the version numbers) in your agent directory under the
Agentsdirectory. The agent version number should match the version you just deployed to the Gitlab container registry.
releaseNotes.md(located in the top-level
testbeddirectory) file with a summary of the changes.
Push your changes to the testbed upstream repository
Check the changes to the code and make sure your edits are there.
Go to the testbed repo webpage in your browser, and then create a merge request to merge your branch into the
Include a link to the GitHub release you created in the testbed merge request.
Once the your merge request is accepted, delete the branch in the testbed repo.