# ZIP does not support timestamps before 1980 **URL:** \ **Category:** Bug Reports\ **Tags:** codedeploy, aws\ **Created:** [June 5, 2017, 9:15pm UTC](https://discuss.circleci.com/t/zip-does-not-support-timestamps-before-1980/13110 "2017-06-05T21:15:06Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![aharita](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/aharita/32/16250_2.png) [@aharita](https://discuss.circleci.com/u/aharita)\ **Post date:** [June 5, 2017, 9:15pm UTC](https://discuss.circleci.com/t/zip-does-not-support-timestamps-before-1980/13110/1 "2017-06-05T21:15:07Z")
Having issues trying to do an AWS CodeDeploy, in the “Create new revision” step, is this a problem with the default container, or something we can/should change on our side? ``` create_application_revision /tmp/codedeploy_applications.json /tmp/codedeploy_revisions.json create_application_revision loaded: {"applications":[{"region":"us-west-2","application_root":"/","revision_location":{"s3Location":{"bucket":"xxx","key":"xxx"},"revisionType":"S3"},"deployment_group":"xxx","application_name":"xxx"}]} Bundling xxx from /home/ubuntu/portal Unhandled exception ZIP does not support timestamps before 1980 ((create_application_revision "/tmp/codedeploy_applications.json" "/tmp/codedeploy_revisions.json")) returned exit code 1 Action failed: Create new revision of xxx ``` ---
**Author:** ![arsenio](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/arsenio/32/16252_2.png) [@arsenio](https://discuss.circleci.com/u/arsenio)\ **Post date:** [June 5, 2017, 10:02pm UTC](https://discuss.circleci.com/t/zip-does-not-support-timestamps-before-1980/13110/2 "2017-06-05T22:02:38Z")
I’m seeing the exact same problem with my builds, as of at least today (this was working just fine two days ago). ---
**Author:** ![jonathanchrisp](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/jonathanchrisp/32/15763_2.png) [@jonathanchrisp](https://discuss.circleci.com/u/jonathanchrisp)\ **Post date:** [June 5, 2017, 10:55pm UTC](https://discuss.circleci.com/t/zip-does-not-support-timestamps-before-1980/13110/3 "2017-06-05T22:55:30Z")
Just to add further weight to this post, we’re also seeing the same problem. I raised this an issue on the aws-cli repo. Please see the following URL: [https://github.com/aws/aws-cli/issues/2639](https://github.com/aws/aws-cli/issues/2639). ---
**Author:** ![Rondineli](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/rondineli/32/12407_2.png) [@Rondineli](https://discuss.circleci.com/u/Rondineli)\ **Post date:** [June 6, 2017, 12:13pm UTC](https://discuss.circleci.com/t/zip-does-not-support-timestamps-before-1980/13110/4 "2017-06-06T12:13:18Z")
I’m seeing the exact same problem as well. Still looking for some solution, it was working like, yesterday. ---
**Author:** ![arsenio](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/arsenio/32/16252_2.png) [@arsenio](https://discuss.circleci.com/u/arsenio)\ **Post date:** [June 6, 2017, 4:04pm UTC](https://discuss.circleci.com/t/zip-does-not-support-timestamps-before-1980/13110/5 "2017-06-06T16:04:56Z")
Is there a way, in either application settings or `circle.yml`, to force bundling to a tarball instead of a zip archive? That could be a good workaround. ---
**Author:** ![dazulu](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/dazulu/32/15852_2.png) [@dazulu](https://discuss.circleci.com/u/dazulu)\ **Post date:** [June 8, 2017, 8:49am UTC](https://discuss.circleci.com/t/zip-does-not-support-timestamps-before-1980/13110/6 "2017-06-08T08:49:48Z")
We are running into this problem as well. Started somewhere over the last couple of days. Will report back if we find cause/solution. ---
**Author:** ![dazulu](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/dazulu/32/15852_2.png) [@dazulu](https://discuss.circleci.com/u/dazulu)\ **Post date:** [June 8, 2017, 9:14am UTC](https://discuss.circleci.com/t/zip-does-not-support-timestamps-before-1980/13110/7 "2017-06-08T09:14:43Z")
It looks all but certain that this is an issue with files in **uglify-js** being somehow created with a timestamp of 1969 (-1). Read through the hot drama at [https://github.com/mishoo/UglifyJS2/issues/2054](https://github.com/mishoo/UglifyJS2/issues/2054). There is some reluctance to look into it. ---
**Author:** ![tom](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/tom/32/27680_2.png) [@tom](https://discuss.circleci.com/u/tom)\ **Post date:** [June 12, 2017, 9:43am UTC](https://discuss.circleci.com/t/zip-does-not-support-timestamps-before-1980/13110/8 "2017-06-12T09:43:30Z")
Thanks for reporting this everyone. The solution for now is to lock uglify-js to `2.8.27`. See this GitHub issue for more details: [https://github.com/aws/aws-cli/issues/2639#issuecomment-307218133](https://github.com/aws/aws-cli/issues/2639#issuecomment-307218133) ---
**Author:** ![ktwbc](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/ktwbc/32/13751_2.png) [@ktwbc](https://discuss.circleci.com/u/ktwbc)\ **Post date:** [April 7, 2018, 1:30pm UTC](https://discuss.circleci.com/t/zip-does-not-support-timestamps-before-1980/13110/9 "2018-04-07T13:30:36Z")
this is happening again on circleci, getting ZIP does not support timestamps before 1980 suddenly on deploy ---
**Author:** ![yueyufu](https://avatars.discourse-cdn.com/v4/letter/y/bc79bd/32.png) [@yueyufu](https://discuss.circleci.com/u/yueyufu)\ **Post date:** [April 20, 2018, 10:32pm UTC](https://discuss.circleci.com/t/zip-does-not-support-timestamps-before-1980/13110/10 "2018-04-20T22:32:56Z")
Having the same issue, even the build which used to pass. ---
**Author:** ![ray-mccord](https://avatars.discourse-cdn.com/v4/letter/r/3ab097/32.png) [@ray-mccord](https://discuss.circleci.com/u/ray-mccord)\ **Post date:** [April 21, 2018, 4:52am UTC](https://discuss.circleci.com/t/zip-does-not-support-timestamps-before-1980/13110/11 "2018-04-21T04:52:36Z")
It is NPM not setting your file timestamps for node\_modules right on install. This causes python’s easy\_zip to choke and throw the error when you go to create a deployment zip file. If this happens to you at any point in the future, CCI probably updated NPM on you, and they re-introduced the bug yet again. As a workaround, add this post-install run script to your package.json in the “scripts” section: `"find ./node_modules/* -mtime +10950 -exec touch {} \\;"` Your package.json will look something like: ``` { "name": "...", "version": "...", "devDependencies": { ... }, "scripts": { "install": "find ./node_modules/* -mtime +10950 -exec touch {} \\;" } } ``` That will update the timestamps of all files in node\_modules that are older than 30 years, allowing the zip to succeed and giving you your CI pipe back. ---
**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\ **Post date:** [July 20, 2018, 4:52am UTC](https://discuss.circleci.com/t/zip-does-not-support-timestamps-before-1980/13110/12 "2018-07-20T04:52:36Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.