Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Why Small Teams Need CI/CD (and How to Set Up Your First Pipeline)

It is a common myth among small engineering teams that CI/CD pipelines are an enterprise luxury. When you only have two or three developers, setting up automated infrastructure can feel like unnecessary overhead. SSHing into a server to pull the latest Git commits seems faster and simpler—until it starts breaking. The reality of manual deployments quickly catches up with growing codebases:…

Many small development groups believe that Continuous Integration/Continuous Deployment (CI/CD) pipelines are unnecessary luxuries for their team size. However, manually deploying code can quickly become problematic as codebases expand. Breaking features often stem from developers forgetting to run tests locally before pushing their changes.

Releases become tense after-hours events where developers anxiously monitor server logs. Instead of deploying code frequently, teams sometimes wait weeks for a single release, making it challenging to identify and fix issues. CI/CD is not about managing vast numbers of services. It is about preserving coding energy by automating testing and deployment processes, resulting in predictable releases.

Small teams can implement a reliable CI/CD pipeline with these straightforward steps, avoiding overwhelming complexity.

Step 1: Test code on every push. The first crucial action is to automatically run your test suite every time code is pushed to the repository or a Pull Request is opened. GitHub Actions can manage this through a workflow file in the repository at .github/workflows/ci.yml. The following code snippet establishes a continuous integration workflow that triggers on pushes and pull requests to the main branch.

It uses the latest version of Ubuntu for the job and checks out the repository using the actions/checkout@v4 action. It also sets up Node.js version 20, installs dependencies using npm ci, and runs tests with npm run lint and npm test. This setup ensures that untested or broken code is identified immediately before it can affect production.

Step 2: Automate the deployment process. Once automated testing is in place, the next step is to eliminate manual server updates. After code merges into the main branch, an automated sequence should deploy the application to the hosting server securely. The following example continues the CI/CD pipeline by deploying code upon a successful test run to the main branch.

It uses the actions/checkout@v4 action to check out the repository and the appleboy/ssh-action@v1.0.3 to execute SSH commands securely through repository secrets for the server IP, username, and SSH private key. Once on the server, the script pulls the latest changes from the main branch and updates the codebase using Docker Compose, allowing for seamless automated deployments.

By automating testing and deployment, small teams can transform CI/CD from perceived overhead into essential infrastructure. Smaller, more frequent pushes make it easier to isolate bugs early, reduce release anxiety, and reclaim developer time for building revenue-generating features.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

Why Your Show HN Got No Upvotes (and What to Change Next Time)

A Show HN stalls for one of four reasons: readers can't try it, the title sounds like an ad, the body has no proof, or the maker isn't in the thread.

  • Readers can't try the product, leading to failed Show HN
  • Title seems like an advertisement, causing it to be skipped
  • Engage with the thread during the first hour to address concerns

Stirling PDF on Linux: pick the package, then verify the file

If you only need to edit a PDF on your own computer, you can start the Stirling PDF desktop app in Local Only mode. The first decision happens before launch: three Linux files in the 3.4.0 release…

  • Choose appropriate Linux package before launching Stirling PDF
  • Verify AppImage integrity with "sha256sum" before use
  • Confirm publisher and release page to avoid confusion

How to find 1688 suppliers in English (prices in USD, no Chinese, no login)

If you sell on Amazon, Shopify, Etsy or TikTok Shop, you have probably heard that the products you see on AliExpress or Alibaba often come from 1688.com , the Chinese domestic wholesale site where…

  • 1688.com is a Chinese wholesale site for factories selling directly to resellers.
  • 1688 Scraper tool extracts supplier data in English with USD prices and machine translation.
  • Tool filters suppliers by various criteria and offers affordable pay-per-result pricing.

A Japanese NLI checker for the space between generation and trust (sealed 0.961, zero-shot baselines 0.79–0.81)

TL;DR — We released ja-nli-v1, a small Japanese natural language inference model: given a premise and a hypothesis, it returns probabilities for entailment / neutral / contradiction.

  • ja-nli-v1 Japanese NLI model achieves 0.9612 accuracy on sealed test
  • Outperforms zero-shot baselines with 0.79–0.81 accuracy
  • Model trained on synthetic data from public-domain government documents

Change a screenshot to the required aspect ratio in the tab before you commit the hero

The docs call for a 16:9 hero, or the OG template is 1200×630. The file in the PR is a 4:3 laptop screenshot. The layout letterboxes it, or a later object-fit: cover chops off the toolbar you meant to…

  • Hero image must be 16:9 aspect ratio, 1200×630 pixels
  • Layout team treats aspect ratio as initial check, not CSS compensation
  • Use in-tab ratio tool to adjust image before committing

More from Saturday 21 November →