#droneci — Public Fediverse posts

On this Saturday that kind of feels like a Sunday, it was time for a little spring cleaning. Taking the time to fix some internal ci flows and tooling. Now no more #DroneCI but only #giteaactions Actions for my internal services. #springcleaning

On this Saturday that kind of feels like a Sunday, it was time for a little spring cleaning. Taking the time to fix some internal ci flows and tooling. Now no more #DroneCI but only #giteaactions Actions for my internal services. #springcleaning

Over the last few days I've gotten a new #GitLab instance setup along with #DroneCI. I think I'm back in business there. I wish I could keep using my #GitHubEnterprise instance but I don't like how I can't keep it open and have to lock it down so much.

Over the last few days I've gotten a new #GitLab instance setup along with #DroneCI. I think I'm back in business there. I wish I could keep using my #GitHubEnterprise instance but I don't like how I can't keep it open and have to lock it down so much.

I'm trying to use #DroneCI host volume. The repo has to be set to trusted. Problem is, my DroneCI settings doesn't have that option...

I'm trying to use #DroneCI host volume. The repo has to be set to trusted. Problem is, my DroneCI settings doesn't have that option...

I'm trying to use #DroneCI host volume. The repo has to be set to trusted. Problem is, my DroneCI settings doesn't have that option...

I'm trying to use #DroneCI host volume. The repo has to be set to trusted. Problem is, my DroneCI settings doesn't have that option...

I'm trying to use #DroneCI host volume. The repo has to be set to trusted. Problem is, my DroneCI settings doesn't have that option...

Yay, no more MissingRegion error! So, I'm sad to see I had to revert/nuke my entire #DroneCI setup after only briefly trying plugging in MinIO.

So I guess just because you can comment something back out in docker-compose, doesn't mean there's no linger side effects.

Yay, no more MissingRegion error! So, I'm sad to see I had to revert/nuke my entire #DroneCI setup after only briefly trying plugging in MinIO.

So I guess just because you can comment something back out in docker-compose, doesn't mean there's no linger side effects.

Yay, no more MissingRegion error! So, I'm sad to see I had to revert/nuke my entire #DroneCI setup after only briefly trying plugging in MinIO.

So I guess just because you can comment something back out in docker-compose, doesn't mean there's no linger side effects.

Yay, no more MissingRegion error! So, I'm sad to see I had to revert/nuke my entire #DroneCI setup after only briefly trying plugging in MinIO.

So I guess just because you can comment something back out in docker-compose, doesn't mean there's no linger side effects.

I'm trying to wrap my head around how to get my #docker #DroneCI (docker) pipeline to publish my final builds to the machine it's on.

Ideally I'd like it to do a direct transfer (scp or rsync) without having to hit the LAN.

Idk if the pipeline builds exist on the same docker network as the host image; are they allowed to communicate directly? If so then does that mean the network that Drone is in, that the pipeline image can communicate with another hosted service?

I'm trying to wrap my head around how to get my #docker #DroneCI (docker) pipeline to publish my final builds to the machine it's on.

Ideally I'd like it to do a direct transfer (scp or rsync) without having to hit the LAN.

Idk if the pipeline builds exist on the same docker network as the host image; are they allowed to communicate directly? If so then does that mean the network that Drone is in, that the pipeline image can communicate with another hosted service?

I'm trying to wrap my head around how to get my #docker #DroneCI (docker) pipeline to publish my final builds to the machine it's on.

Ideally I'd like it to do a direct transfer (scp or rsync) without having to hit the LAN.

Idk if the pipeline builds exist on the same docker network as the host image; are they allowed to communicate directly? If so then does that mean the network that Drone is in, that the pipeline image can communicate with another hosted service?

I'm trying to wrap my head around how to get my #docker #DroneCI (docker) pipeline to publish my final builds to the machine it's on.

Ideally I'd like it to do a direct transfer (scp or rsync) without having to hit the LAN.

Idk if the pipeline builds exist on the same docker network as the host image; are they allowed to communicate directly? If so then does that mean the network that Drone is in, that the pipeline image can communicate with another hosted service?

I'm trying to wrap my head around how to get my #docker #DroneCI (docker) pipeline to publish my final builds to the machine it's on.

Ideally I'd like it to do a direct transfer (scp or rsync) without having to hit the LAN.

Idk if the pipeline builds exist on the same docker network as the host image; are they allowed to communicate directly? If so then does that mean the network that Drone is in, that the pipeline image can communicate with another hosted service?

Just published: New #Git repository from @harnessio faces stiff competition from @github and @gitlab along with corporate #opensource doubts. #droneci #devops https://www.techtarget.com/searchsoftwarequality/news/366552837/New-Git-repository-faces-corporate-open-source-doubts

Just published: New #Git repository from @harnessio faces stiff competition from @github and @gitlab along with corporate #opensource doubts. #droneci #devops https://www.techtarget.com/searchsoftwarequality/news/366552837/New-Git-repository-faces-corporate-open-source-doubts

Just published: New #Git repository from @harnessio faces stiff competition from @github and @gitlab along with corporate #opensource doubts. #droneci #devops https://www.techtarget.com/searchsoftwarequality/news/366552837/New-Git-repository-faces-corporate-open-source-doubts

Just published: New #Git repository from @harnessio faces stiff competition from @github and @gitlab along with corporate #opensource doubts. #droneci #devops https://www.techtarget.com/searchsoftwarequality/news/366552837/New-Git-repository-faces-corporate-open-source-doubts

Just published: New #Git repository from @harnessio faces stiff competition from @github and @gitlab along with corporate #opensource doubts. #droneci #devops https://www.techtarget.com/searchsoftwarequality/news/366552837/New-Git-repository-faces-corporate-open-source-doubts

Von #DroneCI auf #WoodpeckerCI migriert ✅

@drq I use #DroneCI to build and deploy. I'm curious how much #Gitea Actions can replace it. Already upgrading my instance, I'll try this around in the next couple of weeks.

@drq I use #DroneCI to build and deploy. I'm curious how much #Gitea Actions can replace it. Already upgrading my instance, I'll try this around in the next couple of weeks.

@drq I use #DroneCI to build and deploy. I'm curious how much #Gitea Actions can replace it. Already upgrading my instance, I'll try this around in the next couple of weeks.

@drq I use #DroneCI to build and deploy. I'm curious how much #Gitea Actions can replace it. Already upgrading my instance, I'll try this around in the next couple of weeks.

@drq I use #DroneCI to build and deploy. I'm curious how much #Gitea Actions can replace it. Already upgrading my instance, I'll try this around in the next couple of weeks.

@mmeier

#homelab #droneci
Usually they call that "Any" but it's silly they don't include that option :thonking:

@mmeier

#homelab #droneci
Usually they call that "Any" but it's silly they don't include that option :thonking:

@mmeier

#homelab #droneci
Usually they call that "Any" but it's silly they don't include that option :thonking:

@mmeier

#homelab #droneci
Usually they call that "Any" but it's silly they don't include that option :thonking:

What's still a bit frustrating about the entire thing: There was absolutely nothing in the Drone logs to tell me that the new jobs simply didn't have anywhere to run.

So now, all my pipelines have been switched to arm64 and Drone CI runners have been restricted to arm64.

Because of course there is no "I don't care about the runners architecture" option.

#HomeLab #DroneCI

What's still a bit frustrating about the entire thing: There was absolutely nothing in the Drone logs to tell me that the new jobs simply didn't have anywhere to run.

So now, all my pipelines have been switched to arm64 and Drone CI runners have been restricted to arm64.

Because of course there is no "I don't care about the runners architecture" option.

#HomeLab #DroneCI

What's still a bit frustrating about the entire thing: There was absolutely nothing in the Drone logs to tell me that the new jobs simply didn't have anywhere to run.

So now, all my pipelines have been switched to arm64 and Drone CI runners have been restricted to arm64.

Because of course there is no "I don't care about the runners architecture" option.

#HomeLab #DroneCI

What's still a bit frustrating about the entire thing: There was absolutely nothing in the Drone logs to tell me that the new jobs simply didn't have anywhere to run.

So now, all my pipelines have been switched to arm64 and Drone CI runners have been restricted to arm64.

Because of course there is no "I don't care about the runners architecture" option.

#HomeLab #DroneCI

I think the next project will be switching my CI from Drone CI to Woodpecker.

I changed my setup slightly to a more distributed setup with multiple runners. And now it looks like the jobs don't get distributed. No problem, error is probably in my configs.

But Drone's logs show me exactly nothing. Their "Debug" logs are a sad joke.

#HomeLab #DroneCI #Woodpecker

I think the next project will be switching my CI from Drone CI to Woodpecker.

I changed my setup slightly to a more distributed setup with multiple runners. And now it looks like the jobs don't get distributed. No problem, error is probably in my configs.

But Drone's logs show me exactly nothing. Their "Debug" logs are a sad joke.

#HomeLab #DroneCI #Woodpecker

I think the next project will be switching my CI from Drone CI to Woodpecker.

I changed my setup slightly to a more distributed setup with multiple runners. And now it looks like the jobs don't get distributed. No problem, error is probably in my configs.

But Drone's logs show me exactly nothing. Their "Debug" logs are a sad joke.

#HomeLab #DroneCI #Woodpecker

I think the next project will be switching my CI from Drone CI to Woodpecker.

I changed my setup slightly to a more distributed setup with multiple runners. And now it looks like the jobs don't get distributed. No problem, error is probably in my configs.

But Drone's logs show me exactly nothing. Their "Debug" logs are a sad joke.

#HomeLab #DroneCI #Woodpecker

I think the next project will be switching my CI from Drone CI to Woodpecker.

I changed my setup slightly to a more distributed setup with multiple runners. And now it looks like the jobs don't get distributed. No problem, error is probably in my configs.

But Drone's logs show me exactly nothing. Their "Debug" logs are a sad joke.

#HomeLab #DroneCI #Woodpecker

I am going to attempt to setup #DroneCI for my #GodotEngine project with a #Gitea integration. I hope it goes well! 🤞#indiedev

I am going to attempt to setup #DroneCI for my #GodotEngine project with a #Gitea integration. I hope it goes well! 🤞#indiedev

I am going to attempt to setup #DroneCI for my #GodotEngine project with a #Gitea integration. I hope it goes well! 🤞#indiedev

I am going to attempt to setup #DroneCI for my #GodotEngine project with a #Gitea integration. I hope it goes well! 🤞#indiedev

I am going to attempt to setup #DroneCI for my #GodotEngine project with a #Gitea integration. I hope it goes well! 🤞#indiedev

Flaky tests are a problem found in almost every codebase. By definition, a flaky test is a test that both succeeds and fails without any changes to the code. Learn how we reduced flaky tests using #Grafana, #Prometheus, Grafana #Loki, and #DroneCI
https://grafana.com/blog/2023/02/09/how-we-reduced-flaky-tests-using-grafana-prometheus-grafana-loki-and-drone-ci/?mdm=social

Flaky tests are a problem found in almost every codebase. By definition, a flaky test is a test that both succeeds and fails without any changes to the code. Learn how we reduced flaky tests using #Grafana, #Prometheus, Grafana #Loki, and #DroneCI
https://grafana.com/blog/2023/02/09/how-we-reduced-flaky-tests-using-grafana-prometheus-grafana-loki-and-drone-ci/?mdm=social

Flaky tests are a problem found in almost every codebase. By definition, a flaky test is a test that both succeeds and fails without any changes to the code. Learn how we reduced flaky tests using #Grafana, #Prometheus, Grafana #Loki, and #DroneCI
https://grafana.com/blog/2023/02/09/how-we-reduced-flaky-tests-using-grafana-prometheus-grafana-loki-and-drone-ci/?mdm=social

Flaky tests are a problem found in almost every codebase. By definition, a flaky test is a test that both succeeds and fails without any changes to the code. Learn how we reduced flaky tests using #Grafana, #Prometheus, Grafana #Loki, and #DroneCI
https://grafana.com/blog/2023/02/09/how-we-reduced-flaky-tests-using-grafana-prometheus-grafana-loki-and-drone-ci/?mdm=social

Flaky tests are a problem found in almost every codebase. By definition, a flaky test is a test that both succeeds and fails without any changes to the code. Learn how we reduced flaky tests using #Grafana, #Prometheus, Grafana #Loki, and #DroneCI
https://grafana.com/blog/2023/02/09/how-we-reduced-flaky-tests-using-grafana-prometheus-grafana-loki-and-drone-ci/?mdm=social

Playing around with #DroneCI git pipelines are so cool and fun y'all

@shane Of course #nix and #nixos are way smaller and mature, that is out of question. For the CI I have been running #droneCI quite successfully, but really any CI that supports host-runners can be used with a bit of fiddling.

@shane Of course #nix and #nixos are way smaller and mature, that is out of question. For the CI I have been running #droneCI quite successfully, but really any CI that supports host-runners can be used with a bit of fiddling.

@shane Of course #nix and #nixos are way smaller and mature, that is out of question. For the CI I have been running #droneCI quite successfully, but really any CI that supports host-runners can be used with a bit of fiddling.

@andreS CI/CD nutzen wir bei der Arbeit via #Gitlab. Das ist schnell aufgesetzt. Privat bin ich ein Fan von #droneci. Etwas weniger sperrig.
Was ist denn euer konkretes Problem mit CI/CD?

@andreS CI/CD nutzen wir bei der Arbeit via #Gitlab. Das ist schnell aufgesetzt. Privat bin ich ein Fan von #droneci. Etwas weniger sperrig.
Was ist denn euer konkretes Problem mit CI/CD?

Stumbled over #k3d today. Pretty handy to spin-up a #kubernetes for CI environments like #droneci or #woodpecker to run automated deployment tests #devops #sysadmin

Nice if the metrics endpoint of a service is not working anymore (well it works but needs 5+ minutes to finish) because the metrics are calculated by real-time DB queries.

Thanks to a not existing garbage collection for the used tables, they have reached a size of more than 10 million lines now....

#sysadmin #droneci #monitoring