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 Support

The reason why aliens are avoiding earth:
Me : Guys, the CI/CD pipeline is ready. ci.yaml is our config file, so don't remove it as the deployments will fail.
**10 seconds later**
slack: BUILD FAILED
Me: *Looks at git commits* "Brian removed ci.yaml

Wtf BRIAN!🖕🖕🖕🖕

"WE'RE HIRING!!"

Skills Required:

BEFORE: HTML, CSS, JS, jQuery

NOW: REACT/VUE/ANGULAR, NODE, CI/CD PIPELINE, DOCKER, GRAPHQL, JOHN CENA

CI/CD in a nutshell

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?

CTO: "You must write good tests with high coverage, ideally use TDD. We need confidence in our releases."
Also CTO: *Secretly commits code changes directly to master at 3am, breaks tests, skips CI, publishes, tells no-one*

So pm2 (a node process manager package on npm) just caused thousands of CI builds to fail because of an "optionalDependency" on a package called gkt which is requested as a tarball from a server that was returning 503. That package consists of one file which contains this

Ugly logo i made for my CI tool
lol

I killed a man.

Oh, a dev sin, I haven't automated our builds yet and implemented ci.

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 #stolen

Protip: your CI always passes if you don't write any tests

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.

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"

GUYS GOOGLE's CI MASCOT IS TOO ADORABLE

AAAAAAAAAAAAA GJDJGHLFHJDLKJS

CI/CD Pipelines in real life

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!

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?

Top 10 anime betrayals

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!!!

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.

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!

There is nothing sexier than a well designed CI pipeline....i have wet dreams about that green check mark.

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.

The CI just errored out with no explanation.

Like nothing...

Just code 127 on bash...

I think the CI hates me

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... 😀

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't

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 👍

Fucking Jenkins.... Why do you hate me so

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.

!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.

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.

*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?

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...

Me (DevOps) when we started using CI/CD

"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...

Docker + GitLab CI/CD is overpowered 💓

That feeling when your CI pipeline builds.

Hate when my boss says, "hey you, over there, can please automate this stuff, is a pain in the ass..."

When you tryna just wanna get working code but CI says nah

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

Tuesday.
Director: we need to add our partner's project to our ci pipeline
CTO: we need to add ci to this repo, it should work via this tool (not the one we use now)
PM: we need to use this new tool, figure it out until Friday
TL: we need to move all our projects to this new ci tool, don't ask, the task is given by CTO
Me: okay

Friday.
Me: everything is ready except for this one old project
TL: we couldn't use it for one of our projects
PM: we had difficulties with the new tool
CTO: we couldn't add our partner's project to the pipeline
Director: *gives me a warning for being incompetent*

When you start working with a new CI/CD platform

Pushing changes to production via SFTP. Luckily I don't work at that company anymore.

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!

1. Learn Python
2. Learn C#
3. Use CI in my projects
4. (Not dev related) find a girlfriend

"CI/CD is superior because you can continuously break prod"

Building a stable CI/CD pipeline should be listed as the 8th wonder of the world.

Setting up CI.

Right now it took me AT LEAST A FULL DAY TO GET IT RIGHT.

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

*dies*

Friday...
3:20PM...

...

31982 Errors...

...

Good bye cruel world

I didn't break the CI build. I alt fixed it.

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. 😓

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.

-_-

My boss said ignore CI-CD let's just diploy it as it is localhost.

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.

You know something isn't right when you look at your CI/CD dashboard and see this:

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 GHOST

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 dev

How this is a best practice?
What about CI/CD... Every commit to production..?

Wdyt?

Me: makes the same mistake for the 1000th Git commit

My CI:

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...

So now you want the old version? Now you want GIT? Now you want a branching model with CI? 1 year into the project?
FML

I got 99 problems, but a build ain't one

Setting up ci/cd pipelines is like swimming through shit.

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

KMS

absolute CI/CD bastardization 🤡

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?

Don't run `npm install` on your build machine. Use `npm ci` instead.

I'm digging around in Microsoft's CI/CD for VSCode and hilarity ensued

I am learning about CI/CD and DevOps, and i finally made my first build/deploy/unit test script.

I use arch btw

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

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!

Did my first complete CI/CD from jenkins build from scratch and it's a huge win for me

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...!!

B Team: our code is in GitHub and we build and deploy using [generic SaaS ci] to AWS.
Me:

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.yml

If I would get 1 Dollar for everyone who breaks the build, I would never have to work again...

After remembered my boss for two months to create a team GitHub acc, he finally made it today.
Time for a new era 🤓

New frameworks, new source Control what's next?
CI Tools? 😱😂

Feels awesome to work with the good tools you already know from your private projects 🤗

Deleting my failed CI email reports, because I don't need that kind of negativity in my life.

CircleDisc is a CI to Discord Webhook integration package

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

CI/CD is fucking sexy

`git ci -m "Remove not needed escapes"`

Removed some \ from bash script.

But how it sounds :D

Here: this is BDD, a Linter, and Git. CI your shit to staging before you CI to production. Never deploy on a Friday.

** 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 scripts

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.

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.

Finally managed to get gitlab ci working !

First rant here..

So earlier this week, on a php Laravel project, I created a set of nice new features.

The code is tested, locally all fine, I push to Github, circleCi kicks in and double checks myself, still everything green. (Just for a not, its a private project so only I work on it.)

I go ahead and merge, deploy to staging and continue on my next ticket, which is a very small one.

I call it the day, next day I pick back up where I left, test locally, all green, push... then circleCi says no.

I spend 2 days debugging, trying to figure out what is wrong without advance. I just push develop branch again, guess what also failing.

I leave it for the day as I already spend enough time on it.

This morning, I simply do a composer update, push and everything miraculously starts working.. even if there were no changes in the working branches.

Im so mad right now, and this is going in my "try this before you debug a ci" book..

That moment when I finally got tests and CI up and running for my project.

Moved one of my Java projects to Gitlab. Really loving the Auto DevOps and CI. Currently not missing GitHub.

Continuous integration is an example that failure is the piller of success :)

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?

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 😎

svn ci -m "routine submission"

GameDeving.. soon my boss asks us if we can use CI, we make unity fully function with jenkins, after a week, he asks us to use gitlab ci, we make it, 2 hours later he sees the results: "yeah.. forget about ci.. let's use the cloud build".

i'm crying.

Cloud CI/CD is just someone else’s bash script.

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.

Git CI/CD works!!!
.
.
.
.
.
lets see how long that lasts...

Our backend guys don't have CI/CD, so this happens more often than it should.

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!"

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 ]

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?

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?

When my tests pass AND CI succeeds. Or just when my php code works haha

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.

Babysitting CI pipeline that keeps dying for stupid reasons.

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.

Oddly Satisfying Typo

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?

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 #jenkins

"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.

"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.

I hate/love CI

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 😂

GitHub or Bitbucket for CD/CI?

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

Debugging Travis CI is SLOOOOOOOOOOOOOWWWWWWWW.

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.

Watching CI build is the most interesting part of my day. My app always breaks in wonderful and exciting ways. :|

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

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 week

windows sucks in CI/CD!

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.

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?

Gitlab ratelimiting the CI from downloading the code. 🤡

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!

The first commits of every java repository are about setting up the CI process!

#thankyoutravis 😔

netlify.com boom!

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...

🎼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 Story

!rant

there's almost nothing more satisfying then getting an automation script or CI/CD pipeline juuuuuuuust right 😎

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.

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.

Halp

$ git push
...
CI tests fail
$ git commit --amend
$ git push -f

Nothing ever happened....

cant there be a ci/cd pipeline that just works without a hundred hours of configurations... ugh

So talking about discovering Drone CI turned into existential crisis

what a way to start 2020

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 bullshit

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.

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 :/

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 damn

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.o

Just pushed directly to master & going home now while CI is busy

Wish me luck

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 compiling

A CI tool that receives instructions in Python code

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?

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.

Name a more 2018/2019 New Year’s Eve.. We used a new emoji in a commit message and it borked the CI pipeline.

What is your best CI/CD tool? I find Travis awesome for a beginner like me.

any good source to learn about ci/cd pipelines?

When your CI build randomly fails for no apparent reason

It usually starts with a project, a CI pipeline, unit tests, deployment guidelines, and wait - oh crap - what am I building again?

“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

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 :-D

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.

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?

<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%).

CI/CD should be made with sh script only. 3rd third party I use in 6 months it’s just a nightmare

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.

tfw you're trying to get your CI on github to work

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.

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. :P

Happiness is:
1. Successfull pipeline in first try
2. ?

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 luck

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...

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!

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

😑😑😑😑

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)

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.

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. haha

Best tools/guides to setup a pipeline for C# applications that need to be built tested and ran on windows and linux?

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?

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*

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.

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.

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 :D

Im sure you and I can relate this is one of the worst feelings ever. A build failure.

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 way

I hate people who don't do basic debug and say that it is a Infra/DevOps pipeline issues. If you are not able to compile in your local how it can be compiled by CI engine.

!rant
Yesterday at 1:20 am, my first docker image build worked.

- I develop my software (a service in a micro-service architecture) in symfony
- I push it to bitbucket, CircleCI pull the code
- builds a new docker image
- Runs phpunit test using docker exec (lxc-exec, their docker exec doesn't work)
- If the test are successful, CircleCI push the image to hub.docker.com.

Took me hours to fix all the bugs and issues with this process. I feel so proud, yet soooooooooo tired fuck sakes.

I'll publish the template for everything,

- the Dockerfile for the perfect symfony2 image IMO (and I'll create a public symfony2 image)
- The circle.yml I used etc.

Give back to the community.

I love my job.

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.

Setting up ci/cd with github action is super easy