Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Sharing Bluemix DevOps Pipelines with the Application's Source Code

DZone's Guide to

Sharing Bluemix DevOps Pipelines with the Application's Source Code

A quick look at using DevOps pipelines in IBM Bluemix that allow developers to define how to build and deploy their applications.

· DevOps Zone
Free Resource

Best practices for getting to continuous deployment faster and with dramatic results in reduced outage minutes, development costs, and QA testing cycles. Brought to you by Rainforest QA.

With DevOps pipelines in IBM Bluemix developers can define how to build and deploy their applications. For example, applications packaged via Docker. Pipelines can be created manually via the Bluemix web experience and they can be shared as part of the application source code.

This capability is imported when, for example, you want to allow other people to fork your project and deploy it directly to Bluemix via the Bluemix Deploy Button. The documentation describes how to generate a file that includes the pipeline definition. This file needs to be named "pipeline.yml" and put in the directory ".bluemix".

The screenshot below shows how to generate that file. At this point the mechanism might not be the most intuitive one. You have to append "/yaml" to your URL "hub.jazz.net/pipeline/owner/project_name/yaml".

To find out more read the documentation and the blog Forking pipelines from my colleague Robbie Minshall. He describes how to change the generated pipeline file before you should share it by replacing hardcoded values like organization and space names. He also refers to some Bluemix pipeline samples on GitHub that you can use to get started.


Discover how to optimize your DevOps workflows with our on-demand QA solution, brought to you in partnership with Rainforest QA.

Topics:
bluemix ,devops ,cloud

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

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}