I'm really surprised that #TravisCI still exists.

Still using #TravisCI with #GitHub / #GitLab /...? Better don't:
https://news.ycombinator.com/item?id=33906591

Disable its tokens, kick them out and check your repos.

As organization admin review your audit log
https://docs.github.com/en/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization

#security

Seeing news of github revoking personal access tokens after detecting threat actors accessing them. Known details:

- All affected tokens are associated with TravisCI
- No statement from Travis yet on this
- Only data that has been accessed was repo metadata

Please spread word and update if you notice any fresh info, esp from travis

#Github #Security #TravisCI #Travis

From release to support

2019: #Python 3.8

🥇 21 hours: #TravisCI
🥈 20 days: #GitHubActions
🥉 24 days: #AzurePipelines
4️⃣ 25 days: #AppVeyor

2020: Python 3.9

🥇 17 hours: GitHub Actions ⬆️
🥈 20 days: Travis CI ⬇️
🥉 21 days: AppVeyor ⬆️
4️⃣ 22 days: Azure Pipelines ⬇️

2021: Python 3.10

🥇 12 hours: GitHub Actions ↔️
🥈 17 days: Azure Pipelines ⬆️
🥉 28 days: AppVeyor ↔️
4️⃣ 106 days: Travis ⬇️

2022: Python 3.11

🥇 a day: GitHub Actions ↔️
🥈 2 days: Azure Pipelines ↔️
🥉 14 days: AppVeyor ↔️
4️⃣ 28 days: Travis ↔️

#Travis #TravisCI is dying ... its extremely slow today. I feel really sad for it.

I've been using it for years in open source projects. It's the "go to" solution for most of them. And seems it is walking slowly into its grave.

#GitHubActions seem to be the new champion.

@gerazo Szerintem itt egy újabb bekeretezhető mondás. 😂 http://twitter.com/whisperity/status/1336260807819194374 #TravisCI

I just don't want to count the number of repositories I need to migrate out of #TravisCI after their princing update. I am still hoping for a quick U-turn on their side, otherwise I will hardly do anything else this month.

Tried switching from #TravisCI to #GitHub actions for one of my projects cause travis builds have terrible lag lately. Found it quite usable, although there's unfortunately no dashboard of all my build statuses.

Started looking at a Hugo Blog engine again, automated upload to AWS S3 bucket using Travis CI. http://0x32.uk/ #Hugo #travisci

"Technically free software" was a new and very annoying phrase #travisCI

Jesus, still struggling with #python import path on #travisci 😫
https://travis-ci.community/t/django-settings-modules-not-found-modulenotfounderror/4681/5

Dear #Django folks,I struggle on setting up my first coveralls / #travisci integration
https://github.com/Matthias84/papersquirrel/blob/master/.travis.yml

I get: ModuleNotFoundError: No module named 'papersquirrel.settings.ci'
when I fire it up via:
coverage run --source=. manage.py test --settings=papersquirrel.settings.ci
For my local virtualenv it works, but not on travis ... 😢

#python #ci #tests

I stayed up late (early at this point), fighting with #TravisCI's Amazon S3 artifact uploader. I did not win, and I'm very grumpy about that.

:flan_warrior: :flan_rage: :flan_set_fire: :flan_sleep:

Turns out I've been misunderstanding how to use #evm in my #emacs #travisci setup. It's a lot more reliable now I don't need to install cask: https://github.com/stsquad/my-emacs-stuff/commit/4978d7faaa005e00690a3facfb0736563fe60e52

For fun I enabled the #remacs snapshot on my #emacs config #travisci. Turns out it all starts up fine (https://travis-ci.org/stsquad/my-emacs-stuff/jobs/485311706). I guess I should have another go at building remacs and seeing what a #rust powered emacs is like.