Details
-
Bug
-
Status: Open (View Workflow)
-
Blocker
-
Resolution: Unresolved
-
Windows 2012 Server, groovy dsl scripts are in BitBucket, plugin version 5.5
Description
I set up a new Jenkins server 2.138.1( previous server had Jenkins version 1.7, micro focus plugin 4.0.1) and installed this plugin version 5.5 to integrate our Load Runner scripts with jenkins. We are using dsl scripts to build all Jenkins jobs. Somehow my dsl job doesn't create a build step for Performance Center anymore and I see no specific error messages anywhere. Maybe url for API changed, or this new version of plugin requires me to update code. On my old server this script works just fine. Here is part of groovy script which isn't working anymore. Other steps related to Bitbucket/scm and post build work okay. I'm attaching groovy script also
configure { project ->
project / builders << {'com.hp.application.automation.tools.run.PcBuilder'(plugin: 'hp-application-automation-tools-plugin@5.5') {
//{'com.microfocus.application.automation.tools.settings.OctaneServerSettingsBuilder_-OctaneDescriptorImpl'(plugin: 'hp-application-automation-tools-plugin@5.5') {
'pcModel' {
'pcServerName' 'server'
'almUserName' 'jenkinsACA'
//'almPassword' 'adpaca'
//'almPassword'(class:"com.hp.application.automation.tools.model.SecretContainerImpl")
'almPassword'(class:"com.hp.application.automation.tools.model.SecretContainerImpl")
{ '__secret' 'Dsr90dh/+d6p3F8Mi5p4897Scnz/rUOsGF8TEsxzRxI=' }'almDomain' 'NAS'
'almProject' 'ACA'
'testId' test.testId
'testInstanceId' test.testInstanceId
'timeslotDuration'
'postRunAction' 'COLLATE_AND_ANALYZE'
'vudsMode' 'false'
delegate.description test.description
}
'statusBySLA' 'false'
'runId' 0
}
}
}
Hi Eduard,
Please change:
com.hp.application.automation.tools.run.PcBuilder to com.microfocus.application.automation.tools.run.PcBuilder
and then use (do not use the ID value from the example below, you can get the correct ID for the credentials of your user from jenkins home -> Credentials -> ID of a credential record already defined and that you will need to define):
'credentialsId' 'b0f2c3bd-9fdb-4858-8f25-d23ddfa8f5f8'
instead of two fields:
'almUserName' 'jenkinsACA'
'almPassword'(class:"com.hp.application.automation.tools.model.SecretContainerImpl"){
'secret' 'Dsr90dh/+d6p3F8Mi5p4897Scnz/rUOsGF8TEsxzRxI='
}
Also add the parameter:
'retry' 'NO_RETRY'
regards,
Daniel