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

Xvfb is not launched on master node in a multi-configuration job

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • xvfb-plugin
    • Jenkins ver. 1.611, xvfb-plugin 1.0.16

      I've set Xvfb's option "Start only on nodes labeled" to "master" in a multi-configuration job.
      None of the involved slave nodes has a Xvfb executable, only the master node has.
      None of the combinations run on master, but I have a post-build script that needs Xvfb.
      The job's "Restrict where this project can be run" is set to "master".

      I would have expected Xvfb to run on the master during the whole job run, including the post-build phase, but it didn't happen.

      tl;dr a matrix job spawning jobs on nodes without Xvfb, and a post-build jobs that collect such jobs results and creates plots from master.

          [JENKINS-30247] Xvfb is not launched on master node in a multi-configuration job

          zregvart added a comment -

          Jenkins build wrappers do not run in the post build actions, but in Xvfb plugin there is an option you can check called "Shutdown Xvfb with whole job, not just with the main build action" that should help you have the Xvfb running in the post build steps.

          zregvart added a comment - Jenkins build wrappers do not run in the post build actions, but in Xvfb plugin there is an option you can check called "Shutdown Xvfb with whole job, not just with the main build action" that should help you have the Xvfb running in the post build steps.

          Thanks for the quick answer. I've enable that but it didn't work, Xvfb is never started on the master node.

          Alessandro Foresi added a comment - Thanks for the quick answer. I've enable that but it didn't work, Xvfb is never started on the master node.

            zregvart zregvart
            alef Alessandro Foresi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: