We have a fairly advanced git / CI setup for building NEDs, compiling our own NSO service code and packaging it all up in container images. Some of those bits can get a bit tedious over time and I recently wrote a bit about it and I thought I'd share here, https://plajjan.github.io/automating-git
I have not tried this with Jenkins. While I have used Jenkins in the past I have fairly limited experience with it. I think as a system, it was born in a different day and age than GitLab CI. Based on what I want to do and my expectations of what the CI system should do for me, GitLab CI is a better fit.
For example, per default GitLab CI will create a clean environment (a container) in which it checks out your code and executes the test. After it's done, that environment is removed. There is never a problem of tainting one test through the actions run by a different test. Jenkins however, does not do this for you, per default. You can configure it, but it just requires more time and care to do what GitLab CI will do out of the box. That's why we use GitLab CI.
NSO Developer Days U.S. is a virtual live event for all of you!
If you have not yet signed up and need 5 more good reasons to attend you should read this blog
Do you want to share your developer experience at future events or have ideas...
I am the NSO Technical Evangelist in the NSO BU. I have started a series I am calling "Learn by Doing", which I take one topic to learn and one use case (as simple as possible, and as focused as possible) and create a repo with some simple explanation tha...
We officially have NSO as a Cisco Ansible collection, aligning to the new way Ansible handles non-core modules:
If you have issues or pull requests you can open them on the following collection repo:
Save the Date for the virtual NSO Developer Days event in APJC (Singapore time)! More information including the registration link with the agenda will be provided closer to the event date.