Getting started
IntroductionInstalled packagesEnvironment variablesDebugging buildsCachingParallel testingDeployment pipelinesRunning commands as rootIgnoring commandsRun a command in case of an errorSetting timezoneAccess to other repositoriesUsing scriptsGit LFSUbuntu 20.04 Focal
IntroductionFTP/SSH/SFTP/RSYNCCustom scriptHerokuHeroku MigrationAWS Elastic BeanstalkAWS CodeDeployAWS LambdaAWS S3Google App EngineAWS CLIgcloud CLIAzure CLIDigital OceanEngine YardCapistranoGit PushCloudFoundryCloud66anynines
IntroductionBrowser testingBackground commandsGit submodulesCustom DNSArtifacts
IntroductionCassandraCouchDBDynamoDBMongoDBMySQLPostgreSQLSQLite
IntroductionDartElixirGoJava and JVMMeteorNode.jsPHPPythonRubyRust
IntroductionBeanstalkdRabbitMQRedis
IntroductionElasticsearchMemcachedSphinx
IntroductionCloudBees CodeShip Pro introduction guideCloudBees CodeShip Pro introduction guide 2CloudBees CodeShip Pro introduction guide 3CloudBees CodeShip Pro introduction guide 4CloudBees CodeShip Pro introduction guide 5
Migrating to CloudBees CodeShip Pro
Docker for CI/CD
Getting started with CloudBees CodeShip Pro overview and resources
IntroductionServices configSteps configEnvironment variablesImage registriesImage cachingBuild argumentsVolumesHandling secretsMultiple reposServices and databasesSetting an SSH private keyPreinstalled images
IntroductionInstallationUsing the Jet CLIjet cleanupjet decryptjet encryptjet generatejet loadjet runjet stepsjet updatejet validatejet version
IntroductionAWSAWS S3AWS EBAWS ECSAWS EKSAWS CodeDeployAzure Container ServiceHerokuGoogle CloudGoogle App EngineGoogle Cloud FunctionsGoogle Container EngineGoogle Compute EngineKubernetesTerraformDeploy Via SSHDocker SwarmIBM Cloud FoundryIBM Cloud Container Service
IntroductionBrowser testingParallel testing
IntroductionElixirGoJava and JVMNode.jsPHPPythonRuby
IntroductionCaching multi-stage DockerfileContainer is slow to exitDiffering results with Jet CLIDocker Hub rate limitingManaging multiple environments for a serviceReducing log output from dependent containersStep log not appearingUsing env vars in command steps

Using the CloudBees CodeShip API for CI/CD workflows

2 minute read

CloudBees CodeShip API v2

The CodeShip API v2 provides a number of ways for you to programmatically interact with your projects on CodeShip.

To get started visit the API v2 documentation for all the details. If you need help with the API please reach out to our support team.

Core Use Cases

The API is focused on solving a specific set of core use cases:

  • Custom Dashboards - Mix and match data from CodeShip with other systems to create custom dashboards. See this example for inspiration on how to get started.

  • Chaining Projects - Trigger a downstream project based on results from one or more upstream projects, and potentially information from outside of CodeShip. If you’re looking to chain multiple CodeShip projects, consider relying on a notification webhook as the trigger instead of polling the API for updates to the upstream build. See this example for some ideas.

  • Trigger New Builds - Scheduled builds, builds triggered by events in external systems, or just giving QA a button on a webpage to trigger a build.

  • Automatic Project Creation - For those who frequently create new projects you can automatically provision a project on CodeShip, together with provisioning a new repo, test environment, etc.

Available Endpoints

With the above scenarios as a guide, there are these specific endpoints:

  • Authentication and authorization

  • Projects

  • Builds

Projects Endpoint

For projects, you’re able to do most CRUD operations which should allow you to automate most of your project maintenance tasks; especially useful for those with 10s or 100s of projects. There is currently no delete action on projects.

Builds Endpoint

Builds can’t be deleted, but otherwise you can do most anything with them. You can even go a level deeper than what the CodeShip UI offers. If you restart a build, the old build data is kept around, but the UI only shows the latest. With the builds endpoint you can get the information on those old builds as well.

In terms of commands on the builds endpoint, we’ve deviated slightly from "textbook REST" and have allowed endpoints to /restart an existing build or /stop a running build. If you want to trigger a build that pulls the latest code from a given branch, you would POST to the /builds endpoint with the project and the branch in question. More details can be found on this in the API v2 documentation.

API Clients

Go

If you’re using Go for your automation, you can get started more quickly with our CodeShip Go API client. There’s a good introduction in the repo, and also full documentation.

The Go library is released with the MIT license, so feel free to use it as you will. If you have suggestions, bugs or otherwise want to contribute to the project, please use the GitHub issues to submit these (or submit a PR).

Using Anchore
Using Appranix