[Service] Android And WebOS Build Are Failing - May 15, 2013 (PDT)

  • 1
  • Announcement
  • Updated 7 years ago
Dear Everyone

Android build as well as WebOS encounter a service disruption early this morning. All jobs are failing for the past 6 hours. We are still working to address this and we'll keep you posted for status updates.

Sorry for any inconveniences causes.

Thanks
Photo of Amir

Amir

  • 8261 Posts
  • 263 Reply Likes

Posted 7 years ago

  • 1
Photo of Amir

Amir

  • 8261 Posts
  • 263 Reply Likes
Dear Everyone

We truly apologize for delayed updates as we are at a full capacity to tackle this outage.

We finally found the root cause. There were a communication error between our nodes (which compiles all the apps) with our web interfaces (build.phonegap.com) where it fails to announce its completion status making every single jobs appear as pending. We have successfully recover Android nodes, and work are still in progress for WebOS.

If you've seen this message, kindly try rebuild your app and see if Android build successful.

Thanks
Photo of Mario

Mario, Champion

  • 120 Posts
  • 17 Reply Likes
That sounds like an explanation why I got updates with Hydration, but not on the website.

Thx for the good news.
Photo of Andy Kaminski

Andy Kaminski

  • 16 Posts
  • 2 Reply Likes
Thanks. This is a great update.
Photo of rhnkurier

rhnkurier

  • 6 Posts
  • 0 Reply Likes
No, Android is not working for me. Failed to communitcate with build servers.pending
Photo of Andy Kaminski

Andy Kaminski

  • 16 Posts
  • 2 Reply Likes
I thought that initially... try refreshing the page, I think it's just the icons that aren't updating
Photo of rhnkurier

rhnkurier

  • 6 Posts
  • 0 Reply Likes
The Dreamweaver-integrated build service reports: Failed to communitcate with build servers.pending

I will give it a try over the web interface, thanks for the tip.
Photo of Jake

Jake

  • 3 Posts
  • 0 Reply Likes
I got fed up with waiting, so instead of stopping programming, I made this, so I don't have to keep on checking every 10 minutes.

http://pgbuildstat.us/

Just shows the current status of the compilers.
Photo of Mario

Mario, Champion

  • 120 Posts
  • 17 Reply Likes
Thx!
Photo of Andy Kaminski

Andy Kaminski

  • 16 Posts
  • 2 Reply Likes
Nice!
Photo of Ed

Ed

  • 2 Posts
  • 0 Reply Likes
Dude! Nice!
Photo of pistoleta

pistoleta

  • 69 Posts
  • 1 Reply Like
:O you rock!
Photo of rhnkurier

rhnkurier

  • 6 Posts
  • 0 Reply Likes
Sorry, but it now comes to absolutely inacceptable. This plattform is the heartbeat for the "easy" phone developement in the Adobe Dreamweaver-World. The only reason why we bought Dreamweaver is that we don't want to be worry about the compiler, linking, whatever stuff, just programming and running with great ideas. And now this promise of Adobe breaks my neck.

For my customer it is not important why he cannot play with the new app, if it is because of the build-Plattform, my computer or whatever. I have to fulfill my contracts, and the only way to do until tomorrow morning (central european summertime) is to switch to another plattform and work the whole night. This is absolutely NOT, why we bought Dreamweaver!

If the service is down for a few minutes, maybe an hour, its not ok, but things can happen. But for the second day now? No way!
Photo of Eric Evans

Eric Evans

  • 1 Post
  • 0 Reply Likes
Finally got an Android build through, took about 5 minutes.
Photo of Ed

Ed

  • 2 Posts
  • 0 Reply Likes
Got one built and then the next just never completed. I know debugging issues is tough, but businesses are beginning to rely on this service. Lets work to reduce the debug time.
Photo of canariasglobalpress

canariasglobalpress

  • 1 Post
  • 0 Reply Likes
.apk; .xap; .ipk works!

WebOs Black Berry....pending
Photo of Cristian Cascante

Cristian Cascante

  • 3 Posts
  • 0 Reply Likes
I was starting my first development .... :(
Now I'm not sure if PhoneGab is the way ....
Photo of Amir

Amir

  • 8261 Posts
  • 263 Reply Likes
Build service has now back to business.

Closing topic.

This conversation is no longer open for comments or replies.