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!


PHP Laravel Pipeline: No Artifacts Uploaded

My artifacts is not uploaded after successful run of test pipeline. Here's the yml:


here's the result


what should the correct code for the artifact?

1 answer

1 accepted

1 vote
Answer accepted
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 13, 2022

Hi @nymendaros,

I see two issues with the yml file you posted:

1st. The two steps are parallel. Parallel steps can only use artifacts produced by previous steps, not by steps in the same parallel set.

If you want the second step to use an artifact generated by the first step, you will need to remove the parallel keyword.

2nd. I'm afraid that the file path in artifacts cannot render variable names. We have a bug report about this in our issue tracker:

As a workaround, you can determine as an artifact any file with .zip extension as follows:

- "*.zip"

In case you have multiple zip files in the clone directory and you want to avoid having all of them uploaded as artifacts, you can generate this specific zip in a separate folder inside the clone directory, e.g. named 'app', and then define as an artifact any zip file in that directory

- app/*.zip

Please feel free to let me know how it goes and if you need further assistance.

Kind regards,

Sorry for late reply. Thank you for the assistance

This has been solved on the same month (June). We're able to fix the pipeline by removing the parallel directive for the 1st and 2nd step and among other things.

But the $BITBUCKET_BUILD_NUMBER is not incrementing.

Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 21, 2022

Hi @nymendaros,

Thank you for the update and you are very welcome! It's good to hear that the issue was solved.

Regarding $BITBUCKET_BUILD_NUMBER not incrementing, have you perhaps defined a deployment variable, repository variable, or workspace variable with the same name? These variables will override default ones with the same name.

If you add the command ls -lah below the zip command as follows, does the number in the name of the zip not correspond to the build number?

- zip -r example-$ .
- ls -lah

In case you are generating the zip in a directory inside the clone directory, provide the directory name in the ls -lah command.

Kind regards,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events