Skip to content

Update how timeout is defined in yml files. #1078

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

Merged
1 commit merged into from
Jun 25, 2019

Conversation

vatsan-madhavan
Copy link
Member

Update how timeout is defined in yml files.

We just noticed that our 120 min timeout is not working correctly, causing backlogs in build and preventing work from progressing. Trying to define this a different way.

@ghost ghost requested review from rladuca, ryalanms and stevenbrix June 24, 2019 23:31
@ghost ghost added the PR metadata: Label to tag PRs, to facilitate with triage label Jun 24, 2019
@vatsan-madhavan
Copy link
Member Author

Related: #1077

@vatsan-madhavan vatsan-madhavan self-assigned this Jun 24, 2019
@vatsan-madhavan vatsan-madhavan added the auto_merge bot-command label Jun 24, 2019
@ghost
Copy link

ghost commented Jun 24, 2019

Hello @vatsan-madhavan!

Because this pull request has the auto_merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

Do note that I've been instructed to only help merge pull requests of this repository that have been opened for at least 30 minutes, a condition that will be fulfilled in about 5 minutes. No worries though, I will be back when the time is right! 😉

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@vatsan-madhavan
Copy link
Member Author

/azp help

@azure-pipelines
Copy link

Supported commands
  • help:
    • Get descriptions, examples and documentation about supported commands
    • Example: help "command_name"
  • list:
    • List all pipelines for this repository using a comment.
    • Example: "list"
  • run:
    • Run all pipelines or a specific pipeline for this repository using a comment. Use this command by itself to trigger all related pipelines, or specify a pipeline to run.
    • Example: "run" or "run pipeline_name"
  • where:
    • Report back the Azure DevOps orgs that are related to this repository and org
    • Example: "where"

See additional documentation.

@vatsan-madhavan
Copy link
Member Author

/azp list

@azure-pipelines
Copy link

CI/CD Pipelines for this repository:

@vatsan-madhavan
Copy link
Member Author

/azp where

@azure-pipelines
Copy link

Azure DevOps orgs getting events for this repository:

@vatsan-madhavan
Copy link
Member Author

/azp help run

@azure-pipelines
Copy link

  • run:
    • Run all pipelines or a specific pipeline for this repository using a comment. Use this command by itself to trigger all related pipelines, or specify a pipeline to run.
    • Example: "run" or "run pipeline_name"

See additional documentation.

@ghost ghost merged commit fb6c477 into master Jun 25, 2019
@ghost ghost deleted the dev/vatsan/pipeline-timeout-120 branch June 25, 2019 01:36
@ghost ghost locked as resolved and limited conversation to collaborators Apr 16, 2022
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto_merge bot-command PR metadata: Label to tag PRs, to facilitate with triage
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants