On 05/20/2016 07:30 AM, Ullrich Hafner wrote:
9) I see job metadata ("configuration" in Jenkins terminology) are stored as
xml. Job instances
("builds" in Jenkins terminology) metadata is stored only in filesystem or is
any database
used as persistence layer?
I still need an answer here.
> Am 20.05.2016 um 01:05 schrieb Alan Evangelista :
>
> On 05/05/2016 05:36 PM, Alan Evangelista wrote:
>> 1) Is there are developer overview documentation? Having to browse through
>> Jenkins huge
>>code without any overview/design document to start is daunting.
On 05/05/2016 05:36 PM, Alan Evangelista wrote:
1) Is there are developer overview documentation? Having to browse through
Jenkins huge
code without any overview/design document to start is daunting.
As nobody answered this one, I assume that the answer here is "no".
Is there any Jenkins
On 05/06/2016 07:59 AM, Robert Sandell wrote:
2) If I understood correctly, Jenkins UI widgets are implemented in a MVC
style, similar to
Swing. .jelly files
are equivalent to Swing's view and Java classes in .java files are used
to implement
Swing's model.
Is that
Replies to a few inline...
On Thu, May 5, 2016 at 10:36 PM, Alan Evangelista wrote:
> Hi,
>
> I'm starting to browse through Jenkins code and I have a lot of questions.
>
> 1) Is there are developer overview documentation? Having to browse through
> Jenkins huge
>
lot of questions! I will try to answer a few
On Friday, May 6, 2016 at 6:37:04 AM UTC+10, Alan Evangelista wrote:
>
> Hi,
>
> I'm starting to browse through Jenkins code and I have a lot of questions.
>
>
> 7) Why there are hudson and jenkins packages? code in 'hudson' package
> uses different
Hi,
I'm starting to browse through Jenkins code and I have a lot of questions.
1) Is there are developer overview documentation? Having to browse through
Jenkins huge
code without any overview/design document to start is daunting.
2) If I understood correctly, Jenkins UI widgets are