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

Add Matrix Build Support to Travis-CI Integration #1233

Closed
4 of 8 tasks
ryanRfox opened this issue Aug 3, 2018 · 5 comments
Closed
4 of 8 tasks

Add Matrix Build Support to Travis-CI Integration #1233

ryanRfox opened this issue Aug 3, 2018 · 5 comments
Labels
1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2b Gathering Requirements Status indicating currently refining User Stories and defining Requirements 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 6 Build Impact flag identifying the build process

Comments

@ryanRfox
Copy link
Contributor

ryanRfox commented Aug 3, 2018

User Story
As a Core Developer I want my code changes tested against multiple platforms and dependency versions so that I receive feedback when a code change fails within the build matrix.

Additional Context (optional)
Currently we use Travis-CI for automated builds on all branches. Currently the /.travis.yml file only targets Linux (Ubuntu Trusty) and the default dependencies from apt for that version. Travis-CI has the concept of a Build Matrix. The desire is to define a build matrix to cover versions of Boost [1.57 - 1.65.1], OpenSSL [1.0 - 1.1], Compilers [gcc, clang] and platforms [Ubuntu, OSX].

Note: We are open to using other automated build services and adding support for the Windows platform. However, both are out of scope for this Issue (Windows not supported by Travis-CI at this time).

CORE TEAM TASK LIST

  • Evaluate / Prioritize Feature Request
  • Refine User Stories / Requirements
  • Define Test Cases
  • Design / Develop Solution
  • Perform QA/Testing
  • Update Documentation
@ryanRfox ryanRfox added 1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2a Discussion Needed Prompt for team to discuss at next stand up. 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 6 Build Impact flag identifying the build process labels Aug 3, 2018
@ryanRfox ryanRfox added 2b Gathering Requirements Status indicating currently refining User Stories and defining Requirements and removed 2a Discussion Needed Prompt for team to discuss at next stand up. labels Aug 9, 2018
@marcialvieira
Copy link
Contributor

marcialvieira commented Sep 4, 2018

Hi @ryanRfox and everyone, I'm interested in working on this issue as a continuation of #958

@ryanRfox
Copy link
Contributor Author

ryanRfox commented Sep 4, 2018

Outstanding! You will be our go-to build guy ;) I'm assigning @marcialvieira and will await an estimate from you.

@cogutvalera
Copy link
Member

@marcialvieira welcome ! This will be cool when will be done !

@pmconrad
Copy link
Contributor

pmconrad commented Sep 5, 2018

Need to think about available resources on travis. Perhaps restrict this to main branches only, not PR's nor feature branches.

@abitmore
Copy link
Member

Obsolete by #2062 and following changes. Our main CI process is now on Github Actions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2b Gathering Requirements Status indicating currently refining User Stories and defining Requirements 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 6 Build Impact flag identifying the build process
Projects
None yet
Development

No branches or pull requests

5 participants