DZone
DevOps Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > DevOps Zone > Leveraging Jenkins in DevOps Toolchains on Bluemix

Leveraging Jenkins in DevOps Toolchains on Bluemix

In this post, we take a look at how to integrate Jenkins with your DevOps toolchain running with IBM Bluemix. Find out how to do this useful integration!

Niklas Heidloff user avatar by
Niklas Heidloff
CORE ·
Jun. 18, 17 · DevOps Zone · Tutorial
Like (4)
Save
Tweet
5.23K Views

Join the DZone community and get the full member experience.

Join For Free

as part of the ibm bluemix continuous delivery functionality, toolchains allow the integration of third-party and open source tools. one example is the usage of the automation server jenkins to build and deploy applications rather than using the delivery pipelines provided by ibm.

in order to test this functionality, i’ve run a docker jenkins container locally. obviously, you could also deploy jenkins on bluemix, but i wanted to keep it as simple as possible.

in order to configure jenkins, i suggest following the instructions from my colleague eric jodet in the jenkins wiki, since they are more up to date than the instructions currently in the bluemix documentation. also, i struggled to get the cloud foundry deployment to work. i had to install the cf cli manually on my container first.

once everything is configured, you can run jenkins jobs.

jenkins-devops1

in order to send information to ibm cloud devops, different post build actions can be defined.

jenkins-devops2

toolchains receive this data from jenkins and can forward it to other tools, like slack, that are in the same toolchains.

jenkins-devops3

i also like that deployment information is directly added to git issues; for example, links to toolchains and releases as well as labels to mark issues as deployed.

jenkins-devops4

to find out more, read the blog from eric, read the documentation , or try the sample toolchain " deployment risk analytics with github and jenkins ."


Jenkins (software) Bluemix DevOps

Published at DZone with permission of Niklas Heidloff, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Take Control of Your Application Security
  • Refactoring Java Application: Object-Oriented And Functional Approaches
  • ETL, ELT, and Reverse ETL
  • Challenges to Designing Data Pipelines at Scale

Comments

DevOps Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo