On Fri, Dec 15, 2017 at 02:17:40AM +0100, Igor Djordjevic wrote:
>
> This said, and without having you to change your habits too much (nor
> use Git in possibly awkward ways), I`m thinking you may actually
> benefit of using `git worktree add <temp_copy_path>`[1] to create a
> temporary working tree ("working copy", as you say), alongside a
> temporary branch, where you could hack and test as much as you want,
> unaffected by cron job updating and executing the original working
> copy/branch (also not stepping on cron job`s toes yourself).
Interesting command. Did not know about it. Will remembre it for other use
cases!
But in this case, it is not of much use. See, I am doing system configuration
with those scripts. Having two working trees would cause the configuration to
be restored every time cron happens to start the scripts.
Doing the modifications right there where cron executes has the benefit that
cron uses the same modifications which I am using. This way, whenever cron
decides to execute, it is exactly the same as if I would do a "make run" on
the command line. Since all the scripts are designed to be idempotent,
everything works pretty much flawlessly.
--
Josef Wolf
jw@xxxxxxxxxxxxx
