home.social

#travisci — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #travisci, aggregated by home.social.

  1. 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

  2. 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

  3. 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

  4. 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

  5. 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

  6. 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. 👇

    claudiokuenzler.com/blog/1421/

  7. 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. 👇

    claudiokuenzler.com/blog/1421/

  8. 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. 👇

    claudiokuenzler.com/blog/1421/

  9. 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. 👇

    claudiokuenzler.com/blog/1421/

  10. 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.

  11. 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.

  12. 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.

  13. 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.

  14. 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.

  15. 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

  16. 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

  17. 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

  18. 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

  19. 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

  20. 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:

    github.com/actions/setup-pytho

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

    app.travis-ci.com/github/hugov

    travis-ci.community/t/add-pyth

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

  21. 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:

    github.com/actions/setup-pytho

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

    app.travis-ci.com/github/hugov

    travis-ci.community/t/add-pyth

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

  22. 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:

    github.com/actions/setup-pytho

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

    app.travis-ci.com/github/hugov

    travis-ci.community/t/add-pyth

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

  23. 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:

    github.com/actions/setup-pytho

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

    app.travis-ci.com/github/hugov

    travis-ci.community/t/add-pyth

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

  24. 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:

    github.com/actions/setup-pytho

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

    app.travis-ci.com/github/hugov

    travis-ci.community/t/add-pyth

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

  25. #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
    github.blog/2023-03-01-github-

  26. released a extension for helping migrate your & CI/CD pipelines to .
    I'll be curious to see how well it works with non-parity features, extensions, etc. Let me know if you try it
    github.blog/2023-03-01-github-

  27. #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
    github.blog/2023-03-01-github-

  28. #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
    github.blog/2023-03-01-github-

  29. 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:

    mstdn.social/@ganzefolge/10948

  30. 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:

    mstdn.social/@ganzefolge/10948

  31. If you really use , 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:

    mstdn.social/@ganzefolge/10948

  32. 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:

    mstdn.social/@ganzefolge/10948

  33. 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:

    mstdn.social/@ganzefolge/10948

  34. 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

  35. 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

  36. 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

  37. 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

  38. 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

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

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

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

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

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

  44. #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.