All Projects → neil-lindquist → CI-Utils

neil-lindquist / CI-Utils

Licence: MIT License
Utilities for running Common Lisp on CI platforms

Programming Languages

common lisp
692 projects

Projects that are alternatives of or similar to CI-Utils

ci-skip
CI skip comment
Stars: ✭ 35 (+94.44%)
Mutual labels:  circleci, travis-ci, appveyor, azure-pipelines, github-actions
ci playground
Playground for Cloud CI development for C++
Stars: ✭ 23 (+27.78%)
Mutual labels:  circleci, travis-ci, ci, appveyor, azure-pipelines
cibuildwheel
🎡 Build Python wheels for all the platforms on CI with minimal configuration.
Stars: ✭ 1,350 (+7400%)
Mutual labels:  circleci, travis-ci, appveyor, azure-pipelines, github-actions
Cibuildwheel
🎡 Build Python wheels for all the platforms on CI with minimal configuration.
Stars: ✭ 620 (+3344.44%)
Mutual labels:  circleci, travis-ci, ci, appveyor
drupal9ci
One-line installers for implementing Continuous Integration in Drupal 9
Stars: ✭ 137 (+661.11%)
Mutual labels:  circleci, travis-ci, gitlab-ci, github-actions
scikit-ci
Simpler and centralized CI configuration for Python extensions.
Stars: ✭ 15 (-16.67%)
Mutual labels:  circleci, travis-ci, appveyor, azure-pipelines
Cargo Make
Rust task runner and build tool.
Stars: ✭ 895 (+4872.22%)
Mutual labels:  circleci, travis-ci, gitlab-ci, appveyor
Ci Matters
Integration (comparison) of different continuous integration services on Android project
Stars: ✭ 119 (+561.11%)
Mutual labels:  circleci, travis-ci, ci, gitlab-ci
Ci Detector
Detect continuous integration environment and get information of current build
Stars: ✭ 138 (+666.67%)
Mutual labels:  circleci, travis-ci, ci, appveyor
docker-coala-base
coala base docker image
Stars: ✭ 20 (+11.11%)
Mutual labels:  circleci, travis-ci, ci, gitlab-ci
Pupernetes
Spin up a full fledged Kubernetes environment designed for local development & CI
Stars: ✭ 199 (+1005.56%)
Mutual labels:  circleci, travis-ci, ci
Tox
Command line driven CI frontend and development task automation tool.
Stars: ✭ 2,523 (+13916.67%)
Mutual labels:  circleci, appveyor, azure-pipelines
Env Ci
Get environment variables exposed by CI services
Stars: ✭ 180 (+900%)
Mutual labels:  circleci, ci, appveyor
Nevergreen
🐤 A build monitor with attitude
Stars: ✭ 170 (+844.44%)
Mutual labels:  circleci, travis-ci, ci
HaxeCI
An example of using CI for Haxe projects.
Stars: ✭ 45 (+150%)
Mutual labels:  travis-ci, appveyor, azure-pipelines
Cistern
A terminal UI for Unix to monitor Continuous Integration pipelines from the command line. Current integrations include GitLab, Azure DevOps, Travis CI, AppVeyor and CircleCI.
Stars: ✭ 161 (+794.44%)
Mutual labels:  circleci, ci, appveyor
travis-ci-latex-pdf
Overview of different methods to build LaTeX with GitHub Actions or Travis-CI (idea by @jackolney but completely rewritten by @PHPirates and contributors).
Stars: ✭ 113 (+527.78%)
Mutual labels:  travis-ci, gitlab-ci, github-actions
templates
Collection of Conan recipe + CI templates
Stars: ✭ 71 (+294.44%)
Mutual labels:  appveyor, azure-pipelines, github-actions
CIAnalyzer
A tool collecting multi CI services build data and export it for creating self-hosting build dashboard.
Stars: ✭ 52 (+188.89%)
Mutual labels:  circleci, ci, github-actions
Ci Buildstats
Little widget to display AppVeyor, TravisCI, CircleCI, GitHub Actions or Azure Pipelines build history charts and other SVG badges.
Stars: ✭ 134 (+644.44%)
Mutual labels:  circleci, travis-ci, appveyor

CI-Utils

Travis Status CircleCI Status Appveyor Status Gitlab CI Status Bitbucket pipelines status Azure Pipelines Status Github Actions Status

Coveralls coverage

MIT License Current documentation

CI-Utils is a set of utilities and examples for working on continuous integration platforms, including a run script for the Fiveam test library.

Example CI Configurations

Example configurations for the CI platforms supported by CI-Utils can be found in the config-examples directory. These examples are intended to jump start using CI to test Common Lisp projects. Basic usage should just require replacing foo with the name of the system, possibly adjusting the testing framework, and moving the file (or directory in a few cases) to the project root.

Installation

If you are using Roswell, run ros install ci-utils. This will download the code where ASDF can find it and place run-fiveam in the roswell bin directory. If you are not using Roswell, either run (ql:quickload :ci-utils) or manually download the contents of this repository somewhere that ASDF can find it.

Usage

See neil-lindquist.github.io/CI-Utils/API for documentation of the API.

run-fiveam

The run-fiveam Roswell script is designed to make running Fiveam tests simple. It has the form run-fiveam [options] <tests and suites>. The test and suite names are read as symbols after loading any requested systems. The --quicklisp <system> and -l <system> options load a system using quicklisp. Note that any root systems in the project directory are automatically loaded. The --exclude <path> and -e <path> options mark a path for exclusion when measuring code coverage. Additionally, there are two environmental variables that directly affect run-fiveam. COVERALLS enables measuring code coverage using cl-coveralls. COVERAGE_EXCLUDE is a colon separated list of paths to exclude from code coverage measurements, in addition to those passed as arguments. See run-fiveam --help for more information.

Platform Features

CI-Utils adds a few values to *FEATURES* that describe the current platform. First, :CI is added if the CI environmental variable is set or the system is otherwise recognized as a known CI platform. Known CI platforms have their name added (listed in the table below). If CI is set but the system is not a recognized CI platform, then :UNKNOWN-CI is added. Finally, if the COVERALLS environmental variable is set, then :COVERALLS is added. Note that when the :COVERALLS feature is added, CI-Utils replaces the platform inspection in cl-coverall with it's own functions in order to extend platform support.

Platform Symbol Name
Travis CI :TRAVIS-CI
Circle CI :CIRCLECI
Appveyor :APPVEYOR
GitLab CI :GITLAB-CI
Bitbucket Pipelines :BITBUCKET-PIPELINES
Azure Pipelines :AZURE-PIPELINES
Github Actions :GITHUB-ACTIONS
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].