nils/gluon
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

use "gluon-docker-v1" instead of "gluon-docker-1"

Browse Source
This commit is contained in:
lemoer 2020-01-18 17:57:38 +01:00
parent 8c2d9b3437
commit 7f6763b36f
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
contrib/ci/Jenkinsfile vendored
View File

@ -15,7 +15,7 @@ pipeline {
}
}
stage('lint-sh') {
agent { label 'gluon-docker-1' }
agent { label 'gluon-docker-v1' }
steps {
sh 'make lint-sh'
}
@ -47,4 +47,4 @@ pipeline {
# As soon, as you properly rebuilt your docker container, you
# can notify lemoer, that you have updated your node.
#
# - gluon-docker-1: add shellcheck binary to the build environment
# - gluon-docker-v1: add shellcheck binary to the build environment

2
contrib/ci/jenkins-community-slave/README.md
View File

@ -26,7 +26,7 @@ docker run --detach --restart always \
- Your node should appear [here](https://build.ffh.zone/label/gluon-docker/).
- When clicking on it, Jenkins should state "Agent is connected." like here:
![Screenshot from 2019-09-24 01-00-52](https://user-images.githubusercontent.com/601153/65469209-dac6c180-de66-11e9-9d62-0d1c3b6b940b.png)
5. **Your docker container needs to be rebuilt, when the build dependencies of gluon change. As soon as build dependencies have changed, the build dependency api level has to be raised.** After you rebuilt your docker container, notifiy lemoer, so he can bump the versioning number.
5. **Your docker container needs to be rebuilt, when the build dependencies of gluon change. As soon as build dependencies have changed, the build dependency api level has to be raised.** After you rebuilt your docker container, notifiy @lemoer, so he can bump the versioning number.
## Backoff
- If @lemoer is not reachable, please be patient at first if possible. Otherwise contact info@hannover.freifunk.net or join the channel `#freifunkh` on hackint.