CQ ATs are not configured to run properly in other pipelines

XMLWordPrintable

    • Severity 3 - Minor

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      The CQ ATs, when running as part of the Manifesto pipeline, show an issue with the Crowd URL (the proxy actually), as we can see in: https://confluence-bamboo.internal.atlassian.com/build/result/viewBuildResultsQuarantinedTests.action?buildKey=CONFREL-CONFODREL-DTA&buildNumber=371.

      They don't work in the TC pipeline: https://confluence-bamboo.internal.atlassian.com/browse/TEAMCAL-MP-14/test

      They run properly in the CQ pipeline though: https://confluence-bamboo.internal.atlassian.com/browse/CONFQ-PIPE-221

      And they do work on the JIM pipeline: https://confluence-bamboo.internal.atlassian.com/browse/COATHANGER-JIMP-65/test

      As we spoke, it might be related to the Crowd proxy being already installed in the instance when CQ runs the tests, so it's related to the test order if they pass or not. If we move CQ to use the ssh-tunnel, this problem will disappear.

      // cc drichard

              Assignee:
              sthr (Inactive)
              Reporter:
              sthr (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: