This is a test harness for the Perforce Unix SDP (Server Deployment Package). One quick 'vagrant up' will create a Ubuntu and a CentOS box where you can easily run the test harness.
To use this bundle you will need to download and install the following tools, both of which are free.
The following vagrant plugins ("sudo vagrant plugin-install<plugin name>"):
If you're not familiar with Vagrant it is a command line based virtual machine management tool that makes it easy to create and provision virtual machines, all driven by a simple text file. If you haven't used it before be warned: simple VM management is addictive!
VirtualBox is an open source hypervisor made by Oracle. It runs on many platforms and is the default hypervisor for Vagrant. You do not need to know much of anything about Vagrant to use these tools. We'll explain the few commands you will likely need below.
Given that you are using a virtual machine you will need at least 512MB of RAM to run the environment. You will also need at least a gig of drive space to hold the VM image.
1) Have a workpsace which looks like (assuming name of myws.sdp):
View: //guest/perforce_software/sdp/... //myws.sdp/sdp/... //guest/perforce_software/sdp/test/* //myws.sdp/*
2) sync the workspace
3) In addition, you want to do a wget on the following: ftp://ftp.perforce.com/perforce/r14.1/bin.linux26x86_64/p4 to //myws.sdp/sdp/Server/Unix/p4/common/bin/p4 ftp://ftp.perforce.com/perforce/r14.1/bin.linux26x86_64/p4d to //myws.sdp/sdp/Server/Unix/p4/common/bin/p4d
4) From the command prompt run 'vagrant up' in the workspace root directory.
The command 'vagrant up' tells Vagrant to look for the cleverly named 'Vagrantfile' and create the VM described within. Note you will need an internet connection during this process.
Once Vagrant returns you will have a fully functional installation.
You will need very few commands to be successful with Vagrant for this project. Here are the commands you will need.
That's it! With those four commands you should be suitably dangerous to run tests.
One important part of using Vagrant is taking advantage of the shared folders it creates. With this project we automatically link most of the files that are in the directory along with the Vagrantfile to appropriate places within the VM. Things are shared to /sdp within the VM.
These shared folders allow you to use your favorite editors on your computer with the files that are being used by the VM. Without SSHing in you can edit files live inside the VM. This is one of the biggest advantages of using Vagrant; it lets you code with your preferred tools while still having the controlled environment your app needs.
This also means that if at any point you need a clean test environment a quick 'vagrant destroy' and 'vagrant up' will give you a fresh installation with all of your code changes intact. 'vagrant destroy' only deletes the contents of the VM, not the contents of your host machine.
How to run:
1) Run 'vagrant ssh' from the directory you created to shell into the VM. 2) Run 'sudo su - perforce' to become user perforce (home directory is /p4) 3) python3 test_SDP.py (This is a link to the real file under /sdp)
Added convenience aliases and function to provide shorthands for
Docker test environment workflow.
|#8||25154||robert_cowham||Missed README from previous change|
Change scripts to be able to be run from workspace root
So no longer requires funny mapping in workspace view (see README.md for view)
Made sample commands that should work w/o modification, instead
of mixing CentOS/Ubuntu.
Replaced `pwd` with $PWD because `pwd` doesn't render as
reliably in different Markdown editors.
Removed unnecessay 'sudo' (since it is called when aleady
|#5||20881||robert_cowham||Clarify docker instructions.|
|#4||19023||robert_cowham||Update to refer to Docker instead of Vagrant|
|#3||12924||tom_tyler||Very minor doc tweaks in SDP test suite.|
|#2||12028||tom_tyler||Refreshed SDP dev branch, merging down from main.|
Fix test comments regarding workspace setup for Workshop location
Tidy Vangrantfile comments
|#1||10148||tom_tyler||Promoted the Perforce Server Deployment Package to The Workshop.|