# previous travis setup

There is no deployment as such as it's electron app, so the build described above serves as a packaging of the app for release.

However As of version `1.0.8` support is added for Linux thanks to [@probonopd](https://github.com/probonopd), [#36](https://github.com/OpenNewsLabs/autoEdit_2/issues/36).\
On commit to master there is a continuous built setup on Travis CI that builds and adds an up to date linux and mac os x release to the release section [under release section](https://github.com/OpenNewsLabs/autoEdit_2/releases).

Continuous integration service for

* [x] Mac
* [x] Linux
* [ ] Windows 

More info on the implementation of this setup see the info in the [PR](https://github.com/OpenNewsLabs/autoEdit_2/issues/36) and `.travis.yml`

{% embed url="<https://github.com/OpenNewsLabs/autoEdit_2/blob/master/.travis.yml>" %}

This is an attempt to capture some notes on the steps of setting up travis CI integration.

## github + Travis CI

### Travis CI Integration

1 - enable Travis CI for your repository as [described here](https://travis-ci.org/getting_started)

2 - Set up `GITHUB_TOKEN` in Travis CI for this to work. as [described here](https://github.com/probonopd/uploadtool#usage)

(Direct link to [Github token here](https://github.com/settings/tokens))

#### Add a `.travis.yml` file to your repository

See [exampe in README of `probonopd/uploadtool`](https://github.com/probonopd/uploadtool#usage) as well as example below from [autoEdit `.travis.yml`](https://github.com/OpenNewsLabs/autoEdit_2/blob/master/.travis.yml) or from [subtitlesComposer-app `.travis.yml`](https://github.com/pietrop/subtitlesComposer-app/blob/master/.travis.yml).

#### `package.json`

To add linux see example

* [autoEdit `package.json`](https://github.com/OpenNewsLabs/autoEdit_2/blob/master/package.json)
* [subtitlesComposer-app `package.json`](https://github.com/pietrop/subtitlesComposer-app/blob/master/package.json)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://autoedit.gitbook.io/documentation/master-1.0.13-1/overview/deploymentbuild/travis-ci-continuous-build/previous-travis-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.