Now that Scaffold has been forked over, we need to create a new pipeline for releases. Previously, we used Travis CI. However, there have been murmurings that TravisCI will no longer be open source in the near future. So, because of this, CircleCI is a pretty good alternative and should be used moving forward.
The work required on this ticket will be:
Modifying the group_id and artifact_id to reflect the new forked repository
Creating a new account on Travis ~CircleCI~
Creating the new pipeline on CircleCI and any required config files
Going through the Open Source OSSRH configurations again (artifact signing, repository access, etc)
Deploy script should automate the entire process. We could probably use a lot of the travis ci configuration file? These releases should auto version still.
A/C
Releases should be setup through Travis ~CircleCI~
Summary
Now that Scaffold has been forked over, we need to create a new pipeline for releases. Previously, we used Travis CI. However, there have been murmurings that TravisCI will no longer be open source in the near future. So, because of this, CircleCI is a pretty good alternative and should be used moving forward.
The work required on this ticket will be:
A/C