Creating a project in Bluemix DevOps Services
Last updated: 23 June 2016
In an IBM® Bluemix™ DevOps Services project, one or more people can build, share, organize, and manage versions of resources to achieve a goal. Usually, that goal is to create an app. After you create an app in a DevOps Services project, you can deploy the app to IBM® Bluemix™.
- Creating a project from DevOps Services
- Creating a project from the command-line
- Forking a project from DevOps Services
- Creating a project from Bluemix
- Cloning an app by using the Deploy to Bluemix button
When you configure a DevOps Services project to deploy to Bluemix, the project is associated with an organization (org) and space in Bluemix for billing purposes. You can configure the project's pipeline and Web IDE workspace to deploy to any org and space in Bluemix that you have access to.
When you deploy your project to Bluemix, the project becomes a Bluemix app that you can enable services for, such as the Track & Plan service or the Delivery Pipeline service.
You can start a project in several ways. If you want to start by using new code or an existing Git repository, create a project. You can create a project from DevOps Services or from the command line. If you want to start from a copy of the code in another project, fork the code. If you already have an app in IBM Bluemix, you can create a DevOps Services project from the app. You can also clone a fully functioning app by using the Deploy to Bluemix button.
Before you begin
To create a DevOps Services project, you need a Bluemix account. Bluemix accounts provide access to everything you need to develop, track, plan, and deploy apps. You can sign up for a free 30-day trial.
Creating a project from DevOps Services
Log in to DevOps Services. The My Projects page opens.
If this project is your first project, click Start coding. Otherwise, click CREATE PROJECT.
Type the project name.
Select a repository type.
- If you are familiar with GitHub, you can create or link to a GitHub repository. To use a new GitHub repository, click the Create a new repository icon, and then click the Create a Git repo on GitHub icon. If you already have your code in a GitHub repository, you can continue to use that repository with this project. Click the Link to an existing repository icon, and then select the repository from the list.
- If you are familiar with Git and want to create a hosted repository, click the Create a new repository icon, and then click the Create a Git repo on Bluemix icon.
Tip: You can host a local Git repository on DevOps Services. First, create the DevOps Services project; then, force push the local repository to the new hosted repository.
- If you are familiar with IBM® Rational Team Concert™ and want to use Jazz™ source control management (SCM), click the Create a new repository icon, and then click the Create Jazz SCM on Bluemix icon.
If you want to control who can view your project and its code, select the Private Project check box. DevOps Services users who you invite can access your private projects.
Note: To create a private repository on GitHub, you must have a paid GitHub account. If necessary, click Change your GitHub plan or use a private Bluemix repository instead.
If you want to use all of the Track & Plan features, including the ability to create sprints from the project backlog of work items, select the Add features for Scrum development check box.
If you want to use only the traditional planning feature, which uses tasks and iterations without a backlog, clear the check box.
To deploy the project code to Bluemix, select the Make this a Bluemix Project check box.
Creating a project from the command-line
Open a command-line window.
Navigate to a new directory or a directory that already contains code or a cloned Git repo.
Tip: To work with code that is already stored in a GitHub or similar repo,
git clonethe repo to a local directory.
Log in to Bluemix:
When you are prompted for credentials, enter your user ID and personal access token or your IBM id and password.
Note: Your user ID for DevOps Services can be either an IBM id or a federated ID (corporate ID). If you use federated authentication, to log in to your command-line client, you must use a personal access token instead of a password. If you don't use federated authentication, your IBM id and password work with all clients. For more information about creating a personal access token, see What’s federated authentication and how does it affect me?
Start the project creation process by entering
bl createand then follow the prompts on the command line.
If you are creating a project from scratch or from code that is on your computer, a Git repo that is hosted on Bluemix will be created for your code.
If you are creating a project and already have code in a GitHub repo, your new DevOps Services project will be linked with your existing repo.
After you define all of your project details, the Bluemix Live Sync command-line interface creates a DevOps Services project. During project creation, a new DevOps hosted Git repo will be set up and populated with your code or the project will be linked to your existing Git repo. Finally, the code is deployed to Bluemix. Once complete, committing changes to your Git repo, reguardless of where it is hosted, will trigger a new build from the DevOps Services Pipeline.
For more information about the bl command line, see bl commands
Forking a project from DevOps Services
When you fork a project, the original project's source is copied into a new DevOps Services project that you own. You might fork a project for these purposes:
- To implement a feature by following a different process or plan
- To propose changes to a project
- To use another project as the starting point for a new idea
Although the complete source of the original project is copied, you'll notice that aspects of the original project are not in the new project. For example, Build & Deploy pipelines, Track & Plan work items, and any other Bluemix services that were bound to the original project are not in the new project. You can add those services to the new project.
Click EXPLORE, find the project to start from, and click its name.
Click FORK PROJECT.
In the Fork Project window that opens, type your project name, review the contents of the window, and specify options as needed. For more information about the options, see Starting a Bluemix DevOps Services project.
Changing the org or space for a project
After you fork your project, you might need to change the specified org or space. For example, if the org that is selected for the forked project cannot be found, specify a different org to deploy the project.
To change the org or space:
- On the project's Overview page, click the Settings icon.
- Click OPTIONS.
- In the Make this a Bluemix Project section, change the selected org or space.
- Click SAVE.
Creating a project from Bluemix
On your Bluemix Dashboard, click the app to create a DevOps Services project for.
On the app's Dashboard, in the upper-right corner, click ADD GIT.
Review the message and click CONTINUE.
After the repository is created, review the new message and click CLOSE.
Access the new DevOps Services project by clicking EDIT CODE.
If you wrote code for your app, push your code to your project's repository.
Cloning an app by using the Deploy to Bluemix button
App developers can embed the Deploy to Bluemix button in many kinds of content, including readme files, blogs, articles, and web pages. The button is useful when you want to set up a cloned version of an app that is publicly available from a Git repository, such as DevOps Services or GitHub. For more information about the button, see Creating a Deploy to Bluemix button.
When you click the button, Bluemix opens, the app is cloned, any necessary build tools are set up, and the Cloud Foundry script to deploy the app to your Bluemix account is provided. With the Deploy to Bluemix button, you can confidently clone and deploy apps to Bluemix.
Click for an app to open the Deploy to Bluemix page.
Log in to or sign up for Bluemix.
Name your new app and specify any options as needed.
When the deployment is completed, a private DevOps Services project is set up. The project contains a running instance of the app, back-end services, and a dedicated Git repository that you can use to make updates to the app.
© Copyright IBM Corporation 2013, 2016.