Inspiration meets innovation
StackTrack Blog
Dhruvakumar Jonnagaddala
Editorial Team
This guide provides practical guidance and examples for writing cross-platform Jenkins Pipelines that avoid sandbox approval issues and remain maintainable.
Software delivery slows when work stalls in queues, handoffs, and approvals. “Improve flow” is the heuristic that asks: How do we reduce friction from idea to running, observable software? This post gives a practical playbook: map your value stream, shrink batch sizes, cut WIP, eliminate handoffs, automate the path to production, and instrument the system so bottlenecks are obvious and fixable.
Optimize managing Jenkins software for performance, security, and efficiency with expert tips on configuration, resource allocation, plugin management, and more from a leading DevOps MSP.
Jenkins is an automation server written in "Java" and has an embedded servlet container/application server built-in "Jetty". Jetty is developed and maintained by eclipse.org. It Provides a web server and javax.servlet container. It has impressive support for HTTP/2, WebSocket, OSGi, JMX and many other integrations. It is also very simple to use Jetty alternatives like Apache Tomcat (or) Glassfish to host Jenkins.
We’re excited to announce that Servana has successfully completed our ISO/IEC 27001:2022 re-certification audit, conducted by the UKAS-accredited British Assessment Bureau, part of the Amtivo Group.
This update brings important security improvements, bug fixes, and performance enhancements designed to keep your environments running smoothly and securely.
Ideologically we are similar however in the case of Servana we probably offer more comprehensive support and our customers all get a platform that they can do whatever they like with which isn't something you get with a SaaS solution.
Kubernetes and the ecosystem surrounding it are all cloud-native; however, the cost of cloud-native platforms is really high and this leads to a dilemma can you reduce the complexity of your Kubernetes cluster by supplementing self-hosted cloud-native projects with cloud vendor services.
There's a lot of talk these days about DevOps culture. But what is it, really? And why does it matter? In this blog post, we'll explore the human side of DevOps and discuss why culture is so important in achieving success.
An organisation is like a machine. A machine is a system with components that work together; i.e (think integration and automation to achieve the desired outcome). When one part of the machine has a constraint, it can harm the entire system.
Heroku inspired me way back. As a cloud platform, Heroku enabled developers to build and deploy software with no-ops expertise.
You are currently working on a cloud-native application architecture and noticing that it seems to imply a micro-service architecture as well. However you yourself are not fully subscribed to a micro-service architecture for your application.
Micro-services is generally accepted as the only way to do cloud-native because the loosely coupling is considered a best practice for fault tolerant cloud architectures. However we believe its possible to reduce the capability of a monolith by extracting all of the non-business related functions and externalise them with cloud-native replacements
Over the past twenty years, we've tried very hard to learn from industrial processes to help make what we do in technology more efficient. Initially, the effort went into improving how we planned software projects.
DevOps practices are all about automation, cicd, security and monitoring. In this blog post, we will discuss the five key components of a successful DevOps practice!
As a DevOps Engineer I need to consider whether to use a hosted or self-hosted Jenkins for many projects. The questions for each project vary and the answers are not always straightforward.
If you are not a software developer then the best analogy for a bad developer experience would be the feelings of frustration you get when you are stuck in traffic because of roadwork. In your mind, you question the planning authorities thought process. They close a lane during peak hours and cause inexplicable congestion, impacting the lives of commuters that have work to do. Instead of working at night and finishing before the morning.
Software development moves fast, and software engineering teams continuously grapple with the speed of change. To support this, they need tools that are adaptable and extensible. Enter Jenkins a powerful and versatile opensource automation server that has revolutionised modern software teams' operations. In this blog post, we delve into the exciting world of software development with Jenkins Software, exploring its continuous integration and continuous delivery (i.e. CICD) capabilities and how it can transform your software development processes. We believe there is a place for Jenkins Software in modern software development teams.
Over the years we have put hundreds of hours of effort into performance bench-marking so that our customers get a consistent Jenkins developer experience - regardless of their workloads.
Our engineers and architects share practical advice on cloud infrastructure, DevOps automation, identity management, and security-first software delivery. Expect technical deep dives, platform comparisons, upgrade guides, and case studies from real customer projects.
Newsletter
Practical DevOps insights, infrastructure notes, and secure-by-design playbooks. No spam.