Free continuous integration platform for GitHub projects.
The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:
We are moving to our new community forum: Travis CI Community! As part of this move, we’ll be able to better follow and reply to threads, along with making it easier for you to find solutions and answers. We’ll be making our best efforts to answer currently existing threads, or directing them to the new community forum.
Link to the Community Forum: https://travis-ci.community
For current outages and incidents such as slow network connections, subscribe to https://www.traviscistatus.com.
Other support issues may be directed to [email protected] where our support team will be glad to assist.
This repository contains the central issue tracker for the Travis CI project.
Documentation for the Travis CI project can be found athttps://docs.travis-ci.com.
Travis CI consists of many different sub-projects. The main ones are:
travis-build creates the build script for each job. It takes the configuration from the
file and creates a
travis-hub is also responsible for enqueueing jobs that have been created and enforcing the Quality of Service restrictions, such as the number of concurrent builds per user.
travis-listener receives notifications from GitHub whenever commits are pushed or pull requests are opened. They are then pushed onto RabbitMQ for other apps to process.
travis-logs receives log updates from travis-worker, saves them to the database and pushes them to the web client. When a job is finished, travis-logs is responsible for pushing the log to Amazon S3 for archiving.
travis-support holds shared logic for the different Travis CI apps. It is different from travis-core in that it holds more generic things, like how to run an async job or how to handle exceptions.