Replies: 4 comments
-
|
Would also like the ability to change the default 30 day timeout, or ideally have the jobs not fail when 30 days has passed. I'm encountering a situation where all commits in a report are deployed to a staging environment, and then approval is required to deploy to the production environment. However, not all commits are promoted to production, which means the production deployment job fails after 30 days and an error email alert is triggered. |
Beta Was this translation helpful? Give feedback.
-
|
Anyone figure this one out? Experiencing the same thing. |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
|
Not possible |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
So basically I'm using environment deployment review approvals for deployment to production environment. I have configured the pipeline so that only one deployment to production can be active at one time. I am also using Merge queue with 60 minutes total timeout for the deployment pipeline.
The problem is that if someone does not confirm the deployment then the pipeline will be basically stuck for 30 days docs. Another problem is that while the merge queue timeout does remove the job from the queue the pipeline is still left running and is not cancelled unless manually done so. This blocks the whole pipeline unless someone understands a job somewhere in the past is causing this behavior.
So my question is that is there a way to configure that value?
Timeout-minutesfor the job is not working since the job is not basically running at all before it is confirmed.Any help appreciated, please.
Beta Was this translation helpful? Give feedback.
All reactions