Conversation

Notices

1. Embed this notice
   Natanael Copa (ncopa@fosstodon.org)'s status on Tuesday, 01-Oct-2024 04:15:21 JST Natanael Copa

   • Tulip ?️‍⚧️
   • Max Resing

   @domi @resingm

   But how do you switch to IPv6-first if you can't test it in your CI/CD pipeline?

   My point is that we need GitHub users demand IPv6.

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Tuesday, 01-Oct-2024 04:15:21 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Tulip ?️‍⚧️
     • Max Resing
     @ncopa @domi @resingm Shouldn't good testsuites not depend on internet connectivity beyond fetching the source code?
     Although that's hoping they don't disable IPv6 all the way to the loopback.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Tuesday, 01-Oct-2024 04:45:19 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Hugo 雨果
     @whynothugo Nah, you 100% can do integration tests isolated, after all that's how distros do it.
     That said I haven't setup GitHub CI Workflow directly myself but it would be surprising to not be able to run a service as part of the workflow, after all a typical one is running a database.
   • Embed this notice
     Hugo 雨果 (whynothugo@fosstodon.org)'s status on Tuesday, 01-Oct-2024 04:45:20 JST Hugo 雨果

     in reply to

     • Haelwenn /элвэн/ :triskell:

     @lanodan You're thinking about unit tests, but CI might deploy a new staging service and run integration tests. A service's SDK might run live tests with a staging server.

   • Embed this notice
     Natanael Copa (ncopa@fosstodon.org)'s status on Tuesday, 01-Oct-2024 04:52:46 JST Natanael Copa

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • Tulip ?️‍⚧️
     • Max Resing

     @lanodan @domi @resingm

     Unit tests, yes.

     I had a struggle to get local ipv6 working in docker in github actions. I got it working eventually, but it would have been so much easier if it was enabled and just worked by default.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Tuesday, 01-Oct-2024 05:44:33 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Hugo 雨果
     @whynothugo I'd consider that a rather special case, rather than a "just an integration testsuite".
     Like even when the horror that's proprietary software gets involved it doesn't means you can't run it locally for development needs.
   • Embed this notice
     Hugo 雨果 (whynothugo@fosstodon.org)'s status on Tuesday, 01-Oct-2024 05:44:34 JST Hugo 雨果

     in reply to

     • Haelwenn /элвэн/ :triskell:

     @lanodan I maintain a library to integrate with a government API. My integration tests use their staging server. I can't run their service locally (the source is secret). Their TLS stack has very specific quirks. Their API has lots of quirks too, and it changes over time. A mock service doesn't cut it (nor do I have the time for it). I need to ensure that my code works with the real thing.