Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Pipeline with apt update started to fail

We started receiving the below error end of last week from the apt update step. Note our pipeline didn't change:

+ apt update
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Ign:1 stretch InRelease
Ign:2 stretch/updates InRelease
Ign:3 stretch-updates InRelease
Err:4 stretch Release
404 Not Found [IP: 80]
Err:5 stretch-updates Release
404 Not Found [IP: 80]
Err:6 stretch/updates Release
404 Not Found [IP: 80]
Reading package lists...
E: The repository ' stretch Release' does not have a Release file.
E: The repository ' stretch-updates Release' does not have a Release file.
E: The repository ' stretch/updates Release' does not have a Release file.


Our pipeline was running successfully prior to last week. Below is a snippet of our pipeline. Has anyone encountered this issue and resolved it?

- step:
image: maven:3.6.1
- maven
name: Build and Run Unit Tests
- cp settings.yaml $BITBUCKET_CLONE_DIR/src/main/resources/settings.yaml
- cp appSettings.yaml $BITBUCKET_CLONE_DIR/src/main/resources/appSettings.yaml
- cp settings.xml ~/.m2/settings.xml
- apt update
- apt install jq -y

2 answers

1 accepted

0 votes
Answer accepted
Erez Maadani
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 02, 2023

Hi Erez, thank you for the suggestion. We are looking to take a similar action and are still reviewing what version of maven to update to

What we found is that is that Debian 9/stretch moved to
For a short term solution:
We will point apt to the archived version by adding the following line before the apt update line in our pipeline:
echo "deb stretch main" > /etc/apt/sources.list

We found this solution here:

For our Long term solution:
We will look for a newer version of the maven image that supports an updated version of apt

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events