Forum Discussion

Christian_N_DK's avatar
Christian_N_DK
Contributor
4 years ago

Jenkins Jobgeneration with DSL for Testexecute

Hi,

 

I am having issues with generating jobs on Jenkins with the latest plugin updates for the Testcomplete plugin where credentials are a part of the job configuration. When generating the hash value for userPassword changes. And this brings me to the question, if the generated Hash, does have a timeout for validity? Or the generated jobs can "last for ever" with the generated hash value?

I am using Job DSL on Jenkins for generating the test jobs, via groovy code.

configure {
  it / builders << 'com.smartbear.jenkins.plugins.testcomplete.TcTestBuilder' {
    suite(suiteName)
    launchType('lcRoutine')
    project(projectName)
    unit(unitName)
    routine(rName)
    test('')
    executorType('TE')
    executorVersion('14.0')
    actionOnWarnings('MAKE_UNSTABLE')
    actionOnErrors('MAKE_FAILED')
    useTimeout('false')
    timeout('')
    useTCService('false')
    userName()
    userPassword('{ASecretPassword}')
    credentialsId('')
    useActiveSession('true')
    generateMHT('true')
    publishJUnitReports('true')
    }
}

  • vinniew's avatar
    vinniew
    Staff
    4 years ago

    Hi Christian_N_DK 

     

    Hope you are well. 

     

    I'm haven't worked with Job DSL pulg-in before.

     

    However I do have the latest TC plugin

     

    I use the deafult Build step which is Test Complete Test,

     

    Its executed correctly with TC and TE

     

    I am sure the above will work for you however i am just not 100% certain via DSL. 

     

    Will see if anyone else can suggest a WA for this

     

    KR 

    Vincent 

    • Christian_N_DK's avatar
      Christian_N_DK
      Contributor
      4 years ago

      Thanks for the reply.
      Our production code, look a little different, but does not work with newest credentials changes. But the differences are minimal. We generate almost all of our tests. Saves us a lot of maintenance of jobs.