Build artifact checksum changing after each download

[Brenden Smerbeck]

Hello all,

I'm encountering an issue with my build artifacts. I have a build which generates two .tar.gz archives. I'd like to use these in a Yocto build of a custom Linux image. However, every time I download the file from Bamboo and calculate its checksum, the value has changed.

Am I doing something wrong? Or is this just an innate function of Bamboo. 

Thanks for your help.

*EDIT* So I've begun testing this on a couple different hosts. On windows, I can click to download the .tar.gz archive and the sha256 checksum remains the same.

Additionally, on the CentOS host with Yocto, if I perform the following

curl -s <path to archive>|sha256sum

I get the same checksum. The checksum only changes after I download the file using `wget`. I imagine this is why Yocto continues failing the build.

*EDIT 2* So I performed a diff on the two archives and discovered the following:

< <input type="hidden" name="atl_token" value="cd828970f1539040af6457b8398fa11de7d0a7aa" />
---
> <input type="hidden" name="atl_token" value="35a35ae887399c904829400f142485e59f623190" />

Thoughts on how this may be worked around?  

*EDIT 3* Looks like this is an issue with performing an unauthenticated wget

[Brenden Smerbeck · Accepted solution]

Solved. Going to need to implement a deployment process to move it to a local directory for retrieval by Yocto