August 2025 Summaries
9 posts from Harness
Filter
Month:
Year:
Post Summaries
Back to Blog
Database deployment strategies, such as trunk-based, feature-based, and environment-based deployments, each offer unique benefits and challenges for managing schema changes in Database DevOps. Trunk-based deployment facilitates speed and simplicity by allowing developers to commit changes directly to the main branch, though it requires strong automated testing to mitigate risks. Feature-based deployment isolates changes by allowing separate branches for each feature, offering clear ownership and easier rollbacks, but can lead to merge conflicts and delayed integration. Environment-based deployment ensures safety and compliance by progressing changes through sequential environments, though it may slow down delivery. Harness Database DevOps, integrated with Liquibase OSS, supports all three strategies, providing automation, rollback safeguards, and governance to balance speed, safety, and collaboration in database schema management.
Aug 28, 2025
1,169 words in the original blog post.
Harness AI, developed by Jyoti Bansal, is a comprehensive platform designed to revolutionize the software delivery process by using automation and artificial intelligence to streamline steps beyond code generation, such as testing, security, deployment, and optimization. The platform aims to address the bottlenecks that slow down software delivery, which are often exacerbated by fragmented tools and processes, by unifying these stages into a cohesive system that enhances speed, reliability, and security. Harness AI leverages a Software Delivery Knowledge Graph to provide context-specific insights and automation, ensuring that tasks are completed efficiently and securely. The platform's capabilities have demonstrated significant improvements in key performance metrics such as test cycle times, downtime, and pipeline debugging time. Moreover, Harness AI is developed in collaboration with leading tech companies like Anthropic and OpenAI, ensuring that it's deeply integrated into the developer workflow. As part of its launch, Harness AI is now generally available to all Harness customers, marking a significant step forward in the evolution of software delivery.
Aug 26, 2025
1,135 words in the original blog post.
Organizations using Jenkins for CI/CD are encouraged to transition to modern AI DevOps platforms like Harness to reduce maintenance demands and enhance deployment efficiency. While Jenkins has been a longstanding tool in CI/CD, its complexity, resource consumption, and limitations in handling modern DevOps practices create operational challenges as the demand for faster, more reliable software releases increases. Harness offers a structured migration approach, leveraging AI to optimize pipelines, reduce technical debt, and improve security and compliance. Case studies such as Ancestry.com and Citigroup illustrate significant improvements in pipeline efficiency and cost reduction after migrating from Jenkins to Harness, underscoring the benefits of adopting a modern DevOps framework. This shift not only streamlines workflows but also prepares organizations for an AI-native software delivery environment, promising enhanced efficiency and developer satisfaction.
Aug 18, 2025
994 words in the original blog post.
AI is transforming Database DevOps by automating changelog creation, facilitating natural language inputs, and ensuring precise environment-specific deployments, addressing the longstanding lag behind application DevOps. This innovation helps overcome traditional challenges like manual script writing, slow feedback loops, and high-risk production rollouts, which are particularly problematic in AI-driven projects with frequent schema adjustments. Tools like the AI Changeset Generator exemplify this shift, enabling rapid, automated, and accurate database changes by leveraging natural language processing and predictive analytics. By integrating AI, teams can minimize human error, accelerate delivery times, and improve compliance, moving towards a future of autonomous database management. The AI Changeset Generator, for instance, acts as a continuous collaborator, allowing users to generate new changesets or augment existing ones with ease, thereby enhancing the efficiency, reliability, and safety of database change management processes.
Aug 13, 2025
1,466 words in the original blog post.
Open Policy Agent (OPA) is utilized in the Harness platform to enforce governance best practices in DevOps by providing fine-grained access control over software delivery processes. It uses Rego, a declarative language that allows users to write policies ensuring secure and compliant software releases. When an API request is made to Harness, the policy agent evaluates it against a set of policies, outputting a JSON object to determine if the request should be allowed or denied. The language operates by defining conditions that OPA matches against input data, enabling users to create complex rule sets for various scenarios like prohibiting HTTP calls during deployment or ensuring approval steps follow deployment stages. Rego's declarative nature allows it to evaluate conditions without explicitly programming each step, offering flexibility in policy creation for different use cases such as managing permissions and defining access levels. Users can also leverage Rego for defining and controlling variables, sets, arrays, and objects within their policies to enforce specific practices within their software delivery pipelines.
Aug 13, 2025
1,600 words in the original blog post.
Testing OpenTofu and Terraform modules before publishing is crucial to prevent outages, security risks, and widespread breaking changes across environments. By integrating real-world infrastructure testing into the CI/CD pipeline, teams can identify and address misconfigurations early, ensuring only trusted modules are promoted to the registry. The blog highlights the importance of module testing in achieving safe, reusable infrastructure code, emphasizing that without it, a single error can have devastating effects, as illustrated by a past incident where a misconfigured module wiped out an entire staging environment. Testing modules involves running integration pipelines that provision real test environments, allowing for the detection of missing variables, logic errors, and security misconfigurations before they are published. This practice not only ensures the reliability and security of modules but also encourages their reuse by providing confidence in their functionality. Additionally, the blog discusses advanced testing approaches, such as multi-environment testing and compliance validation, while acknowledging the initial overhead in setting up tests, which ultimately yields long-term benefits as the module ecosystem expands.
Aug 11, 2025
1,060 words in the original blog post.
Harness Chaos's Windows command probes enable real-time system health monitoring during chaos experiments, allowing users to test and validate the resilience of their Windows systems against unexpected failures. The process begins with setting up a Windows chaos infrastructure, followed by creating command probes that execute specific commands or PowerShell scripts to monitor critical system behaviors. These probes provide continuous validation during stress tests, such as CPU load experiments, to ensure the system remains responsive. By integrating these probes into chaos experiments, users can gain immediate feedback on how their infrastructure withstands stress and failure scenarios, enhancing confidence in system resilience. The setup involves a detailed installation process, configuration of probe properties, and attachment to chaos experiments to monitor system behavior, ultimately enabling users to build more robust Windows systems capable of handling unexpected challenges.
Aug 11, 2025
1,237 words in the original blog post.
Open source software deployment tools like Argo CD, Jenkins, Spinnaker, Flux, and Harness CD Community Edition offer various approaches to automating software deployment, each with unique strengths and weaknesses. While Jenkins is a well-established CI/CD tool with a vast plugin ecosystem, it struggles with modern declarative deployments. Spinnaker excels in multi-cloud environments but requires significant resources, making it more suitable for large enterprises. Flux and Argo CD emphasize GitOps for Kubernetes, with Flux focusing on simplicity and Argo CD providing user-friendly visualizations, though both require supplementary tools for comprehensive pipeline management. Harness CD Community Edition provides an open-source, pipeline-centric approach but reserves advanced features for its commercial version. The most effective deployment strategies often involve combining open-source tools with commercial solutions to leverage open-source flexibility while achieving the governance, orchestration, and verification capabilities required for modern software delivery.
Aug 07, 2025
1,381 words in the original blog post.
Harness has introduced significant updates in its Q2 feature releases, enhancing tools for Kubernetes, AWS, Terraform, and GitOps to empower engineering teams with more efficient and reliable delivery processes. These updates include declarative rollbacks, advanced GitOps filtering, canary Lambda deployments, and automatic EKS token refreshes, aimed at simplifying workflows, reducing risks, and accelerating feedback loops. The enhancements enable smoother continuous delivery by offering granular control over deployment steps, seamless integration with CI/CD pipelines, and improved artifact management with AWS S3. Additionally, updates in GitOps usability, pipeline execution, and trigger management improve user experience by offering features like fail-fast mode, enhanced notification templates, and project-level execution concurrency. These innovations are designed to enhance deployment confidence, enable rapid recovery from issues, and support dynamic configuration management across cloud environments, aligning with Harness’s mission to deliver faster, safer, and smarter software delivery tools.
Aug 05, 2025
1,577 words in the original blog post.