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

Updating maven jobs that are running causes them to think modules are not built

      If the seed job runs and updates a maven job that is already executing then all modules that have not built for that job are marked as 'not built' which then causes those artifacts to not be fingerprinted correctly. Looking at the console output for the job, it continues to execute correctly, but something about updating the job from the seed job causes it to break.

          [JENKINS-26305] Updating maven jobs that are running causes them to think modules are not built

          Lorenz Bateman created issue -
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 160366 ] New: JNJira + In-Review [ 180328 ]
          Daniel Spilker made changes -
          Component/s New: maven-plugin [ 16033 ]
          Daniel Spilker made changes -
          Assignee Original: Daniel Spilker [ daspilker ]

            Unassigned Unassigned
            lorenzhawkes Lorenz Bateman
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: