Skip to content

[JENKINS-18846] New lazy loading permalinks can break job.lastStableBuild != null => job.lastSuccessfulBuild != null #14760

Description

@jenkins-infra-bot

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.


Originally reported by stephenconnolly, imported from: New lazy loading permalinks can break job.lastStableBuild != null => job.lastSuccessfulBuild != null
  • assignee: jglick
  • status: Resolved
  • priority: Major
  • component(s): core, maven-plugin
  • label(s): 1.509.4-fixed, lazy-loading, permalink, symlink
  • resolution: Fixed
  • resolved: 2013-08-20T18:21:25+00:00
  • votes: 0
  • watchers: 3
  • imported: 2025-11-24
Raw content of original issue

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.

No activity

Activity on this issue will appear here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions