Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JENKINS-19396] Remove log file clutter from Linux agents started by Windows controllers #323

Merged
merged 6 commits into from
May 20, 2024

Conversation

MarkEWaite
Copy link
Contributor

@MarkEWaite MarkEWaite commented Apr 6, 2024

[JENKINS-19396] Remove log file clutter from Linux agents started by Windows controllers

A maven integration job that is started on a Linux agent by a Windows controller will clutter its output with "[pool-1-thread-4 for channel id=206]" messages that confuse warning parsers and distract users.

The problem does not occur when a Linux controller runs a job on either Windows or Linux.

The problem does not occur when a Windows controller runs a job on a Windows agent.

Original change was provided by @samgabriel in:

Includes other pull request as part of the plugin testing:

Testing done

No automated test added because the test failure mode requires a Windows controller and a Linux agent. We don't have infrastructure ready to support that type of cross-platform testing.

Tested on Windows controller with Windows agent and Linux agent and on a Linux controller with Windows agent and Linux agent.

Test configuration includes:

  • Java 21 controller with Java 21 agents on Windows and Linux
  • Two maven jobs, one on the Windows agent, one on the Linux agent
  • Confirmed that the job output is cluttered with "[pool-1-thread-4 for channel id=206]" with the released plugin when Windows controller uses a Linux agent
  • Confirmed that the job output is not cluttered with "[pool-1-thread-4 for channel id=206]" with the incremental build of this plugin when Windows controller uses a Linux agent
  • Confirmed that other job output in other configurations remains correct on Linux and Windows controller with Linux and Windows agents

Continued testing on my Jenkins configuration.

Submitter checklist

Preview Give feedback

dependabot bot and others added 5 commits August 1, 2022 06:05
Bumps [maven-reporting-api](https://github.com/apache/maven-reporting-api) from 3.0 to 3.1.1.
- [Release notes](https://github.com/apache/maven-reporting-api/releases)
- [Commits](apache/maven-reporting-api@maven-reporting-api-3.0...maven-reporting-api-3.1.1)

---
updated-dependencies:
- dependency-name: org.apache.maven.reporting:maven-reporting-api
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [org.codehaus.plexus:plexus-classworlds](https://github.com/codehaus-plexus/plexus-classworlds) from 2.6.0 to 2.7.0.
- [Release notes](https://github.com/codehaus-plexus/plexus-classworlds/releases)
- [Commits](codehaus-plexus/plexus-classworlds@plexus-classworlds-2.6.0...plexus-classworlds-2.7.0)

---
updated-dependencies:
- dependency-name: org.codehaus.plexus:plexus-classworlds
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
…aster/org.apache.maven.reporting-maven-reporting-api-3.1.1', 'dependabot/maven/master/org.codehaus.plexus-plexus-classworlds-2.7.0', 'deprecations' and 'patch-1' into octopus
@MarkEWaite MarkEWaite changed the title [JENKINS-19396] Use correct Linux PATH from Windows controller [JENKINS-19396] Remove log file clutter from Linux agents started by Windows controllers Apr 6, 2024
Comment on lines +152 to +155
protected final String getLoggingPath(MavenInstallation mvn){
return (getLauncher().isUnix()?":":";")+mvn.getHome()+"/conf/logging";
}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the key change in the pull request. Instead of using mvn.getHomeDir().getPath(), it uses mvn.getHome()

@MarkEWaite MarkEWaite marked this pull request as ready for review April 6, 2024 02:19
@mrothe
Copy link

mrothe commented Apr 8, 2024

I've tested the pre-release build (https://ci.jenkins.io/job/Plugins/job/maven-plugin/view/change-requests/job/PR-323/) resulting from this pull request in our environment (1 Windows controller, 2 Linux agents) and can confirm, that the job output is not cluttered with "[pool-1-thread- ... " anymore.

@jglick jglick requested a review from a team as a code owner May 20, 2024 11:27
@jglick jglick enabled auto-merge May 20, 2024 11:29
@jglick jglick merged commit be1706f into jenkinsci:master May 20, 2024
14 checks passed
@MarkEWaite MarkEWaite deleted the octopus branch May 20, 2024 13:03
@MarkEWaite
Copy link
Contributor Author

I think that this should be labeled "bug" so that it is categorized correctly in the changelog. It would also be fine if it were labeled as "maintenance" if that makes more sense to others.

@jglick jglick added the bug label May 20, 2024
@jglick
Copy link
Member

jglick commented May 20, 2024

This plugin does not have CD enabled and I am not intending to release anything. Maybe some other “maintainer” plans to, or maybe @MarkEWaite wants to be added.

@MarkEWaite
Copy link
Contributor Author

Thanks @jglick! I'm using the incremental build in my test environment. I don't feel a pressing need for a release of the plugin.

I'm willing to propose myself as a maintainer, though the other maintainers may hesitate to have my aggressive merging of dependency updates on this plugin. It has some special circumstances that make it more complicated than most plugins.

@jglick
Copy link
Member

jglick commented May 20, 2024

#182 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants