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-58724] Update existing logger to display current run #562

Merged
merged 1 commit into from
Jul 30, 2019
Merged

[JENKINS-58724] Update existing logger to display current run #562

merged 1 commit into from
Jul 30, 2019

Conversation

mat1e
Copy link
Member

@mat1e mat1e commented Jul 30, 2019

@Vlatombe Vlatombe changed the title Update existing logger for JENKINS-58724 [JENKINS-58724] Update existing logger to display current run Jul 30, 2019
@Vlatombe Vlatombe added the enhancement Improvements label Jul 30, 2019
Copy link
Member

@Vlatombe Vlatombe left a comment

Choose a reason for hiding this comment

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

Looks reasonable

@Vlatombe Vlatombe merged commit d0d2d77 into jenkinsci:master Jul 30, 2019
@@ -47,12 +47,14 @@ public KubernetesComputer(KubernetesSlave slave) {
@Override
public void taskAccepted(Executor executor, Queue.Task task) {
super.taskAccepted(executor, task);
LOGGER.fine(" Computer " + this + " taskAccepted");
Queue.Executable exec = executor.getCurrentExecutable();
LOGGER.log(Level.FINE, " Computer " + this + " accepted task " + exec);
Copy link
Member

Choose a reason for hiding this comment

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

BTW sub-INFO logger calls should either use the Supplier overload or message formats

LOGGER.log(Level.FINE, " Computer {0} accepted task {1}", new Object[] {this, exec});

to avoid string concatenation when unused. Unlikely to matter much in this case.

Copy link
Member Author

@mat1e mat1e Jul 30, 2019

Choose a reason for hiding this comment

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

I opened PR 564 for this because it is already merged.

Copy link
Member

Choose a reason for hiding this comment

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

#564 that is. FYI: GitHub has nice handling (hover tips, backlinks) for several kinds of URLs when pasted directly into GH-flavored Markdown, but not when used in a Markdown link.

@mat1e mat1e mentioned this pull request Jul 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvements
Projects
None yet
3 participants