Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options user 31950

In software engineering, continuous integration (CI) implements the continuous building and automated testing of the full software product on a frequent schedule. At least once a day, often several times a day and sometimes as often as after every check in to the version control system.

6
votes
2answers
At $DAYJOB, we have the following release/delivery pipeline: Get new features, work on new features. Once all features are completed, our own QA performs regressions, etc. QA signs off on first UAT …
asked Sep 2 '15 by void.pointer
0
votes
Ultimately we decided to go with a release branch per physical release out the door, regardless of how the customer intended to use it. If a released build happens to never make it through UAT, that's …
answered Oct 1 '15 by void.pointer
3
votes
2answers
At our office, we use JIRA to track issues reported by our QA teams. We also have Bamboo which builds each time we commit to our Git (Stash) repository. QA picks a build from Bamboo and they work with …
asked Nov 17 '14 by void.pointer
22
votes
2answers
A product version, such as v1.0.0.100, represents not only a unique production release of software, but helps identify feature sets and hotfix stages for said product. Right now I see two ways to main …
asked Aug 17 '15 by void.pointer