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
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.
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.
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. There is some reluctance to look into it.
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.