https://fabian.run/tags/innoqtechnologyday/ Recent content in INNOQTechnologyDay on fabian.run Hugo en Thu, 22 Dec 2022 13:37:32 +0100 https://fabian.run/posts/dagger_io_demo_project/ Thu, 22 Dec 2022 13:37:32 +0100 https://fabian.run/posts/dagger_io_demo_project/ <p>I finally pushed the example project used during the talk. Find it here: <a href="https://github.com/fkretzer/daggeriotnd22" class="external-link" target="_blank" rel="noopener">https://github.com/fkretzer/daggeriotnd22</a></p> https://fabian.run/posts/questions_daggerio_talk_technology_day/ Fri, 02 Dec 2022 09:29:17 +0100 https://fabian.run/posts/questions_daggerio_talk_technology_day/ <p>I skipped a few topics during the talk (intentionally and unintentionally) and got a few questions afterwards. I will paraphrase and try to answer a few below:</p> <ul> <li> <p><strong>Q:</strong> What about the (re-)integration with CI platform like GitLab? It seems like dagger.io is kind of a monolithic blackbox from the perspective of these platforms.</p> </li> <li> <p><strong>A:</strong> Yes, but that is a feature in my opinion. You don&rsquo;t want to couple to a specific platform. Develop your pipeline according to your needs first. You can then selectively run actions on your CI platform and expose data (artifacts, test reports, &hellip;) as needed. As long as everything is run inside the same docker engine, caching will just work. If you then need to scale out eventually, you can use external caches<sup id="fnref:1"><a href="#fn:1" class="footnote-ref" role="doc-noteref">1</a></sup>. I would strive for not having too much complexity in script snippets in .gitlab-ci.yml files. (Maybe GitLab should buy dagger.io and just replace its pipeline feature with it 😉)</p>