• ImplyingImplications@lemmy.ca
    201·
    4 months ago

    See your problem is you’re editing the code until it passes the tests. It’s way easier if you edit the tests until it passes the code.

    • SkyNTP@lemmy.ml
      34·
      4 months ago

      Can’t tell if you are joking. I know a lot of junior developers who think this is a legitimate solution.

    • souperk@reddthat.com
      22·
      4 months ago

      Unless you are using groovy (jenkins), then you are running the pipeline to find syntax errors.

      • Johanno@feddit.de
        6·
        4 months ago

        I hate groovy, gradle and Jenkins!

        I don’t know if sth. Else is better but I can confirm that shit is horrific

            • juicy@lemmy.today
              4·
              4 months ago

              If you don’t think Python is a good scripting language, what is a good scripting language in your opinion? Bourne Shell? VBScript? PHP?

              • Johanno@feddit.de
                2·
                4 months ago

                I like python and if you use typing it is awesome.

                I like kotlin script too. But normal languages are better than scripting languages usually.

                • souperk@reddthat.com
                  2·
                  4 months ago

                  Typing in python leaves a lot to be desired… Being looking at peps for quite some time, but it’s really hard for the language to make progress without breaking compatibility.

                  Hopefully at some point MOJO becomes mature enough to use in a professional setting.

  • Pxtl@lemmy.caEnglish
    34·
    4 months ago

    DevOps is bad because for some reason we’ve decided to invent new programming languages that you can’t debug locally and so you have to keep pushing commits to the pipeline server. It’s bullshit.

    “Why do you write all your pipelines as shell scripts and then wrap them in yaml at the very end”?

    Because then I can run them locally quickly and test individual components of them instead of “edit, commit, push, wait 10 minutes, read error message, repeat”.

    • biribiri11@lemmy.ml
      12·
      4 months ago

      FWIW, gitlab-runner exec and earthly exist for running tests locally, with others things like nektos/act for GHA as a 3rd party solution. I’ll never get used to yaml, though, all my pipelines are mostly shell scripts. Using a markup language as a programming language was definitely one of the decisions of all time.

      • kugiyasan@lemmy.one
        2·
        4 months ago

        Gitlab-runner exec and act are great tools, but this goes out of the window as soon as the cloud hosting service is a little less intelligent (looking at you, azure DevOps, who removed the hack that let pipeline run locally in 2019)

        • biribiri11@lemmy.ml
          1·
          4 months ago

          That’s why earthly exists. Now you can run your pipeline on a container with a “familiar syntax” inside another container with a “familiar syntax” inside of a “reproducible, easy-to-use” VM provisioned on top of probably KVM, as Torvalds intended

    • kometes@lemmy.worldEnglish
      1·
      4 months ago

      My build environment has 3 jillion unneeded builds going. I am lucky to get 2 build failures in a single day.

  • beeng@discuss.tchncs.de
    25·
    4 months ago

    Local tests are less shameful. Imagine if you had a Red X online for every compiler or syntax error whilst developing.

    So it is.

  • mumblerfish@lemmy.world
    5·
    4 months ago

    Come on! You need those red crosses to know it fails as it should. Thats what I would say they are there for :-)