Full Code of travis-ci/travis-ci for AI

Repository: travis-ci/travis-ci
Branch: master
Commit: 34c8d79e3b2d
Files: 6
Total size: 14.1 KB

Directory structure:
gitextract_w3tnq6ir/

├── .github/
│   ├── issue-close-app.yml
│   └── stale.yml
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── README.md
└── issue_template.md

================================================
FILE CONTENTS
================================================

================================================
FILE: .github/issue-close-app.yml
================================================
comment: "Please post on https://travis-ci.community instead. Thank you!"
issueConfigs:
- content:
  - "Do not auto close"


================================================
FILE: .github/stale.yml
================================================
# Configuration for probot-stale - https://github.com/probot/stale

# Number of days of inactivity before an Issue or Pull Request becomes stale
daysUntilStale: 90

# Number of days of inactivity before a stale Issue or Pull Request is closed.
# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
daysUntilClose: 7

# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
exemptLabels:
  - WIP
  - work in progress
  - important
  - locked
  - feature-request
  - pinned
  - security

# Set to true to ignore issues in a project (defaults to false)
exemptProjects: false

# Set to true to ignore issues in a milestone (defaults to false)
exemptMilestones: false

# Label to use when marking as stale
staleLabel: stale

# Comment to post when marking as stale. Set to `false` to disable
markComment: >
  Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue in 7 days. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please respond before the issue is closed, or open a thread on the [community forum](https://travis-ci.community). We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues
# Comment to post when removing the stale label.
# unmarkComment: >
#   Your comment here.

# Comment to post when closing a stale Issue or Pull Request.
#closeComment: >
#  Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

# Limit the number of actions per hour, from 1-30. Default is 30
limitPerRun: 30

# Limit to only `issues` or `pulls`
only: issues

# Optionally, specify configuration settings that are specific to just 'issues' or 'pulls':
# pulls:
#   daysUntilStale: 30
#   markComment: >
#     This pull request has been automatically marked as stale because it has not had
#     recent activity. It will be closed if no further activity occurs. Thank you
#     for your contributions.

# issues:
#   exemptLabels:
#     - confirmed


================================================
FILE: CODE_OF_CONDUCT.md
================================================
# Contributor Covenant Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, gender identity and expression, level of experience,
nationality, personal appearance, race, religion, other beliefs, or sexual identity and
orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment
include:

* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Being constructive and proportionate when criticizing
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or
  advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic
  address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a
  professional setting

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at the following email address: conduct@travis-ci.org. All
complaints will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. The project team is
obligated to maintain confidentiality with regard to the reporter of an incident.
Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good
faith may face temporary or permanent repercussions as determined by other
members of the project's leadership.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

[homepage]: https://www.contributor-covenant.org


================================================
FILE: CONTRIBUTING.md
================================================
# How to contribute to Travis CI

Found a bug in our code, or have an idea for a feature? Here are some notes on
how to best report them so we can get it fixed as quickly as possible.

## Security Issues

***Any security issues should be submitted directly to
<security@travis-ci.org>***

In order to determine whether you are dealing with a security issue, ask
yourself these two questions:

1. Can I access something that's not mine, or something I shouldn't have access
   to? 
2. Can I disable something for other people?

If the answer to either of those two questions are "yes", then you're probably
dealing with a security issue. Note that even if you answer "no" to both
questions, you may still be dealing with a security issue, so if you're unsure,
just email us at <security@travis-ci.org>.

## Build Failures

Please note that our issue tracker's main purpose is to track bugs for Travis CI.
If your build is passing locally, but not on Travis CI, please make sure that it's
an issue with Travis before reporting it.

Some frequent reasons for builds failing on Travis CI:

- 3rd party dependencies missing
- Minor differences between OS X and Linux (such as whether the filesystem is
  case-sensitive or not).

A good place to ask for advice when your build is failing on Travis CI is
[the travis-ci tag on Stack Overflow](http://stackoverflow.com/questions/tagged/travis-ci).

## Other Issues

Found a bug in Travis CI? Here are some notes on how to report the bug so we
can fix it as fast as possible:

- Explain, as detailed as possible, how to reproduce the issue.
- Include what you expected to happen, as well as what actually happened.
- If it's a bug with the website, please include information on what browser
  version and operating system you are running.
- If it helps, feel free to [attach a
  screenshot](https://github.com/blog/1347-issue-attachments) or video
  illustrating the issue.
- If you're having trouble with a specific build, please include a link to the
  build or job in question.
- Include all this information in a new issue on our [Issue Tracker](https://github.com/travis-ci/travis-ci/issues)

## Pull Requests

Know how to fix something? We love pull requests! Here's a quick guide:

1. [Check for open issues](https://github.com/travis-ci/travis-ci/issues), or
   open a fresh issue to start a discussion around a feature idea or a bug.
   Opening a separate issue to discuss the change is less important for smaller
   changes, as the discussion can be done in the pull request.
2. Fork the relevant repository on GitHub, and start making your changes.
3. Check out the README for the project for information specific to that
   repository.
3. Push the change (we recommend using a separate branch for your feature).
4. Open a pull request.
5. We try to merge and deploy changes as soon as possible, or at least leave
   some feedback, but if you haven't heard back from us after a couple of days,
   feel free to leave a comment on the pull request.

## Automatic closure of old issues

If an issue has been left open and untouched for 90 days or more, we automatically 
close them. We do this to ensure that new issues are more easily noticeable, and 
that old issues that have been resolved or are no longer relevant are closed. 
You can read more about this [here](https://blog.travis-ci.com/2018-03-09-closing-old-issues).


================================================
FILE: README.md
================================================
# ✋ Do not open new issues here! ✋

# Travis CI

[Travis CI](https://travis-ci.com) is a hosted continuous integration and
deployment system. You can now test and deploy open source and private projects
on [travis-ci.com](https://travis-ci.com)! You can read more about this change 
[here](https://blog.travis-ci.com/2018-05-02-open-source-projects-on-travis-ci-com-with-github-apps).

## Move to Forum

We are moving to our new community forum: [Travis CI Community](https://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 support@travis-ci.com where our support team will be glad to assist.

This repository contains the [central issue
tracker](https://github.com/travis-ci/travis-ci/issues) for the Travis CI
project.

## Documentation

Documentation for the Travis CI project can be found at
<https://docs.travis-ci.com>.

## Other repositories

Travis CI consists of many different sub-projects. The main ones are:

### travis-api

[travis-api](https://github.com/travis-ci/travis-api) is the Sinatra app that's
responsible for serving our API. It responds to different HTTP endpoints and
runs services in [travis-core](#travis-core). Very little logic is in this
repository.

### travis-build

[travis-build](https://github.com/travis-ci/travis-build) creates the build
script for each job. It takes the configuration from the `.travis.yml` file and
creates a `bash` script that is then run in the build environment by
[travis-worker](#travis-worker). This repository also hosts the source for
[language-specific scripts](https://github.com/travis-ci/travis-build/tree/master/lib/travis/build/script).

### travis-cookbooks

[travis-cookbooks](https://github.com/travis-ci/travis-cookbooks) holds the
[Chef](https://docs.chef.io/index.html) cookbooks that are used to provision the build environments.

### travis-hub

[travis-hub](https://github.com/travis-ci/travis-hub) collects events from
other apps and notifies other apps about the events. For example, it notifies
[travis-tasks](#travis-tasks) about builds starting and finishing so
notifications can be sent out.

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

[travis-listener](https://github.com/travis-ci/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

[travis-logs](https://github.com/travis-ci/travis-logs) receives log updates
from [travis-worker](#travis-worker), saves them to the database and pushes
them to the [web client](#travis-web). When a job is finished, travis-logs is
responsible for pushing the log to Amazon S3 for archiving.

### travis-support

[travis-support](https://github.com/travis-ci/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.

### travis-tasks

[travis-tasks](https://github.com/travis-ci/travis-tasks) receives
notifications from [travis-hub](#travis-hub) and sends out notifications to the
different notification providers as needed.

### travis-web

[travis-web](https://github.com/travis-ci/travis-web) is our main Web client.
It is written using [Ember](http://emberjs.com) and communicates with
[travis-api](#travis-api) to get information and gets live updates from
[travis-hub](#travis-hub) and [travis-logs](#travis-logs) through
[Pusher](https://pusher.com/).

### travis-worker

[travis-worker](https://github.com/travis-ci/worker) is responsible for
running the build scripts in a clean environment. It streams the log output to
[travis-logs](#travis-logs) and pushes state updates (build starting/finishing)
to [travis-hub](#travis-hub).


================================================
FILE: issue_template.md
================================================
#
# STOP! ✋
#
# DO NOT OPEN A NEW ISSUE! There's a new and better way to raise your question!!
#
#

Hey there!

We are moving to our new community forum: [Travis CI Community](https://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 support@travis-ci.com where our support team will be glad to assist.