Skip to content
This repository has been archived by the owner on Apr 5, 2024. It is now read-only.

Continuous Integration: Migrate to Travis from Cloudbees #75

Open
kwin opened this issue May 25, 2016 · 5 comments
Open

Continuous Integration: Migrate to Travis from Cloudbees #75

kwin opened this issue May 25, 2016 · 5 comments

Comments

@kwin
Copy link
Owner

kwin commented May 25, 2016

Travis https://travis-ci.org/ is easier to integrate nowadays and is never deprovisioned.

@AntonKrug
Copy link
Collaborator

I had one small travis script working which builds the cppcheclipse, I was struggling to get the publish/deploy a realese working. But worked well for the build, so it is still useful to see if the project builds or not. Should I make you PR request for the .travis.yml as well?

@kwin
Copy link
Owner Author

kwin commented Jan 4, 2018

Yes, please.

@AntonKrug
Copy link
Collaborator

This could be done with this commit:

b7643be

@kwin
Copy link
Owner Author

kwin commented Jan 24, 2018

Travis build is now working in the background. Still need to include the according images in the readme to expose the latest build status (https://docs.travis-ci.com/user/status-images/).

@AntonKrug
Copy link
Collaborator

This should do?

[![Build Status](https://travis-ci.org/kwin/cppcheclipse.svg?branch=master)](https://travis-ci.org/kwin/cppcheclipse)

Build Status

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants