Commit e65f3f25 authored by Romain Bouvier's avatar Romain Bouvier
Browse files

Update README for Xfce

parent 95c3d88c
...@@ -25,7 +25,7 @@ source ~/src/virtualenvs/bztogl/bin/activate ...@@ -25,7 +25,7 @@ source ~/src/virtualenvs/bztogl/bin/activate
# at this point your shell prompt will change to something like "(bztogl) $_" # at this point your shell prompt will change to something like "(bztogl) $_"
pip3 install python-bugzilla pip3 install python-bugzilla
pip3 install python-gitlab pip3 install python-gitlab
pip3 install --user -e . pip3 install -e .
# or use "python3 setup.py install --user" instead of the above # or use "python3 setup.py install --user" instead of the above
``` ```
...@@ -42,6 +42,7 @@ At a high level, `bztogl` needs to be able to do these: ...@@ -42,6 +42,7 @@ At a high level, `bztogl` needs to be able to do these:
look at bugs that are already closed.* Here, by "bugs that are open" look at bugs that are already closed.* Here, by "bugs that are open"
we mean bugs with status `NEW, ASSIGNED, REOPENED, NEEDINFO, we mean bugs with status `NEW, ASSIGNED, REOPENED, NEEDINFO,
UNCONFIRMED`. UNCONFIRMED`.
You can migrate CLOSED/RESOLVED bugs with `--resolved` switch.
# Know what you are doing # Know what you are doing
...@@ -56,7 +57,7 @@ test project instead. ...@@ -56,7 +57,7 @@ test project instead.
1. Create a personal project for testing 1. Create a personal project for testing
2. Get an API key 2. Get an API key
3. Run `bztogl` 3. Run `bztogl --xfce --production`
Each of these steps is detailed below. Each of these steps is detailed below.
...@@ -77,13 +78,14 @@ project there. ...@@ -77,13 +78,14 @@ project there.
key. You can consider `bztogl` to be an application that wants to key. You can consider `bztogl` to be an application that wants to
talk to Gitlab. talk to Gitlab.
If you are using gitlab-test.gnome.org, get an API key at You need to create an "admin" account for the migration, to be able to get all
https://gitlab-test.gnome.org/profile/personal_access_tokens — you can user informations (user email etc).
use "`bztogl`" for in the **Name** field of the application you want Get an API key at https://gitlab.xfce.org/profile/personal_access_tokens
to register. Pick an expiration date in the future, and **turn on** — you can use "`bztogl`" for in the **Name** field of the application you want
the checkboxes for **api** and **read_user**, so that `bztogl` can **Turn on** the checkboxes for **api** and **read_user**, so that `bztogl` can
actually modify your test project. Click on the "*Create personal actually modify your test project. Check **sudo** to be able to impersonate
access token*" button. a user during the migration.
Click on the "*Create personal access token*" button.
**WRITE DOWN THE API TOKEN** you get right after clicking that **WRITE DOWN THE API TOKEN** you get right after clicking that
button. You will not be able to see it again if you navigate away button. You will not be able to see it again if you navigate away
...@@ -99,9 +101,14 @@ virtualenv activated with the `activate` command form that example. ...@@ -99,9 +101,14 @@ virtualenv activated with the `activate` command form that example.
Now you can run this: Now you can run this:
```sh ```sh
bztogl --token <your_api_token> --product myproject bztogl --xfce --token <your_api_token> --product Libxfce4util --target-project bugzilla-migration/libxfce4util
``` ```
Be aware that Xfce production on bugzilla start with an Uppercase!
Using the `--production` switch will effectively do the migration ! So be sure to run it on a test `target-project`
You will get some output: You will get some output:
``` ```
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment