Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Move to another CI?
See original GitHub issueRecently, we have encountered an unexpected build fail issue(https://github.com/line/centraldogma/pull/426). And Travis CI is slower than other CI.
- Appveyor took
24 min 46 sec - Travis took
30 min 58 sec
Travis CI is 25% slower than Appveyor with the same PR.
Related work: I saw an issue which considers moving another CI(Semaphore CI) to reduce build time.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Six Things to Consider When Moving to CI/CD - Medium
Some things to consider as you and your team move towards ... Early on, isolate new subsystems built with CI/CD from your existing...
Read more >Continuous integration vs. delivery vs. deployment - Atlassian
CI stands for continuous integration, a fundamental DevOps best practice where ... the build and can work on fixing it before they move...
Read more >Moving CI's from existing class to another class a... - ServiceNow
Hi Team, I have created a new class extending the configuration table.Into this new class we need to move the CI's from another...
Read more >How to shift left with continuous integration - GitLab
The way to do this is by integrating security testing into deployment pipelines so that code is continually tested, not only against other...
Read more >Moving from CI to CD – Qentelli Way to Successful DevOps
Taking the next step from such practice towards successful DevOps, is to achieve faster CI cycles, which provide feedback on whether a build...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You could use the built in GitHub actions, I use that for all my projects and it works well.
On the other hand, AppVeyor introduced BYOC jobs which allow us to use our servers for running the builds: https://www.appveyor.com/blog/2019/10/01/self-hosted-jobs-on-your-computer-or-in-cloud-vms/