Verified Commit ac3e3ea4 authored by Sven-Hendrik Haase's avatar Sven-Hendrik Haase
Browse files

Store raw VM disks

Going forward, it makes sense to host these raw images as well as there are some use cases for that.
For instance, what if you don't want to use vagrant but instead just use the raw images in qemu directly?
parent 3ef68bb3
Pipeline #888 passed with stages
in 12 minutes and 37 seconds
......@@ -55,6 +55,8 @@ build:
artifacts:
paths:
- "*.box"
- "output-qemu"
- "output-virtualbox-iso"
expire_in: 3h
resource_group: vm-build
......
......@@ -146,7 +146,7 @@
[
{
"type": "vagrant",
"keep_input_artifact": false,
"keep_input_artifact": true,
"output": "Arch-Linux-x86_64-{{ .Provider }}-{{isotime \"2006-01-02\"}}.box"
}
]
......
......@@ -147,7 +147,7 @@
[
{
"type": "vagrant",
"keep_input_artifact": false,
"keep_input_artifact": true,
"output": "Arch-Linux-x86_64-{{ .Provider }}-{{isotime \"2006-01-02\"}}.box"
},
{
......
  • I doubt that the artifacts generated by {vagrant,local}.json are really useful, because of several reasons:

    1. They were only meant for vagrant builds, for raw qemu images we have the cloud.json file.
    2. The images are configured for vagrant, they have a vagrant user, vagrant passwords and default ssh keys in them. This can be a security risk.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment