aboutsummaryrefslogtreecommitdiff
path: root/trigger-linux-linaro-tracking-ll.yaml
AgeCommit message (Collapse)Author
2016-06-03linux-linaro-stable: update jobs to use the GIT smart protocol.Ben Copeland
Change-Id: Ic0a42ca450c6c8c6ca73d565178288244af4466b
2015-10-16trigger-linux-linaro-tracking-ll: don't trigger the ILP32 job anymoreAndrey Konovalov
The linux-linaro-tracking-ll-ilp32 job is now using linux-linaro-extra branch, and it shouldn't be triggered by changes to linux-linaro branch. A separate trigger-linux-linaro-tracking-ll-ilp32 job tracking the updates to the linux-linaro-extra branch has been created recently. Change-Id: Ib2213f6180473f0e9040b65b9c3da5154df3413d Signed-off-by: Andrey Konovalov <andrey.konovalov@linaro.org>
2015-04-16trigger-linux-linaro-tracking-ll: trigger linux-linaro-tracking-ll-ilp32 jobFathi Boudra
Change-Id: Iac74d1de0f3581b1fb9e17aa265e806b4d063d23 Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
2015-04-07use the refs/heads/<branchName> syntaxFathi Boudra
<remoteRepoName>/<branchName> can be ambiguous. Per the documentation: The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch is unambiguous. If ambiguous the first result is taken, which is not necessarily the expected one. Better use refs/heads/<branchName>. Change-Id: I838e2b22e3b256d1c294e8a071a97960f109e652 Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
2015-01-12trigger-linux-linaro-tracking-ll: add automated recipe update notificationFathi Boudra
Change-Id: Iecd8e6d4adfdfd217a2a460aa785063a814e4452 Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
2014-09-10Add trigger-linux-linaro-tracking-ll jobFathi Boudra
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>