Super minor but while looking up this gem on the Rubygem site, got a 404 because of gem.homepage being incorrect: https://github.com/cheeseplus/bento-ya/blob/master/bento-ya.gemspec#L14

This breaks on Windows so we need to File.join and use full paths.

If you bento build with the --cpus flag you will receive a nil error:

bento build -v v201812.03.0 -H --only=virtualbox-iso -c 2
>>> undefined method `each' for nil:NilClass

While each definition runs in parallel via packer there's no way to run more than one build at a time. If you want to build one hypervisor you may want to build 2-3 definitions at a time.

https://github.com/cargomedia/vagrant_cloud

if you dont have parallels installed after the first build it exits as such:

>>> No such file or directory - prlctl

Describe the problem

This project is great! But I'd like to use it to publish boxes to a private artifactory instance.

Software Version

bento-ya (1.1.2)

Possible Solution

The vagrant_cloud gem supports declaring a custom server (the third argument to VagrantCloud::Account) so it seems like this could be a simple change to how vc_account is created to also look for an ENV variable for custom_server.

If you try to specify a config you just get an error

bento build -c builds.yml
>>> undefined method `each' for nil:NilClass

This requires user input by default as SMB is used for the sharing protocol so breaks waiting for input when run non-interactively.

I was thinking it might be worth adding some Travis tests to avoid things like chef/bento#839.

Perhaps even just running bento --help or using a linter would be a good first step?

chef/bento#813

This gem grew out of the desire to cleanup the ad-hoc script and Rakefile that was in the bento repo but as time has went on it seems the original approach has (re-)validated that approach as keeping the code closer to the base repo makes sense. This avoids extra build/publish/install steps and thus far I've not really seen much usage of the bento-ya gem itself - it doesn't quite make sense for public consumption and adds more cognitive load than is necessary to do the job we need.

With the command bento build --version 0.8.15 --only qemu,vmware-iso,virtualbox-iso my_template_file.json I run into the following error message from VBox:

VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).

... because of Qemu/KVM can not run in parallel to VMware or Virtual Box. See: https://askubuntu.com/questions/413511

Now, for a QnD workaround, I've add the packer command line option -parallel=false to packer build in lib/bento/build.rb:

...
cmd.insert(2, "-debug") if debug
cmd.insert(2, "-parallel=false")
cmd.insert(0, "echo") if dry_run
cmd

Now my question. Is there a better way to tell packer to work not in parallel mode (perhaps a central configuration file or environment variable)?

If not, I would like to provide a patch for bento-ya to add a new bento build argument --single that will set the packer parallel mode to true or false (similar to --headed).

It would be useful if --only and --except gave you the examples of what you might exclude or include.

Trying to upload debian-9.1-i386 uncovered that the current code at https://github.com/cheeseplus/bento-ya/blob/master/lib/bento/upload.rb#L26 fails with a 422 Unprocessable Entity if the box name doesn't already exist