Use different name for builder and exported VM #539
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows building a new VM for the current semester while a previous
build of the same semester is still registered in VirtualBox. It doesn't
help having multiple builds of the same VM going at the same time but it
makes things slightly smoother. The exported VM gets to keep the same
name pattern it's always had via the
vmname
argument toVBoxManage export
.Additionally, the
legacy_isotime
function invocation is replaced withthe recommended migration path.