-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
2.3 M9, 6.4.2, 6.7.2
-
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.
- duplicates
-
BAM-21709 Bamboo Agent will not follow HTTP redirects whilst uploading artifacts back to Bamboo Server.
-
- Closed
-
[BAM-4268] Artifact copier does not handle '301 Moved Permanently'
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
Status | Original: Short Term Backlog [ 12074 ] | New: Gathering Impact [ 12072 ] |
Status | Original: Gathering Impact [ 12072 ] | New: Short Term Backlog [ 12074 ] |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1436425 ] | New: JAC Bug Workflow v3 [ 3385940 ] |
Status | Original: Open [ 1 ] | New: Needs Triage [ 10030 ] |
Fix Version/s | Original: 5.10.0 [ 54320 ] | |
Fix Version/s | Original: 5.9.7 [ 58593 ] |
Assignee | Original: Przemek Bruski [ pbruski ] |
Labels | New: bamboo-bugfix-kanban |
To be worked on https://jira.atlassian.com/browse/BAM-21709