alexbrjo

/*
  $ gradle server --include-build path/to/local-plugin
*/

plugins {
  id "org.jenkins-ci.jpi" version "0.22.0"
}

group = "org.jenkins-ci.plugins"

alexbrjo

plugins {...}
group = "org.jenkins-ci.plugins"
jenkinsplugin{...}

dependencies {
  compile 'org.jenkins-ci.lib:dry-run-lib:0.1'
  compileOnly 'org.jenkins-ci:symbol-annotation:1.5'
  jenkinsPlugins 'org.jenkins-ci.plugins:structs:1.5@jar'

  // 1. compilation

alexbrjo

Bitbucket Public API Testing Approach

Given you must check against the Public API and have Unit Test coverage over all methods (including API calls) on every run.

Criteria and considerations for bitbucket branch source plugin

• Ammount of work: quality is a priority with this plugin because a lot of people could be using this plugin, so ammount of work may be less important then having stable and efficient tests
• Unit Tests Offline: this plugin requires connectivity so it's reasonable to have tests that directly aganist the API. Offline tests would be useful if there was a local internet outage or Bitbucket server outages.

Strategy	Ammount of work	Unit Tests Offine

alexbrjo

#!/bin/bash
export PS1="\u[\[\e[1;31m\]\W\[\e[m\]]: "
export GIT_EDITOR=nano
export HGEDITOR=nano

# macOS program shortcuts
export DEFAULT_EDITOR="Sublime\ Text"
export DEFAULT_IDE="IntelliJ\ IDEA\ CE"

alias activity="open -a 'activity Monitor'"

alexbrjo

/**
 * pong.js v1.3.1
 * @author Alex Johnson (github.com/alexbrjo)
 */
var js = document.createElement("script"); 
js.type = "text/javascript";
js.src = 'http://ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js'; 
document.body.appendChild(js);

js.onload = function(){