Automatic import not working with Travis CI

blalop commented 3 years ago

Bug Report

First of all, sorry if this is not the proper way to report this, but I could not find another communication channel to seek for help in this topic.

SUMMARY

From a few months for now, our roles at @idealista are not being automatically published to galaxy. We use travis ci for CI/CD and in the past we configured the webhook according to the docs. And we do that for all our roles, such as the airflow-role's travis config file.

Now, taking a look to "My Imports" in galaxy.ansible.com website, we can see that our last successful auto import has id 821691, as it is the last import with the travis badge appearing in the top right corner. The import can also be checked using the API. We've been publishing manually since then.

But going further, and this is what really bugs me, is that if we take a look at the notifications endpoint logs from galaxy.ansible.com/api:

> curl https://galaxy.ansible.com/api/v1/notifications/ -s | jq '.results | .[] | .created + " " + .travis_build_url'
"2021-07-02T05:48:24.813870Z https://travis-ci.com/idealista/cerebro_role/builds/231548084"
"2021-07-02T05:45:33.319008Z https://travis-ci.com/idealista/prometheus_jmx_exporter_role/builds/231541460"
"2021-07-02T05:37:32.581832Z https://travis-ci.com/avinetworks/ansible-role-aviconfig/builds/231584165"
"2021-07-02T05:35:41.303675Z https://travis-ci.com/avinetworks/ansible-role-avisdk/builds/231584133"
"2021-07-02T05:20:05.925344Z https://travis-ci.com/idealista/solr_role/builds/231541459"
"2021-07-02T04:51:18.945376Z https://travis-ci.com/delphix/ansible-target-host/builds/231582716"
"2021-07-02T03:30:49.683212Z https://travis-ci.com/idealista/prom2teams_role/builds/231541378"
"2021-07-02T03:24:49.130847Z https://travis-ci.com/pmav99/ansible-role-compile_grass/builds/231579984"
"2021-07-02T03:22:53.429803Z https://travis-ci.com/idealista/vips_role/builds/231541323"
"2021-07-02T03:16:10.546951Z https://travis-ci.com/idealista/mysql_role/builds/231541322"

And assuming that this logs are chronologically sorted, it seems that no one has been invoking this endpoint since 2021-07-02 (when our last import was made). So, does this means that no one is calling it properly? Could it be the transition from travis-ci.org to travis-ci.com?

STEPS TO REPRODUCE

Just configure Travis CI to use the Ansible Galaxy's webhook to automatically import any role into Galaxy.

EXPECTED RESULTS

Automatic role import.

ACTUAL RESULTS

No automatic role import, as it has to be manually imported. This also happens to our new roles.

eifelmicha commented 3 years ago

@blalop We experienced the same Issue. A workaround is to trigger the import via Ansible Galaxy command:

ansible-galaxy role import --api-key $GALAXY_API_KEY $GITHUB_USERNAME $GITHUB_REPOSITORY

GITHUB_USERNAME could also be GITHUB_ORGANIZATION

DrPsychick commented 2 years ago

It seems there are no more notifications since late 2021? Is that possible?

https://galaxy.ansible.com/api/v1/notifications/

JensTimmerman commented 1 year ago

I'm also seeing this issue, any updates on if this is going to get fixed? Is there a workaround that's not manually importing on every release?

ansible / galaxy