Why am I suddenly receiving 404 on apt-get upgrade inside my bitbucket-pipeline.yml file?

[Scott McCain]

All of my builds are failing suddenly.  I am getting a 404 on apt-get upgrade, which is the first part of my build step and necessary in order to pull in the correct version of build tools I need.  This has worked flawlessly for over a year and suddenly started failing on all my repos this morning.  None of my devs can do any work right now.

[Petr Vaníček]

Hi,

what are you trying to get? Error 404 mean Not found, so probably you have somewhere bad link (in one of your system repo probably). Can you share more details for that like URL/repo what are you trying?

[Scott McCain]

Here is an expert from my bitbucket-pipeline.yml

This has been working since day one and it's the normal ubuntu/debian apt-get call that should work on any debian image.

branches:
master:
- step:
image: node:6.9.4
name: Build Solution
caches:
- node
script:
- apt-get update
- apt-get install zip -y
- npm install typescript -g
- npm install
- tsc
- mkdir export
- cp -r ./build/* export
- cp -r ./node_modules export
- cd ./export
- zip -X -r ../lambda-upload.zip *
- cd ..
- mkdir dist
- cp lambda-upload.zip dist
artifacts:
- dist/**

[Scott McCain]

Actually, found the problem: https://community.atlassian.com/t5/Bitbucket-Pipelines-articles/Bitbucket-Pipelines-Apt-get-update-returning-404/ba-p/1042290#M54

[Petr Vaníček]

Yeah, that was what I wrote. :-) Perfect when you found where it is exactly.