The way I've done this in past and current positions has evolved over
time. Generally speaking I break all of by build systems up into a
couple of parts depending on what capabilities I need these generally
break down into the following 5 categories:
increment - deals with code checkout (are there
My question is about design strategy, so I want to hear the pros and cons
from those more familiar with Jenkins. Thanks.
On Sunday, February 23, 2014 10:11:39 AM UTC+10, Red wrote:
>
> Hi. I am also new to jenknis. I searched
> http://serverfault.com/search?q=jenkins and found 414 jenkins relat
Hi. I am also new to jenknis. I searched
http://serverfault.com/search?q=jenkins and found 414 jenkins related post.
On Sat, Feb 22, 2014 at 3:45 PM, andres reynaldy
wrote:
> Hi,
>
> I'm new to Jenkins and I'm wondering is this the user forum for jenkins? I
> was expecting a forum, not a gmail
Hi,
I'm new to Jenkins and I'm wondering is this the user forum for jenkins? I
was expecting a forum, not a gmail mailing group. But anyway, I'm here to
ask about the best practice about how to set up integration testing in
Jenkins. Do we deploy that as separate build job thats run after the co
