These are used to build deb packages with our jenkins server

uses jenkins-debian-glue and jenkins blue ocean (jenkinsfile)

Use the Jenkinsfile here as reference

Builds will be automatically built and published to http://repo.ubports.com/

Branch name will decide where the builds land in our repo

http://repo.ubports.com/dists/[branch name]

• vivid lands in http://repo.ubports.com/dists/vivid/

• vivid-dev lands in http://repo.ubports.com/dists/vivid-dev/

• xenial lands in http://repo.ubports.com/dists/xenial/

• xenial-dev lands in http://repo.ubports.com/dists/xenial-dev/

in file /etc/apt/sources.list add

deb http://repo.ubports.com/ [branch name] main

deb http://repo.ubports.com/ vivid main

• Add Jenkinsfile to root of project (find jenkinsfile in this repo)
• Login to ci.ubports.com
• Press Open Blue Ocean
• Press New pipeline
• Select Github
• Select UBports
• Select New Pipeline
• Find and select repository
• Press Create pipeline

• Don't use - in version names (debian/changelog)
• Don't use source format 3.0 quit

By default it will add itself and ubuntu-stable-phone ppa

Branch extension is a quick and simple way to create packages that depend on other packages in a different repo instead of rebulding all packaged, you can simply create a "branch extension" like this:

[depend repo]_-_[branch name]

Example:

xenial_-_awesometest

NOTE: due to a silly bug in jenkins we have to use _-_

Using file is a more permanent way to add depending repos, add one repo per line

Example:

xenial
xenial-caf