Skip to end of metadata
Go to start of metadata

Allows using ClearCase UCM baselines as the input of builds: When using this SCM, users will be asked at build-time to select the baseline on which the job has to work.

Plugin Information

View ClearCase UCM Baseline on the plugin site for more information.

To use this plugin, you need to install the ClearCase Plugin since it relies on it (more precisely, the global configuration data is shared between the two plugins):

 

ClearCase Plugin
1.0.x

ClearCase Plugin
1.1.x

ClearCase Plugin
1.2.x

ClearCase Plugin
1.3.x

ClearCase UCM Baseline Plugin
1.0, 1.1, 1.2

(tick)

(error)

(error)

(error)

ClearCase UCM Baseline Plugin
1.3, 1.4, 1.5.x

(tick)

(tick)

(error)

(error)

ClearCase UCM Baseline Plugin
1.6

(tick)

(tick)

(tick)

(error)

ClearCase UCM Baseline Plugin
1.7.x

(error)

(error)

(error)

(tick)

About this plugin

This plugin adds a new ClearCase UCM baseline SCM mode to the projects: It's then possible for a build to start based on a ClearCase UCM baseline (composite or not) without playing with config specs or having to modify the job configuration. When using the ClearCase UCM baseline SCM mode, the user will be presented with the following screen when starting a new build:

After having clicked on the Build button of this screen, a new view will be created to retrieve the whole content of the selected baseline and the job will be able to work on this data, as usually.

A use case behind this plugin

Let's say your development team is using Hudson as their continuous integration system while developing a new J2EE application. They have defined a new job in Hudson, which runs twice a day (at noon and at night) to frequently ensure everything works fine. This job may do the following:

  1. It gathers the application source code using the ClearCase Plugin.
  2. It builds the application from the source code using the RAD Builder Plugin.
  3. It runs the unit tests (thank you JUnit).
  4. It deploys the application on a production-like application server (for example using the WAS Builder Plugin), ensuring everything is deployed properly (e.g. JDBC resources are available, etc.).
  5. It triggers the execution of non-regression testing.
  6. At one moment or another in this build-flow (depending on your point on view), it creates a new ClearCase baseline.

After some time, once the application has been extensively tested and when most of its functionalities are considered as ready-for-production, one of the baseline is promoted to the RELEASED level. It means your infrastructure team will gather this baseline and deploy on the production environment what has to be deployed.
Hey, minute, we're talking about deployment, right? Something has already been defined in the previously described job to do that! It has run many many times, so it can also surely be used to perform the deployment on the production environment, no? This is when the ClearCase UCM Baseline Plugin comes in: It allows you to reuse what has already been defined in Hudson but to work on promoted baselines rather than working on the HEAD revision.

User guide

There's not much to say here, refer to the inline help (the little question marks at the right of the jobs' configuration screen) to get detailed information:

  • Set the SCM to be ClearCase UCM baseline. You'll notice that it has no parameters (screenshot below).
  • If not already done, activate the This build is parameterized option.
  • Add one (and only one) ClearCase UCM baseline parameter and fill the various fields.
  • You're done!

Now, when starting a new build, the user will be offered with a drop-down list allowing him to chose one of the baselines based on the job's settings:

Some questions and their answers regarding the configuration of this plugin:

  • What if I define the SCM to be ClearCase UCM baseline but without adding the required parameter?
    The build will fail, explaining why.
  • What if I define the SCM to be ClearCase UCM baseline but adding more than one ClearCase UCM baseline parameter?
    The build will fail explaining why.
  • What if I don't set the SCM to be ClearCase UCM baseline but adding some ClearCase UCM baseline parameter?
    Here also, the build will fail explaining why.
  • What if I create a string parameter named ClearCase UCM baseline (using the ClearCase UCM baseline mode)?
    The build will fail, explaining why.

Roadmap

Known limitations

  • The plugin will not work when using it for a job which is not tied to a specific node: It won't be able to get the baselines list before the build is actually assigned to a node.

Version history

Version 1.7.4 (09/19/2011)

  • Implemented JENKINS-9074: A warning message is now displayed if both the Exclude element CHECKEDOUT and Use snaphost view options are checked

Version 1.7.3 (02/20/2011)

  • Implemented HUDSON-8013:
    • Baselines are now displayed from the most recent one to the oldest one.
    • Added a new More recent than field which allows displaying only baselines more recent than a given duration.
  • Implemented HUDSON-8015: Baselines description are now displayed in builds log.
  • Fixed JENKINS-8695: Baselines spread across several PVOBs are now properly handled.

Version 1.7.2 (01/21/2011)

  • Fixed HUDSON-8168: The cleartool command was wrongly generated when adding the -stg option in the Additional mkview arguments field.

Version 1.7.1 (10/01/2010)

  • Fixed an issue which was preventing to use snapshot views.

Version 1.7 (09/02/2010)

  • Compatibility with the 1.3.x versions of the ClearCase plugin – Compatibility with 1.0.x, 1.1.x and 1.2.x has been dropped.

Version 1.6 (06/23/2010)

  • Upward compatibility with the 1.2.x versions of the ClearCase plugin (still supporting the 1.0.x and 1.1.x versions).
  • Added an option to specify additional mkview arguments (cf. HUDSON-6409).
  • Added the possibility to use the CLEARCASE_BASELINE environment variable within the view name (cf. HUDSON-6410).
  • Added a new option to exclude element * CHECKEDOUT from config specs (cf. HUDSON-6411).
  • Fixed HUDSON-6398:
    • Rootless components are now no more taken into account.
    • Load rules are no more duplicated under certain conditions.

Version 1.5.1 (04/02/2010)

  • Fixed HUDSON-6152:
    • No config spec elements/load rules were generated for the selected baseline.
    • The config spec was not used.

Version 1.5 (03/29/2010)

  • Added a new Stream option to filter the displayed baselines (cf. HUDSON-6088).
  • Added a new Use update option to avoid recreating the view each time a new build is triggered (cf. HUDSON-6088 too).
  • Fixed HUDSON-6057: The plugin will try to start the node it is tied to if it is offline.
  • Fixed HUDSON-6029: The plugin will behave properly in a mixed Linux/Windows environment (e.g. the master being Linux and slaves being either Linux or Windows).
  • Fixed HUDSON-5877: Added a new error message to clearly show that the publishers (make baseline and make composite baseline) from the ClearCase plugin can't be used with the ClearCase UCM baseline SCM mode.

Version 1.4 (03/02/2010)

  • Added a new Use snapshot view option (activated per default).
  • The plugin now better handles '/' characters in front of PVOB names: If '/' is/was not specified, it will be automatically added.
  • The VOB parameter has been removed. If you get the following exception, you can safely ignore it:
    ATTENTION: Skipping a non-existent field vob
    com.thoughtworks.xstream.converters.reflection.NonExistentFieldException: No such field com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineParameterValue.vob
    
  • The component root dir is now retrieved from the specified component; In earlier releases, the plugin assumed that the component root dir was identical to the name of component.

Version 1.3 (02/24/2010)

  • Upward compatibility with the 1.1.x versions of the ClearCase plugin (still supporting the 1.0.x versions).
  • Added a new Force rmview option: If the baseline selected for build #n is the same as for build #n-1 (and if the corresponding view still exists), by default the view won't be created/loaded again; Set this option to true so that the view gets recreated anyway.
  • Fixed an issue which was displaying an incorrect view name in builds' history.

Version 1.2 (02/08/2010)

  • Added a new CLEARCASE_BASELINE environment variable.

Version 1.1 (01/22/2010)

  • Added a new Restrict folders to field which allows defining which folders have to be actually downloaded from the ClearCase UCM baseline.

Version 1.0.1 (01/11/2010)

  • Fixed an issue which was preventing to display the list of the baselines when the job was running on a tied slave node

Version 1.0 (01/10/2010)

  • Initial release

48 Comments

  1. I just cannot get this plugin to work. I always end up with:

    Started by user lmcpare
    Building remotely on camox224
    FATAL: hudson.plugins.clearcase.util.BuildVariableResolver.(Lhudson/model/AbstractBuild;Lhudson/Launcher;)V
    java.lang.NoSuchMethodError: hudson.plugins.clearcase.util.BuildVariableResolver.(Lhudson/model/AbstractBuild;Lhudson/Launcher;)V
    	at com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineParameterValue$2.setUp(ClearCaseUcmBaselineParameterValue.java:154)
    	at hudson.model.Build$RunnerImpl.doRun(Build.java:126)
    	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
    	at hudson.model.Run.run(Run.java:1198)
    	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
    	at hudson.model.ResourceController.execute(ResourceController.java:88)
    	at hudson.model.Executor.run(Executor.java:122)
    
    1. Which version of the ClearCase plugin do you use? I've tested it against 1.0.2. There are 99% chances that it doesn't work with 1.1.x or 0.x.

      1. Oh crap! I am using the latest ClearCase plugin, 1.1.1, over Hudson 1.346.

        1. I've sent on your mail an upward compatible version for the ClearCase plugin 1.1 (this is the BuildVariableResolver API which changed). If it works well, I'll commit the changes and release it.

  2. Unknown User (vrspraveen.atluri@gmail.com)

    I am trying to build the code using baseline. but Its not creating the snapshot view ane the build is failing. Is this beacuse of the clearcase ucm baseline version version conflict.

  3. Unknown User (vrspraveen.atluri@gmail.com)

    I am using ClearCase UCM baseline plugin 1.2 with hudson version 1.346. It is not creating the view based on the baseline parameter selected.

    1. Any logs? The information you provide is not enough to get help... But I guess you're not using an 1.0.x version of the ClearCase plugin.

      1. Unknown User (vrspraveen.atluri@gmail.com)

        This uis what I see in tomcat logs.

        Feb 23, 2010 11:39:47 AM org.apache.tomcat.util.http.Parameters processParameters
        WARNING: Parameters: Invalid chunk ignored.
        Feb 23, 2010 11:39:47 AM hudson.model.Run run
        INFO: Util-Services #14 main build action completed: FAILURE

        I Checked in the build logs in .hudson directory It says It couldnt find the pom file. as the view is not getting created from the clearcase ucm baseline plugin.

        I am using

        Hudson ClearCase Plug-in ---  1.1.1
        Hudson UCM Baseline Plugin -- 1.2

        1. I quote the very top of this Wiki page:

          To use this plugin, you need to install the ClearCase Plugin (currently, version 1.0.x) since it relies on it. More precisely, the global configuration data is shared between the two plugins.

          ==> Either install an older version of the CC plugin or wait for the 1.3 release of CC UCM Baseline plugin to be released.

          1. Unknown User (vrspraveen.atluri@gmail.com)

            I downgraded the ClearCase Plugin to 1.0.x but still getting the same error. It is unable to read parameters in the build. below is the exception I am seeing when starting the build.Started by user anonymous
            ln failed: -1
            Parsing POMs
            ERROR: No such file /home/svcwps/.hudson/jobs/util-services/workspace/$

            Unknown macro: {CLEARCASE_VIEWPATH}

            /$

            Unknown macro: {CLEARCASE_VIEWNAME}

            /vob/MP2/UTILS/util-services/pom.xml
            Perhaps you need to specify the correct POM file path in the project configuration?
            Sending e-mails to: praveen.atluri@goAAA.pri
            Finished: FAILURE

            1. OK, so apparently this is not due to the plugin: Seems that the job you are building doesn't replace ${CLEARCASE_VIEWPATH} and ${CLEARCASE_VIEWNAME} with their actual values. I can't help on that since I don't use Maven, but try replacing the variables with their actual values.

              NB: I've released a new version of the plugin which should work fine with CC plugin 1.1

              1. Unknown User (vrspraveen.atluri@gmail.com)

                Hi Thank you for your quick response.

                I upgraded to 1.3 and cc plugin 1.1. It is trying to create a dynamic view in hudson workspace and It is deleting already existing snapshot view. Please let me know If there is any option for snapshot.
                workspace $ cleartool rmview -force praveen_test_view_hudson
                workspace $ cleartool mkview -tag praveen_test_view_hudson praveen_test_view_hudson
                Created view.
                Host-local path: n01apu411.1234.trt.1234.pri:/home/svcwps/.hudson/jobs/util-services_test/workspace/praveen_test_view_hudson
                Global path: /home/svcwps/.hudson/jobs/util-services_test/workspace/praveen_test_view_hudson
                It has the following rights:
                User : svcwps : rwx
                Group: grpccase : r-x
                Other: : r-x
                workspace $ cleartool lsbl -fmt %depends_on_closurep cUTILS_INITIAL@/vob/PVOB_MP2
                The view will be created based on the following config spec:
                — config spec start —
                element * CHECKEDOUT
                element //vob/MP2/UTILS/... cUTILS_INITIAL
                element * /main/0
                load //vob/MP2/UTILS
                — config spec end —
                praveen_test_view_hudson $ cleartool setcs ../configspec649938695585201611.txt
                cleartool: Error: Cannot get view info for current view: not a ClearCase object.
                FATAL: ClearCase UCM baseline failed. exit code=1
                ERROR: Failed to parse POMs
                java.io.IOException: cleartool did not return the expected exit code. Command line="setcs ../configspec649938695585201611.txt", actual exit code=1
                at hudson.plugins.clearcase.HudsonClearToolLauncher.run(HudsonClearToolLauncher.java:94)
                at com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearToolUcmBaseline.setcs(ClearToolUcmBaseline.java:281)
                at com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineParameterValue$2.setUp(ClearCaseUcmBaselineParameterValue.java:293)
                at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:408)
                at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
                at hudson.model.Run.run(Run.java:1198)
                at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
                at hudson.model.ResourceController.execute(ResourceController.java:88)
                at hudson.model.Executor.run(Executor.java:122)
                Finished: FAILURE

                1. The plugin does use snapshot views (which are recreated all the time unless you don't use the new Force rmview option), that's why it's doing cleartool rmview and then cleartool mkview.
                  The plugin currently (as of 1.3) doesn't support dynamic views.

                  Your issue is related to the content of the generated config spec:

                  element //vob/MP2/UTILS/... cUTILS_INITIAL
                  ...
                  load //vob/MP2/UTILS
                  

                  ==> There are two slashes before vob ==> The job is not properly set up.

                  1. Unknown User (vrspraveen.atluri@gmail.com)

                    1) Force rmview option is making no difference. Anyways It is trying to remove and recreate the view all the time

                    2)  when It is recreating the view It is trying to create the dynamic view as -snapshot option is missing in the below command.workspace $ cleartool rmview -force praveen_test_view_hudson
                    workspace $ cleartool mkview -tag praveen_test_view_hudsoon praveen_test_view_hudson
                         

                    1. Unknown User (vrspraveen.atluri@gmail.com)

                      Hello Seaguy,

                      I customized the plugin according to my requirements. Now every thing is good.

                      Thanks for this great and useful plugin.

                      1. Thanks.
                        Is it OK if you send me the changes you made so that I can include them in the source code (MIT license)? You can get my email address by taking a look at my wiki profile.

              2. Unknown User (vrspraveen.atluri@gmail.com)

                ClearCase UCM BASELINE plugin  is creating Dynamic view's by default. Is there any way to enable the snapshot option?

  4. Unknown User (jl.pinardon)

    Hi Mr Seaguy,

    I am currently evaluating Hudson in my company, and more specifically its integration features with ClearCase and UCM.
    Our configuration is :

    • Hudson               : 1.347
    • ClearCase Plugin : 1.1.1
    • UCM Plugin         : 1.3

    I am currently trying to configure the UCM Baseline plugins, and particularly on the fields to fill in the Add Parameter Section. Unless I have missed something, I think there are some issues :

    1. It seems the the pVOB must be entered with its heading /, but not the component vob tag.
      For example, if the vob tag is /myvob and I enter it as is, the generated config spec shows 2 /, i.e. //myvob.
      IMHA, the component vob tag and the pVOB vob tag should be treated equally.
    2. The component field waits for the component name.
      But it appears that this name is used in the config spec to build a rule. For example :

    element /mts_tst_src/COMP_Hudson_UCM_Test/... US1.3_With_Baselining-8

    Just as if the plugin assumes that a component has mandatorily the same name as its root directory. Which is not a clearcase rule.

    1. When setting the config spec, the command is :
    /usr/atria/bin/cleartool setcs ../configspec44660.txt
    

    But the tool is not in a view context.
    So perhaps it would be better to systematically call setcs with -tag <view name>.

    Nevertheless I could also have misunderstood some points. If it is the case, don't hesitate to give me the hints so that I can correctly configure the plugin.
    Thanks for the job, and your help.
    Best Regards.
    J.L.P.

    1. Thanks for your inputs, they're appreciated.

      • For point #3, I've committed a fix for the setcs command to use the -tag option.
      • For point #2, well, I'm not a ClearCase admin/expert but I'll take a look at the cleartool command to see if I can get separately the component name/root dir.
      • For point #1, I don't put '/' when I use the plugin and it works fine, but maybe I've misread you. Just tell me.
      1. Unknown User (jl.pinardon)

        Thanks for your help.

        • Point #3 : OK, I guess it will now work well
        • Point #2 : A solution is :
           cleartool lscomp -fmt "%[root_dir]p\n" <Component Name>
          
          And I  insist on the idea that you cannot assume that the component name is equal to the root dir. It is often something different.
        • Point #1 : Yes, I have unserstood that.
          But most of clearcase users will naturally fill the component vob name with the heading /. Moreover, the pVOB name must be filled with the heading /. So I think it would be really more consistent and easy to understand that both pVOB and component VOB be filled with the complete vob tag. It the usual way to do with clearcase vob tag.

        Thanks again, and best regards.
        J.L.P.

        1. I've committed the changes and will wait for Praveen Atluri to provide me with his changes before releasing 1.3.1 or 1.4.

  5. Bonjour Romain.

    We are using v1.5.1 of your plugin and 1.1.1 of the ClearCase plugin. It works nicely except for one little glitch that unfortunately makes it unusable here... It is caused by the way the plugin handles rootless components. The config specs generated by the plugin adds an invalid rule in the config specs for rootless components. This breaks the config specs and stops the process right there. The plugin should ignore rootless components when composing the config specs rules. In the sample below, the VSP4 component is rootless. Here is what I get:

    Started by user <user>
    Building remotely on <slave>
    [mg20.4-ucm] $ cleartool lscomp -fmt %[root_dir]p VSP4@\vsp4pvob
    [mg20.4-ucm] $ cleartool lsbl -fmt %[depends_on_closure]p VSP4_MG20.105.08.00.00.09@\vsp4pvob
    VSP4TOOLS_UCM_IMPORT_VSP4TOOLS_IMPORT@\vsp4pvob VSP4API_MG20.3_API_5.3.6@\vsp4pvob VSP4SOURCE_MG20.105.08.00.00.09@\vsp4pvob[mg20.4-ucm] $ cleartool lsbl -fmt %[component]p VSP4_MG20.105.08.00.00.09@\vsp4pvob
    VSP4[mg20.4-ucm] $ cleartool lsbl -fmt %[component]p VSP4TOOLS_UCM_IMPORT_VSP4TOOLS_IMPORT@\vsp4pvob
    VSP4TOOLS[mg20.4-ucm] $ cleartool lscomp -fmt %[root_dir]p VSP4TOOLS@\vsp4pvob
    \vsp4tools[mg20.4-ucm] $ cleartool lsbl -fmt %[component]p VSP4API_MG20.3_API_5.3.6@\vsp4pvob
    VSP4API[mg20.4-ucm] $ cleartool lscomp -fmt %[root_dir]p VSP4API@\vsp4pvob
    \vsp4api[mg20.4-ucm] $ cleartool lsbl -fmt %[component]p VSP4SOURCE_MG20.105.08.00.00.09@\vsp4pvob
    VSP4SOURCE[mg20.4-ucm] $ cleartool lscomp -fmt %[root_dir]p VSP4SOURCE@\vsp4pvob
    \vsp4sourceThe view will be created based on the following config spec:
    --- config spec start ---
    element * CHECKEDOUT
    element "\..." VSP4_MG20.105.08.00.00.09 -nocheckout
    element "\vsp4tools\..." VSP4TOOLS_UCM_IMPORT_VSP4TOOLS_IMPORT -nocheckout
    element "\vsp4api\..." VSP4API_MG20.3_API_5.3.6 -nocheckout
    element "\vsp4source\..." VSP4SOURCE_MG20.105.08.00.00.09 -nocheckout
    element * /main/0 -ucm -nocheckout
    load \vsp4source\dsp
    load \vsp4source\dsp
    ---  config spec end  ---
    [mg20.4-ucm__mgdsp-vista-1] $ cleartool setcs -tag mg20.4-ucm__mgdsp-vista-1 ..\configspec521091634415078695.txt
    cleartool: Error: No registered VOB tag in path: "/...".
    cleartool: Error: Config spec semantic processing failed.
    cleartool: Error: Unable to change configuration specification: error in configuration specification.
    

    Please note also that the load rules are duplicated.

    1. Hmmm, that can be easily fixed (although I don't see why the load rule gets duplicated – do you use the Restrict folders to field?).
      May you open a JIRA issue and assign it to me please? I'll try to fix that very soon (maybe tom), but as the update center is currently broken, it might take some time for the new release to get actually published.

      1. Yes, I do use the Restrict folders to field. But even if I leave that field empty I end up with duplicated load rules.

        As requested, I submitted a JIRA issue and assigned it to you: http://issues.jenkins-ci.org/browse/JENKINS-6398.

        Looking forward to a fix for this, as I foresee a wide usage of this plugin over here when it supports rootless components correctly.

  6. Unknown User (alexvai@amdocs.com)

    Hi,

     I customized your plugin :) Thanks.

    I have a question. How can i pass build parameters from index.jelly  as environment variables to Execute Shell or cmd?

    1. I'm not sure to understand your question. Have you taken a look at the way I handle the CLEARCASE_VIEWPATH, CLEARCASE_BASELINE, etc., env variables?

  7. I have having the original posted problem. Is there a solution that does not require using an older clearcase plugin?
    Thanks
    ClearCase plugin 1.2.1
    ClearCaseUCMplugin 1.5.1
    Started by user koesterb
    No emails were triggered.
    FATAL: com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineSCM cannot be cast to hudson.plugins.clearcase.ClearCaseUcmSCM
    java.lang.ClassCastException: com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineSCM cannot be cast to hudson.plugins.clearcase.ClearCaseUcmSCM
    at hudson.plugins.clearcase.ucm.UcmMakeBaseline.prebuild(UcmMakeBaseline.java:208)
    at hudson.model.AbstractBuild$AbstractRunner.preBuild(AbstractBuild.java:614)
    at hudson.model.AbstractBuild$AbstractRunner.preBuild(AbstractBuild.java:609)
    at hudson.model.AbstractBuild$AbstractRunner.preBuild(AbstractBuild.java:605)
    at hudson.model.Build$RunnerImpl.doRun(Build.java:120)
    at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
    at hudson.model.Run.run(Run.java:1241)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
    at hudson.model.ResourceController.execute(ResourceController.java:88)
    at hudson.model.Executor.run(Executor.java:124)

    1. Hi, this is because the version of the ClearCase UCM Baseline plugin you use is not compatible with the ClearCase plugin 1.2. There's a table at the top of this page which emphasizes compatibility. You need version 1.6 which I've not released yet, I'm waiting for some tests to end.

      1. Can I get a pre-release? I'd be happy to help you test it.

  8. Unknown User (vrspraveen.atluri@gmail.com)

    Hi Romain, I have a Master node on AIX and Slave Node on Windows. When ClearCase UCM plugin is ran on Slave node. It is getting the Cleartool value from the global configuration. Is there a release for adding an option to override the 'cleartool' location for slaves.

    1. Hi,

      Such a feature can't be part of this plug-in since the global configuration relies on the one of the ClearCase plug-in. I submitted a patch (JENKINS-5527) for the ClearCase plug-in some time ago but it's not been applied yet (I guess this is because it would make the new release of the ClearCase plug-in incompatible with current configurations). In the meantime, the best is to add cleartool to the PATH for all your nodes, master or slaves.

      1. Unknown User (vrspraveen.atluri@gmail.com)

        Hi Romain,

        I downloaded the patch (Hudson-5527) and  updated  the cleartool path for my nodes but CLEARCASE UCM BASELINE plugin is still looking at the global configuration.Can I get a temporary fix for this plugin?

        1. Well, maybe you can get the code by yourself and do the fix. Once the ClearCase plug-in integrates the feature, then I'll do a fix, but for the moment I won't (no time to do free consultancy services (smile) ).

          1. Unknown User (vrspraveen.atluri@gmail.com)

            Hi  Romain,  I customized the plugin for the moment to get going. Thanks very much (thumbs up)

  9. After supplying parameters PVOB, Component, Stream and View Name, when I click build, it shows empty drop-down for baselines.

    What could be the issue here? I am new to clearcase UCM. I am running jenkins on a windows machine.

    Appreciate your help.

    -Rajneesh

    1. The account used to run Hudson has the expected rights on the ClearCase server? Is your job assigned to a given node?

      1. Issue resolved. It was just a misconfiguration.

  10. still get the error when creating the view “cleartool mkview -tag $view-name $view-name" with plugin 1.7.3, additional view-name added at the end of command line, how to resolve it?

    1. Please fill a JIRA issue when reporting a problem, I've just sees your message now.

  11. Hi

    When trying to run job in CLI and need to provide baseline name parameter, got the following error:

    "CLI parameter submission is not supported for the class com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineParameterDefinition type.

    Please file a bug report for this."

    The command I use:

    c:\Jenkins>java -jar jenkins-cli.jar -s http://builder:8080/ build "Test_Job" -p "ClearCase UCM baseline=TestBL_03_04_12"

    Please advise.

    Thanks,

    Zeev

  12. Hello There, Is There a way to pass stream name using another string/CHoice Parameter to clearcase UCM parameters? I would liek to use same job for all env type builds where streams differ from each one.

    1. This is not supported, as your use case is not valid: You should have one dedicated job per stream.

  13. Did any one had a luck to use this plug in for continuous integration . I have error when i tried to do so.It can not pick baseline automatically.I tried with clearcase UCM plug in but its not linux compatible.

    1. The plugin doesn't retrieve baselines automatically. You must run the job manually and pick a baseline. This is not a matter of operating system, but an unsupported use case.

  14. Do we have environment variables similar to echo "CLEARCASE_BASELINE ,CLEARCASE_VIEWNAME and CLEARCASE_VIEWPATH " to echo stream name ,vob name and pvob name selected

    1. This is documented in the inline help: Click on the various blue interrogation mark icons and you'll see which variables are available. Basically, your need is covered, but read the documentation for know the variable names.

  15. Hello, 

    i think there is a bug in class ClearCaseUcmBaselineParameterDefinition. 

    The variable private transient DateFormat dateFormat = new SimpleDateFormat("yyyyMMdd.HHmmss") should not be transient, because when i set the job parameter Display baselines more recent than, and restart the hudson server, and i try to construct a job, the list of baselines will be empty until a enter in job configuration and save it.

    The above exception was throwed in my tests

    Caused by: java.lang.NullPointerException

    at com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineParameterDefinition$2.evaluate(ClearCaseUcmBaselineParameterDefinition.java:358)

    at org.apache.commons.collections.CollectionUtils.filter(CollectionUtils.java:405)

    at com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineParameterDefinition.getBaselines(ClearCaseUcmBaselineParameterDefinition.java:355)

    Caused by: java.lang.NullPointerException at com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineParameterDefinition$2.evaluate(ClearCaseUcmBaselineParameterDefinition.java:358) at org.apache.commons.collections.CollectionUtils.filter(CollectionUtils.java:405) at com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineParameterDefinition.getBaselines(ClearCaseUcmBaselineParameterDefinition.java:355)

  16. Hello, 

    i think there is a bug in class ClearCaseUcmBaselineParameterDefinition. 

    The variable private transient DateFormat dateFormat = new SimpleDateFormat("yyyyMMdd.HHmmss") should not be transient, because when i set the job parameter Display baselines more recent than, and restart the hudson server, and i try to construct a job, the list of baselines will be empty until a enter in job configuration and save it.

    The above exception was throwed in my tests

    Caused by: java.lang.NullPointerException

    at com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineParameterDefinition$2.evaluate(ClearCaseUcmBaselineParameterDefinition.java:358)

    at org.apache.commons.collections.CollectionUtils.filter(CollectionUtils.java:405)

    at com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineParameterDefinition.getBaselines(ClearCaseUcmBaselineParameterDefinition.java:355)

    Caused by: java.lang.NullPointerException at com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineParameterDefinition$2.evaluate(ClearCaseUcmBaselineParameterDefinition.java:358) at org.apache.commons.collections.CollectionUtils.filter(CollectionUtils.java:405) at com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineParameterDefinition.getBaselines(ClearCaseUcmBaselineParameterDefinition.java:355)