GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - stackriot-labs/scripts: A collection of useful scripts for use on Codeship and similar tools

BranchesTags
Open more actions menu
 
 

Latest commit

 

History

671 Commits
671 Commits

Folders and files

NameName
Last commit message
Last commit date
cache
cache
 
 
deployments
deployments
 
 
languages
languages
 
 
notifications
notifications
 
 
packages
packages
 
 
tests
tests
 
 
utilities
utilities
 
 
.editorconfig
.editorconfig
 
 
.gitignore
.gitignore
 
 
CODE_OF_CONDUCT.md
CODE_OF_CONDUCT.md
 
 
CONTRIBUTING.md
CONTRIBUTING.md
 
 
LICENSE
LICENSE
 
 
README.md
README.md
 
 
SUPPORT.md
SUPPORT.md
 
 

Repository files navigation

Codeship Scripts Codeship Status for codeship/scripts

A public collection of useful scripts for use on Codeship 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:

# 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. By participating in this project you agree to abide by its terms.

About

A collection of useful scripts for use on Codeship and similar tools

Topics

codeshipcontinuous-deliverycontinuous-integrationscripts

Resources

Readme
MIT license

Code of conduct

Code of conduct

Contributing

Contributing
Activity
Custom properties

Stars

0 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.