mirror of
https://github.com/puppetlabs/vmfloaty.git
synced 2026-01-25 21:28:40 -05:00
Add release instructions and reference docker image
This commit is contained in:
parent
68843c1ecf
commit
4ab4d511f7
2 changed files with 45 additions and 20 deletions
53
README.md
53
README.md
|
|
@ -1,37 +1,48 @@
|
|||
# vmfloaty
|
||||
|
||||
[](https://badge.fury.io/rb/vmfloaty)
|
||||
[](https://github.com/puppetlabs/vmfloaty/actions/workflows/ci.yml)
|
||||
[](https://github.com/puppetlabs/vmfloaty/actions/workflows/test.yml)
|
||||
|
||||
A CLI helper tool for [Puppet's VMPooler](https://github.com/puppetlabs/vmpooler) to help you stay afloat.
|
||||
|
||||

|
||||
|
||||
- [Install](#install)
|
||||
- [Usage](#usage)
|
||||
- [Example workflow](#example-workflow)
|
||||
- [vmfloaty dotfile](#vmfloaty-dotfile)
|
||||
- [Basic configuration](#basic-configuration)
|
||||
- [Using multiple services](#using-multiple-services)
|
||||
- [Using backends besides VMPooler](#using-backends-besides-vmpooler)
|
||||
- [Valid config keys](#valid-config-keys)
|
||||
- [Tab Completion](#tab-completion)
|
||||
- [VMPooler API](#vmpooler-api)
|
||||
- [Using the Pooler class](#using-the-pooler-class)
|
||||
- [Example Projects](#example-projects)
|
||||
- [Contributing](#contributing)
|
||||
- [Code Reviews](#code-reviews)
|
||||
- [Releasing](#releasing)
|
||||
- [Special thanks](#special-thanks)
|
||||
- [vmfloaty](#vmfloaty)
|
||||
- [Install](#install)
|
||||
- [Ruby](#ruby)
|
||||
- [Docker](#docker)
|
||||
- [Usage](#usage)
|
||||
- [Example workflow](#example-workflow)
|
||||
- [vmfloaty dotfile](#vmfloaty-dotfile)
|
||||
- [Basic configuration](#basic-configuration)
|
||||
- [Using multiple services](#using-multiple-services)
|
||||
- [Using backends besides VMPooler](#using-backends-besides-vmpooler)
|
||||
- [Valid config keys](#valid-config-keys)
|
||||
- [Tab Completion](#tab-completion)
|
||||
- [VMPooler API](#vmpooler-api)
|
||||
- [Using the Pooler class](#using-the-pooler-class)
|
||||
- [Example Projects](#example-projects)
|
||||
- [Contributing](#contributing)
|
||||
- [Code Reviews](#code-reviews)
|
||||
- [Releasing](#releasing)
|
||||
- [Special thanks](#special-thanks)
|
||||
|
||||
## Install
|
||||
|
||||
### Ruby
|
||||
|
||||
Grab the latest from ruby gems...
|
||||
|
||||
```bash
|
||||
gem install vmfloaty
|
||||
```
|
||||
|
||||
### Docker
|
||||
|
||||
Run the docker image:
|
||||
|
||||
`docker run -it --rm -v ~/.vmfloaty.yml:/home/floatyuser/.vmfloaty.yml ghcr.io/puppetlabs/vmfloaty --help`
|
||||
|
||||
## Usage
|
||||
|
||||
```plain
|
||||
|
|
@ -177,10 +188,12 @@ Please wait for multiple code owners to sign off on any notable change.
|
|||
|
||||
## Releasing
|
||||
|
||||
Releasing is a two step process:
|
||||
Follow these steps to publish a new GitHub release, build and push the gem to <https://rubygems.org>, and build and push a Docker Image to GitHub Container Registry:
|
||||
|
||||
1. Submit a release prep PR that updates `lib/vmfloaty/version.rb` to the desired new version and get that merged
|
||||
2. Navigate to <https://github.com/puppetlabs/vmfloaty/actions/workflows/release.yml> --> Run workflow --> select "main" branch --> Run workflow. This will publish a GitHub release, build, and push the gem to RubyGems.
|
||||
1. Bump the "VERSION" in `lib/vmpooler/version.rb` appropriately based on changes in `CHANGELOG.md` since the last release.
|
||||
2. Run `./release-prep` to update `Gemfile.lock` if necessary and `CHANGELOG.md`.
|
||||
3. Commit and push changes to a new branch, then open a pull request against `main` and be sure to add the "maintenance" label.
|
||||
4. After the pull request is approved and merged, then navigate to <https://github.com/puppetlabs/vmfloaty/actions/workflows/release.yml> --> Run workflow --> select "main" branch --> Run workflow. This will publish a GitHub release, build and push the gem to RubyGems, and build and push a Docker Image to GitHub Container Registry.
|
||||
|
||||
## Special thanks
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue