devdocs:deploy_new_build_server
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
devdocs:deploy_new_build_server [2018/12/30 21:53] z5t1 |
devdocs:deploy_new_build_server [2019/01/07 17:12] (current) z5t1 |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| The following is the process for deploying a new build server. | The following is the process for deploying a new build server. | ||
| + | - Edit the ''/etc/pickle.conf'' file and set MIRROR variable to point to the staging server. | ||
| - Install the the build server buildtools (substitute the version number of Cucumber Linux you are building in for "x.y"): ''cd && git clone https://gitlab.cucumberlinux.com/cucumber/buildtools.git && cd buildtools && make install-build-server VERSION=x.y''. | - Install the the build server buildtools (substitute the version number of Cucumber Linux you are building in for "x.y"): ''cd && git clone https://gitlab.cucumberlinux.com/cucumber/buildtools.git && cd buildtools && make install-build-server VERSION=x.y''. | ||
| - Edit the ''/opt/buildtools/config'' file and set the STAGING_SERVER variable to the appropriate value. | - Edit the ''/opt/buildtools/config'' file and set the STAGING_SERVER variable to the appropriate value. | ||
| Line 10: | Line 11: | ||
| - Set the timestamps on all of the files in ''/var/log/packages'' to the time you want to start building from. Any updates to the ports tree that took place after this time will trigger a rebuilding of the affected package. Any updates to the ports tree that took place before it will not. | - Set the timestamps on all of the files in ''/var/log/packages'' to the time you want to start building from. Any updates to the ports tree that took place after this time will trigger a rebuilding of the affected package. Any updates to the ports tree that took place before it will not. | ||
| - Alternatively, you can run ''pickle --update && pickle'' and install all the available updates. This will cause the build server to build any new updates, but skip any old ones. | - Alternatively, you can run ''pickle --update && pickle'' and install all the available updates. This will cause the build server to build any new updates, but skip any old ones. | ||
| + | - Run ''/opt/buildtools/auto_update'' to update the local files and build any updates. | ||
devdocs/deploy_new_build_server.1546206814.txt.gz ยท Last modified: 2018/12/30 21:53 by z5t1
Page Tools
