test: implement test using Kitchen and Inspec, and CI with Travis

[daks]

What type of PR is this?

Implement semantic-release and a limited set of Kitchen/Inspec tests on some platforms.

Primary type

• [build] Changes related to the build system
• [chore] Changes to the build process or auxiliary tools and libraries such as documentation generation
• [ci] Changes to the continuous integration configuration
• [feat] A new feature
• [fix] A bug fix
• [perf] A code change that improves performance
• [refactor] A code change that neither fixes a bug nor adds a feature
• [revert] A change used to revert a previous commit
• [style] Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)

Secondary type

• [docs] Documentation changes
• [test] Adding missing or correcting existing tests

Does this PR introduce a BREAKING CHANGE?

No.

Related issues and/or pull requests

Describe the changes you're proposing

Pillar / config required to test the proposed changes

Debug log showing how the proposed changes work

Documentation checklist

• Updated the README (e.g. Available states).
• Updated pillar.example.

Testing checklist

• Included in Kitchen (i.e. under state_top).
• Covered by new/existing tests (e.g. InSpec, Serverspec, etc.).
• Updated the relevant test pillar.

Additional context

Formula working on a limited set of platforms. First version of semantic-release implementation. Tests pass on working platforms.

[myii]

Great PR, @daks. For the first part of the review, there's just some files which need to be added direct from the template-formula:

1. .rubocop.yml
2. .salt-lint
3. .yamllint
4. release-rules.js

And one that needs to be removed:

1. docs/CONTRIBUTING_DOCS.rst

---

With these done, only yamllint errors need to be resolved:

rabbitmq-formula$ yamllint -s .
./pillar.example
  1:1       warning  missing document start "---"  (document-start)
  2:1       warning  comment not indented like content  (comments-indentation)
  3:12      warning  truthy value should be one of [false, true]  (truthy)
  4:12      warning  truthy value should be one of [false, true]  (truthy)
  18:16     warning  truthy value should be one of [false, true]  (truthy)
  21:9      error    wrong indentation: expected 10 but found 8  (indentation)
  22:11     error    wrong indentation: expected 12 but found 10  (indentation)
  28:16     warning  truthy value should be one of [false, true]  (truthy)
  31:9      error    wrong indentation: expected 10 but found 8  (indentation)
  32:11     error    wrong indentation: expected 12 but found 10  (indentation)
  47:8      warning  missing starting space in comment  (comments)
  50:1      error    syntax error: could not find expected ':'

---

After that, it's just a matter of arranging the platforms for testing, with some changes to kitchen.yml (for the new platforms that are supported) and .travis.yml. These are pretty good examples to base that upon:

• https://github.com/myii/redis-formula/blob/ci/upgrade-matrix-after-2019.2.2/kitchen.yml
• https://github.com/myii/redis-formula/blob/ci/upgrade-matrix-after-2019.2.2/.travis.yml

[daks]

@myii I added missing files, fixed lint errors, but I'm not sure what to do with the testing matrix, I already took the one from template-formula.

[daks]

@myii I updated files from template-formula and also FORMULA to only include Debian and Ubuntu as, for now, those are the only platforms supported.

Feel free to comment if needed, or merge it, as I think it's OK now.

[myii]

@daks I'll have a look at this within the next day. If there are only minor issues (such as .travis.yml needing updating, as it appears it does), then I'll just append a commit and get this merged.

---

Actually, since the new pre-salted images are effectively available now, I'll probably include those in the commit as well.

[myii]

@daks I've added 2b5e400, would you care to check it before this is merged?

[myii]

Thanks for the confirmation on Slack, @daks -- merged.

[saltstack-formulas-travis]

🎉 This PR is included in version 0.15.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