• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest
    • 2.2
    • 2.2
    • User Interface
    • None

      Our windows installer build (https://jira2.bamboo.atlassian.com/browse/JWI-ENT) has it's test-reports directory set to: subprojects/installer/target/TEST*.xml

      For some reason since the Bamboo upgrade to 2.2-SNAPSHOT, this was reset back to */test-reports/.xml. I also can't change it back now. It always defaults back to */test-reports/.xml.

      Can this be fixed ASAP please since our windows installer build is failing because of it .

            [BAM-3183] Test results directory can't be updated

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 1433467 ] New: JAC Bug Workflow v3 [ 3378945 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Bamboo Workflow 2016 v1 [ 1406911 ] New: Bamboo Workflow 2016 v1 - Restricted [ 1433467 ]
            Marek Went (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2014 v2 [ 607226 ] New: Bamboo Workflow 2016 v1 [ 1406911 ]
            James Dumay made changes -
            Workflow Original: Bamboo Workflow 2014 [ 595200 ] New: Bamboo Workflow 2014 v2 [ 607226 ]
            James Dumay made changes -
            Workflow Original: Bamboo Workflow 2010 [ 201356 ] New: Bamboo Workflow 2014 [ 595200 ]
            MarkC made changes -
            Workflow Original: reviewflow [ 164340 ] New: Bamboo Workflow 2010 [ 201356 ]
            MarkC made changes -
            Workflow Original: jira [ 147533 ] New: reviewflow [ 164340 ]
            MarkC made changes -
            Fix Version/s New: 2.2 [ 14112 ]
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            MarkC added a comment -

            Should now be sorted for a BEAC & J2BAC

            MarkC added a comment - Should now be sorted for a BEAC & J2BAC

            Don Willis added a comment -

            Not only do we continue to have this problem, but after the workaround it keeps reverting to the default, test-results, all by itself.
            I suspect there's a weirdness because we're invoking maven through a script. Even when we've had the setting undisturbed for a while, we've received this message:

            Could not find ant Junit test results in the /opt/j2ee/domains/bamboo.atlassian.com/confluence/webapps/atlassian-bamboo/data/current/xml-data/build-dir/CONFFUNC-SELENIUMFF directory.

            Obviously, since we don't have any ant results this sort-of makes sense, but doesn't help us. (And this Plan was working before, although I can't guarantee the configuration hasn't changed in some other weird way since the last working build)

            Don Willis added a comment - Not only do we continue to have this problem, but after the workaround it keeps reverting to the default, test-results, all by itself. I suspect there's a weirdness because we're invoking maven through a script. Even when we've had the setting undisturbed for a while, we've received this message: Could not find ant Junit test results in the /opt/j2ee/domains/bamboo.atlassian.com/confluence/webapps/atlassian-bamboo/data/current/xml-data/build-dir/CONFFUNC-SELENIUMFF directory. Obviously, since we don't have any ant results this sort-of makes sense, but doesn't help us. (And this Plan was working before, although I can't guarantee the configuration hasn't changed in some other weird way since the last working build)

              mark@atlassian.com MarkC
              andreask@atlassian.com Andreas Knecht (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: