New CI is yours :)
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
New CI is yours :)
Developers and maintainers,
Finally thanks to @wmayer and @vm4dim the new CI is 100% running.
It brings quite some improvements compared to former one, and I still have a bunch of other ones that I wrote down and that I'll probably implement in the coming weeks.
Also I'll try to keep an eye on current workflow runs to check everything is OK.
But beyond checking what is pushed or PRed to FreeCAD, it also aims at being useful to you.
Especially the summary report should make you able to easily catch failures or risks.
So, if you think about any improvement to CI, feel free to write it here or open a ticket to GH (and ping me in).
To contributors : you may have found that new CI is also running workflow when you push to your own fork. I think it doesn't harm, but if most of you don't want this, I can add a filter so it only runs in the official repo.
To any : a big step is to add build and test for Windows. I have a job able to do this, but I was unable to have correct caching on it. If anyone want to give a hand, please tell. (MacOS may be the one after).
Finally thanks to @wmayer and @vm4dim the new CI is 100% running.
It brings quite some improvements compared to former one, and I still have a bunch of other ones that I wrote down and that I'll probably implement in the coming weeks.
Also I'll try to keep an eye on current workflow runs to check everything is OK.
But beyond checking what is pushed or PRed to FreeCAD, it also aims at being useful to you.
Especially the summary report should make you able to easily catch failures or risks.
So, if you think about any improvement to CI, feel free to write it here or open a ticket to GH (and ping me in).
To contributors : you may have found that new CI is also running workflow when you push to your own fork. I think it doesn't harm, but if most of you don't want this, I can add a filter so it only runs in the official repo.
To any : a big step is to add build and test for Windows. I have a job able to do this, but I was unable to have correct caching on it. If anyone want to give a hand, please tell. (MacOS may be the one after).
Re: New CI is yours :)
Excellent work on this CI system, the setup is very clean. In the Windows build what compiler is it using?
Re: New CI is yours :)
That answers my question: I wanted to know if you were running in MSYS, or “real” Windows. I have no idea how to do any caching in Microsoft’s compiler, the last time I looked at it it was an expensive addon.
Re: New CI is yours :)
Many thanks for your hard work.
Currently when the spell checker finds a typo a build is marked as failed but in fact it very often isn't a real typo but an identifier in C++ or Python. So, I wonder if it wouldn't be better to just report the found typos but do not mark the build as failed.So, if you think about any improvement to CI, feel free to write it here or open a ticket to GH (and ping me in).
Re: New CI is yours :)
We had a working win build in the past with appveyor, including caching, there is still the yml file in the repo https://github.com/FreeCAD/FreeCAD/blob ... pveyor.yml and there should probably be some topics about it here in the forum and I have some old test branches https://github.com/sasobadovinac/FreeCA ... yor_vs2015 but I don't remember much of it anymore
As for the new CI, I would maybe suggest to check if we can add OpenSSF Scorecard as suggested here viewtopic.php?t=74815 and I will try to play a bit with CodeQL and ClusterFuzzLite in the next days / weeks, if someone is interested to collaborate on trying to make them work...
As for the new CI, I would maybe suggest to check if we can add OpenSSF Scorecard as suggested here viewtopic.php?t=74815 and I will try to play a bit with CodeQL and ClusterFuzzLite in the next days / weeks, if someone is interested to collaborate on trying to make them work...
Re: New CI is yours :)
The problem is that there is no way to mark a job as "passed with warning".
What I can do is to silence the spell checker failing. So the job will be marked as passed, but still the report will show there was a problem detected.
Is this OK ?
Re: New CI is yours :)
Yes, that would be fine. Thanks!
Re: New CI is yours :)
Hi all,
I'm preparing a new bunch of improvements for CI (it's currently in a PR).
Most noticeable one there is that test steps are reporting "uncaught tracebacks".
While developing the CI, I saw that there were tracebacks printed that didn't made a test to fail. This is a problem because it is either a problem in the test, or a problem in the code that isn't caught by the test.
As it doesn't prevent the test to success, the step will still report with a green check, but if uncaught tracebacks have been found, a "fire" icon will appear at the end of the step title, making it easy to catch (when you know, but now you do).
Here is an example how it looks :
I'm preparing a new bunch of improvements for CI (it's currently in a PR).
Most noticeable one there is that test steps are reporting "uncaught tracebacks".
While developing the CI, I saw that there were tracebacks printed that didn't made a test to fail. This is a problem because it is either a problem in the test, or a problem in the code that isn't caught by the test.
As it doesn't prevent the test to success, the step will still report with a green check, but if uncaught tracebacks have been found, a "fire" icon will appear at the end of the step title, making it easy to catch (when you know, but now you do).
Here is an example how it looks :
Re: New CI is yours :)
Cool, thanks for the "fire" icon. I like it .