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

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • analysis-core-plugin
    • None
    • Windows 7, Jenkins 1.546 and 1.532, Jenkins started as Service
    • 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

            Code changed in jenkins
            User: Ulli Hafner
            Path:
            pom.xml
            tasks.iml
            http://jenkins-ci.org/commit/tasks-plugin/9f10bf8c91e24db028a8c3d750f39eaa03d96e56
            Log:
            JENKINS-21268 JENKINS-14727 Make maven-plugin a mandatory dependency.

            Workaround for JENKINS-21268. The maven plug-in can't be optional without breaking the API. This issue needs to be adressed in 2.x release.

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: pom.xml tasks.iml http://jenkins-ci.org/commit/tasks-plugin/9f10bf8c91e24db028a8c3d750f39eaa03d96e56 Log: JENKINS-21268 JENKINS-14727 Make maven-plugin a mandatory dependency. Workaround for JENKINS-21268 . The maven plug-in can't be optional without breaking the API. This issue needs to be adressed in 2.x release.

            Code changed in jenkins
            User: Ulli Hafner
            Path:
            pom.xml
            http://jenkins-ci.org/commit/warnings-plugin/0cf405ecbd22b85773efa6f8cc03c3ae6f14968d
            Log:
            JENKINS-21268 JENKINS-14727 Make maven-plugin a mandatory dependency.

            Workaround for JENKINS-21268. The maven plug-in can't be optional without breaking the API. This issue needs to be adressed in 2.x release.

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: pom.xml http://jenkins-ci.org/commit/warnings-plugin/0cf405ecbd22b85773efa6f8cc03c3ae6f14968d Log: JENKINS-21268 JENKINS-14727 Make maven-plugin a mandatory dependency. Workaround for JENKINS-21268 . The maven plug-in can't be optional without breaking the API. This issue needs to be adressed in 2.x release.

            Code changed in jenkins
            User: Ulli Hafner
            Path:
            pom.xml
            http://jenkins-ci.org/commit/warnings-plugin/4b1cc29344b7199b56db1072948821270a648971
            Log:
            JENKINS-21268 JENKINS-14727 Make maven-plugin a mandatory dependency.

            Workaround for JENKINS-21268. The maven plug-in can't be optional without breaking the API. This issue needs to be adressed in 2.x release.

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: pom.xml http://jenkins-ci.org/commit/warnings-plugin/4b1cc29344b7199b56db1072948821270a648971 Log: JENKINS-21268 JENKINS-14727 Make maven-plugin a mandatory dependency. Workaround for JENKINS-21268 . The maven plug-in can't be optional without breaking the API. This issue needs to be adressed in 2.x release.

            Code changed in jenkins
            User: Ulli Hafner
            Path:
            pom.xml
            http://jenkins-ci.org/commit/checkstyle-plugin/54384636ac114dcab6fe52fe7916b952f536199e
            Log:
            JENKINS-21268 JENKINS-14727 Make maven-plugin a mandatory dependency.

            Workaround for JENKINS-21268. The maven plug-in can't be optional without breaking the API. This issue needs to be adressed in 2.x release.

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: pom.xml http://jenkins-ci.org/commit/checkstyle-plugin/54384636ac114dcab6fe52fe7916b952f536199e Log: JENKINS-21268 JENKINS-14727 Make maven-plugin a mandatory dependency. Workaround for JENKINS-21268 . The maven plug-in can't be optional without breaking the API. This issue needs to be adressed in 2.x release.

            Code changed in jenkins
            User: Ulli Hafner
            Path:
            pom.xml
            http://jenkins-ci.org/commit/checkstyle-plugin/2e997a90c1c07020e5f442baa1d386698802a713
            Log:
            JENKINS-21268 JENKINS-14727 Make maven-plugin a mandatory dependency.

            Workaround for JENKINS-21268. The maven plug-in can't be optional without breaking the API. This issue needs to be adressed in 2.x release.

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: pom.xml http://jenkins-ci.org/commit/checkstyle-plugin/2e997a90c1c07020e5f442baa1d386698802a713 Log: JENKINS-21268 JENKINS-14727 Make maven-plugin a mandatory dependency. Workaround for JENKINS-21268 . The maven plug-in can't be optional without breaking the API. This issue needs to be adressed in 2.x release.

            People

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

              Dates

                Created:
                Updated:
                Resolved: