×
There are potential pitfalls associated with each approach to scaling Jenkins, but with careful planning, many of them can be avoided or managed.
Missing: android | Show results with:android
This first approach involves deploying a single Jenkins master with multiple Jenkins agents that teams use to run their build workloads (typically on ...
Sizing a Jenkins environment depends on a number of factors, which makes it a very inexact science. Achieving an optimal configuration requires some ...
Missing: availability | Show results with:availability
Refactoring a Jenkins plugin for compatibility with Pipeline jobs. This is a guest post by Chris Price. Chris is a software engineer at Puppet, ...
Missing: high | Show results with:high
The following plugin provides functionality available through Pipeline-compatible steps. ... This option works in addition to the regular thresholds (e.g. if "x" ...
Missing: android scalability
The following plugin provides functionality available through Pipeline-compatible steps. ... Consider errors and warnings with high severity ... Note that this ...
Missing: android scalability
The /whoAmI/ URL allows determining who the current user is. It is available to users without permissions to troubleshoot permissions issues. /wsagents/ handles ...
Missing: android scalability
The following plugin provides functionality available through Pipeline-compatible steps. ... For added security, Veracode highly ... Selecting this checkbox creates ...
Missing: android scalability
A few weeks ago, my colleague Brian Dawson and I were invited to present on Scaling Jenkins for Continuous Delivery with Microsoft Azure in Microsoft's Reactor ...
Missing: high | Show results with:high
Fix a runtime error when viewing the build time trend on Java 17. (issue 68215); Provide supporting infrastructure to enable Pipeline: Groovy to work around a ...