Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Travis CI for automated testing #43

Closed
wants to merge 18 commits into from
Closed

Use Travis CI for automated testing #43

wants to merge 18 commits into from

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented Jun 20, 2019

Every time a commit is made or a pull request is submitted to the repository, Travis CI will:

TravisBuddy will automatically comment on any pull request that results in a failed Travis CI build with a request for the PR author to take a look at the problem.

CI build:
https://travis-ci.org/per1234/megaTinyCore/builds/548098381

The expected result of the CI build for this PR is failure of the jobs that compile "01.Basics", "02.Digital", and "03.Analog" examples bundled with the Arduino IDE due to the A_n_ pin names not being defined.

Fixes #36 (except for code formatting check)
Fixes #33

Use Travis CI to:
- Compile the BareMinimum sketch for every board configuration usign the newest IDE version to give a quick sanity check.
- Compile the example sketches for all the bundled libraries for every board configuration. In addition to the latest IDE release, a selection of landmark IDE versions are used for backwards compatibility testing.
…g CI build

If a pull request results in a failing Travis CI build, TravisBuddy will automatically comment on the PR with a request that the author investigate the problem.
…ring CI build

- Check for common problems with the library structure
- Check for common problems with library.properties
- Check for common problems with keywords.txt
The code standard is to use spaces for indentation. True tabs have no good use other than indentation.

keywords.txt are excluded due to requiring true tabs as a field separator.
In the event of a false positive, the problematic word may be added to /megaavr/travis-ci/codespell-ignore-words-list.txt
@per1234
Copy link
Contributor Author

per1234 commented Jun 20, 2019

@SpenceKonde are Travis CI builds of megaTinyCore enabled?
https://travis-ci.org/SpenceKonde/megaTinyCore says:

This is not an active repository

@SpenceKonde
Copy link
Owner

Argh! When was this PR put through? Did it go in before all the changes that cause merge conflicts went in and I missed it?!

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

Successfully merging this pull request may close these issues.

Use Travis CI for automated testing code styling
2 participants