OctoLinker VS Travis CI.com

GitHub Repo | Chrome Store | Website

OctoLinker is a GitHub browser extension that converts language-specific statements such as include, require, or import into links. It is packed with the capability to connect dependencies defined in files such as package.json, composer.json, Gemfile, or requirements.txt to their corresponding GitHub project page.

Respository - OctoLinker

The OctoLinker enables easy navigation between project codes, transforming language-specific instructions (such as include, require or import) into links that redirect to the file referenced in the code or to an external site.

And it became quite a good conversation like, well, I wish that it would also update my GitHub Actions tree because of my Travis CI tree because I wish it did this, I wish it did that. I think the biggest users were the WG, the browser rendering engine people. They had some requirements they couldn't use until they were fixed. So we had a really good conversation there. But yeah, tech is never the hard part; it's always the people.

This tool is written in Golang and still used travis-ci as CI. Furthermore, some parts of the release process were still manually, such as uploading the assets to a GitHub release and generating the release notes. We wanted to have this automated.

You should use a service like Travis CI. Much easier than the route you are taking.

https://fastlane.tools https://danger.systems https://www.sonarqube.org https://codemagic.io/ https://travis-ci.org

Datree has really good integration with CicleCi, TravisCi, GitHub Actions, GitLab also.

For the majority of their work, they need tools for Version Control (GitHub, GitLab), Container Management(Kubernetes, Docker), APM (Elastic, AppDynamics), Deployments and Server Monitoring(Datadog), CI/CD & Test Automation (Jenkins, TravisCI, CircleCI, GitHub Actions), etc..

Known tools: Jenkins Alternatives: Github Actions, Gitlab , CircleCI, TravisCI, ArgoCD

First of all go to travis-ci.org and sign up/in to travis with your github account. Note that you have to authorise Travis to do some stuff like doing commits after a build.

TIP: there are plenty of platforms for working and understanding CI/CD, you can check for instance GitHubActions, TravisCI, CircleCI before jumping to Azure, AWS or Jenkins

In small projects, or side projects, you can use the TravisCI + GitHub Actions approach; GitHub already has some built-in options for setting up ymls and help you with Merge Requests and Deployments.