Git Branch Odoo Version
| Lines of Code | 795 |
| Technical name | to_git_odoo_version |
| License | OPL-1 |
| Website | https://viindoo.com/apps/modules/18.0/to_git_odoo_version |
| Read description for | v 11.0 v 12.0 v 13.0 v 14.0 v 15.0 v 16.0 v 17.0 v 19.0 |
| Required Apps | Discuss (mail) |
| Included Dependencies | Git Management Viindoo Base Odoo Versions Management SSH Keys Management Product Licenses Config Management |
| Extensions | Odoo Apps Management |
Git branches that know which Odoo version they are
Branches are mapped to Odoo versions - by name, in bulk, or when a URL is added - repositories flag Odoo source code, branches declare the branches they depend on, and an Odoo version lists its branches.
Git Branch Odoo Version (technical name to_git_odoo_version) is an Odoo 18.0 app for Odoo Community and Odoo Enterprise and Viindoo Cloud, built for release manager, developer.
At a Glance
The facts of Git Branch Odoo Version, version 0.1, in one place. Published by Viindoo.
How It Works
Add the repository; Assign Odoo Versions; declare dependencies.
A branch
Odoo version and the branch it depends on.
The repository
Branches 16.0 and 17.0.
The version
Git Branches button.
Its branches
Odoo and the addons repository.
What You Get
Odoo Version on git branches
Assign Odoo Versions in bulk from branch names
Version picked when adding a git URL
Depending and depended branches, same version enforced
Odoo source code and enterprise flags on repositories
Branches listed on the Odoo version
What This App Does Not Do
Read this before you buy. Everything below is something the app deliberately leaves to another app or to you.
Set the version by hand otherwise.
Keep them on the same series.
Works Well With
Apps from the same stack, built to fit this one:
Who Should Use Git Branch Odoo Version?
Release manager
Which branch serves 17.0.
Developer
Dependencies declared, not remembered.
Frequently Asked Questions
What does Git Branch Odoo Version do?
Branches are mapped to Odoo versions - by name, in bulk, or when a URL is added - repositories flag Odoo source code, branches declare the branches they depend on, and an Odoo version lists its branches.
What does Git Branch Odoo Version not do?
Assignment by name needs branch names like 17.0. Set the version by hand otherwise. Dependencies across versions are refused. Keep them on the same series.
Who is Git Branch Odoo Version for?
Release manager: Which branch serves 17.0. Developer: Dependencies declared, not remembered.
Which Odoo version and editions does it support?
Odoo 18.0 - Odoo Community, Odoo Enterprise, Viindoo Cloud. Upgrades to a newer Odoo series are a separate purchase for that series.
What does it depend on?
It installs on top of: to_git, to_odoo_version, to_product_license. Odoo installs them with it.
How do I set it up?
Add the repository; Assign Odoo Versions; declare dependencies.
What works well with it?
Git Management (to_git): The repositories. Odoo Modules (to_odoo_module): Modules discovered in branches.
Can I try it before buying?
Yes - the Live Preview button at the top of this page opens the module's own screen on a working database.
How do I get support?
Write to apps.support@viindoo.com with your Odoo version and the technical name to_git_odoo_version; pre-sales questions go to sales@viindoo.com.
See Git Branch Odoo Version in Action
Live demo: v18demo-int.viindoo.com/web#action=to_git.git_repository_action
Need help with Git Branch Odoo Version?
For questions, implementation support or a custom feature, contact Viindoo.
Pre-Sales & Partnership
sales@viindoo.comUpgrades to a newer Odoo series are a separate purchase for that series.
All Viindoo apps: Viindoo Apps
Technical Requirement
Changes log
0.1 - Latest on the 17.0 line
- Aligned with the 17.0 models and views.
Installation
- Navigate to Apps.
- Search with keyword to_git_odoo_version.
- Press Install.
Instructions
After installing the module, navigate to Git > Git > Git Repository and select the repository that you have created. From here, the new fields to indicate whether this git repository belongs to the Odoo Enterprise version or not, and also the default license version applied to this module is added.
Navigate to Git > Git > Git Branches, and select the checked-out git branch. On the selected branch, the software will add the following information:
- Odoo Version: When you pull code from the repository and checkout a version of this branch, the respective Odoo version will be automatically recognized. In case there is an error while pulling code or checkout a branch, press Assign Odoo Version to search for the suitable Odoo version for this git branch.
- The information will be automatically recognized:
- Is Odoo Source Code;
- Odoo Addons Inside;
- Is Odoo Enterprise.
- Default License Version: The license applied to the source code of this branch.
- Depending Branches: Git branches that this branch depends on.
Note: You need to install the to_git module to pull code to your repository and checkout git branches.
This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file).
You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one).
It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software.
The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
