Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-9459

Could not instantiate test set scheduler in Hudson Master Slave environment

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Postponed
    • Component/s: qc-plugin
    • Labels:
      None
    • Environment:
      windows server 2008 Master and Slave
      Quality Center 10
    • Similar Issues:

      Description

      Not sure this is a bug, but wasn't sure how else to find out, and or debug. We are able to copy cscript command out of the console, run it at a command prompt and have success, but when we run it via the QC plug-in in a Master and Slave environment, we get "Could not instantiate test set scheduler" every time.

      FYI..If we try to run the command as a a windows batch build step instead of the QC plug-in we get the same error.

      Logged in with user bbonn
      Opened project TEST_AUTOMATION\Test_Automation

      ------------------------------------------------

      TestSet Name ID

      ------------------------------------------------

      BAT_Test 204

      ------------------------------------------------
      Could not instantiate test set scheduler
      Creating report...
      Report Created
      FATAL: Couldn't run tests
      Finished: FAILURE

        Attachments

          Activity

          Hide
          bbonn bbonn added a comment -

          Not really resolved, but we know what is going on now and I am not sure it is up to this plug-in to fix. We have a named user that runs the Hudson windows service on the slaves in our environment. Because of company policy this user does not have log in rights, only the right to run services (Company Policy...). So when this user tries to schedule a test it fails because he doesn't have rights to control other apps on the slave i.e. Quality Center Scheduler (I guess..)

          If you do have thoughts on how to improve this process I would love to hear them, or if you would like more detail, but for now I am marking this postponed. Thanks!

          Show
          bbonn bbonn added a comment - Not really resolved, but we know what is going on now and I am not sure it is up to this plug-in to fix. We have a named user that runs the Hudson windows service on the slaves in our environment. Because of company policy this user does not have log in rights, only the right to run services (Company Policy...). So when this user tries to schedule a test it fails because he doesn't have rights to control other apps on the slave i.e. Quality Center Scheduler (I guess..) If you do have thoughts on how to improve this process I would love to hear them, or if you would like more detail, but for now I am marking this postponed. Thanks!

            People

            Assignee:
            rseguy Romain Seguy
            Reporter:
            bbonn bbonn
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: