timeoutinMinutes doesn't work for single job format about azure-pipelines-yaml HOT 11 CLOSED

It's accepted under the pool key but it seems to have no effect. It seems impossible to set a timeout with the standard single-job format.

from azure-pipelines-yaml.

I do see a few places in the docs which specify the single-job format implies default options:

Note: If you have only one job, you can use single-job syntax which omits many of the keywords here.
https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema#job

You can skip the job syntax if you need only a single job with the standard options.
https://docs.microsoft.com/en-us/azure/devops/pipelines/process/phases?tabs=yaml&view=azure-devops

from azure-pipelines-yaml.

Thanks @mikeharder I guess my point was more that in the full syntax the timeoutInMinutes lives at the top level within a job, so I was expecting it to live at the same level in the single job syntax but it doesn't, it lives in pool of which there is no mention in the docs. Other properties in the full syntax work the same way in the single syntax but this property doesn't.

from azure-pipelines-yaml.

trigger:

• master

jobs:

• job: Package
  timeoutInMinutes: 120

  pool:
  name: 'Hosted Ubuntu 1604'

  steps:

  • task: Maven@3
    inputs:
    mavenPomFile: 'pom.xml'
    mavenOptions: '-Xmx3072m'
    javaHomeOption: 'JDKVersion'
    jdkVersionOption: '1.8'
    jdkArchitectureOption: 'x64'
    publishJUnitResults: false
    testResultsFiles: '**/surefire-reports/TEST-*.xml'
    goals: 'install'

It still throwing these errors
Job issues

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 ?

from azure-pipelines-yaml.

Related: microsoft/azure-pipelines-agent#1849

from azure-pipelines-yaml.

I have a question: @geofflamrock says: If I move the timeoutInMinutes into the pool element it works ok.,
@lukeschlather: It's accepted under the pool key but it seems to have no effect. It seems impossible to set a timeout with the standard single-job format.

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.

from azure-pipelines-yaml.

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.

from azure-pipelines-yaml.

Moved into Developer Community by me: https://developercommunity.visualstudio.com/content/problem/1007432/timeoutinminutes-doesnt-work-for-single-job-format.html

from azure-pipelines-yaml.

@geofflamrock:
Please go to this link and answer Microsoft team: https://developercommunity.visualstudio.com/content/problem/1007432/timeoutinminutes-doesnt-work-for-single-job-format.html

from azure-pipelines-yaml.

Thanks @Saibamen I've tested and it's now working as documented, I've replied back on the other link.

from azure-pipelines-yaml.

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 ?

from azure-pipelines-yaml.