Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-21626

Permanent build due to the use of an environment variable in config spec


    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • clearcase-plugin
    • None
    • linux, clearcase v7

      I have declared a clearcase label in an environment variable:
      I use this variable in a job's config spec.
      The job is configured to Poll SCM every 3 minutes.
      A build is triggered every time with the following reason :
      [WARNING] CSPEC configured != catcs (view)
      REASON: New config spec detected.
      It worked fine with plugin 1.3.6 or 1.3.4 (don't remember), ko with 1.4

      here is the complete polling log :

      Started on Feb 3, 2014 12:44:13 PM
      Polling SCM changes on master
      Checking if build is running
      Checking if a build has already happened
      Checking if revision state is known
      Checking if we have a build with a valid workspace

                                                          • get view CSPEC ***********************
                                                            [workspace] $ /usr/atria/bin/cleartool catcs -tag catalogservices_deploy-xsat-packages-and-models_jenkins
                                                            element /vobng/catalog_services/ main/LATEST
                                                            element /vobng/catalog_services/xsat/... main/LATEST

      element /vobng/smstk /main/LATEST -nocheckout
      element /vobng/smstk/maven/... XSAT_V04_14 -nocheckout

      [WARNING] CSPEC configured != catcs (view)
      REASON: New config spec detected.
      Done. Took 52 ms
      Changes found

            vlatombe Vincent Latombe
            vnouguier Vincent Nouguier
            0 Vote for this issue
            3 Start watching this issue