I've been running automated builds on my Jenkins machine for several projects, but today I faced a strange issue. Out of 10 builds, 7 failed within a 10-minute window because a specific file that should be on EBS was reported as 'not present.' When we checked an hour later, the file was definitely there. After that hiccup, the subsequent builds went smoothly. I'm trying to figure out if it's possible for a file to go unavailable in EBS, as this is the first time I've encountered something like this. I'd also like to know if there are any EBS logs that could provide insights on this situation. Any help would be appreciated! Thanks!
3 Answers
Definitely not an EBS error. While an entire volume might have an outage due to rare circumstances, not a single file would have that kind of behavior.
The issue is likely not related to EBS itself. It might be something specific to your Jenkins setup or the Linux distribution you're using. EBS is just block storage, and it doesn't know about your files.
This issue isn't from EBS. Check around your Jenkins configuration or the operating system. EBS is just a file storage solution.
Thanks for the input!