2

With Atlassian BitBucket, you can have:

  • Projects, which incorporate..
  • Source code repositories.

Now, you could have a microservices with more than just one codebase and need therefore more than just repository. What is the best practice to reflect this if you have many different projects?

My idea now is to encode microservice prefixes to repository names, but is this really the way to go?

Like:

  • Project A
    • service1.repo1
    • service1.repo2
    • service2.repo1
  • Project B
    • serviceN.repoX
  • Can you give concrete examples? – AnoE Dec 17 '17 at 13:37
  • They are given above – Peter Dec 17 '17 at 19:04
1

One could also create libraries and call them using a dependency manager like a package.json if node is used or ivy if the code is written in java.

  • But what does this mean to repo layout? – Peter Oct 17 '17 at 18:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.