openSUSE-release-tools/gocd/vagrant-publisher.gocd.yaml
Dan Čermák 7f9d90b04b
Change vagrant publisher resource to staging-bot
resources cannot have arbitrary names, atm only the following are supported:
- monitor
- repo-checker
- staging-bot

=> use staging-bot as the publisher can take a while to run, but it will not run
   permanently so monitor is overkill
2021-10-25 10:14:28 +02:00

23 lines
922 B
YAML

format_version: 3
pipelines:
openSUSE.Vagrant.Publish:
group: openSUSE.Checkers
lock_behavior: unlockWhenFinished
environment_variables:
ATLAS_TOKEN: '{{SECRET:[opensuse.secrets][ATLAS_TOKEN]}}'
materials:
git:
git: https://github.com/openSUSE/opensuse-release-tools.git
timer:
spec: 0 0 0 ? * *
only_on_changes: false
stages:
- Run:
approval: manual
resources:
- staging-bot
tasks:
- script: |
ruby.ruby3.0 obs-to-vagrantcloud.rb --url https://download.opensuse.org/tumbleweed/appliances/boxes/Tumbleweed.x86_64.json --organization opensuse --new-box-name Tumbleweed.x86_64 --provider libvirt
ruby.ruby3.0 obs-to-vagrantcloud.rb --url https://download.opensuse.org/tumbleweed/appliances/boxes/Tumbleweed.x86_64.json --organization opensuse --new-box-name Tumbleweed.x86_64 --provider virtualbox