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

Bamboo Variables are not expanded in MSTest results path definition

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Low Low
    • 3.2 M0, 3.2
    • 2.7.3
    • None
    • None

      In a MSBuild/NANT/devenv.com builder, if the Test Result Files location include a Bamboo variable, the variable is not expanded and bamboo will not be able to find the file.

      Example:

      [AbstractDotNetBuilder] Processing test results in:E:\bamboo-home\xml-data\build-dir\131073\PROJ-PLAN-JOB1 with path: TestResults-${bamboo.buildNumber}.trx

            [BAM-8230] Bamboo Variables are not expanded in MSTest results path definition

            Marcin Gardias added a comment -

            MSTest Runner introduced in 3.1 does not have this problem

            Marcin Gardias added a comment - MSTest Runner introduced in 3.1 does not have this problem

            Renan Battaglin added a comment -

            Ensure that this will be reviewed for all builders.

            Renan Battaglin added a comment - Ensure that this will be reviewed for all builders.

            Renan Battaglin added a comment -

            A possible workaround to keep the XML files would be to set them as Artifacts so that Bamboo can save them, however they will not be stored in a "unique folder" that can identify the tests as being from an specific build and allow Bamboo to find them without having to specify a variable in the Test Results location field.

            Renan Battaglin added a comment - A possible workaround to keep the XML files would be to set them as Artifacts so that Bamboo can save them, however they will not be stored in a "unique folder" that can identify the tests as being from an specific build and allow Bamboo to find them without having to specify a variable in the Test Results location field.

            Renan Battaglin added a comment -

            Currently, the lack of variable expansion don't allow plans to keep a history of the test results.

            If the results are always created in the same folder and are are not cleaned between builds, all builds will have access to all the results accumulated from the previous builds.

            The variable expansion is essential to allow builds to keep the results separated per build and readable per build.

            Renan Battaglin added a comment - Currently, the lack of variable expansion don't allow plans to keep a history of the test results. If the results are always created in the same folder and are are not cleaned between builds, all builds will have access to all the results accumulated from the previous builds. The variable expansion is essential to allow builds to keep the results separated per build and readable per build.

              mgardias Marcin Gardias
              rbattaglin Renan Battaglin
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: