ClearCase Plugin

Integrates Hudson with ClearCase.

Plugin Information

Plugin ID clearcase
Latest Release 1.3.5
Latest Release Date Jan 05, 2011
Plugin Central Plugin Central 3.2
Sources Github
Support Eclipse Hudson Forum
Issue Tracking Eclipse Bugzilla
Hudson Core (latest) 3.3.0
1.0 and Later Configuration Incompatible With Earlier Versions

Please note that version 1.0 and later of the ClearCase plugin is not configuration-compatible with earlier versions. Projects using base ClearCase will need to be reconfigured, with load rules removed from the config spec and specified separately in the new Load Rules field. This needs to be done for all base ClearCase projects, including those using dynamic views.

With this plugin you can use either base ClearCase and UCM ClearCase as the SCM for Hudson projects. The plugin uses the cleartool executable to work with a ClearCase server - this requires that the cleartool command (and therefore the full ClearCase client) be installed on master and all slaves on which you wish to run ClearCase jobs. The SCM also supports polling, so it can start a build when changes are detected on the branch or stream specified in the job configuration.

Usage

Global configuration

  • Set up the cleartool executable in the Hudson configuration. To verify that the executable can be used by Hudson press the "Check cleartool version"

Base ClearCase

Basic configuration

  • Set the name of the view that will be used by ClearCase. The view name has to be unique in the ClearCase region the master/slaves are using.
  • Set the config spec that should be used. This should not contain any load rules.
  • Specify one or more load rules - this is required, even with a dynamic view. The load rules are used both for determining the contents of snapshot views and for constructing the "cleartool lshistory" command used for polling and generating changelogs.
    • Load rules should be separated by newlines.
    • Load rules should be a path to a file or directory within the view, i.e., "vob/some_vob" or "\some_other_vob\directory". The path can have a leading file separator, or not. You can also have load rules starting with "load", as you would in a snapshot config spec outside of Hudson - the "load " will be removed and the path will be processed as normal.
  • Check "Use update" if you wish to use the same view for every build - this will greatly speed up your builds, since the view won't be recreated and repopulated every build, but build output will be left in the view.
    • This option is only applicable to snapshot views. Dynamic views are not removed and recreated.
  • Specify one or more branches - these branches will be used for polling for changes and assembling changelogs.
Advanced configuration

  • Click the "Advanced" button to reveal the advanced options, including the dynamic view options.
  • Excluded regions
    • Optionally, specify one or more regular expressions representing files or directories which you wish to ignore when polling and generating changelogs. In this example, any changes to a file named "version.properties" or "Version.properties" anywhere in the source tree will be ignored.
  • Additional mkview arguments
    • If you need to pass additional arguments to "cleartool mkview", such as -gpath, -hpath, -server, etc, do that here. You can refer to the workspace the view will be under as $WORKSPACE, and the view name as $CLEARCASE_VIEWNAME. These will be replaced before being passed to "cleartool mkview".
  • Filter destroy sub-branch events
    • If selected, "destroy sub-branch" events, which are generally the result of removing a version 0 of a file, will be ignored in polling.
  • Remove ClearCase view on rename
    • If selected, the view will be removed, via "cleartool rmview", if the job is renamed, since the workspace directory will change and the existing view will no longer be valid.
  • Multi-site poll buffer
    • Optionally, if you wish to have polling check for changes since the last build plus an additional period of time, in case of changes made at another site before the build which had not yet been synced to the build site by build time, enter that buffer period here, in minutes.
Dynamic view configuration

  • Optionally, you can use an existing dynamic view, rather than a new snapshot view. To do so, check "Use dynamic view" under the advanced options.
  • View root
    • Required for dynamic view use - this is the directory or drive under which dynamic views live. On Unix, this is generally "/view", while on Windows, it's generally "M:\".
  • Do Not Reset Config Spec
    • If selected, the dynamic view's config spec won't be changed, regardless of whether it matches the config spec specified in the job configuration.

UCM ClearCase

  • To be documented

Frequently asked questions

Are the view attributes available in the build scripts?

There are three environment variables set after checkout :

  • CLEARCASE_VIEWNAME : The path of the view relative to the workspace
  • CLEARCASE_VIEWPATH : The absolute path of the view
  • CLEARCASE_VIEWTAG : The view tag

Can the view name be updated with the name of the job ?

Yes, it is possible to add ${USER_NAME}, ${NODE_NAME} and ${JOB_NAME} in a view name which are replaced with the name of the user, node and job.

Error when creating view (storage directory must be in UNC style)

Jamie Burrell solved it by doing the following at the command line of the machine on which Hudson runs. Note that the view name need not be the one you are using for Hudson. It needn't ever be used. I also had trouble using localhost, and needed to use my machine name.:

cleartool mkstgloc -view mystgloc \\<host>\<shared folder>\<view name>.vws

The above solution did work but it sets the view storage location globally for everyone in the same region. A better solution may be:
(under the "Advanced" button in the "Additional mkview arguments" field):

-vws \\<host>\<shared folder>\<view name>.vws




Error when retrieving history (Error: Not an object in a vob: "vobs")

On Linux and Solaris there are sometimes problems retrieving the ClearCase history using lshistory. In the Advanced section in the configuration it is possible to specify one or several paths in the VOB path(s) field that will be used when retrieving the history. If the config spec contains "vobs/gtx2" then the VOB path(s) field should be set to gtx2. (Mail thread, issue #1053)

Todo list

  • Add documentation on how to install a build trigger on a Clear case server
  • UCM: Add ability to perform difference report between any two builds using baseline

Changelog

Trunk

Version 1.3.5 (January 5th 2011)

  • Improvement : Enabled tracking changes on a label (thanks raspy) issue #7218
  • Bug fix : NPE when job started while delivery in progress issue #8230
  • Disabling changelog for rebases as it consumes too much memory/time. (no JIRA issue)
  • Remove dependency to deprecated method in core (this method will be removed in a future core release)

Version 1.3.4 : Skipped because of release problems, see 1.3.5

Version 1.3.3 (November 9th 2010)

  • Bug fix : Fails to resolve build properties in IVY. This depends on Hudson core 1.382 to actually work (although the plugin doesn't require 1.382 minimum)
  • First version released from Github (https://github.com/hudson/hudson-clearcase-plugin). If you want to contribute patches, this is the best way to do it !

Version 1.3.2 (October 28th 2010)

Error formatting macro: jiraissues: java.lang.RuntimeException: Not Found

Version 1.3.1

  • Released August 4th 2010
  • Bug fix : The parsing of "baselines desc" command fails when cleartool error occured (issue #7015)
  • Bug fix : clearcase plugin attempts and fails to remove view on job deletion (issue #6729)
  • Bug fix : Lost of Clearcase configuration during maven site (issue #7027)
  • Bug fix : Multiple pvobs in project config not supported now (issue #7014)
  • Bug fix : Polling not working anymore with Clearcase Base (issue #6999)
  • Bug fix : When a view tag exists but the view path has been deleted, the view cannot be created.
    Workaround is to execute 'cleartool rmview -force -tag <viewtag>' and relaunch the build

Version 1.3

  • Released July 13th 2010
  • Information : This new version stores additional information about the SCM state. As such, when upgrading, a new run of your jobs triggered on SCM polling will be launched in order to record config spec (for Base Clearcase) or foundation baselines (UCM)
  • New feature : Load rules should be derived from stream foundation - not typed in by user (issue #5898)
  • New feature: UCM : Implement SCM new polling logic to support rebases better (issue #6705)
  • Improvement: Allowing view path not to be the same as view tag (issue #6227)
  • Bug fix (Regression) : Load rules containing spaces not handled properly (issue #4443)
  • Bug fix : Job failure after changing clearcase load rules (issue #6591)
  • Bug fix : ClearCase error after user canceled previous update (issue #6702)
  • Bug fix : cleartool rmview -tag is not supported by Clearcase LT (issue #6806)
  • Bug fix : Recent Changes are not accurate with Clearcase UCM (issue #3538, fixed by issue #6705)
  • Bug fix : Clearcase polling can take a huge amount of time (issue #5255, fixed by issue #6705)
  • Bug fix : Lshistory polling/changelog misses certain file changes during rebase. (issue #1717, fixed by issue #6705)

Version 1.2.1

  • Released June 5th 2010
  • Bug fix: Allow variables to be parsed in configspec field (issue #5568)
  • Bug fix: Job failure after changing clearcase load rules (issue #6591)
  • Bug fix: Newly created development stream cannot be built (issue #1719)
  • Bug fix: ClearCase error after user canceled previous update (issue #6702)

Version 1.2

  • Released May 5th 2010
  • Bug fix: If load rules ended with slash or backslash, no checkins would ever be registered as valid changes. (issue #5342)
  • Bug fix: Handle variable replacement in view name properly during job deletion or renaming. (issue #5364)
  • Bug fix: Removing existing snapshot views often fails. (issue #5574)
  • Bug fix: Use 'cleartool setcs -current' instead of 'cleartool update' (reopened) (issue #4569)
  • RFE: add ClearCase report. Shows ClearCase related information: for builds running with base ClearCase configuration show the the CSPEC that was used. For builds running with UCM ClearCase show the stream and baselines that were used (baselines will be shown only if CodeFreeze option was selected in the UCM ClearCase configuration).
  • RFE: UCM - Implement code freeze for dynamic view. This includes adding new workflow for UCM checkout: create build stream as a child of the configured stream and use that stream for building.
  • RFE: UCM - Implement clean build for dynamic view. This is implemented by removing and recreating the view on each build.
  • RFE: UCM - support overriding the configured stream by STREAM parameter.
  • RFE: UCM - support running concurrent builds on different streams. Implemented by dynamically allocating view name.
  • RFE: Better handling of job renaming/deletion and behaviour regarding custom workspace
  • RFE: Plugin will be more resilient in case of existing view tag or view path in the way. Instead of failing, it will remove the view tag and/or rename the view path.

Older versions

Please see Release Notes Archives.

Labels:

plugin-scm plugin-scm Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.
  1. Nov 22, 2007

    Anonymous says:

    Hi, I only started using Hudson yesterday, and I love it. Even though my proj...

    Hi,
    I only started using Hudson yesterday, and I love it. Even though my project isn't using CI, I can, quickly and easily. I have found an omission from your directions though.
    We usually use dynamic CC views. That means we don't have a view storage location setup by default. I then had problems with your plugin running and needing a view storage location.
    For the edification of others, the error I got was :

    started
    [workspace] $ cleartool mkview -snapshot <my view name>
    cleartool: Error: storage directory must be in UNC style (e.g. \\host\share\...)
    FATAL: Clear Case failed. exit code=1
    FATAL: Clear tool did not return the expected exit code. Command line="cleartool mkview -snapshot <my view name>", actual exit code=1
    java.io.IOException: Clear tool did not return the expected exit code. Command line="cleartool mkview -snapshot siml_tsa_autobuild_view", actual exit code=1
    	at hudson.plugins.clearcase.ClearCaseSCM.run(ClearCaseSCM.java:272)
    	at hudson.plugins.clearcase.ClearCaseSCM.createView(ClearCaseSCM.java:175)
    	at hudson.plugins.clearcase.ClearCaseSCM.checkout(ClearCaseSCM.java:108)
    	at hudson.model.AbstractProject.checkout(AbstractProject.java:541)
    	at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:223)
    	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:189)
    	at hudson.model.Run.run(Run.java:649)
    	at hudson.model.Build.run(Build.java:102)
    	at hudson.model.ResourceController.execute(ResourceController.java:70)
    	at hudson.model.Executor.run(Executor.java:62)
    

    I solved it by doing the following at the command line of the machine on which Hudson runs:

    cleartool mkstgloc -view mystgloc \\<host>\<shared folder>\<view name>.vws
    

    Note that the view name need not be the one you are using for Hudson. It needn't ever be used. I also had trouble using
    localhost
    , and needed to use my machine name.

    If that is successful, next time you run the build, it should work.

  2. Nov 22, 2007

    Jamie Burrell says:

    Sorry - the above was by me. Forgot I hadn't logged in. Jamie

    Sorry - the above was by me. Forgot I hadn't logged in.

    Jamie

  3. Dec 11, 2007

    Anonymous says:

    Hello folks, Before bombarding you with questions about ClearCase support, I wa...

    Hello folks,

    Before bombarding you with questions about ClearCase support, I wanted to ask about the 'readiness' of Hudson for prime time use with ClearCase. Success stories?

    Cheers,

    Mike T

  4. Dec 12, 2007

    Jamie Burrell says:

    Mike, I'd completely recommend Hudson and ClearCase. I'm using CC6/Maven2, wit...

    Mike,

    I'd completely recommend Hudson and ClearCase. I'm using CC6/Maven2, with a VOB that contains multiple projects, like so:

    vobs
      +-programme
          +-subprogramme
              +-project1
              +-project2
              +- ...
    

    Thanks to Erik's help (the original version I downloaded was missing some required features), I have each of these running as individual builds, with no problems (at least not with ClearCase or Hudson). Bear in mind this is in an Investment Bank on a mission-critical project costing millions of dollars.
    Erik is very helpful, highly responsive and the turnaround is pretty high. I can't vouch for the usability of the dynamic views (not having used that side of things), but the rest of it seems top notch.

    Jamie

  5. Dec 20, 2007

    Anonymous says:

    Any plans to add UCM support?  I -think- this would boil down to th...

    Any plans to add UCM support?  I -think- this would boil down to the following additions/changes:

    - Create views with stream name instead of a specific config spec (config spec is derived from stream configuration); modify UI to take a stream name instead of a config spec

    - Report contributing activities (UCM tasks) in revision log for builds

    - Allow builds to be triggered based on changes to latest code, latest baselines, or both (also allow user to specify which components to monitor for changes to streamline these checks)

  6. Dec 21, 2007

    Erik Ramfelt says:

    Please use the available mailing lists for requesting features and asking questi...

    Please use the available mailing lists for requesting features and asking questions about the plugin as this wiki is not being actively monitored.

  7. Nov 06, 2008

    Jeffrey Cameron says:

    I have recently tried to use this plugin and it works pretty well for me.  ...

    I have recently tried to use this plugin and it works pretty well for me.  I did notice two issues though:

     1. There is no way to supply credentials.  If you are using Hudson as a service running under the LocalService account on Windows then it's almost impossible to create a view on a ClearCase server elsewhere on the network.  Would it be possible to add support to allow the plugin to impersonate another user whose credentials are authorised to access the server?

     2. When I have found that the better option in UCM for Continuous Integration is to make a baseline for each successful and and use diffbl -pred to look for changes.  Maybe the SCM plugin could allow the user to either use the lshistory option or diffbl?

  8. Nov 20, 2008

    cuiyz says:

    Hi Guys, I got a ClearCase issue like this: [<my view name>] $ cleartool...

    Hi Guys,

    I got a ClearCase issue like this:

    [<my view name>] $ cleartool lsactivity -fmt '\"%[headline]p\" \"%[stream]p\" \"%u\" \n' aa_-_bb_cc_dd_ee_ff_gg_hh_ii_jj
    FATAL: java.io.IOException: Too many open files
    

    The original log is:

    started
    [workspace] $ cleartool rmview -force <my view name>
    Removing references from VOB "<my vob path>" ...
    Removed references to view "<my workspace path>/<my view name>" from VOB "<my vob path>".
    [workspace] $ cleartool mkview -snapshot -stream <my project name>@<my vob path> -tag <my view name> <my view name>
    Selected Server Storage Location "goblin_viewstore".
    Created view.
    Host-local path: goblin:<my Host-local path>/<my view name>.2.vws
    Global path:     <my Host-local path>/<my view name>.2.vws
    It has the following rights:
    User : <my user name>  : rwx
    Group: <my group name> : r-x
    Other:                 : r-x
    cleartool: Warning: Unable to register new snapshot view: not a ClearCase object
    snapshot view may not be recognized by some commands.
    Created snapshot view directory "<my view name>".
    Attached view to stream "<my project name>".
    [workspace] $ cleartool update -force -log NUL -add_loadrules <my view name>//<my vob sub path_1>
    Making dir "<my vob sub path_1>/a".
    Processing dir "<my vob sub path_1>/a".
    Making dir "<my vob sub path_1>/a/b".
    Processing dir "<my vob sub path_1>/a/b".
    Loading "<my vob sub path_1>/a/b/c" (1842 bytes).
    Loading "<my vob sub path_1>/a/b/c.inc" (3321 bytes).
    Making dir "<my vob sub path_1>/a/b/d".
    Processing dir "<my vob sub path_1>/a/b/d".
    Loading "<my vob sub path_1>/a/b/d/a.h" (1029 bytes).
    Loading "<my vob sub path_1>/a/b/d/b.h" (167 bytes).
    Loading "<my vob sub path_1>/a/b/d/c.h" (206 bytes).
    Loading "<my vob sub path_1>/a/b/d/d.h" (2540 bytes).
    End dir "<my vob sub path_1>/a/b/d".
    ... ...
    ... ...  // Thousands of "Loading ..." here.
    ... ...
    Making dir "<my vob sub path_2>/3d/jetty".
    Processing dir "<my vob sub path_2>/3d/jetty".
    Loading "<my vob sub path_2>/3d/a/a.tar" (15892480 bytes).
    Loading "<my vob sub path_2>/3d/a/b.tar" (32051200 bytes).
    End dir "<my vob sub path_2>/3d/a".
    End dir "<my vob sub path_2>/3d".
    Done loading "/<my vob sub path_2>/3d" (5592 objects, copied 1160287 KB).
    [<my view name>] $ cleartool lshistory -r -since 17-nov.19:25:35 -fmt '\"%Nd\" \"%En\" \"%Vn\" \"%[activity]p\" \"%e\" \"%o\" \n%c\n' -branch brtype:<my project name> -nco <my vob sub path_1> <my vob sub path_2>
    "20081117.225225" "<my vob sub path_1>/a/src/com/a/b/c/d/e/f1.java" "/main/<my project name>/2" "a" "create version" "checkin"
    "20081117.225152" "<my vob sub path_1>/a/src/com/a/b/c/d/e/f2.java" "/main/<my project name>/2" "a" "create version" "checkin"
    Fixes
    "20081117.224502" "<my vob sub path_1>/a/src/com/a/b/c/d/e/f3.java" "/main/<my project name>/2" "a" "create version" "checkin"
    Added file element "a.java".
    Added file element "b.java".
    Added file element "c.java".
    ... ...
    ... ...  // Hundreds of "history" here.
    ... ...
    [<my view name>] $ cleartool lsactivity -fmt '\"%[headline]p\" \"%[stream]p\" \"%u\" \n' a
    "a" "<my project name>" "tom_matt"
    [<my view name>] $ cleartool lsactivity -fmt '\"%[headline]p\" \"%[stream]p\" \"%u\" \"%[contrib_acts]p\" \n' deliver.a_11.0.20081117.211100
    "deliver a_11.0 on 11/17/2008 9:11:00 PM." "<my project name>" "a" "rebase.a_11.0.20081103.233928 rebase.a_11.0.20081110.005818 a_UTS_00016435_aa_to_bb_cc_dd_dd aa_bb_cc_description"
    ... ...
    ... ...  // Thousands of "activity" here.
    ... ...
    [<my view name>] $ cleartool lsactivity -fmt '\"%[headline]p\" \"%[stream]p\" \"%u\" \n' aa_-_bb_cc_dd_ee_ff_gg_hh_ii_jj
    FATAL: java.io.IOException: Too many open files
    java.io.IOException: java.io.IOException: Too many open files
     at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
     at java.lang.ProcessImpl.start(ProcessImpl.java:65)
     at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
     at hudson.Proc$LocalProc.<init>(Proc.java:104)
     at hudson.Proc$LocalProc.<init>(Proc.java:82)
     at hudson.Launcher$LocalLauncher.createLocalProc(Launcher.java:311)
     at hudson.Launcher$LocalLauncher.launch(Launcher.java:302)
     at hudson.plugins.clearcase.HudsonClearToolLauncher.run(HudsonClearToolLauncher.java:62)
     at hudson.plugins.clearcase.ClearToolExec.lsactivity(ClearToolExec.java:67)
     at hudson.plugins.clearcase.ucm.UcmChangeLogAction.callLsActivity(UcmChangeLogAction.java:142)
     at hudson.plugins.clearcase.ucm.UcmChangeLogAction.callLsActivity(UcmChangeLogAction.java:158)
     at hudson.plugins.clearcase.ucm.UcmChangeLogAction.callLsActivity(UcmChangeLogAction.java:158)
               ... ...
               ... ...
     at hudson.plugins.clearcase.ucm.UcmChangeLogAction.callLsActivity(UcmChangeLogAction.java:158)
     at hudson.plugins.clearcase.ucm.UcmChangeLogAction.callLsActivity(UcmChangeLogAction.java:158)
     at hudson.plugins.clearcase.ucm.UcmChangeLogAction.parseHistory(UcmChangeLogAction.java:106)
     at hudson.plugins.clearcase.ucm.UcmChangeLogAction.getChanges(UcmChangeLogAction.java:56)
     at hudson.plugins.clearcase.AbstractClearCaseScm.checkout(AbstractClearCaseScm.java:205)
     at hudson.model.AbstractProject.checkout(AbstractProject.java:664)
     at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:260)
     at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:234)
     at hudson.model.Run.run(Run.java:793)
     at hudson.model.Build.run(Build.java:88)
     at hudson.model.ResourceController.execute(ResourceController.java:70)
     at hudson.model.Executor.run(Executor.java:88)
    

    I think it probably because I have too many history and activity, Hudson could not handle it. 

    Could I just disable the "Changes Analysis" in Hudson, how to do it?

    Thanks for your help!

  9. Nov 24, 2008

    ALU Enterprise says:

    Dear all, [...] [Qestion move. cf Mailing list] -- ALU

    Dear all,

    [...]

    [Qestion move. cf Mailing list]

    --

    ALU

  10. Jan 22, 2009

    Rüdiger Hoffner says:

    I try to use Clearcase-Plugin with Snapshot-Views. My config-spec has a large si...

    I try to use Clearcase-Plugin with Snapshot-Views. My config-spec has a large size, so it's impüossible to use, because i got an error.

     A good solution for this would be a checkbox "Use existing view" which doesnt need a config-spec.

    On the other hand i tried also a Dynamic-View where i got an error "cleartool -lshistory ...." getting filesize too large.

    Any ideas on this or do you need a detailed error description ???

  11. Mar 09, 2009

    G. Lohmann says:

    If you have an UCM View Branch Setup like: VOBs +-Features +-Integratio...

    If you have an UCM View Branch Setup like:

    VOBs
      +-Features
          +-Integration
              +-Project
                  +-ProjectBranch1
                  +-ProjectBranch2
              +- ...
    

    with e.g. a Folder structure in the Project like:

    \Root
        \src
        \generated
        \libs
        ...
    

    and ever come accross the following error on Hudson:

    [] $ cleartool lshistory -r -since 7-mar.21:31:29 -fmt '\"%Nd\" \"%En\" \"%Vn\" \"%[activity]p\" \"%e\" \"%o\" \n%c\n' -branch brtype: -nco Root
    cleartool: Error: Branch type not found: "".
    FATAL: UCM ClearCase failed. exit code=1
    FATAL: cleartool did not return the expected exit code. Command line="lshistory -r -since 7-mar.21:31:29 -fmt \"%Nd\" \"%En\" \"%Vn\" \"%[activity]p\" \"%e\" \"%o\" \n%c\n -branch brtype: -nco Root", actual exit code=1
    java.io.IOException: cleartool did not return the expected exit code. Command line="lshistory -r -since 7-mar.21:31:29 -fmt \"%Nd\" \"%En\" \"%Vn\" \"%[activity]p\" \"%e\" \"%o\" \n%c\n -branch brtype: -nco Root", actual exit code=1
        at hudson.plugins.clearcase.HudsonClearToolLauncher.run(HudsonClearToolLauncher.java:76)
        at hudson.plugins.clearcase.ClearToolExec.lshistory(ClearToolExec.java:57)
        at hudson.plugins.clearcase.ucm.UcmChangeLogAction.getChanges(UcmChangeLogAction.java:61)
        ...
    

    then it might be the reason of the Branch has no changes in the given directory (-nco ) and therfore point to (show) the Version of the Parent which mean the Folder will not have the Branch_Type specified by -branch.

    You have two options here ... add a Folder to -nco where you are sure you have checkouts and the real Branch Type you looking for ... or even more easy ... check-in & undo-checkout the parent to force a creation of the Branch Type on that folder.

    [by the way ... I think the plugin should not FAIL on something like a simple resolve of the history. Maybe the history might not be available but that should not effect the build itself ...]

  12. Mar 16, 2009

    Rajesh Sarva says:

    Hi, My requirement is to apply labels on source code before build and upda...

    Hi,

    My requirement is to apply labels on source code before build and update the snapshot view using the latest label. The label will be based on build number ex:1.1.buildnumber.1

    1.Apply label on all the source files ex:1.1.buildnumber.1.

     I can use NAnt for this.

    2.Update the view.

    Is it possible to use Hudson variables in config spec.

    element * CHECKEDOUT
    element 1.1.$

    Unknown macro: {BUILD_NUMBER}

    .1
    element * /main/LATEST

    it seems this does not work.

    Any other work-around for this. 

  13. Apr 06, 2009

    Slide Earl says:

    I am getting this from the "Last UCM ClearCase Polling Log" I assume it grabs t...

    I am getting this from the "Last UCM ClearCase Polling Log"

    I assume it grabs the items to look for differences in based on the load rules. I think it's having problems with the newlines in the loadrules, but if I remove the newlines where I enter the loadrules, it gives me another error when trying to get the sources using the update.

    Started on Apr 6, 2009 3:45:42 PM
    [TTC_svccadm_view] $ cleartool lshistory -r -since 6-apr.14:57:45 -fmt '\"%Nd\" \"%En\" \"%Vn\" \"%e\" \"%o\" \n' -branch brtype:TTC1_Int -nco ttc_boot
    ttc_focus
    ttc_primitives
    ttc_ecos
    ttc_tools
    cleartool: Error: Unable to access "ttc_boot
    ": Filename too long.
    cleartool: Error: Unable to access "ttc_focus
    ": Filename too long.
    cleartool: Error: Unable to access "ttc_primitives
    ": Filename too long.
    cleartool: Error: Unable to access "ttc_ecos
    ": Filename too long.
    Done. Took 0.59 sec
    No changes

    Is there anything I need to do to set this up better?

    1. Apr 07, 2009

      Slide Earl says:

      Actually, if I run the command on the command line, the error occurs on the -fmt...

      Actually, if I run the command on the command line, the error occurs on the -fmt argument. I had to change the single quotes to double quotes and it works on the command line. Is this because the plug-in is mainly for Linux?

  14. Apr 16, 2009

    Park Su Jin says:

    Hello I would like to get source in Clear Case with polling mode using Hudson. ...

    Hello
    I would like to get source in Clear Case with polling mode using Hudson.

    But I can not find how to ignore cleartool error during update snapshut view.

        ※ We can do like following lines in Ant.

            <ccupdate viewpath="$

    Unknown macro: {ViewPath}

    " graphical="false" overwrite="true" rename="false" failonerr="false" />

        ※ Hudson always use following option to update view

            "c:\Program Files\Rational\ClearCase\bin\cleartool.exe" update -force -log NUL hudson_frontier_view

    Do you know how do I ignore cleartool error without using Ant?

        I wonder if Hudson use polling mode when Hudson invoke Ant file to update clear case view or not.

    Have a good day.

    1. Apr 17, 2009

      Andrew Bayer says:

      Hi - We don't have the option of ignoring errors in cleartool executions, nor d...

      Hi -

      We don't have the option of ignoring errors in cleartool executions, nor do we intend to add that option. Sorry.

      A.

      1. Jun 12, 2009

        Andrey B says:

        This option will be very useful. In my company users have different access per...

        This option will be very useful.
        In my company users have different access permission to different folder
        When we running ct update and user do not have read access to folder, cleartool return error.
        For users with access privilege to secured folder update is fine
        Have a nice day.

  15. Sep 18, 2009

    Duncan McLaren says:

    Hi, I have just started looking at using Hudson with Clearcase UCM as an altern...

    Hi,

    I have just started looking at using Hudson with Clearcase UCM as an alternative to CruiseControl and I am finding that things are not working as I might expect them to. The setup menu on Hudson was very straighforward, so I'm assuming that I haven't missed an obvious solution to my issues.

    My project has a composite baseline configured with a Read-only component. This component is a Business Information Model which is managed in another project, and releases of this model are made available to various application development projects by including it as a Read-only component. Updates to this Information Model are made available to the development project by changing the Base configuration of the stream, but the changes are not part of the development stream that the Hudson project is configured to look at.

    When I change the base configuration, the changes to my read-only component are not picked up on the Hudson server when the view is updated. From what I can see, the plugin re-writes (setcs) the View config spec with the load rules at the start of every build. It then executes an update with an add_loadrules option for each load rule. This kind of update appears to ignore configuration changes on the stream. If a simple clearcase update view, with no additional paramters, is executed then the view configuration is synchronized with the stream, and the modifications to the Read-only component are picked up.

    Is there a specific reason why you perform an update for each load rule?

    Another potential issue with this approach is that if I remove a component and delete the load rule no update will be execute to remove the redundant elements from the view, where-as setcs followed by a simple update of the view would unload these unncessary elements.

    My second issue is that changes to the Read-only component are not detected by the lshistory command because it is only looking at the modifications made to a single stream. In addition to this lshistory on the read-only component would be difficult to work with because the changes to the Read-only component could be made weeks before it is used in the current stream.

    A more accurate way of detecting changes might be to parse the update log (which is currently re-directed to NUL) looking for new, updated or unloaded components (ignore Hijacked).

    In summary I think there are 2 distinct problems here:

    1. Changes to read-only components are not detected and loaded in to the view

    2. Changes to read-only components won't trigger a build.

    In my case the first problem is the killer because I have to log on to the Hudson server and manually update each affected view when the Read-only component is modified. These changes are generally linked with code changes which will appear in lshistory, so problem 2 would be less important.

    Has anyone else encountered these issues?

    regards

    Duncan

  16. Nov 10, 2009

    David Hausladen says:

    Word of caution to folks new to this plugin: open file handles maintained by so...

    Word of caution to folks new to this plugin: open file handles maintained by some editors, Windows command consoles, and J2EE apps will prevent the view removal logic from executing properly. You'll see something like this in the build log.

     
    Removing references from VOB "\MY_PVOB" ...
    Removed references to view "E:\hudson\jobs\job_name\workspace\view_name" from VOB "\MY_PVOB".
    cleartool: Error: E:\hudson\jobs\job_name\workspace\view_name\view_root_dir\path\to\some\file.extension: Permission denied
    ...
    cleartool: Error: Unable to remove the snapshot view directory.
    cleartool: Error: E:\hudson\jobs\job_name\workspace\view_name: Directory not empty
    cleartool: Error: Unable to remove the snapshot view directory.
    	at hudson.plugins.clearcase.ClearToolSnapshot.rmview(ClearToolSnapshot.java:144)
    	at hudson.plugins.clearcase.action.UcmSnapshotCheckoutAction.checkout(UcmSnapshotCheckoutAction.java:87)
    	at hudson.plugins.clearcase.AbstractClearCaseScm.checkout(AbstractClearCaseScm.java:410)
    	at hudson.model.AbstractProject.checkout(AbstractProject.java:1003)
    	at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:428)
    	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:376)
    	at hudson.model.Run.run(Run.java:1174)
    	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
    	at hudson.model.ResourceController.execute(ResourceController.java:88)
    	at hudson.model.Executor.run(Executor.java:123)
    

    The remedy appears to be to restore the plugin's desired end state--a snapshot view with the correct owner and name. To achieve this, I

    1. login as the same user that runs the hudson service,
    2. remove the offending directory after closing all programs that might have handles open, then
    3. create the view using the command from a successful build's log,
    4. update the view from windows explorer (could be done from commandline also), and
    5. manually kick off the job.

    If anyone else has run into similar problems and found a better way of recovering, I'd love to hear about it.

  17. Jan 18, 2010

    Roshan Soni says:

    Hi, Does anyone know if this plugin supports CC 7.1? Thanks, Roshan

    Hi, Does anyone know if this plugin supports CC 7.1?

    Thanks,

    Roshan

  18. Jan 26, 2010

    Hugo Monteiro says:

    Hi there! Thanks for creating this plugin. I have some minor requests for...

    Hi there!

    Thanks for creating this plugin.

    I have some minor requests for it:

    1) When using Clearcase snapshot views, a "cleartool lsview" is executed to check if the view already exists, I presume. The problem is that, the output of it should not be shown in the actual job's log, since it's not directly related with the build process.A command like "cleartool lsview $CLEARCASE_VIEWNAME" could be used instead, which would return only the actual view's information, if the view already exists, or return an exit code = 1 if the view doesn't exists, which in this case the view can be created if configured that way.
     Really, the main issue for me with this output is that, in large companies, there could be hundreds of views (as in my case) in only one Clearcase region! In which a listing of the full Clearcase Views of that region, not only could take long to get (slowing the build every time), but also will clutter up the build's log, when issue the suggested command, will be faster and cleaner.

    2) It would be great to allow variables to be specified in ConfigSpec/Load Rules fields, for greater flexibility. These fields would have to be pre-processed before they were sent/set in Clearcase View. This would allow greater flexibility when creating job's for similar projects that would only have differences in directories names in configspec or load rules.

    ex:
    1) /vob/customer/project1
    2) /vob/customer/project2

    - config spec #1 -
    element * LABEL1
    load /vob/customer/$

    Unknown macro: {PROJECT}

    - end config spec -

    This way we could create a job for a customer that would allow to specify the $PROJECT variable before the build runs, using the parameters feature hudson provides. Like PROJECT=project1 or PROJECT=project2.

    3) Alternative of the above, it would be nice to have an extension of this plugin into hudson's parameterized plugin, to allow entering configspec directly when requesting a new build, instead of having to configure the build again, save it, and start the build.

    I'm asking this because we use hudson both for continuous integration and official builds. In CI "mode" we use it in a common way. But for official builds, we need to configure the environment, specially the configspec, and this will greatly increase simplicity and flexibility when dealing with a bigger number of jobs.

    Thanks!

    1. Jan 26, 2010

      Andrew Bayer says:

      Could you open a bug at http://issues.hudson-ci.org for #1? The output of lsview...

      Could you open a bug at http://issues.hudson-ci.org for #1? The output of lsview showing up in the build log is not deliberate - I'll fix that. You can open feature requests for #2 and #3 as well, though no promises on either of those.

  19. Feb 01, 2010

    Saravanan BV says:

    Hi, I have started using Hudson and integrated CC plugin. I am getting the fol...

    Hi,

    I have started using Hudson and integrated CC plugin. I am getting the following error while trying to run the build.
    I need to know how to set a CC view through hudson?

    Console Output:
    Started by user anonymous
    [sbarathu_lat] $ /usr/atria/bin/cleartool pwv -root
    /view/sbarathu_lat
    [workspace] $ /usr/atria/bin/cleartool startview sbarathu_lat
    [workspace] $ /usr/atria/bin/cleartool catcs -tag sbarathu_lat
    element * CHECKEDOUT
    #element /cm4/tools/coverity/... /main/LATEST
    element /vobs/esam/configspecs/ISAM_mainstream.cs /main/aaaa/isr41/51
    include /view/LATEST/vobs/esam/configspecs/ISAM_mainstream.cs@@/main/aaaa/isr41/51
    [sbarathu_lat] $ /usr/atria/bin/cleartool lshistory -all -since 1-feb-10.12:38:41utc+0000 -fmt '\"%Nd\" \"%u\" \"%En\" \"%Vn\" \"%e\" \"%o\" \n%c\n' -nco vobs/esam/configspecs vobs/esam/build
    [workspace] $ /bin/sh -xe /var/tmp/hudson4754014555775014105.sh
    + /usr/atria/bin/clearmake -C gnu -f /vobs/esam/build/ecnt-c/OS/Makefile E=SUN VERBOSE=X all
    clearmake: Error: Unable to open file "/vobs/esam/build/ecnt-c/OS/Makefile": No such file or directory.
    Finished: FAILURE

  20. Feb 09, 2010

    Justin Bischoff says:

    Hello, Thanks for writing a great plug-in! I appear to be having a permissions...

    Hello,

    Thanks for writing a great plug-in! I appear to be having a permissions issue that I can't seem to get around. I am unfortunately not too familiar with the cleartool - do I need to provide my login credientials for the Set Config Spec command to work?

    [workspace] $ cleartool rmview -force hudson_view_auto
    [workspace] $ cleartool mkview -snapshot -tag hudson_view_auto -vws \\Fm5sgcedevs04\workspace\hudson_view_auto\view.stg.vws hudson_view_auto
    Created view.
    Host-local path: Fm5sgcedevs04:C:\Program Files\Hudson\jobs\Test Build 001\workspace\hudson_view_auto\view.stg.vws
    Global path: \\Fm5sgcedevs04\workspace\hudson_view_auto\view.stg.vws
    Created snapshot view directory "hudson_view_auto".
    [hudson_view_auto] $ cleartool setcs ..\configspec62998.txt
    cleartool: Error: Unable to access "\gfx_Development\Test\Tools": Permission denied.
    cleartool: Error: Unable to access "\gfx_Development\Test\ghal3d": Permission denied.
    cleartool: Error: Unable to access "\gfx_Development\Tools": Permission denied.
    cleartool: Error: Unable to access "\gfx_Development\Source": Permission denied.
    cleartool: Error: 4 config spec load rule problems encountered.

    Thanks,

    -Justin

    1. Feb 10, 2010

      Justin Bischoff says:

      I think the problem is that access is controlled to our clear case server, yet h...

      I think the problem is that access is controlled to our clear case server, yet hudson is accessing as anonymous.

      Started by user anonymous

      -Justin

    2. Feb 12, 2010

      Joseph Boulos says:

      I'm having a similar issue.  I'm not sure if it is Hudson, ClearCase Plugin...

      I'm having a similar issue.  I'm not sure if it is Hudson, ClearCase Plugin, or ClearCase itself.  I just hung up with IBM and they point the finger back at Hudson.

      We have a folder within a VOB that is extra protected.  Users of the main group can access the whole VOB, except 1 subfolder.  Only users of a special group can access that subfolder.  The user that runs Hudson is part of that special group.  However, builds from Hudson always come back with Permission Denied.

      The interesting thing is, if I go manually onto the Hudson server where the build runs and use ClearCase Explorer to click on the folder within the view, then rerun the job from Hudson, it magically starts working.

      One thing I tried is to just run ls or dir on that protected directory from Hudson, and then to also do the same thing from a .bat that the Windows Scheduler runs.  Hudson gets permission denied, but the one run by Windows Scheduler works fine.  I thought it had to do with Interactive user versus Non-Interactive user.  It may still, but using Windows Scheduler worked fine.

      Any ideas anyone?  Justin, did you figure out a workaround?

      Also, I get this problem all the time, including when I start the job and therefore it is started by the right user with access to the special group, not anonymous.

      1. Feb 23, 2010

        Justin Bischoff says:

        I had to modify the Hudson service to run as a user with permissions to access C...

        I had to modify the Hudson service to run as a user with permissions to access ClearCase. I currently am pre-creating the view manually before kicking off the Hudson job.

        I don't think I have seen your particular permissions problem though.

        -Justin

  21. Mar 09, 2010

    Jes struck says:

    Polling the ClearCase repository now just reports "No changes from last build." ...

    Polling the ClearCase repository now just reports "No changes from last build." Even do im sure there are changes on the stream, Is there any one else that have seen this and know why, changes won't be reported or shown on hudson' "Changes site"

    Im running a distrubuted setup on 2 machines atm. but we just about to expand to 4, and using "Hudson 1.339" and "Clearcase 1.1.1" and "ClearCase UCM Baseline 1.3" in our configuration.

    Please i can use any help given, in advance.
    Thanx

    btw. im using ClearCase LT version 6.15 AND UCM

    THE ERROR WE ARE GETTING IS AS FOLLOWING:
    Started on 09-03-2010 13:02:26
    [workspace] $ cleartool pwv -root
    C:\path\to\workspace
    [workspace] $ cleartool lshistory -all -since 9-mar-10.10:02:25utc+0000 -fmt '\"%Nd\" \"%u\" \"%En\" \"%Vn\" \"%e\" \"%o\" \"%[activity]p\" \n%c\n' -branch brtype:branchname -nco '"265_Rc\Rc_ProdSw "' '"265_Rc\Rc_SubSys "' '"265_Rc\Rc_HwTest "' '"265_Rc\Rc_Lib "' '"265_Rc\Rc_Hal "' '"265_Rc\Rc_Tp "' '"265_Rc\Rc_Model "' '"265_Rc\Rc_Func "' '"265_Rc\Rc_WinSim "' '"265_Rc\Rc_Safety "' '"265_Rc\Rc_Ui "' '"265_Rc\Rc_Si "' 265_Pump\P_RcpcPumpSi
    cleartool: Error: Branch type not found: "branchname".
    "20100309.123316" "USER" "C:\path\to\workspace\VOB\COMPONENT\paht\to\chnages\file" "\main\MS_E_mainline_int\branchname\3" "create version" "checkin" "Activity identifier"

    Done. Took 1,2 sec
    No changes

    why does it say "No changes" when there are a change????....

  22. Apr 22, 2010

    Trent Fisher says:

    I just started using Hudson with ClearCase, but it appears that its use of dynam...

    I just started using Hudson with ClearCase, but it appears that its use of dynamic views is a bit off when creating new ones for each build. If it finds a view with the same name, it tries to remove it via this odd sequence:

    [workspace] $ /usr/atria/bin/cleartool rmview -force -avobs -uuid d8b2ef8f.4e5411df.91cb.00:1d:09:70:2e:5e
    [workspace] $ /usr/atria/bin/cleartool unregister -view -uuid d8b2ef8f.4e5411df.91cb.00:1d:09:70:2e:5e
    [workspace] $ /usr/atria/bin/cleartool rmtag -view hudson_view
    [workspace] $ /usr/atria/bin/cleartool mkview -tag hudson_view -host sdc60010vob -gpath /net/sdc1006nap.us.oracle.com/vol/sdc60010vob/vws/hudson_view.vws -hpath /ccase/vws/hudson_view.vws /ccase/vws/hudson_view.vws
    cleartool: Warning: "/ccase/vws/hudson_view.vws" and "/net/sdc1006nap.us.oracle.com/vol/sdc60010vob/vws/hudson_view.vws" do not reference the same filesystem location.
    cleartool: Warning: Storage pathname "/ccase/vws" may not reside on host "sdc60010vob".
    cleartool: Error: Unable to create directory "/ccase/vws/hudson_view.vws": File exists.
    cleartool: Error: Unable to create view "/ccase/vws/hudson_view.vws".
    FATAL: Base ClearCase failed. exit code=1

    Two problems with this: as you can see, this leaves the view storage laying around, and then the mkview fails as a result. But if you try to manually remove the view storage, it will fail because the view_server process has files open. So to make this sequence work, you would need to do "cleartool endview -server viewname" and then remove the view storage.

    Of course, after you've done that, you've effectively rewritten the "rmview" command... so why not just do rmview? I looked in the source and found this line:

    launcher.getListener().fatalError("Dynamic view does not support rmview");

    I'm not sure what this is about as I have been doing "rmview" on dynamic views for over 15 years, it works fine.

    ++thanks,
    trent...

  23. May 05, 2010

    abhijit joshi says:

    Hi, It seems that issue with space characters in the load paths have reappeared...

    Hi,

    It seems that issue with space characters in the load paths have reappeared on the new plugin version. I have older version of the plugin (0.9.1) running on one hudson and latest version 1.2 on  other hudson.

    The older one specifies load path as

    load "/XYZ/ABC File Management.sln"

    and newer one specifies the same but in seperate load path section now

    /XYZ/ABC Management.sln

    The old job succeeds to load the file while the newer one fails saying cleartool: Error: Unable to lookup "ABC" in "\XYZ@@\main\100": No such file or directory.
    cleartool: Error: Unable to access "\XYZ\ABC": No such file or directory.
    cleartool: Error: Pathname "File" is not a full VOB pathname: it does not begin with a "\".
    cleartool: Error: Pathname "Management.sln" is not a full VOB pathname: it does not begin with a "\".

    cleartool: Error: 3 config spec load rule problems encountered.
    Can you please check if the following fix with plug-in version 1.1 is really fixed?

    Bug fix: Load rules containing spaces are now handled properly in cleartool calls. (issue #4443)

    Regards,

    abhijit

  24. Jun 23, 2010

    jun ji says:

    if specify "branches" , hudson use cleartool lshistory -r -since 23-jun-10.08:29...

    if specify "branches" , hudson use cleartool lshistory -r -since 23-jun-10.08:29:40utc+0000 -fmt '\"%Nd\" \"%u\" \"%En\" \"%Vn\" \"%e\" \"%o\" \n%c\n' -branch brtype:FDT1105 -nco

    to get update.

    We may have "/main/b1/FDT1105" & "/main/b2/FDT1105"

    Is there any way to select specific branch, just add "grep /main/b1/FDT1105" when lsh ?

  25. Jun 23, 2010

    Aswini Ray says:

    I want to modify the current clearcase plugin to meet the demand of our project....

    I want to modify the current clearcase plugin to meet the demand of our project. Can anybody tell me how to copy the clearcase plugin source codes without copying it manually from Fisheye repository.

    Regards,
    Aswini

    1. Jul 14, 2010

      Nadjib says:

      Voila! https://hudson.dev.java.net/servlets/ProjectDocumentList?folderID=80...
  26. Aug 19, 2010

    Ciprian says:

    Hello , I am using Hudson and ClearCase pluggin, but I have some problems, I'm ...

    Hello ,

    I am using Hudson and ClearCase pluggin, but I have some problems, I'm running on REDHAT OS

    I declared a node slave and i want to execute a shell with the command  cleartool setview <view_name> and it's works, but when I run cleartool pwv it shows me that there is no view set.

    May someone help me with this issue ? Has anyone a idea ?

    I'm using a dynamic view, which already exist.

    Regards,

    Ciprian

  27. Oct 17, 2010

    M. Certain says:

    I've been trying to get Hudson setup to work with ClearCase dynamic views for a ...

    I've been trying to get Hudson setup to work with ClearCase dynamic views for a week now with little success. It seems that for some reason Hudson does not have access to the View drives on the machine where I'm running Hudson. I have Hudson installed on a Windows XP machine with ClearCase 7. I setup Hudson to run as a service and run as my user to ensure that it would have access to the same things as myself on this machine. I can also do an "echo %UserName%" from batch scripts executed by Hudson and it will indicate my username. However, it still appears that Hudson does not have permissions to these views.

    For example, if I try to change drives to one of my ClearCase view drives in the batch script, I see the following...

    C:\hudson\jobs\XXXXXX\workspace>V:
    The system cannot find the drive specified.

    It also seems that I must put my Hudson workspace directory in the view on the M:\ where I want to execute my build batch script. If I don't, then I will get the following error..

    clearaudit: Error: No current view

    I also can't put the workspace directory on the drive mapped to the view I'm interested in otherwise I will get the following error.

    Started by user anonymous
    java.io.IOException: Failed to mkdirs: V:\XXXXXXX
        at hudson.FilePath.mkdirs(FilePath.java:812)
        at hudson.model.AbstractProject.checkout(AbstractProject.java:1080)
        at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
        at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
        at hudson.model.Run.run(Run.java:1280)
        at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
        at hudson.model.ResourceController.execute(ResourceController.java:88)
        at hudson.model.Executor.run(Executor.java:137)
    Finished: FAILURE

    However, it seems that I still only have limited success with using the M:\ view root drive as well. When I do use the view root drive where references to all of my views are located, I still run into problems here where it seems like Hudson has only read-only access for some reason. So I'll see errors like the following...

    WARNING XXXXXX: Could not create temp dir in M:/xxxxxx_view7: couldn't create directory "M:\xxxxxx_view7\xxxxx_tmp_3840_0": The media is write protected (error code 19)

    Whenever I open a DOS command line window (via cmd.exe) and try to run these same batch scripts, they work perfectly. I have access to both the M:\ drive and all of my mapped view drives such as V: that I referenced above. So I don't understand what the difference is between running these batch commands from cmd.exe vs. Hudson running them.

    Has anyone had similar problems as this and been able to resolve them?

  28. Nov 19, 2010

    me says:

    Hi, Sorry, if this was already posted... I'm running hudson on linux with a hu...

    Hi,

    Sorry, if this was already posted...

    I'm running hudson on linux with a hudson-slave on a windows server using clearcase plugin(1.3.3)

    To get around the permission issue below...you'll need to change the user id the hudson-slave service is running as.  It's currently running as SYSTEM which is why i was getting the error below.

    cleartool: Warning: Config spec OK, but unable to tell view server to load.
    cleartool: Warning: View server should be restarted.
    cleartool: Error: Unable to change configuration specification: Permission denied.
    FATAL: UCM ClearCase failed. exit code=1

    Hope this helps...

    1. Nov 19, 2010

      me says:

      PLEASE DO NOT DO THIS, IT CRASHED MY SERVER!!!...Sorry if anyone has...

      PLEASE DO NOT DO THIS, IT CRASHED MY SERVER!!!...Sorry if anyone has tried it already.  it's fine after running the cleartool setcs, but when it runs maven commands, it's downhill after that...

  29. Jul 06, 2011

    Lisandro says:

    Hi, I have install Hudson in my PC with Server Tomcat 7.0 and need download a vi...

    Hi,
    I have install Hudson in my PC with Server Tomcat 7.0 and need download a view created with
    IBM Rational Clear Case, but without need to install Clear Case(without 'cleartool') in this PC.
    Does some tool compatible with Hudson exist (open source please)?
    The idea that we have is not to index in any external resource the server,
    we must have everything necessary in the server without need to install
    Clear Case in this one machine and without depending on another machinem
    because of it we wanted to know if there exists the
    possibility of a free tool compatible with Hudson.
    Thanks and Regards

  30. Sep 14, 2011

    Nagaraju says:

    Hi,    When i build my project i got success mail to my mail id .In m...

    Hi,

       When i build my project i got success mail to my mail id .In mail  body it shows only url .But i want to display text like "your build is successful " for this where i have to configure

    Thanks

  31. Oct 10, 2011

    Richard Hill says:

    Trying to run a simple batch script that will start my ClearCase build, it fails...

    Trying to run a simple batch script that will start my ClearCase build, it fails with "permission denied".  When I execute from the command prompt it works.  I was able to make this work by setting the Hudson service to start using my login.

  32. Nov 02, 2011

    Mark Yu says:

    I run into the integration issue with base clearcase with Hudson.  I have ...

    I run into the integration issue with base clearcase with Hudson. 

    I have Hudson running in windows xp, Clearcase server is running a Solaries machine.  I can only access clearcase server by using cleartool through unix client or clearcase remote client with Eclipse.

    So I do not know how I can configure clearcase from Hudson (config system) page to get clearcase integrated.

    In ClearCase installation, I put D:\Program Files\IBM\RationalSDLC\ClearCase\, it is the path where cleartool is installed in my xp.  I would not be able to access ClearCase unix server from window xp.

    Thanks in advance!


  33. Nov 28, 2011

    zafer altug says:

    hi, I am newbie at jenkins. I am trying to work with a dynamic ucm view. But I ...

    hi,
    I am newbie at jenkins. I am trying to work with a dynamic ucm view.
    But I have got "Error: Unabled to change configuration specification: Permission denied" error,
    when jenkins set the config spec of view with "cleartool setcs ... " command.
    Is there any way of not to reset config spec like base clearcase and avoiding this error.
    Thanks in advance..

  34. Nov 30, 2011

    Donner Speer says:

    Wow! This information was truly valuable to me. Ill be coming back to your b...

    Wow! This information was truly valuable to me. Ill be coming back to your blog.

    elegant wedding dresses

  35. Jan 24, 2012

    Marcos Lambolay says:

    Hi people, i have been trying to set the "excluded regions" on "advanced configu...

    Hi people, i have been trying to set the "excluded regions" on "advanced configuration" since i want to exclude a file.

    I have been entering in such field the next values, but i can't get to exclude the file that i want to exclude (build.properties or anything that finishes as "build.properties", thus i use "*")

    So far i have tried:

    (escaping characters)
    .*build\.properties

    (not escaping characters, with slash)
    /*build.properties

    (not escaping characters, with backslash)
    *build.properties

  36. Jan 25, 2012

    Akash says:

    Hi, I am trying to use Hudson for my project but the CC version I have is pretty...

    Hi, I am trying to use Hudson for my project but the CC version I have is pretty old (Version 7.0.1.7).

    I tried to integrate hudson with this CC but the plugin available is for newer version of CC and uses command arguments which are unknown to older version.

    I am not able to find plugin compatible to this version of CC. Can anyone help?

    Thanks
    Akash.