I have a jenkins job running on a Openshift pod.

It has 2 stages running in parallel.

1. Running few stages in sequence : mostly mvn commands

1. Running individual stage : helm commands

My pipeline syntax looks something like :

parallel{ 
  stage('Parallel-Process-1'){ 
    stages{ 
      stage('Build Stage'){ 
        //mvn commands
      } 
      stage('Upload docker image'){ 
        //mvn command 
      }
    }
  } 
  stage('Parallel-Process-2'){ 
     //helm commands 
  } 
}

With this, Pipeline is failing in one of the child stages of Parallel-Process-1

In the logs, there is no exception. mvn process logs are disconnected and post-action starts.

Jenkins somehow(incorrectly) seems to get a signal that the build stage has completed and moves to the post activity.

[DEBUG] Writing tracking file /home/jenkins/.m2/repository/org/apache/maven/doxia/doxia-core/1.8/_remote.repositories 
|DEBUG| Single MS CI | Build and UT | Publishing Junit test results Recording test results No test report files were found. Configuration error?

Findings :

1. mvn process did not get terminated (I could see the complete success logs in the pods workspace)

Question : Why Jenkins is not able to monitor the nested parallel process ?

Tools : Jenkins-2.235.2 Declarative Pipeline plugin-1.5.1 Job type : Multibranch (Workflow)