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-41795] Report event origins #79

Merged
merged 3 commits into from Feb 8, 2017

Conversation

stephenc
Copy link
Member

@stephenc stephenc commented Feb 7, 2017

Downstream of jenkinsci/scm-api-plugin#27

See JENKINS-41795

Reports the origin of events, the event logs will now look something like:

screen shot 2017-02-07 at 11 56 09

And the tooltip for a branch event will include the origin if known:

screen shot 2017-02-07 at 11 57 40

@reviewbybees

@KostyaSha
Copy link
Member

Exposing debug information to end users looks like overkill. Who cares about this IPs?

@@ -62,6 +64,10 @@ public Date getTimestamp() {
return new Date(timestamp);
}

public String getOrigin() {
Copy link
Member

Choose a reason for hiding this comment

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

@CheckForNull

Copy link
Member Author

Choose a reason for hiding this comment

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

@NonNull because the event will substitute ?

@@ -1 +1,2 @@
blurb=Branch event at {0,time} on {0,date}
origin=Origin: {0}
Copy link
Member

Choose a reason for hiding this comment

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

Will this show Origin: ? if the origin is unknown?

Copy link
Member Author

Choose a reason for hiding this comment

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

yes

@stephenc
Copy link
Member Author

stephenc commented Feb 7, 2017

@KostyaSha said:

Exposing debug information to end users looks like overkill. Who cares about this IPs?

When the user is trying to determine why they have strange extra builds being triggered the IP address of the origin of the requests is vital.

There is no value in hiding the information from users as it will be in the logs that anyone with Item/READ can access anyway, and we cannot hide the origin in the logs from non-admins (plus the origin is expected to normally be the SCM system - given that the SCM links will be pointing to that system, its IP address is not exactly top secret)

The origin is only available as a tool-tip so not exactly in your face either

@stephenc stephenc merged commit 4254434 into jenkinsci:master Feb 8, 2017
@stephenc stephenc deleted the jenkins-41795 branch February 8, 2017 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants