In the last year I spent quite some time adding automated builds in Travis and added them into the repository (as .travis.yml) - just to see now no builds have been running in the past 8 months!
When looking at the repository through Travis CI, a red error message popped up at the top of the screen:
Builds have been temporarily disabled for public repositories due to a negative credit balance
Yes, Travis CI has moved away from a free to a paid plan service while ago. However for some low key repositories, such as my monitoring plugins, there are almost no builds to do and many of the initial 10'000 free credits are still available:
After having contacted support, I got a fairly quick response to simply log out of Travis CI, log back in and trigger a build. This should clear the error and automated builds should start again.
By doing that, it seems that new permissions are needed in order for Travis to integrate itself into the GitHub repositories:
After authorizing Travis CI on my GitHub account, I forced a new build by using More options -> Trigger build:
And indeed, a new build starts up:
After triggering a manual build on the newly created branch for the PR (I mentioned at the top), the build "icon" can now also be seen next to the PR again:
AWS Android Ansible Apache Apple Atlassian BSD Backup Bash Bluecoat CMS Chef Cloud Coding Consul Containers CouchDB DB DNS Database Databases Docker ELK Elasticsearch Filebeat FreeBSD Galera Git GlusterFS Grafana Graphics HAProxy HTML Hacks Hardware Icinga Icingaweb Icingaweb2 Influx Internet Java KVM Kibana Kodi Kubernetes LXC Linux Logstash Mac Macintosh Mail MariaDB Minio MongoDB Monitoring Multimedia MySQL NFS Nagios Network Nginx OSSEC OTRS Office PGSQL PHP Perl Personal PostgreSQL Postgres PowerDNS Proxmox Proxy Python Rancher Rant Redis Roundcube SSL Samba Seafile Security Shell SmartOS Solaris Surveillance Systemd TLS Tomcat Ubuntu Unix VMWare VMware Varnish Virtualization Windows Wireless Wordpress Wyse ZFS Zoneminder