You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the process for creating a build pipeline through the 'build' button in the KRCI Portal uses hardcoded timeout values for the PipelineRun. This task aims to enhance this process by implementing logic to dynamically retrieve and apply the timeout value from the kind: TriggerTemplate, specifically from the tt-build.yaml file within the edp-tekton repository.
Acceptance Criteria
The logic for creating a PipelineRun through the KRCI Portal's 'build' button dynamically retrieves the timeout value from the kind: TriggerTemplate (tt-build.yaml).
Hardcoded timeout values in the KRCI Portal (createBuildPipelineRunInstance function) are replaced with dynamically sourced values from the TriggerTemplate.
The implementation supports seamless updates to the timeout value within the TriggerTemplate, automatically reflecting in the build pipeline creation process without additional code modifications.
Comprehensive testing is performed to ensure that the dynamic timeout retrieval and application function correctly across various scenarios.
Documentation is updated to reflect the new logic for dynamic timeout handling in the build pipeline creation process.
The text was updated successfully, but these errors were encountered:
Currently, the process for creating a build pipeline through the 'build' button in the KRCI Portal uses hardcoded timeout values for the
PipelineRun
. This task aims to enhance this process by implementing logic to dynamically retrieve and apply the timeout value from thekind: TriggerTemplate
, specifically from thett-build.yaml
file within theedp-tekton
repository.Acceptance Criteria
The logic for creating a
PipelineRun
through the KRCI Portal's 'build' button dynamically retrieves the timeout value from thekind: TriggerTemplate
(tt-build.yaml
).Hardcoded timeout values in the KRCI Portal (
createBuildPipelineRunInstance
function) are replaced with dynamically sourced values from theTriggerTemplate
.The implementation supports seamless updates to the timeout value within the
TriggerTemplate
, automatically reflecting in the build pipeline creation process without additional code modifications.Comprehensive testing is performed to ensure that the dynamic timeout retrieval and application function correctly across various scenarios.
Documentation is updated to reflect the new logic for dynamic timeout handling in the build pipeline creation process.
The text was updated successfully, but these errors were encountered: