Docker container orchestration platform

Overview

Helios Circle CI Slack Status Download

Status: Bug-fix only

This project was created when there were no open source container orchestration frameworks. Since the advent of Kubernetes and other tools, we've stopped adding new features to helios and are now switching to other tools like Kubernetes. This project will no longer have new features or accept PRs for new features. We will continue to accept bug fixes, however.

Helios is a Docker orchestration platform for deploying and managing containers across an entire fleet of servers. Helios provides a HTTP API as well as a command-line client to interact with servers running your containers. It also keeps a history of events in your cluster including information such as deploys, restarts and version changes.

Usage Example

# Create an nginx job using the nginx container image, exposing it on the host on port 8080
$ helios create nginx:v1 nginx:1.7.1 -p http=80:8080

# Check that the job is listed
$ helios jobs

# List helios hosts
$ helios hosts

# Deploy the nginx job on one of the hosts
$ helios deploy nginx:v1 <host>

# Check the job status
$ helios status

# Curl the nginx container when it's started running
$ curl <host>:8080

# Undeploy the nginx job
$ helios undeploy -a nginx:v1

# Remove the nginx job
$ helios remove nginx:v1

Getting Started

If you're looking for how to use Helios, see the docs directory. Most probably the User Manual is what you're looking for.

If you're looking for how to download, build, install and run Helios, keep reading.

Prerequisites

The binary release of Helios is built for Ubuntu 14.04.1 LTS, but Helios should be buildable on any platform with at least Java 8 and a recent Maven 3 available.

Other components that are required for a helios installation are:

Install & Run

Quick start for local usage

Use helios-solo to launch a local environment with a Helios master and agent.

First, ensure you have Docker installed locally. Test this by making sure docker info works. Then install helios-solo:

# add the helios apt repository
$ sudo apt-key adv --keyserver hkp://keys.gnupg.net:80 --recv-keys 6F75C6183FF5E93D
$ echo "deb https://dl.bintray.com/spotify/deb trusty main" | sudo tee -a /etc/apt/sources.list.d/helios.list

# install helios-solo on Debian/Ubuntu
$ sudo apt-get update && sudo apt-get install helios-solo

# install helios-solo on OS X
$ brew tap spotify/public && brew install helios-solo

Once you've got it installed, bring up the helios-solo cluster:

# launch a helios cluster in a Docker container
$ helios-up

# check if it worked and the solo agent is registered
$ helios-solo hosts

You can now use helios-solo as your local Helios cluster. If you have issues, see the detailed helios-solo documentation.

Production on Debian, Ubuntu, etc.

Prebuilt Debian packages are available for production use. To install:

# add the helios apt repository
$ sudo apt-key adv --keyserver hkp://keys.gnupg.net:80 --recv-keys 6F75C6183FF5E93D
$ echo "deb https://dl.bintray.com/spotify/deb trusty main" | sudo tee -a /etc/apt/sources.list.d/helios.list

# install Helios command-line tools
$ sudo apt-get install helios

# install Helios master (assumes you have zookeeperd installed)
$ sudo apt-get install helios-master

# install Helios agent (assumes you have Docker installed)
$ sudo apt-get install helios-agent

Note that the Helios master and agent services both try to connect to ZooKeeper at localhost:2181 by default. We recommend reading the Helios configuration & deployment guide before starting a production cluster.

Manual approach

The launcher scripts are in bin/. After you've built Helios following the instructions below, you should be able to start the agent and master:

$ bin/helios-master &
$ bin/helios-agent &

If you see any issues, make sure you have the prerequisites (Docker and Zookeeper) installed.

Build & Test

First, make sure you have Docker installed locally. If you're using OS X, we recommend using docker-machine.

Actually building Helios and running its tests should be a simple matter of running:

$ mvn clean package

For more info on setting up a development environment and an introduction to the source code, see the Developer Guide.

How it all fits together

The helios command line tool connects to your helios master via HTTP. The Helios master is connected to a Zookeeper cluster that is used both as persistent storage and as a communications channel to the agents. The helios agent is a java process that typically lives on the same host as the Docker daemon, connecting to it via a Unix socket or optionally TCP socket.

Helios is designed for high availability, with execution state being confined to a potentially highly available Zookeeper cluster. This means that several helios-master services can respond to HTTP requests concurrently, removing any single point of failure in the helios setup using straight forward HTTP load balancing strategies.

Production Readiness

We at Spotify are running Helios in production (as of October 2015) with dozens of critical backend services, so we trust it. Whether you should trust it to not cause smoking holes in your infrastructure is up to you.

Why Helios?

There are a number of Docker orchestration systems, why should you choose Helios?

  • Helios is pragmatic. We're not trying to solve everything today, but what we have, we try hard to ensure is rock-solid. So we don't have things like resource limits or dynamic scheduling yet. Today, for us, it has been more important to get the CI/CD use cases, and surrounding tooling solid first. That said, we eventually want to do dynamic scheduling, composite jobs, etc. (see below for more). But what we provide, we use (i.e. we eat our own dogfood), so you can have reasonable assurances that anything that's been in the codebase for more than a week or two is pretty solid as we release frequently (usually, at least weekly) into production here at Spotify.

  • Helios should be able to fit in the way you already do ops. Of the popular Docker orchestration frameworks, Helios is the only one we're aware of that doesn't have anything much in the way of system dependencies. That is, we don't require that you run in AWS or GCE, etc. We don't require a specific network topology. We don't require you run a specific operating system. We don't require that you're using Mesos. Our only requirement is that you have a ZooKeeper cluster somewhere and a JVM on the machines which Helios runs on. So if you're using Puppet, Chef, etc., to manage the rest of the OS install and configuration, you can still continue to do so with whatever Linux OS you're using.

  • Don't have to drink all the Kool-Aid. Generally, we try to make it so you only have to take the features you want to use, and should be able to ignore the rest. For example, Helios doesn't prescribe a discovery service: we happen to provide a plugin for SkyDNS, and we hear that someone else is working on one for another service, but if you don't want to even use a discovery service, you don't have to.

  • Scalability. We're already at hundreds of machines in production, but we're nowhere near the limit before the existing architecture would need to be revisited. Helios can also scale down well in that you can run a single machine instance if you want to run it all locally.

Other Software You Might Want To Consider

Here are a few other things you probably want to consider using alongside Helios:

  • docker-gc Garbage collects dead containers and removes unused images.
  • helios-skydns Makes it so you can auto register services in SkyDNS. If you use leading underscores in your SRV record names, let us know, we have a patch for etcd which disables the "hidden" node feature which makes this use case break.
  • skygc When using SkyDNS, especially if you're using the Helios Testing Framework, can leave garbage in the skydns tree within etcd. This will clean out dead stuff.
  • docker-maven-plugin Simplifies the building of Docker containers if you're using Maven (and most likely Java).

Findbugs

To run findbugs on the helios codebase, do mvn clean compile site. This will build helios and then run an analysis, emitting reports in helios-*/target/site/findbugs.html.

To silence an irrelevant warning, add a filter match along with a justification in findbugs-exclude.xml.

The Nickel Tour

The sources for the Helios master and agent are under helios-services. The CLI source is under helios-tools. The Helios Java client is under helios-client.

The main meat of the Helios agent is in Supervisor.java, which revolves around the lifecycle of managing individual running Docker containers.

For the master, the HTTP response handlers are in src/main/java/com/spotify/helios/master/resources.

Interactions with ZooKeeper for the agent and master are mainly in ZookeeperAgentModel.java and ZooKeeperMasterModel.java, respectively.

The Helios services use Dropwizard which is a bundle of Jetty, Jersey, Jackson, Yammer Metrics, Guava, Logback and other Java libraries.

Community Ideas

These are things we want, but haven't gotten to. If you feel inspired, we'd love to talk to you about these (in no particular order):

  • Host groups
  • ACLs - on jobs, hosts, and deployments
  • Composite jobs -- be able to deploy related containers as a unit on a machine
  • Run once jobs -- for batch jobs
  • Resource specification and enforcement -- That is: restrict my container to X MB of RAM, X CPUs, and X MB disk and perhaps other things like IOPs, network bandwidth, etc.
  • Dynamic scheduling of jobs -- either within Helios itself or as a layer on top
  • Packaging/Config for other Linux distributions such as RedHat, CoreOS, etc.
