StarlingUAS / ProjectStarling

BRL Flight Arena Infrastructure 2.0
Other
16 stars 3 forks source link

Add testing framework #134

Closed rob-clarke closed 2 years ago

rob-clarke commented 2 years ago

Adds a testing framework to test images and integration

Example tests have been written for the starling-mavros image

TODO

rob-clarke commented 2 years ago

I'd like to figure out the workflow properly before merging this. I think some sort of staging tag/area would be useful as we only want a fully consistent set of images to be pushed to the dev/latest/versioned tag. At the moment I think stage 1 images will be pushed without knowing if stage 2 / 3 images pass their tests successfully.

Potentially want to push all images to a staging area/tag then have a step similar to the current release step to actually add the final tags to the images / push them to docker hub.

mhl787156 commented 2 years ago

I agree with you it does seem like a bad idea to push early ones without later ones being pushed. I will leave this in your capable hands! Shall we use github container registry? I assume that should be just as effective as Azure. Either that or you could create another organisation in docker for staging.

rob-clarke commented 2 years ago

Test infrastructure added and working. Need to ensure that the correct images are being tested before merging

rob-clarke commented 2 years ago

The caching behaviour is a little unclear still, but on my machine the entire build is able to be skipped from cache on ghcr

Will need to watch that the "named" tags are updated correctly too when this makes it into dev/master