Condition Execution Evaluations Before Pipeline Initialization
long-term
Z
Zinc Peacock
Hello,
I have found an issue regarding to pipeline evaluation phase before pipeline step 'initialize'.
This pipeline execution failed after 3 minutes (a bit long)
This step is normally executed when the codebase branch name is prefixed by 'release' or by 'bugfix', but the pipeline execution had been done from 'develop' codebase branch name (and the develop secret had been declared yet at project level).
According to input set used for pipeline execution , pipeline's conditions executions can maybe be evaluated to determine a stage steps path (and so on to be able to determine also maximum CPU and memory values limits), and so on avoid to request a secret for a step that won't be executed.
May it be possible to create a feature request or a fix for this issue ? Thank you
Best regards,
Frederic Collette
Log In
Canny AI
Merged in a post:
Pipeline Pod Resources Calculation At Init Phase
C
Cinnabar Flamingo
Two steps with different execution conditions can not be executed at the same time because of some input toggle value. Yet the pipeline stage pod created in our Kubernetes cluster included the two steps and summed the cpu & memory limit resources requesting a hug amount of CPUs and memory.
It seems that the Harness CI engine can not evaluate the step execution conditions and so on determine the steps execution path during initialization phase, especially if the execution conditions. include variables values by input set choices.
C
Cinnabar Flamingo
Harness support ticket in relation : https://support.harness.io/hc/en-us/requests/70849
N
Nofar Bluestein
long-term
N
Nofar Bluestein
under review
Pranav Rastogi
pending feedback