You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, if using a SaaS tool for static-code analysis, it's unlikely to be ok for an outage on that SaaS product to break your pipelines such that you can't update your product.
Clearly there are options here, including:
Simple & documented process to disable certain pipeline steps so that the SaaS outage in question can be worked around
Running a self-hosted equivalent of that SaaS product as a backup
... and what makes sense will clearly depend on the impact of any outage, the criticality of that SaaS tool, the SLA of the service, etc, etc.
The text was updated successfully, but these errors were encountered:
For example, if using a SaaS tool for static-code analysis, it's unlikely to be ok for an outage on that SaaS product to break your pipelines such that you can't update your product.
Clearly there are options here, including:
... and what makes sense will clearly depend on the impact of any outage, the criticality of that SaaS tool, the SLA of the service, etc, etc.
The text was updated successfully, but these errors were encountered: