基于源码构建，1.8jdk报错

[13813586515]

Describe the bug
基于源码构建多模块的包，选择openjdk1.8，报错

To Reproduce
Steps to reproduce the behavior:
1.拉取多模块代码
2.选择其中一个模块
3.点击构建
4.构建失败报错

Screenshots

The relevant information:

• Rainbond Version [e.g. v6.1.1]
• Browser [chrome] (if it is the front-end bugs, please provide)

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Title: Built based on source code, 1.8jdk reports an error

[zzzhangqi]

@13813586515 这种情况是无法通过 buildpack.rainbond.com 获取在线构建包资源

1. 看 Gateway 日志，buildpack.rainbond.com 是通过 Gateway 代理的。

kubectl logs -fl name=rbd-gateway -n rbd-system apisix

2. 使用以下命令检查域名是不是 buildpack.rainbond.com

kubectl get apisixupstream -n rbd-system buildpack-upstream

kubectl get apisixroute -n rbd-system lang-proxy

3. 如果域名不对，检查 rainbond-operator 版本是否为 v6.1.1-release

kubectl get deploy rainbond-operator -n rbd-system -o yaml | grep image

4. 如果 rainbond-operator 版本不是最新，修改镜像为最新版本 v6.1.1-release

kubectl edit deploy rainbond-operator -n rbd-system

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

@13813586515 In this case, it is impossible to obtain online build package resources through buildpack.rainbond.com

1. Looking at the Gateway log, buildpack.rainbond.com is proxied through the Gateway.

kubectl logs -fl name=rbd-gateway -n rbd-system apisix

2. Use the following command to check whether the domain name is buildpack.rainbond.com

kubectl get apisixupstream -n rbd-system buildpack-upstream

kubectl get apisixroute -n rbd-system lang-proxy

3. If the domain name is incorrect, check whether the rainbond-operator version is v6.1.1-release

kubectl get deploy rainbond-operator -n rbd-system -o yaml | grep image

4. If the rainbond-operator version is not the latest, modify the image to the latest version v6.1.1-release

kubectl edit deploy rainbond-operator -n rbd-system

[13813586515]

@13813586515 这种情况是无法通过 buildpack.rainbond.com 获取在线构建包资源

1. 看 Gateway 日志，buildpack.rainbond.com 是通过 Gateway 代理的。

kubectl logs -fl name=rbd-gateway -n rbd-system apisix
2. 使用以下命令检查域名是不是 buildpack.rainbond.com

kubectl get apisixupstream -n rbd-system buildpack-upstream
kubectl get apisixroute -n rbd-system lang-proxy
3. 如果域名不对，检查 rainbond-operator 版本是否为 v6.1.1-release

kubectl get deploy rainbond-operator -n rbd-system -o yaml | grep image
4. 如果 rainbond-operator 版本不是最新，修改镜像为最新版本 v6.1.1-release

kubectl edit deploy rainbond-operator -n rbd-system

发现确实是升级到6.1.1之后 operator 还在6.1.0，但是现在dockerhub无法连接，没法拉取6.1.1的镜像

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

@13813586515 In this case, it is impossible to obtain online build package resources through buildpack.rainbond.com

1. Looking at the Gateway log, buildpack.rainbond.com is proxied through the Gateway.

kubectl logs -fl name=rbd-gateway -n rbd-system apisix
2. Use the following command to check whether the domain name is buildpack.rainbond.com

kubectl get apisixupstream -n rbd-system buildpack-upstream
kubectl get apisixroute -n rbd-system lang-proxy
3. If the domain name is incorrect, check whether the rainbond-operator version is v6.1.1-release

kubectl get deploy rainbond-operator -n rbd-system -o yaml | grep image
4. If the rainbond-operator version is not the latest, modify the image to the latest version v6.1.1-release

kubectl edit deploy rainbond-operator -n rbd-system

I found that after upgrading to 6.1.1, the operator is still in 6.1.0, but now dockerhub cannot connect and cannot pull the 6.1.1 image.

[zzzhangqi]

@13813586515 这种情况是无法通过 buildpack.rainbond.com 获取在线构建包资源

1. 看 Gateway 日志，buildpack.rainbond.com 是通过 Gateway 代理的。

kubectl logs -fl name=rbd-gateway -n rbd-system apisix
2. 使用以下命令检查域名是不是 buildpack.rainbond.com
kubectl get apisixupstream -n rbd-system buildpack-upstream
kubectl get apisixroute -n rbd-system lang-proxy
3. 如果域名不对，检查 rainbond-operator 版本是否为 v6.1.1-release
kubectl get deploy rainbond-operator -n rbd-system -o yaml | grep image
4. 如果 rainbond-operator 版本不是最新，修改镜像为最新版本 v6.1.1-release
kubectl edit deploy rainbond-operator -n rbd-system

发现确实是升级到6.1.1之后 operator 还在6.1.0，但是现在dockerhub无法连接，没法拉取6.1.1的镜像

@13813586515 使用国内镜像：registry.cn-hangzhou.aliyuncs.com/goodrain/rainbond-operator:v6.1.1-release

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

@13813586515 In this case, it is impossible to obtain online build package resources through buildpack.rainbond.com

1. Looking at the Gateway log, buildpack.rainbond.com is proxied through the Gateway.

kubectl logs -fl name=rbd-gateway -n rbd-system apisix
2. Use the following command to check whether the domain name is buildpack.rainbond.com
kubectl get apisixupstream -n rbd-system buildpack-upstream
kubectl get apisixroute -n rbd-system lang-proxy
3. If the domain name is incorrect, check whether the rainbond-operator version is v6.1.1-release
kubectl get deploy rainbond-operator -n rbd-system -o yaml | grep image
4. If the rainbond-operator version is not the latest, modify the image to the latest version v6.1.1-release
kubectl edit deploy rainbond-operator -n rbd-system

Found that after upgrading to 6.1.1, the operator is still in 6.1.0, but now dockerhub cannot connect and cannot pull the 6.1.1 image

@13813586515 Use domestic mirror: registry.cn-hangzhou.aliyuncs.com/goodrain/rainbond-operator:v6.1.1-release

[13813586515]

@13813586515 这种情况是无法通过 buildpack.rainbond.com 获取在线构建包资源

1. 看 Gateway 日志，buildpack.rainbond.com 是通过 Gateway 代理的。

kubectl logs -fl name=rbd-gateway -n rbd-system apisix
2. 使用以下命令检查域名是不是 buildpack.rainbond.com
kubectl get apisixupstream -n rbd-system buildpack-upstream
kubectl get apisixroute -n rbd-system lang-proxy
3. 如果域名不对，检查 rainbond-operator 版本是否为 v6.1.1-release
kubectl get deploy rainbond-operator -n rbd-system -o yaml | grep image
4. 如果 rainbond-operator 版本不是最新，修改镜像为最新版本 v6.1.1-release
kubectl edit deploy rainbond-operator -n rbd-system

发现确实是升级到6.1.1之后 operator 还在6.1.0，但是现在dockerhub无法连接，没法拉取6.1.1的镜像

@13813586515 使用国内镜像：registry.cn-hangzhou.aliyuncs.com/goodrain/rainbond-operator:v6.1.1-release

升级到国内镜像是没问题了，jar包打包也没有问题，推送到仓库的镜像也没有问题，但是到最后还是报错了，报错内容：

这是还需要升级什么组件吗

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

@13813586515 In this case, it is impossible to obtain online build package resources through buildpack.rainbond.com

1. Looking at the Gateway log, buildpack.rainbond.com is proxied through the Gateway.

kubectl logs -fl name=rbd-gateway -n rbd-system apisix
2. Use the following command to check whether the domain name is buildpack.rainbond.com
kubectl get apisixupstream -n rbd-system buildpack-upstream
kubectl get apisixroute -n rbd-system lang-proxy
3. If the domain name is incorrect, check whether the rainbond-operator version is v6.1.1-release
kubectl get deploy rainbond-operator -n rbd-system -o yaml | grep image
4. If the rainbond-operator version is not the latest, modify the image to the latest version v6.1.1-release
kubectl edit deploy rainbond-operator -n rbd-system

It is found that after upgrading to 6.1.1, the operator is still in 6.1.0, but now dockerhub cannot connect and cannot pull the 6.1.1 image.

@13813586515 Use domestic mirror: registry.cn-hangzhou.aliyuncs.com/goodrain/rainbond-operator:v6.1.1-release

There was no problem upgrading to the domestic image, there was no problem packaging the jar package, and there was no problem pushing the image to the warehouse. However, in the end, an error was still reported. The error content was:

Is there any component that needs to be upgraded?

[zzzhangqi]

@13813586515 see https://www.rainbond.com/docs/troubleshooting/common#%E6%BA%90%E7%A0%81%E6%9E%84%E5%BB%BA%E6%8F%90%E7%A4%BA-error-failed-to-solve-goodrainmerunner