# Travis build stuck on "Trying to build"

**URL:** <https://travis-ci.community/t/travis-build-stuck-on-trying-to-build/10796>\
**Category:** Node.js\
**Tags:** travis-build\
**Created:** [December 10, 2020, 12:08am UTC](https://travis-ci.community/t/travis-build-stuck-on-trying-to-build/10796 "2020-12-10T00:08:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![djhouseknecht](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/djhouseknecht/32/5792_2.png) [@djhouseknecht](https://travis-ci.community/u/djhouseknecht)\
**Post date:** [December 10, 2020, 12:08am UTC](https://travis-ci.community/t/travis-build-stuck-on-trying-to-build/10796/1 "2020-12-10T00:08:38Z")

</div>

My open source project can’t seem to build. I have pushed commits and tried triggering a new build using the new Beta feature on travis-ci. The build is stuck on “Trying to build”

 ![image](https://us1.discourse-cdn.com/flex015/uploads/travis_ci/original/2X/9/942ebcf160e13c5ac92ae00bcf50c0c329fb9efc.png)

Any ideas what may be happening?

Little history (not sure if this matters): I pushed a commit to master and then shortly after run a `git commit amend --no-edit && git push --force`. Not sure if that is what got it stuck. Since then I tried to trigger the build via travis-ci.

Link to build: [https://travis-ci.org/github/djhouseknecht/rollup-plugin-version-injector/builds/748658729](https://travis-ci.org/github/djhouseknecht/rollup-plugin-version-injector/builds/748658729)

---

<div class="post-metadata">

**Author:** ![djhouseknecht](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/djhouseknecht/32/5792_2.png) [@djhouseknecht](https://travis-ci.community/u/djhouseknecht)\
**Post date:** [December 10, 2020, 3:26pm UTC](https://travis-ci.community/t/travis-build-stuck-on-trying-to-build/10796/3 "2020-12-10T15:26:29Z")

</div>

It eventually starting building around 01:00 EST last night. Is there rate limiting or something going on here? I see it happening to other builds of mine. It holds up releases since I release the npm version inside the travis build.

---

<div class="post-metadata">

**Author:** ![hugovk](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/hugovk/32/684_2.png) [@hugovk](https://travis-ci.community/u/hugovk)\
**Post date:** [December 10, 2020, 6:18pm UTC](https://travis-ci.community/t/travis-build-stuck-on-trying-to-build/10796/4 "2020-12-10T18:18:33Z")

</div>

Travis CI are going to shut down [travis-ci.org](http://travis-ci.org) by the end of the year, all projects need to migrate over to [travis-ci.com](http://travis-ci.com). They’ve been moving resources over, hence the slow builds on .org.

> **[Travis CI Documentation](https://docs.travis-ci.com/user/migrate/open-source-repository-migration)**
>
> Migrating repositories to travis-ci.com

However, on .com there’s a new pricing model. You’ll get a certain number of credits to begin with. When they run out, you can either pay to subscribe, or contact support to apply for their new open source plan.

> **[The Travis CI Blog: The new pricing model for travis-ci.com](https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing)**
>
> Changes to Travis CI pricing are coming!
> 
> At Travis CI, we design CI/CD products to make code testing and deployment easy. We are a huge supporter of open-source teams, with many projects such as ...

However, there are huge delays in support replying, if ever, and when they do they say they’re waiting for approval from management, or someone recently was told that things are on hold pending more info from management.

I ran out of credits so couldn’t build anything for two weeks. Support then gave me a one-off top-up of 50k credits whilst still awaiting approval from management. I’ve not heard anything in 9 days.

The new pricing model was launched with no notice, meaning some projects that had already migrated no longer have the choice of very slow builds on .org, or no builds on .com.

The mixed messaging and especially lack of communication, coupled with builds stopping altogether, means many open-source projects are moving to other CI providers, such as GitHub Actions.

---

<div class="post-metadata">

**Author:** ![djhouseknecht](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/djhouseknecht/32/5792_2.png) [@djhouseknecht](https://travis-ci.community/u/djhouseknecht)\
**Post date:** [December 10, 2020, 7:40pm UTC](https://travis-ci.community/t/travis-build-stuck-on-trying-to-build/10796/5 "2020-12-10T19:40:22Z")

</div>

Ah man, that is sad. Having to wait potentially days for builds to run kills release timeframes and most all of my open source projects are using [travis-ci.org](http://travis-ci.org). I guess I will have to look into migrating to GitHub Actions. If anyone has some working examples setup for node/npm open source projects, I’d love to check them out!

---

<div class="post-metadata">

**Author:** ![hugovk](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/hugovk/32/684_2.png) [@hugovk](https://travis-ci.community/u/hugovk)\
**Post date:** [December 11, 2020, 8:08pm UTC](https://travis-ci.community/t/travis-build-stuck-on-trying-to-build/10796/6 "2020-12-11T20:08:40Z")

</div>

Here’s a well-commented example I found:

> <https://github.com/ETSOO/NotificationUI/blob/8e33d4ba92eaffbdc1780b5339586e310915f2c3/.github/workflows/main.yml>

Another short one:

> <https://github.com/aaronpowell/react-foldable/blob/915d54a16825543b8d6ca2d70df60fd949642ec2/.github/workflows/build.yml>

Lots more here:

> **[Build software better, together](https://github.com/search?l=YAML&p=3&q=github%2Bactions%2Bnode%2Bnpm&type=Code)**
>
> GitHub is where people build software. More than 50 million people use GitHub to discover, fork, and contribute to over 100 million projects.
