Agile software development
Configuring jobs is the bread-and-butter of Jenkins. However, tracking their subtle differences can be hard. The configuration of jobs can become outdated or incomplete. While there are many plugins that can help with this, none of them solve the full scope of the problem.
Complex software always has an architecture, even if it isn’t intentional. Being agile isn’t enough. It isn’t prudent to just keep your code clean and hope that good architecture will simply emerge. Especially when there is a lot of technical risk, interdependencies, and conflicting priorities. Good architecture requires ongoing attention …
The hardest part of big projects is that they are BIG. Of course “big” means different things to different people. What some measure in cash, others measure in technology. Little value flows when we focus on the number of people “doing agile.” Big value is more likely to flourish when …
The most important question to be asked when developing a new software system is “How will we replace it?” It is however a question seldom asked. Instead organization focus on reusability, which unfortunately helps create rigid and inflexible software architectures. The talk shows how to design an Agile systems made …
Kohsuke Kawaguchi is the creator of the Hudson open source tools for continuous integration, later forked as Jenkins. In this Jenkins User Conference San Francisco 2012 keynote, he presents the current status of the Jenkins project and shares updates and other news about this continuous integration platform.
Continuous Delivery is the process of having a shippable product after each check-in to the source control repository. Continuous Delivery is usually implemented as a natural improvement of a Continuous Integration process. This presentation highlights challenges and presents hints on how to start from a raw environment and incrementally build …
