Skip to content

Move from CircleCI/Packet.net to GH Actions #54

@arm4b

Description

@arm4b

At the moment we build ST2 vagrant box + OVA by requesting a bare-metal instance at Packet.net, making a Packer build there and deploying produced artifact to the Vagrant Cloud.

Turns out GH Actions can now support Vagrant + Virtualbox (via nested virtualization? ).

Explore/research the https://stackoverflow.com/a/60380518/4533625 and https://github.com/jonashackt/vagrant-github-actions and moving the pipeline to GH Actions which will save us some $ and complexity by not using external Packet.net bare-metal instance. Side effects could be: slow/unstable build process, needs evaluation.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions