Skip to content

@charleskorn charleskorn released this Feb 16, 2020

What's new

  • It's now possible to use expressions like references to environment variables in the local path for volume mounts, for example:

    containers:
      build-env:
        # ... other config
        volumes:
          - local: $CODE_DIR
            container: /code

    (#289 - thanks to @flobas for the suggestion)

What's changed

  • Releases will now be published to the batect/batect Bintray repository. The old repository will not be removed, but new versions will only be published to the new repository. This should have no impact for most users - the latest version of the wrapper script will use the new repository automatically.

Getting started

First time using batect? Take a look at the getting started guide, or the many sample projects.

How to upgrade from previous versions

If you're already using batect, run ./batect --upgrade to upgrade automatically.

Assets 5

@charleskorn charleskorn released this Feb 9, 2020

What's new

  • Created Docker containers will now be given user-friendly names, making them easier to identify when running commands like docker ps.

    For example, if a task starts a db container and an app container, the running Docker containers will be given names like db-abcd23 and app-abcd23 (#401 - thanks to @camjackson for the feedback in the batect Spectrum community)

  • The sample projects page now includes @yearofthedan's example showing using batect with Terraform to provision resources in GCP.

What's been fixed

  • The issue where pulling an image could time out while waiting for the extraction step to complete has been fixed.

  • The issue where image pull progress would get stuck on 'download complete' while Docker was extracting image layers has been fixed.

  • The issue where batect would fail to start when running as part of a GitHub Actions workflow with java.lang.IllegalArgumentException: The value '3.0.10+azure' is not recognised as a valid version. has been fixed.

Getting started

First time using batect? Take a look at the getting started guide, or the many sample projects.

How to upgrade from previous versions

If you're already using batect, run ./batect --upgrade to upgrade automatically.

Assets 5

@charleskorn charleskorn released this Jan 30, 2020

What's new

  • batect now supports complex expressions in environment variable and build arg values, such as Hello, $USERNAME! and <DB:4000. More details are available in the new expressions section in the documentation.

What's been fixed

  • The issue where pulling large Windows container images over a slow connection could time out has been fixed.

Getting started

First time using batect? Take a look at the getting started guide, or the many sample projects.

How to upgrade from previous versions

If you're already using batect, run ./batect --upgrade to upgrade automatically.

Assets 5

@charleskorn charleskorn released this Jan 22, 2020

What's changed

What's been fixed

  • The issue where batect would hang or timeout waiting for a container to become healthy when running with Docker 19.03.5 has been fixed (#393 - thanks to @alexswilliams for reporting this issue).

Getting started

First time using batect? Take a look at the getting started guide, or the many sample projects.

How to upgrade from previous versions

If you're already using batect, run ./batect --upgrade to upgrade automatically.

Assets 5

@charleskorn charleskorn released this Jan 18, 2020

🎉 60th release!

What's new

  • batect now supports running Windows containers. (#275 - thanks to @DamianBis for the feedback)

    While common cases have been tested, Windows container support should be considered beta quality - please report any issues you encounter.

  • The documentation now has a page explaining how to use batect with GitHub Actions.

What's been fixed

  • The issue where an environment variable could not be set to an empty value has been fixed (#340 - thanks to @alexswilliams for reporting this issue).

Getting started

First time using batect? Take a look at the getting started guide, or the many sample projects.

How to upgrade from previous versions

If you're already using batect, run ./batect --upgrade to upgrade automatically.

Assets 5

@charleskorn charleskorn released this Jan 3, 2020

What's new

  • The concept of config variables has been added. Config variables allow you simplify your configuration file, and document and codify the different options available to a developer using your tasks.

    They are useful for a number of use cases:

    • Reducing duplication in configuration files
    • Simplifying management of developer-specific preferences (eg. a developer's preferred log output level)
    • Simplifying management of sets of environment-specific settings (eg. managing sets of test environment connection settings for a CI server)

    Config variables can currently be used in environment variables for containers and tasks, and build args for containers.

    There is more information on config variables in the documentation.

  • It is now possible to override the image used by a container on the command line.

    ./batect --override-image build-env=ruby:2.7.0 unitTest will run the unitTest task with the build-env container using the ruby:2.7.0 container.

  • An extra section has been added to the CircleCI documentation page, showing how to define a reusable command that runs batect (thanks to @ineffyble for the contribution offline)

What's changed

  • The output of ./batect --help has been improved to make it more readable: the options are now shown in groups and the descriptions wrap at the edge of your terminal window.

  • Pre-release versions of batect are no longer uploaded to Bintray due to space constraints. Pre-release versions will be made available again in the future.

What's been fixed

  • A clearer error message will now be shown when attempting to run batect on Windows when Docker is configured for Windows containers. (Running Windows containers with batect is not currently supported.)

  • The issue where batect may randomly freeze, particularly on Windows, has been fixed.

Getting started

First time using batect? Take a look at the getting started guide, or the many sample projects.

How to upgrade from previous versions

If you're already using batect, run ./batect --upgrade to upgrade automatically.

Assets 5

@charleskorn charleskorn released this Dec 8, 2019

What's new

  • Output from setup commands is now shown when running with --output all (previously it was only shown if the command failed)

  • Output from image builds is now shown when running with --output all (previously it was only shown if the build failed)

  • It is now possible to mount devices into containers (#290 - thanks to @TassSinclair and @wilvk for the PR)

  • It is now possible to use a Docker daemon that requires TLS, such as Minikube's Docker daemon (#278 - thanks to @aidansteele for the feedback)

  • -T has been added as an alias for --list-tasks

What's changed

  • ⚠️ batect now requires at least Docker version 18.03.1 due to issues in earlier versions where containers would randomly freeze

What's been fixed

  • The issue where building an image that used base images from multiple private repositories could fail if they had not previously been pulled has been fixed

Getting started

First time using batect? Take a look at the getting started guide, or the many sample projects.

How to upgrade from previous versions

If you're already using batect, run ./batect --upgrade to upgrade automatically.

Assets 5

@charleskorn charleskorn released this Nov 17, 2019

What's new

  • It's now possible to run arbitrary commands after a container becomes healthy but before any dependent containers start. This is useful for doing any setup that can't be baked into the image. See the docs for more information and an example. (#105 - thanks to @jagregory for the initial suggestion and many others for their comments on that issue)

What's changed

  • ⚠️ batect now requires at least Docker version 17.12 (and 17.12.1 is recommended due to this bug)

Getting started

First time using batect? Take a look at the getting started guide, or the many sample projects.

How to upgrade from previous versions

If you're already using batect, run ./batect --upgrade to upgrade automatically.

Assets 5

@charleskorn charleskorn released this Oct 30, 2019

What's been fixed

  • The issue where building a Dockerfile with an ADD instruction that downloads a file from a URL would fail has been fixed (#270 - thanks to @alpha-er for the feedback)

  • Coloured output will no longer be used if either stdout or stderr are not connected to terminals.

Getting started

First time using batect? Take a look at the getting started guide, or the many sample projects.

How to upgrade from previous versions

If you're already using batect, run ./batect --upgrade to upgrade automatically.

Assets 5

@charleskorn charleskorn released this Oct 11, 2019

What's been fixed

  • The issue where running batect when stdin had been redirected (eg. when running batect as part of a pre-commit hook) would fail on Mac, Linux or Windows has been fixed (thanks to @josh- and @brijesa for the feedback)

Getting started

First time using batect? Take a look at the getting started guide, or the many sample projects.

How to upgrade from previous versions

If you're already using batect, run ./batect --upgrade to upgrade automatically.

Assets 5
You can’t perform that action at this time.