This guide should include:
- Why Use Debian Packages
- Creating Debian Packages
Why Use Debian Packages
While Spinnaker is flexible to use any dependency management system, it is predisposed to manage Debian packages due to its default settings with Rosco, Orca and Jenkins.
Out-of-the-box settings for Spinnaker look for an archived package with a
.debsuffix within Jenkins. It also grabs the version from the package and automatically appends it to the package name within Rosco. This makes it easy to specify your package in Rosco without the version number,
mycompany-appbut during the bake provisioning process it will install the version that was specified by the Jenkins build:
Debian packaging allows service teams to easily add their app specific configuration to common packer templates. If you’re using any Debian linux based system (Ubuntu, DSL, Astra, etc) you’ll likely be using Debian packages for your system configuration and dependency management so it’s a natural extension to use it for your own applications. Using Debian packages will help reduce the variations in packer templates or variables passed to packer templates during the bake process.
Creating Debian Packages
Creating a Debian package can be done through various open-source packaging tools. If you’re using Java, using the
OS Package library is a good place to start. Of course you can always use the packaging tools provided by Debian. Here is a good example of using a Debian package for a Spinnaker configuration repo.
Example: Debian Package with OSPackage Gradle Plugin
Begin by creating a
build.gradle. Below is an example of what a gradle file might look like for a application that builds a war.
Then build your Debian package based on your gradle build file:
If the build succeeds then you should find a Debian package in the following path: