docker issueshttps://0xacab.org/leap/docker/-/issues2018-10-08T13:42:28Zhttps://0xacab.org/leap/docker/-/issues/5Use "changes" CI parameter to detect file changes2018-10-08T13:42:28ZVaracUse "changes" CI parameter to detect file changesWe are using a self-baked mechanism to detect if certain files changed.
Gitlab now introduced the "changes" parameter just for this case:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21981/diffs#b846104e9f7364189580726a297509c...We are using a self-baked mechanism to detect if certain files changed.
Gitlab now introduced the "changes" parameter just for this case:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21981/diffs#b846104e9f7364189580726a297509c92ae8c5de_448_455https://0xacab.org/leap/docker/-/issues/2only build images based on master branch2017-09-06T06:20:25Zazulonly build images based on master branchThe repository will always serve the last image build. If we build images based on other branches we might end up overwriting the current image with builds based on outdated or WIP Dockerfiles.
(based on discussion in !3)The repository will always serve the last image build. If we build images based on other branches we might end up overwriting the current image with builds based on outdated or WIP Dockerfiles.
(based on discussion in !3)https://0xacab.org/leap/docker/-/issues/1Schedule builds to update packages regularly2019-05-24T16:42:53ZazulSchedule builds to update packages regularlybased on discussion in !3
Tried to achieve this in riseuplabs/docker: https://0xacab.org/riseuplabs/docker/pipeline_schedules
Turns out it does not work due to the docker caching logic. If the Dockerfile does not change at all it will ...based on discussion in !3
Tried to achieve this in riseuplabs/docker: https://0xacab.org/riseuplabs/docker/pipeline_schedules
Turns out it does not work due to the docker caching logic. If the Dockerfile does not change at all it will also cache 'apt update' and the like. The caching can be disabled with a flag - which is what i planned to do for the scheduled builds next.
Micah proposed to use a cron job in !3. Not sure which path we want to follow here.