Deployment fails on adding new website version to '.versions' file
In #437 (closed), we added switching of website versions. The deployment adds new website versions to a .versions
file. This fails, as the grep
may return a non-zero exit code if the new version is not yet present, making the Jenkinsfile
stop.
For v3.0-M1 deployment, I'll update the website manually. But, we should fix the Jenkinsfile
so that is works properly for future releases. For nightlies, it is not a problem, because nightly
is already in the .versions
file.