[#JRA-8718] Make CVS Timeout parameter settable by the user

JIRA

Make CVS Timeout parameter settable by the user

Created: 05/Dec/05 05:23 PM Updated: 22/Dec/05 06:19 PM

Component/s:

CVS integration

Affects Version/s:

None

Fix Version/s:

3.4.3

Time Tracking:

Not Specified

File Attachments:

CvsRepositoryUtilImpl.class (13 kB)
2.

CvsRepositoryUtilImpl_1.class (0.7 kB)
3.

CvsRepositoryUtilImpl_2.class (2 kB)
4.

CvsRepositoryUtilImpl_3.class (2 kB)

Participants:	Alan Berezin, Anton Mazkovoi [Atlassian], Brian Nguyen [OLD] and Nick Menere [Atlassian]
Since last comment:	2 years, 42 weeks ago
Resolution Date:	22/Dec/05 06:19 PM
Labels:

Description

« Hide

At the moment the cvs timeout is hardcoded into jira. This really should be a settable parameter when the CVS modules are created.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Brian Nguyen [OLD] added a comment - 12/Dec/05 04:16 PM

For those who are experiencing this problem with the timeout this patch will increase the timeout to 30 Minutes.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 12/Dec/05 04:21 PM

To install the patch please make a backup of the WEB-INF/classes/com/atlassian/jira/vcs/cvsimpl/CvsRepositoryUtil.class file under the JIRA web application and then replace it with the attached file.

If you are using JIRA standalone then restart JIRA. If you are using the EAR/WAR distribution of JIRA you will need to run 'build.sh clean' and then 'build.sh' to rebuild the web app (use build.bat on Windows instead of build.sh). Then redeploy the webapp.

[ Permlink | « Hide ]

Alan Berezin added a comment - 12/Dec/05 04:43 PM

Placed new class file in webapp and restarted jira. Then edited the cvs config on the screen to point to the new path I want. Moving the 69MB cvs log worked as expected (it took 9 min)

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 12/Dec/05 04:49 PM

Alan,

Thanks a lot for the update.

Anton

[ Permlink | « Hide ]

Alan Berezin added a comment - 12/Dec/05 05:53 PM

I spoke too soon. Allthough I did not get a timeout on the cvs page, and although the whole cvs file appears to have been generatated at the new location, when I go back to the CVS modules screen, it indicates that the log file that is pointed to is still the original source location. Furthermore, when I hit the Test link, I get a "lock cannot be obtained" error.

So, I guess it really isnt fixed. Sorry.

[ Permlink | « Hide ]

Brian Nguyen [OLD] added a comment - 20/Dec/05 09:38 PM

Apologies for this but I attached the incorrect files.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 21/Dec/05 04:34 AM

Please find the patches for JIRA 3.4.x that should increase the timeout to 40 minutes attached. To install the patches:

If you are using JIRA Standalone please do the following:

Download all 4 attached files
Rename CvsRepositoryUtilImpl_1.class to CvsRepositoryUtilImpl$1.class
Rename CvsRepositoryUtilImpl_2.class to CvsRepositoryUtilImpl$2.class
Rename CvsRepositoryUtilImpl_3.class to CvsRepositoryUtilImpl$3.class
Copy the 4 files to <jira_install_dir>/atlassian-jira/WEB-INF/classes/com/atlassian/jira/vcs/cvsimpl/ overwriting the files there
Restart JIRA

If you are using the WAR distribution of JIRA:

Download all 4 attached files
Rename CvsRepositoryUtilImpl_1.class to CvsRepositoryUtilImpl$1.class
Rename CvsRepositoryUtilImpl_2.class to CvsRepositoryUtilImpl$2.class
Rename CvsRepositoryUtilImpl_3.class to CvsRepositoryUtilImpl$3.class
Copy the 4 files to <jira_install_dir>/webapp/WEB-INF/classes/com/atlassian/jira/vcs/cvsimpl/ overwriting the files there
Run 'build.sh clean' on unix or 'build.bat clean' on windows
Run 'build.sh' on unix or 'build.bat' on windows
Redeploy the JIRA web app into your application server
Restart the application server

[ Permlink | « Hide ]

Nick Menere [Atlassian] added a comment - 22/Dec/05 06:19 PM

As of 3.4.3, the CVS timeout is settable on a per module basis.