Yes, and that's also the reason why I think Jenkins should not get a database 
backend  for any configuration but only for build results and tracking 
Domi

> On 24.10.2015, at 12:37, Christopher Orr <[email protected]> wrote:
> 
> It seems they're talking about both system configuration and job
> configuration — in the next section, talking about Travis, they refer to
> keeping job config in SCM (via `.travis.yml`) as a good thing.
> 
> 
>> On 23/10/15 23:39, Richard Bywater wrote:
>> My impression was that they were talking about system configuration
>> which presumably isn't touched in the areas you mention?
>> 
>> Richard.
>> 
>> 
>> On Fri, 23 Oct 2015 10:13 pm Jesse Glick <[email protected]
>> <mailto:[email protected]>> wrote:
>> 
>>    On Fri, Oct 23, 2015 at 4:53 AM, [email protected]
>>    <mailto:[email protected]> <[email protected]
>>    <mailto:[email protected]>> wrote:
>>> They have some points compared to jerkins:
>>    http://concourse.ci/concourse-vs.html#jenkins
>>> ..specially:
>>> - every configuration must be backed in a version control system
>>> - first class support for pipelines
>> 
>>    Yes, it is an interesting read. I think multibranch Workflow plus
>>    Docker integration starts to close the gap on these two bullet points.
>>    (See my recent webinar for background.) It is not the same as having a
>>    system designed according to these principles from the start.
>> 
>>    --
>>    You received this message because you are subscribed to the Google
>>    Groups "Jenkins Developers" group.
>>    To unsubscribe from this group and stop receiving emails from it,
>>    send an email to [email protected]
>>    <mailto:jenkinsci-dev%[email protected]>.
>>    To view this discussion on the web visit
>>    
>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr11DM64CJYwBPga7YN3fRWz7tUqpqpgbKLucR-K2eZYpA%40mail.gmail.com.
>>    For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google
>> Groups "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to [email protected]
>> <mailto:[email protected]>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMui944Q9mBvbkzEx3DgQax%2Bum1UqxGG9R%2BfMV%2BVs1kV3LJctA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMui944Q9mBvbkzEx3DgQax%2Bum1UqxGG9R%2BfMV%2BVs1kV3LJctA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/562B5F80.4050401%40orr.me.uk.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/A2EEDA2C-A0BB-42CD-8FAF-2C59245AE0ED%40fortysix.ch.
For more options, visit https://groups.google.com/d/optout.

Reply via email to