Hi @actuallyamitsq ,
the upgrade is rather manual by design as you should always prepare a backup of your database prior to upgrading as well as inform your users about it specially when it comes to upgrading to an LTS as it can take quiet some time to do so.
nevertheless there are a few points that might help you to design a pipeline that updates your instance automatically:
There are tools that search for newer images on the docker hub and deploy them automatically, but i am not aware of any that run on fargate. you could still store the sha256 hash of the image and compare it against a manual pull in a pipeline to check if there is a new image available on the docker hub. for this you should use the tag
sonarqube:8-enterprise. of cause you need to change this when we release the 9.x series in the future, but there will of cause be an announcement from our side about that.
So now that you are aware of a new image and re deployed sonarqube using this new image is the question of database migrations on the table. to trigger a database migration via the api you can use the following api endpoint:
a documentation to this api endpoint can be found in the embedded documentation in your sonarqube instance (questionmark → web api), but this one only needs a
POST and that’s it. if this call is needed can be checked using
if you need to migrate your database it will return
The database migration can take some time.
For the LTS upgrade as you are already on the 8.x release this should be yet another normal update for you. when you jump from LTS to LTS the procedure will be the same, but will take longer.
As a last note you should check that, if you are using 3rd party plugins, they are compatible with the new version. for the embedded language analyzers you can assume that there will be no issue but for community plugins you have to manually check.
hope this helps you to get a better picture of how to automate the update procedure of sonarqube