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

When a deliver fails, the changelog is NOT written, case 9869

XMLWordPrintable

      The changelog and the deliver is done in the same remote method. If the deliver fails, the changelog is lost.
      Split it up, so that failed delivers still have changelogs.

      This is actually not something the SCM implementation can do anything about.
      The change log is parsed and written in the same breath as the ClearCase deliver. This means that the core dictates, that if anything fails in checkout() no change log is written.

      This is also applicable for the git plugin when the "Merge before build" option is set.

      If the deliver or the merge fails, the change log is not written, even though there is an actual change set. No one is blamed as a result.

          [JENKINS-19558] When a deliver fails, the changelog is NOT written, case 9869

          Christian Wolfgang created issue -
          Christian Wolfgang made changes -
          Summary Original: When a deliver fails, the changelog is written, case 9869 New: When a deliver fails, the changelog is NOT written, case 9869
          Christian Wolfgang made changes -
          Component/s New: core [ 15593 ]
          Component/s New: git [ 15543 ]
          Description Original: The changelog and the deliver is done in the same remote method. If the deliver fails, the changelog is lost.
          Split it up, so that failed delivers still have changelogs.           		New: The changelog and the deliver is done in the same remote method. If the deliver fails, the changelog is lost.
          Split it up, so that failed delivers still have changelogs.

          This is actually not something the SCM implementation can anything about.
          The change log is parsed and written in the same breath as the ClearCase deliver. This means that the core dictates, that if anything fails in checkout() no change log is written.

          This is also applicable for the git plugin when the "Merge before build" option is set.
          Christian Wolfgang made changes -
          Description Original: The changelog and the deliver is done in the same remote method. If the deliver fails, the changelog is lost.
          Split it up, so that failed delivers still have changelogs.

          This is actually not something the SCM implementation can anything about.
          The change log is parsed and written in the same breath as the ClearCase deliver. This means that the core dictates, that if anything fails in checkout() no change log is written.

          This is also applicable for the git plugin when the "Merge before build" option is set.           		New: The changelog and the deliver is done in the same remote method. If the deliver fails, the changelog is lost.
          Split it up, so that failed delivers still have changelogs.

          This is actually not something the SCM implementation can anything about.
          The change log is parsed and written in the same breath as the ClearCase deliver. This means that the core dictates, that if anything fails in checkout() no change log is written.

          This is also applicable for the git plugin when the "Merge before build" option is set.

          If the deliver or the merge fails, the change log is not written, even though there is an actual change set. No one is blamed as a result.
          Christian Wolfgang made changes -
          Description Original: The changelog and the deliver is done in the same remote method. If the deliver fails, the changelog is lost.
          Split it up, so that failed delivers still have changelogs.

          This is actually not something the SCM implementation can anything about.
          The change log is parsed and written in the same breath as the ClearCase deliver. This means that the core dictates, that if anything fails in checkout() no change log is written.

          This is also applicable for the git plugin when the "Merge before build" option is set.

          If the deliver or the merge fails, the change log is not written, even though there is an actual change set. No one is blamed as a result.           		New: The changelog and the deliver is done in the same remote method. If the deliver fails, the changelog is lost.
          Split it up, so that failed delivers still have changelogs.

          This is actually not something the SCM implementation can do anything about.
          The change log is parsed and written in the same breath as the ClearCase deliver. This means that the core dictates, that if anything fails in checkout() no change log is written.

          This is also applicable for the git plugin when the "Merge before build" option is set.

          If the deliver or the merge fails, the change log is not written, even though there is an actual change set. No one is blamed as a result.
          Jesse Glick made changes -
          Link New: This issue depends on JENKINS-19740 [ JENKINS-19740 ]
          Mads Nielsen made changes -
          Fix Version/s New: current [ 10162 ]
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 151012 ] New: JNJira + In-Review [ 193776 ]
          Mark Waite made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            praqma Praqma Support
            wolfgang Christian Wolfgang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: