Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-3595

Provide more build-specific variables

XMLWordPrintable

    • 0
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently only "custom.p4.revision.number" is available.

      It would be great if bamboo's perforce module could additionally provide:

      • custom.p4.port - Perforce server as specified in the plan configuration
      • custom.p4.client - Perforce clientname (workspace) as specified in the plan configuration
      • custom.p4.username - Perforce username as specified in the plan configuration
      • custom.p4.revision.previous - The change set number of the previous build (or 0 for initial builds).

      We have a number of tests that work directly on the perforce-depot (e.g. doing commit statistics, checks etc.).
      Without those variables we would have to specify them a second time (e.g. in the plan's builder arguments).

      In addition it would be great to also have global variables for:

      • buildForceClean - The flag "Force Clean Build"
      • buildTimeStamp - The build's start time
      • projectKey - From "Plan Details"
      • projectName - From "Plan Details"

            Unassigned Unassigned
            37f99458018f Stefan Brabec
            Votes:
            5 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: