fjdk
  • Communities
  • Create Post
  • Create Community
  • heart
    Support Lemmy
  • search
    Search
  • Login
  • Sign Up
testeronious@lemmy.world to Programming@programming.dev · 1 year ago

Jenkins was invented b/c an engineer “got tired of incurring the wrath of his team every time his code broke the build.”

graphite.dev

external-link
message-square
27
fedilink
120
external-link

Jenkins was invented b/c an engineer “got tired of incurring the wrath of his team every time his code broke the build.”

graphite.dev

testeronious@lemmy.world to Programming@programming.dev · 1 year ago
message-square
27
fedilink
From the 80's to 2024 - how CI tests were invented and optimized
graphite.dev
external-link
While Google started automating its build tests in 2003, the engineering industry took longer to do the same. But automation was sorely needed: Software systems are growing larger and ever more complex… To make matters worse, new versions are pushed to users frequently, sometimes multiple times each day. This is a far cry from the world of shrink-wrapped software that saw updates only once or twice a year. The ability for humans to manually validate every behavior in a system has been unable to keep pace with the explosion of features and platforms in most software. - Software Engineering at Googlehttps://abseil.io/resources/swe-book/html/ch11.html#testing_overview Add author/source Sun Microsystem’s engineer, Kohsuke Kawaguchi, was key to ushering in the next era of testing. In 2004, he created “Hudson”https://community.jenkins.io/t/lets-thank-kohsuke-the-creator-of-jenkins/168 (later renamed to Jenkins in fun Oracle drama). At his day job, Kohsuke “got tired of incurring the wrath of his team every time his code broke the build.” He could have manually triggered tests before each code contribution, but instead, Kohsuke chose the classic engineering solution and created an automated program. The Hudson tool acted as a long-lived test server that could automatically verify each code change as it integrated into the codebase.
  • AggressivelyPassive@feddit.de
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    It can’t be that hard to create a test harness, so I can plug my own variables into the runner context.

    Even just an 80% solution would speed up development tremendously.

    • BatmanAoD@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Well, for GitHub Actions, there’s this: https://github.com/nektos/act

Programming@programming.dev

programming@programming.dev

Subscribe from Remote Instance

Create a post
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



Visibility: Public
globe

This community can be federated to other instances and be posted/commented in by their users.

  • 183 users / day
  • 1.1K users / week
  • 2.97K users / month
  • 7.16K users / 6 months
  • 1 local subscriber
  • 20.1K subscribers
  • 2.15K Posts
  • 30.6K Comments
  • Modlog
  • mods:
  • snowe@programming.dev
  • Ategon@programming.dev
  • MaungaHikoi@lemmy.nz
  • BE: 0.19.8
  • Modlog
  • Instances
  • Docs
  • Code
  • join-lemmy.org