Tag Info

New answers tagged

1

Another way to think of it is not as a "doc server", but that you're building a "Developer Portal" for your API consuming audience. This might include developers, but it could also include product managers, UI/UX folks, business analysts, etc. Some things a Developer Portal might expose, beyond just raw documentation include: Sample code Sample apps ...


1

Do I need to use tags for every version? If by "version" you mean a set of files that make up a release or a release candidate, then I strongly recommend tagging every version. If you need to refer to version 1.2.7 down the road, do you want to hunt for a commit's hash or just use the version number? Also if you use git describe to record build ...


9

You should look at git-flow. It's an excellent (and popular) branching model. Git Flow Summary Branching The main trunks that stay around forever are develop and master. master holds your latest release and develop holds your latest "stable" development copy. Contributors create feature branches (prefixed with feature/ by convention) off of develop : ...


0

Scanning your list I see version as your focus, so... One way to maintain versions is with branches and merging (or rebasing). So you have: master then you create a branch v1 then you add more changes to master(diff1) then you create a branch v3 then you add more changes to master(diff2) Now: To update Version 2 you now do git checkout v2 ...


2

Do I need to use a tag for every version? No, you don't need to use tags at all. If you want to tag every release, that's fine, or if you want to tag every single time your CI system builds, you could do that too. Tags are essentially just giving a user friendly name to the commit, so that you can easily pull it up and view it later. Should I create ...


0

TL;DR: It depends, but not because of continuous integration. You can version everything together which will simplify dependency management, or you can split the code and make dependency management explicit between the different code bases. This isn't really a question about continuous integration. The driving concern when splitting code bases is if you ...


1

CI server are only co-ordinators, they schedule and run builds, they schedule and run tests, and some schedule and run deployments. Its the latter you are worrying about and that's ultimately a task for whatever tool you use to deploy your build project onto whatever hardware or VM is going to be used for testing. I have a project that consists of a client ...



Top 50 recent answers are included