-
Notifications
You must be signed in to change notification settings - Fork 940
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
timeoutinMinutes doesn't work for single job format #48
Comments
I do see a few places in the docs which specify the single-job format implies default options:
|
Thanks @mikeharder I guess my point was more that in the full syntax the |
trigger:
jobs:
It still throwing these errors The agent has received a shutdown signal. This can happen when the agent service is stopped, or a manually started agent is canceled. @ geofflamrock , @mikeharder do you have an idea ? |
azure pipelines have a 60 minutes default per job. Public jobs can run for 3 hours but seems that we need to move to a different format. See: microsoft/azure-pipelines-yaml#48 Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>
It's accepted under the |
thanks again azure devops microsoft/azure-pipelines-yaml#48
Related: microsoft/azure-pipelines-agent#1849 |
I have a question: @geofflamrock says: So: How to change timeout in any possible way? With example, please. I don't care it is for all pipeline or one/two/three jobs. |
In order to consolidate to fewer feedback channels, we've moved suggestions and issue reporting to Developer Community. Sorry for any confusion resulting from this move. |
Moved into Developer Community by me: https://developercommunity.visualstudio.com/content/problem/1007432/timeoutinminutes-doesnt-work-for-single-job-format.html |
@geofflamrock: |
Thanks @Saibamen I've tested and it's now working as documented, I've replied back on the other link. |
I have added timeoutInMinutes for vstest task which is defined in a yaml template, when I pass the parameter for timeoutInMinutes it's not considering the value. Can anyone let me know if timeoutInMinutes is supported for all tasks or if the specific task has to support it so does it works ? |
When using the full syntax for jobs the timeoutInMinutes can be set at the same level as the job. From the docs:
However if I set it when using the single-job syntax the build pipeline fails with error "Unexpected value 'timeoutInMinutes'"
If I move the timeoutInMinutes into the pool element it works ok.
If this is by design then it might be worth updating the docs to indicate this.
Thanks :)
The text was updated successfully, but these errors were encountered: