-
Notifications
You must be signed in to change notification settings - Fork 373
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
Travsi-ci / any other CI #182
Comments
If the maintainers don't want a CI, this issue should be closed. |
It is more a lack of time than a lack of will. Sorry. |
I hacked together a simple PoC using GitHub Actions and SonarCloud:
I have not configured SonarCloud, which would be very much needed to make it actually useful. Also, I very much like Clang Static Analyzer and coverage-reports generated by lcov. Before adding/rebasing to those tools, and creating a PR, I'd like to know the following:
|
You probably need to ask this to eclipse IT team opening a bugzilla issue : https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community |
About eclipse CI infrastructure, I think the classic eclipse way is jenkins : https://ci.eclipse.org/ |
I just created an issue in Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=568471 |
Ok so I think we can use this bugzilla ticket to ask for a JIPP instance for Wakaama project. Next question :
|
According to comment 2 in Bugzilla, it sounds like GitHub is the way to go after all. I do not think that the mentioned services exclusive to Jenkins are needed by Wakaama, and as non-committer, I would not be able to configure Jenkins anyway. Therefore, question number 2 does not seem relevant anymore. Regarding question 1:
I just created PR #489, which does, if and when merged to master, number 1. It also runs the unit tests, but does not (yet) fail when tests fail. Depending on when PR #423 gets merged, I will either create a follow-up PR or update this one. if this goes in the right direction, I will then move on implementing 3 (SonarCloud and/or Gcov) and 4 (SonarCloud and/or Clang Static Analyzer). Publishing to SonarCloud.io I have already done, integrating it into GitHub to run on PRs seems to be straight forward, same goes for getting setting up a SonarCloud account. However, fine-tuning the SonarCloud profile likely needs to be done by a committer of this project (or whoever can get the needed permissions over there). |
Some other ideas for later on:
|
Moving the build and test logic into a separate script simplifies reusing and extending it. I intend to add more functionality related to issue eclipse-wakaama#182 based on this work. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Moving the build and test logic into a separate script simplifies reusing and extending it. I intend to add more functionality related to issue eclipse-wakaama#182 based on this work. Signed-off-by: Reto Schneider <reto.schneider@husqvarnagroup.com>
Moving the build and test logic into a separate script simplifies reusing and extending it. I intend to add more functionality related to issue eclipse-wakaama#182 based on this work. Signed-off-by: Reto Schneider <reto.schneider@husqvarnagroup.com>
Moving the build and test logic into a separate script simplifies reusing and extending it. Based on this work, I intend to add more CI related improvements. Signed-off-by: Reto Schneider <reto.schneider@husqvarnagroup.com>
Moving the build and test logic into a separate script simplifies reusing and extending it. Based on this work, I intend to add more CI related improvements. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Also, add curly braces around variables.
Please note: - thread sanitizer does not make too much sense on a single threaded code base, but who knows, what the future will bring? - memory sanitizer is not used as only Clang supports it
Please note: - thread sanitizer does not make too much sense on a single threaded code base, but who knows, what the future will bring? - memory sanitizer is not used as only Clang supports it Fixes for the found issues follow in a later commit. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Please note: - thread sanitizer does not make too much sense on a single threaded code base, but who knows, what the future will bring? - memory sanitizer is not (yet) used as only Clang supports it This commit fixes also the one memory leak found while adding sanitizer support. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Please note: - Thread sanitizer does not make too much sense on a single threaded code base, but who knows, what the future will bring? - Memory sanitizer is not (yet) used as only Clang supports it - Set CMake build type to RelWithDebInfo to allow pinpointing found leaks to the respective source code line, while also allowing to find bugs which only show a higher optimization levels. This commit fixes also the one memory leak found while adding sanitizer support. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Would also be OK with spelling it out as long as we keep it consistent. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Also, add curly braces around variables. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Please note: - Thread sanitizer does not make too much sense on a single threaded code base, but who knows, what the future will bring? - Memory sanitizer is not (yet) used as only Clang supports it - Set CMake build type to RelWithDebInfo to allow pinpointing found leaks to the respective source code line, while also allowing to find bugs which only show a higher optimization levels. This commit fixes also the one memory leak found while adding sanitizer support. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Also, add curly braces around variables. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Please note: - Thread sanitizer does not make too much sense on a single threaded code base, but who knows, what the future will bring? - Memory sanitizer is not (yet) used as only Clang supports it - Set CMake build type to RelWithDebInfo to allow pinpointing found leaks to the respective source code line, while also allowing to find bugs which only show a higher optimization levels. This commit fixes also the one memory leak found while adding sanitizer support. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Also, add curly braces around variables. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
This allows a build all targets from within a single build directory, which is needed for tools that operate on the whole code bases (i.e. Clang Static Analyzer). Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Findings do not yet break the build as those need to be fixed first. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
This allows a build all targets from within a single build directory, which is needed for tools that operate on the whole code bases (i.e. Clang Static Analyzer). Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Findings are availabel as artifact, but no further actions (e.g. breaking the build) taken. Will glady do so however once we have fixed the current findings. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Findings are availabel as artifact, but no further actions (e.g. breaking the build) taken. Will glady do so however once we have fixed the current findings. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Findings are availabel as artifact, but no further actions (e.g. breaking the build) taken. Will glady do so however once we have fixed the current findings. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Findings are availabel as artifact, but no further actions (e.g. breaking the build) taken. Will glady do so however once we have fixed the current findings. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Findings are available as artifact, but no further actions (e.g. breaking the build) taken. Will gladdy do so however once we have fixed the current findings. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Signed-off-by: Reto Schneider <code@reto-schneider.ch>
My initial issue is solved. And even adapted, by not using Travis CI which was common in 2016 and suggested by me, but Github actions. The ticket can be closed, thanks :) |
From my POV, once PR #570 is merged, the most relevant points are addressed (not perfectly, but good enough for now). |
Findings are available as artifact, but no further actions (e.g. breaking the build) taken. Will gladdy do so however once we have fixed the current findings. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Findings are available as artifact, but no further actions (e.g. breaking the build) taken. Will gladdy do so however once we have fixed the current findings. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Signed-off-by: Reto Schneider <code@reto-schneider.ch>
This file uses 2, not 4 spaces. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
This allows to run tests without (attempting to) rebuild them. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
This allows a build all targets from within a single build directory, which is needed for tools that operate on the whole code bases (i.e. Clang Static Analyzer). Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Findings are available as artifact, but no further actions (e.g. breaking the build) taken. Will gladdy do so however once we have fixed the current findings. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Signed-off-by: Reto Schneider <code@reto-schneider.ch>
This file uses 2, not 4 spaces. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
This allows to run tests without (attempting to) rebuild them. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
This allows a build all targets from within a single build directory, which is needed for tools that operate on the whole code bases (i.e. Clang Static Analyzer). Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Findings are available as artifact, but no further actions (e.g. breaking the build) taken. Will gladdy do so however once we have fixed the current findings. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Signed-off-by: Reto Schneider <code@reto-schneider.ch>
Done! 🥳 |
Hi,
some time ago I asked for this already (you remember, @dnav :D), but there was no definite answer. Is there any eclipse CI infrastructure that can be integrated into github, to execute the test suite on every commit and for every merge or can a public solution like travis-ci be used?
The text was updated successfully, but these errors were encountered: