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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,640,963
Community Members
 
Community Events
196
Community Groups

Simple build with docker env does not grab artifacts

Edited

Hi all,

I decided to move my build from agent env to dokcer env. My docker is created from ubuntu image + some apt-get install etc.

I am starting docker with build-dir and tmp dir attached from host off course.

Build completes successfully but artifacts are not fetched.

After some struggling I decided to change whole build plan to single stage, with single job with single script task doing only:

touch test

My artifact definition is:

Location: empty

Copy pattern *

 

Artefact is not published. I can see the artifact (empty file called test) created on the host in proper dir.
When I start docker container manually by copy-paste command from log I can see the file as well.

What am I doing wrong?

Do I need to set entry dir in my docker somehow? Is the problem that docker user is root (I did not change that deliberately, but I can if needed).

1 answer

1 accepted

0 votes
Answer accepted

After much more debugging I found that this is not docker problem.

Artifacts are found but are failing to publish.

Logs: Unexpected HTTP status code: HTTP/1.1 302

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events