This plugin allows you to use AccuRev as a SCM.
First things first - install the plugin, either through the Jenkins plugin administration, or manually.
Select Manage Jenkins from the main menu, then select Configure System from the options presented:
If the plugin was installed properly, you should find a section on this page for AccuRev which looks like this:
Click Add to add a new server definition:
Fill in the each of the settings:
Hitting the Advanced... button reveals three more options:
Now scroll to the bottom of the page and make sure you hit the Save button, otherwise your changes will not take.
Once the server settings are configured, new builds can choose it for pulling down code. Create a new build, give it a job name, and select the type of build (free-style, maven2, etc) and click OK. On the subsequent screen, you'll see a section called Source Code Management where you can select AccuRev. Select AccuRev, and the following options will appear:
You should see the server entry you created in the Server drop-down, and it is likely selected by default. Select it if it is not. Then enter in the names of the Depot and Stream you wish to build.
There are three advanced options at the job level. The inline help provides detailed information on these, so take advantage of them for detailed information. Here is a summary:
If you decide to stop using a workspace after having done a build, you must manually go into accurev and move the workspace directory so that it does not point at the jenkin's workspace location.
The following options are only valid when you are using a workspace:
this option is primarily useful in cases where you are using an accurev workspace and when performing a build on that workspace would cause artifacts to overlap in the parent stream. If you keep getting warnings and failed builds due to overlaps, and you don't want to purge the entire workspace on each build then you need this option.
There are a couple of important things to know about using AccuRev workspaces with this plugin. The first is that, even though you are using a workspace, the plugin will purge and repopulate the workspace whenever there is a failed build. Also, sometimes Hudson will trigger a build when no files have changed in the backing stream. These are due to limitations / issues with the AccuRev CLI (at least, the 4.5.* versions).
Skip to end of metadata Go to start of metadata