Confirmed users
4,293
edits
ReleaseEngineering/OPSI: Difference between revisions
→Installing the package file on production
| Line 129: | Line 129: | ||
=== Installing the package file on production === | === Installing the package file on production === | ||
Please note that you should NOT install packages onto the production OPSI server unless they have been properly reviewed and checked in. That means your package should be landed in opsi-package-sources (hg), and you should land any binaries in opsi-binaries as cltbld@staging-puppet (CVS). | |||
(For production): | (For production): | ||
# as cltbld on the opsi server | # as cltbld on the opsi server | ||
| Line 143: | Line 145: | ||
su -c './regenerate-package package-name' | su -c './regenerate-package package-name' | ||
Your package should now show up in the OPSI Config Editor. | Your package should now show up in the OPSI Config Editor. Make sure to set staging slaves to install/update the package as well as production ones. | ||
== Documentation/Links == | == Documentation/Links == | ||