How to invoke a Jenkins build from Assembla on GIT push

1. Click New Job
2. Select Build a maven2/3 project
3. Then fill up these fields, the rest can be filled with any values
1. Source Code Management=GIT
2. Repository URL=Copy your URL from Assembla, must be in this format: [email protected]:YOUR_PROJECT.git
3. Advance->Name=origin
4. Branches to build=master
5. Build Triggers (checked)
1. Build whenever a SNAPSHOT dependency is built
2. Poll SCM - leave schedule field blank
6. Root pom=eg YOUR_PROJECT/pom.xml
7. Goal options=clean install OR install
8. Build Environment (checked)
1. SSH agent (select jenkins)
9. Post-build Actions
1. Deploy artifacts to artifactory
1. Select your artifactory server
2. Target release=libs-release-local
3. Target Snapshot=libs-snapshot-local
4. Deploy maven artifacts (checked)
5. Capture and publish build info (checked)

1. Create a new file in ~/.profile
1. In bash type: vi ~/.profile
2. Press :qw
3. Press: Enter
2. Paste the following lines (ssh-agent need to be set before invoking ssh-add):

# Note: ~/.ssh/environment should not be used, as it already has a different purpose in SSH.

env=~/.ssh/agent.env

# Note: Don't bother checking SSH_AGENT_PID. It's not used
#       by SSH itself, and it might even be incorrect
#       (for example, when using agent-forwarding over SSH).

agent_is_running() {
    if [ "$SSH_AUTH_SOCK" ]; then
        # ssh-add returns:
        #   0 = agent running, has keys
        #   1 = agent running, no keys
        #   2 = agent not running
        ssh-add -l >/dev/null 2>&1 || [ $? -eq 1 ]
    else
        false
    fi
}

agent_has_keys() {
    ssh-add -l >/dev/null 2>&1
}

agent_load_env() {
    . "$env" >/dev/null
}

agent_start() {
    (umask 077; ssh-agent >"$env")
    . "$env" >/dev/null
}

if ! agent_is_running; then
    agent_load_env
fi

if ! agent_is_running; then
    agent_start
    ssh-add
elif ! agent_has_keys; then
    ssh-add
fi

unset env

1. In Ubuntu call execute: curl http:///git/[email protected]:.git&branches=master
2. Go to jenkins job and look at Git Poll log, if something is wrong you will encounter Common Problem #1