sebastianliebscher opened a new pull request, #24473:
URL: https://github.com/apache/superset/pull/24473

   ### SUMMARY
   On Docker Hub Superset has published over 20k tags so far with most of them 
not being a release tag. This is a huge amount of unnecessary tags hosted 
Docker Hub.
   
   Currently, there are three scenarios of pushing tags:
   
   - on PR by Superset committer
   ```
     Rolling with tags:
     - apache/superset:add536543b3d96774fbdebdc6c36ae286a3a329e
     - apache/superset:elizabeth-fix-examples-load
     - apache/superset:pr-24410
   ```
   example: 
https://github.com/apache/superset/actions/runs/5282886796/jobs/9558388071
   
     
   - on commit to master
   ```
     Rolling with tags:
     - apache/superset:d5f88c18f61cc919a8bdecfa92251d0d4d35abac
     - apache/superset:master
     - apache/superset:latest
   ```
   example: 
https://github.com/apache/superset/actions/runs/5333985229/jobs/9665184088
   
   - on release
   ```
     Rolling with tags:
     - apache/superset:2817aebd69dc7d199ec45d973a2079f35e5658b6
     - apache/superset:2.1.0
     - apache/superset:2.1.0
   ```
   example: 
https://github.com/apache/superset/actions/runs/4613689991/jobs/8155936157
   
   The tags `master` and `latest` are identical. I think `master` can be 
removed as common practice is to use `latest` tag. Also, the image SHA tags 
don't seem to be used by any other CI job.
   I recommend reducing the pushed image tags to:
   
   - on PR by Superset committer
   ```
     Rolling with tags:
     - apache/superset:pr-24410
   ```
   
   - on commit to master
   ```
     Rolling with tags:
     - apache/superset:latest
   ```
   
   - on release
   ```
     Rolling with tags:
     - apache/superset:2.1.0
   ```
   
   The ephemeral env workflow shouldn't be affected by this, as it uses the 
"pr-(number)" image
   example: 
https://github.com/apache/superset/actions/runs/5293709377/jobs/9582193999
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to