We need to have a way to exclude some deployments from being idled. This is useful when we need to troubleshoot a jenkins instance running in production where we cant easily reproduce the problem in staging.
For instance, if the idler sees a specific annotation on the DC, skip idling it and dont scale it down.
One more reason to do this is that development of idler requires connecting to prod-preview and restricting local idler to a single user using the JC_FIXED_UUID env var. Since an idler is already running in prod-preview it often handles the openshift event causing more than the actual dc events to be generated.
Thus the proposal is to allow idler to ignore certain users on prod-preview perhaps by using the feature-toggle-service (see related discussion)
We need to have a way to exclude some deployments from being idled. This is useful when we need to troubleshoot a jenkins instance running in production where we cant easily reproduce the problem in staging.
For instance, if the idler sees a specific annotation on the DC, skip idling it and dont scale it down.
One more reason to do this is that development of idler requires connecting to prod-preview and restricting local idler to a single user using the
JC_FIXED_UUID
env var. Since an idler is already running in prod-preview it often handles the openshift event causing more than the actual dc events to be generated.Thus the proposal is to allow idler to ignore certain users on prod-preview perhaps by using the feature-toggle-service (see related discussion)
Also related: https://github.com/fabric8-services/fabric8-jenkins-idler/issues/83