You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Codepipeline sees changes and kicks off the build process in 2 different regions (us-east-1 and us-east-2)
Expected Behavior
Based on the docs, I would expect the "contenthash" values on both of my builds to be the same for my main.js, main.css and chunk.js files.
Actual Behavior
On the 2 different boxes, my app builds successfully, but the hashnames are totally different.
I know this is happening because CodePipeline is bringing my code into a directory that they are creating dynamically. The "hash" is based on the directory that the code is built in.
Reproducible Demo
Clone the CRA base into a local working directory (./cra1 as an example).
Clone it again into another local working directory (./cra2 as an example).
Run npm run build on both folders.
Note the "compiled" filenames are different but their content is the same.
The text was updated successfully, but these errors were encountered:
whatadewitt
changed the title
Hash Names in AWS CodePipeline
Different Hash Names in AWS CodePipeline
Apr 1, 2019
Is this a bug report?
Yes
Did you try recovering your dependencies?
Yes
Which terms did you search for in User Guide?
Deployment, static files, hosting
Environment
Steps to Reproduce
Expected Behavior
Based on the docs, I would expect the "contenthash" values on both of my builds to be the same for my main.js, main.css and chunk.js files.
Actual Behavior
On the 2 different boxes, my app builds successfully, but the hashnames are totally different.
I know this is happening because CodePipeline is bringing my code into a directory that they are creating dynamically. The "hash" is based on the directory that the code is built in.
Reproducible Demo
Clone the CRA base into a local working directory (./cra1 as an example).
Clone it again into another local working directory (./cra2 as an example).
Run
npm run build
on both folders.Note the "compiled" filenames are different but their content is the same.
The text was updated successfully, but these errors were encountered: