job/configs.git -

Age	Commit message (Collapse)	Author
2016-10-14	tcwg-*: Use build-discarder instead of logrotate.	Christophe Lyon
	Change-Id: I864b319706660d9fef1daa7b213c5488a7039d8e
2016-07-25	tcwg-*: Remove usage of obsolete --fileserver option	Maxim Kuvyrkov
	Change-Id: Ica9ca31f8d11ea0b5bb8140c431c88e5d84bcb27
2016-07-07	tcwg-bkk16-buildfarm-benchmark: Change ABE default branch to stable.	Yvan Roux
	Change-Id: Ib81735b4553e831b48219d27b796247c59717ef4
2016-05-13	tcwg-buildfarm: Fix bash syntax error in trap handler	Maxim Kuvyrkov
	Change-Id: If3f0b860c1442cf009d422fe3e310d9f63f95bef
2016-05-12	tcwg-*: Ignore failure to finalize schroot session	Maxim Kuvyrkov
	... and rely on tcwg-cleanup-stale-schroot-sessions to clean it up later. Change-Id: Ib668b55b06bbca5c97e39d30183ebbf96f66c101
2016-04-19	tcwg-bkk16-buildfarm-benchmark: Rebase on top of tcwg-bkk16-buildfarm.	Yvan Roux
	Change-Id: I9a899d81faa8404652fad99e0ec5d9812fab5219
2016-04-05	tcwg-bkk16-buildfarm-benchmark: Set explicit TRIPLE	Bernard Ogden
	Safer than relying on triple-derivation code in tcwg-benchmark, which is there more for interactive use. This trick probably won't work for the schroot-* cases, but these also happen to be the native cases, and we don't support that yet. Change-Id: Idbf402b69418d5ca3842b6cfcadd5c57c02d3c34
2016-04-04	tcwg-bkk16-buildfarm-benchmark: Tie matrix parent to master	Bernard Ogden
	The copy-to-master trick requires that matrix parent is the same node as master. As we only tie the parent of the matrix to master, this should create negligible node on master, though it will mean a long-running job consming one executor. Change-Id: Ia6a1c6203a8c7efd863cc207de17ab19d7171032
2016-04-04	tcwg-bkk16-buildfarm-benchmark: Revert "Explicit bench_parameters destination"	Bernard Ogden
	This reverts commit 1291cd4c10d0c68576986ecb2b9e9b6cd3032856. This commit did not have the desired effect. The real problem is that matrix parent != jenkins master node. Change-Id: Ic66a07710a7ad7e356471126e6dfcc3d37e2d753
2016-04-04	tcwg-bkk16-buildfarm-benchmark: Explicit bench_parameters destination	Bernard Ogden
	Implicit 'copy to workspace of current job' destination appears to get the wrong path. Change-Id: Ia60a79c185a0c5482943ea742b4175563e1d467e
2016-03-24	tcwg-bkk16-buildfarm-benchmark: Only trigger on success	Bernard Ogden
	Makes no sense to run benchmark if build failed. Prevents us running with an old bench_parameters if build manages to fail before we empty the bench_parameters file. Change-Id: Ia2029b9ec5f3d2121379f95f53dde185d598bf7c
2016-03-24	tcwg-bkk16-buildfarm-benchmark: Refer to triggers from child-workspace	Bernard Ogden
	Add a comment to the child-workspace setting, so that editors may spot that changing child-workspace requires changing the triggers. Change-Id: I8c5b3c1ee3d188bc3b7bc4b52881c9ca15a2067a
2016-03-24	tcwg-bkk16-buildfarm-benchmark: Fix trigger paths	Bernard Ogden
	Paths were not taking account of child-workspace setting. Change-Id: Ie04e33f66be208e762bce7f841bc996d7955a85e
2016-03-24	tcwg-bkk16-buildfarm-benchmark: Eliminate race	Bernard Ogden
	We were triggering LAVA jobs before publishing the artifacts, for reasons spelled out in the long comment that this patch removes. Now that LAVA jobs are building more efficiently (see abe commit cfac0279e002c1e1fdd2e95118ed50b84f5a8a76) it is likely that LAVA jobs will try to access unpublished artifacts. Now we use trigger-parameterized-builds after publishing the artifacts. This happens on the master of the matrix job, not in the slaves, so we have to copy the bench_parameters file from slave to master. Because there is no matrix-intelligence in trigger-paramterized-builds, we have to spell out an explicit trigger with the full path to the bench_parameters file for each job that we want to submit. This creates 2 dependencies with other parts of the job config: 1) If we change the list of targets for which we benchmark in the shell stanza, we must also change the trigger-parameterized-builds stanza accordingly. 2) If we change the axes of the multinode job, we must also change the trigger-paramaterized-builds stanza accordingly. Comments pointing to the trigger-parameterized-builds stanza are added to both afffected locations. We might have a bench_parameters file from an old run hanging around in the master workspace. Therefore it is no longer sufficient to create bench_parameters conditionally in the slave. Instead, we make it empty in the slave, then conditionally give it content. If the slave does not create bench_parameters content then the empty file gets copied to master and does not trigger a build. When ci.linaro.org uses a JJB with a fix for https://storyboard.openstack.org/#!/story/2000444 in it, we can use files from matrix slaves in trigger-parameterized-builds and get rid of all this complexity. Change-Id: Ife12844725b4916b88286e8aca4922ac9a5ce625
2016-03-22	tcwg-bkk16-buildfarm-benchmark: Benchmark armv8l	Bernard Ogden
	Change-Id: I108cf5c0a8fac9aacd27be185af3b0646b154d60
2016-03-22	tcwg-bkk16-buildfarm-benchmark: Create artifact_parameters before first exit	Bernard Ogden
	Change-Id: I8fd6418f8367782ea89afd11bbe64b077b16a13e
2016-03-22	tcwg-bkk16-buildfarm-benchmark: Add run_benchmark parameter	Bernard Ogden
	Change-Id: If4adae5674907de214cec6b67c1ac6406cb444fd
2016-03-22	tcwg-bkk16-buildfarm-benchmark: Apply benchmarking patches to ↵	Bernard Ogden
	tcwg-bkk16-buildfarm Equivalent to the changes to tcwg-buildfarm.yaml starting at https://review.linaro.org/#/c/10894/3 Change-Id: I3d239bd1f0397e2951e2030063b140af95f33657