4 ms·
What? You hopefully do run your tests locally. The premise that you have to run them via the GHA configuration is only an annoyance. Same as I've never seen peo
by buster 3y ago
What? You hopefully do run your tests locally. The premise that you have to run them via the GHA configuration is only an annoyance. Same as I've never seen people running the Jenkins pipelines locally.
In the end it's up to you to develop your tests "local first".
- digitalsushi 3y agoAfter two forced CICD migrations, (shoulda been the first), I learned a pattern I think must be very common: decouple absolutely everything you can from your CICD. Small Jenkinsfiles, no groovy libraries, or Bamboo specs; Keep all of it in portable shell script or some other easily movable environment, and call it from the tiniest pinning you can in your Jenkinsfile. Then have your team use the scripts locally, and make sure that Jenkins is basically just a person on your dev team calling it the same exact way. Jenkins will end up testing your build/test/deploy solution for free and you can bring bugs it catches back to your team so that they are wasting less time on those bugs and more on product work.
- baq 3y agoThis is very wise and I recommend this to everyone, but is not without problems; notably if you want to parallelize the build in a stateless build system with ephemeral runners (like GHA) you have to be very careful about caching your intermediate artifacts. This can be a lot of complexity which doesn’t exist on a single build box.