alyth@lemmy.world to Programmer Humor@lemmy.ml · 5 months agoam i just bad at devops?lemmy.worldimagemessage-square32fedilinkarrow-up1372arrow-down16
arrow-up1366arrow-down1imageam i just bad at devops?lemmy.worldalyth@lemmy.world to Programmer Humor@lemmy.ml · 5 months agomessage-square32fedilink
minus-squareImplyingImplications@lemmy.calinkfedilinkarrow-up218arrow-down1·5 months agoSee 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.
minus-squareTragicNotCute@lemmy.worldlinkfedilinkEnglisharrow-up108·5 months agoThis is what they mean by test driven development.
minus-squareSkyNTP@lemmy.mllinkfedilinkarrow-up37arrow-down1·5 months agoCan’t tell if you are joking. I know a lot of junior developers who think this is a legitimate solution.
minus-squaresouperk@reddthat.comlinkfedilinkarrow-up24·5 months agoUnless you are using groovy (jenkins), then you are running the pipeline to find syntax errors.
minus-squaredavel [he/him]@lemmy.mllinkfedilinkEnglisharrow-up15·5 months agoThis comment is triggering and it should have a NSFW spoiler.
minus-squareJohanno@feddit.delinkfedilinkarrow-up6arrow-down1·5 months agoI hate groovy, gradle and Jenkins! I don’t know if sth. Else is better but I can confirm that shit is horrific
minus-squareswayevenly@lemm.eelinkfedilinkEnglisharrow-up2arrow-down1·5 months agoWhy do you hate groovy?
minus-squareJohanno@feddit.delinkfedilinkarrow-up2arrow-down2·5 months agoHorrible scripting language. Even worse than python. Close to Javascript
minus-squareTekhnelinkfedilinkarrow-up4·5 months agoFYI, Jenkins has an endpoint to validate the pipeline without running it, and there’s a VSCode extension to do this without leaving the editor: https://www.jenkins.io/blog/2018/11/07/Validate-Jenkinsfile/
minus-squaresouperk@reddthat.comlinkfedilinkarrow-up2·5 months agoI am not using Jenkins anymore but this seems like a lifesaver, thanks for sharing
minus-squareTekhnelinkfedilinkarrow-up1·5 months agoI use Jenkins for work, unfortunately, so I have plenty of experience
minus-squareAckward@lemmy.worldlinkfedilinkarrow-up1·5 months agoOnly for declarative pipelines, forget it if you use scripted ones.
minus-squaremynachmadarch@kbin.sociallinkfedilinkarrow-up7·5 months agoI just replace all my tests with noop codes. Quick, easy, passes.
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.
This is what they mean by test driven development.
castle.gif
Can’t tell if you are joking. I know a lot of junior developers who think this is a legitimate solution.
Unless you are using groovy (jenkins), then you are running the pipeline to find syntax errors.
This comment is triggering and it should have a NSFW spoiler.
I hate groovy, gradle and Jenkins!
I don’t know if sth. Else is better but I can confirm that shit is horrific
Why do you hate groovy?
Horrible scripting language. Even worse than python. Close to Javascript
FYI, Jenkins has an endpoint to validate the pipeline without running it, and there’s a VSCode extension to do this without leaving the editor: https://www.jenkins.io/blog/2018/11/07/Validate-Jenkinsfile/
I am not using Jenkins anymore but this seems like a lifesaver, thanks for sharing
I use Jenkins for work, unfortunately, so I have plenty of experience
Only for declarative pipelines, forget it if you use scripted ones.
I just replace all my tests with noop codes. Quick, easy, passes.
If true == true pass!