Skip to content
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

feat(semantic-release): implement for this formula #44

Merged

Conversation

myii
Copy link
Member

@myii myii commented Oct 29, 2019

PR progress checklist (to be filled in by reviewers)

  • Changes to documentation are appropriate (or tick if not required)
  • Changes to tests are appropriate (or tick if not required)
  • Reviews completed

What type of PR is this?

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

semantic-release PRs do not modify the functionality of the formula itself. The exception in this case is that testing revealed the issue with the ntp service not running in a container for opensuse. So this is checked for in the formula and the tests are structured accordingly.

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

```bash
ntp-formula$ yamllint -s .
./pillar.example
  1:1       warning  missing document start "---"  (document-start)
  11:1      error    duplication of key "ntp" in mapping  (key-duplicates)
  15:1      error    duplication of key "ntp" in mapping  (key-duplicates)
  21:1      error    duplication of key "ntp" in mapping  (key-duplicates)
  24:4      error    syntax error: found character '%' that cannot start any token
  25:89     error    line too long (92 > 88 characters)  (line-length)
```
@myii myii force-pushed the feat/implement-semantic-release branch from e1724cd to d27e896 Compare October 29, 2019 03:54
* E.g. `opensuse-leap-151`:

```bash
kitchen@0e066e43d255:~> systemctl status ntpd
WARNING: terminal is not fully functional
-  (press RETURN)● ntpd.service - NTP Server Daemon
   Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled)
   Active: inactive (dead)
Condition: start condition failed at Sat 2019-10-26 04:11:32 UTC; 13min ago
           └─ ConditionVirtualization=!container was not met
     Docs: man:ntpd(1)
```

* Check for `Docker` for the time being (other containers _are_ possible) --
  replace earlier method of checking for the `kitchen` user:
  - `salt['environ.get']('SUDO_USER', '') == 'kitchen'`
@myii myii force-pushed the feat/implement-semantic-release branch from d27e896 to 598da25 Compare October 29, 2019 08:38
@aboe76 aboe76 merged commit d2d6c18 into saltstack-formulas:master Oct 30, 2019
@aboe76
Copy link
Member

aboe76 commented Oct 30, 2019

Nice @myii

@myii myii deleted the feat/implement-semantic-release branch October 30, 2019 21:14
@myii
Copy link
Member Author

myii commented Oct 30, 2019

Thanks.

@saltstack-formulas-travis

🎉 This PR is included in version 0.19.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants