How-To: Push Jenkins results to tTriage

Besides that the app can perform to PULL automatically every certain period of time, you can perform a PUSH from Jenkins using two methods:

1. You can use the Jenkins plugin especially tailor-made for tTriage Follow the configuration details How-To: Jenkins Plugin Configuration about how to use it
2. Or, you can use the tests to push the results: Bitbucket or detailed info in: How-To: Create a push from Jenkins using a test

The goal of this test is to be used as lastest step in a pipeline in order to push test result and validate if all suites in a container are triaged.

MANDATORY PARAMETERS:

• Server: The server parameters (port by default is 8080) and the path (if apply, by default is /)
  • qe.server.url
  • qe.server.port
  • qe.server.path
• Authorization: You need to ask for the ClientId and SecretId of your connector. How-To: Pull / Push configuration
  • qe.server.clientId
  • qe.server.secretId
• Target: The target are the container, executor or product to validate.
  • If you need to push test result you need to run:
    • qe.test.views i.e: Deploy,Test,ETC (you can set multiple view, coma separated. The view by default is All)
    • test=AllPushTestSuite
  • If you need to validate the triage result
    • qe.test.containerid
    • qe.test.executorid
    • qe.test.productid
    • test=com.clarolab.pipeline.test.[PipelineContainerAPITest | PipelineExecutorAPITest | PipelineProductAPITest]
• Jenkins CI: The server where tests are running.
  • qe.jenkins.url
  • qe.jenkins.username
  • qe.jenkins.token

OPTIONAL PARAMETERS:

• qe.test.timeout The amount of milliseconds to wait if the triage is not done. By default is 30secs
• qe.test.repeat The amount of retries. By default are 5 times

Note: In both cases you can push the result and validate if the triage is completely done and you product is ready for deploy

Copyright (c) 2019, Clarolab. All rights reserved.