无人机自托管,无人机服务器之间的管道路由
Drone self-hosted, pipeline routing between Drone servers
我有开发和生产 kubernetes 集群,每个集群都有无人机服务器。两台服务器都在观看同一组 github 回购。
我想做这样的事:
---
kind: pipeline
name: artifacts
drone_instance: dev # <--- magic routing
steps:
- ...
trigger:
event: tag
ref: refs/tags/dev-*
---
kind: pipeline
name: deploy_dev
drone_instance: dev # <--- magic routing
steps:
- ...
trigger:
event: tag
ref: refs/tags/dev-*
---
kind: pipeline
name: deploy_prod
drone_instance: prod # <--- magic routing
steps:
- ...
trigger:
event: tag
ref: refs/tags/prod-*
例如运行 不同无人机实例上的不同管道。我正在查看 platform
过滤器,但它似乎在 Kubernetes 模式下不可用。有人破解过类似的东西吗?
注意:对应的 gh 线程 https://github.com/drone/drone-runtime/issues/63
在 Gitter 中得到 drone.io 团队的回答:
I recommend using .drone.yml for prod, and then creating a
.drone.dev.yml for dev. In your dev Drone instance, in the repository
settings, point Drone at the .drone.dev.yml
我有开发和生产 kubernetes 集群,每个集群都有无人机服务器。两台服务器都在观看同一组 github 回购。
我想做这样的事:
---
kind: pipeline
name: artifacts
drone_instance: dev # <--- magic routing
steps:
- ...
trigger:
event: tag
ref: refs/tags/dev-*
---
kind: pipeline
name: deploy_dev
drone_instance: dev # <--- magic routing
steps:
- ...
trigger:
event: tag
ref: refs/tags/dev-*
---
kind: pipeline
name: deploy_prod
drone_instance: prod # <--- magic routing
steps:
- ...
trigger:
event: tag
ref: refs/tags/prod-*
例如运行 不同无人机实例上的不同管道。我正在查看 platform
过滤器,但它似乎在 Kubernetes 模式下不可用。有人破解过类似的东西吗?
注意:对应的 gh 线程 https://github.com/drone/drone-runtime/issues/63
在 Gitter 中得到 drone.io 团队的回答:
I recommend using .drone.yml for prod, and then creating a .drone.dev.yml for dev. In your dev Drone instance, in the repository settings, point Drone at the .drone.dev.yml