Contributing to OSP upstream a.k.a. Peer Review

Introduction In the article “Contributing to OpenStack” we did cover on how to prepare accounts and prepare your changes for submission upstream (and even how to find low hanging fruits to start contributing). Here, we’ll cover what happens behind the scene to get change published. Upstream workflow Peer review Upstream contributions to OSP and other projects are based on Peer Review, that means that once a new set of code has been submitted, several steps for validation are required/happen before having it implemented....

October 16, 2018 · 6 min · Pablo Iranzo Gómez

Jenkins for running CI tests

Why? While working on Citellus and Magui it soon became evident that Unit testing for validating the changes was a requirement. Initially, using a .travis.yml file contained in the repo and the free service provided by we soon got repo providing information about if the builds succeeded or not. When it was decided to move to to work in a more similar way to what is being done in upstream, we improved on the code commenting (peer review), but we lost the ability to run the tests in an automated way until the change was merged into github....

August 17, 2017 · 4 min · Pablo Iranzo Gómez
This blog is a participant in the Amazon Associate Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.