You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi , I'm trying to create Deployment project for my bamboo plan. As a part of it , im trying to create Artifact.
For SBT Assemblty everytime jar file will be created in
So now when i'm defining artifact what is the copy pattern i should give so that only jar file will be available for next Task( for eg: SCP Task)
If i define
Location --> folder/<<sbtproject>>/target
copy pattern --> **/scala*/Assembly*.jar
Then after next scp task , i can see Assembly jar with scala folder in target director
How can i over come this ? so that i can only copy jar files to respective envionments.
Hello @Kailash, welcome to the Atlassian Community :)
May I ask some clarifying questions before I can try to help you?
I want to understand better which part or behaviour of artifact copying in Bamboo you specifically want to overcome, maybe, can you rephrase your question?
Also, you mentioned that you have the SBT Assembly jar being created, is that being created from a build plan or an environment task?
Hi @Victor Debone , Thanks for reply.
The part where i was facing difficult was while defining the "copy Pattern" for Deployment Project.
So when i trigger the deployment project, the scp task was coping the assembly jar with folders as welll.
for eg: scala-2.12/Assembly_0.21.jar
I resolved this issue by adjusting the copy pattern.