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,458,998
Community Members
 
Community Events
176
Community Groups

A central place for managing repositories

Deleted user May 21, 2018

So we have nearly 200 repositories, many of which have the same configurations:

  • environment variables for Pipeline builds
  • default administrator users
  • default branch permissions
  • default reviewers
  • SSH key

and many other settings are basically the same in our company. For example, we have user-groups for reviewers and we don't have to go and set that for each repository, we could just set it once

 

Another problem is - one of the thing we are facing right now - we set docker username/passwords and some other environment variables for Pipeline build... any change in our Pipeline process, resetting password, adding new env variable, all requires one person to go through all the 200 repositories and set them one by one. You can tell that when a repeating task is in place human makes mistakes... now imagine after setting all those repositories, something comes up and we'll need to change them again.

 

I wish there was a central settings page for all repositories so any repository would inherit those settings unless a specific configuration needs to be overridden in the repo settings itself.

 

I'd like to know your opinion

Thanks

 

 

 

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events