Skip to content

Instantly share code, notes, and snippets.

View whereismyjetpack's full-sized avatar

Dann whereismyjetpack

  • The Pennsylvania State University
View GitHub Profile

Keybase proof

I hereby claim:

  • I am whereismyjetpack on github.
  • I am dannbohn (https://keybase.io/dannbohn) on keybase.
  • I have a public key ASCA7VrRidqCy8IeDyEjzGUwqSI-St7tkMK7GNA6Stf3zAo

To claim this, I am signing this object:

@whereismyjetpack
whereismyjetpack / ReleaseViaJGitFlow.md
Created December 3, 2017 12:54 — forked from lemiorhan/ReleaseViaJGitFlow.md
How to make a release with Git and Maven via JGitFlow

How to make a release with Git and Maven via JGitFlow

Imagine that you are versioning your sourcecode in git and building your code via maven. You need to make releases before deploying to production regularly. What should be the strategy we need to follow for releasing?

I've used maven-release-plugin for years to make releases. It worked perfectly with maven and svn, but we started to face problems when we migrated our code to git and to make releases on git.

After checking the literature, we decided to use JGit-Flow which is a maven plugin based on and is a replacement for the maven-release-plugin enabling support for git-flow style releases via maven.

I do not want to explain the details much because there are many great posts explaining all.

@whereismyjetpack
whereismyjetpack / ReleaseViaJGitFlow.md
Created December 3, 2017 12:54 — forked from lemiorhan/ReleaseViaJGitFlow.md
How to make a release with Git and Maven via JGitFlow

How to make a release with Git and Maven via JGitFlow

Imagine that you are versioning your sourcecode in git and building your code via maven. You need to make releases before deploying to production regularly. What should be the strategy we need to follow for releasing?

I've used maven-release-plugin for years to make releases. It worked perfectly with maven and svn, but we started to face problems when we migrated our code to git and to make releases on git.

After checking the literature, we decided to use JGit-Flow which is a maven plugin based on and is a replacement for the maven-release-plugin enabling support for git-flow style releases via maven.

I do not want to explain the details much because there are many great posts explaining all.

build:
stage: build
script:
- docker login -u $DOCKER_USER -p $DOCKER_TOKEN $DOCKER_REGISTRY
- docker build -t $DOCKER_REGISTRY/$REGISTRY_NAMESPACE/$CI_PROJECT_NAME:$CI_COMMIT_SHA .
- docker push $DOCKER_REGISTRY/$REGISTRY_NAMESPACE/$CI_PROJECT_NAME
cache:
untracked: false
paths: []
# frozen_string_literal: true
require 'zip'
class SolrConfigurator
def zip_file
File.open(tempfile)
end
Sidekiq::Queue.all.each do |q|
OkComputer::Registry.register "sidekiq_#{q.name}", OkComputer::SidekiqLatencyCheck.new("#{q.name}")
end
class QueueLatencyCheck < OkComputer::Check
def check
@failures = nil
@message = Hash.new
queues = Sidekiq::Queue.all
binding.pry
queues.each do |q|
OkComputer::Registry.register "sidekiq_#{q.name}", OkComputer::SidekiqLatencyCheck.new("#{q.name}")
# latency(q.name)
end
@whereismyjetpack
whereismyjetpack / solr_password.py
Created October 28, 2022 18:01
Ansible solr_password lookup
# Inspired by https://gist.github.com/eribeiro/aaa3f7e62750aa8a5799dde035179010
from __future__ import absolute_import, division, print_function
__metaclass__ = type
DOCUMENTATION = """
name: solr_password
short_description: Set Solr Authentication String for use in security.json
options:
_terms: