New lazy loading permalinks can break job.lastStableBuild != null => job.lastSuccessfulBuild != null

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      I have seen this on some Maven module builds, especially ones where only some of the modules in the pom are build, e.g. by using `-pl some-module -am`

      The MavenModuleSet will have both lastSuccessfulBuild and lastStableBuild defined.

      The individual MavenModule instances, however, will only have lastStable defined.

            Assignee:
            Jesse Glick
            Reporter:
            Stephen Connolly
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: