Changes are made on the code, thus checked out items that appear in Plastic.When a developer starts working on one issue, then the issue is open. The workflow will resemble something like this: To configure Plastic SCM to work on the Task on changeset working mode, the user has to configure the Bugzilla extension and select the Bind issues to Plastic changesets option, as explained before on the Client section. Otherwise an error is printed and the operation is cancelled: If it starts with the task prefix, it will then pick the number contained on it and ask Bugzilla if there is a matching bug number. With this attribute created, each time a child branch is going to be created on the repository where it is defined, the extension will check the name of the new branch. Using the Attributes view in the Plastic SCM GUI: Using the command line run the following command:Ĭm attribute create plastic-enforce-task-branch.This attribute must be created using one of the following methods: In order to setup the branch creation check on a repository, create an attribute named plastic-enforce-task-branch on the desired repositories. This check is performed on the branch creation operation, only for child branches. Only if there is a bug number defined in Bugzilla the working branch will be allowed. It is possible to setup the Plastic SCM repositories so that numbered branches associated to tasks are checked against Bugzilla. By selecting a branch the Bugzilla task information is displayed in Plastic SCM: the number or identifier, task owner, status, title and description.īy double clicking on the task pane or by clicking on the Open issue in browser button ( ), a new browser window will be opened and will display the full information of the task in Bugzilla: The branch name for the new branch must match the configured extension prefix (if it has been set) and the numeric identifier on Bugzilla.īy clicking on the Show extended information button ( ) in the Branches view the information associated to the branches will be displayed on the right panel of the Plastic GUI. Using this working mode, every Bugzilla task is associated to a Plastic branch when creating a new one. Parameter to assign one of these values: TaskOnBranch or TaskOnChangeset.Ĭonfigure the rest of the Bugzilla extension parameters (URL where your Bugzilla server is locatedĪt, credentials, branch prefix, and so on) accordingly. /home/pablo/.plastic4/issuetrackers/localhost_8087/allrepos/nf./home/pablo/.plastic4/issuetrackers/localhost_8087/info/nf.Then, you'll have, for example, something like this: Applications/PlasticSCM.app/Contents/IssueTrackerConfigSamples ![]() Plasticscm_install_path/client/extensions/config_samples
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |