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

Shared and exclusive locking

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • Platform: All, OS: All

      It would be nice if one could specify that an upstream job should be prevented
      from running (again) until all depending downstream jobs has terminated, just as
      well as downstream jobs should be prevented from running until the upstream
      job(s) has completed.
      In our case we have a monolithic "common project" generating a vast amount of
      dll's making it undesirable to upload them all as artifacts. Then we have a lot
      of other projects depending on bits and parts from this "common project", but
      not always all parts. Thus, we have configured these projects to get their
      dependencies directly from the workspace of the "common project" which all work
      out well as long as one is careful with the scheduling of the jobs. Only, when
      allowing e.g. commit triggered builds this can lead to all sorts of errors
      because jobs can be started interdependently.

        1. hudson-1990.patch
          9 kB
          ev
        2. patch.txt
          8 kB
          Damien Coraboeuf

            Unassigned Unassigned
            boerrild boerrild
            Votes:
            10 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: