3 results found

1. Fix strange behaviour with skipping tenants in runbook that have latest snapshot

   When running a Runbook and only one tenant is available the tenant is automatically selected and a checkbox is shown saying "Skip tenants where Snapshot Y7484HM is the current version deployed to ExampleEnvironment". It's checked by default.

   However when deselecting the tenant and selecting it again this checkbox doesn't appear. It seems like it's connected to the automatic selection of the tenant which is strange.

   Additionally it would make sense to have this checkbox disabled by default (or configurable) because Runbooks are for routine tasks (as the website says) where we WANT to run the Runbook multiple times (although there are no changes in the Runbook). Right now our people use the Runbook multiple times per day and need to disable this checkbox every time.

   When running a Runbook and only one tenant is available the tenant is automatically selected and a checkbox is shown saying "Skip tenants where Snapshot Y7484HM is the current version deployed to ExampleEnvironment". It's checked by default.

   However when deselecting the tenant and selecting it again this checkbox doesn't appear. It seems like it's connected to the automatic selection of the tenant which is strange.

   Additionally it would make sense to have this checkbox disabled by default (or configurable) because Runbooks are for routine tasks (as the website says) where we WANT to run the Runbook multiple times (although there… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Runbooks  ·  Delete…  ·  Admin →

2. Alternate Cron Expression while Trigger is Failing

   Runbooks can be run via a scheduled Trigger. This is a very useful feature. But it would be nice if the Trigger had a feature to help when the triggered RunBook Run fails.

   I would like to propose that another field be added to the Trigger creation page. It could be called "Error Cron Expression".

   When the RunBook Run by the Trigger fails, the Trigger would switch its Cron Expression to use the "Error Cron Expression". Once the Trigger starts succeeding, then it would switch back to the normal Cron Expression.

   The idea is that, when a Trigger is failing, it can be useful to run it at a different frequency. Sometimes you want to back off to not overwhelm a system with failed calls. If the Trigger is a "once a day" kind of trigger, you may want to run the Trigger every hour till is starts succeeding (since a failed "once a day" trigger means it will not try again till the next day).

   Either use case would be fulfilled by an "Error Cron Expression" feature.

   Runbooks can be run via a scheduled Trigger. This is a very useful feature. But it would be nice if the Trigger had a feature to help when the triggered RunBook Run fails.

   I would like to propose that another field be added to the Trigger creation page. It could be called "Error Cron Expression".

   When the RunBook Run by the Trigger fails, the Trigger would switch its Cron Expression to use the "Error Cron Expression". Once the Trigger starts succeeding, then it would switch back to the normal Cron Expression.

   The idea is that, when a Trigger is failing,… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Runbooks  ·  Edit…  ·  Delete…  ·  Admin →

3. Push new certificates without having to do a deployment

   It is great that you can now centrally manage your certificates from within Octopus Deploy. I am using this for managing the bound https cert in IIS sites and it works great.

   One drawback we've found is that if a certificate is replaced, you have to re-deploy the project again to apply the new certificate. Our deployment process is quite lengthy and involved, turning services on and off causing at around 10-15mins of downtime of our system.

   Ideally, we would be able to push a new certificates to any tentacle that has the old certificate, without triggering a deployment of all the services. Bonus points if this also updated the new certificate thumbprint in IIS as well.

   It might be expected that you must re-deploy to install the new certificate, I just personally find that it causes significantly more down-time that it could be, if only the certificate was pushed.

   It is great that you can now centrally manage your certificates from within Octopus Deploy. I am using this for managing the bound https cert in IIS sites and it works great.

   One drawback we've found is that if a certificate is replaced, you have to re-deploy the project again to apply the new certificate. Our deployment process is quite lengthy and involved, turning services on and off causing at around 10-15mins of downtime of our system.

   Ideally, we would be able to push a new certificates to any tentacle that has the old certificate, without triggering a deployment of… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Runbooks  ·  Delete…  ·  Admin →