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

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

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • clearcase-plugin
    • None
    • linux, clearcase v7

    Description

      I have declared a clearcase label in an environment variable:
      latestXsatLabel=XSAT_V04_14
      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

      Attachments

        Activity

          fine, I'll fix that as well tomorrow. Thanks for your feedback!

          vlatombe Vincent Latombe added a comment - fine, I'll fix that as well tomorrow. Thanks for your feedback!

          Could you please try with this new build?

          vlatombe Vincent Latombe added a comment - Could you please try with this new build ?

          Code changed in jenkins
          User: Vincent Latombe
          Path:
          src/main/java/hudson/plugins/clearcase/ClearCaseSCM.java
          src/test/java/hudson/plugins/clearcase/ClearCaseSCMTest.java
          http://jenkins-ci.org/commit/clearcase-plugin/ab085df2c806e01d1b5f84029778da904bf9cae9
          Log:
          JENKINS-21626 Resolve parameters in config spec when checking if
          config spec has changed.

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Vincent Latombe Path: src/main/java/hudson/plugins/clearcase/ClearCaseSCM.java src/test/java/hudson/plugins/clearcase/ClearCaseSCMTest.java http://jenkins-ci.org/commit/clearcase-plugin/ab085df2c806e01d1b5f84029778da904bf9cae9 Log: JENKINS-21626 Resolve parameters in config spec when checking if config spec has changed.

          I just tried version 05/Feb/14.
          It works fine !

          vnouguier Vincent Nouguier added a comment - I just tried version 05/Feb/14. It works fine !
          vlatombe Vincent Latombe added a comment - - edited

          Released in 1.5

          vlatombe Vincent Latombe added a comment - - edited Released in 1.5

          People

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

            Dates

              Created:
              Updated:
              Resolved: