Skip to content

Repository session was not closed for unexpected exceptions#190

Merged
oleg-nenashev merged 2 commits intojenkinsci:masterfrom
hakanai:patch-1
Dec 12, 2017
Merged

Repository session was not closed for unexpected exceptions#190
oleg-nenashev merged 2 commits intojenkinsci:masterfrom
hakanai:patch-1

Conversation

@hakanai
Copy link
Copy Markdown
Contributor

@hakanai hakanai commented Jun 25, 2017

Previous code caught two specific checked exceptions and closed the repository session only for those. But RuntimeException could occur as well, so the new pattern will work in all cases where success did not occur.

Previous code caught two specific checked exceptions and closed the repository session only for those. But RuntimeException could occur as well, so the new pattern will work in all cases where success did not occur.
@hakanai
Copy link
Copy Markdown
Contributor Author

hakanai commented Jun 25, 2017

A bit of background here is that we're seeing Jenkins keeping SVN repositories locked, but in a non-reproducible way which prevents us opening an issue for it. I found this in a quick audit of the code for improper resource handling. It may not be the issue, but it's at least an issue. I should probably check SVNKit itself too.

The one problem with editing in GitHub itself is that you can't check before committing. ;)
Copy link
Copy Markdown
Member

@oleg-nenashev oleg-nenashev left a comment

Choose a reason for hiding this comment

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

Looks good to me, IIRC there is a similar change in the proposed PRs

@oleg-nenashev
Copy link
Copy Markdown
Member

Retriggered CI

@oleg-nenashev oleg-nenashev merged commit c486ec8 into jenkinsci:master Dec 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants