chore: Add a simple Vagrantfile for running tests

[vpodzime]

Makes running tests locally, yet in an isolated environment, really easy.

Ticket: none
Changelog: none

[mender-test-bot]

@vpodzime, start a full integration test pipeline with:

• mentioning me and start integration pipeline

---

my commands and options

You can prevent me from automatically starting CI pipelines:

• if your pull request title starts with "[NoCI] ..."

You can trigger a client pipeline on multiple prs with:

• mentioning me and start client pipeline --pr mender/127 --pr mender-connect/255

You can trigger GitHub->GitLab branch sync with:

• mentioning me and sync

You can print PR statistics for a repository with:

• mentioning me and print fast pr stats (Team stats only)
• mentioning me and print full pr stats (Detailed report)
• options: --repo <repo>, --team <name>, --all-repos, --exclude-drafts, --exclude-user <user>
• mentioning me and print full pr stats --repo mender --all-repos --exclude-drafts

You can cherry pick to a given branch or branches with:

• mentioning me and:

 cherry-pick to:
 * 1.0.x
 * 2.0.x

[vpodzime]

ci/gitlab/integ-testsExpected — Waiting for status to be reported

Not going to waste money on this, there are no functional changes here.

[mzedel]

Can you ensure this works on a Mac as well using the corresponding runner? Otherwise it's bound to be pointed to for other people and not working.

[michalkopczan]

Nice. I don't see what does it give us that running the tests locally does not, but it's a valid way to do it of course

[vpodzime]

what does it give us that running the tests locally does not

Isolation and separation plus an environment that the tests expect (I'm not installing docker on my workstation, for example).

[vpodzime]

Otherwise it's bound to be pointed to for other people and not working.

Could be. This is really just me sharing what I used myself just in case someone else finds it handy. It's good enough for me to have it here in the PR and close it without merging, but then it's just harder to discover than having it in the repo.

[michalkopczan]

Isolation and separation plus an environment that the tests expect (I'm not installing docker on my workstation, for example).

All right. If you don't want to install docker then using vagrat makes sense. 👍
If on the other hand you'd use docker, then FYI: the tests use docker + files in /tmp, they're not really changing anything on your workstation.

[mzedel]

What's in the repo turns into maintenance - what's not possible to maintain from everyone because of a single persons installation preferences is IMO just not acceptable to go in a repo.
Ensure this works on the platforms we use please.

[mzedel]

I'm not installing docker on my workstation

Considering that docker is an integral part of the entire project setup IMO you are not willing to be part of the project 🤷.

[elkoniu]

I like it a lot and thanks for putting this together @vpodzime How about my idea of storing those vagrant files for various repo in one place - like mender-qa dir etc?. This way they wont be a part of the repos to maintain, instead we will have a library of them in one place ready to use. Also we could have single CI job there testing if they are still working fine.

[vpodzime]

I shared what I had. That's what I wanted to do. Nothing beyond that is what I'm willing to invest my time and effort into. I'll keep using this whenever I need, you guys can take it and improve/adjust it for your needs. It will be here in the PR.