Integrating ALM For Bamboo

Issue #5 new
Mohamed Ashraf created an issue

After creating the task in Bamboo server, we tried to execute the plan. The plan is getting executed successfully, but we are getting error that "Erro=13" not able to execute ALMTSRunner.exe.

Please let me know how to resolved this issue.

Comments (16)

  1. Nadim Hussein

    I was able to resolve this issue by selecting Clean working directory after each build from Bamboo Job Miscellaneous tab

    bamboo.png

    Now the job run with no errors but it didn't access ALM and launch the UFT scripts ...basically it is not doing anything ...here is the log

    30-Oct-2018 14:25:17 Build ETRM - Felix Regression - Default Job #11 (ETRM-FR-JOB1-11) started building on agent Default Agent 30-Oct-2018 14:25:17
    30-Oct-2018 14:25:17 Build working directory is /home/miami/bamboo/xml-data/build-dir/ETRM-FR-JOB1 30-Oct-2018 14:25:17 Executing build ETRM - Felix Regression - Default Job #11 (ETRM-FR-JOB1-11) 30-Oct-2018 14:25:17 Running pre-build action: VCS Version Collector 30-Oct-2018 14:25:17 Starting task 'Execute UFT scripts for Felix' of type 'com.mdb.plugins.almtaskforbamboo:ALMTask' 30-Oct-2018 14:25:17 Extracting ALM Test Set Runner:/home/miami/bamboo/xml-data/build-dir/ETRM-FR-JOB1 30-Oct-2018 14:25:17 Reading folder.../home/miami/bamboo/xml-data/build-dir 30-Oct-2018 14:25:17 Preparing secure configuration for ALM Test Set Runner 30-Oct-2018 14:25:17 ********** 30-Oct-2018 14:25:17 Starting ALM Test Set Runner 30-Oct-2018 14:25:17 Process returned code 2 30-Oct-2018 14:25:17 ********* 30-Oct-2018 14:25:17 ALM Test Set Runner finished 30-Oct-2018 14:25:17 Creating test results in Bamboo for ALM test execution... 30-Oct-2018 14:25:17 Parsing test results under /home/miami/bamboo/xml-data/build-dir/ETRM-FR-JOB1... 30-Oct-2018 14:25:17 Test results created in Bamboo for ALM test execution. 30-Oct-2018 14:25:17 *********** 30-Oct-2018 14:25:17 Finished task 'Execute UFT scripts for Felix' with result: Success 30-Oct-2018 14:25:17 Running post build plugin 'NCover Results Collector' 30-Oct-2018 14:25:17 Running post build plugin 'Artifact Copier' 30-Oct-2018 14:25:17 Running post build plugin 'npm Cache Cleanup' 30-Oct-2018 14:25:17 Running post build plugin 'Clover Results Collector' 30-Oct-2018 14:25:17 Running post build plugin 'Docker Container Cleanup' 30-Oct-2018 14:25:17 Successfully removed working directory at '/home/miami/bamboo/xml-data/build-dir/ETRM-FR-JOB1' 30-Oct-2018 14:25:17 Finalising the build... 30-Oct-2018 14:25:17 Stopping timer. 30-Oct-2018 14:25:17 Build ETRM-FR-JOB1-11 completed. 30-Oct-2018 14:25:17 Running on server: post build plugin 'NCover Results Collector' 30-Oct-2018 14:25:17 Running on server: post build plugin 'Build Hanging Detection Configuration' 30-Oct-2018 14:25:17 Running on server: post build plugin 'ALM Task JIRA updater' 30-Oct-2018 14:25:17 Running on server: post build plugin 'Clover Delta Calculator' 30-Oct-2018 14:25:17 Running on server: post build plugin 'Maven Dependencies Postprocessor' 30-Oct-2018 14:25:17 All post build plugins have finished 30-Oct-2018 14:25:17 Generating build results summary... 30-Oct-2018 14:25:17 Saving build results to disk... 30-Oct-2018 14:25:17 Logging substituted variables... 30-Oct-2018 14:25:17 Indexing build results... 30-Oct-2018 14:25:17 Finished building ETRM-FR-JOB1-11.

    
    
  2. Vikas Borse repo owner

    Does the UFT scripts run from ALM testlab? Please also check if UFT can be run remotely. The plugin runs the ALM tests . The test must be runnable from ALM.

    Please provide more info so that we can try to help.

    Thanks Vikas Borse

  3. Nadim Hussein

    I have UFT14.02 and ALM12.52 , I run test set from ALM and it launch UFT and execute the scripts in the testset with no issues. We are running Bamboo on Linux server and I did the required configuration for ALMTask for Bamboo add-on as in the document.

    I thought cleaning the work directory after each build will fix the issue.

    now I am getting the original error again ...here is Bamboo job log:

    30-Oct-2018 16:02:10 ********** 30-Oct-2018 16:02:10 Starting ALM Test Set Runner 30-Oct-2018 16:02:10 Cannot run program "/home/miami/bamboo/xml-data/build-dir/ETRM-FR-JOB1/ALMTSRunner.exe" (in directory "/home/miami/bamboo/xml-data/build-dir/ETRM-FR-JOB1"): error=13, Permission denied 30-Oct-2018 16:02:10 Process returned code -1 30-Oct-2018 16:02:10 ************

  4. Nadim Hussein

    "Can you please check if the user by which the agent is started has executable permission?"

    I logged in to Bamboo as Uma and executing the scripts from ALM as nhussein (admin user for ALM).

    ALMTaskforBamboo is configured to connect to ALM as nhussein

    please see below screenshots for both Bamboo and ALM configurations

    Bamboo Setup1.JPG Bamboo Setup2.JPG ALM Login.JPG ALM TestSet.JPG

  5. Nadim Hussein

    Another thing I noticed ...when I run the job in Bamboo it completes in less than 1 sec ... this doesn't make sense as connecting to ALM and trying to bring up the UFT scripts will take more than 30 sec.

    Run Results.JPG

  6. Vikas Borse repo owner

    Hi Nadim, Its not a problem with the users you use to login the webclient. Can you please check with your Bamboo administrator what user has started the Bamboo agent ( In your case “Default agent” as per the screnshot)

    The user which has started Bamboo user must have executable permissions.

    The job will finish in few seconds as the TestRunner is not started execution due to permission error.

    Thanks Vikas Borse

  7. Nadim Hussein

    I checked with Bamboo admin and the bamboo user used for execution (Default agent) already have executable permissions in Bamboo.

    However that same user (Default agent) doesn't exist in ALM and I don't I think I can add him to ALM since he doesn't exist in our AD and ALM have LDAP integration.

    any other suggestions?

    Thanks

  8. Nadim Hussein

    @vika_bhardwaj

    Our Bamboo is running on Linux box , the problem the exe file (ALMTSRunner.exe) won't execute on linux, those are windows executables

    do we have to have Bamboo running on Windows box in order to use this integration with ALM?

    Thanks

  9. Nadim Hussein

    @vikasborse

    1- I tired with Bamboo running on Windows and the execution worked fine. so I guess it doesn't work on Bamboo which runs on Linux as it won't be able to execute the ALMTSRunner.exe (not sure if you can solve this as most companies run Bamboo on Linux).

    2- As I mentioned the ALM execution part is working but the JIRA integration is not ... getting below error... any idea how to fix it ? I noticed in the JIRA integration the plugin doesn't care about the issue type or the JIRA project in which the test is saved under ... it search by test name but in reality the test name in ALM might not match the test name in JIRA so mapping through JIRA ID or ALM ID custom field in JIRA is better.... Did the JIRA part work for you?

    08-Nov-2018 17:04:00 Connected to JIRA 08-Nov-2018 17:04:00 Bamboo URL is: http://172.27.121.49:8085 08-Nov-2018 17:04:00 Failed to execute plugin 'ALM Task JIRA updater' with error: com.atlassian.bamboo.jira.jiraissues.JiraIssueUtils.<init>(Lcom/atlassian/bamboo/applinks/JiraApplinksService;Lcom/atlassian/bamboo/resultsummary/ResultsSummaryManager;Lcom/atlassian/event/api/EventPublisher;Lcom/atlassian/bamboo/configuration/AdministrationConfigurationAccessor;Lcom/atlassian/bamboo/deployments/versions/service/DeploymentVersionLinkedJiraIssuesService;)V 08-Nov-2018 17:04:00 Running on server: post build plugin 'Clover Delta Calculator' 08-Nov-2018 17:04:00 Running on server: post build plugin 'Maven Dependencies Postprocessor' 08-Nov-2018 17:04:00 All post build plugins have finished

  10. Vikas Borse repo owner

    Hi Nadim, You are right. The default agents on Bamboo server installed on any non windows platform will not run ALM tests. But you can always install a Remote Agent on Windows machine. In this case it will not matter on which platform Bamboo server is installed as tests will be running on Remote Agent which is Windows machine.

    For Jira related issues, it does gives issues on some Bamboo installations as the jira related classes does not get found by the plugin on server.Can you let us know Bamboo version?

    Thanks Vikas Borse

  11. Nadim Hussein

    Hi Vikas,

    Atlassian Bamboo version 6.2.3 build 60210 - 20 Nov 17 JIRA server JIRA v7.3.8

    Which Bamboo version should I use to get it work with JIRA?

    Do I have to have UFT script name in ALM matching the script name in JIRA in order to get the execution status updated in JIRA ( by the way I am using Zephyr for hosting my manual tests)

    Thanks

  12. Log in to comment