https://github.com/juju4/ansible-upgrade-pkgs-gem

upgrade gem packages
https://github.com/juju4/ansible-upgrade-pkgs-gem

Last synced: 12 days ago
JSON representation

upgrade gem packages

• Host: GitHub
• URL: https://github.com/juju4/ansible-upgrade-pkgs-gem
• Owner: juju4
• License: bsd-2-clause
• Created: 2017-01-07T21:12:54.000Z (about 8 years ago)
• Default Branch: main
• Last Pushed: 2024-11-24T20:23:35.000Z (about 2 months ago)
• Last Synced: 2024-11-24T21:19:30.244Z (about 2 months ago)
• Language: Shell
• Size: 51.8 KB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# upgrade-pkgs-gem ansible role

Ansible role to upgrade gem packages

## Requirements & Dependencies

### Ansible

It was tested on the following versions:

 * 2.2

 * 2.5

### Operating systems

Ubuntu 14.04, 16.04, 18.04 and Centos7

## Example Playbook

Just include this role in your list.

For example

```

- host: all

  roles:

    - juju4.upgrade-pkgs-gem

```

## Variables

Nothing specific for now.

## Continuous integration

This role has a travis basic test (for github), more advanced with kitchen and also a Vagrantfile (test/vagrant).

Default kitchen config (.kitchen.yml) is lxd-based, while (.kitchen.vagrant.yml) is vagrant/virtualbox based.

Once you ensured all necessary roles are present, You can test with:

```

$ gem install kitchen-ansible kitchen-lxd_cli kitchen-sync kitchen-vagrant

$ cd /path/to/roles/juju4.upgrade-pkgs-gem

$ kitchen verify

$ kitchen login

$ KITCHEN_YAML=".kitchen.vagrant.yml" kitchen verify

```

or

```

$ cd /path/to/roles/juju4.upgrade-pkgs-gem/test/vagrant

$ vagrant up

$ vagrant ssh

```

## Troubleshooting & Known issues

## License

BSD 2-clause