4 stories
Your CI/CD pipeline builds fast, but does it build right? While your automated builds and deployments handle the mechanics of software delivery, catching code quality issues often falls to manual reviews, which, while hugely valuable, can sometimes miss more subtle problems.
Two documents appeared on 8 September. An arXiv paper measures what happens when a coding agent reads a poisoned repository under four permission models.
When a small change is made to an application, one thing usually follows: Run the regression suite. It makes sense. We want to make sure the change didn't break anything somewhere else. But recently I started thinking about something: Do we really need to run every test after every code change?
📋 👇 𝗙𝗿𝗲𝗲 𝗖𝗜/𝗖𝗗 𝗖𝗵𝗲𝗰𝗸𝗹𝗶𝘀𝘁 — 𝗬𝗼𝘂𝗿 𝗖𝗼𝗺𝗽𝗹𝗲𝘁𝗲 𝗜𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝗚𝘂𝗶𝗱𝗲 If you want to make sure your pipeline is actually production-ready, grab our CI/CD checklist — 👉 https://bit.ly/4pCqhF2 A developer writes some code on their laptop.
Showing 4 of 4 stories
You're all caught up.
Get the top AI news and tools straight to your inbox every week.
Weekly · AI news
Join 15,000+ AI enthusiasts
