The Blueprint for a Smooth Release Engineering Process#

Isn’t it satisfying when everything falls into place just as you’d hoped? In the complex world of development, where multiple cogs are in motion at any given time, having a well-defined plan can make all the difference. Here’s a streamlined guide to setting up a robust Release Engineering (Releng) system that ensures efficient and error-free deployments.

Step-by-Step Implementation#

1. Version Control with Git#

We begin by storing all our configuration files and Puppet manifests in a Git repository. It serves as the central hub where changes are tracked and updated.

To disable a service, you must be root or have sudo privileges.

For example, to disable the Puppet service, you would run the following command:

svcadm disable network/cswpuppetd:default

This will disable the Puppet service and prevent it from running.

To verify that the service has been disabled, you can run the following command:

svcs | grep puppet

This will list all of the services that are currently running, and if the Puppet service is disabled, it will not be listed.

/var/svc/log/network-cswpuppetd:default.log
/var/svc/log/network-cswpuppetmasterd:default.log

use tail -f <log file name>