[ https://ovirt-jira.atlassian.net/browse/OVIRT-2471?page=com.atlassian.jira.p... ] Daniel Belenky updated OVIRT-2471: ---------------------------------- Description: As new projects have new timeout requirements, we should allow them to configure the timeout from stdci.yaml. The configuration should probably go to runtime_requirements and configurable under the 'timeout' key. The configuration should be from the following form: {code:java} [0-9]+(\s+)?(h|s|m) {code} and where h, s and m can have multiple forms such as hour, hours, minute, etc... Example: {code:java} --- runtime requirements: timeout: 2h {code} was: As new projects have new timeout requirements, we should allow them to configure the timeout from stdci.yaml. The configuration should probably go to runtime_requirements and configurable under the 'timeout' key. The configuration should be from the following form: [0-9]+(\s+)?(h|s|m) and where h, s and m can have multiple forms such as hour, hours, minute, etc... Example: {code:java} --- runtime requirements: timeout: 2h {code}

Make timeout configurable from STDCI DSL ----------------------------------------

Key: OVIRT-2471 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2471 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: infra

As new projects have new timeout requirements, we should allow them to configure the timeout from stdci.yaml. The configuration should probably go to runtime_requirements and configurable under the 'timeout' key. The configuration should be from the following form: {code:java} [0-9]+(\s+)?(h|s|m) {code} and where h, s and m can have multiple forms such as hour, hours, minute, etc... Example: {code:java} --- runtime requirements: timeout: 2h {code}

-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)