Welcome to the documentation for Vagrant - the command line utility for managing the lifecycle of virtual machines. This website aims to document every feature of Vagrant from top-to-bottom, covering as much detail as possible.
Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s main goals are simplicity and ease-of-use. It also has a strong focus on security and reliability, featuring a minimum of moving parts, usage of OpenSSH for transport (with an accelerated socket mode and pull modes as alternatives), and a language that is designed around auditability by humans–even those not familiar with the program.
Welcome to the Job DSL API Viewer. This is the Job DSL reference, showing all available DSL methods. Use the navigation on the left to browse all methods starting from the methods available in the script context.
Rsync is a tool created as part of the Samba project that provides quick and incremental file transfer. It serves as a replacement for the scp and rcp tools. Rsync is a great way to upload files to a remote server, particularly when you need the remote machine to maintain a current mirror of the local files using minimal transfer, because rsync is very efficient in what it transfers over the network.
Welcome to the Job DSL API Viewer. This is the Job DSL reference, showing all available DSL methods. Use the navigation on the left to browse all methods starting from the methods available in the script context. The Job DSL API currently supports 204 Jenkins plugins. Click the on the top-right to filter methods by plugin.
So CloudCamp in London on the 6th July has the tagline “Serverless and the the death of devops”. OMG folks can you please stop doing this? I really like the CloudCamp folks – it’s a fun event and a really vibrant community, but the whole “death of devops” thing really grinds my gears. I blame Simon Wardley. 😉
Canary release is a technique to reduce the risk of introducing a new software version in production by slowly rolling out the change to a small subset of users before rolling it out to the entire infrastructure and making it available to everybody.
How do you measure DevOps success? Talk “metrics” for DevOps work or cloud-native infrastructures, and the conversation tends to revolve around familiar operational and productivity measures. Uptime. Transactions per second. Bugs fixed. Commits. Familiar categories of data that are straightforward to track and would seem to at least passingly correlate with some combination of efficiency, health of the environment, and development speed.
Introduction Groovy… is an agile and dynamic language for the Java Virtual Machine builds upon the strengths of Java but has additional power features inspired by languages like Python, Ruby and Smalltalk makes modern programming features available to Java developers with almost-zero learning curve provides the ability to statically type check and statically compile your code for robustness and performance supports Domain-Specific Languages and other compact syntax so your code becomes easy to read and maintain makes writing shell and build scripts easy with its powerful processing primitives, OO abilities and an Ant DSL increases developer productivity by reducing scaffolding code when developing web, GUI, database or console applications simplifies testing by supporting unit testing and mocking out-of-the-box seamlessly integrates with all existing Java classes and libraries compiles straight to Java bytecode so you can use it anywhere you can use Java
I've been working quite a bit with Docker these last few weeks and one thing that I found really annoying was all these unused containers and images taking up precious disk space. I wish Docker has a 'docker clean' command that would delete stopped containers and untagged images. Perhaps sometime in the near future as the project is very active. But for the time being, these commands should do the job.
DescriptionThis extension is able to create a MarkDown file format that contains all commit comments associated to the build.The file can be placed in any valid path, by default it will part of the artifacts.
You can share your packages anywhere you can share an image with badges. You can put a badge directly into your project's home page in Azure DevOps Services or in any Markdown/README file so readers can easily discover and consume your package.
The year was 2012 and operating a critical service at Netflix was laborious. Deployments felt like walking through wet sand. Canarying was devolving into verifying endurance (“nothing broke after one week of canarying, let’s push it”) rather than correct functionality. Researching issues felt like bouncing a rubber ball between teams, hard to catch the root cause and harder yet to stop from bouncing between one another. All of these were signs that changes were needed.
Over the past decade, engineering and technology organizations have converged on a common set of best practices for building and deploying cloud-native applications. These best practices include continuous delivery, containerization, and building observable systems.