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

inaccurate change set reporting when using teamconcert plugin with multi-configuration projects

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: teamconcert-plugin
    • Labels:
      None
    • Environment:
      Jenkins (LTS 1.642.4), Multi-configuration project type, team concert plugin (latest, 1.2.0.0), RTC SCM 5.0.2
    • Similar Issues:

      Description

      Using the teamconcert plugin with Jenkins multi-configuration projects, there is a window (~1-3 minutes, depending how long it takes for the scm load and child builds to start) between when the "parent" build will accept incoming changes to the build work space, load the work space, reports the change set information in the parent build's "changes" interface, and when the "children" builds of the multi-configuration project start and do the same accept of incoming changes.

      If someone delivers a change set in between the parent accepting, and any of the children builds accepting, the parent will not know that the child build accepted another change into the work space, but the change was actually there.

      This makes it difficult for us to accurately know which build a change was in by looking at the parent build's 'changes' page (/job/continuous.dev/changes), more importantly, it can also mean that two 'child' builds will be building different content from each other.

      Note that normally 'child' builds report no change sets in their 'changes' interface, except when this race condition occurs, and in that situation the child build that accepted the change set will report the change set information in it's own 'changes' interface (it will not appear in /job/continuous.dev/changes, but in, for example /job/continuous.dev/label_exp=ppc64le/changes).

      Comparing our change set history in Jazz SCM to Jenkins, I see this happening approximately once per month for each stream we build, and it's particularly likely to happen when our Jenkins slaves are under heavy load.

        Attachments

          Activity

          Hide
          lvaikunt Lakshmi Narasimhan Vaikuntam added a comment -

          1.2.0.0 supports loading from a Jazz SCM snapshot. If the child builds are expected to build against same content, then it could be configured to load from a snapshot instead of a Jazz SCM workspace.

          https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin#TeamConcertPlugin-JobConfiguration

          One option here is to have a job to load from a Jazz SCM workspace. Then start the multi configuration job (which is configured to load from snapshot), passing the snapshot uuid through a parameter.

          Show
          lvaikunt Lakshmi Narasimhan Vaikuntam added a comment - 1.2.0.0 supports loading from a Jazz SCM snapshot. If the child builds are expected to build against same content, then it could be configured to load from a snapshot instead of a Jazz SCM workspace. https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin#TeamConcertPlugin-JobConfiguration One option here is to have a job to load from a Jazz SCM workspace. Then start the multi configuration job (which is configured to load from snapshot), passing the snapshot uuid through a parameter.
          Hide
          rkivisto Ray Kivisto added a comment -

          That should work, I'm glad this feature was added in the latest version. I will need to do extra coding to be able to switch, since our test automation and our developers rely on info in the change log, but this defect can be closed now.

          Show
          rkivisto Ray Kivisto added a comment - That should work, I'm glad this feature was added in the latest version. I will need to do extra coding to be able to switch, since our test automation and our developers rely on info in the change log, but this defect can be closed now.

            People

            Assignee:
            lvaikunt Lakshmi Narasimhan Vaikuntam
            Reporter:
            rkivisto Ray Kivisto
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: