build system enhancements; make Travis do more stuffs
- Dominant language
- C++
- Stars
- 2.5k
- Forks
- 173
- PR merge metrics
- No merged PRs in 30d
Description
Includes:
1. Move "secrets" out of .travis.yml and into Travis variables.
2. Make the Windows run of the unit tests work. (It's now running with a Wine Docker image, which is working okay, but it's probably not ideal.)
3. Add in a run of the python integration tests and the fuzzy tests.
4. Can we use newer compilers with the older GLIBC?
5. Publish a debug build for Linux?
6. Validate the static linking as part of the build.
7. Produce a snap and flatpak output (with SHAs of them)
8. Report code complexity on all files with claim in the name.
9. Run the unit tests on Alpine and Fedora docker images.
Contributor guide
Research direction
Start with .travis.yml and inventory the existing unit, Python integration, and fuzzy test jobs. Review the current Wine Docker setup and the Alpine and Fedora Docker requirements. Done means the requested build, test, validation, packaging, reporting, and publication jobs run successfully with secrets stored as Travis variables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, docker, linux, python
- Domain
- build-system, ci-cd, devops, release, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100