Gitlab CI Artifacts永久移动错误301？

我刚刚完成设置Gitlab Ci以使用Maven 3和Java 8的Docker容器来构建我的项目。然而，当我尝试将生成的jar文件保存为工件时，构建成功完成，Docker告诉我，找到jar文件后，工件已被永久移动....Gitlab CI Artifacts永久移动错误301？

这一个让我挠了挠头。

这里是我的Giitlab CI YML文件：

image: kaiwinter/docker-java8-maven 

before_script: 
    - apt-get update --fix-missing 
    - apt-get install -y git 
    - git clone -v https://github.com/stefaneidelloth/javafx-d3.git /builds/external/javafxd3 
    - cd /builds/external/javafxd3/javafx-d3 
    - mvn install 
    - cd /builds/external/myDemo 


build: 
script: "mvn -B install" 
tags: 
    - java8 
    - maven3 
artifacts: 
    paths: 
    - target/*.jar

这是从工作控制台的最后几行。

[INFO] BUILD SUCCESS 
[INFO] ------------------------------------------------------------------------ 
[INFO] Total time: 15.547 s 
[INFO] Finished at: 2017-04-06T17:58:06+00:00 
[INFO] Final Memory: 34M/462M 
[INFO] ------------------------------------------------------------------------ 
Uploading artifacts... 
target/*.jar: found 1 matching files    
WARNING: Uploading artifacts to coordinator... failed id=105 responseStatus=301 Moved Permanently status=301 Moved Permanently token=4pf6n8aT 
WARNING: Retrying...        
WARNING: Uploading artifacts to coordinator... failed id=105 responseStatus=301 Moved Permanently status=301 Moved Permanently token=4pf6n8aT 
WARNING: Retrying...        
WARNING: Uploading artifacts to coordinator... failed id=105 responseStatus=301 Moved Permanently status=301 Moved Permanently token=4pf6n8aT 
FATAL: invalid argument        
Job succeeded

来源

2017-04-06 Setix

我能解决这个问题。显然，码头容器虽然可以ping gitlab主机，但无法解析运行程序中指定的工件上传器域名。我将/etc/gitlab-runner/config.toml中的runner配置更改为主机的IP，并且工件复制得很好。

来源

2017-04-06 19:52:54 Setix

Gitlab CI Artifacts永久移动错误301？

回答

相关问题