View Issue Details

IDProjectCategoryView StatusLast Update
0025228mantisbtdocumentationpublic2019-01-17 09:32
Reporterthennerich Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status confirmedResolutionopen 
Product Version2.18.0 
Target VersionFixed in Version 
Summary0025228: CVS integration not working anymore
Description

Hello,

we have a customer who is working with mantis for over 10 years now. We are updating mantis from version 1.2.11 to 2.18.0 at the moment. Everything is working good so far, except the CVS integration which is not working anymore.

The documentation of mantis seems to be a little outdated:

The newest entries which I (and google) can find is https://mantisbt.org/blog/archives/mantisbt/8 and http://www.mantisbt.org/wiki/doku.php/mantisbt:faq :

Does MantisBT integrate with CVS?

Yes. See the following resources:

Manual page for source control integration (http://www.mantisbt.org/manual/manual.configuration.source.control.integration.php)
ScmBug Project (http://freshmeat.net/projects/scmbug/)

Both links are dead.

There exists a new plugin for source integration https://github.com/mantisbt-plugins/source-integration which is supporting GIT, Subversion and Mercurial, but not CVS.

Is there any chance to integrate the commit messages from CVS to Mantis v2.x again?

TagsNo tags attached.

Activities

atrol

atrol

2019-01-15 08:25

developer   ~0061242

Last edited: 2019-01-15 08:26

View 2 revisions

Built-in source code integration support has been removed starting from version 1.3.0., see https://mantisbt.org/blog/archives/mantisbt/440
Reintroducing support in Mantis core will hardly happen, as starting from 1.2.x, using the source control integration plugin was the recommended method.

The best way in long term would be to implement it as enhancement of the plugin.
The first step would be to create a ticket at https://github.com/mantisbt-plugins/source-integration/issues
I don't expect that someone will start implementing it (you never know), as CVS is dead since more than 10 years https://savannah.nongnu.org/projects/cvs so the second step would be to create a fork of the plugin and send a pull request with the changes.

While more thinking about it, I don't even know if extending the plugin is a good idea.
Implement something new (and maintain it!) to support something dead.
Wouldn't it be better to invest time in migrating CVS to Git or Mercurial?

thennerich

thennerich

2019-01-15 09:20

reporter   ~0061243

Thank you for your reply and the pointers how to proceed. I think you are right: It would be better to migrate to a newer version-control system. On the other hand it can be quite costly (or even impossible) to migrate legacy source code with a legacy development environment (running on a legacy system for legacy customers) to a state of the art environment...

Never the less: The blog entry mentioned before (first hit on google: https://www.google.de/search?q=mantisbt+cvs) has a date of July 2007, so everyone can see, that this is quite old.

The FAQ (last changed 2014) is another story. Wouldn't it be a good idea to update the FAQ or (at least) mark the complete FAQ as outdated?

For that reason I put that ticket to category "documentation"...

atrol

atrol

2019-01-15 09:47

developer   ~0061244

Last edited: 2019-01-15 09:48

View 2 revisions

Wouldn't it be a good idea to update the FAQ or (at least) mark the complete FAQ as outdated?

Right.
There is no clear decision at the moment, if the Wiki will be completely removed or updated and/or replaced by another type of documenation.
As a first step, I added a hint at the top of the page and removed the broken CVS links

atrol

atrol

2019-01-15 09:52

developer   ~0061245

migrate legacy source code with a legacy development environment (running on a legacy system for legacy customers) to a state of the art environment...

In this case I would keep Mantis 1.2.x, but update to latest 1.2.20 in case you are interested in having fixed at least some security related bugs.
If security is important for you, even 1.2.20 can't be recommended.

thennerich

thennerich

2019-01-15 10:04

reporter   ~0061246

Thank you for the updated FAQ, much better now.

May I point you to another outdated page: https://mantisbt.org/wiki/doku.php/mantisbt:features?s[]=cvs

atrol

atrol

2019-01-15 10:11

developer   ~0061247

May I point you to another outdated page

Thanks for the pointer, but I think there is no need to start a list of outdated pages.
I expect it could become a quite long one :-)

Issue History

Date Modified Username Field Change
2019-01-15 07:54 thennerich New Issue
2019-01-15 08:25 atrol Status new => feedback
2019-01-15 08:25 atrol Note Added: 0061242
2019-01-15 08:26 atrol Note Edited: 0061242 View Revisions
2019-01-15 09:20 thennerich Note Added: 0061243
2019-01-15 09:20 thennerich Status feedback => new
2019-01-15 09:47 atrol Note Added: 0061244
2019-01-15 09:47 atrol Status new => confirmed
2019-01-15 09:48 atrol Note Edited: 0061244 View Revisions
2019-01-15 09:52 atrol Note Added: 0061245
2019-01-15 10:04 thennerich Note Added: 0061246
2019-01-15 10:11 atrol Note Added: 0061247