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

CC_BASELINE doesn't update value

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I am triggering a downstream job and passing CC_BASELINE as a parameter.

      Each time the parent view updates and builds properly

      from the polling log -
      Started on Feb 10, 2012 4:36:22 PM
      [CCUCM] Getting baselines for :
      [CCUCM] * Stream: ECLPS_Feb12_Int@\ECLPS_PVOB
      [CCUCM] * Component: eclps_src@\ECLPS_PVOB
      [CCUCM] * Promotion level: ANY

      [CCUCM] polling streams: self
      The last baseline: baseline:BUILDBOX_2012_02_10_13_19_01@\ECLPS_PVOB:

      • Shortname: BUILDBOX_2012_02_10_13_19_01
      • PVOB : \ECLPS_PVOB
      • Type : Baseline
      • Level : BUILT
      • Component: component:eclps_src@\ECLPS_PVOB
      • Stream : stream:ECLPS_Feb12_Int@\ECLPS_PVOB
      • Date : Fri Feb 10 13:19:02 EST 2012

      The found baseline: baseline:BUILDBOX_2012_02_10_16_19_01@\ECLPS_PVOB:

      • Shortname: BUILDBOX_2012_02_10_16_19_01
      • PVOB : \ECLPS_PVOB
      • Type : Baseline
      • Level : BUILT
      • Component: component:eclps_src@\ECLPS_PVOB
      • Stream : stream:ECLPS_Feb12_Int@\ECLPS_PVOB
      • Date : Fri Feb 10 16:19:03 EST 2012

      but the value passed in CC_BASELINE is baseline:BUILDBOX_2012_02_07_14_19_00@\ECLPS_PVOB

      That baseline seems to have been the baseline first built by the parent stream.

      Is CC_BASELINE updating for other people?

      Tim

        Attachments

          Activity

          Hide
          wolfgang Christian Wolfgang added a comment -

          What version of the plugin are you using?

          Has this always been an issue?

          Show
          wolfgang Christian Wolfgang added a comment - What version of the plugin are you using? Has this always been an issue?
          Hide
          phx_collier Tim Collier added a comment -

          jenkins 1.447 ucm 1.0.5 and I have just started with jenkins (transitioning from bamboo)

          entirely possible that this is a configuration issue, but it seems pretty straightforward

          "trigger parameterized build on other projects"
          Predefined parameters
          CC_BASELINE=${CC_BASELINE}

          Show
          phx_collier Tim Collier added a comment - jenkins 1.447 ucm 1.0.5 and I have just started with jenkins (transitioning from bamboo) entirely possible that this is a configuration issue, but it seems pretty straightforward "trigger parameterized build on other projects" Predefined parameters CC_BASELINE=${CC_BASELINE}
          Hide
          phx_collier Tim Collier added a comment -

          I am re-running the build after removing the parameter from the "predefined parameters" and just passing it as part of the "current build parameters"

          It might be that predefined are eveluated once upon setup and "current" passes the current value.

          It's a guess, but might make sense.

          Show
          phx_collier Tim Collier added a comment - I am re-running the build after removing the parameter from the "predefined parameters" and just passing it as part of the "current build parameters" It might be that predefined are eveluated once upon setup and "current" passes the current value. It's a guess, but might make sense.
          Hide
          phx_collier Tim Collier added a comment -

          that didn't work either as the CC_BASELINE value is not a parameter to the current build but a value set by the current build

          any ideas?

          Show
          phx_collier Tim Collier added a comment - that didn't work either as the CC_BASELINE value is not a parameter to the current build but a value set by the current build any ideas?
          Hide
          phx_collier Tim Collier added a comment -

          i think this is the unexpected way that the parameterized plugin works -

          Peter Schuetze -"...The parameter is just exposed as a simple environment variable, which usually can not be persisted in a way, that it survives the current shell session. You have the same issue when changing or creating new environment variables. They also don't survive the build step."

          I think this is probably why there is a special parameter setup for Subversion revision.

          this is not an issue with cm plugin

          Sorry for the churn

          Show
          phx_collier Tim Collier added a comment - i think this is the unexpected way that the parameterized plugin works - Peter Schuetze -"...The parameter is just exposed as a simple environment variable, which usually can not be persisted in a way, that it survives the current shell session. You have the same issue when changing or creating new environment variables. They also don't survive the build step." I think this is probably why there is a special parameter setup for Subversion revision. this is not an issue with cm plugin Sorry for the churn
          Hide
          jbrejner Jens Brejner added a comment -

          Hi Tim.

          Is this still an issue for you ? I think it is possible, so please let me know if I should look into it.

          Show
          jbrejner Jens Brejner added a comment - Hi Tim. Is this still an issue for you ? I think it is possible, so please let me know if I should look into it.

            People

            Assignee:
            wolfgang Christian Wolfgang
            Reporter:
            wolfgang Christian Wolfgang
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: