3 ms·
Feel this pain so much. If you are debugging Github Action container builds, and each takes over ~40 minutes to build.. you can burn through a whole work day o
by kelseydh 2y ago
Feel this pain so much. If you are debugging Github Action container builds, and each takes over ~40 minutes to build.. you can burn through a whole work day only testing six or seven changes.
There has to be a better way. How has nobody figured this out?
- elAhmo 2y agoThere is act, that allows you to run actions locally. Although not exactly the same as the real thing, it can save time. https://github.com/nektos/act https://github.com/nektos/act
- mab122 2y agoIn organization setting this is almost useless if you are (or forced to) use some pre-made actions and/or actions that are for your organization only (they cannot be downloaded) also useless if you are forced to use self hosted runner with image that you don't have access to. Not to mention env/secrets and networking...
- terminalbraid 2y agoThis is a great tool, but I always cringe when something so important comes from a third party
- deleted 2y ago[deleted]
- cantagi 2y agoact is brilliant - it really helps iterate on github or gitea actions locally.
- esafak 2y agoThere's dagger; CI as code. Test your pipeline locally, in your IDE.