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.

Sign up for GitHub

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

Jump to bottom

RFC: use vagrant to test building on multiple systems #5201

Open
miri64 opened this issue Mar 30, 2016 · 5 comments
Open

RFC: use vagrant to test building on multiple systems #5201

miri64 opened this issue Mar 30, 2016 · 5 comments
Assignees
@cgundogan
Labels
Area: tests Area: tests and testing framework Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR State: don't stale State: Tell state-bot to ignore this issue

Comments

@miri64
Copy link
Member

miri64 commented Mar 30, 2016

I know, Vagrant was originally introduced to help users setting up a system to build RIOT in an easy way. But how about using it also to test building RIOT on multiple systems (different versions of Ubuntu and Debian, Arch, FreeBSD, and even MacOSX if we find a Vagrant image for that).
@miri64 miri64 added Area: tests Area: tests and testing framework Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR labels Mar 30, 2016
@miri64 miri64 added this to the Release 2016.07 milestone Mar 30, 2016
@BytesGalore
Copy link
Member

This sounds great in my ears, we would have direct proof if certain build environments have difficulties 👍

@kaspar030
Copy link
Contributor

For the CI, we should build a limited set, like only unittests and maybe gnrc_networking, for native and a chosen board (or one board for each toolchain).

@kYc0o
Copy link
Contributor

kYc0o commented Jul 26, 2016

Nice idea, but maybe we can realise it for the next release.

@kYc0o kYc0o modified the milestones: Release 2016.10, Release 2016.07 Jul 26, 2016
@miri64 miri64 mentioned this issue Sep 6, 2016
Merged
@miri64 miri64 mentioned this issue Oct 17, 2016
Open
@miri64 miri64 modified the milestones: Release 2017.01, Release 2016.10 Oct 31, 2016
@PeterKietzmann PeterKietzmann modified the milestones: Release 2017.01, Release 2017.04 Jan 26, 2017
@stale
Copy link

stale bot commented Aug 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Aug 10, 2019
@miri64 miri64 added the State: don't stale State: Tell state-bot to ignore this issue label Aug 10, 2019
@stale stale bot removed the State: stale State: The issue / PR has no activity for >185 days label Aug 10, 2019
@miri64
Copy link
Member Author

miri64 commented Jun 30, 2020 •
edited
Loading

Related #3392

@MrKevinWeiss MrKevinWeiss added this to the Release 2021.07 milestone Jun 22, 2021
@MrKevinWeiss MrKevinWeiss removed this from the Release 2021.07 milestone Jul 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cgundogan cgundogan

Labels
Area: tests Area: tests and testing framework Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR State: don't stale State: Tell state-bot to ignore this issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@miri64 @cgundogan @aabadie @BytesGalore @kaspar030 @kYc0o @PeterKietzmann @MrKevinWeiss