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

Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger

    • 3.24

      After upgrading from 1.525 to 1.528 there is a lot of extra logging in our Maven build logs. This makes it hard to read the logs. It still happens in 1.529

      It is the org.apache.maven.cli.event.ExecutionEventLogger entries.

      Note:
      They are multimodule maven builds
      Timestamper plugin is active so Time is duplicated in the logs below:

      16:47:28 Aug 27, 2013 4:47:29 PM org.apache.maven.cli.event.ExecutionEventLogger projectDiscoveryStarted
      16:47:28 INFO: Scanning for projects...
      16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
      16:47:29 INFO: ------------------------------------------------------------------------
      16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
      16:47:29 INFO: Reactor Build Order:
      16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
      16:47:29 INFO: 
      16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
      ...
      ...
      16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
      16:47:29 INFO:                                                                         
      16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
      16:47:29 INFO: ------------------------------------------------------------------------
      16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
      16:47:29 INFO: Building xxxxx
      16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
      16:47:29 INFO: ------------------------------------------------------------------------
      16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
      16:47:29 INFO: 
      16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
      16:47:29 INFO: --- maven-clean-plugin:2.4.1:clean (default-clean) @ xxx ---
      16:47:32 Aug 27, 2013 4:47:33 PM hudson.maven.ExecutedMojo <init>
      16:47:32 WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
      16:47:32 Aug 27, 2013 4:47:33 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
      16:47:32 INFO: 
      16:47:32 Aug 27, 2013 4:47:33 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
      

          [JENKINS-19396] Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger

          Tommy Bø added a comment -

          We noticed this after upgrading from 1.525 to 1.526. It seems that this happens in the main target in regular maven jobs. When we set up maven executions in post-build steps the log statements are fine.

          Tommy Bø added a comment - We noticed this after upgrading from 1.525 to 1.526. It seems that this happens in the main target in regular maven jobs. When we set up maven executions in post-build steps the log statements are fine.

          cowwoc added a comment -

          I am getting the following (equally hard to read) output with Maven 3.1.0, Jenkins 1.529:

          [pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger - Scanning for projects...
          

          I'm only interested in the logger message. Meaning, please trim everything up to (and including) the logger name.

          cowwoc added a comment - I am getting the following (equally hard to read) output with Maven 3.1.0, Jenkins 1.529: [pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger - Scanning for projects... I'm only interested in the logger message. Meaning, please trim everything up to (and including) the logger name.

          Hannes Kogler added a comment -

          same here!

          upgraded from 1.518 to 1.526 today and have the same problem. Does anybody know where the additional logging entries come from?

          Hannes Kogler added a comment - same here! upgraded from 1.518 to 1.526 today and have the same problem. Does anybody know where the additional logging entries come from?

          cadiolis added a comment -

          Same here! Very irritating to have the log filled up with apparent useless information

          cadiolis added a comment - Same here! Very irritating to have the log filled up with apparent useless information

          Worksarounds appreciated. These messages make build logs very hard to read.

          Julio Morimoto added a comment - Worksarounds appreciated. These messages make build logs very hard to read.

          Per J. Lund added a comment -

          Same here. In addition it seems that the error messages is not displayed at all!
          I had to roll back to 1.523 to get a usable version.

          Per J. Lund added a comment - Same here. In addition it seems that the error messages is not displayed at all! I had to roll back to 1.523 to get a usable version.

          cowwoc added a comment -

          Agreed. Error messages are also missing for me. Someone should increase the priority of this bug.

          cowwoc added a comment - Agreed. Error messages are also missing for me. Someone should increase the priority of this bug.

          Dexter Hu added a comment -

          Same here! Does anyone have a workaround for latest version?

          Dexter Hu added a comment - Same here! Does anyone have a workaround for latest version?

          Dexter Hu added a comment -

          I had to roll back to 1.525 to solve this problem

          Dexter Hu added a comment - I had to roll back to 1.525 to solve this problem

          Daniel Beck added a comment -

          Separate issue exists for missing errors: JENKINS-19352

          Possibly related (or even caused by): JENKINS-15935

          Daniel Beck added a comment - Separate issue exists for missing errors: JENKINS-19352 Possibly related (or even caused by): JENKINS-15935

          kutzi added a comment -

          Can others confirm that this is still happening in 1.529+?
          The changelog mentions that this was fixed in 1.529 http://jenkins-ci.org/changelog

          kutzi added a comment - Can others confirm that this is still happening in 1.529+? The changelog mentions that this was fixed in 1.529 http://jenkins-ci.org/changelog

          cowwoc added a comment - @kutzi, I already did. See https://issues.jenkins-ci.org/browse/JENKINS-19396?focusedCommentId=184739&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-184739

          kutzi added a comment -

          @cowwoc I did see that, but it's not clear for me if you're seeing the same problem reported originally (i.e. duplicated log entries) or some other related issue

          kutzi added a comment - @cowwoc I did see that, but it's not clear for me if you're seeing the same problem reported originally (i.e. duplicated log entries) or some other related issue

          Harald Albers added a comment -

          @kutzi This issue is still present in Jenkins 1.531's Maven 3.0 builds. The changelog entry you mentioned must be about a different, Maven 3.1 related issue.

          Harald Albers added a comment - @kutzi This issue is still present in Jenkins 1.531's Maven 3.0 builds. The changelog entry you mentioned must be about a different, Maven 3.1 related issue.

          Raúl Wegmann added a comment -

          I can also confirm that this is still happening in 1.532 (Maven 3.0 builds).

          Raúl Wegmann added a comment - I can also confirm that this is still happening in 1.532 (Maven 3.0 builds).

          Dan Albu added a comment -

          Same happened on Jenkins v. 1.533 with Maven 2/3 jobs

          Dan Albu added a comment - Same happened on Jenkins v. 1.533 with Maven 2/3 jobs

          Per J. Lund added a comment -

          Is there some logger configuration that I am missing in my setup?
          Something that changed since 1.523?
          The versions between 1.524-1.533 are completely useless to us.
          All error messages from maven are lost and it is impossible to see what caused a build to fail.
          The output is flooded with useless log and important info is not even shown.
          We will have to stay with 1.523 until this is fixed.

          Sorry for my frustration - I like, and depend on a great product like Jenkins!

          Per J. Lund added a comment - Is there some logger configuration that I am missing in my setup? Something that changed since 1.523? The versions between 1.524-1.533 are completely useless to us. All error messages from maven are lost and it is impossible to see what caused a build to fail. The output is flooded with useless log and important info is not even shown. We will have to stay with 1.523 until this is fixed. Sorry for my frustration - I like, and depend on a great product like Jenkins!

          Dan Albu added a comment -

          @ Per : you can see from the discussion there is a bug not fixed that causes all this problems. Try v 1.522. I made a revert back to that one myself. We all are waiting for this bug to get fixed

          Dan Albu added a comment - @ Per : you can see from the discussion there is a bug not fixed that causes all this problems. Try v 1.522. I made a revert back to that one myself. We all are waiting for this bug to get fixed

          kutzi added a comment -

          Workaround: add -Djava.util.logging.SimpleFormatter.format="%4$s: %5$s%6$s%n" to the MAVEN_OPTS of the affected jobs

          kutzi added a comment - Workaround: add -Djava.util.logging.SimpleFormatter.format="%4$s: %5$s%6$s%n" to the MAVEN_OPTS of the affected jobs

          Code changed in jenkins
          User: Christoph Kutzinski
          Path:
          src/main/java/hudson/maven/MavenModuleSetBuild.java
          http://jenkins-ci.org/commit/maven-plugin/11b05a7615a43902b5577782b415aa5befa9121d
          Log:
          [FIXED JENKINS-19396] use less verbose logging format for Maven 3 builds

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/maven/MavenModuleSetBuild.java http://jenkins-ci.org/commit/maven-plugin/11b05a7615a43902b5577782b415aa5befa9121d Log: [FIXED JENKINS-19396] use less verbose logging format for Maven 3 builds

          kutzi added a comment -

          Would be great if someone could try the fixed maven-plugin before I cut a release from it:
          https://www.dropbox.com/sh/kjkh5g3r68kmlj7/JvgKJnf7gp

          kutzi added a comment - Would be great if someone could try the fixed maven-plugin before I cut a release from it: https://www.dropbox.com/sh/kjkh5g3r68kmlj7/JvgKJnf7gp

          Paolo Compieta added a comment - - edited

          Hi, just installed the plugin and got a clean log.
          Also, i notice at the begginning of the console output the additional maven opt "-Djava.util.logging.SimpleFormatter.format=%4$s: %5$s%6$s%n"
          +1

          Paolo Compieta added a comment - - edited Hi, just installed the plugin and got a clean log. Also, i notice at the begginning of the console output the additional maven opt "-Djava.util.logging.SimpleFormatter.format=%4$s: %5$s%6$s%n" +1

          Harald Albers added a comment -

          Works with current Jenkins 1.534. The added lines no longer appear.

          Harald Albers added a comment - Works with current Jenkins 1.534. The added lines no longer appear.

          Hi,

          This fixes it for builds using JDK 7 but not for builds using JDK 6

          thanks
          Geoff

          Geoff Cummings added a comment - Hi, This fixes it for builds using JDK 7 but not for builds using JDK 6 thanks Geoff

          From what I can tell, the java.util.logging.SimpleFormatter.format property feature was introduced in Java 7. Still have extra logging for maven builds using Java 6

          Geoff Cummings added a comment - From what I can tell, the java.util.logging.SimpleFormatter.format property feature was introduced in Java 7. Still have extra logging for maven builds using Java 6

          kutzi added a comment -

          @Geoff, thanks for the feedback. Seems you're right - the property was added in Java 7.
          I'll try to find a way to fix this for Java 6, too.

          BTW: I'm open for pull requests, if someone has a clever solution

          kutzi added a comment - @Geoff, thanks for the feedback. Seems you're right - the property was added in Java 7. I'll try to find a way to fix this for Java 6, too. BTW: I'm open for pull requests, if someone has a clever solution

          Hao CHEN added a comment -

          Still seeing this in 1.535 (JDK 7)

          Hao CHEN added a comment - Still seeing this in 1.535 (JDK 7)

          kutzi added a comment -

          I just uploaded a test build which should fix the issue for JDK 6, too
          https://www.dropbox.com/sh/kjkh5g3r68kmlj7/JvgKJnf7gp
          Please test

          kutzi added a comment - I just uploaded a test build which should fix the issue for JDK 6, too https://www.dropbox.com/sh/kjkh5g3r68kmlj7/JvgKJnf7gp Please test

          Code changed in jenkins
          User: Christoph Kutzinski
          Path:
          src/main/java/hudson/maven/Maven3Builder.java
          src/main/java/hudson/maven/MavenConsoleFormatter.java
          src/main/java/hudson/maven/MavenModuleSetBuild.java
          http://jenkins-ci.org/commit/maven-plugin/d8862d4ee8585411b6a46ce1101000962cc4bcb0
          Log:
          [FIXED JENKINS-19396] use less verbose logging format for Maven 3 builds

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/maven/Maven3Builder.java src/main/java/hudson/maven/MavenConsoleFormatter.java src/main/java/hudson/maven/MavenModuleSetBuild.java http://jenkins-ci.org/commit/maven-plugin/d8862d4ee8585411b6a46ce1101000962cc4bcb0 Log: [FIXED JENKINS-19396] use less verbose logging format for Maven 3 builds

          Working great in Jenkins 1.535!!

          thanks very much !!

          Geoff Cummings added a comment - Working great in Jenkins 1.535!! thanks very much !!

          kutzi added a comment -

          Geoff, Java 6 and/or Java 7?

          kutzi added a comment - Geoff, Java 6 and/or Java 7?

          Code changed in jenkins
          User: Christoph Kutzinski
          Path:
          src/main/java/hudson/maven/Maven3Builder.java
          src/main/java/hudson/maven/Maven3ConsoleFormatter.java
          src/main/java/hudson/maven/MavenConsoleFormatter.java
          http://jenkins-ci.org/commit/maven-plugin/035d780980c316dc25cc656bd18d302172bc78d5
          Log:
          JENKINS-19396 Maven3ConsoleFormatter shouldn't be public, so it doesn't become part of the API. Plus: added license

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/maven/Maven3Builder.java src/main/java/hudson/maven/Maven3ConsoleFormatter.java src/main/java/hudson/maven/MavenConsoleFormatter.java http://jenkins-ci.org/commit/maven-plugin/035d780980c316dc25cc656bd18d302172bc78d5 Log: JENKINS-19396 Maven3ConsoleFormatter shouldn't be public, so it doesn't become part of the API. Plus: added license

          Oh Java 6 is what I was using.

          I forgot to test with Java 7, I'll check that tomorrow morning

          Geoff Cummings added a comment - Oh Java 6 is what I was using. I forgot to test with Java 7, I'll check that tomorrow morning

          puce added a comment -

          The issue is still there in v1.535 with a multi-module build where the top-level POM and one of the other Maven projects is useing:

          <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-toolchains-plugin</artifactId>
          <executions>
          <execution>
          <phase>validate</phase>
          <goals>
          <goal>toolchain</goal>
          </goals>
          </execution>
          </executions>
          <configuration>
          <toolchains>
          <jdk>
          <version>1.8</version>
          <vendor>oracle</vendor>
          </jdk>
          </toolchains>
          </configuration>
          </plugin>

          and

          java version "1.8.0-ea"
          Java(TM) SE Runtime Environment (build 1.8.0-ea-b111)
          Java HotSpot(TM) 64-Bit Server VM (build 25.0-b53, mixed mode)

          puce added a comment - The issue is still there in v1.535 with a multi-module build where the top-level POM and one of the other Maven projects is useing: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-toolchains-plugin</artifactId> <executions> <execution> <phase>validate</phase> <goals> <goal>toolchain</goal> </goals> </execution> </executions> <configuration> <toolchains> <jdk> <version>1.8</version> <vendor>oracle</vendor> </jdk> </toolchains> </configuration> </plugin> and java version "1.8.0-ea" Java(TM) SE Runtime Environment (build 1.8.0-ea-b111) Java HotSpot(TM) 64-Bit Server VM (build 25.0-b53, mixed mode)

          puce added a comment -

          There seem to be patches after v1.535

          Is this already fixed?

          puce added a comment - There seem to be patches after v1.535 Is this already fixed?

          Jesse Glick added a comment -

          @puce the Maven plugin is now independent, not tied to a specific Jenkins version.

          Jesse Glick added a comment - @puce the Maven plugin is now independent, not tied to a specific Jenkins version.

          aldaris added a comment -

          Is this going to be backported to LTS? I'm running into the same problem with 1.509.4

          aldaris added a comment - Is this going to be backported to LTS? I'm running into the same problem with 1.509.4

          Daniel Beck added a comment -

          aldaris: 1.509.x is obsolete. 1.532.1 has been released two weeks ago (nobody bothered to update the web site though), which seems to include the fix.

          Daniel Beck added a comment - aldaris: 1.509.x is obsolete. 1.532.1 has been released two weeks ago (nobody bothered to update the web site though), which seems to include the fix.

          aldaris added a comment -

          Thanks for the heads up, I've completely missed that release.

          aldaris added a comment - Thanks for the heads up, I've completely missed that release.

          With Jenkins ver. 1.532.1, we still get too many of these entries:

          Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
          INFO: ------------------------------------------------------------------------
          Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
          INFO: Reactor Build Order:
          Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
          INFO:
          Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
          INFO:

          Christian Eichenberger added a comment - With Jenkins ver. 1.532.1, we still get too many of these entries: Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted INFO: ------------------------------------------------------------------------ Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted INFO: Reactor Build Order: Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted INFO: Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted INFO:

          Daniel Beck added a comment -

          Christian Eichenberger: Update Maven Plugin to version 2.0. It's now independent of the core version.

          Daniel Beck added a comment - Christian Eichenberger: Update Maven Plugin to version 2.0. It's now independent of the core version.

          cowwoc added a comment -

          @Christian,

          I have the Maven Integration plugin 2.2 installed, and I'm still seeing org.apache.maven.cli.event.ExecutionEventLogger everywhere. Shouldn't this issue be reopened?

          cowwoc added a comment - @Christian, I have the Maven Integration plugin 2.2 installed, and I'm still seeing org.apache.maven.cli.event.ExecutionEventLogger everywhere. Shouldn't this issue be reopened?

          cowwoc added a comment -

          @Daniel Beck,

          Sorry, the last comment was directed at you. I am getting a very verbose syntax:

          [pool-3-thread-1] INFO org.apache.maven.cli.transfer.Slf4jMavenTransferListener - Downloading:  http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.4/maven-install-plugin-2.4.pom
          

          It looks like the logging pattern is at fault. I am expecting the line to begin with "Downloading". Is there any way to make it less verbose?

          cowwoc added a comment - @Daniel Beck, Sorry, the last comment was directed at you. I am getting a very verbose syntax: [pool-3-thread-1] INFO org.apache.maven.cli.transfer.Slf4jMavenTransferListener - Downloading: http: //repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.4/maven-install-plugin-2.4.pom It looks like the logging pattern is at fault. I am expecting the line to begin with "Downloading". Is there any way to make it less verbose?

          Reopen by mistake

          Kent Granström added a comment - Reopen by mistake

          Samuel Gabriel added a comment - - edited

          This issue still occur when running master on windows and slaves on linux with maven plugin version 3.8. The culprit is line https://github.com/jenkinsci/maven-plugin/blob/8adb97e92fbf0af494c26cc64611bd648b6ae8e9/src/main/java/hudson/maven/Maven31ProcessFactory.java#L66 which is also found in Maven32ProcessFactory Maven33ProcessFactory and Maven35ProcessFactory 

          The problem is mvn.getHomeDir().getPath() is running on master which uses windows and the file path become \home\jenkins\tools... maven cp becomes 

          -cp /home/jenkins/maven35-agent.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven-3.6.3/boot/plexus-classworlds-2.6.0.jar:\home\jenkins\tools\hudson.tasks.Maven_MavenInstallation\Maven-3.6.3/conf/logging jenkins.maven3.agent.Maven35Main /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven-3.6.3 /home/jenkins/remoting.jar /home/jenkins/maven35-interceptor.jar /home/jenkins/maven3-interceptor-commons.jar 40073

           

          this can be easily corrected by changing the line to 

           

          path += (getLauncher().isUnix()?":":";") + mvn.getHome() + "/conf/logging";

           

          mvn.getHome() is a string with the correct path separator.

          Samuel Gabriel added a comment - - edited This issue still occur when running master on windows and slaves on linux with maven plugin version 3.8. The culprit is line https://github.com/jenkinsci/maven-plugin/blob/8adb97e92fbf0af494c26cc64611bd648b6ae8e9/src/main/java/hudson/maven/Maven31ProcessFactory.java#L66  which is also found in Maven32ProcessFactory Maven33ProcessFactory and Maven35ProcessFactory  The problem is mvn.getHomeDir().getPath() is running on master which uses windows and the file path become \home\jenkins\tools... maven cp becomes  -cp /home/jenkins/maven35-agent.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven-3.6.3/boot/plexus-classworlds-2.6.0.jar :\home\jenkins\tools\hudson.tasks.Maven_MavenInstallation\Maven-3.6.3/ conf/logging jenkins.maven3.agent.Maven35Main /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven-3.6.3 /home/jenkins/remoting.jar /home/jenkins/maven35-interceptor.jar /home/jenkins/maven3-interceptor-commons.jar 40073   this can be easily corrected by changing the line to    path += (getLauncher().isUnix()? ":" : ";" ) + mvn.getHome() + "/conf/logging" ;   mvn.getHome() is a string with the correct path separator.

          I created this pull request in order to fix the issue 

          https://github.com/jenkinsci/maven-plugin/pull/191

          Samuel Gabriel added a comment - I created this pull request in order to fix the issue  https://github.com/jenkinsci/maven-plugin/pull/191

          Mark Waite added a comment -

          I've created a pull request that includes the changes from pull request 191 and several others and have confirmed that the problem reported in JENKINS-19396 is fixed by that change.

          The pull request generated an incremental build of the plugin on ci.jenkins.io that you can install on your controller to confirm the fix works. Please report your results from testing that pre-release build so that the plugin maintainers can see your results in addition to my results. They are much more likely to be persuaded to merge the pull requests when multiple users tell them that their issue is resolved by the change.

          Mark Waite added a comment - I've created a pull request that includes the changes from pull request 191 and several others and have confirmed that the problem reported in JENKINS-19396 is fixed by that change. The pull request generated an incremental build of the plugin on ci.jenkins.io that you can install on your controller to confirm the fix works. Please report your results from testing that pre-release build so that the plugin maintainers can see your results in addition to my results. They are much more likely to be persuaded to merge the pull requests when multiple users tell them that their issue is resolved by the change.

          Basil Crow added a comment -

          Fixed in jenkinsci/maven-plugin#323. Released in 3.24.

          Basil Crow added a comment - Fixed in jenkinsci/maven-plugin#323 . Released in 3.24 .

            sgabriel Samuel Gabriel
            gcummings Geoff Cummings
            Votes:
            34 Vote for this issue
            Watchers:
            44 Start watching this issue

              Created:
              Updated:
              Resolved: