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

Is there any way to change pipe(integration) name?

Hi, everyone.

 

Please take your attention on the picture below. Is there any posibility to make the step more informative?

 

Screen Shot 2023-02-04 at 7.38.07 PM.png

2 answers

1 accepted

1 vote
Answer accepted
Patrik S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 07, 2023

Hello @Namig Garajamirli ,

Thank you for reaching out to Atlassian Community!

The log section you shared will print the command being executed by the script. I'm afraid it's not possible to change that to a different value as that is the name of the command. However I can think of the following workarounds that might help get more context of what the pipe is doing : 

  • Separate the pipes into different steps and give each step a different name : 
        - step:        
            name: SSH into serverA
            script:
              - pipe: atlassian/ssh-run:0.4.1
                variables:
                  SSH_USER: '<string>'
                  SERVER: '<string>'
                  COMMAND: '<string>'
        - step:        
            name: SSH into serverB
            script:
              - pipe: atlassian/ssh-run:0.4.1
                variables:
                  SSH_USER: '<string>'
                  SERVER: '<string>'
                  COMMAND: '<string>
    With this change, there would be only one pipe per step, and you would be able to differentiate each step name in the step list on the right side.
    Screenshot 2023-02-07 at 3.12.48 PM.png
  • Add an echo command before the pipe so it prints more details about what that specific pipe will do :
    - step:        
            name: My step
            script:
              - echo "SSH into server A"
              - pipe: atlassian/ssh-run:0.4.1
                variables:
                  SSH_USER: '<string>'
                  SERVER: '<string>'
                  COMMAND: '<string>'
              - echo "SSH into server B"
              - pipe: atlassian/ssh-run:0.4.1
                variables:
                  SSH_USER: '<string>'
                  SERVER: '<string>'
                  COMMAND: '<string>'
    This will show the echo command before each pipe execution
    Screenshot 2023-02-07 at 3.19.38 PM.png

Hope that helps! Let me know in case you have any other questions.

Thank you, @Namig Garajamirli !

Patrik S

Thank you for the detailed answer, @Patrik S!

According to the docs, you should be able to just set the name besides variables:

https://support.atlassian.com/bitbucket-cloud/docs/step-options/#Name

https://support.atlassian.com/bitbucket-cloud/docs/step-options/#Pipe

Is this currently a bug? @Patrik S 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events