solimusical.blogg.se

1. Bugzilla migration install#
2. Bugzilla migration archive#
3. Bugzilla migration code#
4. Bugzilla migration free#

Once logged into mysql as root, create the bugs user and the database: mysql> create user IDENTIFIED BY 'XXXpasswordXXX' mysql> create database bugs mysql> show databases

Bugzilla migration install#

Install MySQL, set the service to start on boot, and set the mysql root password: yum groupinstall "MySQL Database" chkconfig -levels 2345 mysqld service mysqld restart /usr/bin/mysqladmin -u root password 'XXXX'

Add these lines to the end of your nf file: PerlSwitches -w -T PerlConfigRequire /var/Restart Apache service httpd restart Setup MySQL Open the /etc/httpd/conf/nf file in your favorite editor.

Try the main site to ensure that apache is setup correctly by browsing to your site name or to You should see the default apache site showing that the webserver is installed properly. Install the Web Server, set the run levels, and start the service: yum groupinstall "Web Server" yum chkconfig -levels 2345 httpd on service httpd restart These directions all assume that you have a Bugzilla 3.0 database that you’ve backed up with teh following commands: sudo mkdir /data/backups/mysql-bugzilla-3.0 sudo chown mysqldump -u bugs -password=XXXXXXXXX bugs | gzip -9v > `date '+/data/backups/mysql-bugzilla-3.0/bugs_%Y%m%d.sql.gz'` Backup Your Current Bugzilla 3.0 Database I tried to arrange all of these in an order that will work, but if you have to install the bugzilla folder first and continually re-run. script over and over throughout the process to check myself and figure out what needed to occur next. I know that I had to periodically go back the the. You may find that some of these instructions may need to be run in a slightly different order, but this is a pretty complete account of what it took to get this going on the new server. Since I was already writing these down as I went, I thought that I would share these instructions with the greater Linux community. The migration to the new system will start on friday () and should be finished until monday ().I recently did a migration from Bugzilla 3.0 running on one server to Bugzilla 4.0 running on a new server. Project is obsolete and will be deleted (meanwhile managed in the OW2 Jira) The issues should be classified in the new palladio component structure But the new Jira Projects will only contain those issues explicitly identified as valid with an active stakeholder. To make this explicit: We will not loose any issues, because they will be imported in the new system and archived here.

This means, if you are responsible for a component or a stakeholder of one or more issues, you should copy those issues from the imported bugzilla projects to the new Jira projects. To start with a clean issue tracker and get control over the issues in the system, we have decided to explicitly copy only those issues identified as relevant to the new projects. Those imported projects get a name starting with "Bugzilla …", an id starting with and the category "Old Bugzilla Projects" ( )

Bugzilla migration archive#

We will import the Bugzilla projects as separated projects into the system to archive their information and issues. If you want to create a new project: please send a request with an informal proposal to Michael Hauck or Benjamin Klatt.

Bugzilla migration code#

The structure is aligned with the new code repository (SVN) structure introduced in 2011: SVN Code Repository The issue tracker will host separate projects for our top level development projects (e.g., Palladio, Workflow Engine, Ginpex) and subcomponents (e.g., Palladio ProtoCom or Palladio Reliability). Users with an KIT/ATIS account are pleased to use their according LDAP credentials.

Bugzilla migration free#

If you have any further questions, feel free to send an email to klatt(at)fzi.de.įurther information about system are documented on this page: Palladio Jira.Įveryone is able to login or create an account. Thanks to this, we are now migrating to a Jira installation as a new Issue Tracker.įind some details about the migration below.

In 2011, Palladio has been officially accepted by Atlassian as an OpenSource community project.