Problems with build definition when used with Jenkins workflow/pipeline
Hi
There are already several build definitions with corresponding Jenkins (free-style) jobs working without problems. In future we think about using a workflow/pipeline in Jenkins. Therefore I tried to implement a first test pipeline. This was not successful due to the following problem...
I created a new pipeline in Jenkins and a build definition in RTC (using the existing/working build engine).
When saving the build definition in eclipse a error message is displayed (It seems that the built definition is saved nevertheless):
When trying to start a build with the pipeline job from the eclipse client the execution fails and produces the following log .
Any ideas how to solve this error?
Sadly pictures I inserted are not shown :(
There are already several build definitions with corresponding Jenkins (free-style) jobs working without problems. In future we think about using a workflow/pipeline in Jenkins. Therefore I tried to implement a first test pipeline. This was not successful due to the following problem...
I created a new pipeline in Jenkins and a build definition in RTC (using the existing/working build engine).
When saving the build definition in eclipse a error message is displayed (It seems that the built definition is saved nevertheless):
This Error is only shown when the pipeline job is selected in the build defeinition. Wehen a "free-style" jenkins job is selected no error occurs.Error parameterizing Jenkins Job -- Error updating Hudson/Jenkins Job: Unable to read configuration of job
When trying to start a build with the pipeline job from the eclipse client the execution fails and produces the following log .
When the pipeline is started in Jenkins the pipeline job is finishing without problems.Error starting Hudson/Jenkins build for job "Pipeline_Test": com.ibm.team.repository.common.TeamRepositoryException: Error parameterizing the Hudson/Jenkins Job![]()
Any ideas how to solve this error?
Sadly pictures I inserted are not shown :(
Accepted answer
Sounds like a permission problem from the Jenkins side. It is trying to read the Jenkins XML file to determine information on the job as well as attempting to make the job a parameterized one. Since it has problem reading/writing that data to Jenkins I would guess that the jobs are protected from the RTC user attempting to read the Jenkins server.
~Spencer
~Spencer
Comments
Lakshmi Narasimhan T V
JAZZ DEVELOPER Mar 18 '16, 12:44 a.m.