- Allow user to specify architecture of packages (arm64 or amd64)
- Upload artifacts for all packaged architectures to artifactory
- Fixed regressions introduced by incorrect linting fixes. Most significantly,
preventing the
VERSION
file from being included in release packages.
- Allow Base Image to be configured on execution.
- Updated dependencies.
- Adapted code to reflect Docker API changes, specifying at least one stream is now required. conjurinc/debify#86
- Supply debian distribution to fpm
- Bump
bundler
gem to 2.2.33.
- Fixed publish-rubygems.sh by using git safe directory
- Upgrade ruby version to 3.0.
- Bump
cucumber
gem to 7.1. - Bump
conjur-api
gem to 5.3.7. - Bump
conjur-cli
gem to 6.2.6. - Bump
aruba
gem to 2.0. - Bump
jfrog-cli
to :latest.
- Update to use automated release process
- Refine bundler related steps in
debify package
flow: onlypackage.sh
file configures and invokes bundler.Dockerfile.fpm
only copies files and adjusts folder structure. - Remove bundler 1.* support
- Debify now receives the flag
--output
as input to indicate the file type that it should package (e.grpm
). If this flag is not given, the default value isdeb
. conjurinc/debify#56
- Debify now packages and publishes an RPM file, alongside a debian file. conjurinc/debify#49
debify package
now offers an--additional-files
flag to provide a comma separated list of files to include in the FPM build that are not provided automatically bygit ls-files
. conjurinc/debify#52
- Bug causing
all
files in the git repo to be added to the debian file. conjurinc/debify#50
- Updated FPM and Test images to use a base image with FIPS-compliant Ruby and OpenSSL.
- Updated sandbox password to match Conjur password complexity requirements.
- Reverted to
bundler
v1.bundler
v2 was creating incompatible paths for downstream packages. - Made FPM Ruby version use
ruby2.5
instead ofruby2.6
since that is what our appliance image uses otherwise the gems bundled in the packages are unusable.
- Upgraded to use Ruby 2.6 and latest version of FPM
- Update Conjur Dockerfile from Ubuntu 14.04 --> 18.04 as 14.04 repos
are now behind a pay wall
Ruby is installed from
ppa:brightbox/ruby-ng
however that PPA doesn't currently supply ruby2.2 for Ubuntu 18.04. The documentation suggests this combination is available, so it may be a temporary problem. To work around the problem, ruby is bumped from 2.2 to 2.3 as 2.3 is the oldest version available for Ubuntu 18.04.
- Upgrade
docker-debify
to use Ruby 2.6.
-
Use a Docker env-file (docker.env, by default) to pass environment variables to the debify container.
-
Make sure
--env
variables get passed along to the Conjur container when testing, too.
- Fix a bug causing duplicate files between normal and dev packages when a file name contained a space.
- Pin
ruby-xz
gem in fpm Dockerfile, so it works on Ruby 2.2. Upstream issue: jordansissel/fpm#1493
- Update fpm container to use Ruby 2.4, fixes
ruby-xz
dependency
- add
--net
support totest
andsandbox
subcommands - Use Docker::Container.start! to start containers, to avoid swallowing important errors.
- Make sure .bundle/config in the 'main' package excludes test and development groups.
- Build -dev package with development/test dependencies and use it on
debify test
.
- Install fpm dependency libffi-dev
- Make Conjur cert available in dockerized debify container
- Add a cuke for
debify publish
- Added artifactory url option to
debify publish
, defaults to jfrog.io domain - Added artifactory repo option to
debify publish
, defaults to 'debian-private'
- Fix publishing support in docker-debify
- Take out a
require 'pry'
that had snuck in. - Fix
publish
subcommand, broken after factoring publish out into a separate action.
- Read artifactory credentials from the environment
(
ARTIFACTORY_USER
,ARTIFACTORY_PASSWORD
), only contact Conjur if they're not set.
- Buils a docker image to run debify, convert tests to use it, pipeline build
- When not on the master branch,
debify publish
uses the branch name as the component name, rather than always using'testing'
.
debify publish
now checks env varBRANCH_NAME
as well asGIT_BRANCH
. Jenkins pipelines useBRANCH_NAME
, Jenkins jobs useGIT_BRANCH
.
- debify now uses
~/.docker/config
auth if pulling an image fails due to auth
- Use new conjurops variables in
publish
command, fall back to old conjurops
- Fix the description of the
--version
argument to indicate that the version now comes from theVERSION
file.
- Add
detect-version
command. - Read version from VERSION file, if it exists.
- Add
--port
sandbox option
- When testing,
docker exec
into the Conjur container to run/opt/conjur/evoke/bin/wait_for_conjur
.
- Add
--volumes-from
- Fix typo in error message
- Pin bundler to 1.11.2
- Minor workflow tweaks, and some changes to work around Docker For Mac issues
- Base image used for packaging on Ubuntu 14.04
- Install ruby2.2 and related packages
- Add
name
andWorkingdir
options to the sandbox container.
- Add
debify sandbox
.
- Fixed publish internal Dockerfile.
- Run internal containers as privileged if Docker >= 1.10.0.
- Upgrading Ruby for packaging from 2.0 to 2.2.4.
- Print messages to stderr instead of stdout during packaging.
- Only consider tags matching v*.. when determining package version string.
- Provide the package to purge before installing the new version.
- Don't nuke the entire existing source install dir, there may be necessary files in there.
- Remove the need for a 'latest' debian.
- Fix bug in the error message for 'detect_version'.
- Use a more reliable way to detect the current branch.
publish
: Remove the default value of the 'component' flag.clean
: Don't create a container unless deletions will actually be performed.
- Add
debify clean
.
package
: Add--dockerfile
option.package
: Ensure thatGemfile.lock
is in the container.test
: PropagateSSH_AUTH_SOCK
to the container.