PVCS SCM

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID pvcs_scm Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
1.1
Jul 21, 2010
1.324
Source Code
Issue Tracking
Maintainer(s)
Subversion
Open Issues
Brian Lalor (id: blalor)
Usage Installations 2013-Apr 47
2013-May 35
2013-Jun 34
2013-Jul 41
2013-Aug 33
2013-Sep 42
2013-Oct 38
2013-Nov 38
2013-Dec 39
2014-Jan 48
2014-Feb 44
2014-Mar 41

This plugin provides integration with Serena's PVCS Version Manager SCM.

Configuring

Configuration of the PVCS plugin should be fairly straightforward, but my experience with PVCS is that nothing about PVCS is straightforward, simple, or in line with how other SCM systems work. This plugin was developed around the PCLI command-line tool, and I basically had to bludgeon that utility into submission....

System-level config

Specify the path to the pcli executable, or just use "pcli" if it is in the environment path of the user running Jenkins.

Basic config

Project root

Specify the root of your project in this field. It is the path used by all PVCS clients (including the desktop GUI) to access your source.

Archive root

This is the path to the actual archive files on the PVCS server's filesystem. This is required to determine which files were changed from build to build; you can go back and set this later, if you need to, without modifying your builds.

Changelog prefix fudge

This is prefixed to the archive path of a file when determining the changes made to a build, after the "Archive root" (above) has been stripped off.

Module

This is the path to the directory which will be recursively retrieved from the project root. It must start with a leading "/".

So, to tie it all together, let's say the top-level pom.xml for your Maven project is at /2008_10/myProject/pom.xml, with a PVCS project root of //repository/PVCS/October_Release. The archive files are stored on the PVCS server's filesystem at //repository/pvcs/repository/TRUNK, so /2008_10/myProject/pom.xml actually resides at //repository/pvcs/repository/TRUNK/myProject/pom.xml.

You would specify:

  • the project root as //repository/PVCS/October_Release
  • the archive root as //repository/pvcs/repository/TRUNK/myProject/pom.xml
  • changelog prefix fudge as 2008_10/
  • module as /2008_10/myProject

Advanced config

Since PVCS is too brain-dead to tell you when a file is deleted, it is best to leave this box checked so that all checked-out files will be deleted before a build is started. This ensures that your workspace accurately reflects the current state of the repository.

Change Log

Version 1.1 (Jul 21, 2010)
  • Add ability to provide loginid, pvcs workspace, promotion group, version label while generating the pcli command
  • Fix help links
  • Updated code for more recent Hudson
Version 1.0 (Nov 5, 2008)
  • Initial release

Labels

Edit
plugin-scm plugin-scm Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Add Comment