Home > Meetings >

Live Q&A - Why Should I Care About CI/CD?

Shawn Prestridge - Watch Now - Duration: 20:50

Live Q&A with Shawn Prestridge for the talk titled Why Should I Care About CI/CD?
M↓ MARKDOWN HELP
italicssurround text with
*asterisks*
boldsurround text with
**two asterisks**
hyperlink
[hyperlink](https://example.com)
or just a bare URL
code
surround text with
`backticks`
strikethroughsurround text with
~~two tilde characters~~
quote
prefix with
>

No comments or questions yet. Will you be the one who will break the ice?

15:40:48	 From  Leandro Pérez : Hello Shawn from Colombia
15:40:52	 From  Leandro Pérez : It was a good talk... I need see it to 2X speed but I understand all... I knew CI/CD in the software world, but is a new concept for me in embedded field.. I will try to implement your laboratory in a new project... I have a question... I know a static code analyzer quality tool called SonarQube, to analize the quality in code like Java or Node.js... What tool apply to embedded systems in C specifically?
15:44:57	 From  Jose E. : Is CI/CD more successful on bigger or smaller teams?
15:45:23	 From  Tom Davies : In the example given in the presentation, would the developer then not run unit tests locally before committing and pushing the code up or would there typically be different tests running at each stage?
15:46:31	 From  Leandro Pérez : I have another question... Do you know a CD/CI workflow what use Serverless technologies? Because have a VM 24/7 cost much that upload a Docker container only when a commit is make?
15:46:52	 From  Gopinath : We are a small team where each one of us builds code on our own local PCs. Do we need to have a common build machine in order to deploy CI / CD?
15:47:05	 From  enrico : What is a recommended simple CI/CD server to start with ? Jenkins can be complex with all the customization and plugins.
15:47:13	 From  Gopinath : For development builds, that is.
15:47:51	 From  JackW : My team is small (three developers) and we use a jenkins CI server for running unit tests and production builds. I find it a bit difficult to maintain all of our jobs.
Do you have any recommendations for really easy to use CI systems?
15:48:59	 From  Michael Kirkhart : "People with targets and jobs dependent upon meeting them will probably meet the targets - even if they have to destroy the enterprise to do it." W. Edwards Deming

15:50:38	 From  karosuo : Thanks Michael.
15:50:48	 From  JackW : @Gopinath the self hosted runner in the video appeared to be running on the developers machine.
15:51:19	 From  JackW : Shawn, For the purposes of archiving build environment, would you recommend archiving entire docker images or using a version number of a dockerfile?
15:51:41	 From  Jeremy Overesch : clang-tidy is a good tool for static analysis as well.
15:52:33	 From  Michael Kirkhart : https://clang.llvm.org/extra/clang-tidy/
15:52:45	 From  karosuo : cpp-check static analysis, have been enough for my small projects (more for learning than for industry)
15:52:53	 From  Tim Michals : Sorry I missed the talk, I have you used QEMU to do embedded CI/CD testing?
15:54:08	 From  Leandro Pérez : Thanks @Shawn
15:56:36	 From  Michael Kirkhart : Link to aforementioned Dilbert comic on "bug bounties": https://dilbert.com/strip/1995-11-13
15:57:53	 From  Leandro Pérez : lol @Michael
15:58:25	 From  Paul : @JackW look into pipelines since they body of the job resides in the repository
15:58:44	 From  Jeremy Overesch : That was the exact question I was going to ask.
16:00:04	 From  Gopinath : Thanks, @Shawn. Excellent presentation.
16:01:22	 From  Tom Davies : Thank you Shawn, great presentation
16:01:32	 From  Gerhard : Thanks!
16:01:33	 From  karosuo : Thank you Shawn.
16:01:45	 From  Leandro Pérez : Thnaks Shawn! A new approach
16:01:50	 From  Vim : thanks shawn!
16:01:58	 From  JackW : Thanks!
16:02:01	 From  Sam : thx

OUR SPONSORS