Skip to content

Instantly share code, notes, and snippets.

View planforfailure's full-sized avatar
🏠
Working from home

planforfailure

🏠
Working from home
View GitHub Profile
@ngpestelos
ngpestelos / remove-docker-containers.md
Last active August 20, 2024 19:34
How to remove unused Docker containers and images

May 8, 2018

I wrote this four years ago, so instead use this command:

$ docker rmi $(docker images -q -f dangling=true)
@merikan
merikan / Jenkinsfile
Last active April 16, 2025 07:30
Some Jenkinsfile examples
Some Jenkinsfile examples
@lemajes
lemajes / ansible-delete-wildcard.yml
Last active September 27, 2024 10:20
[Ansible Delete Folders And Files Wildcard] Delete folders and files wildcard method with Ansible #script #yml #ansible #delete #wildcard
- hosts: all
tasks:
- name: Ansible delete file wildcard
find:
paths: /etc/wild_card/example
patterns: "^he.*.txt"
use_regex: true
register: wildcard_files_to_delete
- name: Ansible remove file wildcard
@VincentLoy
VincentLoy / error.txt
Last active June 16, 2024 08:41
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743
Err:19 https://packages.sury.org/php stretch InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743
Ign:26 http://ftp.au.debian.org/debian stretch InRelease
Hit:27 http://ftp.au.debian.org/debian stretch Release
Fetched 456 kB in 2s (189 kB/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.sury.org/php stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743
W: Failed to fetch https://packages.sury.org/php/dists/stretch/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743
W: Some index files failed to download. They have been ignored, or old ones used instead.

Pipeline version 1

pipeline {
  agent { label "linux" }
  stages {
    stage('Hello') {
      steps {
        sh '''
          aws --version
        '''
@wtfred
wtfred / GitlabCiAnsibleGalaxyGitRepository.md
Last active January 10, 2024 19:15
Using same requirements.yml in gitlab-ci with roles in private git repositories, using tokens

I had a problem using ansible / ansible-galaxy to install roles from a requirements.yml file.

My roles are listed like this:

- src: git+ssh://[email protected]/ansible/roles/my_role.git
  version: "v1.0.0"

This is working fine when running ansible-galaxy install -r requirements.yml on a host which have permission on the role repository (with a pair of ssh keys)

In Gitlab you can't define a "Deploy key" at group level, so i needed to use a token instead.

vSphere 6 Enterprise Plus:
1C20K-4Z214-H84U1-T92EP-92838
1A2JU-DEH12-48460-CT956-AC84D
MC28R-4L006-484D1-VV8NK-C7R58
5C6TK-4C39J-48E00-PH0XH-828Q4
4A4X0-69HE3-M8548-6L1QK-1Y240
vSphere with Operations Management 6 Enterprise:
4Y2NU-4Z301-085C8-M18EP-2K8M8
1Y48R-0EJEK-084R0-GK9XM-23R52