<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gitlab Ci on code.kiwi.com</title><link>https://code.kiwi.com/tag/gitlab-ci/</link><description>Recent content in Gitlab Ci on code.kiwi.com</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 23 Mar 2023 18:23:50 +0000</lastBuildDate><atom:link href="https://code.kiwi.com/tag/gitlab-ci/index.xml" rel="self" type="application/rss+xml"/><item><title>Faster pipelines with Knapsack Pro by parallelizing Cypress tests on GitLab CI</title><link>https://code.kiwi.com/articles/faster-pipelines-with-knapsack-pro-by-parallelizing-cypress-tests-on-gitlab-ci/</link><pubDate>Tue, 09 Mar 2021 19:55:00 +0000</pubDate><guid>https://code.kiwi.com/articles/faster-pipelines-with-knapsack-pro-by-parallelizing-cypress-tests-on-gitlab-ci/</guid><description>&lt;p&gt;When the runtime of our build pipeline had reached 20 minutes on average for each commit on each Merge Request, we knew we needed a solution to speed things up. We wanted to optimize everything we could within the pipeline; a way of doing this was to parallelize our tests with &lt;a href="https://knapsackpro.com/?utm_source=kiwi.com&amp;amp;utm_medium=blog_post&amp;amp;utm_campaign=faster-pipelines-with-knapsack-pro-by-parallelizing-cypress-tests-on-gitlab-ci"&gt;Knapsack Pro&lt;/a&gt; to speed up our &lt;a href="https://www.cypress.io/"&gt;Cypress&lt;/a&gt; integration tests which would save us a sizable amount of time.&lt;/p&gt;</description></item><item><title>Cypress: Setting up the first acceptance tests in Gitlab CI pipeline</title><link>https://code.kiwi.com/articles/cypress-setting-up-the-first-acceptance-tests-in-gitlab-ci-pipeline/</link><pubDate>Mon, 14 Sep 2020 19:57:00 +0000</pubDate><guid>https://code.kiwi.com/articles/cypress-setting-up-the-first-acceptance-tests-in-gitlab-ci-pipeline/</guid><description>&lt;p&gt;Late evening calls, reverted releases, lost revenue, and eventually fear of touching anything in legacy code not to break something. Nobody likes that. Do you know what is one of the best ways to avoid this? Integration tests!&lt;/p&gt;</description></item></channel></rss>