This is a test harness for the Perforce Unix SDP (Server Deployment Package). It used to use Vagrant, but has now been converted to use Docker containers (see older versions of this file for Vagrant instructions).
To use this bundle you will need to download and install the following free tool:
https://docs.docker.com/engine/installation/
If you're not familiar with Docker, it is building up a huge momentum because of its sweet spot functionality which addresses fast creation of virtual environments and the ability to ship images with all dependencies between different environments.
1) Create a workspace named YourID.test_sdp_dev.sdp (replacing YourID with your account name in the Perforce Public Depot). The root directory should be the directory where this README.md file was found, such that it creates the sdp folder below this directory and maps some test files in this directory. The View: of the workspace should look like this sample:
View:
//guest/perforce_software/sdp/dev/... //YourID.test_sdp_dev.sdp/sdp/...
p4 -s -c YourID.test_sdp_dev sync3) From the command prompt run run_docker_tests.sh from the root directory of the workspace. The first time you run it will take a while as it builds the initial docker images!
sdp/test/run_docker_tests.shBuild your docker image (from workspace root):
1) sdp/test/build_docker_image.sh centos7
How to run all tests:
1) podman run --rm -v $PWD/sdp:/sdp perforce/centos7-sdp /p4/docker_entry.sh
How to interactively poke around inside the container (run scripts manually):
1) podman run --rm -v $PWD/sdp:/sdp -it perforce/centos7-sdp /bin/bash 2) Run 'su - perforce' to become user perforce (home directory is /p4) 3) cat reset_sdp.sh 3) SECONDS=0; /p4/test_sdp.sh; echo "EC=$?; SECONDS=$SECONDS"
Substitute 'centos7' with 'ubuntu22' or similar to use different Linux distros in above commands.
Once you are comfortable with the workflow above, see the env.sh file that contains shorthands to speed up your workflow.
Welcome
=======
This is a test harness for the Perforce Unix SDP (Server Deployment Package).
It used to use Vagrant, but has now been converted to use Docker containers (see older
versions of this file for Vagrant instructions).
Requirements
------------
To use this bundle you will need to download and install the following free tool:
https://docs.docker.com/engine/installation/
If you're not familiar with Docker, it is building up a huge momentum because of its
sweet spot functionality which addresses fast creation of virtual environments and
the ability to ship images with all dependencies between different environments.
https://docs.docker.com/mac/
Usage
-----
1) Create a workspace named YourID.test_sdp_dev.sdp (replacing YourID with your account name in the Perforce Public Depot). The root directory should be the directory where this README.md file was found, such that it creates the `sdp` folder below this directory and maps some test files in this directory. The `View:` of the workspace should look like this sample:
View:
//guest/perforce_software/sdp/dev/... //YourID.test_sdp_dev.sdp/sdp/...
p4 -s -c YourID.test_sdp_dev sync
3) From the command prompt run run_docker_tests.sh from the root directory of the workspace. The first time
you run it will take a while as it builds the initial docker images!
sdp/test/run_docker_tests.sh
Workflow for testing
--------------------
Build your docker image (from workspace root):
1) sdp/test/build_docker_image.sh centos7
How to run all tests:
1) podman run --rm -v $PWD/sdp:/sdp perforce/centos7-sdp /p4/docker_entry.sh
How to interactively poke around inside the container (run scripts manually):
1) podman run --rm -v $PWD/sdp:/sdp -it perforce/centos7-sdp /bin/bash
2) Run 'su - perforce' to become user perforce (home directory is /p4)
3) cat reset_sdp.sh
3) SECONDS=0; /p4/test_sdp.sh; echo "EC=$?; SECONDS=$SECONDS"
Substitute 'centos7' with 'ubuntu22' or similar to use different Linux distros in above commands.
Convenience Aliases
--------------------
Once you are comfortable with the workflow above, see the env.sh file that
contains shorthands to speed up your workflow.
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #11 | 30388 | C. Thomas Tyler |
Released SDP 2024.1.30385 (2024/06/11). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
| #10 | 27331 | C. Thomas Tyler |
Released SDP 2020.1.27325 (2021/01/29). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
| #9 | 25483 | C. Thomas Tyler |
Released SDP 2019.1.25480 (2019/04/11). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
| #8 | 25245 | C. Thomas Tyler |
Released SDP 2019.1.25238 (2019/03/02). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
| #7 | 25012 | Robert Cowham | Propagate test updates from dev and fix failing test by also propagating deleted script. | ||
| #6 | 20974 | C. Thomas Tyler |
Released SDP 2016.2.20972 (2016/11/01). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
| #5 | 19322 | Robert Cowham |
Propagate Docker tests to Main. No functional change. |
||
| #4 | 13587 | C. Thomas Tyler |
Copy up of recent minor dev branch changes to auxiliary scripts and comments. No core SDP functionality changes. |
||
| #3 | 11828 | Robert Cowham | Clarify paths and instructions for testing. | ||
| #2 | 10459 | Robert Cowham |
Fix test comments regarding workspace setup for Workshop location Tidy Vangrantfile comments #review |
||
| #1 | 10148 | C. Thomas Tyler | Promoted the Perforce Server Deployment Package to The Workshop. |