-
Improvement
-
Resolution: Unresolved
-
Major
-
Jenkins 2.121.3
Windows Server 2008 R2
PTC Integrity Plugin 2.2
I am facing an issue with PTC integrity plugin used via Pipeline script.
In principle it is working fine. But when trying to execute the job on a different master the script fails, as the checkout command for PTC includes the hash for the server configuration as well as Configuration name: configurationName, serverConfig:
e.g:
checkout([ $class: 'IntegritySCM',
checkpointBeforeBuild: false,
configPath: '/any/any/project.pj',
configurationName: 'ed1d9d74-cb0b-4446-ba16-0b5520e061cf',
restoreTimestamp: false,
serverConfig: '6038a84b-7e07-4c2f-b2d6-fe95e4039f3c',
skipAuthorInfo: false
])
If the plugin could be improved to also accept the name of the configuration instead or additional to the hash, this would increase interoperability of the pipeline scripts a lot. And also the configurationName: could be omitted I think...
e.g:
checkout([ $class: 'IntegritySCM',
checkpointBeforeBuild: false,
configPath: '/any/any/project.pj',
restoreTimestamp: false,
serverConfig: 'user@mks.location.domain.com:7001',
skipAuthorInfo: false
])
In the drop down menu of the snippet generator, also the name is in clear text and not represented as hash 
[JENKINS-53559] PTC integrity plugin used via Pipeline script can not run on other Master due to maschine dependent hash
Gregor Heilmann
created issue -
Gregor Heilmann
made changes -
| Description |
Original:
I am facing an issue with PTC integrity plugin used via Pipeline script. In principle it is working fine. But when trying to execute the job on a different master the script fails, as the checkout command for PTC includes the hash for the server configuration as well as Configuration name: _configurationName_, _serverConfig_: e.g: {{checkout}}{{([ $class: 'IntegritySCM', }} {{ checkpointBeforeBuild: false,}} {{ configPath: '/any/any/project.pj',}} {{ configurationName: 'ed1d9d74-cb0b-4446-ba16-0b5520e061cf', }} {{ restoreTimestamp: false, }} {{ serverConfig: '6038a84b-7e07-4c2f-b2d6-fe95e4039f3c', }} {{ skipAuthorInfo: false}} {{ ])}} If the plugin could be improved to also accept the name of the configuration instead or additional to the hash, this would increase interoperability of the pipeline scripts a lot. And also the {{configurationName:}} could be ommited I think... e.g: {{checkout}}{{([ $class: 'IntegritySCM', }} {{ checkpointBeforeBuild: false,}} {{ configPath: '/any/any/project.pj',}} {{restoreTimestamp: false, }} {{ serverConfig: 'user@mks.location.domain.com:7001', }} {{ skipAuthorInfo: false}} {{ ])}} In the drop down menu of the snippet generator, also the name is in clear text and not represented as hash ;) |
New:
I am facing an issue with PTC integrity plugin used via Pipeline script. In principle it is working fine. But when trying to execute the job on a different master the script fails, as the checkout command for PTC includes the hash for the server configuration as well as Configuration name: _configurationName_, _serverConfig_: e.g: checkout([ $class: 'IntegritySCM', checkpointBeforeBuild: false, configPath: '/any/any/project.pj', configurationName: 'ed1d9d74-cb0b-4446-ba16-0b5520e061cf', restoreTimestamp: false, serverConfig: '6038a84b-7e07-4c2f-b2d6-fe95e4039f3c', skipAuthorInfo: false ]) If the plugin could be improved to also accept the name of the configuration instead or additional to the hash, this would increase interoperability of the pipeline scripts a lot. And also the {{configurationName:}} could be omitted I think... e.g: checkout([ $class: 'IntegritySCM', checkpointBeforeBuild: false, configPath: '/any/any/project.pj', restoreTimestamp: false, serverConfig: 'user@mks.location.domain.com:7001', skipAuthorInfo: false ]) In the drop down menu of the snippet generator, also the name is in clear text and not represented as hash ;) |