Artifact copier does not handle '301 Moved Permanently'

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Low
    • None
    • Affects Version/s: 2.3 M9, 6.4.2, 6.7.2
    • Component/s: Artifacts
    • Severity 3 - Minor

      When jira2.bamboo.atlassian.com was renamed jira.bamboo.atlassian.com the artifact copier stopped working (though the builds still passed):

      Failed to execute plugin 'Artifact Copier' with error: java.io.IOException: Unexpected HTTP status code: 301 Moved Permanently

      What happened is that jira2.bamboo.atlassian.com is now redirecting to jira.bamboo.atlassian.com and the agents are still (mis-)configured to communicate to https://jira2.bamboo.atlassian.com/agentServer/. The agents seem to handle the redirect correctly, but the artifact copier does not.

            Assignee:
            Unassigned
            Reporter:
            bain
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: