Some RQM Build-In Execution Variables not passed to Command Line Adapter
Hi community,
We would like to trigger automated tests once a build has been run successfully. Therefore we have enabled the RQM Build Provider and scheduled a job for a successful build. The Build Result itself is a binary which should be flashed into some embedded hardware and it is attached to the RTC Build Result artefact after it has been built successfully. Once a build has been run successfully a test shall be executed on a remote machine using the RQM Command Line Adapter which flashes the binary into the embedded hardware. Therefore the executed script shall fetch the created binary from the RTC Build Result artefact. Our idea was to use the RQM Execution variables to find the correct build result in RTC. We have already created a small Java program which is able to fetch the binary from the result. One argument for the program should be the build definition name. Therefore we enabled the built-in vars for the RQM test script but the
RQM_BUILDDEFINITION_NAME
isn't
passed to the adapter even though that is described in the IBM help. For the time being only
the are passed to the adapter.
What do we need to do to pass the
RQM_BUILDDEFINITION_NAME
to variable to the adapter? We are using CLM5.0.2.
Best regards Matthias |
One answer
Hi Matthias,
Is the Build Record associated to any build definition? Comments
Matthias Buettgen
commented Apr 26 '16, 12:19 p.m.
Hi Reshma,
I apologize for my late response because I was involved in some other stuff in the meantime.
Anyway, we verified the the issue and recognized the following behavior.
If a an automated test is executed manually in the UI and the build record has been assigned manually all build related execution variables are passed to the adapter.
If the automated test is executed by an execution schedule (the build is recognized by RQM based on the build provider) then the RQM_BUILDDEFINITION_NAME is not passed to the adapter. The Build label (BUILD_RECORD_NAME) is passed using this setup.
We need the Build Definition Name because we fetch the build result from the RTC build record in order to test it.
Br
Matthias
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.