Hello, > Then you can use: > "scripts_folder" string => "$(sys.workdir)resources/scripts"; > > Yeah, that's what I'll be doing, but currently I'm just "testing out" the > files in a location other than "masterfiles" so that they won't be copied to > other nodes as they're being tested. How do you suggest I go about testing > scripts? Work on the "masterfiles" folder itself on a different machine? For testing, I am using a special class "testing" and I enable it only on the clients that I want to. You can set the "scripts_folder" variable as depending on the particular class.
!testing:: "scripts_folder" string => "$(sys.workdir)/resources/scripts"; testing:: "scripts_folder" string => "/cf-test/project/resources/scripts"; For the actual development I use an additional policy server and a limited number of nodes that I am ok to break, so yes, it's always a good idea to separate the development, testing and production environments. Running scripts (particularly as root) which are yet being tested on the production machine is... well, it depends. It might either ruin your nerves or your wallet. > For the particular java case, I prefer to use Debian or RedHat packages > to distribute it. If you just want to unpack it from a zipfile, perhaps > it is better to just use a copy promise and copy this from a master > server where it is kept unpacked. > > I did use rpm to install packages, but I'm required to install a particular > version of Oracle's JDK and the latest version of maven, and setting up the > repositories and stuff got quite patchy, that's why I decided to maintain > installation media locally and install from there. I would either create a custom package with the set (JDK version x and maven), or make CFEngine copy the whole thing. I am sure you can find a particular JDK version pre-packaged, I don't know about maven. And CFEngine can make sure for you that the system uses that particular version. Cheers, Ballock _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
