![]() 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. #WINDOWS JIRA CLIENT FULL#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 allrepos, which means that all of your repositories will be linked to the issue tracker.Ĭopy the nf example configuration file into the new created path.The name of the repository that you want to link to the issue tracker. $HOME/.plastic4, where repository is one of the following values: To do this:Ĭreate the structure issuetrackers/ server_port/ repository under This way all the Plastic clients have the same Bugzilla settings by default. Set a global extension configuration in the server.You can configure the Bugzilla extension on the Plastic SCM client on your Linux or macOS machine using one of these methods: Now, you must configure the Bugzilla parameters (URL where your Bugzilla server is located at, credentials,Ĭlient configuration - Linux and macOS systems Select the Bind issues to Plastic changesets option. If you want to bind to a particular repository with Bugzilla, then select that repository.īy default, the Bind issues to Plastic branches option is activated to work with the If you want to bind to all your repositories with the issue tracker, then select Repositories. Global extension configuration, then select the Now, select the repository you want to Apply binding to: In the new window, click the Issue trackers tab.Ĭlick the radio button Bind to this issue tracking system. #WINDOWS JIRA CLIENT HOW TO#Read how to configure the Bugzilla integration on your Windows, Linux, or macOS system.įollow these steps to configure the Bugzilla extension on the Plastic SCM client on your Windows machine:Ĭlick the Preferences tab of the main window of the Plastic SCM GUI. To setup the Bugzilla extension functionality, copy the script file plastic.cgi (included on plasticscm_install_path/client/extensions/bugzilla) to the Bugzilla installation folder.ĭepending on the server's operating system, the first line of the script file may have to be changed: In this chapter, you will learn how to configure the Bugzilla integration both in the server and in the client sides. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |