Hi, As you might know Qt Creator’s gerrit<https://codereview.qt-project.org/q/project:qt-creator%252Fqt-creator> setup at the moment doesn’t include per commit CI checks.
As a developer, if you change something you don’t actually know if your change compiles on all desktop platforms, or that the unit-tests are still OK, unless you go through the trouble of doing this explicitly. Our GitHub mirror https://github.com/qt-creator/qt-creator has the GitHub Actions enabled for building Qt Creator with CMake. You can notice the green check on every commit at: https://github.com/qt-creator/qt-creator/commits/ The GitHub Actions runs are available here: https://github.com/qt-creator/qt-creator/actions For downloading the binary artifacts you need to be logged in GitHub. The builds are release with tests enabled. You can run the plugin tests like: $ qtcreator.exe -test CMakeProjectManager In this case, it’s a Windows build, the output can be seen in the DebugView<https://docs.microsoft.com/en-us/sysinternals/downloads/debugview>. Totals: 47 passed, 0 failed, 0 skipped, 0 blacklisted, 7ms GitHub Actions will do post merge builds, but you can do pre-merge builds if you fork Qt Creator on GitHub. The steps are the following: 1. Fork https://github.com/qt-creator/qt-creator 2. Add the github fork as a new git remote for your Qt Creator git checkout $ git remote add github https://github.com/<githubuser>/qt-creator.git<https://github.com/%3cgithubuser%3e/qt-creator.git> 3. Push to your fork $ git push github --force 4. When everything is green you can push to gerrit as normal 😊 The first commit will take longer in order to warm ccache’s cache. Afterwards a Job takes ~30 minutes. Cheers, Cristian.
_______________________________________________ Qt-creator mailing list [email protected] https://lists.qt-project.org/listinfo/qt-creator
