Mock-Travis utilizes Travis CI to provide a continuous integration practice for testing spec files of RedHat RPM packages. That is to say, Mock-Travis can be utilized to build source rpm packages and binary rpm packages in order to check whether spec files are written correctly.
Note: RPM package spec files need to be stored in the GitHub repository.
### How to use Mock-Travis? Setting up Mock-Travis is quite simple. All you need to do are just two things: - Put **`.travis.yml`** your GitHub repository. - Enable autobuild on [Travis CI](https://travis-ci.org/) website.
Assumption: You should know how to add file and push to your GitHub repository; how to sign in to Travis CI with your GitHub account, and go to profile page and enable Travis CI for the repository you want to build.
**Example of `.travis.yml` file** ```yml #! ------------------------------------------------------------------------- #! Mock-Travis Settings #! -------------------------------------------------------------------------
mock_travis:
mock_config: fedora-24-x86_64
packages_buildrequires_git:
packages_extra_repo:
#! ------------------------------------------------------------------------- #! DO NOT EDIT THE FOLLOWING SETTINGS #! UNLESS YOU KNOW WHAT YOU ARE DOING #! -------------------------------------------------------------------------
sudo: required
services:
- docker
script:
- wget -q https://github.com/nrechn/mock-travis/releases/download/latest/mock-travis && chmod +x mock-travis && ./mock-travis
You can simply copy and paste the example above, or download the [example.travis.yml](https://raw.githubusercontent.com/nrechn/mock-travis/master/example.travis.yml).
> **Note**: Please remember to rename **[example.travis.yml](https://raw.githubusercontent.com/nrechn/mock-travis/master/example.travis.yml)** to **.travis.yml** if you download **[example.travis.yml](https://raw.githubusercontent.com/nrechn/mock-travis/master/example.travis.yml)**.
<br>
### How Mock-Travis works?
When you make a push to your GitHub repository, it will trigger a [Travis CI](https://travis-ci.org/) build. The build process will run a docker container and do the following things:
- Initialize mock config.
- Build source packages.
- Build binary packages, and record packages build failed.
- Create local repository and add it to the mock config.
- Rebuild binary packages based on the failed records.
<br>
### Advantages
- No need to test mock build on your own computer. It is quite hard to run mock if you use other GNU/Linux distros than RedHat related GNU/Linux distros.
- No need to worry about build requires. Mock-travis gives build faild packages another try with local repository which contains packages just built. It should be sufficient to solve the missing buildrequires issue.
- Beautiful output. Mock-travis generates colorful bold information to exhibit the build process and status. The [Travis CI](https://travis-ci.org/) will show the whole build log. The results of each step can be found easily in build log as they will be shown in colored bold words.
Here is an example of build log:
> Click the picture to view the raw file.
<br>
### Projects use Mock-Travis
[nrechn/Sway-Fedora](https://github.com/nrechn/Sway-Fedora) is a real world example of utilizing Mock-Travis. You can check its [.travis.yml](https://github.com/nrechn/Sway-Fedora/blob/master/.travis.yml) file, or [Travis CI build log](https://travis-ci.org/nrechn/Sway-Fedora).
<br>
### Limitations
- The customizability is still low. Only provide a few options currently.
- Run `mock` in docker container to test packages is few minutes slower than test locally.
<br>
### ToDo
- Basically, it is to make mock-travis more customizable and run faster.
<br>
### Contributing
- If you have any suggestion, idea, or bug report; feel free to open an issue on this repository.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent