aboutsummaryrefslogtreecommitdiffstats
path: root/jobs/update-osmo-ci-on-slaves.yml
AgeCommit message (Collapse)AuthorFilesLines
2020-01-15docker: move to docker-playground.gitOliver Smith1-0/+24
Instead of building "osmocom:deb9_amd64" from this repository, build "$USER/debian-stretch-jenkins" from docker-playground.git (same Dockerfile). Adjust all jobs to use the new image name. Add a new "update-osmo-ci-on-slaves-dp" jenkins job, which triggers the existing "update-osmo-ci-on-slaves" job whenever docker-playground.git changes. Replace docker/rebuild_osmocom_jenkins_image.sh with scripts/osmo-ci-docker-rebuild.sh, so we can get rid of the docker dir. I thought about dropping the script completely, and directly writing the two lines into contrib/jenkins.sh. But I kept the extra script for convenience, when testing locally. Related: OS#4345 Depends: docker-playground I125ae8a6bcabbd1f485028c79b0abacda0622c3a Change-Id: I30a61aebcadef5536e74edd35e1c75ef77a2da9f
2020-01-08jobs/update-osmo-ci-on-slaves: origin/master onlyOliver Smith1-0/+2
Don't run, when different branches were pushed. Change-Id: I2cf55391066b60cf6a594f528ed0eaf59a886391
2018-04-24jobs: update-osmo-* remove old build nodesAlexander Couzens1-2/+0
Change-Id: Ia7f98e55895b150da473a38a3e68b188acd0e76a
2018-04-24jobs: update-osmo*: remove non-existent node build2-deb8buildAlexander Couzens1-1/+0
The jobs will stall when trying to handle a non-existent node Change-Id: Id9f25d8a5f6d0521e2b70884f46de5dee14d8092
2018-04-11jobs: update-osmo-* reformat a list to be human readableAlexander Couzens1-1/+10
Change-Id: Ic64463d3974fdbf3967e67a77c75490d7ca80fb7
2018-04-05jobs/update-osmo*: add new nodes to the update jobsAlexander Couzens1-1/+1
Change-Id: Ib103b3343d582f7a78f0c4cec00c94078a078584
2018-02-25jenkins: add node admin2-deb8build to the update jobsAlexander Couzens1-1/+1
Change-Id: I6b703b9f27865b146f20bea953fe3d6500a88166
2018-02-25jenkins: add node admin2-deb9build to the update jobsAlexander Couzens1-1/+1
Change-Id: Ie3803a46ee192dc72823291004ee20f4bdbe0126
2018-01-08Send email on update-* job failuresMax1-0/+4
Notify intern@ if either update-osmo-ci or update-osmo-python jobs failed. Those are essential for our CI and test infrastructure so we should look into related failures right away. Change-Id: I0d51e35424a26eab7d38152e13f3ac6fd3f3997c Related: OS#2821
2017-12-15jobs: fix poll-scm on update-osmo-ci-on-slavesNeels Hofmeyr1-0/+6
poll-scm was missing by accident Change-Id: I027c5fa12c8be9434e3efec11976004c7924c472
2017-12-15jobs: add build2-deb8build to update-osmo-ci-on-slaves jobNeels Hofmeyr1-1/+1
Change-Id: I48246067f05227efc18b46cb1b29d1c50f4eab84
2017-12-09jobs: gerrit, master, update-osmo-ci: fix build-discarder sectionNeels Hofmeyr1-3/+4
The build-discarder section was silently not working. It needs to be nested below a 'properties' node. Also the names need to be dashed and not camelCased. Change-Id: I9503200a8873e616f9195d4bb1d6163c464b305e
2017-11-28jobs: update-osmo-ci-on-slaves: remove build2-deb8buildNeels Hofmeyr1-1/+1
The node is offline and has been for a long time. The last osmo-ci-on-slaves job ran for a week waiting for it to come back online. Change-Id: I5a315d1ce3d7d5763ba07bf29f9cdd5d6f7c6491
2017-11-28jobs: add update-osmo-ci-on-slaves.ymlNeels Hofmeyr1-0/+23
Change-Id: Ia933288f87f53f832732f650ba4be30d58faea7f
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-27 19:22:22 +0000