allura-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jon Schewe <jpsch...@mtu.net>
Subject Re: Status of allura import
Date Fri, 12 Apr 2013 01:23:05 GMT
I don't have any other planned improvements right now. Although I'd be
happy to go over the changes that you are planning, if that helps.


On Mon, Apr 8, 2013 at 4:54 PM, Dave Brondsema <dave@brondsema.net> wrote:

> Hey Jon,
>
> We're thinking about smoothing out this process for other SourceForge
> projects.
>  Automating a lot of the things you listed as "manual".  Just wanted to
> mention
> this in case you were planning on making any further improvements, I don't
> want
> us to duplicate anything or cause conflicts.
>
> -Dave
>
> On 3/27/13 6:56 PM, Jon Schewe wrote:
> > Here are my notes that I used to track my progress doing this migration.
> I
> > needed to make some changes to allura_import.py, those changes are
> reflected in
> > the pull request for allura ticket 6020. One big downside to the new
> tracker is
> > the lack of ability to sort the saved search results by priority.
> >
> > Some python modules needed to be installed, but I don't remember which
> ones
> > beyond the following:
> >   * python-paste
> >
> > Steps
> >   * notify developers of the potential migration
> >   * Migrate the wiki manually - there are some scripts on gist to help wi
> > th this, although I didn't end up using them.
> >     * <https://gist.github.com/619537>
> >     * <https://gist.github.com/1286682>
> >   * Update website redirection.
> >   * Notify all developers of the migration.
> >   * Remove ticket write permissions
> >   * Start migration.
> >   * Use `~/src/allura-git/scripts/trac_export.py` to export the tickets
> to
> > allura-import.json
> >    * ./scripts/trac_export.py --no-attachments -o
> > ~/projects/fll-sw/allura-import.json --only-tickets -v
> > https://sourceforge.net/apps/trac/fll-sw/
> >     * Keep repeating this until it doesn't fail, it seems to timeout
> quite a bit
> >   * Request import API key
> >   * Use `~/src/allura-git/scripts/allura_import.py` with `user_map.json`
> and
> > allura-import.json to import tickets
> >     * PYTHONPATH=~/src/allura-git/Allura
> >     * export PYTHONPATH
> >     * python ~/src/allura-git/scripts/allura_import.py \
> >       -a API \
> >       -s SECRET \
> >       -p fll-sw \
> >       -t issues \
> >       -u https://sourceforge.net \
> >       --user-map=user_map.json \
> >       --verbose \
> >       allura-import.json
> >   * Manually add milestones
> >   * Manually pull the attachments for tickets.
> >     * worked from trac files backup, didn't have many so manually worked
> >   * Update wiki documentation for where to file bugs
> >   * Notify developers
> >
> >
> > On Wed, Mar 27, 2013 at 10:48 AM, Jon Schewe <jpschewe@mtu.net
> > <mailto:jpschewe@mtu.net>> wrote:
> >
> >     Thanks, it looks like all of the information went in. I'll be
> posting the
> >     steps I used and references to the tickets I filed to get the import
> to
> >     work. I am disappointed that the saved searches can't sort on
> priority.
> >
> >
> >     On Wed, Mar 27, 2013 at 8:10 AM, Dave Brondsema <dave@brondsema.net
> >     <mailto:dave@brondsema.net>> wrote:
> >
> >         It might take a minute or two for search indexes to be updated.
>  It
> >         looks like
> >         search includes your imported tickets now.  Also, the API
> endpoint at
> >         https://sourceforge.net/rest/p/fll-sw/issues just lists a
> little bit of
> >         info for
> >         each ticket.  If you want an API endpoint for full details on a
> ticket,
> >         just add
> >         the number to the URL like:
> https://sourceforge.net/rest/p/fll-sw/issues/1
> >
> >         On 3/26/13 7:24 PM, Jon Schewe wrote:
> >         > Wait, I spoke too soon. In my email came a link to the ticket
> and that
> >         shows
> >         > more information.
> >         > https://sourceforge.net/p/fll-sw/issues/1/
> >         >
> >         >
> >         > On Tue, Mar 26, 2013 at 6:23 PM, Jon Schewe <jpschewe@mtu.net
> >         <mailto:jpschewe@mtu.net>
> >         > <mailto:jpschewe@mtu.net <mailto:jpschewe@mtu.net>>>
wrote:
> >         >
> >         >     OK, I hacked up a fix that creates a new hash for the
> document to
> >         import:
> >         >                 doc_import={}
> >         >                 doc_import['trackers'] = {}
> >         >                 doc_import['trackers']['default'] = {}
> >         >                 doc_import['trackers']['default']['artifacts']
> =
> >         [ticket_in]
> >         >
> >         >     Now I can import a ticket. I can see it
> >         >     at https://sourceforge.net/rest/p/fll-sw/issues, but not
> >         >     at
> >
> https://sourceforge.net/p/fll-sw/issues/search/?q=status%3Awont-fix+or+status%3Aclosed
> >         >
> >         >     It also looks like most of the information didn't get
> imported.
> >         That's not
> >         >     going to be very helpful. This is the raw JSON for the
> ticket that was
> >         >     imported. I would have expected the comments, milestone,
> status,
> >         submitter
> >         >     to make it in.
> >         >       {
> >         >         "assigned_to": "jpschewe",
> >         >         "cc": "",
> >         >         "class": "ARTIFACT",
> >         >         "comments": [
> >         >           {
> >         >             "class": "COMMENT",
> >         >             "comment": "  * **milestone** set to _Parking
> Lot_\n\n",
> >         >             "date": "2010-10-02T21:41:54Z",
> >         >             "submitter": "jpschewe"
> >         >           },
> >         >           {
> >         >             "class": "COMMENT",
> >         >             "comment": "  * **owner** set to _jpschewe_\n  *
> >         **status** changed
> >         >     from _new_ to _accepted_\n\n",
> >         >             "date": "2010-10-02T21:51:55Z",
> >         >             "submitter": "jpschewe"
> >         >           },
> >         >           {
> >         >             "class": "COMMENT",
> >         >             "comment": "  * **status** changed from _accepted_
> to
> >         _closed_\n  *
> >         >     **resolution** set to _invalid_\n  * **component** set to
> >         _General_\n\n",
> >         >             "date": "2010-10-02T22:58:37Z",
> >         >             "submitter": "jpschewe"
> >         >           }
> >         >         ],
> >         >         "component": "General",
> >         >         "date": "2010-09-21T01:18:00Z",
> >         >         "date_updated": "2010-10-02T22:58:37Z",
> >         >         "description": "testing MyLyn",
> >         >         "id": 1,
> >         >         "keywords": "",
> >         >         "milestone": "Parking Lot",
> >         >         "priority": "major",
> >         >         "resolution": "invalid",
> >         >         "status": "closed",
> >         >         "submitter": "jpschewe",
> >         >         "summary": "test ticket",
> >         >         "type": "defect"
> >         >       }
> >         >
> >         >
> >         >
> >         >     On Tue, Mar 26, 2013 at 5:54 PM, Jon Schewe <
> jpschewe@mtu.net
> >         <mailto:jpschewe@mtu.net>
> >         >     <mailto:jpschewe@mtu.net <mailto:jpschewe@mtu.net>>>
> wrote:
> >         >
> >         >         Looks like tickets_in should be set to doc in my case.
> >         Although line 80
> >         >         is now giving me problems as it looks like you're
> trying to
> >         reuse the
> >         >         JSON document to submit and it's not working because
> it's not
> >         formatted
> >         >         as expected.
> >         >
> >         >
> >         >         On Tue, Mar 26, 2013 at 5:47 PM, Jon Schewe <
> jpschewe@mtu.net
> >         <mailto:jpschewe@mtu.net>
> >         >         <mailto:jpschewe@mtu.net <mailto:jpschewe@mtu.net>>>
> wrote:
> >         >
> >         >             So far it's going poorly:
> >         >
> >         >             Traceback (most recent call last):
> >         >               File
> >         "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> >         >             line 123, in <module>
> >         >                 main()
> >         >               File
> >         "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> >         >             line 51, in main
> >         >                 verbose=options.verbose)
> >         >               File
> >         "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> >         >             line 69, in import_tracker
> >         >                 tickets_in =
> doc['trackers']['default']['artifacts']
> >         >             TypeError: list indices must be integers, not str
> >         >
> >         >             File to import is attached.
> >         >
> >         >
> >         >
> >         >             On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe
> >         <jpschewe@mtu.net <mailto:jpschewe@mtu.net>
> >         >             <mailto:jpschewe@mtu.net <mailto:jpschewe@mtu.net>>>
> wrote:
> >         >
> >         >                 I'll try. Should I post them back to the list?
> >         >
> >         >
> >         >                 On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen
> >         <rbowen@rcbowen.com <mailto:rbowen@rcbowen.com>
> >         >                 <mailto:rbowen@rcbowen.com
> >         <mailto:rbowen@rcbowen.com>>> wrote:
> >         >
> >         >                     So, I see you've got a new ticket open
> about this,
> >         which
> >         >                     seems to indicate that you're making
> progress. I was
> >         >                     wondering if we could persuade you to take
> really
> >         good notes
> >         >                     and produce some docs of how this process
> works?
> >         >
> >         >                     --Rich
> >         >
> >         >                     On Feb 23, 2013, at 4:53 PM, Jon Schewe
> wrote:
> >         >
> >         >>                     Things have settled down on my project a
> bit now,
> >         so I've
> >         >>                     gone ahead with the migration. I haven't
> migrated the
> >         >>                     tickets yet because the code link is
> broken. If
> >         anyone has
> >         >>                     any insight into this, it would be much
> appreciated.
> >         >>
> https://sourceforge.net/p/allura/tickets/5844/
> >         >>
> >         >>                     Once this is resolved I'll try the ticket
> import.
> >         >>
> >         >>
> >         >>                     On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen
> >         >>                     <rbowen@rcbowen.com <mailto:
> rbowen@rcbowen.com>
> >         <mailto:rbowen@rcbowen.com <mailto:rbowen@rcbowen.com>>>
wrote:
> >         >>
> >         >>
> >         >>                         On Dec 5, 2012, at 3:17 PM, Jon
> Schewe wrote:
> >         >>
> >         >>>                         I'm not sure how I would go about
> creating a
> >         test
> >         >>>                         project on SourceForge. I'm not
> setting up
> >         my own
> >         >>>                         Allura instance, I'm using the one
on
> >         SourceForge.
> >         >>>
> >         >>
> >         >>                         Go to http://sf.net/create and click
> the
> >         Create Your
> >         >>                         Project button. That'll get you
> started.
> >         >>
> >         >>                         --
> >         >>                         Rich Bowen
> >         >>                         rbowen@rcbowen.com
> >         <mailto:rbowen@rcbowen.com> <mailto:rbowen@rcbowen.com
> >         <mailto:rbowen@rcbowen.com>> :: @rbowen
> >         >>                         rbowen@apache.org <mailto:
> rbowen@apache.org>
> >         <mailto:rbowen@apache.org <mailto:rbowen@apache.org>>
> >         >>
> >         >>
> >         >>
> >         >>
> >         >>
> >         >>
> >         >>
> >         >>
> >         >>
> >         >>                     --
> >         >>                     http://mtu.net/~jpschewe
> >         >>
> >         >
> >         >                     --
> >         >                     Rich Bowen
> >         >                     rbowen@rcbowen.com <mailto:
> rbowen@rcbowen.com>
> >         <mailto:rbowen@rcbowen.com <mailto:rbowen@rcbowen.com>> ::
> @rbowen
> >         >                     rbowen@apache.org <mailto:
> rbowen@apache.org>
> >         <mailto:rbowen@apache.org <mailto:rbowen@apache.org>>
> >         >
> >         >
> >         >
> >         >
> >         >
> >         >
> >         >
> >         >
> >         >
> >         >                 --
> >         >                 http://mtu.net/~jpschewe
> >         >
> >         >
> >         >
> >         >
> >         >             --
> >         >             http://mtu.net/~jpschewe
> >         >
> >         >
> >         >
> >         >
> >         >         --
> >         >         http://mtu.net/~jpschewe
> >         >
> >         >
> >         >
> >         >
> >         >     --
> >         >     http://mtu.net/~jpschewe
> >         >
> >         >
> >         >
> >         >
> >         > --
> >         > http://mtu.net/~jpschewe
> >         >
> >
> >
> >
> >         --
> >         Dave Brondsema : dave@brondsema.net <mailto:dave@brondsema.net>
> >         http://www.brondsema.net : personal
> >         http://www.splike.com : programming
> >                       <><
> >
> >
> >
> >
> >     --
> >     http://mtu.net/~jpschewe
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
>
>
>
> --
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
>               <><
>



-- 
http://mtu.net/~jpschewe

Mime
View raw message