Skip to content
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

CI - linters and changelog github actions workflow #410

Merged
merged 2 commits into from
Nov 6, 2023

Conversation

abikouo
Copy link
Collaborator

@abikouo abikouo commented Apr 20, 2023

CI migration from zuul to GHA

@abikouo
Copy link
Collaborator Author

abikouo commented Apr 20, 2023

recheck

@softwarefactory-project-zuul
Copy link
Contributor

This change depends on a change that failed to merge.

Change ansible/ansible-zuul-jobs#1789 is needed.

@mariolenz
Copy link
Collaborator

There already is a test for a changelog: #406 / #433

For the linter test, I don't understand why you use abikouo/github_actions/.github/workflows/tox-linters.yml@tox_linters. It looks like there is one in ansible-network/github_actions. I think it would be better to use this one.

Actually, I think it would be best to have linting in ansible-collections/collection_template and we could just copy it it to this collection. Maybe you should create a PR there to implement a default linting CI workflow ;-)

@abikouo
Copy link
Collaborator Author

abikouo commented Nov 6, 2023

There already is a test for a changelog: #406 / #433

For the linter test, I don't understand why you use abikouo/github_actions/.github/workflows/tox-linters.yml@tox_linters. It looks like there is one in ansible-network/github_actions. I think it would be better to use this one.

Actually, I think it would be best to have linting in ansible-collections/collection_template and we could just copy it it to this collection. Maybe you should create a PR there to implement a default linting CI workflow ;-)

@mariolenz this PR needs some updates.
Indeed, the changelog workflow added here is not valid anymore as there is already one.
And yes we should not reference action from personal repos.

Copy link

codecov bot commented Nov 6, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (ec973b9) 35.67% compared to head (3259851) 35.67%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #410   +/-   ##
=======================================
  Coverage   35.67%   35.67%           
=======================================
  Files         143      143           
  Lines       11305    11305           
  Branches     2291     2291           
=======================================
  Hits         4033     4033           
  Misses       7197     7197           
  Partials       75       75           
Flag Coverage Δ
sanity 35.67% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

Copy link
Collaborator

@mariolenz mariolenz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm no GHA expert but as far as I can see this LGTM.

@alinabuzachis What do you think?

@mariolenz
Copy link
Collaborator

Depends-On: ansible/ansible-zuul-jobs#1789

I've removed this. I think it makes more sense if removing those tests from Zuul should depend on implementing them here in the collection instead of the other way around ;-)

Copy link
Contributor

Build failed (gate pipeline). For information on how to proceed, see
http://docs.openstack.org/infra/manual/developers.html#automated-testing

https://ansible.softwarefactory-project.io/zuul/buildset/f816da8c9beb48d2aad2edd775f0e067

✔️ build-ansible-collection SUCCESS in 10m 38s
✔️ ansible-tox-linters SUCCESS in 20m 13s
ansible-test-sanity-docker-devel FAILURE in 13m 45s (non-voting)
ansible-test-sanity-docker-milestone FAILURE in 12m 17s (non-voting)
ansible-test-sanity-docker-stable-2.9 POST_FAILURE in 28m 47s
✔️ ansible-test-sanity-docker-stable-2.10 SUCCESS in 14m 45s (non-voting)
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 22m 28s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 19m 56s
✔️ ansible-test-sanity-docker-stable-2.13 SUCCESS in 17m 26s
✔️ ansible-test-sanity-docker-stable-2.14 SUCCESS in 19m 30s
✔️ tox-cloud-refresh-examples-vmware SUCCESS in 11m 30s
✔️ ansible-galaxy-importer SUCCESS in 5m 16s

@mariolenz
Copy link
Collaborator

regate

Copy link
Contributor

Build succeeded (gate pipeline).
https://ansible.softwarefactory-project.io/zuul/buildset/1612a2b7ce0a49379f1823eb6214b456

✔️ build-ansible-collection SUCCESS in 17m 22s
✔️ ansible-tox-linters SUCCESS in 17m 01s
ansible-test-sanity-docker-devel FAILURE in 11m 53s (non-voting)
ansible-test-sanity-docker-milestone FAILURE in 11m 18s (non-voting)
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 16m 06s
✔️ ansible-test-sanity-docker-stable-2.10 SUCCESS in 16m 12s (non-voting)
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 14m 50s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 13m 33s
✔️ ansible-test-sanity-docker-stable-2.13 SUCCESS in 11m 50s
✔️ ansible-test-sanity-docker-stable-2.14 SUCCESS in 13m 24s
✔️ tox-cloud-refresh-examples-vmware SUCCESS in 11m 11s
✔️ ansible-galaxy-importer SUCCESS in 4m 48s

Copy link
Contributor

Pull request merge failed: Resource not accessible by integration, You may need to manually rebase your PR and retry.

@mariolenz mariolenz merged commit 79e8a98 into ansible-collections:main Nov 6, 2023
9 checks passed
@mariolenz
Copy link
Collaborator

Cool, we now also have a GHA linting workflow. Thanks @abikouo!

softwarefactory-project-zuul bot pushed a commit to ansible/ansible-zuul-jobs that referenced this pull request Nov 8, 2023
vmware_rest: Remove 2.13 / 2.14 sanity tests

Depends-On: #1830
Moving 2.13 / 2.14 sanity tests to GHA.
cc @alinabuzachis
edit:
Also remove linting: ansible-collections/vmware.vmware_rest#410

Reviewed-by: Alina Buzachis
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants