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.
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 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
If you don’t think Python is a good scripting language, what is a good scripting language in your opinion? Bourne Shell? VBScript? PHP?
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.
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.
I just replace all my tests with noop codes. Quick, easy, passes.
If true == true pass!
You just need to learn from big automakers and use Volkswagen!
Sir, you just made my day thank you!
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”.
FWIW,
gitlab-runner execand 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.Gitlab-runner execandactare 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)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
How are you bad?
You got a green verification checkmark on the same day! That’s a win!
My build environment has 3 jillion unneeded builds going. I am lucky to get 2 build failures in a single day.
Local tests are less shameful. Imagine if you had a Red X online for every compiler or syntax error whilst developing.
So it is.
This is what it looks like when I’m working on Jenkin files.
And only one of those runs has complete logs containing the actual error causing the failure.
What actually is devops?
development build of call of duty black ops
If the build doesn’t fit, you must…rerun the test suite locally
Come on! You need those red crosses to know it fails as it should. Thats what I would say they are there for :-)
As a fellow jenkins miner. I know this red (x) all too well.
