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

Adapt git browsers for Jetty 12 EE 9 transition #1620

Merged

Conversation

MarkEWaite
Copy link
Contributor

Adapt git browsers for Jetty 12 EE 9 transition

No need to throw ServletException when checking for URL validity. IOException is sufficient and avoids including Jakarta EE in the method signature.

Testing done

  • Confirmed that AssemblaWeb still reports the expected message when an invalid URL is provided and that it reports no message when a valid URL is provided. Confirmed that Assembla has changed URLs and broken the browsing links that previously worked. Separate bug report
  • Confirmed that GitBlit browsing works as expected by installing a GitBlit server. https://hub.docker.com/r/gitblit/gitblit
  • Confirmed that ViewGit browser provides change links as expected. Confirmed that the ViewGit URL check logic no longer works on the site used as an example. Now reports that https://repo.or.cz/ does not look like a ViewGit site. Separate bug report

Did not check Gitiles because the Gitiles source repository is archived on GitHub at https://github.com/google/gitiles . No further development is expected.

Did not check TFS2013 because I have no idea where to find a Team Foundation Server 2013 installation.

Did not check Fisheye because I could not find a Fisheye server on the public internet.

Resolves one of the changes needed for Jetty 12 EE 9. More changes are noted in:

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests - that demonstrates feature works or fixes the issue

No need to throw ServletException when checking for URL validity.
IOException is sufficient and avoids including Jakarta EE in the method
signature.

Testing done:

* Confirmed that AssemblaWeb still reports the expected message when an
  invalid URL is provided and that it reports no message when a valid
  URL is provided.  Confirmed that Assembla has changed URLs and broken
  the browsing links that previously worked. Separate bug report

* Confirmed that GitBlit browsing works as expected by installing a
  GitBlit server. https://hub.docker.com/r/gitblit/gitblit

* Confirmed that ViewGit browser provides change links as expected.
  Confirmed that the ViewGit URL check logic no longer works on the
  site used as an example.  Now reports that https://repo.or.cz/ does
  not look like a ViewGit site. Separate bug report

Did not check Gitiles because the Gitiles source repository is archived
on GitHub at https://github.com/google/gitiles .  No further development
is expected.

Did not check TFS2013 because I have no idea where to find a Team
Foundation Server 2013 installation.

Did not check Fisheye because I could not find a Fisheye server on the
public internet.
@MarkEWaite MarkEWaite requested a review from a team as a code owner August 3, 2024 13:10
@MarkEWaite MarkEWaite added the chore Reduces maintenance effort by changes not directly visible to users label Aug 3, 2024
@MarkEWaite MarkEWaite enabled auto-merge (squash) August 3, 2024 13:12
@MarkEWaite MarkEWaite merged commit 1c84367 into jenkinsci:master Aug 3, 2024
17 checks passed
@MarkEWaite MarkEWaite deleted the stop-throwing-servlet-exception branch August 3, 2024 13:55
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Reduces maintenance effort by changes not directly visible to users
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant