brick
brick copied to clipboard
electricitymaps
Simple monorepo build tool based on Docker
Bumps [arrow](https://github.com/arrow-py/arrow) from 0.12.1 to 0.15.1. Release notes Sourced from arrow's releases. Version 0.15.1 [FIX] Fixed a bug that caused Arrow to fail when passed a negative timestamp string. [FIX]...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
To reproduce: 1. add an `BRICK_` env variable as part of a command in the build step 2. run the prepare step without the env variable (`brick prepare`) 3. brick...
The caching mechanism checks for file inputs, and might abort a docker build if the inputs haven't changed. However, other informations might invalidate the build, such as e.g. an environment...
Seems like it's broken again for some reason.. Haven't dived too deep into it, but as far as I can tell, it finds images with same dependency-hash yet still builds...
We could enable current builds by having multiple `brickdockerfile` files and an overview of dependencies. Note that it will complicate the code and make debugging harder.
Origin https://github.com/tmrowco/brick/issues/3 TBD
Looking through different brick `BUILD.yaml` files, I noticed that in some steps `command` is used while in some others there is a list of `commands`. I assumed the two are...
This could be useful to cache builds even further. For example, a first prepare step could install apt packages (almost never modified), another could install python requirements (sometimes modified)
We could make sure the CLI autoupdates: https://bitbucket.org/jorkar/autoupgrade/src/master/ Some more links: - https://circleci.com/blog/continuously-deploying-python-packages-to-pypi-with-circleci - https://packaging.python.org/tutorials/packaging-projects/