This is the home of the Component Based Development tool set, CBD.
The CBD System can be deployed by a Perforce admin to enhance Component-Based Development workflows.
This version of the CBD System is known to work with 2014.2 Perforce servers.
--- Coming Soon ---
If you just want the latest released version of the file, it is in the Perforce server here:
Please contact Perforce Consulting (mailto:Consulting@Perforce.com) for more information.
===
All registered Workshop users have open access (but not write) to the CBD, specifically to this path:
//guest/perforce_software/cbd/main/...The open access level confers the ability to edit and shelve changes for a pre-commit review process. We'll review the change, and either incorporate it or provide feedback. Be sure to provide a detailed change description, and also include the tag/text "[review]" in your changelist description to initiate a Swarm code review.
Optionally, you may also branch the cbd folder, or some subset of it, into your own guest area. Creating a branch spec is recommended for this purpose, e.g. with a branch spec something like this:
Branch: your_name-cbd
Owner: your_name
Description:
Branch for CBD Updates by your_name.
Options: unlocked
View:
//guest/perforce_software/cbd/main/... //guest/your_name/cbd/main/...Edit, test and submit changes in your branch. Then when you are done, merge your changes back into our mainline, shelving them for review.
File a job. Name the job CBD-N, where N is the next available job number which you must assign manually. To see the next available job number, add one to the biggest number you see when running:
p4 jobs -e 'Job=CBD-*'
Then set the Project value to: perforce-software-cbd
Filing a job is not strictly required, but increases the transparency of what you're doing, and helps promote it.
Component Based Development (CBD) System === Welcome --- This is the home of the Component Based Development tool set, CBD. Introduction --- The CBD System can be deployed by a Perforce admin to enhance Component-Based Development workflows. P4D Compatibility --- This version of the CBD System is known to work with 2014.2 Perforce servers. --- Coming Soon --- If you just want the latest released version of the file, it is in the Perforce server here: https://swarm.workshop.perforce.com/projects/perforce-software-baseline-and-branch-import/files/dist/cbd.tgz Contact Us --- Please contact Perforce Consulting (mailto:Consulting@Perforce.com) for more information. === Contributing by Shelving --- All registered Workshop users have **open** access (but not **write**) to the CBD, specifically to this path: //guest/perforce_software/cbd/main/... The **open** access level confers the ability to edit and **shelve** changes for a pre-commit review process. We'll review the change, and either incorporate it or provide feedback. Be sure to provide a detailed change description, and also include the tag/text "[review]" in your changelist description to initiate a Swarm code review. Contributing by Branching --- Optionally, you may also branch the cbd folder, or some subset of it, into your own guest area. Creating a branch spec is recommended for this purpose, e.g. with a branch spec something like this: Branch: your_name-cbd Owner: your_name Description: Branch for CBD Updates by your_name. Options: unlocked View: //guest/perforce_software/cbd/main/... //guest/your_name/cbd/main/... Edit, test and submit changes in your branch. Then when you are done, merge your changes back into our mainline, shelving them for review. Guidelines for CBD Contributors --- * Communicate using Swarm! Let folks know what you're planning before you work to hard on something that might already be underway. * File a job. Name the job CBD-N, where N is the next available job number which you must assign manually. To see the next available job number, add one to the biggest number you see when running: p4 jobs -e 'Job=CBD-*' Then set the Project value to: **perforce-software-cbd** Filing a job is not strictly required, but increases the transparency of what you're doing, and helps promote it. * We prefer changes that are generic, and have a wide appeal.
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #9 | 22312 | C. Thomas Tyler | Updated docs. | ||
| #8 | 19885 | Robert Cowham | Clarified that README.md has replaced README.docx | ||
| #7 | 16352 | C. Thomas Tyler | Fixed a typo. | ||
| #6 | 13835 | C. Thomas Tyler |
Added Windows support for server-side components. These changes should not interfere with Linux operation. Includes: * Sample Windows broker config file. * Windows batch file wrapper scripts. * Code changes to support minor variations for Windows and Linux SDP. * Some defensive coding to avoid an exception to avoid processing a Classic workspace. |
||
| #5 | 13732 | C. Thomas Tyler | Updated README.md (copy up). | ||
| #4 | 12151 | C. Thomas Tyler | Fixed a typo, s/CDB/CBD/. | ||
| #3 | 12148 | C. Thomas Tyler | Added a bit more info. | ||
| #2 | 12145 | C. Thomas Tyler | Updated README.md to have an overview of what CBD is all about. | ||
| #1 | 12086 | C. Thomas Tyler | Added basic README.md file for CBD. |