The issues as npmjs.org have been resolved. Builds are stabilizing on our Jenkins instance.
Thanks to Brian Jacobel for providing a workaround while npm was having issues. For ongoing status, check status.npmjs.org. Thanks Ben On Wed, Jul 6, 2016 at 8:10 AM, Ben Patterson <[email protected]> wrote: > Hi all - > > Just a heads up that Jenkins builds are failing due to what appears to be > an issue with the npm registry. (Certain packages+versions are reaching a > 502 error when we attempt to pull them down). > > We will update you once we have any relevant, additional information. > > *Impact*: > > - Jenkins builds will fail, such as pull requests > - On devstack, if you have run an install recently, then your cached > version of the npm packages will be fine; however, if your local cache is > out of date and attempts to pull down affected packages, you will be > impacted as well. > > > Regards > Ben > > > -- > *Ben Patterson* > > edX | Engineering Manager | [email protected] > > 141 Portland Street, 9th floor > > Cambridge, MA 02139 > http://www.edx.org <http://www.edxonline.org/> > > [image: > http://www.e-learn.nl/media/blogs/e-learn/edX_Logo_Col_RGB_FINAL.jpg?mtime=1336074566] > -- *Ben Patterson* edX | Engineering Manager | [email protected] 141 Portland Street, 9th floor Cambridge, MA 02139 http://www.edx.org <http://www.edxonline.org/> [image: http://www.e-learn.nl/media/blogs/e-learn/edX_Logo_Col_RGB_FINAL.jpg?mtime=1336074566] -- You received this message because you are subscribed to the Google Groups "General Open edX discussion" group. To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/CAAwyC2b3bszN1yxb3yYb2r9cfNMfOtup4nsuX%2BN0PG2f4mvdRw%40mail.gmail.com.
