| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
* Stage multi-arch awx image
- change CI to use `make awx-kube-build` instead of build playbook
- update staging CI to build and push multiarch awx image
- update doc to use `make awx-kube-build` to build awx image
- remove build playbook (no longer used)
|
|
|
|
|
|
|
| |
* Update DOCKER_COMPOSE command
docker-compose will stop being supported soon and this is causing CI flake setting DOCKER_COMPOSE default to `docker compose`
* Give AWX network a static name
|
|
|
| |
speed up CI, also AWX code change won't effect that test
|
| |
|
|
|
| |
Removing Podman var to use Docker again in the collection ci
|
|
|
|
| |
dependent on https://github.com/ansible/awx-ee/pull/235
|
|
|
| |
Promote multi-arch awx manifest
|
|
|
|
|
|
| |
build amd64 and ARM image for
- awx
- awx_devel
- awx_kube_devel
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Allow dev image to build on fork
Fix uppercase repo owner error in CI
example
```
Run docker pull ghcr.io/TheRealHaoLiu/awx_devel:devel
docker pull ghcr.io/TheRealHaoLiu/awx_devel:devel
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
env:
LC_ALL: C.UTF-8
CI_GITHUB_TOKEN: ***
DEV_DOCKER_OWNER: TheRealHaoLiu
COMPOSE_TAG: devel
py_version: 3
invalid reference format: repository name must be lowercase
```
---------
Co-authored-by: Rick Elrod <rick@elrod.me>
|
| |
|
|
|
|
|
|
|
|
| |
The github workflow that we have set up for branch deletion doesn't work:
- the `on: delete` event does not support the `branches:` filter
- the `mode` flag for the aws_s3 module does not have `delete` as one
of the options. The proper option appears to be `delobj`.
|
|
|
| |
Co-authored-by: Hao Liu <44379968+TheRealHaoLiu@users.noreply.github.com>
|
|
|
| |
Co-authored-by: Hao Liu <44379968+TheRealHaoLiu@users.noreply.github.com>
|
| |
|
|
|
|
|
|
| |
* We introduced multi networks to our docker env. The code this replaces
would return both networks' ip addresses concatinated i.e.
'192.168.2.1192.168.2.3'.
|
|
|
|
| |
This has been broken since 20.0.1.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* [CI] Reduce GHA timeouts from 6h default
The goal here is to never interfere with a real run (so most of the
timeout-minutes values seem rather high) but to avoid having 6h long
runs if something goes crazy and never ends.
Signed-off-by: Rick Elrod <rick@elrod.me>
* Do bash hackery instead
Signed-off-by: Rick Elrod <rick@elrod.me>
---------
Signed-off-by: Rick Elrod <rick@elrod.me>
|
|
|
|
|
|
|
| |
--location (-L) parameter will prompt curl to submit a new request if the URL is a redirect.
After moving to galaxy-NG without -L the curl falsely return 302 for any version
Co-authored-by: John Barker <john@johnrbarker.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* allow pytest --migrations to succeed
* We actually subvert migrations from running in test via pytest.ini
--no-migrations option. This has led to bit rot for the sqlite
migrations happy path. This changeset pays off that tech debt and
allows for an sqlite migration happy path.
* This paves the way for programatic invocation of individual migrations
and weaving of the creation of resources (i.e. Instance, Job Template,
etc). With this, a developer can instantiate various database states,
trigger a migration, assert the state of the db, and then have pytest
rollback all of that.
* I will note that in practice, running these migrations is dog shit
slow BUT this work also opens up the possibility of saving and
re-using sqlite3 database files. Normally, caching is not THE answer
and causes more harm than good. But in this case, our migrations are
mostly write-once (I say mostly because this change set violates
that :) so cache invalidation isn't a major issue.
* functional test for migrations on sqlite
* We commonly subvert running migrations in test land. Test land uses
sqlite. By not constantly exercising this code path it atrophies. The
smoke test here is to continuously exercise that code path.
* Add ci test to run migration tests separately, they take =~ 2-3
minutes each on my laptop.
* The smoke tests also serves as an example of how to write migration
tests.
* run migration tests in ci
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are a number of changes here:
- Abstract out a GHA composite action for running the dev environment
- Update the e2e tests to use that new abstracted action
- Introduce a new (matrixed) job for running collection integration
tests. This splits the jobs up based on filename.
- Collect coverage info and generate an html report that people can
download easily to see collection coverage info.
- Do some hacks to delete the intermediary coverage file artifacts
which aren't needed after the job finishes.
Signed-off-by: Rick Elrod <rick@elrod.me>
|
| |
|
|
|
|
|
| |
(#14398)
Signed-off-by: Rick Elrod <rick@elrod.me>
|
| |
|
|
|
|
| |
This reverts commit 3ae6174050900d61e349afb3e804367ba9957720.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
Signed-off-by: Rick Elrod <rick@elrod.me>
|
| |
|
|\
| |
| | |
ci: workflows security hardening
|
| |
| |
| | |
Signed-off-by: Alex <aleksandrosansan@gmail.com>
|
| |
| |
| | |
Signed-off-by: Alex <aleksandrosansan@gmail.com>
|
| |
| |
| | |
Signed-off-by: Alex <aleksandrosansan@gmail.com>
|
| |
| |
| |
| | |
- also will now publish awx image for devel
|
|\ \
| | |
| | | |
Only allow promote and stage to run on the awx repo
|
| | | |
|