social.tchncs.de is one of the many independent Mastodon servers you can use to participate in the fediverse.
A friendly server from Germany – which tends to attract techy people, but welcomes everybody. This is one of the oldest Mastodon instances.

Administered by:

Server stats:

3.9K
active users

#ci

6 posts6 participants0 posts today

🔥 Keep your commits consistent!
🔥 forgejo-commit-path-rules v0.2.3 ensures your commit messages align with your file changes.

🧩 Enforce commit message and file path rules in your repo!

🦀 Written in Rust
⭐ Repo: https://codeberg.org/kemitix/forgejo-commit-path-rules
🎬 A ForgeJo Action/CLI Tool

✨ What's New:

- Coloured highlights in logging (supports --no-colour)
- all matching strategy for paths (default is any)
- Built in templates: docs, feature, tests and fixes

🛠 Usage:

- Define rules in .forgejo/commit-path-rules.toml
- Run via CLI or ForgeJo Action

Install:
cargo install forgejo-commit-path-rules

CLI Usage:
forgejo-commit-path-rules --workspace . --no-colour

Forgejo Action:

 jobs:
  validate:
   steps:
    - uses: actions/checkout@v3
      with:
        fetch-depth: 0
    - name: Run forgejo-commit-path-rules
      uses: kemitix/commit-path-rules@v0.2.3
      with:
        args: --verbose
Forgejo: Beyond coding. We Forge.forgejo-commit-path-rulesEnforce consistency between commit messages and file changes in your repository.

Some valuable advice on #CI - see below for the source:
---
After years of dealing with this (first Jenkins, then GitLab, then GitHub), my takeaway is:

* Write as much CI logic as possible in your own code. Does not really matter what you use (shell scripts, make, just, doit, mage, whatever) as long as it is proper, maintainable code.

* Invest time that your pipelines can run locally on a developer machine as well (as much as possible at least), otherwise testing/debugging pipelines becomes a nightmare.

* Avoid YAML as much as possible, period.

* Don't bind yourself to some fancy new VC-financed thing that will solve CI once and for all but needs to get monetized eventually (see: earthly, dagger, etc.)

* Always use your own runners, on-premise if possible

Source news.ycombinator.com/item?id=4

news.ycombinator.comAlready see people saying GitLab is better: yes it is, but it also sucks in diff... | Hacker News

You wanted Java 24? How adorable. 🤡

Fun fact: Ancient relics like Maven happily obey any Java version 🏺, but modern, cutting-edge tools. Gradle, AWS Lambda, and more require new releases just to function. 🔄 Because nothing says progress like mandatory dependencies. 🎭

Meanwhile, Kubernetes & Maven sit back, laughing. 😏
They do whatever they want. 🚀
They are independent. 🔓
Unlike you. 🫠

#DevLife #ProgrammingMemes #SoftwareEngineering #CodeHumor #programming #coding #Maven #Gradle #AWSLambda #DevOps #DependencyHell #CI/CD #BuildFails #JustDevThings #Relatable #WhyIsThisSoAccurate #EngineerCult

the other #rustlang thingy that's been cooking (and just passed a #ci run) is called #taggart.

it uses #tengri to pop up an interactive table to edit things, namely: the #id3 tags of music releases

its purpose? why, to make it easier to prepare a certain pile of content (that we've accumulated with a friend over the past, what, 6-7 years), for publication in a sovereign #faircamp instance! but none of it's well-tagged and existing interactive mediatag editors are ugh

codeberg.org/unspeaker/taggart

Codeberg.orgtaggarttaggart
Replied in thread

@metacosm Chez #Github, ils poussent à l'usage des #actions, des bouts de #CI réutilisables fournis par eux ou par la communauté. C'est possible aussi avec #Gitlab, facilement, mais je trouve qu'ils y poussent moins.

Chez #Gitlab, tu as des _jobs_ dans des _stages_, clairs, faciles, lisibles.
Chez #Github tu as des _steps_ dans des _jobs_ eux mêmes rangés dans des _worflows_ appelant potentiellement des _actions_, bordélique, foutraque.

Replied in thread

@fuchsiii @grumpygamer oftentimes said cores ain't even "dedicaded" but shared...

  • In the case of #CyberBunker they literally sold #Nehalem(-EX) hardware to customers (cross referenced by datasheets/specsheets and the fact they never updated the listings in 15+ years!)

"shared core VPS" are a very big mistake, espechally on Hosters like #Hetzner...

  • Ask me how I know!

So OFC said systems are overworked, espechally the convenience-based options where one just shoves on files and tells it to "bake it"...

  • OFC it shouldn't be the responsibility of a #GameDev to #DIY one's own #CI / #CD infrastructure, and I think given the size and complexity of said games it would be overkill to do so.

If feasible, just grab' yourself a decently performing PC/Server/Laptop you can chug in a closet, SSH/RDP onto and use it as "build servant" ("Rechenknecht") to run your builds and then sent a notification once done.

Gamedev MastodonRon Gilbert, Esq. (@grumpygamer@mastodon.gamedev.place)My desktop machine can fully rebuild the game in a few minutes. Azure takes 20-30 minutes. I'm sure many of these cloud services are using way over worked VMs. I'll deal with it because I don't want to set up and maintain my own machines for building. I have a game to make and CI build machines isn't where I want to spend any effort.