GitHub sync Success

User tests: Successful: Unsuccessful:

avatar elkuku
elkuku
26 Jan 2014

This will refactor the get project command and remove the project specific sub commands comments, events, issues, labels and milestones.
The command is now meant to be run on a periodic base, looking for modified issue descriptions and comments, while making as few requests as possible.

During the initial import of issues, when setting up the project, a large amount of requests might be necessary, depending on the amount of issues and their comments.
A mechanism has been implemented to allow more then one account to be used in those circumstances.
To achieve this, the GitHub object has been extended to check for the remaining GitHub rate limit.

New options:

  • issue Process only a single issue.
  • range_from First issue to process.
  • range_to Last issue to process.
  • force f Force an update even if the issue has not changed.

A new column updated_date as been added to the #__activities table, mainly to check for modified comments on GitHub

avatar elkuku elkuku - open - 26 Jan 2014
avatar b2z
b2z - comment - 28 Jan 2014

Looks good. Need to test it :)

avatar elkuku
elkuku - comment - 28 Jan 2014

Oh, this will also Fix #213 and #238

avatar elkuku elkuku - change - 29 Jan 2014
Labels Added: GitHub sync
avatar elkuku
elkuku - comment - 29 Jan 2014

So I deployed this branch to a server and set up a cron job to run the get project command hourly for both projects. Another one is set up for the update server command running every 10 minutes.
Both are running just fine.
@mbabker and @b2z have been added as admins so they might have a look at the cron log.
TEST server: http://jissues-nikp3h.rhcloud.com/

avatar mbabker
mbabker - comment - 1 Feb 2014

Well, let's do it!

avatar mbabker mbabker - reference | - 1 Feb 14
avatar mbabker mbabker - merge - 1 Feb 2014
avatar mbabker mbabker - close - 1 Feb 2014
avatar elkuku elkuku - head_ref_deleted - 1 Feb 2014

Add a Comment

Login with GitHub to post a comment