You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running my GitHub actions from self hosted runners for my enterprise. We are consistently running into issues with dockerhub rate limits, and forcing people to login to our artifactory and so forth in order to build containers. Where we can we prefer to not have to do so and run everything from within GitHub actions and not have to call out to artifactory to proxy to dockerhub.
Due to pull limits for dockerhub, is it possible to add a GitHub Container Registry option of the docker containers used so that when pulling occurs it uses GitHub Actions auth to pull the containers.
Another option would be to add an action that just simply downloads liquibase and sets it up for use via cli just like the other issue mentioned before that was closed: #119
As of today we just have to download the binary and set up our environment ourselves, but it would be nice to not have to do all that custom code.
The text was updated successfully, but these errors were encountered:
I am running my GitHub actions from self hosted runners for my enterprise. We are consistently running into issues with dockerhub rate limits, and forcing people to login to our artifactory and so forth in order to build containers. Where we can we prefer to not have to do so and run everything from within GitHub actions and not have to call out to artifactory to proxy to dockerhub.
Due to pull limits for dockerhub, is it possible to add a GitHub Container Registry option of the docker containers used so that when pulling occurs it uses GitHub Actions auth to pull the containers.
Another option would be to add an action that just simply downloads liquibase and sets it up for use via cli just like the other issue mentioned before that was closed: #119
As of today we just have to download the binary and set up our environment ourselves, but it would be nice to not have to do all that custom code.
The text was updated successfully, but these errors were encountered: