tailieunhanh - Code Leader Using People, Tools, and Processes to Build Successful Software phần 7

Hình 5-7 Mục đích là cho người dùng doanh nghiệp để xác định các bảng bởi vì nó là người dùng doanh nghiệp, những người biết những gì các kết quả dự kiến . Phương pháp này tốt nhất là áp dụng thuật toán để kiểm tra, chứ không phải là để thử nghiệm chức năng hơn. | Part II Process Some SCC tools even support this concept as a first-class feature. In certain configurations of IBM Rational ClearCase all check-ins are made locally in the working copy and the personal branch is actually kept on the developer s hard drive. You can check in check out roll back and so on and it all occurs locally. At some point you then integrate up to the ClearCase server which involves taking a diff of the tip in the working copy and merging that into the server s integration copy. That means that the copy on the server is always serving as the integration branch and each developer s working copy is playing the part of the personal branch. This makes the process very clear even using integration as a first-class part of the nomenclature. In Microsoft s Visual Studio Team System a developer can shelve his or her work which in essence automatically creates a personal branch for that developer. However you cannot commit multiple change sets to one shelveset so shelving a set of changes is a one-time operation that does not carry history or allow rollbacks. Shelving is most useful when you want to store a set of changes someplace that isn t just local to your hard drive but don t want to risk breaking the integration build. Subversion as seen above doesn t have any native notion of a personal branch but because Subversion makes branching so simple and easy to organize personal branches are trivial to create and manage. Subversion also makes it easy to see other user s personal branches so work can be shared or reviewed without interfering with the integration branch. However your SCC tools support them personal branches allow developers to continue committing or rolling back changes without affecting the integration branch or the CI process. Task Branches Perhaps the most useful way to use branches to support a CI process is the task branch. Task branches represent a single branch for each integration. That integration might be equal to one task .

TỪ KHÓA LIÊN QUAN
crossorigin="anonymous">
Đã phát hiện trình chặn quảng cáo AdBlock
Trang web này phụ thuộc vào doanh thu từ số lần hiển thị quảng cáo để tồn tại. Vui lòng tắt trình chặn quảng cáo của bạn hoặc tạm dừng tính năng chặn quảng cáo cho trang web này.