Disable Horde scheduling for local iteration

Development Pipeline & Plugins
, ,
1

Small workflow question. We have our stream.json set up with a number of schedules builds When someone fires up a local horde server to test a config change or debug a feature, all the scheduled builds kick off and start fighting over the agent. And then each new CL triggers more. We have been editing the stream.json file locally to disable all the schedules, but it’s a pain, especially if we want to make a change to that streams file. We have to revert some, but not all, changes. it’s all very error prone.

Is there a better way to handle this workflow?

2

Steps to Reproduce

3

Hi Thomas,

The only way to disable scheduled jobs is to use the MongoReadOnlyMode setting (docs). It disables many other things, but CL-based job triggers might still be active. We try to avoid mixing prod and dev envs for this reason. Internally at Epic, individual developers use a local environment (not shared nor connected to our central P4). We have a shared dev env for devs, which uses our main P4 but a separate database. Then of course our central prod environment.