Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Duplicate
    • Component/s: core
    • Labels:
      None
    • Similar Issues:

      Description

      Hey
      Since the last update from Jenkins two options are blocking job to get startet. I have among 60 jobs. Each job depents on another job. It is ist nessassary that the chain is respected. There for I set the two options (in german)
      Build blockieren, solange vorgelagertes Projekt gebaut wird.
      Build blockieren, solange nachgelagertes Projekt gebaut wird.
      But now some jobs dont get startet. They are all watiting in the waiting queue. In previous version all jobs get startet. Is there somethong wrong now?

        Attachments

          Issue Links

            Activity

            ahmedalkhalaf Ahmed Alkhalaf created issue -
            oleg_nenashev Oleg Nenashev made changes -
            Field Original Value New Value
            Component/s core [ 15593 ]
            Component/s _test [ 19622 ]
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Which Jenkins version did you use before the upgrade? And which one do you use now?

            Show
            oleg_nenashev Oleg Nenashev added a comment - Which Jenkins version did you use before the upgrade? And which one do you use now?
            Hide
            danielbeck Daniel Beck added a comment -

            Works as designed, emphasis mine:

            When this option is checked, Jenkins will prevent the project from building when a dependency of this project is in the queue, or building. The dependencies include the direct as well as the transitive dependencies.

            When this option is checked, Jenkins will prevent the project from building when a child of this project is in the queue, or building. The children include the direct as well as the transitive children.

            So it is actually fairly easy to build a deadlock of some kind in larger job chains, but that's how it's documented.

            Show
            danielbeck Daniel Beck added a comment - Works as designed, emphasis mine: When this option is checked, Jenkins will prevent the project from building when a dependency of this project is in the queue, or building. The dependencies include the direct as well as the transitive dependencies. When this option is checked, Jenkins will prevent the project from building when a child of this project is in the queue, or building. The children include the direct as well as the transitive children. So it is actually fairly easy to build a deadlock of some kind in larger job chains, but that's how it's documented.
            oleg_nenashev Oleg Nenashev made changes -
            Assignee Oleg Nenashev [ oleg_nenashev ]
            danielbeck Daniel Beck made changes -
            Link This issue is related to JENKINS-27708 [ JENKINS-27708 ]
            danielbeck Daniel Beck made changes -
            Link This issue is related to JENKINS-27968 [ JENKINS-27968 ]
            Hide
            danielbeck Daniel Beck added a comment -

            Assuming this duplicates JENKINS-28926, for which a fix will be in Jenkins 1.618 or so.

            Show
            danielbeck Daniel Beck added a comment - Assuming this duplicates JENKINS-28926 , for which a fix will be in Jenkins 1.618 or so.
            danielbeck Daniel Beck made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Duplicate [ 3 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 163751 ] JNJira + In-Review [ 197303 ]

              People

              • Assignee:
                Unassigned
                Reporter:
                ahmedalkhalaf Ahmed Alkhalaf
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: