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

No build.xml is created when warnings plugin is used in combination with deactivated maven plugin

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: analysis-core-plugin
    • Labels:
      None
    • Environment:
      Windows 7, Jenkins 1.546 and 1.532, Jenkins started as Service
    • Similar Issues:
    • Released As:
      warnings-ng 1.0.0-beta1

      Description

      The Warnings Plug-in doesn't seem to work correctly if the maven plugin is deactivated. In our case it prevented the creation of the build.xml at the end of a build. As long as Jenkins is running, all builds and their history are shown correctly, but after a restart, Jenkins can't get the necessary informations to build up the history due to missing build.xml. This results in a faulty build history (no past builds are shown).

      To reproduce, follow these steps:
      1. Deactivate the maven plugin
      2. Make sure you have the Warnings and msbuild plugin installed
      3. Create a job which contains a msbuild step (we used msbuild 4.0)
      4. Create a post buildstep "Scan for compiler warnings" and use "Scan console log" with "msbulid parser"

      In our case, with above setup, no build.xml was created if:

      • maven was deactivated AND warnings was turned on

      In other combinations (maven on/off, warnings on/off) a build.xml was created hence the problem lies within the Warnings plugin and not maven.

      In Attachment you find a minimal example (no_buildXml_minExample.jpg) where you can reproduce the bug by turning maven on/off. In the example you can see that Build #2 is missing - this was done with deactivated maven.

      no_buildXml_plugins.jpg shows our installed Jenkins plugins in case there are other unknown side effects.

        Attachments

          Issue Links

            Activity

            marquito77 Marko Stefanovic created issue -
            marquito77 Marko Stefanovic made changes -
            Field Original Value New Value
            Summary No build.lxml is created when warnings plugin is used in combination with deactivated maven plugin No build.xml is created when warnings plugin is used in combination with deactivated maven plugin
            marquito77 Marko Stefanovic made changes -
            Description The Warnings Plug-in doesn't seem to work correctly if the maven plugin is deactivated. In our case it prevented the creation of the build.xml at the end of a build. As long as Jenkins is running, all builds and their history are shown correctly, but after a restart, Jenkins can't get the necessary informations to build up the history due to missing build.xml. This results in a faulty build history (no past builds are shown).

            To reproduce, follow these steps:
            1. Deactivate the maven plugin
            2. Make sure you have the Warnings and msbuild plugin installed
            3. Create a job which contains a msbuild step (we used msbuild 4.0)
            4. Create a post buildstep "Scan for compiler warnings" and use "Scan console log" with "msbulid parser"

            In our case, with above setup, no build.xml was created if:
            - maven was deactivated AND warnings was turned on

            We tested that in all other combinations a build.xml was created to make sure that the problem lies within the Warnings plugin and not maven.
            The Warnings Plug-in doesn't seem to work correctly if the maven plugin is deactivated. In our case it prevented the creation of the build.xml at the end of a build. As long as Jenkins is running, all builds and their history are shown correctly, but after a restart, Jenkins can't get the necessary informations to build up the history due to missing build.xml. This results in a faulty build history (no past builds are shown).

            To reproduce, follow these steps:
            1. Deactivate the maven plugin
            2. Make sure you have the Warnings and msbuild plugin installed
            3. Create a job which contains a msbuild step (we used msbuild 4.0)
            4. Create a post buildstep "Scan for compiler warnings" and use "Scan console log" with "msbulid parser"

            In our case, with above setup, no build.xml was created if:
            - maven was deactivated AND warnings was turned on

            In other combinations (maven on/off, warnings on/off) a build.xml was created hence the problem lies within the Warnings plugin and not maven.
            drulli Ulli Hafner made changes -
            Priority Major [ 3 ] Minor [ 4 ]
            Component/s maven [ 16033 ]
            marquito77 Marko Stefanovic made changes -
            Attachment no_buildXML_jenkins_err.log [ 24956 ]
            drulli Ulli Hafner made changes -
            Link This issue is related to JENKINS-14727 [ JENKINS-14727 ]
            marquito77 Marko Stefanovic made changes -
            Environment Windows 7, Jenkins as Service, Windows 7, Jenkins 1.546 and 1.532, Jenkins started as Service
            marquito77 Marko Stefanovic made changes -
            Attachment no_buildXml_InstalledPlugins.jpg [ 24959 ]
            Attachment no_buildXml_minExample.jpg [ 24960 ]
            marquito77 Marko Stefanovic made changes -
            Description The Warnings Plug-in doesn't seem to work correctly if the maven plugin is deactivated. In our case it prevented the creation of the build.xml at the end of a build. As long as Jenkins is running, all builds and their history are shown correctly, but after a restart, Jenkins can't get the necessary informations to build up the history due to missing build.xml. This results in a faulty build history (no past builds are shown).

            To reproduce, follow these steps:
            1. Deactivate the maven plugin
            2. Make sure you have the Warnings and msbuild plugin installed
            3. Create a job which contains a msbuild step (we used msbuild 4.0)
            4. Create a post buildstep "Scan for compiler warnings" and use "Scan console log" with "msbulid parser"

            In our case, with above setup, no build.xml was created if:
            - maven was deactivated AND warnings was turned on

            In other combinations (maven on/off, warnings on/off) a build.xml was created hence the problem lies within the Warnings plugin and not maven.
            The Warnings Plug-in doesn't seem to work correctly if the maven plugin is deactivated. In our case it prevented the creation of the build.xml at the end of a build. As long as Jenkins is running, all builds and their history are shown correctly, but after a restart, Jenkins can't get the necessary informations to build up the history due to missing build.xml. This results in a faulty build history (no past builds are shown).

            To reproduce, follow these steps:
            1. Deactivate the maven plugin
            2. Make sure you have the Warnings and msbuild plugin installed
            3. Create a job which contains a msbuild step (we used msbuild 4.0)
            4. Create a post buildstep "Scan for compiler warnings" and use "Scan console log" with "msbulid parser"

            In our case, with above setup, no build.xml was created if:
            - maven was deactivated AND warnings was turned on

            In other combinations (maven on/off, warnings on/off) a build.xml was created hence the problem lies within the Warnings plugin and not maven.

            In Attachment you find a minimal example (no_buildXml_minExample.jpg) where you can reproduce the bug by turning maven on/off. In the example you can see that Build #2 is missing - this was done with deactivated maven.

            no_buildXml_plugins.jpg shows our installed Jenkins plugins in case there are other unknown side effects.
            drulli Ulli Hafner made changes -
            Component/s analysis-core [ 15709 ]
            kveretennicov Konstantin Veretennicov made changes -
            Link This issue is related to JENKINS-15156 [ JENKINS-15156 ]
            rlx Renaud Lehoux made changes -
            Priority Minor [ 4 ] Critical [ 2 ]
            drulli Ulli Hafner made changes -
            Component/s warnings-plugin [ 15513 ]
            Priority Critical [ 2 ] Minor [ 4 ]
            drulli Ulli Hafner made changes -
            Link This issue is duplicated by JENKINS-30514 [ JENKINS-30514 ]
            drulli Ulli Hafner made changes -
            Link This issue is duplicated by JENKINS-31603 [ JENKINS-31603 ]
            drulli Ulli Hafner made changes -
            Link This issue is related to JENKINS-14727 [ JENKINS-14727 ]
            drulli Ulli Hafner made changes -
            Link This issue depends on JENKINS-14727 [ JENKINS-14727 ]
            drulli Ulli Hafner made changes -
            Labels analysis-core-2.0
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 153131 ] JNJira + In-Review [ 178430 ]
            drulli Ulli Hafner made changes -
            Link This issue depends on JENKINS-14727 [ JENKINS-14727 ]
            drulli Ulli Hafner made changes -
            Link This issue depends on JENKINS-44957 [ JENKINS-44957 ]
            drulli Ulli Hafner made changes -
            Labels analysis-core-2.0
            drulli Ulli Hafner made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            Released As warnings-ng 1.0.0-beta1

              People

              • Assignee:
                drulli Ulli Hafner
                Reporter:
                marquito77 Marko Stefanovic
              • Votes:
                3 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: