integration?This might be possible, but has not been tested.
Some versions of linux seem to have problems connecting to JIRA when it is on the same machine. This is simple to resolve though, instead of setting the jira_server option to localhost:8080 in your config file, simply set it to your to your machines fully qualified domain name, for example jira-server:8080 (port will vary dependant upon your JIRA install). This will fix the problem.
The diagrams in the user guide illustrates a number of components, some of which are included in a project, others which are not. As of revision UCM4SVN Rev 1.3a managing Read/Write aspect is achieved using Subversion/Apache permission handling.
We are currently looking to supporting sub-components after revision 1.3a, which would make this feature potentially possible in the future.
Because each activity is self contained on a branch, all the changes for the activity will be related to that branch. You can use svn log on the Activity branch that's in a Component to see all the changes. (If you are are using an issue tracker such as JIRA, you can also install our JIRA2SVN product to record the change set).
New UCM4SVN baselines are created/set via the Component editor tab. The default is to use the HEAD revision however any SVN revision number can be defined as a 'Stable' point for the activity branching to stem from. See the UCM4SVN User Guide.
In newer versions of firefox they have disabled the ability to copy to clipboard. To get around this, you will need to change some user preferences. In your address bar type "about:config"
In there change the following options to true.
signed.applets.codebase_principal_support
You require a valid user account and a password to access UCM4SVN. Anonymous access is not allowed.
Depending on the user type, authentication occurs against one of the following:-
At this moment in time, UCM4SVN does not support access via HTTPS.
This should be possible using an ssl tunnel, but has not been tested.
We support access to JIRA via HTTPS, so it is already possible to use a secure SSL connection to access your JIRA server.
For ClearQuest, UCM4SVN uses ClearQuest's CQPerl API. With remote ClearQuest repositories (i.e. installations where the UCM4SVN server does not live on the ClearQuest server) the level of security depends on your database connector configuration and, of course, the capabilities of your DBMS.
The Subversion repository is accessed via the svn command line. Whilst we do not specifically test with Subversion via HTTPS, you should be able to secure access to Subversion by using a https://... URL for your components in UCM4SVN.
Please note that with self-signed server certificates, Subversion will normally prompt you to accept the untrusted certificate.
For self-signed certificates to be usable with UCM4SVN, you need to log in to the UCM4SVN server host and permanently accept the certificate as the user used for running the UCM4SVN server.
Login is as the UCM4SVN user and perform a simple operation on the HTTPS URL, e.g.:-
svn ls https://svn.mycompany.com:5544/svn/myrepos
You will then be prompted with the following message:-
Error validating server certificate for 'https://svn.mycompany.com:5544': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: svn.mycompay.com - Valid: from Mon, 01 Jun 2009 09:46:02 GMT until Tue, 01 Jun 2010 09:46:02 GMT - Issuer: SomeOrganizationalUnit, SomeOrganization, SomeCity, SomeState, -- - Fingerprint: 92:4f:93:9f:4b:a7:a3:da:88:b0:c7:e2:6e:06:ac:43:1c:06:08:4b (R)eject, accept (t)emporarily or accept (p)ermanently? p
Please select "p" to permanently accept the certificate.
If security is a priority, we recommend that a dedicated user account is used for the UCM4SVN server and that suitable permissions are applied to the UCM4SVN workspace directory, the database and configuration files in particular, which will minimise the risk of unauthorised access. For added security, a dedicated machine with limited user access can be used as the UCM4SVN server.
On login via the API, with the user's user name and password, a dedicated token is provided to secure access to API functions. All API functions require a valid login token; anonymous access is not allowed. Note that login tokens expire after ten minutes of inactivity.
UCM4SVN can integrate with the ReviewBoard code-review management system. Please note that at this point UCM4SVN requires ReviewBoard 1.5 beta.
Note that UCM4SVN does not work with ReviewBoard 1.0, and there are no plans to support this release. ReviewBoard 1.0 does not provide the functionality required for a good integration with UCM4SVN.
Whilst we do not specifically test with 64-bit operating systems, most Clearvision products will run on most 64-bit variants of the supported operating systems.
On Vista and Windows 7 64-bit, you should be able to start the product normally.
On 64-bit Linux distributions such as Ubuntu or Debian, you will need to install the ia32-libs package, which installs a basic set of 32-bit libraries, allowing you to run Clearvision products. A similar procedure is required for Redhat Enterprise and Fedora.