These instructions assume you are using Minishift 1.0.1 or newer as your OpenShift installation.
You'll also need a wsk
binary in your $PATH
to interact with
OpenWhisk after it's deployed. Download the latest version for your OS
//usr/bin/env jbang "$0" "$@" ; exit $? | |
//DEPS info.picocli:picocli:4.2.0 | |
//DEPS org.eclipse.jgit:org.eclipse.jgit:5.8.1.202007141445-r | |
import org.eclipse.jgit.api.ListBranchCommand; | |
import org.eclipse.jgit.api.errors.GitAPIException; | |
import org.eclipse.jgit.lib.Ref; | |
import org.eclipse.jgit.lib.Repository; | |
import org.eclipse.jgit.revwalk.RevCommit; |
#!/bin/bash | |
_USER=${1:-$ACCESS_REDHAT_USERNAME} | |
_PASSWORD=${2:-$ACCESS_REDHAT_PASSWORD} | |
[ "" == "${_USER}" ] || [ "" == "${_PASSWORD}" ] && echo "${BASH_SOURCE[0]} <RedHat_access_user> <RedHat_access_password>" && exit 1 | |
oc create secret docker-registry access-red-hat --docker-server=registry.redhat.io --docker-username=${_USER} --docker-password=${_PASSWORD} --docker-email=user@redhat.com -n openshift --as system:admin | |
oc secrets link default access-red-hat --for=pull -n openshift --as system:admin |
podTemplate( | |
cloud: 'openshift', | |
label: 'mypod', | |
name: 'productization', | |
namespace: 'ci-cd', | |
containers: [ | |
containerTemplate( | |
name: 'jnlp', | |
image: 'openshift/jenkins-slave-maven-centos7', | |
workingDir: '/tmp', |
These instructions assume you are using Minishift 1.0.1 or newer as your OpenShift installation.
You'll also need a wsk
binary in your $PATH
to interact with
OpenWhisk after it's deployed. Download the latest version for your OS
#!groovy | |
import groovy.json.JsonOutput | |
import groovy.json.JsonSlurper | |
def label = "mypod-${UUID.randomUUID().toString()}" | |
podTemplate(label: label, yaml: """ | |
spec: | |
containers: | |
- name: mvn | |
image: maven:3.3.9-jdk-8 |
Go has excellent build tools that mitigate the need for using make
.
For example, go install
won't update the target unless it's older
than the source files.
However, a Makefile can be convenient for wrapping Go commands with
specific build targets that simplify usage on the command line.
Since most of the targets are "phony", it's up to you to weigh the
pros and cons of having a dependency on make
versus using a shell
script. For the simplicity of being able to specify targets that
can be chained and can take advantage of make
's chained targets,
# install Homebrew | |
$ su ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" | |
# show brew commands | |
$ brew help | |
# check current user | |
$ echo $(whoami) | |
# grant access to the folders |
SpringContextSingleton.getBean("staticAssetsFilter").setAggregateAndCompress(false) |
<!DOCTYPE html> | |
<html> | |
<head> | |
<style> | |
body.loading #splash { | |
opacity: 1; | |
} | |
#splash { | |
position: absolute; | |
top: 0; |