odoo13-addon-github-connector 13.0.4.0.0

Synchronize information from Github repositories

This module allows you to:

• Fetch into Odoo social information from Github (Organizations, Teams, Users)

• Fetch into Odoo Code structure information from Github (Repositories, Branches)

• Download source code from Github

• Analyze repository code from rules previously created

Table of contents

• Installation

• Configuration

  • Technical Information

• Usage

  • Initial upload from Github

  • Select branches to download

  • Team / members synchronization

  • Repositories synchronization

  • Fetching the source code

  • Analysis source code

  • Data creation in Github

  • Note

  • Reporting

• Known issues / Roadmap

• Bug Tracker

• Credits

  • Authors

  • Contributors

  • Maintainers

Installation

To install this addon, you need to install some python dependencies

``sudo pip install PyGitHub``
``sudo pip install pygount``
``sudo pip install pathspec``

Analysis source code is generated by https://github.com/roskakori/pygount

Configuration

Once installed, you have to:

1. Open your odoo.conf file and add extra settings to mention Github credentials, and the local path where the source code will be downloaded:

   • source_code_local_path = /workspace/source_code/

Note: you can define the route as environment variable using the key SOURCE_CODE_LOCAL_PATH

Note: make sure that Odoo process has read / write access on that folder

• github_token = your_github_access_token

or

• github_login = your_github_login

• github_password = your_github_password

Note: if token and login/password are provided, the token will be used. The login/password auth will be deprecated by GitHub in the future.

1. Go to ‘Settings’ / ‘Technical’ / ‘Parameters’ / ‘System Parameters’ and define the following values:

   1. github.max_try: number of call to the API before an error is raised. The more unstable/slow your connection, the higher should be this value

   2. git.partial_commit_during_analysis: Set to True if you want to commit the result of the analysis in the database after each repository analysis. We recommend to set to True when you perform the initial download (potentially with a lot of repositories) in order to reduce the size of the transaction

   

2. Go to your(s) user(s) form to add them in the new ‘Connector Github Manager’ groups. The members of this group will have the possibility to run Github synchronization.

Technical Information

This module provides 4 crons that you can enable:

• Synchronize All Organizations and Teams (cron_update_organization)

• Synchronize Branches List for All repositories (cron_update_branch_list)

• Download Source Code for All Github Branches (cron_download_code)

• Analyze Source Code for All Github Branches (cron_analyze_code)

Usage

Initial upload from Github

To fetch information from Github, you have to:

1. go to ‘Github’ / ‘Settings’ / ‘Sync Object’

2. Select the object type you want to synchronize and its Gthub name

   

3. Once done for your organization(s), go to ‘Github’ / ‘Github Commnunity’ / ‘Organizations’

   

4. Optionally, once organization is created, you can create series for your projects. Go to ‘Github’ / ‘Organizations’ / click on your organization / ‘Organization Series’ Tabs

   

Select branches to download

This setting will prevent to download undesired branches, downloading only main branches (releases):

1. In the ‘Settings’ tab, set repositories you don’t want to download (or repositories you want to download). If ‘Specific repositories’ is set, ‘Ignored Repositories’ value is ignored.

2. In the ‘Settings’ tab, set the URL of the ‘External Services’ you use for Continuous Integration and Coverage.

   

3. Once done, click on buttons ‘Syncs’, to synchronize repositories, teams and members. (This process can take a while depending of your size)

   

Team / members synchronization

You can synchronize members teams:

1. Go to ‘Teams’ / tree view / ‘Actions’ / ‘Update from Github’.

   

2. In each team, you can see the members list and the role of the members

   

3. In each team, you can see the repositories list but not the permissions of the team. (See ‘Known Issues’ Section)

   

Repositories synchronization

You can synchronize the branches of your repositories:

1. Go to ‘Repositories’ / tree view / ‘Actions’ / ‘Update from Github’

   

2. In each repository, you can see the main branches list and the size of code source.

   

Fetching the source code

Finally, you can download locally the source code of all your branches:

1. Go to ‘Repository Branches’ / tree view / ‘Actions’ / ‘Download and Analyse Source Code’.

   

2. In the tree view you can update manually source code or refresh analysis.

   

Analysis source code

It’s possible to create custom analysis rules that relate to a GitHub organization, GitHub repository and/or GitHub repository branch to analyze code.

1. Go to ‘Settings’ / ‘Analysis rule groups’ and create records that allow to organize the rules

2. Go to ‘Settings’ / ‘Analysis rules’ and create rules, for example:

1. Name: All code, Group: General, Paths: *

2. Name: Python code, Group: General, Paths: *.py

3. Name: Xml code, Group: General, Paths: *.xml

4. Name: Repository 1, Group: Custom, Paths: /path/

Note: Paths field in ‘Analysis rule’ allow to put multiple paths for line, path format is according to https://git-scm.com/docs/gitignore#_pattern_format

1. Go to GitHub > GitHub Community > Organizations and define Analysis rules (optional)

2. Go to GitHub > GitHub Repository > Repositories and define Analysis rules (optional)

3. Go to GitHub > GitHub Repository > Repository Branches and define Analysis rules (optional)

Analysis source code is executed when ‘Update Source Code Analysis’ button in some ‘Repository Branch’, get all the Analysis rules (Repository + Organization) and analyze code and generate info about it Other option to Analysis source code is in cron called ‘Analyze Source Code for All Github Branches’

You can see in ‘Repository Branch’ / ‘Code Analysis’ the info obtained from analysis rules.

Data creation in Github

You have the possibility to creates two items in Github directly from Odoo

1. Teams:

   1. Go to ‘Settings’ / ‘Create Team in Github’.

   2. Set the information and click on Create in Github.

   3. Odoo will try to create the team. If access right and datas are correct, the creation will be done directly in Github

   4. Later on, a synchronization will be performed, to create the according team in the Odoo instance.

   

2. Repositories:

   1. Go to ‘Settings’ / ‘Create Team in Github’.

   2. Set the information and click on Create in Github.

   

Note

Analysis in this module is basic: for the time being, it just gives branches size.

Nevertheless, you can develop an extra Odoo Custom module to extend analysis function and get extra statistics, depending on your needs.

In that way, you can see the module github_connector_odoo, if your repositories contain Odoo modules.

Reporting

This module provides several reports

Branches by Serie

Sizes by Serie

Repository branch analysis rule

Known issues / Roadmap

• For the time being, Github API doesn’t provide some informations that are available by the classic UI, that includes:

  1. team hierarchy: the field is present in the model github_team.parent_id, but unused.

• Possible improvements:

  1. Create a new module github_connector_website, that could display teams / repositories / branches informations for non logged users.

  2. Analyze commits (author, quantity by series, etc…): this feature has been partially implemented in a V8.0 PR.

  3. Synchronize Pull Request, Issues, Comments: this feature has been partially implemented in a V8.0 PR.

• Refactor the github connector:

  A python library called PyGitHub is available. It could be interesting to use it, instead of using custom code. However, this lib doesn’t provide good access to child object, generating for the time being, unnecessary API calls. For example, updating a repository should call before a call to the parent organization (The current module is so faster).

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

• GRAP

• Akretion

• Tecnativa

Contributors

• Sylvain LE GAL (https://twitter.com/legalsylvain)

• Sébastien BEAU ([e-mail])

• Benoît GUILLOT ([e-mail])

• Enrique Martín ([e-mail])

• Tecnativa:”,

  • Pedro M. Baeza

  • Vicent Cubells

  • Alexandre Díaz

  • Ernesto Tejeda

  • Carlos Roca

  • Víctor Martínez

Maintainers

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/interface-github project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.