Maven feeds

Maven repositories can be configured as an external feed, allowing the artifacts contained in the repository to be consumed by the Octopus steps that deploy Java packages, as well as the generic Transfer a package step.

Adding an external Maven feed

The following steps can be followed to add an external Maven feed.

  1. Select Library ➜ External feeds and click the ADD FEED button.
  2. Select Maven Feed from the Feed Type field.
  3. Enter the name of the feed in the Feed name field.
  4. In the Feed url field, enter the URL of the Maven feed. The URL must point to the directory under which the initial directory that makes up the Maven artifact group ids are found. For example, for the Maven central repo the URL is and the SonaType Snapshot repo URL is
  5. If the Maven repository is password protected, the credentials can be entered into the Feed login and Feed password field.
  6. The *Download attempts (attempts)* field defines the number of times that Octopus will attempt to download an artifact from a Maven repository. Failed attempts will wait for the number of seconds defined in the Download retry backoff (seconds) field before attempting to download the artifact again.

When configuring external Maven repositories, we need to link to the repository itself and not the services that are used to search the repositories. For example URLs like or can’t be entered because these are sites for searching the repositories, and not the repositories themselves.

Referencing Maven artifacts

When referencing a Maven artifact, the package ID is in the format group:artifact.

For example, to reference the Maven artifact with the group of org.wildfly.swarm.testsuite and artifact of testsuite-https (i.e. the artifacts found at, you would enter a package ID of org.wildfly.swarm.testsuite:testsuite-https.

Maven Artifact Names

Prior to 2020.3.0, the packaging type is determined automatically from the extensions supported by Octopus, which are:

  • zip
  • jar
  • ear
  • rar
  • war

So the package ID org.wildfly.swarm.testsuite:testsuite-https for version 2017.10.0 would download the WAR file

Since 2020.3.0, Maven artifacts can be specified with an optional packaging and classifier. For example, the artifact ID of org.example:myartifact:zip will select the ZIP package with the group org.example and the artifact ID of myartifact, or org.example:myartifact:jar:sources will select the JAR package with the sources classification.

The packaging must be defined when using a classifier.

If no packaging selection is specified, the first matching package is selected from the list of extensions above.

Searching for Maven artifacts

As Maven repositories do not expose an API (repositories are just a filesystem structure), there is no way to search them in Octopus the way you might search a NuGet repository. The package ID for a Maven artifact must be complete for Octopus to identify it, and partial package IDs will not return a list of partial matches.

Maven Package Suggestion

Downloading SNAPSHOT releases

When downloading SNAPSHOT releases of Maven artifacts, the latest SNAPSHOT version will be downloaded. This version is then saved in the Octopus cache, and will be reused in subsequent deployments of the same SNAPSHOT version.

What this means is that if a new SNAPSHOT artifact is published to the Maven repository after Octopus has saved the previous SNAPSHOT artifact to its local cache, Octopus will continue to use the older locally cached version.

To force Octopus to download the newer SNAPSHOT release, select the Re-download packages from feed option when deploying.

Re-download packages from feed

Versioning with Maven feeds

When using artifacts from a Maven feed, the Maven versioning scheme is used.

The following qualifiers in the version are used to indicate that it is a pre-release version:

  • alpha (or the a shorthand) e.g. 1.0.0-alpha1 or 1.0.0-a1.
  • beta (or the b shorthand) e.g. 1.0.0-beta1 or 1.0.0-b1.
  • milestone (or the m shorthand) e.g. 1.0.0-milestone1 or 1.0.0-m1.
  • rc or cr e.g. 1.0.0-rc1 or 1.0.0-cr1.
  • SHAPSHOT e.g. 1.0.0-SNAPSHOT.

Version ranges with Maven feeds

When defining versions ranges against artifacts sourced from a Maven feed (when defining a channel rule for example), the Maven range specification is used. The table below shows some common examples of Maven version ranges.

1.0x >= 1.0 * The default Maven meaning for 1.0 is everything (,) but with 1.0 recommended. Obviously this doesn’t work for enforcing versions here, so it has been redefined as a minimum version.
(,1.0]x <= 1.0
(,1.0)x < 1.0
[1.0]x == 1.0
[1.0,)x >= 1.0
(1.0,)x > 1.0
(1.0,2.0)1.0 < x < 2.0
[1.0,2.0]1.0 <= x <= 2.0
(,1.0],[1.2,)x <= 1.0 or x >= 1.2. Multiple sets are comma-separated
(,1.1),(1.1,)x != 1.1

Troubleshooting Maven feeds

  1. Can you download the POM file directly from the Maven repository from the Octopus Server? For example, the Google Guava POM file for version 24.0-jre is If you can not, then there is likely to be an issue with the URL or your network settings.
  2. The Maven URL to be configured in Octopus includes the path up to the to the start of the group id. For Guava, the group id is This maps to the com/google/guava component of the URL. So the Maven URL to be configured in Octopus is, because this is the part of the URL that does not include the group id.
  3. Maven artifacts must be referenced in the group:artifact format. For Guava, the group is and the artifact is guava. So this would be referenced in Octopus as

Help us continuously improve

Please let us know if you have any feedback about this page.

Send feedback

Page updated on Sunday, January 1, 2023