Scheduled jobs deactivated after 60 days - workaround?

Hi

I have a job scheduled to run every night to update a docker image for dependency check with the latest up to date database - GitHub - dependency-check/DependencyCheck_Builder: It builds a dependency check image with the updated database every night

However after 60 days it gets disabled… which is quite bad. Is there any way to avoid having the workflow disabled after 60 days?

Thanks

1 Like

Not that I’m advocating it (and this may violate terms, so check before implementing), but my understanding is that they’re deactivated if the repository is inactive.

If one of your workflows:

  1. committed something – saying that it had checked the dependencies of everything and was happy
  2. and then pushed that to the repository (e.g. to the gh-pages branch)

… then it’s possible that the repository would no longer qualify as inactive.

I think if I were you, I’d have the page that it publishes to gh-pages list the versions of all the software it’s using. That’d make the page useful.

1 Like

Yeah for sure the empty commit will make it work but it’s a bit dirty. Im sure there’s something better to do

Oh, I’m suggesting a non-empty commit – make a commit reporting what you’re caching. That makes it useful for everyone. It’s slightly less dirty than an empty commit :slight_smile:.