ClearCase UCM Baseline Plugin

New homepage
This plug-in is being maintained by its owner/maintainers from a new home. The plug-in is still compatible with Hudson, however, the entry points for documentation and issue reporting have been combined in order to provide a single point of entry.

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

Plugin ID clearcase-ucm-baseline
Latest Release 1.7.4
Latest Release Date Sep 19, 2011
Plugin Central Plugin Central 3.2
Sources [External]
Support Eclipse Hudson Forum
Issue Tracking Eclipse Bugzilla
Hudson Core (latest) 3.3.3


Quick Overview

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.

Labels:

plugin-scm-related plugin-scm-related Delete
tier3-compat-plugin tier3-compat-plugin Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.
  1. Feb 17, 2010

    Patrick Renaud says:

    I just cannot get this plugin to work. I always end up with: Started by user l...

    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. Feb 18, 2010

      Romain Seguy says:

      Which version of the ClearCase plugin do you use? I've tested it against 1.0.2. ...

      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. Feb 18, 2010

        Patrick Renaud says:

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

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

        1. Feb 18, 2010

          Romain Seguy says:

          I've sent on your mail an upward compatible version for the ClearCase plugin 1.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. Feb 22, 2010

    Praveen Atluri says:

    I am trying to build the code using baseline. but Its not creating the snapshot ...

    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. Feb 22, 2010

    Praveen Atluri says:

    I am using ClearCase UCM baseline plugin 1.2 with hudson version 1.346. It is no...

    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. Feb 23, 2010

      Romain Seguy says:

      Any logs? The information you provide is not enough to get help... But I guess y...

      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. Feb 23, 2010

        Praveen Atluri says:

        This uis what I see in tomcat logs. Feb 23, 2010 11:39:47 AM org.apache.tomcat...

        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. Feb 23, 2010

          Romain Seguy says:

          I quote the very top of this Wiki page: To use this plugin, you need to install...

          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. Feb 23, 2010

            Praveen Atluri says:

            I downgraded the ClearCase Plugin to 1.0.x but still getting the same error. It ...

            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. Feb 24, 2010

              Romain Seguy says:

              OK, so apparently this is not due to the plugin: Seems that the job you are buil...

              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. Feb 25, 2010

                Praveen Atluri says:

                Hi Thank you for your quick response. I upgraded to 1.3 and cc plugin 1.1. It i...

                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_closure]p 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. Feb 26, 2010

                  Romain Seguy says:

                  The plugin does use snapshot views (which are recreated all the time unless you ...

                  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. Feb 26, 2010

                    Praveen Atluri says:

                    1) Force rmview option is making no difference. Anyways It is trying to remove a...

                    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. Feb 27, 2010

                      Praveen Atluri says:

                      Hello Seaguy, I customized the plugin according to my requirements. Now every ...

                      Hello Seaguy,

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

                      Thanks for this great and useful plugin.

                      1. Mar 01, 2010

                        Romain Seguy says:

                        Thanks. Is it OK if you send me the changes you made so that I can include them ...

                        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. Feb 25, 2010

                Praveen Atluri says:

                ClearCase UCM BASELINE plugin  is creating Dynamic view's by default. Is th...

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

  4. Mar 01, 2010

    Jean-Luc Pinardon says:

    Hi Mr Seaguy, I am currently evaluating Hudson in my company, and more specific...

    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. Mar 01, 2010

      Romain Seguy says:

      Thanks for your inputs, they're appreciated. For point #3, I've committed a fi...

      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. Mar 01, 2010

        Jean-Luc Pinardon says:

        Thanks for your help. Point #3 : OK, I guess it will now work well Point #2 ...

        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. Mar 01, 2010

          Romain Seguy says:

          I've committed the changes and will wait for Praveen Atluri to provide me with h...

          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. Apr 29, 2010

    Patrick Renaud says:

    Bonjour Romain. We are using v1.5.1 of your plugin and 1.1.1 of the ClearCase p...

    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. Apr 29, 2010

      Romain Seguy says:

      Hmmm, that can be easily fixed (although I don't see why the load rule gets dupl...

      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. Apr 29, 2010

        Patrick Renaud says:

        Yes, I do use the Restrict folders to field. But even if I leave that field empt...

        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.hudson-ci.org/browse/HUDSON-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. Jun 14, 2010

    Alex Vainshtein says:

    Hi,  I customized your plugin :) Thanks. I have a question. How can i pas...

    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. Jun 14, 2010

      Romain Seguy says:

      I'm not sure to understand your question. Have you taken a look at the way I han...

      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. Jun 15, 2010

    bill koester says:

    I have having the original posted problem. Is there a solution that does not req...

    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. Jun 16, 2010

      Romain Seguy says:

      Hi, this is because the version of the ClearCase UCM Baseline plugin you use is ...

      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. Jun 16, 2010

        bill koester says:

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

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

  8. Jul 01, 2010

    Praveen Atluri says:

    Hi Romain, I have a Master node on AIX and Slave Node on Windows. When ClearCase...

    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. Jul 01, 2010

      Romain Seguy says:

      Hi, Such a feature can't be part of this plug-in since the global configuration...

      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 (HUDSON-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. Jul 02, 2010

        Praveen Atluri says:

        Hi Romain, I downloaded the patch (Hudson-5527) and  updated  the cle...

        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. Jul 01, 2010

          Romain Seguy says:

          Well, maybe you can get the code by yourself and do the fix. Once the ClearCase ...

          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 ).

          1. Jul 02, 2010

            Praveen Atluri says:

            Hi  Romain,  I customized the plugin for the moment to get going. Than...

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

  9. Feb 04, 2011

    Eli says: