-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows testing using kitchen-vagrant #112
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some initial feedback.
718e172
to
c89b98c
Compare
@dafyddj Apologies for the poor-quality communication earlier, both here and in Slack -- I was out and about so it got a bit messy. I'm glad you figured out what I was trying to say!
I'd very much welcome Windows testing, even if it was only local. It would help with PRs that have got stuck, such as the following: In terms of CI/CD, there's a potential solution. You may have noticed that Cirrus CI has been enabled for this org's repos and is being used for a few of them (e.g. |
I have had a little play with kitchen-docker using Windows containers (support was only added a matter of weeks ago), and there's a slight gotcha in that files cannot be uploaded to the container while it's running - so, at least at the moment, it's not really a viable testing method. |
c89b98c
to
c24e1cc
Compare
@myii care to take another look at this? I've changed the approach a little: pre-Salted Windows image; re-use of Inspec tests and |
@dafyddj Sounds good! I'll try to have a look at this soon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dafyddj This is an excellent PR! I can see this becoming the basis for all sorts of Vagrant-based testing across our formulas. Thank you very much for addressing this problem.
I've got a few requests that I've mentioned inline. I haven't clearly defined the one about a separate test pillar, so please shout if anything's unclear. I also want to draw the attention of the other contributors to this, so we can confirm a standard structure that can be used in other formulas as well.
Checked with: myii/ssf-formula#81
@dafyddj Whatever decision is reached, it would be good to update the testing section in the |
While I look over this, what do you think of this approach (1037162) whereby |
Resulting Travis output here. |
Yes, this is on my TODO list. |
@dafyddj This has crossed my mind plenty of times, since getting my hands dirty with all of the linters. It's nice to see a working method. It definitely appeals to the perfectionist in me but that's not necessarily a good thing! Having cast my eye over a lot of debug output, it's obvious that we'd have to use a fairly relaxed set of So what are my concerns? They're a bit elusive right now but I suppose one is that we could end up distracting ourselves unnecessarily, or giving ourselves too many hoops to jump through. Another is that the lint won't cover the whole of each source file; the rendered files will miss sections due to conditionals, etc. The issue surrounding I'd still like to see this in action, though. How about we do this in a separate job with Please don't mistake this as a negative response in any way. I would definitely use this in a personal capacity, within a well-defined environment. My feedback here is more measured, trying to consider the wider implications. |
@dafyddj Another reason for having a general purpose
|
bc7b160
to
d2575e2
Compare
@dafyddj Is this still a WIP? |
Yes, still have a couple of things to add to it. |
@dafyddj OK, please ping me when you're ready for the next stage. |
@myii I've added to the documentation and updated my Vagrant box (to version 2019.10.141), so this PR is ready for further review. |
80cce57
to
c09c15a
Compare
* and with paths that contain spaces
* so that adapters are created before service is started
* use `rspec-retry` to make retrying the logfile test platform-independent * do some DRYing of the inspec control files
c09c15a
to
0229d14
Compare
🎉 This PR is included in version 0.15.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
I'm putting this out there to gather some opinions.
Would this be useful to add to the formula, despite the fact that the tests can't be run in any CI/CD service that I know of?
Testing requires Virtualbox and Vagrant on the local machine.
The OpenVPN server is first run on a linux box, and the tests are subsequently run on the Windows box.