![]() Veertu Inc (creators of Anka) state that the performance of using shared/mounted folders is not optimized. Set this to true if you do not wish to mount the current directory into the Anka VM. The path to a file containing environment variables you wish to inject into you Anka VM.Įxample. Set this to true to inject the environment variables set on your host into the Anka VM.Įxample: true environment-file (optional) You can set the value to "shrink" in order to remove other local tags for the vm-name, optimizing the footprint.Įxample: true inherit-environment-vars (optional).We suggest monitoring for registry availability or failures. This prevents your registry from being a single point of failure for pipelines. Should your registry be down and the pull fail, the plugin will not fail the buildkite run.Set this value to true if you wish to pull the VM Template before the VM is cloned and started. The tag associated with the VM Template ( vm-name) you wish to pull from the Anka Cloud Registry.Įxample: latest vm-registry-version (optional)Ī version associated with the VM Template you wish to pull from the Anka Registry (every tag has a version number assigned to it).īy default, the anka-buildkite-plugin will only pull the VM Template from the Anka Registry if it's not on the Node. ![]() ![]() The plugin will create a step-specific clone prior to execution.Įxample: macos-base-10.14 vm-registry-tag (optional) The name of the Anka VM Template to use as the base. Run any of your post-commands (see below). Run any of your pre-commands (see below).Įxecute your command inside of the cloned virtual machine. chef/anka#v0.7.2: vm-name: macos-base-10.14 Hook Steps Hookĭownload the specified virtual machine from your registry (if applicable).Ĭlone the virtual machine and perform any hardware modifications. command: make test agents: "queue=mac-anka-large-node-fleet " plugins: In the VM, make sure remote login is enabled ( System Preferences > Sharing).We recommend using Anka Build 2.3 or greater with this plugin, especially if you have Big Sur VMs. If we are unable to detect the FUSE driver within your VM, we will use the anka cp utility to copy the contents of your volume (or current working directory) into the VM (unless no-volume is true).The error you'd see otherwise is state_lib/b026f71c-7675-11e9-8883-f01898ec0a5d.ank: failed to open image, error 2 This prevents collision/ram state corruption when you're running two different jobs and pulling two different tags on the same anka node. A lock file ( /tmp/anka-buildkite-plugin-lock) is created around pull and cloning.The plugin does not automatically mount the buildkite-agent or inject any BUILDKITE_ environment variables.The plugin will create a cloned VM to run instructions in and will delete the VM on pipeline status cancellation, failure, or success.You need to ensure your Anka Nodes (host machines running Anka software) have the Buildkite agent installed and show under your Agents listing inside of Buildkite.A Buildkite plugin for running pipeline steps in Anka virtual machines.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |