Continuous Delivery is an emerging area of software development, which takes continuous integration one step further. Software teams practicing continuous delivery create build pipelines that enable them to integrate, test, and deploy their software products with high frequency.
2
votes
3answers
271 views
Continous Delivery TFS
Is it possible to achieve Continuous Delivery using TFS e.g. Windows Service? There are > 1000 posts on how to use msdeploy with TFS for WEB projects.
I am trying to understand why there are no ...
6
votes
3answers
291 views
How do I structure code and builds for continuous delivery of multiple applications in a small team?
Background:
3-5 developers supporting (and building new) internal applications for a non-software company. We use TFS although I don't think that matters much for my question.
I want to be able to ...
2
votes
3answers
72 views
What guidelines are best suited for leveraging automatic deployments? [closed]
We are hoping to leverage a static code analysis tool (Sonar) as part of our continuous integration server, and are hoping to determine some useful guidelines to serve as a base for allowing the ...
3
votes
2answers
179 views
How to communicate within a company what is being Continually Deployed
I work for a small development company, 20 people total in the entire company, 3 in actual development, and we've adopted CD for our commits to trunk, and it works great, from a code management and ...
4
votes
4answers
1k views
How to implement Continuous Delivery with Java webapp?
I've been reading about Continuous Delivery and it sounds awesome to automate the deployment process. I've been reading about possibilities how to do this with Java Webapps, but usually it ends up ...
11
votes
6answers
806 views
How can Continuous Delivery work in practice?
Continuous Delivery sounds good, but my years of software development experience suggest that in practice it can't work.
(Edit: To make it clear, I always have lots of tests running automatically. ...
13
votes
4answers
261 views
At what point should you switch to release build?
One of the practices set out in Jez Humble's Continuous Delivery is that you should build one package and then release it to each environment you deploy to, so that the deployment and the artifacts ...
6
votes
5answers
920 views
“Release Early Release Often” for Android and iPhone Apps
I wanted to know the experiences others have about doing the Agile way of "Release Early, Release Often" with iPhone and Android Apps. Its not a problem with webapps as the update happens at the ...
2
votes
6answers
391 views
Which deployment technologies makes sense in Continuous Deployment?
In my understanding a major point in Continuous Deployment is (well, obviously I guess) that deployment is automatically done as a part of the building process.
Conceptually it is easy to understand ...
7
votes
5answers
617 views
is anyone out there using continuous delivery?
I am curious if anyone out there is striving for "continuous delivery"? Are the toolsets mature enough to make this a reality?
8
votes
2answers
3k views
Writing a Jenkins plugin - non-Java-Expert
Can anyone point me (.NET by career, primarily Ruby by hobby) in the right direction(s) for learning how to write a Jenkins plugin? I'm looking specifically at build summary information and trend ...
