Basic pipeline for js-ipfs

[victorb]

Works with branch https://github.com/ipfs/js-ipfs/tree/jenkins-integration

This job config contains the following:

• Set Github project to github.com/ipfs/js-ipfs
• Define BranchOrTag parameter for job, which is used to decide what to fetch from SCM
• Use Jenkinsfile from SCM source

Looks like this in js-ipfs

Dockerfile:

FROM node:6.9.4

WORKDIR /usr/src/app

COPY package.json /usr/src/app/package.json

RUN npm install

COPY . /usr/src/app

CMD ["npm", "run", "test:unit:node"]

Jenkinsfile:

node {
	def VERSION = "latest"
	stage("Checkout") {
		git branch: 'jenkins-integration', url: 'https://github.com/ipfs/js-ipfs.git'
		VERSION = sh(returnStdout: true, script: "git rev-parse HEAD").trim()
	}
	stage("Build") {
		sh "docker build -t quay.io/ipfs/js-ipfs:$VERSION ."
	}
	stage("Test") {
		sh "docker run quay.io/ipfs/js-ipfs:$VERSION"
	}
}

In the future, we'll have docker base-images for all JS projects + shared-libs for the Jenkinsfile so definition would be more similar to this:

node {
  runCheckout(),
  runBuild(),
  runTest()
}

Or even implicit Jenkinsfile if some rule matches.

[ghost]

Is UserRemoteConfig the part that fetches the Jenkinsfile? It's not very obvious that it always takes the Jenkinsfile from master :)

[victorb]

Yeah, "org.jenkinsci.plugins.workflow" defines how to execute the workflow, UserRemoteConfig defines that the jenkinsfile should be fetched from scm. Right now, it fetches it based on the revision you provide, I'll add a future task to make sure jenkinsfile is fetched from master unless job triggered from a maintainer, or something similar.

[ghost]

I think this LGTM 👍 UserRemoteConfig could be a bit more expressive