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

Maven2 builds not checking for parent's snapshot building

    • Icon: Improvement Improvement
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: All, OS: All

      On Maven 2 projects, I have checked on the "Build whenever a SNAPSHOT dependency
      is built" feature. However, it does not build when its parent snapshot changes.

      The description does not say it checks for the parent builds (only states it
      checks dependencies, plugins, and extensions), so probably it is working as
      designed.

      This enhancement request is to add checking of the parent snapshots.

      A workaround is to check on the "Build after other projects are built" feature
      and enter the parent snapshot project on each of the modules, but that's effort
      and maintenance, especially with a large quantity of components, and
      particularly with regular releases!

          [JENKINS-2996] Maven2 builds not checking for parent's snapshot building

          kutzi added a comment -

          Does this still happen in current versions of Jenkins?
          In my experience, this should work now.

          kutzi added a comment - Does this still happen in current versions of Jenkins? In my experience, this should work now.

          kutzi added a comment -

          Cannot reproduce in current versions

          kutzi added a comment - Cannot reproduce in current versions

          foal added a comment -

          I can confirm this issue on 1.499 with some exceptions. In my case the changing in parent pom is trigered children progect to build but not the all.

          The tipical situation after parent build is

          mail#11
          JRS Commons. Spring local beans#25
          JRS Commons. Base domain support#13
          JRS OSS Flexess#40
          JRS Commons. GWT (no)
          JRS Internal POM. Obfuscated#44
          JRS Internal POM#42
          JRS Commons. GXT ExtInfo#11
          JRS OSS Simple User Manager (SUM)(no)

          As you can see JRS Commons. GWT and JRS OSS Simple User Manager were not trigered for some reason.

          foal added a comment - I can confirm this issue on 1.499 with some exceptions. In my case the changing in parent pom is trigered children progect to build but not the all. The tipical situation after parent build is mail#11 JRS Commons. Spring local beans#25 JRS Commons. Base domain support#13 JRS OSS Flexess#40 JRS Commons. GWT (no) JRS Internal POM. Obfuscated#44 JRS Internal POM#42 JRS Commons. GXT ExtInfo#11 JRS OSS Simple User Manager (SUM)(no) As you can see JRS Commons. GWT and JRS OSS Simple User Manager were not trigered for some reason.

          kutzi added a comment -

          @foal without knowing your project structure, it's difficult to decide if it's a bug or an issue in your setup.
          If you have an independent testcase, please attach it to this issue. Otherwise, please ask for help on the users list.

          kutzi added a comment - @foal without knowing your project structure, it's difficult to decide if it's a bug or an issue in your setup. If you have an independent testcase, please attach it to this issue. Otherwise, please ask for help on the users list.

            Unassigned Unassigned
            jeffjensen jeffjensen
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: