Unpopular opinion about Microsoft buying GitHub.

Just putting it out there that when you made your github repos you did so under their privacy policy and terms and will be protected under those in the future, and that both GitHub and Microsoft are corporations with the goals of making money.

Are people seriously mad that their code has gone from one capitalist corporation to another, with no foreseeable change in privacy or data policy? I have respect for those that switched to self hosted long ago since that's going from corporate to private, but if you throw away the UX and community GitHub has developed because a multinational corporation (with so many branches, products and divisions, which happens to have a few products you don't like) will soon own it, are you actually making a rational, guided decision?

Also just throwing it out there that GitLab is also a company. They've also had issues with keeping data intact in the past. They do, however, have free private repos (although I can't ever trust someone who gives me "free" privacy) as well as builtin CI. There are some definite upsides to it, although the UX has a ton of differences. If you're expecting the same dashboard and workflow you've used on GitHub, don't, GitLab has cool features but the bells and whistles aren't the exact same.

If you're switching to GitLab solely because of Microsoft, step back and think, regardless of how popular it might make you to hate Microsoft, is it really worth changing your development ecosystem to go from one corporate entity to another solely because you don't like the company?

I use GitLab and GitBub as well as Bitbucket and selfhosted git on a daily basis. They each have their upsides and downsides; but I think switching from one to the other solely because of Microsoft is not only totally irrational, but really makes light of/disrespects the amazing tools and UX the teams behind each one have carefully developed. Pick your Git hosting based on features and what works out for your use case, not because of which corporate overlord has their name plastered on it.

(Also just throwing it out there that lots of devs love VS Code, and that's Microsoft owned too... They did also build and pioneer a bunch of really cool shit for devs including Typescript so it's not like they're evil or incapable in any sense?)

Current work project is microservices architecture out of 4 - 8 components.

It is fully Infrastructure as a Code automatized. I just change somewhere code, git pushing

And it automatically invokes Gitlab CI, terraform, ansible, kubernetes helm charts.
Auto checking itself with unit and integration tests in autoredeployed staging env. Then it saves tested results to docker registry and asks for one button verificating click to be rereleased to prod.

I just go for drink or eat food. While all the stuff is happening.

And I am proud that all the infrastructure, backend and frontend I made on my own.

I don't need to remember how to Deploy it. It is all automatized

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

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 👍

TL;DR: At a house party, on my Phone, via shitty German mobile network using the GitLab website's plain text editor. Thanks to CI/CD my changes to the code were easily tested and deployed to the server.

It was for a college project and someone had a bug in his 600+ lines function that was nested like hell. At least 7 levels deep. Told him before I went to that party it's probably a redefined counter variable but he wouldn't have it as he was sure it was an error with the business logic. Told him to simplify the code then but he wouldn't do that either because "the code/logic is too complex to be simplified"... Yeah... what a dipshit...
Nonetheless I went to the party and He kept debugging. At some point he called me and asked me to help him the following day. Knowing that the code had to be fixed anyways I agreed.
I also knew I wouldn't be much of a help the next day due to side effects of the party, so I tried looking at this shitshow of a function on my phone. Oh did I mention it was PHP, yet? Yeah... About 30 minutes and a beer later I found the bug and of course it was a redefined counter variable... My respect for him as a dev was already crumbling but it died completely during that evening

That feeling when your CI pipeline builds.

Docker + GitLab CI/CD is overpowered 💓

Happiness is receiving this email :')

Normal peeps: I wasted time in that relationship
Me: I wasted time to fix "unable to access gitlab.com please check if you have access to the file" only to realize the site was down

whhooOOOOOOOOOOOOOSHSHHHHHHHHHHHMMMMMMMMMMMMMRRRRRRRRR

yepp, that's me running a GitLab pipeline on my PC and laptop (laptop is noisier, 'cuz PC has Noctua all over the case).

Turns out running a pipeline of ~200 jobs is quite network-demanding. To the levels where my DNS server in LAN is timing out. And streaming Netflix in parallel kills some of the gitlab runners.

daammnnnn.... I so don't want to pay for an EC2 or EKS at this stage :/

But then again, I don't remember when was the last time I heard fans whooshing in my lappy. I so got used to only hearing the coils whine in it...

Decisions, decisions

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

Hi everyone,
I got an hardware question. Im planning on getting a personal home server. I want to use it as a small gitlab server, continues integration, and the like for personal projects.
It has to be power efficient otherwise my dad will start crying.
I want it to be relatively cheap and running linux.
Ive got no clue what the best thing todo is. Should I get a prebuild one or build one myself.
For prebuild ones, what brands should I look at?
For a custom built what hardware do you recommend me?

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

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

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

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

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.

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.

Apart of the fact that WordPress itself is one big hack, my most creative hacky solution was making it (dev) environment friendly.

First, I created a DB pull and push tool in NodeJS (on TypeScript). Then, because WP is so clever and stores internal URLs in full length in the DB, I had to create a DB migrator (find & replace) and attached it to the DB pull task.
After this, of course WP still has its config in one file, so I used composer to install phpdotenv and filled the config with environment variables.
Bundled with some good ol' Gitlab CI/CD magic, the website is now 10% sanely developable.

It feels like having to shovel piles of shit, but with a golden shovel. Everything stinks as hell but at least there is a tiny bling to it, temporarily.

But in all seriousness: WordPress is a god damn fucking pile of tumors!

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

Gitlab ratelimiting the CI from downloading the code. 🤡

Non-devs will never understand the satisfaction when you see your tests run successfully on GitLab for the first time. (Last course at university and we are supposed to do TDD for the first time. )

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.

Finally managed to get gitlab ci working !

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 the ops team needs to go through a 5 step "protocol" over a couple of days, just to open a damn port in the firewall, so that our CI server can access the local GitLab server..
Seems like the migration of the last couple of projects from SVN to Git is going to take a little longer than I expected..

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.

Microsoft is buying GitHub?

Actually, that sounds great. A lot of people here are making it sound like this is the end of the world as we know it, but how do we know that they will make it awful? The Microsoft of today is different than the Microsoft of 2007. The purchase is simply a way to expand their enterprise offerings. I have experimented with Office365, and it is actually really useful. GitHub will be a way to expand that offering to software development companies.

Who knows? We may even get some kind of Azure CI service built directly into GitHub repos?

However, I see why some people are concerned. If they want to move to GitLab, I don't actually blame them a bit. I was already using it before it was cool!

The point of this rant is that we should give Microsoft a chance, and not jump ship right away.

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?

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.

You want to go home but pipeline fails. RIP

!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

This week has been a good week, work wise at least.

My projects are coming along, I’m getting a CI-CD server spun up so we can start making use of Gitlab runners for builds and testing (deployment is next on my list)

The boss gave good feed back in the gitlab issues I raised after a demo yesterday (new features, nothing major but it’s nice to have positive feed back)

My focus has very much been on the technical side of things, testing and de-bugging web services,

The boss is very keen for me to start implementing apis, starting with one of the apps I’m working on, so we can start writing apis for other systems which integrate with third parties.

I’m actually excited about my work again, and I think it shows, which is why they’re steering me this way.

I’m going to give it 6 months and then ask for a pay review, as I think my responsibilities have increased enough to warrant at least asking about a pay rise

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

What the hell kind of tool is Gitlab? I just want to automatically backmerge hotfixes from master to development. Even fucking Bitbucket had a checkbox to enable this. But not Gitlab, no, you better create a pipeline job in your already unreadable, overcrowded pipeline yml, but oh, the checked out repo in the pipeline is a detached head and you cant push with the user that checks out there. So what, just use a project acess token which revokes after a year breaking your task and then switch origin amd branch manually. But your token-user can't push to protected branches, so create a merge request instead, which requires approvals, making the automated step no longer automated.
But dont worry, you can just use the gitlab api to overwrite the approval rules for this MR so it requires 0 approvals. But to do so you must allow everyone to be able to overwrite approval rules therefor compromising security.
And so you made a feature that should effectively be a checkbox a 40+ line CI job which compromises your repo security.

which nuthead of an architect is responsible for the way gitlab (and its CI) is designed?

Someone here on devrant told me

You cant learn everything. Its impossible. Instead you just have to learn how to learn

Now i got flashback to this several weeks later

And i begin to realize as i learn gitlab ci/cd (i only know github cicd so far)

Wondered

How would i integrate this cicd with spring boot java backend app?
Or angular?
Or nextjs?
Or nodejs?

Then I realized

I dont have to fucking learn all of that individually

Instead i can just learn how gitlab cicd works once

And then apply that same concept with slight modifications to whatever tech stack is in use

Does this make sense?

Is this how i should think while i learn new tech?

Is this the proper way of learning how to learn?

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?

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.

Why do some employers make such a distinction between learning the tools at university and learning the same tools at the workplace?

Are they backward or old? Don't they know modern, high-quality universities have modern environments that are in fact real life?

Environments with acc-test-prod-dev with gitlab, ci/cd in Scrum teams and the works? Heck, at my uni we even worked at real companies, did internships there for months!

Come on.. to me this 'the tools you learned in school isn't the same experience as real life experience'. Right, these guys must be on some conservative backward model because there is in fact no difference.
I have worked both during my uni internship at a real company (in teams too) as well as irl at real companies and there is no difference, it's the same thing.
I don't care if I've learned to experience git + ReactJS etc during an internship through uni or at a workplace. It's all bureaucracy.

Sublime,
Docker,
git + gitlab + gitlab ci,
Terminator + fish

With that, im a coding machine ! ^^

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

I cant find 1 single normal Fucking tutorial explaining how to code FULL DEVOPS PIPELINE for deployment to AWS.

A pipeline that includes
- gitlab (ci cd)
- jenkins
- gradle
- sonarqube
- docker
- trivy
- update k8s manifest
- terraform
- argocd
- deploy to EKS
- send slack notification

How Fucking hard is it for someone to make a tutorial about this????? How am i supposed to learn how to code this pipeline????

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.

looking for suggestions for a self hosted CMS. I tried Ghost, and it looks real nice, but there's no option to have just 1 section be private, you can only make the whole thing private. I tried Drupal but honestly it's just way too complicated for what I need, and doesn't look very aesthetically pleasing.
basically, here's the features I'm looking for:
- ability to set privacy/access control on a per-page or per-section basis
- Markdown for content editing
- ability to use regular HTML when needed
- ability to upload content via an API (so that I can publish documentation via my gitlab CI)

What stack are you using to test your angular app and why?
We’re using Karma + Jasmine for writing unit tests, because it’s the default, and run them on GitLab CI in a Docker container. For UI testing we don’t use the default Protractor but Selenium, because we haven’t found a way to run Protractor tests with a dedicated webserver.

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.

I confess, I did a trolling today.

Kinda deployed staging in production today. Nothing happened, but the fact that it stayed there for an hour.

Why so long? Because gitlab would ratelimit the CI would and prevent it from executing for an hour straight and AWS was also a jockster by capping the download of the image to <1MB, so we couldn't even retag it

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?

How do you setup your ci/cd pipeline to work just like you want it, without having to create a quadrillion commits in your repository? Create a branch, make a quadrillion changes and squash them at the end? Is there a better way?