Manual Renovate API trigger skipped due to schedule constraints

[ThibautMarechal]

How are you running Renovate?

Self-hosted Renovate

Which platform you running Renovate on?

Other (please specify)

Which version of Renovate are you using?

13.1.0

Please tell us more about your question or problem

Hi,
I'm running a self-hosted instance of renovate-ce on my repositories in bitbucket-server.
My goal is to have Renovate:

• run automatically on weekends (via schedule), and
• still allow a manual trigger at any time using the APi: [POST] /api/v1/repos/{org}/{repo}/-/jobs/run.

I use this set of configuration define at the repository level:

At the repository level, I use this config:

{
  "extends": ["https://renovate.evs.tv/api/config/via-map-ui"]
}

which ultimately extends:

{
  "extends": ["schedule:weekends"],
  "updateNotScheduled": true,
  "prCreation": "immediate",
  "prConcurrentLimit": 0,
  "prHourlyLimit": 0
}

The scheduled runs work as expected.

However, when triggering Renovate manually via the API outside the scheduled window, branch creation is skipped with the log message: Skipping branch creation as not within schedule (comming from this)

Based on my research, is this use case (scheduled automation + schedule-agnostic manual runs) currently impossible with existing configuration options?

If so, would it make sense to introduce a configuration option allowing manual triggers to ignore schedules ?
I’d be happy to help work on this if that's a valid use case 😁

Logs (if relevant)

No response

[RahulGautamSingh]

Such a feature is not in the timeline currently. Is it not possible to use dependency dashboard in your case, to trigger specific/all awaiting schedule PRs?

[ThibautMarechal]

Sadly Bitbucket server doesn't support issues wich is what renovate use to create a Dependency dashboard. (If I'm not mistaken)

I found a messy workarround. Set the MEND_RNV_CRON_JOB_SCHEDULER_ALL environment variables to only run on weekend, while each repo allow it at anytime.
The problem is that there are many team in my company, and each of them may want a different schedule ber repository. It would be great to avoid having to deploy a full Renovate instance by team/repo 😅

[RahulGautamSingh]

Either you should run daily (a global instance) that way the updates will fall on schedule or should not have schedules if you want to create updates each time the bot is run.

Is this not the right way, for your case?

[nabeelsaabna]

@RahulGautamSingh does checkedbranches (similar to the dependency dashboard) bypass the schedule ?