-
Bug
-
Resolution: Fixed
-
Major
-
None
Currently, inside the build container steps, shell executions cannot access build-level parameters, such as SCM properties or Build information like BUILD_NUMBER.
A workaround to allow this is to redeclare it:
environment{
BUILD_NUMBER = "${BUILD_NUMBER}
}
But this should be fixed to allow smoother use of the Kubernetes Plugin
- is related to
-
JENKINS-49110 withSonarQubeEnv in Jenkins pipeline not setting SonarQube env whe using Kubernetes
- Resolved