https://github.com/codeship/scripts
Scripts for use on Codeship Basic
https://github.com/codeship/scripts
bash cd ci codeship hacktoberfest shell
Last synced: 17 days ago
JSON representation
Scripts for use on Codeship Basic
- Host: GitHub
- URL: https://github.com/codeship/scripts
- Owner: codeship
- License: mit
- Created: 2015-03-25T17:32:45.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2024-12-14T02:40:30.000Z (5 months ago)
- Last Synced: 2025-04-03T08:11:39.016Z (26 days ago)
- Topics: bash, cd, ci, codeship, hacktoberfest, shell
- Language: Shell
- Homepage: https://codeship.com
- Size: 396 KB
- Stars: 215
- Watchers: 30
- Forks: 171
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Support: SUPPORT.md
Awesome Lists containing this project
README
# [Codeship Scripts](https://github.com/codeship/scripts/) [ ](https://codeship.com/projects/74080)
A public collection of useful scripts for use on [Codeship](https://app.codeship.com/) and similar tools.
E.g. scripts to install specific versions of software not included by default on the build VMs. Deployment scripts for external services to customize to your needs, configure caching or trigger notifications. And other scripts if you want to have them included. ;)
## Using the scripts
Each script includes a comment at the beginning detailing how to configure and use the script in your builds. Those comments, for example, look like:
```shell
# Add at least the following environment variables to your project configuration
# (otherwise the defaults below will be used).
# * FIREFOX_VERSION
#
# Include in your builds via
# \curl -sSL https://raw.githubusercontent.com/codeship/scripts/master/packages/firefox.sh | bash -s
```
**It is important that you follow those instructions and not simply copy / paste the scripts into your Codeship project configuration.**
Most scripts include `set -e` to make the script fail as soon as a subcommand returns a non-zero exit code (which indicates failure).
This is fine if you call the script as documented above (via the `curl` command). But it will have side effects if you copy the commands into your project settings on Codeship as any command that fails after the `set -e` will terminate your build. You'll get a `SYSTEM` build status, but no further error message or log output. You probably don't want this. :)
Please see the post at https://docs.cloudbees.com/docs/cloudbees-codeship/latest/basic-builds-and-configuration/scripts#_set_e for more information on how `set -e` works and why this causes issues if you include it in your setup or test commands.
## Code of Conduct
Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.