Packer
jenkins-bootstrap-shared
Our great sponsors
Packer | jenkins-bootstrap-shared | |
---|---|---|
65 | 6 | |
14,872 | 323 | |
0.5% | - | |
9.4 | 6.5 | |
5 days ago | 6 months ago | |
Go | Groovy | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Packer
-
The 2024 Web Hosting Report
To manage a VM, you can use something as simple as just manual actions over SSH, or can use tools like Ansible, Hashicorp's Packer and Terraform or other automations. For an app where there is minimal load and security/reliability concern, VMs are still a great option that provide a lot of value for the buck
-
Avoiding DevOps tool hell
Server templating: Using Packer has never been easier to create reusable server configurations in a platform-independent and documented manner.
-
How to create an iso image of a finished system
I'll give you hard, but rewarding and easy to modify(once you know what you're doing) way. Packer may be a thing you're looking for.
-
13.2 ZFS root AMIs in AWS
It is straightforward to build them with packer (I have built AMIs for 13.0 and 13.1, but 13.2 should be exactly the same). I've been meaning to write a blog post about it for a while, but have not gotten to it yet... In any case, what I am doing is using the EBS Surrogate Builder to start an instance running the official FreeBSD 13.2 image with an extra volume attached and run a script to create a zpool on the extra volume and bootstrap and configure FreeBSD 13.2-RELEASE on it. After that packer takes care of creating an AMI out of that extra volume, so you can use it... If you have any issues, let me know, and maybe I will finally get to writing that blog post...
-
DevOps Tooling Landscape
HashiCorp Packer is a tool for creating machine images for a variety of platforms, including AWS, Azure, and VMware. It allows you to define machine images as code and supports a wide range of configuration options.
-
auto-provisioning multiple raspberry pi's
Packer is a tool that can be used to build machine images. Basically, it takes a base image, runs a series of steps to provision that image, and then burns a new image. In my workplace we use it heavily to build AWS AMIs. But it has an ARM plugin that looks to be very very suitable for building customised Raspberry Pi images (my quick read of the doco there says it can go ahead and write the final image to an SD card for you too).
- How do hosting companies immediately create vm right after purchasing one?
-
Packer preseed file seems to not be read
Seems related to https://github.com/hashicorp/packer/issues/12118 But the workaround discribed in the comments doesn’t seems to work anymore
-
How to create AMI which also copies the user data?
I'd suggest using a tool like Packer to build a gold image based on your base AMI and all your changes. Then you'll have your own AMI you can launch new instances with.
-
Is migrate for compute engine M4CE suitable for migrating VMs (to GCP) which are part of auto scaling groups in AWS ?
Your assumption sounds correct. It sounds like you shouldn't focus on migrating specific instances, but instead migrating the template image used for autoscaling into GCP. I tend to prefer Packer for this job, or otherwise recreating the golden image directly on GCP.
jenkins-bootstrap-shared
-
Looking for a speaker on a panel on "how to make the most of Jenkins", pm me if interested
You can capture plugins and Jenkins versions using the script console to provision a second pristine Jenkins for additional testing like upgrade testing. I go deeper into this with complete immutable Jenkins infrastructure with jenkins-bootstrap-shared.
-
Steps to improve maintenance efforts
I recommend capturing your plugin versions. You can do it via maven or gradle. You could use the script console scripts on Jenkins. For testing upgrades you would need other means.
-
What is the best course/courses to learn pipeline as code with Groovy and Jenkins
Jenkins as immutable infra
-
How to safely upgrade jenkins plugin. What is the fail proof way to do it.
You can do this by script console yourself and use the community docker image. Alternately, you can try out jenkins-bootstrap-shared project I made which pulls Jenkins into a JKD8 container (I plan to upgrade it to OpenJKD11 since Jenkins now supports that).
-
How to use Jenkins the DevOps way in 2022
Here's how I have it scripted. (documentation : https://github.com/samrocketman/jenkins-bootstrap-shared/tree/main/scripts/upgrade )
What are some alternatives?
Vagrant - Vagrant is a tool for building and distributing development environments.
configuration-as-code-plugin - Jenkins Configuration as Code Plugin
helm - The Kubernetes Package Manager
jenkins-script-console-scripts - A repository of one-off script console scripts for Jenkins.
oVirt - oVirt website
blog - A personal technical blog. Full featured complete with automated peer review.
cloud-init-vmware-guestinfo - A cloud-init datasource for VMware vSphere's GuestInfo interface
groovy-guru - Groovy Intellisense for Visual Studio Code
kubernetes - Production-Grade Container Scheduling and Management
jervis - Self service Jenkins job generation using Jenkins Job DSL plugin groovy scripts. Reads .jervis.yml and generates a job in Jenkins.
QEMU - Official QEMU mirror. Please see https://www.qemu.org/contribute/ for how to submit changes to QEMU. Pull Requests are ignored. Please only use release tarballs from the QEMU website.
pipeline-library - Collection of custom steps and variables for our Jenkins instance(s)