/var/svc/log/network-cswpuppetd:default.log
/var/svc/log/network-cswpuppetmasterd:default.log
use tail -f <log file name>
/var/svc/log/network-cswpuppetd:default.log
/var/svc/log/network-cswpuppetmasterd:default.log
use tail -f <log file name>
Subversion is more than just a tool for tracking changes in your code. It can be a cornerstone of an effective release engineering strategy, offering features that facilitate a smooth transition of code from development to production. Here, we’ll explore two techniques you can employ: utilizing revision numbers and creating tags.
Most people who have dabbled in Subversion are familiar with revision numbers. Let’s say you make a commit and your code becomes “revision 1234.” You can then export this specific revision to your development environment for testing. Once it passes your rigorous checks, it’s off to the QA environment for further scrutiny.
When it comes to software development, a robust and efficient build script can be a game-changer. Whether you’re working on a Java project or any other type of application, the right build script can streamline the whole process and make life a whole lot easier for developers. Here’s a rundown of some best practices to keep in mind when you’re writing your build script:
Choose a programming language that is compatible across multiple platforms, especially if you’re working on a Java project. This flexibility will save you from a lot of headaches down the line when dealing with different operating systems.