Tested against the WebKit git repo by entering the repo with 1 file dirty.
git diff --quiet --ignore-submodules HEAD # Will tell if there are any uncomitted changes, staged or not.
0.6 sec
git diff-index --quiet HEAD # Only tracked
2 sec
package.sh lives at the same level as your pom. Honestly you could put it all inline with the exec plugin.
The reason I don't is it's easier to edit the shell script. It doesn't HAVE to live at the same level as the pom but that's in the search path for the exec plugin.
I also wanted to have the conditional logic for SNAPSHOT builds (appending the timestamp). There are obviously many ways the shell script could blow up at this point.
The rest of this pom actually does some stuff to package up a copy of our component with a customized distribution of Jetty8 similar to what the hightide distribution does. We basically vendor the container with the application.
The only thing missing that I can see right now is attaching the generated deb artifact and pushing it to artifactory. Well...that and making sure it doesn't blow up on me for stupid reasons.
| # commands to ignore | |
| cmdignore=(htop tmux top vim) | |
| # end and compare timer, notify-send if needed | |
| function notifyosd-precmd() { | |
| retval=$? | |
| if [[ ${cmdignore[(r)$cmd_basename]} == $cmd_basename ]]; then | |
| return | |
| else | |
| if [ ! -z "$cmd" ]; then |
A lot of times you are developing a web application on your own laptop or home computer and would like to demo it to the public. Most of those times you are behind a router/firewall and you don't have a public IP address. Instead of configuring routers (often not possible), this solution gives you a public URL that's reverse tunnelled via ssh to your laptop.
Because of the relaxation of the sshd setup, it's best used on a dedicated virtual machine just for this (an Amazon micro instance for example).
| #!/usr/bin/env bash | |
| # Runs a command wrapped in btrfs snapper pre-post snapshots. | |
| # Usage: $ snp <commands> | |
| # e.g.: $ snp pacman -Syyu | |
| # Requirements: snapper (https://wiki.archlinux.org/title/snapper) | |
| # The latest version of this script is hosted at https://gist.github.com/erikw/5229436 | |
| log_path="/var/local/log/snp" | |
| date=$(date "+%Y-%m-%d-%H%M%S") | |
| log_file="${log_path}/snp_${date}.log" |
| #!/bin/bash | |
| # Dashing service | |
| # Add this file to /etc/init.d/ | |
| # $ sudo cp dashboard /etc/init.d/ | |
| # Update variables DASHING_DIR, GEM_HOME, & PATH to suit your installation | |
| # $ sudo nano /etc/init.d/dashboard | |
| # Make executable | |
| # $ sudo chmod 755 /etc/init.d/dashboard | |
| # Update rc.d | |
| # $ sudo update-rc.d dashboard defaults |
Dashing widget to display a Jenkins build status and build progress
The widget is based on the meter-widget which is default in the Dashing installation
The widget can also see the progress of a "pre-build", i.e if you have a job triggering the actual build you want to define, you can configure this job in the jenkins_build.rb as a prebuild.
For more information, please see Coding Like a tosser
Simple Dashing widget to countdown until a certain moment. Flashes the widget when finished.
##Usage
To use this widget, copy countdown.html, countdown.coffee, and countdown.scss into the /widgets/countdown directory.
To include the widget in a dashboard, add the following snippet to the dashboard layout file:
