You can name it anything you want, but I have named mine modern-jenkins. NOTE: Don’t check the “Initialize this repo with a README” button. We will be storingĮverything we do in this tutorial on GitHub. Primary SCM host with either their public or on-premise offering. Worlds largest hub for sharing code and lots of companies use it as their Create the repo and populate the master branchĬreate an account on GitHub 1 if you do not have one already. We get to the point of configuring our deployment, we will add some encryption toĬover the secret data. You shouldīe able to do this for free as GitHub allows unlimited open source projects. Running what’s in the code blocks Flesh out the repo structureįirst let’s make sure that we have a repo to work on setup in GitHub. I’m going to treat this as a tutorial so you should be able to follow along by Like this right off the bat is a premature optimization IMO. Making a bunch of different repos for a project I prefer instead to start out with a mono-repo and if there comes a time in which Makes things very hard to find on a system that you contribute to infrequently. I am a fan of this idea for certain use cases, but what I have found is that it In the past we tended to use a lot of separate repos and to treat themĪs if they were fully independent and could be shared with any other team as is. Means that we should separate concerns within the tree and make things easy We want our repo to be intuitively laid out as there is the chance that almostĮvery engineer in the company will need to interact with it at some point. Of all projects start with a SCM (source control management) repository. System should be, we can begin to lay down the foundation. Now that we have a good idea of what the desired traits and abilities of our
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |