Using Codesion Git Repositories with DEV@cloud Jenkins

The CloudBees Ecosystem provides a set of services that are integrated with the core CloudBees services. Codesion is the newest entrant into the ecosystem. Codesion provides code repositories, issue tracking services and others (full listing here). 

Signing up for Codesion
Once logged into CloudBees, go to the Services menu and click on Codesion (if you are currently logged in to DEV@cloud, the Subscribe to Codesion Service link will take you to the page). Enter the appropriate configuration information. You will get an email from the Codesion team with the domain, email and password for the Codesion instance provisioned for you. 

Click on the Codesion link in CloudBees Services menu and you will land at Codesion hub, enter the provided credentials to start using Codesion. 

You can create new repositories by clicking the Projects tab and creating a new project and choosing the appropriate repository type within the project. 

Setting up Access Control 

For each repository, we need at least two users that can access the repository. The first users (actually type of users) are developers who can commit code and the second type of user is the Jenkins instance that will checkout code and run the builds. 

To create the users, go to the People tab in the Codesion hub and add a new user. For each user, you need to enter an SSH public key to access the account. Setting up the SSH key is fairly straightforward for a developer (the developer should enter the one they are using). For Jenkins to gain access, you need to pick the key from the CloudBees DEV@cloud Authorization -> CloudBees Public Key field from the configuration of a job.

Enter this key into the key field of the user config within the Codesion user config page.

The last step is to add these users to the project (aka repository) so that the repository service can allow access to these users. Go to Projects->PROJECT NAME->People on Codesion Hub and add the users that you just created. 

Once done - you should have access to the repositories and be able to build it from the CloudBees DEV@cloud instance. 

- Harpreet Singh
Senior Director, Product Management
Blog Categories: 

Add new comment