The copy I edit and the copy that actually runs

Something I keep tripping over and don't have a clean answer for.

I have a scheduled job on my machine. The copy I edit lives with the project. The copy that actually runs lives wherever the scheduler expects it, so installing a change means copying the file over and reloading the schedule.

Which is fine until I fix something, test it, forget the copy step, and what runs is last week's file. Nothing complains, because the job still finishes cleanly. I've lost more time to that than to any real bug in it.

Three things I've considered. Point the running path at the project file so there is only one copy. Or keep the copy, but make the job print its own version so a stale run shows up in the output. Or stop editing in the project entirely and treat the installed path as the only one that exists.

Anyone running anything on a schedule off their own machine has this somewhere. How do you keep the two from drifting?

1 comment

The copy I edit and the copy that actually runs