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

Wrong Computer used for SCM polling

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • clearcase-plugin
    • None
    • Windows XP Pro and Server 2003.

    Description

      The clearcase plugin always uses the current computer for resolution of build variables rather than the Computer associated with the last build, even when polling on the last build's Computer. This causes polling to fail for us. We allow our jobs to roam freely in the cluster. But based on the code, even if the job was tied to a particular node and the node was not the master node, AND the view-name depends upon node-specific configuration, the polling fails.

      To let our jobs roam freely in the cluster, we introduced a node-specific attribute to the view name. Our views are all named ${SHORT_COMPUTERNAME}_${JOB_NAME}. SHORT_COMPUTERNAME is a parameter uniquely defined on each Node. This is so that clearcase doesn't complain when there are 2 views for the job in the cluster.

      hudson: 1.339
      clearcase: 1.1

      Attachments

        Activity

          PatrikSchalin PatrikSchalin added a comment -

          Is there a way to get hold of a build with this fix, we are currently suffering from this...

          PatrikSchalin PatrikSchalin added a comment - Is there a way to get hold of a build with this fix, we are currently suffering from this...
          dhauslad dhauslad added a comment -

          If your organization doesn't use either Maven 2 and Subversion, install them.

          Read these.

          http://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial
          http://wiki.jenkins-ci.org/display/JENKINS/Hints+for+plugin-development+newbies

          Do a Subversion update to get the latest to your machine. The url for the clearcase plugin is:

          https://svn.dev.java.net/svn/hudson/trunk/hudson/plugins/clearcase

          From the folder you create to house the plugin, do "mvn clean package" or "mvn package". I like to clean before every build because it updates the build timestamp that you see in the installed plugins tab in Hudson.

          The build creates a target folder inside the root one. It has the clearcase.hpi. You can either manually copy that to your plugins directory and restart Hudson or use the Hudson UI's pluginManager/advanced page to install it from the machine you build it on.

          Enjoy!

          dhauslad dhauslad added a comment - If your organization doesn't use either Maven 2 and Subversion, install them. Read these. http://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial http://wiki.jenkins-ci.org/display/JENKINS/Hints+for+plugin-development+newbies Do a Subversion update to get the latest to your machine. The url for the clearcase plugin is: https://svn.dev.java.net/svn/hudson/trunk/hudson/plugins/clearcase From the folder you create to house the plugin, do "mvn clean package" or "mvn package". I like to clean before every build because it updates the build timestamp that you see in the installed plugins tab in Hudson. The build creates a target folder inside the root one. It has the clearcase.hpi. You can either manually copy that to your plugins directory and restart Hudson or use the Hudson UI's pluginManager/advanced page to install it from the machine you build it on. Enjoy!
          abayer Andrew Bayer added a comment -

          Also, FYI, I'll be pushing a release of 1.1.1 (http://wiki.jenkins-ci.org/display/JENKINS/ClearCase+Plugin#ClearCasePlugin-Version1.1.1) by the end of the week. I just want to make sure I catch as many of the easy-to-fix 1.0->1.1 bugs as possible.

          abayer Andrew Bayer added a comment - Also, FYI, I'll be pushing a release of 1.1.1 ( http://wiki.jenkins-ci.org/display/JENKINS/ClearCase+Plugin#ClearCasePlugin-Version1.1.1 ) by the end of the week. I just want to make sure I catch as many of the easy-to-fix 1.0->1.1 bugs as possible.
          dhauslad dhauslad added a comment -

          I look forward to the 1.1.1 release! I really appreciate your responsiveness on this stuff. Sorry about hounding you about 2934 (I'm a newbie to JIRA and SVN) and didn't get the notification (or notice) your comment on it.

          As a quick sanity check, I diffed our versions of the key files and found only one diff that I think will cause me a problem. On version 25724 of AbstractClearCaseSCM, you have generateNormalizedViewName(lastBuild) whereas I have generateNormalizedViewName(variableResolver). I think this will make a difference because the signature you're using defaults to the current computer when constructing a BuildVariableResolver. I need it to be the computer from the last build.

          dhauslad dhauslad added a comment - I look forward to the 1.1.1 release! I really appreciate your responsiveness on this stuff. Sorry about hounding you about 2934 (I'm a newbie to JIRA and SVN) and didn't get the notification (or notice) your comment on it. As a quick sanity check, I diffed our versions of the key files and found only one diff that I think will cause me a problem. On version 25724 of AbstractClearCaseSCM, you have generateNormalizedViewName(lastBuild) whereas I have generateNormalizedViewName(variableResolver). I think this will make a difference because the signature you're using defaults to the current computer when constructing a BuildVariableResolver. I need it to be the computer from the last build.
          abayer Andrew Bayer added a comment -

          You're right - I just blanked on that. It's in now.

          abayer Andrew Bayer added a comment - You're right - I just blanked on that. It's in now.

          People

            abayer Andrew Bayer
            dhauslad dhauslad
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: