![]() ![]() Figure 1: httpd home pageīugzilla does require a Web server and the Apache HTTP (httpd) server package, and its dependencies need to be installed. The ‘-K’ option prompts for the sudo password for the ‘centos’ user account. You can use up to four v’s for a more detailed output. The ‘-vv’ represents the verbosity in the Ansible output. ![]() The above playbook can be invoked using the following command: $ ansible-playbook -i inventory/kvm/inventory playbooks/configuration/bugzilla.yml -tags repo -vv -K Yum: name=* update_cache=yes state=present The Ansible playbook for installing the repositories is given below:. These need to be installed first, and then ‘yum update’ is required to update the cache. The installation of Bugzilla requires additional repositories - deltarpm and epel-release. You can now test connectivity from Ansible to the CentOS 7 VM using the following command: $ ansible -i inventory/kvm/inventory bugzilla -m ping You should also add an entry in the /etc/hosts file for the CentOS VM, as shown below: 192.168.122.87 bugzilla SELinux needs to allow access for port 80. The inventory/kvm/inventory file contains the following: bugzilla ansible_host=192.168.122.87 ansible_connection=ssh ansible_user=centos ansible_password=passwordĪ ‘centos’ user is created in the guest VM, and sudo access is provided for this user using the visudo command. The Ansible inventory, playbook and configuration files are created on the host system as follows: ansible/inventory/kvm/ The version of Ansible used is 2.6.0 as indicated below: $ ansible -versionĬonfigured module search path = Īnsible python module location = /usr/lib/python3.6/site-packages/ansible The host system is a Parabola GNU/Linux-libre x86_64 system, and Ansible is installed using the distribution package manager. Get a chance to use Bugzilla and many more which we offer.A CentOS 7 (x86_64) guest virtual machine (VM) using KVM/QEMU will be used to install and configure Bugzilla. Register here and be the master of your application testing. We hope this blog helped you to understand the process better of how integration should be done between QA Touch with Bugzilla. Snapshot of Messages Posted in Bugzilla by QA TouchĪny bugs posted in QA Touch will automatically appear in Bugzilla after completing the above steps. Have a look at the below screenshot for your reference. Select a Bugzilla project from the list and click submit to Map.Map the respective repository to the QA Touch Project with bugs that are added in the repository. Mapping Bugzilla Project to QA Touch Project After a successful configuration, the status becomes connected as shown in the below snapshot.Enter the Bugzilla Username, Password, URL and API Key.Click the Administration → Integration Settings.Here’s the step-by-step guide one should be following for a successful and seamless Bugzilla Integration with QA Touch:Īdministration → Integration Settings Navigation The below snapshots shows the steps to access the avatar. Enter the description, click the radio button and submit.Generate a new API key with an optional description.QA Touch offers seamless integration with Bugzilla presenting the best way to keep all the bugs posted in the Bugzilla. Bugzilla quickly became a favorite of the open-source crowd (with its genesis in the open-source browser project, Mozilla) Bug-tracking systems allow individual or groups of developers effectively to keep track of outstanding problems with their product. We are pleased to announce our community that QA Touch is now integrated with Bugzilla.īugzilla is a bug or issue-tracking system. Lightweight integration with issue trackers, including JIRA, JIRA Server, SLACK, GitHub, GitLab, Bitbucket, Trello, Assembla. QA Touch is a cloud-based test management tool providing end-to-end solutions for agile get flexibility, visibility, and better software. ![]()
0 Comments
Leave a Reply. |