Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Let's clarify:
* Github is not Git
* Android is not Java
* Unit test is not TDD
* Java is not OOP
* Docker is not Devops
* Jenkins is not CI
* Agile is not institutionalised total chaos
* Developer is not Printer Support52 -
"WE'RE HIRING!!"
Skills Required:
BEFORE: HTML, CSS, JS, jQuery
NOW: REACT/VUE/ANGULAR, NODE, CI/CD PIPELINE, DOCKER, GRAPHQL, JOHN CENA12 -
Just finished this great book! It was really entertaining and interesting 🙂
And it explained the advantages of DevOps and CI/CD in a very understandable way 😁
Do you have any other good recommendations for IT novels?
10 -
Dear recruiters,
if you are looking for
- Java,Python, PHP
- React,Angular
- PostgreSQL, Redis, MongoDB
- AWS, S3, EC2, ECS, EKS
- *nix system administration
- Git and CI with TDD
- Docker, Kubernetes
That's not a Full Stack Developer
That’s an entire IT department
Yours truly #stolen9 -
Just scored my personal red flag bingo in new project:
- engineers who work there for 20+ years
- their own in house build tool
- "we have Jira so it means we are agile"
- "we have Jenkins so it means we do Ci/cd"
- git adoption is "in progress"15 -
senior devops in the school IT dep: "gcc is not working, it keeps telling theres no input files when there is, and its failing most of my builds"
are you sure sir? Give it another go
(Meanwhile my friends managed to sneak a "fixed image")
see? it works.
Senior Devops: " I swear it didn't work"
(we giggle)
check the last build's .bashrc
>alias gcc= (the error message e was referring)
Senior Devops: "MOTHERFUCKERS"
Actually its just your infra that we pushed the image to, school infra is unaffected
I mean it was fun while it lasted.4 -
Yet another nice (bad) tool with a funny name: volkswagen
> Volkswagen detects when your tests are being run in a CI server, and makes them pass.
LOOOOL
https://github.com/auchenberg/...3 -
Woooooooo!
Just finished my first fully automated CI/CD system. Now all my commits go through the pipeline and gets deployed to live automatically.
It's a small project but still, it's really cool!10 -
Oh boy, I think I need a new pair of pants.
GitLab (!Github) have improved their ci/CD pipelines to allow you to chain jobs 🥳🤤
https://about.gitlab.com/2019/08/...
2 -
Really, I hate this composer / bower / npm shitholes!
Why the hell is my app 300MBs?!? Because that shitty pudding composer decided to download the ENTIRE git including README.md, examples, 5 hours of assembly-giraffe porn, my granny's pajamas and two wraps of kebabs!
How hard is it to define the folder that contains the REQUIRED library so that our project might stay at 5MBs instead of 300?18 -
A coworker complained that the ci server is to slow for a build. Found 4000 js library source files which are copied in each build.
-
Do Travis CI's email subjects really need to say "Still failing". As if I don't feel bad enough.
Fuck you Travis i'm trying!!!1 -
The spaghetti monster is online.
Literally changes on the last minute.
Pushed to master, let CI/CD deal with it and left for lunch.
Bugs? Haha, sure.
Serious one? You can bet.
Do you care? Nope.5 -
There is nothing sexier than a well designed CI pipeline....i have wet dreams about that green check mark.3
-
Gitlab's CI/CD, Jenkins, TeamCity, Travis, Bamboo,.....
Fuck it, I'm too lazy to learn them all to pick the best choice for my case.
Meet 'pipeline.bash'
Perfect!
15 -
The CI just errored out with no explanation.
Like nothing...
Just code 127 on bash...
I think the CI hates me
5 -
You dense motherfuxker. There is a reason why we create a separate feature branch, put our code there, check the CI and THEN merge that to master. The whole reason of merge feature to master is that the CI DOES NOT GET FUCKED UP! You never keep committing your feature changes directly to master. THAT'S HOW YOU FUCK THE CI UP.9
-
PSA:
Next time you plan on changing all your model names from "xxxxx" to "xxxxxModel", under a minor version bump so that everyones CI breaks, in order to deliver no benefit whatsoever ..... don't8 -
Today, I suddenly received a "build error" email for master on a project that I am working on with my grp.
So I panicked and opened the log to see who messed up. This is what I see
-
I recently started working with CI/CD in gitlab. I don't know why I had such a hard time getting it to work. I left it hanging for another day. Yesterday, before I went to sleep, I merged to master branch. On waking up I can't explain my happiness when I saw my pipeline... 😀
6 -
CI/CD is probably the best thing that I ever learned about in the software engineering field.
Whenever I merge into master, my code automatically builds and the artifacts are uploaded to a new release on github.
Beautiful.4 -
So happy I found GitLab! Best feature is the integrated CI. No need to pay to have CI for private repositories for my hobby projects 👍14
-
someone pushes code and breaks ci.
me: you broke the build
her: (ignoring the explicit error message) it works on my machine, travis is broken
me: it doesn't even work on my machine!
her: I forgot to push one file, sorry.1 -
!rant
I've been doing wrong these last year, so I decided to step up my game, implementing on my work cycle:
+ Testing
+ CI
It feels fucking great. If you're not doing it, it's time.
1 -
Every last 10 days of the year we have a break...
I'm just gonna implement CI/CD in this motherfucking environment and blow everyone's mind at January, I'm sick of working as an amateur... -
"I couldn't fix the test so I commented it out."
"I removed build timeouts because our jobs started taking that long."
Next I'm waiting for "Compiling the code is good enough we don't need tests" before I lose it...1 -
Hate when my boss says, "hey you, over there, can please automate this stuff, is a pain in the ass..."
2 -
*Makes a small change in Webpack generator for Eclipse Theia*
*Takes 10 minutes to complete all tests*
*PR*
*Travis CI builds*
*Takes 30+ minutes*
Uh, Travis, you okay?
-
Infra engineers should be war veterans
I literally spent 4-5 days on CI, DevOps and Intune
The worst part is you don't even know what will happen until the CI runs
4 -
That moment you receive an email: your CI build is failing.
Ok. What went wrong?
Three new commits that do not seem to alter anything related to the failure.
*reverts commits and tries again*
Still failing.
WTF?!
*restarts previous builds*
They now fail too.
FUCK! BASTARD! Are you kidding me?
*investigates*
Turns out that repo of dependency changed and is not compatible anymore.
Argh! Son of bitch! -
YESSS!!!! IT'S GREEN!!! FINALLYYYY!!!!!!!!
3 weeks ago I started building this CI pipeline. Finally, I see something GREEN!! YAYYYYYYYYYY!!!!!!!
P.S. A complete build requires 23GB of disk space, lasts 1h40m, and artifacts are too big to be cached, so everything must be shoved into a single CI job.
You've gotta love building monoliths...11 -
Setting up CI.
Right now it took me AT LEAST A FULL DAY TO GET IT RIGHT.
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
*dies*5 -
👍 https://github.com/auchenberg/...
"If you want your software to be adopted by Americans, good tests scores from the CI server are very important. Volkswagen uses a defeat device to detect when it's being tested in a CI server and will automatically reduce errors to an acceptable level for the tests to pass. This will allow you to spend less time worrying about testing and more time enjoying the good life as a trustful software developer."10 -
CI came up with 265 errors. (deploying to an old server to bring it back).
I make some very clever fixes and run it again.
Now we have 269 errors.
-_-2 -
Finally my employer managed to pay for the upgrade license to have 80 instead of 40 seats in our CI tool. Took only 4 months. Guess who is currently using 110 seats. 😓2
-
Built a whole test suite around our Laravel app which has been pointed out to exec as slowing down CI and yielding no value to the user.
Arguing it’s ensuring something our users is using doesn’t accidentally break just gets brushed off as incompetence.
Oh well, I’ll just skip tests in CI and continue writing and running tests on my own as I don’t feel confident just cowboy fixing things.2 -
Started my new job as a devops engineer, its been al month and i have never seen the seen of aws console or travis ci, dont even have credentials for any company cloud services.
I guess i should change my job title to backend dev1 -
THE MOTHER FUCKING INTEGRATION TEST ALWAYS BREAKS IN CI ONLY, NOT ON MY MACHINE. SEEMS LIKE HE HAS SOME PERSONAL ISSUES WITH ME. THE FUKING HAUNTING GHOST4
-
I think I'm getting crazy...
Yesterday evening I finally thought it was a great idea to set up Gitlab CI to let the server build (ng cli) and deploy (via FTP) an Angular5 SPA on commits on the master branch.
BUT...
The npm package "vinyl-ftp" thinks it is pretty fucking funny to just randomly stop in the middle of uploading files or just upload some files with 0 bytes in size.
WHAT THE HELL?
After some hate infested trial and error, it seems that the more parallel channels I set up, the more chance I get that all files are correctly uploaded, but never all.
If anybody here happens to be some kind of mighty byte bender and knows what to do, I'd be thankful. But I will probably try out a different client in the docker image...1 -
See that dip in JSON in 2018? It's countered by a slight rise in YAML. According to this article, it's because of all CI and Docker services. Can't think of many reasons to use YAML above e.g. JSON.
https://theregister.co.uk/AMP/2018/...
20 -
I know you, youre out there somewhere, coding, feeling like shit, putting your best, listening to coldplay, in the server room, your basement ... I know you veryy well
1 -
Every fucking day I'm asked some fucking stupid question that could have been easily figured if this fucker took 2 mins to look.
"Hey why isn't the issue closed with your commit message? Is it because the CI fail?"
No you dipshit. It's because it hasn't been merged into the master branch. And no the CI didn't fail. If you took 20 seconds to actually look into the pull request you'll see it passed.
God why? -
Other Team: "our builds don't clean up properly"
*docker rm -f $(docker ps -a)*
Other Team: "our builds keep filling up machines"
*docker rmi $(docker images -q)*
Random Team Member: "My builds keep failing on service foo randomly exiting"
Other Random Team Member: "Why is there no caching on our builds"
...
team panics thinking it's their fault as our main job still passes, as it's on another machine.
...
When we find out after tracking build history
KMS2 -
Just found out that the CI for valgrind on my personal project wasn't working properly, I'm leaking memory all over the fucking place...
Fuck this shit -
** me setting up GitLab CI **
- run pipeline
- FAIL
- env variable not passed to one of the shell scripts
- set -x, rerun
- FAIL
- same reason. env variable is OK in the `set -x` output
- comment out `set -x`, rerun
- still FAIL
- same reason
- find a `set +x` left in one of the scripts
- comment that out
- rerun
- PASS
- WTF?!?!?!?
- continue on swearing for wasted better half of the day debugging my scripts12 -
You guys! You guys! You'll never believe what happened today!
I used out CI pipeline half a dozen times today and it worked every time!
Seems impossible, I know, but it's true!1 -
So I need a .gitlab-ci.yml file in the root folder of my repository for GitLab CI to work.
I've done that. Hitting my head against wall as I keep getting an error ".gitlab-ci.yml is missing from root directory"
Hour later I found out this is the filename I used: .github-ci.yml2 -
Here: this is BDD, a Linter, and Git. CI your shit to staging before you CI to production. Never deploy on a Friday.
-
I am learning about CI/CD and DevOps, and i finally made my first build/deploy/unit test script.
I use arch btw6 -
So, spent half a night setting up Travis CI. Just couldn't understand how CI will improve productivity...? But man when it worked... I wondered why I did not do it early... It even sends notification to my Slack channel...!!3
-
Moved one of my Java projects to Gitlab. Really loving the Auto DevOps and CI. Currently not missing GitHub.
-
CI CD pipelines in my company... Having CICD suppose to help development... Now we have countless templates and tools (github actions, circle ci, agro, aws beanstalk, azure pipelines, serverless, terraforms, cloud formation, helm charts, ECR, Vault... and few more).
Total chaos, doing simple CICD for 1 api and 1 lambda took 3 days so far, and will take bit more.
On top of that, no one have idea which part of scripts are doing what exactly, as responsibilities are in different tools (each tool have different config files).
Does deployment have to be so complex? Or is it that my company DevOps team makes it so unnecessary complicated?4 -
You can connect to Docker containers directly via IP in Linux, but not on Mac/Windows (no implementation for the docker0 bridged network adapter).
You can map ports locally, but if you have the same service running, it needs different ports. Furthermore if you run your tests in a container on Jenkins, and you let it launch other containers, it has to connect via IP address because it can't get access to exposed host ports. Also you can't run concurrent tests if you expose host ports.
My boss wanted me to change the tests so it maps the host port and changes from connecting to the IP to localhost if a certain environment variable was present. That's a horrible idea. Tests should be tests and not run differently on different environments. There's no point in having tests otherwise!
Finally found a solution where someone made a container that routed traffic to docker containers via a set of tun adapters and openvpn. It's kinda sad Docker hasn't implemented this natively for Mac/Windows yet.4 -
Me (new position): Hey, can I run this locally?
Other dev: No, it can only run through CI.
Me (exploring): Oh, I see. CI -> Docker -> Makefile -> Ansible -> Packer -> Terraform -> new EC2 image -> new EC2 host -> command.
Well fuck. That's not going to work locally.4 -
Nothing better than walking out of the examination classroom, opening up your phone and being flooded with emails and messages about production servers being down
It's that time of the week again
Luckily, now that everything is in place everything is 100% automated with ci/cd 😎2 -
I've just wasted 2 hours fixing an issue with a GitLab CI YAML definition, all because of a single colon:
echo "Detected changes: compiling new locks"
I swear to god, whoever thought it is a good idea to use YAML for CI scripts should rot in hell.15 -
Travis CI will finally allow you to run both open source *and* private repos on travis-ci.com. That's awesome. Does that make your life simpler to manage .org n .com things?
https://blog.travis-ci.com/2018-05-...1 -
Finally found a way to deploy my Docker image to my VPS with nothing else than GitlabCI. My CI/CD system will soon be perfect.
[ Heavy breathing ]3 -
YES!
Finally got our CI/CD line working correctly after two days worth of intensive work.
Got me thinking - what do you use for CI/CD? -
this really happened:
Interface Team Lead: "hey I want any time deployments and better QA"
Me: "ok sure. I have CI/CD, but yiu need to work in feature branches / tags, and make sure your code passes automated builds and unit tests"
Team Lead: "I dont have time to test it makes me unproductive! and creating a branch is an extra step which is going to set me back. Im telling the boss you are impacting performance!"
Me: "you want better deployments and QA, but you can even create a branch or tes your work?"
Team Lead: "We have deadlines!" -
Do you guys know the feeling when your opening PR on side project late at night..
The CI takes forever to make all the analyses and checks and you almost fall asleep because your so fucking tired? -
The CI infrastructure and external tooling at the company I work at is a complete joke. Feels like it was designed by an intern left alone.
95% of the time a build fails or hangs, it's because we are getting race conditions or a hanging VM with our crappy Windows jenkins slaves. Quite possibly because we are not using proper tooling for monitoring those VMs as well. Anyways, I don't have access and control on it and it's not even my job to fix it.
Though, I am being asked to monitors these pieces of junk jenkins jobs outside of my work hours because company devs all over the world use it... but there is no fucking way to know it failed unless I log onto jenkins every hour and check everything manually... which is stupid as fuck for a software engineer.
I can't even implement slack hooks to get notifications or something when it fails because we will stop paying for it soon, so I have to connect to my freaking VPN on my PC and check everything.
And what's the fucking ghetto solution instead of fixing it properly? Restarting VMs and rerunning a build. Because someone in management wants to see a passing build, even though it means jackshit. Half of these jobs are tagged as unstable, so what's the fucking point?
Pisses me off when people work like morons and pressure others to do the same.1 -
Can't believe i've just had to explain master/slave terminology to someone who has been running our Jenkins CI/CD stack for several years.
That's unusual right?6 -
What the fck is CI/CD?!! Hmmm 🤔 I don’t know, but it sounds trendy so might as well pretend to know it to sound cool.13
-
shutdown an old Jenkins CI pipeline from one of our teams... after one month they call us to bring it online again because they don't know how to build it manually.... lol #automation #scripting #jenkins2
-
When I have a Jenkins build fail, then fix the issue, I run the build four more times manually to make that branch "sunny" again.1
-
Jenkins you are a bad butler! Why can't you just do your job? We wouldn't be in this pickle if it weren't for your incapability!
Job opening: any suggestions for a replacement butler?4 -
Watching CI build is the most interesting part of my day. My app always breaks in wonderful and exciting ways. :|
-
Got engaged to set up the CI for a project. Worked with the main developer to set up the dev environment only to find out that he deleted 80% of the migration files because he didn't know what they were
-
"Here customer, have the username, password, and URL of our developer's CI environment! You can test all of your features there. "
" Devs: Please don't make any changes to dev code that would cause the CI system to run."
That's not how this works. That's not how any of this works.2 -
My biggest bad habit (for now!) is rushing changes. I have no real deadlines, yet I rush commits and cause failures in our CI tool every week1
-
Just published my first composer package :) It's no big deal most likely but had to let go my excitement somewhere...
It's a package to jumpstart PHP projects wanting to use Gitlab CI by adding some defaults, and adding automated on commit formatting checks.
Main reason I created it, is because i was tired of doing the same config over and over again for my projects...
Anyhow if anyone were to be interested, here it is => https://packagist.org/packages/...
Oh and by the way, yes, it's PHP, and yes I actually do like working with it :)3 -
I have officially decided to use CI (Jenkins) at work because "apt-get update && apt-get upgrade -y && composer self-update && composer update && npm update -g && npm update && bower install --allow-root && gulp" after a pull doesn't seem healthy 😂2
-
So I was searching how to speedup my page speed of site which is built on Codeigniter and despite minified css and js I read this:
" CI active records are garbage, use classic quries"
:'( I used active records all over my app -
I just put my side project working with friends to Gitlab.com. Start to wondering why I was choosing between github and bitbucket while gitlab provides free private repo, free CI runners, and all other useful collaboration tools.6
-
When you are new to a technology and language, but have to make full use of its feature.
You know, make tests, implement production code, planning deployment, build a CI. All by myself.
No regrets, though. Challenge accepted!1 -
Counted it out... 100k LoC frontend & backend... Not a single automated test. No unit testing, no integration testing, nothing. I've been asked to implement a CI server.
Halp5 -
"Sorry, but nothing in this MR is as it should be (I don't even know where to start) - all you do here is waste scarce CI resources"
Much helpful. Such wow. Teach me how to make such toxic and useless merge request comments.5 -
After a couple of days reading bout CI/CD i find it really compilated for my usecase. Server for jankins server for rancher server for anything and a lot of configurations to make it work. So i gave up and decided to build my own CI tool which turned out to be easiear than all of this. So i wrote a simple cli tool in go which listens on master branch of every directory specified in a .yml file and everytime a new commit is done it pulls the repo and rebuilds the container. Pretty easy without having to deal with all the bullshit15
-
I am lying down on the floor because I cannot figure out why this specs pass locally but repeatedly fail on the ci/cd pipeline. Literally done everything now I just want to lie here and sleep.3
-
I had to argue with my lead today, to prove that docker is actually a container technology and not a CI CD pipeline -_-
That too in the team meeting.
P.S. Not much of his fault though, as ours is a mobile app development team :/5 -
!rant
there's almost nothing more satisfying then getting an automation script or CI/CD pipeline juuuuuuuust right 😎 -
🎼Cu-cum-ber docs led me to beliiiiiiiiiiiieve
The exit flag was un-nec-e-ssaryyy
Thought I’d make a new branch
Remove it in CI
Let it run in Jenkins
That’s the reason for the never-ending teeeeest ruuuun 🎶
^to the tune of Neverending Story6 -
I currently use Github as my git server and have worked a little bit with Travis. Sadly Travis can't deploy to local network targets and that's why I had the idea to create my own basic CI for the local network: It will be a simple nodejs-app and listens to pushes via Github Webhooks. Then it fetches the code from Github and runs a task runner like Gulp over it and tests it with any nodejs testing framework. Then it deploys the compiled, tested and linted app to the local network. What do you think of this idea?8
-
Today is the day when we rip out our old deployment system and get some new blood running through the CI/CD pipelines. Wish me good luck! Please...2
-
Yesterday, I was expecting my merge request to be closed.
I've done all the stuff my tech lead told me to do.
All tests passes, green light boyzzzzz.
Gitlab CI pipeline passes, greeeeeen light I said.
In Jenkins everything f*cked up...
Why ??
Well it was a conflict with 3 other MRs, missing rebase from other dudes.
And because they were remote working, got to clean up all this mess.
That's was a day off.
PS : well that's was not so off, I could fix a UB on a ternary and extend a test which was not covering some cases.
PS2 : learn git damn3 -
When I'm at a medium sized company: Let's get CI/CD so we can build things and release things fast and stress free.
Now working at a big company. We have all the CI/CD we can ask for. Why are things still so slow and stressful o.o5 -
Don't you just love it when gitlab's ci pipelines crash for no apparent reason, causing tests which cannot fail to just magically break down, change logging levels to Just about anything and basically PMS for about 3 hours before it decides it needs to restart completely and when you return the same pipeline which you've been trying to fix for the better part of an entire evening, after regular work hours, it. Fucking. Works. With. No. Changes. To. The. Entire. FUCKING. System.
Waste of a day.3 -
Question for devs who work in large multi-team environments:
A) What is your code review process like? Does a senior review it once and then it's off to QA or do you have "levels" of approval?
B) If you're launching a feature that depends on another team how are you coordinating it? Do you just talk over a ticket and then hit merge and deploy at the same time or like what's your process like?
C) What CI/CD tool do you use? Also what code hosting platform do you use? Github/GItlab/etc.
D) Are you currently happy with the CI tool you're using? If not what are some common issues you're facing?5 -
“I can’t wait for all those breaking changes, mismatched package versions, new build tool configurations, virtual boxes, and CI setup!” ~ hourly billing
“Let’s use HTML.” ~ value pricing -
First time I use Travis CI today :D
(And my first build error ever...)
In combination with Nuxt.js it is so fucking useful for Vue Development. Wow!
I think I've found my new favourite JS Framework.
Had a bit of trouble with Github Pages but I just created a 'source' branch with the source code and a 'master' branch with the deployed site. The reason is that organization sites can only be published from 'master' branch for some reason...
Anyways Travis CI is very useful!3 -
For all the effort it takes to setup CI/CD it's totally worth it. My god this is marvellous I've wasted over 40 build minutes already just to see a spinner spin until it turns green :-D2
-
My department never has real pressure like real outside deadlines. Except for this project.
Now guess what happened during the final hours of the project:
Fuckin circleCI goes into "degraded performance" (last time it was "partial outage").
I feel like calling my friends Johnny Walker and Jack Daniels over for some late night work. :P1 -
50 build minutes per month? what is this, 1990? it's not like atlassian is scraping around for money either....
sheesh
and the rich get richer...
WELCOME CIRCLE CI! (almost TOO generous in my opinion)
4 -
Name a more 2018/2019 New Year’s Eve.. We used a new emoji in a commit message and it borked the CI pipeline.
3 -
It usually starts with a project, a CI pipeline, unit tests, deployment guidelines, and wait - oh crap - what am I building again?
-
GitHub Actions. That is all.
Well, not really. Trying to convert a grunt script which we have packaging our WordPress plugins to be done as a GitHub action instead and I'm about to throw my machine out of the window.5 -
Tired of writing git commit messages
Try this
git:master>⚡ mym
Fixing Lukasz's bugs.
git:master>⚡ mym
some brief changes
git:master>⚡ git ci -m "$(mym)"
Based on http://whathecommit.com2 -
I decided to make some new icons for Atom editor (the launcher/executable ones), because I liked the vscode-icons project.
Made the repo on GitHub and decided to automate making the icons for different OS using Travis CI.
Started writing the Python Script for Travis.
My google queries:
How to generate icons for Linux?
I can use SVG or generate a PNG, many libraries available. 👍👍
How to generate icons for Windows?
Generate PNGs of various sizes and pack in an .ico file. Easy enough
So far so good.
How to generate icons for Mac?
Mac needs a .icns file, a package of PNGs of various sizes. Libraries available but can be done on OSX only. 😫😫
Then I think, what OS does Travis use?
Oh, I can specify macOS in it 😁😁😁
Starts the build 😎😎
Travis doesn't support Python on macOS
😑😑😑😑 -
Codeigniter (a PHP framework). Every time I stumble upon a CI project, it's always a mess, since they don't have that good of a documentation like Laravel.2
-
<Question>
I'm curious: For those of you who have tests running in CI pipelines at work:
How long does it take to run the tests, in relation to the system's size?
At my company, it's ~ 30 mins, testing 1M lines of code (750k SLOC) written in Java (85%) and JS (15%).7 -
Having code review with static code analysis and running unit tests on every commit is super useful. Except when you are commiting stuff in a biggest repo in company that goes through CI in ~20min+ and if you try to additionally deploy it to dev server... you'd better brace yourself...1
-
Dahhhh. Pay for a damn hosted CI server please, like Circle or Travis, so I don't have to maintain this crappy Jenkins instance. More "plugin" updates by default than a crappy wordpress site.
Talking of which. Circle CI has come on leaps and bounds since I last looked at it. So much nicer than Travis. Think this is going to be my de-facto CI solution for open source stuff from now on.10 -
A few weeks ago I finally got buy in to migrate our web team to GitLab for CI/CD.
All week GitLab has been having issues, pretty much rendering us unable to deploy anything with confidence.
Can't wait for _this_ to come up. haha2 -
It's really fun to not have access to the CI backend and keep only troubleshooting build crashes through a CI that takes 15min to run until it crashes :)))
1 diagnostic command == 1 pipeline run
1 typo == another run :)
it's been 2 sprints now. Still no luck2 -
Spent the whole day testing the tests.
CI is pretty fun, I get to slack off the whole day, because one test run takes around 10 minutes (without compiling3 -
I love that I need to fucking babysit the fucking CI pipeline because, half of the times, it just RANDOMLY FAILS and I need to hit that fucking retry button like a 19th century kid respooling a loom.6
-
What CI software are you using?
Are you happy with it or what do you hate about it.
I tried 5 different CI platforms in the past week, and I did not like any of them..
Any recommendations? (Can also be self hosted, I have a k8s cluster at my disposal)
// a short rant about team city
wE uSe koTliN dSL to reduce how much configuration is needed, fuck you I ended up with even more, it's horrible I have 40+ micro services, meta runners sounded like a awesome feature until I found out you need to define one for ever single fucking project...
Oh and on top of that, you cannot use one from root parent, but also it cannot be named the same.
Why is all ci software just so retarded - sorry I really cannot put it any other way10 -
flutter run
>Unable to load asset.
flutter clean
flutter run
*10 mins later*
>Unable to load asset.
*I should prob use ci for this*
flutter clean
flutter run
>Unable to load asset.
*sunken cost fallacy intensifies*1 -
Started working on the game I want to make. Decided to go through the android publishing and it took like an hour to get it all set up. CI/CD not easy with game engines either.
-
Should I connect my vacuum roboter to Travis CI/Appveyor and let it start cleaning on each successful deploy for a minute?
Just collecting ideas for the time it arrives and I root it :D7 -
Testing builds remotely with pushes before testing them locally because I'm too lazy to bring up the local CI server.
Ending up with over 9000 "Testing build" commits.1 -
I just seen github's new pricing model. Does it make sense to switch from a self hosted gitblit server? And what free-cheap ci servers do they have?3
-
Hi guys,
I'm going to make a template project for Cpp. And one of my questions is how to use Travis ci to test things with clang 6, on every platform. I was thinking about using a custom docker, but I didn't find a project using this. Is there a problem with it?5 -
Question for my fellow devs:
Do you feel like you are spending too much time on maintaining ur devops/infrastructure rather than focusing on the actual product?
Do you think your company would be willing to spend a bit of money to outsource scaling problems to someone else and just focus on the product?
Ik we got lots of fancy new CI platforms like Circle CI GH actions etc but like I personally feel like I’m doing certain infrastructure tasks twice when I look at the two different codebases I work on.8 -
Follow-up to my exp with Travis CI: https://devrant.com/rants/5006826
As my allotted credits are set to expire on December 23, I sent a request for 25k monthly OSS credits to Travis support on December 18.
Mind you this is only half of the credits of their lowest subscription price and I didn't ask for extra CPU, so not much to ask.
While for the previous credit request, I got an answer within 24h, this request has gone unanswered for over 2 working days and I noticed it got labeled with "Priority: low" although I will be unable to continue my OSS work in 2 days.
Let's see whether they plan to really uphold their promise that "they will always support open-source" -
Frontend: $ vue init ducksoupdev/vue-webpack-typescript bodywork, setup some linters, formaters and ci and I'm ready to go
Backend: $ cargo new --bin gears, setup some linters, formaters and ci and I'm ready to go -
What's better in general:
#1 master merge -> production
#2 master merge -> button -> production
And why?
At work we currently use #2 because sometimes we need to make manual changes or update images on prod before we can fully update the code
Edit: This should have been a 'question' not a joke/meme, sorry about that -
A home hosted build server for continuous integration is always crap and a blocker for everyone. If you don’t have 5(yes, five) full time admins/devops to support that, forget about building the infrastucture yourself. There are companies whose business is to provide CI as a service, why do you think you can beat them with your crappy Jenkins installation?
I’ve seen a 200 company failing with 2 people. I’ve seen another one completely failing, because the admins didn’t know what CI meant, and a small one failing with 0.5. The only place where it kind of worked used Gitlab. -
!rant
For the past weeks I've been reading about continuous integration and today I finally decide to dive into Gitlab-CI. After a couple hours I finally managed to have a working pipeline for one of my project using a self-hosted runner and holly shit that was satisfying. Now I just don't see myself not using this in the future -
Just a reminder that Terraform is insecure by design and if you even THINK about using it to execute CI/CD deployments not built into the cloud (Jenkins, on-prem CI/CD, etc...), then you're a DOUBLE fool. God i hate my infra team sometimes...15
-
Small rant:
Spent a week or so setting up CI/CD for all our repos.
Next week: were migrating to a new git service and need to redo it all.
I've actually really enjoyed it though so I cant complain too much -
Here's my checklist:
- education opportunities? Conferences etc.
- blogging?
- open source contribution?
- test coverage?
- CI/CD?
- always meet with the team -
The CI on Mac is broken. Again.
Next time I have a client that wants me to work with Apple, I'll double my rate. -
I have never used Docker and/or Kubernetes. Motivate me to use it by telling me how cool it is.
I want to build a complete ci-pipeline but am too lazy to start... there is so much to do, and I don't know where to start.6 -
Best tools/guides to setup a pipeline for C# applications that need to be built tested and ran on windows and linux?1
-
It's the top of Round #6, the score is:
CI-Pipeline with 5 points, and the developer with 0. Remember, these rounds are 20 minutes long. Let's see if the developer can get a point before the end of the first two hours.1 -
!rant
What a great feeling when you push a big bunch of changes and CI makes it over the biggest hurdle (lint and test). Time for a fresh cup o' coffee while the build finishes. -
Daaamn.. Dagger.io is actually quite cool. Spent 2 days learning and building a dagger module for my project's ci and I've gotta tell ya - I'm lovin' it!
-
What do you hate most about your current CI/CD setup at work?
Mine is that staging and production are released independently. If staging fails, it can still roll out to master. This scares me.9 -
spends almost 5 weeks trying to get CI/CD to work with Kubernetes (including installing Kubernetes itself).
Decides that he might go see if Nomad is a better thing for him...
Man, if only I discover stuff sooner...3 -
This fucking ci/cd test keeps deleting my dB collections and I can't see what the fuck is going on. Circleci is of the devil and I won't stop fucking using it. I must crack this shit😡2
-
Why do tech writers always produce deliverable documents in Word files instead of Markdown, LaTeX, or anything that is easy to CM? It would be easier to track revision history and dump out of the CI/CD pipeline to the customer.4
-
Creating the build script for the CI pipeline:
- 20% trying to avoid someone getting access to passwords, tokens, etc.
- 10% writing commands for the build and tests
- 70% writing work arounds for bugs and errors caused by the CI system or SDKs in headless environments...4 -
I want to store my built application inside of some kind of registry or repository. Is this best practice and are there tools for doing this? I cant find anything except Artifactory, which is pretty expensive.14
-
Spent all afternoon trying to make CI work for my own personal website, trying out a new concept, that I call Frontend only, it restores, builds, but fails to deploy with connection dropped after a few seconds... For all of the Gods and Saints of deployment please grant me stable connections, thanks
PS: you guys at cPanel Fuck You, thanks -
If you centralize your development model, ie even just say CI/CD for a mid-size company > 50 devs, you are setting up for failure, maybe not now but eventually when the market catches up.
A single point of contention is just bad.5 -
I'm in charge of our Maven based build process. Doing CI with Jenkins. Coworker develops huge multi module project, doesn't take care of hierarchical structures or any other Maven good practices.
Build fails due to several circular dependencies and other ill stuff.
My fault.
Ragemode. -
YES! YES! YEEEEES! FINALLY!
I've been trying to get some systems to run successfully on docker swarm. Now forget a regular swarm, there have issues just getting it to pass CI builds, and Finally, YES FINALLY it passed!!!!
I now need to pass my self on the back...
-
ci tools in cooperation with git servers because i work on different machines and only one of them has the full development environment. (every other machine has only an editor (atom or vi) and git when it comes to dev tools)
-
Alpine 3.10 image's shell doesn't know globstar. After reading some article and feeds written by GNU and stackoverflow, I replace ** with {*, */*, */*/*, */*/*/*, */*/*/*/*, */*/*/*/*/*} in CI scripts to meet the temporary requirement sadly :/3
-
please i need your advice :)
I need to reform a service that offers legal advice and thus serves around 5000 Microsoft Word legal advice documents for the end user and every year there are 200 more documents created and published and changed manually.
So i had this idea to use a CMS, Git and continuous integration for
- automatic spell checking
- automatic assigning the copy text to translation bureaus, and get translations back.
- version control the texts and translations.
- document generation in multiple formats
- checking the text flow in the document (no overflown text)
- Checking for accessibility for the handy caped
- Deploying it on the Website
Do you think this is feasible? Can something that was made for code also be used to handle copy text documents? In my head this would save so much work but i'm no expert in CI/CD.
Thank you for your advice!8 -
Travis CI is good. Yup.
Coveralls is good. Agreed.
Appveyor, codeclimate, Jenkins?
Okay, that’s too much. At this rate, no features are gonna get done. -
So, it works on my Mac and in my teammate's PC on Node 4.0, 4.4, and 6.9 but random tests fail on the CI build with 4.4. FUUUUUUUUUCCCCCCKKKK!
-
Guys and gals, what's tour opinion on static website generators? Have you ever used one?
The concept kind of intrigues me and I was considering a Hugo + Travis CI stack.7 -
Fuck teamcity. You locked my domainaccount 2 times already this week. Even when i used a accesskey it queried the AD.2
-
Was working with my internship boss to implement an CI but the documentation were cryptic and no fucking support on the forum whatsoever.
So I started working on creating my own CI dubbed Blackjack CI and he posts this on the forum
https://discuss.circleci.com/t/...
But how fucking hard can it be to have fucking propped documation.2 -
I love that Travis-CI lets you change all the on site fonts to comic sans, but no dark theme. Maybe if I paid them...
-
As a front-end developer who has a firm grasp on web tooling, I still think the sheer amount of knowledge needed for dev-ops/deploy tools is staggering.
-
Does the company you work at have a CI/CD pipeline (Continuous Integration/Continuous Delivery, e.g. with Octopus Deploy)?
Sometimes it surprises me how many companies don't have this..10 -
Puppeteer, where have you been all my life?
Also anyone get a chance to check out cypress.io and uilicious and if so, what were your experiences? what would you recommend? -
GitLab, you really should fix your CI.
I mean, I know .gitlab-ci.yml has to be written carefully, having in mind that GL shell is a castrated bourne shell, but come on... Failing a pipeline because I used a semicolon in an `echo` parameter string?
echo ""items: 0" ## this will fail
echo "items 0" ## this will pass
This is a bit too much.
Removed the semicolon and the pipeline worked just fine.
11 -
Few things are more frustrating than fixing a bug only to have CI break because the fucking test runner that has always worked, and is working locally, just won't run on fucking CI, preventing you from deploying said fix.
-
Me: Code checked in, CI and tests passed, deployment kicked off. Huh maybe I won't have to stay late after all!
Production Web Server:
-
I keep a collection of strange logs I see scrolling by the CI Pipeline. What's your strangest log entry?
-
Would you consider compression (gzip static files) as a prepare step of the deploy stage or as a part of the build stage?
It's somewhat irrelevant but its bugging me8 -
!rant
I haven't used CI/CD to actually deploy an app. But I really want to automate all of that in my company. We use gitlab, so the logical thing is to use Gitlab's devops(?). Anyone who can guide me on an adventure for starting on CI/CD? Not sure if I need to give any more info, please let me know14 -
To the ones using GitLab CI/CD:
Is there a way to trigger a pipeline run on a specific commit? Like in a situation where you're deploying every commit to master into prod, and you need to roll back, but without reverting the commit history.14 -
Pipeline as json is pain and you can't even validate until it breaks on the ci
#makesProgrammingHell4 -
Just testing the waters here and seeing what I read online has any basis to this:
Jenkins is the WordPress of CI/CD tools
...Discuss6 -
Which CI is best for open source?
TravisCI look pretty promising, GitHub Actions too, but with Travis you can have 3 concurrent jobs on their OpenSource plan. -
How can it be hat magento, one of "the" eCommerce softwares with a pretty based "cloud" plan and all that, is just offline for "planned maintenance" for TWO DAYS?!
CI/CD?
Cloud?
Dont your customers pay you enough for this basic stuff?
And also the opensource segment ist offline for the whole "maintenance" period.
RANT -
*deletes env var* "I'll just hard code this to localhost for now, my ci/cd pipeline will setup everything later"
*Pushes to master, forgets to undo*
Aw fuk,
I should of just changed the .env file -
Anyone who has worked with travis-ci for building their python project git branch? Seems that my yml is not configured properly and don't know how to create one correctly. The current build error is attached. Any leads are helpful.
Ps: Have not pushed any unit test cases in this project
FYI: deliberately marked branch and stuff in astresik. you can assume it is correct.
4 -
Does anyone uses GoCD over Jenkins?
Is it really better or just a nice homepage?
The interface remembers me CircleCI.2 -
Anyone ever passed docker builds between stages in gitlab ci?
I'm googleing my ass off and doing it via caching atm but it's unreliable. Artifacts are no option either for 2gigs of image.
It'd be nice to drop this `docker save --output image.tar` solution altogether..
Am I the only one trying to have seperate build, test and deploy stages for their docker builds?15 -
I'm tired of this crap. You know what? Next time, just git push directly and let code analysis/CI machines broadcast all the insults you require on slack.
-
I want to share one of my recent interview experience..
so first round was telephonic and technical guy seems cool as he did not emphasis on syntax, function name etc.. but just took the info of my tech on which I am working on and discuss some approaches to find a solution towards the problem.. ( I guess thats pretty well for experienced dev)
Second round was assignment and its a hell of assignment :( atleast for me.. Like I work in CI 3 and I did assignment on CI 4. almost everything is changes in CI 4 ( I mean its structure writing the way of routes,models and controllers).. But I took the challenge personally and finished 95% of assignment ..
Overall this interview experience was pleasant one.. :) -
My build is failing on the CI server
you are the DevOps engineer please fix it
this is not how this works, this is not how any of this works -
F***ing GitHub Actions.
I just wanted to make Snapcraft builds of my game with CI and instead I'm fiddling around with YAML syntax because for some reason everything got formatted incorrectly.
Also I have no way of testing the workflow locally to save me commits. So I have to wait five minutes each time to find out that I yet again somehow mucked up the script and it couldn't snap the executable.7 -
Just realized a crucial thing when using Node.js together with Travis CI: Be VERY specific when you specify dependencies!!!1
-
Splitting acceptance tests into categories of "blocking" and "non-blocking" just to allow CI to pass, is a waste of time and effort.
-
Watching CI builds run your tests and then deploy the passed version to thousands of users....oh, and the free hardware :)
-
It wasn't an entirely solo projext but ever part of it was completely solo. I felt very proud of the ETL, DICOM metadata search database and Ci/CD pipelines that I built for an oil and gas company. They didn't understand the CI/CD parts so didn't take it anywhere after we'd finished.
-
Wasted a day fighting the breaking changes and new bugs over at Google Cloud Build's GitHub integration (alpha)... I had a good CI/CD flow that is broken now because of the change... anyway, I will switch over to Circle CI... have had enough of alpha bugs for the next few months... Google Cloud Build does have an attractive pricing (free 120 build minutes per day) and a whopping 10 concurrent builds limit... but it is only supported by the community and you don't get a lot of active developers feedbacks...
-
Just wondering any of you has seen automated tests in a CI machine? Theyre not reliable enough to be running all the time because many times its just an empty error amd its tedious to investigate and wastes lots of time2
-
Screw you bamboo. Everything would be so much easier with Jenkins but this company already bought the full atlassian stack
-
Anyone know of any companies/agencies that are looking for freelance technical writers, for blog posts and such?
Mainly within the areas of DevOps, CI/CD, Kubernetes, bash etc. -
What CI CD are you using for work? Ours is a self hosted sub domain jenkins in a VM.
Also, what CI CD is almost required in every job? Jenkins? Thanks!3 -
I'm not sure why travis-ci job for node 4 is complaining for something which doesn't exist anymore.
Is it because I'm not using semicolon after 'use strict'? But then it should not work locally and in other travis-ci jobs as well.
https://travis-ci.org/restify/...
https://github.com/node-muneem/...1 -
I have this sbt test that keeps failing on CI. Locally it works fine but soon as it goes through circle CI, shit gets fucked. Now when I incessantly keep rerunning the working flow without any change, it eventually passes and I am able to deploy. I have no idea wtf is happening or what to do about it. Isn't containerizatiom supposed to solve this whole worked on my machine conundrum? I am too unenthusiastic and numb to even feel anyway about this. Wish everything would end.5
-
Motivation to work: 404 not found!
This project is going to crash, the client wants live but we have a broken ci/cd and the application is not even finished.1 -
What's the point of Docker Hub's automated builds? It's often faster to just set up a CI build to do the same thing, and it's the same amount of effort to get going.
It's way too damn slow. -
I see some of web framework use .env to store configuration file (eg Laravel, CI). Is there any benefits to store configuration file on .env file? Is it consider a good practice?5
-
Hmm..
My game changing caching proxy [mitmcache] in CI implementation works miracles in localhost. It shaves off build times significantly: what used to build in ~2min now builds in 18sec.
However, this doesn't seem to be true in CI... For some reason build times remain the same [more or less] when cached and considerably longer when the cache is cold/empty..
Damn it.
I don't understand why...
A week wasted. And I have to explain the client why me failing in this is a good thing, so I'd get paid
https://gitlab.com/netikras/... -
Is there anyone here into DevOps? I have lots of questions to ask and no one is answering on StackExchange :'(10
-
you want to build a database dump with bamboo.
the job works, everything is green AF - but there are no build artifacts. you check the buildconfig 5 times and then you realize, there are blanks after the copy pattern of the frak'n build artifact.
dafuq is this..? -
Git, GitLab CI, and Python's SetupTools are pain, hell, and they ruined my day. I can't get my project onto PyPI because it constantly errors out. Ugh.3
-
this afternoon, we got email from our pentester. He said that he got some security vulnerability in our project. He found .git/ folder in project directory in production server. He considered it as security vulnerability because user can see all git branch on remote repo. He recommend us to remove that folder but the problem is, we using CI/CD so we need that .git/ folder. My question is it bad practice to use git on production server?10
Top Tags
Weekly Rant
View