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,459,097
Community Members
 
Community Events
176
Community Groups

How to hide or name pipelines for the manual run UI?

I know we can name a custom pipeline and that name will appear in the pipeline choice dropdown in the manual run UI, but how to either name or hide the automatic pipelines?

As seen below I see the branch and pull-requests triggers which are incomprehensible to a user trying to figure out which pipeline to manually run.  

Screen Shot 2022-05-12 at 4.52.14 PM.png

1 answer

0 votes

Hi Douglas,

I'm afraid that it is not possible to either rename or hide certain pipelines from this dropdown. The dropdown will show all pipelines available for the branch you have selected (or for a certain commit, if you are using the Run pipeline option of a commit's page). We provide the link See configuration next to the dropdown, so a user can view the yml file and details of each pipeline for that branch/commit.

That being said, I can create a feature request about either naming or hiding the automatic pipelines from the dropdown, for our development team to consider.
Would you like me to proceed with that?
If so, what would be preferable and more convenient for you? Giving a name to these pipelines? Or having a checkbox in this dialog to show only custom ones?

Kind regards,
Theodora

Yes, thanks! this is not very 'human' readable.   Seems it would be following a common pattern to use the 'name' property for that eh?   and use the manual property maybe to hide in the drop down?

a checkbox in this dialog to show only custom ones in the run uI could work, but I honestly think naming is better. Consider I want my QA team to manually trigger a build for a branch currently in a PR process and use the 'PR based pipeline' which is not a custom build.  We devops devs could work around that though with reusable pipeline blocks ala <<: *nameofpipeline

 

branches:
'master':
name: "name of trigger here"
- step:
script:
- echo "foo"
name: "name of a step"
'{feature/*,bugfix/*}':
name: "trigger CI build example name to see in run UI"
'someother/branchpatter':
manual: false

Hi Douglas,

Thank you for the feedback!

I went ahead and created a feature request in our issue tracker:

Please make sure to add your vote to that ticket (by selecting the Vote for this issue link) as the number of votes helps the development team and product managers better understand the demand for new features.

You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.

Implementation of new features is done as per our policy here and any updates will be posted in the feature request.

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events