Vote #68433
完了Resolving issues with the commit message produces the wrong comment with CVS
0%
説明
The comment redmine automatically closes the issue with will say something like 'Applied in changeset r_4.' instead of the actual changeset number.
journals
You mean there's a "_" in the message that shouldn't be here ? And can you test if it's still the case in 1.0.x versions ?
--------------------------------------------------------------------------------
Sorry, I should of clarified that -- no. Our actual revision numbers are in the thousands, but the numbers in the update message are always small. It looks like they are maybe temporary revisions used to group the CVS file changes into one changeset. I've also noticed that if I refresh the activity page while redmine is polling the respository the same 'changeset r_4' messages will appear. If I refresh after it is done they end up as real changeset numbers e.g. r9779.
I can't easily check the 1.0.x versions without upgrading our server.
--------------------------------------------------------------------------------
I confirmed svn trunk has this problem.
I attach an image.
The reason is following.
# cvs adapter creates changeset with temporary revison "_X" at source:tags/1.0.3/app/models/repository/cvs.rb#L121
# Changeset.after_create() is called and new journal is added at source:tags/1.0.3/app/models/changeset.rb#L76
# cvs adapter changes revisons "_X" to "Y" at source:tags/1.0.3/app/models/repository/cvs.rb#L148
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
To fix this issue, I generate pseudo scmid "branch_name-YYYYMMDD-HHMMSS".
Redmine generates pseudo revision number, and using this number for auto close issue text is very difficult.
Redmine supports scmid of Git, Mercurial, Bazaar and Darcs.
Redmine supports "commit:scmid" in wiki. You can use first some letters of scmid.
For example, "commit:branch_name-YYYYMMDD-HHMM".
--------------------------------------------------------------------------------
related_issues
relates,Closed,996,CVS view ends up with "duplicate key violates unique constraint" after 0.7.0RC1 update