Issues
  • Agent re-registration now preserves jobs deployed on the replaced host

    Agent re-registration now preserves jobs deployed on the replaced host

    I.e. if agent A has job J deployed to it, and is then replaced by agent B under the same name the B will also automatically get J deployed to it.

    Previously, the automatic re-registration would fail if there were any deployed jobs on the host being replaced -- which was the case almost all of the time. With this in place, the automatic re-registration should actually work. (History of any existing jobs will also be preserved.)

    opened by gimaker 23
  • Doesn't run in 250 MB RAM

    Doesn't run in 250 MB RAM

    Hi,

    I tried your mvn clean test and ran into a "There is insufficient memory for the Java Runtime Environment to continue." issue, not sure why you need more than 250MB to build helios, doesn't seem too big of an application.

    Best Regards,

    opened by ramonck 22
  • Add support for specifying resources for a container

    Add support for specifying resources for a container

    Hi!

    This PR makes it possible to specify runtime constraints for a container, such as memory and cpu usage. Currently it's not exposed in the cli, but you can set the parameters if you create a job from a json file.

    Example:

    python-hello.json:

    {
      "image" : "google/python-hello:2.7",
      "resources" : {
        "cpuShares" : 512,
        "cpuset" : "0",
        "memory" : 104857600,
        "memorySwap" : 1024
      }
    }
    

    helios create -f python-hello.json python-hello:v1 docker inspect on the running container will then return something like this:

    [
      {
        "Config": {
          "Cpuset": "0",
          "CpuShares": 512,
          "Memory": 104857600,
          "MemorySwap": 1024,
          "..."
        },
      }
    ]
    
    enhancement 
    opened by carlanton 19
  • Helios web front-end??

    Helios web front-end??

    Hi do not know if this is place to ask. Helios has a restful API for interacting with helios-master as does helios cli. I would like to contribute to the project, creating a front-end to manage helios via web.

    I hope to help this project grow. Thanks for everything.

    help wanted 
    opened by alejandrojnm 19
  • Support resolution of namespaced agent names in Helios Solo.

    Support resolution of namespaced agent names in Helios Solo.

    @spotify/helios-team

    Hopefully this PR is reaching its final form. It:

    • Fixes the helios solo container's start.sh such that namespaced Helios agent names (i.e. mynamespace.solo.local) are resolvable by SkyDNS.
    • Tweaks the namespaced Helios agent names to end in .local for compatibility with our SkyDNS setup.
    • Supports specifying arbitrary env vars to be set inside the HeliosSoloDeployment container.
    • Supports reading said env vars from helios.conf
    • Updates an existing service discovery integration test to use a HeliosSoloDeployment.

    The culmination of the above should mean we can specify our whacky Spotify SRV record format as an env var in spotify-helios-testing's helios.conf and leave our defaults sane for everyone else. That will look something like:

    helios.solo.profile : "local"
    helios.solo.profiles : {
      local : {
        env : {
            REGISTRAR_HOST_FORMAT: "_spotify-${service}._${protocol}.services.${domain}"
        }
      }
    }
    
    opened by negz 19
  • Add health check gauge

    Add health check gauge

    null

    opened by davidxia 18
  • client: Use ssh-agent identity for TLS client auth

    client: Use ssh-agent identity for TLS client auth

    Use the local SSH agent identity to generate a self-signed certificate for TLS client authentication, and sign the handshake hash with ssh-agent.

    This lets the client setup a secure SSL connection and prove ownership of its SSH public key. It is up to the server to verify the public key against a known-good list (like in LDAP).

    opened by rohansingh 16
  • Helios Testing broken with Docker for Mac (beta)

    Helios Testing broken with Docker for Mac (beta)

    The Docker for Mac beta ships a Docker setup packaged and well running on top of xhyve. Though the docker CLI is smart enough to find it (it knows where the socket is) other tools that look for the docker daemon need the DOCKER_HOST environment variable to be set. In this case, it should point at unix:///var/tmp/docker.sock.

    Unfortunately setting DOCKER_HOST seems to break the TemporaryJobs.builder() as that contains a fair amount of glue to try and figure out where the heck Docker went. This results in the following stack trace:

    [main] WARN com.spotify.helios.client.Endpoints - Unable to resolve hostname null into IP address
    java.net.UnknownHostException: null: unknown error
        at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
        at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
        at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)
        at java.net.InetAddress.getAllByName0(InetAddress.java:1276)
        at java.net.InetAddress.getAllByName(InetAddress.java:1192)
        at java.net.InetAddress.getAllByName(InetAddress.java:1126)
        at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45)
        at com.spotify.helios.client.Endpoints.of(Endpoints.java:92)
        at com.spotify.helios.client.Endpoints.of(Endpoints.java:79)
        at com.spotify.helios.client.HeliosClient$Builder.setEndpoints(HeliosClient.java:532)
        at com.spotify.helios.client.HeliosClient$Builder.setEndpointStrings(HeliosClient.java:548)
        at com.spotify.helios.testing.TemporaryJobs$Builder.endpointStrings(TemporaryJobs.java:663)
        at com.spotify.helios.testing.TemporaryJobs$Builder.endpoints(TemporaryJobs.java:658)
        at com.spotify.helios.testing.TemporaryJobs$Builder.configureWithEnv(TemporaryJobs.java:602)
        at com.spotify.helios.testing.TemporaryJobs$Builder.<init>(TemporaryJobs.java:562)
        at com.spotify.helios.testing.TemporaryJobs.builder(TemporaryJobs.java:507)
        at com.spotify.helios.testing.TemporaryJobs.builder(TemporaryJobs.java:502)
        at com.spotify.helios.testing.TemporaryJobs.builder(TemporaryJobs.java:494)
        at com.spotify.helios.testing.TemporaryJobs.builder(TemporaryJobs.java:490)
        at com.spotify.podservice.client.HttpPodserviceClientIT.<clinit>(HttpPodserviceClientIT.java:23)
        at sun.misc.Unsafe.ensureClassInitialized(Native Method)
        at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:43)
        at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:142)
        at java.lang.reflect.Field.acquireFieldAccessor(Field.java:1088)
        at java.lang.reflect.Field.getFieldAccessor(Field.java:1069)
        at java.lang.reflect.Field.get(Field.java:393)
        at org.junit.runners.model.FrameworkField.get(FrameworkField.java:73)
        at org.junit.runners.model.TestClass.getAnnotatedFieldValues(TestClass.java:230)
        at org.junit.runners.ParentRunner.classRules(ParentRunner.java:255)
        at org.junit.runners.ParentRunner.withClassRules(ParentRunner.java:244)
        at org.junit.runners.ParentRunner.classBlock(ParentRunner.java:194)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:362)
        at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:344)
        at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:269)
        at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:240)
        at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:184)
        at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:286)
        at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:240)
        at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
    

    I believe that this is caused by the following code path: https://github.com/spotify/helios/blob/83bb315662db0b1eede2385a178e2afe48d633e2/helios-testing/src/main/java/com/spotify/helios/testing/TemporaryJobs.java#L565-607

    We end up hitting L596 and because DOCKER_HOST is set and will now try to parse unix:///var/tmp/docker.sock as a URI and call getHost() on it, which will return null. Because of the string concat and not explicitly checking for that null it means we end up adding an endpoint of http://null:5801.

    This in turn causes the eventual java.net.UnknownHostException: null: unknown error when we try to do the DNS lookup for the host part of the endpoint.

    opened by daenney 16
  • Upgrade server side components to Java 8

    Upgrade server side components to Java 8

    Leave client side on Java 7 so we don't break projects using TempJobs or HeliosClient.

    enhancement 
    opened by davidxia 15
  • Introduce a 'rolling operation' concept.

    Introduce a 'rolling operation' concept.

    The target job ID and rollout options of a rolling update are associated with the rolling operation - not the deployment group itself. Each rolling operation is associated with a deployment group. The 'reason' for a rolling update (i.e. manual or 'hosts changed') is a property of the rolling operation.

    Deployment groups may now have state 'stable' or 'unstable'. Stable deployment groups are known to be running the same job across all agents. Unstable groups are known to have some containers down, or to be running different jobs across agents. Rolling operations model the states previously associated with deployment groups (ROLLING_OUT, DONE, FAILED).

    Some hacks (i.e. the DeploymentGroupResponse) have been put in place in order to avoid breaking the existing REST and CLI APIs.

    This change means:

    • A failed rolling update will no longer require human intervention to unblock future automatic (i.e. 'hosts changed') rolling updates.
    • Rolling restarts could be implemented as a variant of a rolling operation - perhaps as a rolling operation with a null jobId?
    • We could expose an audit trail of a deployment group's rolling updates.
    opened by negz 15
  • Bump commons-io from 2.5 to 2.7

    Bump commons-io from 2.5 to 2.7

    Bumps commons-io from 2.5 to 2.7.

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Bump jackson-databind from 2.9.10 to 2.9.10.7

    Bump jackson-databind from 2.9.10 to 2.9.10.7

    Bumps jackson-databind from 2.9.10 to 2.9.10.7.

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 1
  • Docs improvement for `rolloutOptions`

    Docs improvement for `rolloutOptions`

    Hi!

    Have a look here: https://github.com/spotify/helios/blob/master/docs/user_manual.md#rolloutoptions

    I would like to know details about these rolloutOptions fields:

    • migrate: what does this do?
    • parallelism: number of nodes that will be updated in parallel I assume, pretty certain about this one
    • timeout: is this in seconds? Is it per node or for the whole rollout job?
    • overlap: what does this do?
    • token: where is this token used? why is it "insecure"?
    • ignoreFailures: what happens on failures with this on? Is the rollout marked as success in spite of the failures?
    opened by walles 1
  • Bump junit from 4.12 to 4.13.1

    Bump junit from 4.12 to 4.13.1

    Bumps junit from 4.12 to 4.13.1.

    Release notes

    Sourced from junit's releases.

    JUnit 4.13.1

    Please refer to the release notes for details.

    JUnit 4.13

    Please refer to the release notes for details.

    JUnit 4.13 RC 2

    Please refer to the release notes for details.

    JUnit 4.13 RC 1

    Please refer to the release notes for details.

    JUnit 4.13 Beta 3

    Please refer to the release notes for details.

    JUnit 4.13 Beta 2

    Please refer to the release notes for details.

    JUnit 4.13 Beta 1

    Please refer to the release notes for details.

    Commits
    • 1b683f4 [maven-release-plugin] prepare release r4.13.1
    • ce6ce3a Draft 4.13.1 release notes
    • c29dd82 Change version to 4.13.1-SNAPSHOT
    • 1d17486 Add a link to assertThrows in exception testing
    • 543905d Use separate line for annotation in Javadoc
    • 510e906 Add sub headlines to class Javadoc
    • 610155b Merge pull request from GHSA-269g-pwp5-87pp
    • b6cfd1e Explicitly wrap float parameter for consistency (#1671)
    • a5d205c Fix GitHub link in FAQ (#1672)
    • 3a5c6b4 Deprecated since jdk9 replacing constructor instance of Double and Float (#1660)
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Bump org.bouncycastle

    Bump org.bouncycastle

    opened by oberkem 0
  • Upgrade dropwizard-core dep from 0.7.1 to 0.9.2

    Upgrade dropwizard-core dep from 0.7.1 to 0.9.2

    which includes this fix https://github.com/dropwizard/dropwizard/issues/523.

    opened by davidxia 0
  • Upgrade dropwizard-core dep from 0.7.1 to 0.9.3

    Upgrade dropwizard-core dep from 0.7.1 to 0.9.3

    which includes this fix https://github.com/dropwizard/dropwizard/issues/523.

    opened by davidxia 1
  • Support jackson 2.11.0+

    Support jackson 2.11.0+

    Jackson 2.11.0 changes the default _tzSerializedWithColon value from false to true, this causes a "Id hash mismatch" when trying to deploy a job. withColonInTimeZone has been available since 2.9.1 so this will break on older version, If this is an issue we would probably have to resort to reflection.

    opened by jwiklund 10
  • Bump netty-all from 4.1.5.Final to 4.1.42.Final

    Bump netty-all from 4.1.5.Final to 4.1.42.Final

    Bumps netty-all from 4.1.5.Final to 4.1.42.Final.

    Commits
    • bd907c3 [maven-release-plugin] prepare release netty-4.1.42.Final
    • 2791f0f Avoid use of global AtomicLong for ScheduledFutureTask ids (#9599)
    • 86ff76a Fix incorrect comment (#9598)
    • 5e69a13 Cleanup JNI code to always correctly free memory when loading fails and also ...
    • eb3c4bd ChunkedNioFile can use absolute FileChannel::read to read chunks (#9592)
    • 76592db Close eventfd shutdown/wakeup race by closely tracking epoll edges (#9586)
    • 0a2d85f Fix GraalVM native image build error (#9593)
    • dc4de7f We need to use NewGloblRef when caching jclass instances (#9595)
    • 4499384 Update to netty-tcnative 2.0.26.Final (#9589)
    • 8648171 Fix *SslEngineTest to not throw ClassCastException and pass in all cases (#9588)
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    opened by dependabot[bot] 0
  • bump joda-time, unify version to 2.9.2 to avoid inconsistency

    bump joda-time, unify version to 2.9.2 to avoid inconsistency

    unify joda-time versions across modules to avoid inconsistency.

    opened by kaifeng-h 1
Releases(0.9.282)
Owner
Spotify
Spotify
Packages your JAR, assets and a JVM for distribution on Windows, Linux and Mac OS X

About Packages your JAR, assets and a JVM for distribution on Windows, Linux and macOS, adding a native executable file to make it appear like a nativ

libgdx 2.2k Mar 14, 2021
IzPack - Source Code

IzPack IzPack is a widely used tool for packaging applications on the Java platform as cross-platform installers. License IzPack is published under th

IzPack 260 Mar 11, 2021
Adaptable, fast automation for all

Gradle is a build tool with a focus on build automation and support for multi-language development. If you are building, testing, publishing, and depl

Gradle 11.6k Mar 12, 2021