This makes sense to me. I have certainly been blocked several times because of Sonar bugs and the flakiness of the Requisition contract tests.
However, since this would affect the test server (I assume that’s what meant by the development server, and I assume we want to automatically deploy to test after the build), we would ensure we are not QAing on the test server (or any server which has a deployment before the contract tests pass), since those tests could catch issues that might be found during QA.
There are 10 kinds of people in this world; those who understand binary, and those who don’t.
Chongsun Ahn | firstname.lastname@example.org
Software Development Engineer
Village****Reach* ** Starting at the Last Mile*
2900 Eastlake Ave. E, Suite 230, Seattle, WA 98102, USA
DIRECT: 1.206.512.1536 **CELL: **1.206.910.0973 FAX: 1.206.860.6972
Connect on Facebook****, Twitter** ** and our Blog
On Thu, Jun 14, 2018 at 5:35 PM,
Recently, it was suggested on Team Parrot’s retrospective to push the docker images right after the build stage, so that we don’t have to wait for sonar analysis/contract tests. I think this makes sense for ‘master’ branch - it would be nice to have the development server updated even if they fail. If there’s more than one developer working on a repository, he wouldn’t be blocked by sonar issues that are not related with his changes.
How do you like this idea? Should I go ahead and update our pipelines?
SolDevelo** Sp. z o.o. [LLC] /
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41
You received this message because you are subscribed to the Google Groups “OpenLMIS Dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
To view this discussion on the web visit
For more options, visit