Announcing official support for Jenkins, CircleCI, and TravisCI

Nov 4, 2014 • packagecloud

TL;DR

packagecloud is excited to officially announce support for Jenkins, CircleCI, and TravisCI.

Take a look at the updated docs with example configurations and information on how to push deb, rpm, and gem packages directly to packagecloud from your build process.

If you use a continuous integration system other than Jenkins, CircleCI, or TravisCI, let us know.

New feature tab

Each packagecloud repository now displays an additional feature tab for repository owners and collaborators giving information about how to configure each of the supported build systems to push objects to packagecloud.

CI Tab - packagecloud.io

Jenkins

To push packages to packagecloud from Jenkins you’ll need to install and configure the packagecloud Jenkins plugin.

You can find the step by step installation and configuration instructions on the packagecloud Jenkins plugin wiki page.

There are 3 steps to the configuration process:

  • Plugin installation: begin by finding and installing the Jenkins plugin via the Jenkins UI
  • Credentials setup: next, use Jenkins’ credentials system to store your packagecloud username and API token
  • Configure post-build job: finally, add a post-build step to your Jenkins job, enter the repository to push to, and select the operating system and version

Visiting our Jenkins documentation when logged into packagecloud.io will display your API token and username needed to configure the Jeknins credentials.

CircleCI

To push packages to packagecloud from CircleCI you must:

  • Set an environment variable named PACKAGECLOUD_TOKEN in your project’s settings and the value must match your packagecloud API access token. Visit your API token settings page to get your API token.

  • Create a circle.yml file which installs the package_cloud gem and pushes the package to the OS and version of your choice. For more info on your API access token, please refer to the API Tokens section in API docs.

dependencies:
  pre:
    - gem install package_cloud

deployment:
  production:
    branch: master
    commands:
      - package_cloud push user/repo/os/version ./path/to/package.ext

Travis CI

To push packages to packagecloud from Travis CI you must:

  • Set an environment variable named PACKAGECLOUD_TOKEN in your project’s settings and the value must match your packagecloud API access token. Visit your API token settings page to get your API token.

  • Create a .travis.yml file which installs the package_cloud gem and pushes the package to the OS and version of your choice. For more info on your API access token, please refer to the API Tokens section in API docs.

before_install:
  - gem install package_cloud

script:
  - package_cloud push user/repo/os/version ./path/to/package.ext

Questions? We’re here to help! Email support@packagecloud.io

Never miss an update!

Subscribe to our RSS feed