Foreman » Packaging

Update foreman-docker to 4.1.0

update foreman-docker to 4.0.0

plugins:foreman_docker - Release 3.2.1

plugins:foreman_docker - Release 3.2.0

Update foreman-docker to 3.1.0

Update foreman-docker to 3.0.0

Use foreman-ruby to run bundler in plugin build scripts

Fixes builds of plugins on OSes such as trusty where the default Ruby is
different to the foreman-ruby version, causing `foreman` installation
errors as gems are missing the correct `ruby-dev` package.

plugins:foreman-docker - Release 2.1.1

plugins:docker - release 2.0.1

plugins:foreman_docker - Release 2.0.0

Replace plugin upgrade/install test to fix Bundler errors

When a plugin is upgraded and the version changes, the `bundle show`
command always failed as bundler.d/ had already been updated, but the
Gemfile.lock and vendor/ area was out of date.

Error from an upgrade where 1.0.1 was currently installed, but...

plugins:foreman_docker - Release 1.4.1

Fix changelog formatting

plugins:foreman_docker - Release 1.4.0

plugins:foreman_docker - Release 1.3.1

plugins:foreman_docker - Release 1.3.0

plugins:foreman_docker - Release 1.2.4

Update foreman_docker to 1.2.3

plugins:foreman_docker - Release 1.2.2

Generate plugin API docs at build time

plugins:foreman_docker - Release 1.2.1

plugins:foreman_docker - Release 1.2.0

plugins:foreman_docker - Release 1.1.0

plugins:foreman_docker - Release 1.0.1

Precompile and ship plugin assets in foreman_docker

Depends on Foreman #8925 to support reading manifest.yml from Foreman's own
public/assets/ directory rather than the gem installation root which is
generated at install-time by bundler/rubygems.

plugins:foreman_docker - Release 1.0.0

Set HOME to ~foreman as rb-readline requires it

Added ruby-foreman-docker