diff options
| author | dd <dd@wx.tnyzeq.icu> | 2024-07-03 15:10:10 +0200 |
|---|---|---|
| committer | dd <dd@wx.tnyzeq.icu> | 2024-07-03 15:10:26 +0200 |
| commit | 7fcee011a6ff9b49df048a57a3f6171ac8b8d76c (patch) | |
| tree | 5908103152e9bc85e6a85547ee979db0c9701151 | |
| parent | 01b14b0f8597d3f42bff3eb32efbe3c17b064651 (diff) | |
| download | vyos-jenkins-7fcee011a6ff9b49df048a57a3f6171ac8b8d76c.tar.gz vyos-jenkins-7fcee011a6ff9b49df048a57a3f6171ac8b8d76c.zip | |
added information about rerunning automated scripts
| -rw-r--r-- | readme.md | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -113,6 +113,11 @@ If all went well, then all steps should complete successfully and then you can: And you should have the ISO(s) in current directory (`/opt/vyos-jenkins`). +Jenkins will automatically detect changes and build new packages, thus if you keep build server running then +it should keep the repositories up to date by itself. This way you can just use build-iso.sh again and again. +You should check on the Jenkins **Build History** from time to time and/or before you build ISO to make sure all +is going well. This is the same way how the official repository works. + You could be also interested in the [Smoketest](#smoketest). If something isn't right, then see [Something is wrong](#something-is-wrong). |