#travisci — Public Fediverse posts

Apr 2015: Git repo
Aug 2016: #GitHub project created
Jan 2017: Mailing list
Feb 2017: Coocook.org registered
Feb 2017: adopted #TravisCI
mid 2017: 1st use at event with 100s of people
Jan 2018: open for self registration
Apr 2020: integration of #Bootstrap
Apr 2021: last notification from TravisCI
Jun 2022: move to #GitLab
Sep 2022: GitLab CI pipeline
Dec 2022: joined #Mastodon
Jul 2023: 1st #ReactJS UI elements
Feb 2024: 1st security flaw, fixed within 13h
Sep 2024: purchase list with 1 click

Apr 2015: Git repo
Aug 2016: #GitHub project created
Jan 2017: Mailing list
Feb 2017: Coocook.org registered
Feb 2017: adopted #TravisCI
mid 2017: 1st use at event with 100s of people
Jan 2018: open for self registration
Apr 2020: integration of #Bootstrap
Apr 2021: last notification from TravisCI
Jun 2022: move to #GitLab
Sep 2022: GitLab CI pipeline
Dec 2022: joined #Mastodon
Jul 2023: 1st #ReactJS UI elements
Feb 2024: 1st security flaw, fixed within 13h
Sep 2024: purchase list with 1 click

An automated CI/CD pipeline, which uses #TravisCI in the background, stopped working.

The error of the build output referred to an expired repository key of the #MongoDB repositories. While the dist image itself needs to be fixed by Travis CI, a quick workaround is to disable the MongoDB repos inside the build process. Here's how. 👇

https://www.claudiokuenzler.com/blog/1421/travis-ci-builds-fail-expired-key-error-mongodb-apt-repository

Busy migrating my #FOSS projects from #TravisCI to #CircleCI.

Travis is super expensive and with the free offering for my FOSS projects out the window, it just doesn't make sense for me anymore.

Busy migrating my #FOSS projects from #TravisCI to #CircleCI.

Travis is super expensive and with the free offering for my FOSS projects out the window, it just doesn't make sense for me anymore.

And the last two releases saw GHA/AP improve their lead:

2022: Python 3.11

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

2023: Python 3.12

🥇 13 hours: @github Actions ↔️
🥇 13 hours: Azure Pipelines ↔️
🥉 20 days: Travis CI ⬆️
4️⃣ 28 days: AppVeyor ⬇️

And GitHub Actions already has 3.13 alpha available!

#Python #CI #CImedals #medals #GitHubActions #AzurePipelines #TravisCI #AppVeyor #Python311 #Python312 #Python313

And the last two releases saw GHA/AP improve their lead:

2022: Python 3.11

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

2023: Python 3.12

🥇 13 hours: @github Actions ↔️
🥇 13 hours: Azure Pipelines ↔️
🥉 20 days: Travis CI ⬆️
4️⃣ 28 days: AppVeyor ⬇️

And GitHub Actions already has 3.13 alpha available!

#Python #CI #CImedals #medals #GitHubActions #AzurePipelines #TravisCI #AppVeyor #Python311 #Python312 #Python313

Python 3.13 alpha 1 was released on Friday and GitHub Actions added it on Monday 🚀

If you're up for some early testing, here's how:

https://github.com/actions/setup-python/issues/742#issuecomment-1764118264

Meanwhile, Travis CI still don't have 3.12.0 final, they're still beta 1+ from May, 2023...

https://app.travis-ci.com/github/hugovk/test/jobs/611062434#L212

https://travis-ci.community/t/add-python-3-12/14006?u=hugovk

#Python #Python3.12 #Python3.13 #GitHubActions #CI #GitHub #TravisCI

Python 3.13 alpha 1 was released on Friday and GitHub Actions added it on Monday 🚀

If you're up for some early testing, here's how:

https://github.com/actions/setup-python/issues/742#issuecomment-1764118264

Meanwhile, Travis CI still don't have 3.12.0 final, they're still beta 1+ from May, 2023...

https://app.travis-ci.com/github/hugovk/test/jobs/611062434#L212

https://travis-ci.community/t/add-python-3-12/14006?u=hugovk

#Python #Python3.12 #Python3.13 #GitHubActions #CI #GitHub #TravisCI

#GitHub released a #CLI extension for helping migrate your #AzureDevOps #Jenkins #CircleCI #GitLab & #TravisCI CI/CD pipelines to #GitHubActions.
I'll be curious to see how well it works with non-parity features, extensions, etc. Let me know if you try it
https://github.blog/2023-03-01-github-actions-importer-is-now-generally-available/

#GitHub released a #CLI extension for helping migrate your #AzureDevOps #Jenkins #CircleCI #GitLab & #TravisCI CI/CD pipelines to #GitHubActions.
I'll be curious to see how well it works with non-parity features, extensions, etc. Let me know if you try it
https://github.blog/2023-03-01-github-actions-importer-is-now-generally-available/

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

If you really use #TravisCI, now should be the time to switch. They were sold and the new owners run it rather bad. Third time they lost github tokens in two years:

https://mstdn.social/@ganzefolge/109484052994865843

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

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 ↔️

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 ↔️

#introduction greetings all, I'm a Berlin-based Italian/Australian from Sydney who arrived in Berlin to finish a doctoral research project 10 years ago and never left.

Currently I'm working as a Senior Software Engineer at #GitLab, an open source DevOps platform, after stints at #ThoughtWorks, #Rasa, and #TravisCI. I owe my career to the awesome humans of the Berlin ruby community, and to all my colleagues along the way.

I like taking photos, reading books, and watching TV.

#introduction greetings all, I'm a Berlin-based Italian/Australian from Sydney who arrived in Berlin to finish a doctoral research project 10 years ago and never left.

Currently I'm working as a Senior Software Engineer at #GitLab, an open source DevOps platform, after stints at #ThoughtWorks, #Rasa, and #TravisCI. I owe my career to the awesome humans of the Berlin ruby community, and to all my colleagues along the way.

I like taking photos, reading books, and watching TV.

Travis CI security flaw potentially leaves thousands of open source projects exposed https://buff.ly/3nB9yUE #security #TravisCI #tools #OpenSource #SoftwareDevelopment #FOSS #TravisCI

Travis CI flaw exposed secrets of thousands of open source projects - Enlarge (credit: Getty Images)
A security flaw in Travis CI potentially exposed... - https://arstechnica.com/?p=1794622 #vulnerability #opensource #bitbucket #dataleak #travisci #secrets #biz&it #github #tech

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.

With #TravisCI basicly (silently) killing OSS support it's time to take some serious effort to move quickly all the repos to github actions
I seriously supposed to have other priorities, but there is no much choice 🙄

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

Migrating from #TravisCI to #AzurePipelines? @Ryan_Levick has some tips to show you: https://www.youtube.com/watch?v=2RNO99VH1UA