Java4all’s gists

Java4all / gist:b97b3c1b42e9ea85283e300de89774b8

Created March 13, 2026 00:55

pattern

	pipeline:
	# ── Your actual service tag names ─────────────────────────────────────────
	# Must match exactly what appears before the colon in your log lines.
	# Log line: [2024-01-15T10:00:15.123z] service-exec: docker()
	# Tag: service-exec
	static_tags:
	- "service-exec" # ← replace with your real tag names
	- "service-deploy"
	- "service-test"

Java4all / gist:1ed47e79fd3a8bd49f93d32470eca26f

Created September 23, 2025 12:02

get_cert_venafi

	#!/usr/bin/env python3
	import yaml
	from pathlib import Path

	# Custom type to force PyYAML to use a literal block style (\|) for multiline strings
	class LiteralStr(str):
	pass

	def represent_literal_str(dumper, data):
	# Use the YAML string tag and force literal style

Java4all / gist:26ff36e2d5e4e3fffccc6d84fda71017

Created July 28, 2025 18:17

groovy call

	jenkins_create_token() {
	local user=$1 pass=$2 name=$3 jurl=$4

	# Get CSRF crumb
	local crumb
	crumb=$(curl -s -u "$user:$pass" \
	"$jurl/crumbIssuer/api/xml?xpath=concat(//crumbRequestField,\":\",//crumb)")

	# Create token
	curl -s -u "$user:$pass" \

Java4all / gist:5fc23bd19eaab85d71ed152508d35503

Last active July 14, 2025 14:10

aws examples

	# Instance ID
	INSTANCE_ID=$(curl -s http://169.254.169.254/latest/meta-data/instance-id)

	# Region
	REGION=$(curl -s http://169.254.169.254/latest/dynamic/instance-identity/document \
	\| jq -r '.region')

	# Fetch the "Name" tag
	NAME=$(aws ec2 describe-tags \
	--region $REGION \

Java4all / gist:404394ae83d77dedd554fc0293b97684

Last active July 11, 2025 20:22

Jenkins plugin check

	inal Version — jenkins_audit.py
	python
	#!/usr/bin/env python3
	import argparse
	import os
	import requests
	from packaging.version import Version, InvalidVersion
	from tabulate import tabulate

Java4all / gist:0c9206c687633c2030650d5f523eb99b

Last active July 12, 2025 00:45

Plugins dependency check

	# cli.py

	import argparse
	import os
	from main import analyze_plugin

	def main():
	parser = argparse.ArgumentParser(
	description="\U0001F9E9 Jenkins Plugin Compatibility Analyzer",
	formatter_class=argparse.ArgumentDefaultsHelpFormatter

Java4all / gist:dcb43edbd70729a3d4bf94b7cfb293e9

Last active July 11, 2025 08:55

	# Directory where plugin .hpi files will be stored
	# File: plugins.yaml

	# Define plugins with specific versions
	# Example YAML file to track plugin versions

	---
	plugins:
	- name: git
	version: 5.1.0

Java4all / gist:a81e337e10166cf713feb580072e1dee

Created July 11, 2025 08:03

groovy install pugin

	import jenkins.model.*
	import hudson.PluginWrapper
	import java.nio.file.*

	def pluginDir = new File(Jenkins.instance.rootDir, "plugins")
	def pluginList = [
	[name: "git", version: "5.2.1"],
	[name: "workflow-job", version: "2.40"]
	]

Java4all / gist:7c82c302b063f538031d736a86e43991

Last active July 9, 2025 12:53

Jenkins CB plugin managment over casc

	CloudBees CI (the enterprise version of Jenkins) uses Configuration as Code (CasC) bundles to manage plugins in a scalable, automated, and version-controlled way. Here's a detailed breakdown of how plugin management works within CasC bundles:

	A. What Is a CasC Bundle?
	A CasC bundle is a structured collection of YAML files that define the configuration of a CloudBees CI instance — including plugins, security, jobs, RBAC, and more. These bundles can be stored in Git and applied automatically to controllers via the CloudBees Operations Center.

	B. Plugin Management via CasC

	1. plugins.yaml File
	This file lists all plugins that should be installed on a controller. It supports both CAP (CloudBees Assurance Program) plugins and custom plugins.

Java4all / gist:f5032a0aac9c5aff1cea96ad9fa7ddd5

Created July 9, 2025 07:01

What is plugins in Jenkins?

	1. What Is a Plugin in Jenkins?
	A Jenkins plugin is a self-contained Java archive (.hpi or .jpi file) that extends Jenkins' core functionality. Plugins allow Jenkins to integrate with tools like Git, Docker, Maven, Slack, and even custom steps in your pipeline.
	They’re the backbone of Jenkins’ flexibility — you can add build triggers, post-build actions, UI elements, pipeline steps, and more.

	2. Where Are Plugins Stored?
	Jenkins stores plugins in the following location on the controller (master) node:

	$JENKINS_HOME/plugins/
	Each plugin is stored as a .jpi or .hpi file.