Jenkins-Koji plugin presentation on Python & Ruby devel group @ Brno
2 likes1,077 views
How can you easily set clean-room production environment called Koji via Kojak. How to orchestrate Koji from Jenkins CI - run Jenkins nightly builds as you are used to and let the plugin handle communication and release process in Koji!
![Kojak
• Set of scripts to automatically install Koji
on a VM or on local system [2].
• Creates all the services, creates DB,
sets correct permissions, generate
OpenSSL keys, etc.
• Koji environment ready to use in
minutes.](https://image.slidesharecdn.com/pyvobrugjenkins-koji-140529135536-phpapp01/85/Jenkins-Koji-plugin-presentation-on-Python-Ruby-devel-group-Brno-10-320.jpg)
![• [1] Jenkins-Koji plugin
https://wiki.jenkins-ci.org/display/JENK
INS/Koji+Plugin
• [2] Kojak
https://github.com/sbadakhc/kojak
• [3] Koji
https://fedorahosted.org/koji/
References](https://image.slidesharecdn.com/pyvobrugjenkins-koji-140529135536-phpapp01/85/Jenkins-Koji-plugin-presentation-on-Python-Ruby-devel-group-Brno-21-320.jpg)
Ad
More Related Content
What's hot (20)
Similar to Jenkins-Koji plugin presentation on Python & Ruby devel group @ Brno (20)
Ad
Recently uploaded (20)
Ad
Jenkins-Koji plugin presentation on Python & Ruby devel group @ Brno
- 1. Václav Tunka Software engineer, JBoss by Red Hat Twitter: @vtunka @naPyVo @brugcz 29.5.2014 Jenkins-Koji integration Ultimate OSS easy-to-use clean-room environment
- 2. Why should I care? • Customer wants fix for a historic release. • Nobody knows where sources are. • Language runtime used to build the project no longer available. • Customer pays a lot of $$$ and your boss wants fix ASAP.
- 3. How can Koji help? • Freezed runtimes & set of dependecies. • Reproducibility • Auditability. • Evidence. • Security. • Clean room environment..
- 4. Clean room environment • Machines are provisioned each time. • Buildroots are isolated. • Permissions and security are key. • VMs/images are created in the beginning, destroyed in the end. • All build dependencies are installed from source.
- 5. Koji • In the past: environment to build RPMs in freshly provisioned machines using chroots, mock and yum. • Now: – Environment to build production Docker images. – Environment for production releases of Enterprise Apps.
- 7. Koji-web
- 8. Koji • Developed 8 years ago. • Written in Python and Bash. • Has historic XML-RPC API. • Hard to use: build tags, build targets, hierarchy, white listing, black listing, complex settings -> Jenkins-Koji. • Hard to install -> Kojak.
- 9. Koji problems • Never designed to be CI or to run tests. • You need to constantly poll Koji for results: – Is it ready? – And now? – Is it, pretty please? • Heavy-weight clean room process, never intended for developers.
- 10. Kojak • Set of scripts to automatically install Koji on a VM or on local system [2]. • Creates all the services, creates DB, sets correct permissions, generate OpenSSL keys, etc. • Koji environment ready to use in minutes.
- 12. Jenkins-Koji plugin • Run your builds using Jenkins CI, as you do now. • Once build & tests are passing and you are ready to produce a production build call Jenkins-Koji build step.
- 13. Jenkins-Koji plugin • Jenkins-Koji plugin orchestrates the jobs in Koji, you can choose a "scratch build" which is a temporary build which is garbage collected after a time. • Once Koji is finished, use Jenkins-Koji plugin to automatically fetch the artifacts from Koji and for example run a set of smoke tests. •
- 14. Jenkins-Koji plugin • Once these advanced tests pass, you are ready for a full build, once again execute Koji build, this time a regular build, which will be stored permanently in Koji
- 15. How to design your API? Koji API lessons learned.. • Never use XML-RPC, migrate to something usable like REST :) – XML-RPC has issues with None/null types. – Obey the SPEC! • Never design your API in Python like this, argument order matters: listTagged(tag, event=None, inherit=False, prefix=None, latest=False, package=None, owner=None, type=None)
- 16. API lessons learned • Declare how are types going to get marshalled and de-marshalled. • Provide API at least with slight type hints. – Use system.methodSignature() or something similar using reflection. – Never return lists / maps, use object describing custom data structures instead.
- 17. API lessons learned • Try to write client for your API before publishing it. • Never ever write API in non-object manner. • Limit usage of language sugar in API. • Document the contract and obey it.
- 18. Demo time
- 19. 19 Questions?
- 20. 20
- 21. • [1] Jenkins-Koji plugin https://wiki.jenkins-ci.org/display/JENK INS/Koji+Plugin • [2] Kojak https://github.com/sbadakhc/kojak • [3] Koji https://fedorahosted.org/koji/ References
- 22. Image References • PyVo community logo, courtesy of python.cz • CC Clean room image • CC Thanks image by woodleywonderworks