forked from Tecnativa/doodba
-
Notifications
You must be signed in to change notification settings - Fork 0
[pull] master from Tecnativa:master #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
pull
wants to merge
330
commits into
S3b4Bus0:master
Choose a base branch
from
Tecnativa:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+5,862
−1,624
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added a test to run pg_dump, which will fail if the server is newer than the client.
Dockerfiles vscode autoformatter is ugly. Enable autoformat only for python.
With this patch, if a repo has a README file (for example) and it's included as `*`, it will not fail saying that addon is missing. @Tecnativa TT20969
This is a useful case for Doodba users, where possibly you want to pre-merge a patch done for Odoo v11 into your Odoo v13 deployment, before Odoo approves it. Using just git branches is not much helpful in this case because no git history is shared, so conflicts would arise always. In fact, this might be the best way to apply merges *always*. That's to be investigated. Upstream support for diffs and patches is being tracked in acsone/git-aggregator#34, but in the mean time this option is available today, so it's better to make it more obvious. @Tecnativa TT19951
* Fix README: slightly incorrect example of generated repos.yaml * Add new ENV node in addons.yaml Fix #258
Before this patch: - When an addon was included with `--with`, its dependencies were not detected. - When an addon was excluded with `--without` but it was a dependency of another addon that was included, it ended up in the final list (although explicitly excluded). TT20969 TT20963
This makes logs actually useful because they will expand and print the commands being executed.
It's common that you want to test enterprise addons in a separate fashion from the rest of addons, same as core, extra or private addons. To support that, from now on, a repo called `enterprise` will be excluded when you run `addons` with `--extra` flag. Just add `--enterprise` explicitly if you need it. TT20969
fix link in README
This breaking change will follow Tecnativa/doodba-scaffolding#56. @Tecnativa TT20505
Co-authored-by: Jairo Llopis <[email protected]>
It turns out that an arguments syntax error exits with 0x2, which is the same exit code I chose to indicate there are no addons. This way, there's no way to know if there was a real error or there were simply no addons found. So I change the exit code for addons not found to 0x4. Tecnativa/doodba-qa#17 won't be able to complete without this patch. TT21246
Running production before creating inverseproxy leads to following error ERROR: Network inverseproxy_shared declared as external, but could not be found. Please create the network manually using `docker network create inverseproxy_shared` and try again.
This helps keeping a more consistent README code. Includes the change and it execution.
Python 3.5 is flawed. It affects Odoo badly as shown in odoo/odoo#20158. Odoo claims to have included a workaround for that in their code, but that simply doesn't work according to real world tests. The only fix is to update Python version, so here's the update. @Tecnativa TT21841
command "addons" doesn't accept modules as positional arguments. Example: $ docker-compose run --rm odoo addons init --test web_debranding doodba INFO: Executing addons init --test web_debranding usage: addons [-h] [-c] [-d] [-e] [-f] [-i] [-n] [-p] [-s SEPARATOR] [-t] [-x] [-w WITH_] [-W WITHOUT] {init,update,list} addons: error: unrecognized arguments: web_debranding
* implement geoip installation with account id and license key * fix, use curl instead of wget (wget is not available in 10.0 and 13.0) * skip geoip test if no credentials provided in environment * fix, follow redirects in curl * fix, correct output parameter for curl * fix: always install geoipupdater in base image * enable configuring geoip in build and environment * fix test for unconfigured geoipupdate * use log instead of echo in shell scripts * fix, remove unused onbuild args and env, declare env variables * fix: install geoip2 pip dependency for all versions * Move geoip script to plumbum * fix readme * move ARG and ENV to suggested places This also installs plumbum by default inside doodba and checks its presence. See #7 (comment). Co-authored-by: Jairo Llopis <[email protected]>
These are moved now to Tecnativa/doodba-copier-template#32. This way, no more remainders of doodba-scaffolding exist anymore.
This is a requirement to be able to use click-odoo-makepot @Tecnativa TT23467
It seems the tested module `web_debranding` was removed from it-projects-llc/misc-addons repo (which is renamed now, BTW), so I hack the `ODOO_VERSION` env variable to use it as a commit which contains that module. Also I'm pinning eslint<7 for v12, or it uses unsupported syntax and fails the test.
Travis, for some weird reason, stopped pushing images to the Docker Hub like 2 months ago. Its syntax is awful and it's faster for me to dump it than fix it. BTW this will fix #295. @Tecnativa TT23467
[UPD] Test environment
[FIX] Set ubuntu 24.04 on test environment
[FIX] Pip packages installation
[FIX] 15.0 build
Revert quick fixes
[FIX] Test Environment: Don't use published 'onbuild' image
[IMP] Using test images on test-pr stage
[FIX] Point Buster APT sources to archive
[DCK] Use https to get pgdg
… cleanup) with #578 the images for 16.0 and 17.0 were changed to use 2 layers instead of one layer
[FIX][16.0][17.0][18.0] Dockerfile: restore single layer install
[ADD] Odoo 19.0
in case the image was not pushed to registries in the build-push-pr step. also skip building onbuild images in tests if image got pushed in build-push-pr step.
…s_base_search_fuzzy_18.0 [IMP] tests: activate test_dependencies_base_search_fuzzy for 18.0
[IMP] tests: assert successful image build before testing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )