jenkinsci / jenkinsci/subversion-plugin

[JENKINS-10945] Latest changes should include merged revisions (like svn log -g)

Open
#838 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component:subversion-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
131
Forks
275
Avg merge
12h 4m
Merged PRs (30d)
6

Description

If one of the changes included in a Jenkins build was a merge, the actual commit message of that merge is often not very useful. Sometimes one would like to see all the commit messages for the revisions that were included in that merge. This is the purpose of the -g switch of svn log.

It would be handy if that information was recorded in the job's list of changes.


Originally reported by hendrik, imported from: Latest changes should include merged revisions (like svn log -g)
  • status: Open
  • priority: Minor
  • component(s): subversion-plugin
  • resolution: Unresolved
  • votes: 2
  • watchers: 1
  • imported: 20251212-090250
Raw content of original issue

If one of the changes included in a Jenkins build was a merge, the actual commit message of that merge is often not very useful. Sometimes one would like to see all the commit messages for the revisions that were included in that merge. This is the purpose of the -g switch of svn log.

It would be handy if that information was recorded in the job's list of changes.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by tracing how the subversion-plugin records revisions in a Jenkins job's change list, then determine how SVN merged revisions could be represented. Done means builds involving merges expose the included revisions' commit messages, as requested by the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.