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

Meteor

2 minute read

Versions and setup

Meteor is not installed on CloudBees CodeShip Basic by default, but it can be easily added.

First run Meteor’s default installer:

\curl https://install.meteor.com/ | sh
▼

Custom Versions

This setup script will always pull for the most recent meteor tool. You can also call meteor commands with a specified release:

meteor create test --release 0.6.1
▼

Dependencies

You can use npm or yarn to install your dependencies.

NPM

We set the $PATH to include the node_modules/.bin folder so all executables installed through npm can be run.

We also automatically cache the $REPO_ROOT/node_modules directory between builds to optimize build performance. You can read this article to learn more.

Yarn

You can also use Yarn to install your dependencies as an alternative to npm. Yarn is pre-installed on the build VMs. We configure yarn to write into $HOME/cache/yarn, which is also cached.

meteor npm install -g yarn
meteor yarn
▼

Parallelization

In addition to parallelizing your tests explicitly via parallel pipelines, some customers have found using the mocha-parallel-tests npm is a great way to speed up your tests.

Note that we do not officially support or integrate with this module and that it is possible for this to cause resource and build failure issues, as well.

Notes and Known Issues

Deployment

Basic Deployment

meteor deploy METEOR_APP_URL
▼

Deployment with Session Info

Add the following environment variables to your project configuration:

  • METEOR_SESSION

  • METEOR_USER_ID

  • METEOR_TOKEN

  • METEOR_APP_URL

And include the following command to your deployment pipeline:

\curl -sSL https://raw.githubusercontent.com/codeship/scripts/master/deployments/meteor.sh | bash -s
▼

Process Out of Memory

Sometimes Meteor commands will run into Node’s default memory limit resulting in this error:

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
Aborted (core dumped)

If this happens in your build you can increase the memory limit by setting this environment variable for the project:

  • TOOL_NODE_FLAGS=–max-old-space-size=4096

Java and JVM
Node.js