Re: Automatic Plugin Documentation [GSOC 2016]

[Daniel Beck]

> On 07.05.2016, at 01:00, martinda  wrote:
> 
> As a plugin user, and as a very occasional contributor, what would help me 
> document plugins better and faster would be to know where the documentation I 
> put in the code ends up on the web, and where to put the documentation in the 
> code (the help*.html files).

This project is about basically replacing today's plugin wiki pages by 
named-by-convention files in the GitHub repo (e.g. README.*), and integrating 
it into the jenkins.io site.

See the proposal titled 'Automatic plugin documentation publishing on 
https://jenkins-ci.org/' here for the basic idea:
https://wiki.jenkins-ci.org/display/JENKINS/Google+Summer+Of+Code+2016

So this does not deal with documentation inside the plugins as all. However, it 
should improve the situation for people who want to learn about plugins before 
installing them.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7B0C74DF-2772-4722-BC80-3E20FEE304C2%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Maven Plugin (a new release)

[Olivier Lamy]

Hi Craig,
I'm not sure if you need scm first or if they can have independant release?
I will try to do my best but lack of time next week (buzy weekend for me
next week).

Cheers
--
Olivier

On 6 May 2016 at 17:19, Craig Rodrigues  wrote:

> Hi,
>
> Would you be able to help with maven-scm plugin?
> See:
>
> http://mail-archives.apache.org/mod_mbox/maven-dev/201605.mbox/%3CCAG%3DrPVf6GP3tgXoaAGdru6bQ_CLONo%2BGQUcLPRWpDmP8KqGM7w%40mail.gmail.com%3E
>
> Thanks.
>
> --
> Craig
>
>
> On Thu, May 5, 2016 at 9:56 PM, Olivier Lamy 
> wrote:
>
>> Hi,
>> No worries.
>> I usually try to be as secret/quiet as possible!! :-)
>> BTW we are in an opensource world so as long as you have committer karma
>> you can do it as well :-)
>> Anyway I can try next week to cut a release (as I will be off from
>> thursday next week, if you don't see any release you will have to wait one
>> more week :-))
>> Cheers
>> Oli
>>
>> On 5 May 2016 at 04:58, Manuel Jesús Recena Soto 
>> wrote:
>>
>>> I'm sorry, I mean Olivier Lamy ;-)
>>>
>>> I was not sure what was your real name.
>>> On May 4, 2016 20:00, "Manuel Jesús Recena Soto" 
>>> wrote:
>>>
 Hello Olamy,

 Do you plan to cut a new release of Maven Plugin?

 I'd like to see this PR in a new release:
 https://github.com/jenkinsci/maven-plugin/pull/62

 Regards,

 --
 Manuel Recena Soto
 * manuelrecena.com [/blog]
 * linkedin.com/in/recena

>>> --
>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CABa-Uoe%2BDNkxMLsJi1eXYZO%3DeidKkmjavHPbqD%3DkUoMf_22A0w%40mail.gmail.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>>> Olivier Lamy
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>> --
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPoyBqT4BaPdoVC45PDg29v2%3D6%3Da9kgq_txjj9daHzBt7exLEw%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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3DrPVe1%3DpctZ%3DTUyQ%3D%3DMdNg49eo12fPc_zTPEu3siYqD_zoSg%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPoyBqRB0tTOKBWB%2BukKTAZfiTtOoA8Zqz5o66NKVvfHcfcNzg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Automatic Plugin Documentation [GSOC 2016]

[martinda]

Hello Cynthia,

As a plugin user, and as a very occasional contributor, what would help me 
document plugins better and faster would be to know where the documentation 
I put in the code ends up on the web, and where to put the documentation in 
the code (the help*.html files).

I don't know if this is part of the work you intend to do, but perhaps a 
plugin documentation guide section, in the plugin tutorial 
, would be 
useful. If I had a list of everything that can be documented (some sort of 
check-list), and where it is published (where users will see it), it would 
help me document the plugins I work on from time to time. I am sure I have 
seen plugin documentation documented somewhere but I can't find it right 
now. For those who write plugins more regularly, they just know what to do, 
but for occasional contributors like me, I have to look it up each time (by 
comparing with other plugins) and it is always time consuming - this should 
be easy to find.

I would also draw the attention to JENKINS-33980 
. To me this issue is 
an example that people do want to read detailed plugin documentation, 
before they installing plugins. Again, I don't know if this is part of your 
GSoC project.

Thanks in advance,
Martin

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/df5c74a1-b302-4158-aacb-f44939143cf4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC 2016][support-core plugin] Community Bonding

[Minudika Malshan]

Hi,

Thank you Arnaud for introducing me to the community.
First I would like to thank Steve and Arnaud for the massive support
they've given me so far throughout this project. It's an honor and a
pleasure to work with the amazing Jenkins community.
I will do my best on this project and I'm looking forward to work with you
all.

Thanks a lot.
Minudika

On Fri, May 6, 2016 at 10:18 PM, Arnaud Héritier 
wrote:

> Hi jenkins dev,
>
>   Minudika's proposal to improve our support-core plugin was accepted by
> Google (You may have seen this in another thread).
>
>   I would like to thanks Minudika for joining us and for the interest he
> has for this subject. Steven and myself will be mentoring this project but
> from my point of view all our community should be mentoring our students.
> Thus don't hesitate to guide him, help him and challenge him :-) (I think
> it should be the same for all our students)
>
>   About support-core plugin improvements to develop for GSoC we selected
> these 3 items :
>
>- https://issues.jenkins-ci.org/browse/JENKINS-33090 - Ease the
>management bundles by the administrator
>- https://issues.jenkins-ci.org/browse/JENKINS-21670 - Option to
>anonymize customer labels
>- https://issues.jenkins-ci.org/browse/JENKINS-33091 - Allow to create
>an issue and submit a bundle into the OSS tracker
>
>   The goal behind these issues is to ease the adoption/usage of the plugin
> and to have it useful for every jenkins plugin maintainer.
>
>   Minudika already started to learn about Jenkins and this plugin but I
> think that for the community bonding period it may makes sense to work with
> him on little improvements on this plugin (or otherscode) to have some
> concrete things to share/exchange.
>
>   In the support-core plugin we have already various entries in our
> backlog :
> https://issues.jenkins-ci.org/issues/?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20component%20%3D%20'support-core-plugin'
>  I don't know if some or them could be a good playground to start to play
> with.
>
>   All your feedbacks are welcome.
>
> Thanks
>
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMqS2UetwpV_uLvmu%3D1Gm31vpaExHNoaBWPv-vr77wuMiacoGg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[GSoC 2016][support-core plugin] Community Bonding

[Arnaud Héritier]

Hi jenkins dev,

  Minudika's proposal to improve our support-core plugin was accepted by
Google (You may have seen this in another thread).

  I would like to thanks Minudika for joining us and for the interest he
has for this subject. Steven and myself will be mentoring this project but
from my point of view all our community should be mentoring our students.
Thus don't hesitate to guide him, help him and challenge him :-) (I think
it should be the same for all our students)

  About support-core plugin improvements to develop for GSoC we selected
these 3 items :

   - https://issues.jenkins-ci.org/browse/JENKINS-33090 - Ease the
   management bundles by the administrator
   - https://issues.jenkins-ci.org/browse/JENKINS-21670 - Option to
   anonymize customer labels
   - https://issues.jenkins-ci.org/browse/JENKINS-33091 - Allow to create
   an issue and submit a bundle into the OSS tracker

  The goal behind these issues is to ease the adoption/usage of the plugin
and to have it useful for every jenkins plugin maintainer.

  Minudika already started to learn about Jenkins and this plugin but I
think that for the community bonding period it may makes sense to work with
him on little improvements on this plugin (or otherscode) to have some
concrete things to share/exchange.

  In the support-core plugin we have already various entries in our backlog
:
https://issues.jenkins-ci.org/issues/?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20component%20%3D%20'support-core-plugin'
 I don't know if some or them could be a good playground to start to play
with.

  All your feedbacks are welcome.

Thanks

-
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-9n6qTPGGijM9vu4bVhjzvOO6_0fBM%3D4eD7msT%2BHg5WcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jelly question: How to construct the URL of a section on the Jenkins configuration page?

[Martin Weber]

Am Freitag, 6. Mai 2016, 15:15:38 schrieb Robert Sandell:
> True, but since the specific section he mentioned to link to is gone in 2.0
> I saw no need :)
> 
> But yea, something is adding those anchor points, but it's not
> lib/form/section.jelly so some magic javascript seems to be adding them
> after the jelly has been rendered.

It is in lib/form/breadcrumb-config-outline/init.js

I inspected the generated config page and found a 
  element is generated for each section. The element has a _name_ 
attribute with a value derived from the tool descriptor.
For the JDK tool, it gives
 

W3C says, there is no name attribute allowed for , but it is allowed for  
. 
Looks like someone already tried to generate an anchor here, but messed up the 
jelly code.

Martin

-- 
Cd wrttn wtht vwls s mch trsr.


-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1579286.g8drh4QRpN%40linux.
For more options, visit https://groups.google.com/d/optout.

Re: Jelly question: How to construct the URL of a section on the Jenkins configuration page?

[Martin Weber]

Am Freitag, 6. Mai 2016, 13:46:13 schrieb Robert Sandell:
> Links in the side panels are implementations of Action. And you can add
> transient actions to jobs via the TransientActionFactory extension
> point.
> 
> In Jenkins 2.0 the Global Tool Configuration got put on a separate
> configuration page, like what has happened earlier with the Global Security
> Configuration.

So, if that is an a separate page now, I see no point to place a link on the 
job page.

Martin

-- 
Cd wrttn wtht vwls s mch trsr.


-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2780188.ISBOjQh2vK%40linux.
For more options, visit https://groups.google.com/d/optout.

Re: Jelly question: How to construct the URL of a section on the Jenkins configuration page?

[Robert Sandell]

Ok, so those anchors are added by
lib/form/breadcrumb-config-outline/init.js and it is just using a counter
for each achor it adds, so it won't be easy to guess what that would be,
there is a TODO marked in that file to make a more user friendly id, but
who knows when someone will take that on :)

Instead In your case I would try to add my own, more deterministic anchors
in a similar way as the breadcrumb init.js is doing that for example uses
the backend id of the section (or fix the js in core to also use the id).

/B

On Fri, May 6, 2016 at 3:15 PM, Robert Sandell 
wrote:

> True, but since the specific section he mentioned to link to is gone in
> 2.0 I saw no need :)
>
> But yea, something is adding those anchor points, but it's not
> lib/form/section.jelly so some magic javascript seems to be adding them
> after the jelly has been rendered.
>
> /B
>
> On Fri, May 6, 2016 at 1:57 PM, Daniel Beck  wrote:
>
>>
>> > On 06.05.2016, at 13:46, Robert Sandell  wrote:
>> >
>> > Links in the side panels are implementations of Action. And you can add
>> transient actions to jobs via the TransientActionFactory extension
>> point.
>>
>> I think you're missing the point here. The problem isn't how to place the
>> link, it's how to link to a specific section of the target form.
>>
>> --
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/0D1B15DD-59F8-4320-B159-76996B1B8B1F%40beckweb.net
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Robert Sandell
> *Software Engineer*
> *CloudBees Inc.*
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS1oF5LoemCzqc%2BNNbO68RVr%3DziL%2BiU45Vp0nvYYSouo4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jelly question: How to construct the URL of a section on the Jenkins configuration page?

[Robert Sandell]

True, but since the specific section he mentioned to link to is gone in 2.0
I saw no need :)

But yea, something is adding those anchor points, but it's not
lib/form/section.jelly so some magic javascript seems to be adding them
after the jelly has been rendered.

/B

On Fri, May 6, 2016 at 1:57 PM, Daniel Beck  wrote:

>
> > On 06.05.2016, at 13:46, Robert Sandell  wrote:
> >
> > Links in the side panels are implementations of Action. And you can add
> transient actions to jobs via the TransientActionFactory extension
> point.
>
> I think you're missing the point here. The problem isn't how to place the
> link, it's how to link to a specific section of the target form.
>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/0D1B15DD-59F8-4320-B159-76996B1B8B1F%40beckweb.net
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS3EwQiB0v3drjy2qOgzotEkGpLO76N-rAvD4Fehn6%2Bkgw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jelly question: How to construct the URL of a section on the Jenkins configuration page?

[Daniel Beck]

> On 06.05.2016, at 13:46, Robert Sandell  wrote:
> 
> Links in the side panels are implementations of Action. And you can add 
> transient actions to jobs via the TransientActionFactory extension point.

I think you're missing the point here. The problem isn't how to place the link, 
it's how to link to a specific section of the target form.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0D1B15DD-59F8-4320-B159-76996B1B8B1F%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: [JENKINS-30189] Add option to [mercurial plugin to] ignore certain commits, e.g. by user

[Ken Guest]

Thanks Aldrin,

I wasn't aware of that plugin - it seems very useful.

Ken

On Thursday, May 5, 2016 at 4:10:10 PM UTC+1, Aldrin Leal wrote:
>
> Wouldnt altering "CI Skip" Plugin to add this behaviour be possible?
>
> --
> -- Aldrin Leal,  / 
> http://about.me/aldrinleal
>
> On Thu, May 5, 2016 at 10:07 AM, Ken Guest  
> wrote:
>
>> Hi,
>>
>> For whatever reason I can't seem to get any password resets or related 
>> actions to work when attempting to log in to vote for adding functionality 
>> to the  mercurial plugin  so it can
>> optionally ignore commits from specified users. ( 
>> https://issues.jenkins-ci.org/browse/JENKINS-30189 ). Does voting on 
>> issues make a difference anyway?
>>
>> I thought it would be an idea to email this list to see if anybody might 
>> need do something to get those password resets/emails working again.
>>
>> I haven't developed anything in Java in over a decade, but if there is 
>> something I can do (or learn) to add that functionality to the mercurial 
>> plugin for jenkins I'd love to know what it might be.
>>
>> Any pointers?
>>
>> I found https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial and 
>> am reading my way through it - and through a few related articles.
>>
>> Thanks,
>>
>> Ken
>>
>>
>> -- 
>> http://about.me/kenguest/
>>
>> -- 
>> 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 jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAKcc2m-Ps2Hoei_10XWrPiaHsexe1Bb6vuUEhwT%2BYr_X1ZM_9g%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/d350ff2f-5246-4519-af3c-578ae91b581c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jelly question: How to construct the URL of a section on the Jenkins configuration page?

[Robert Sandell]

Links in the side panels are implementations of Action. And you can add
transient actions to jobs via the TransientActionFactory extension
point.

In Jenkins 2.0 the Global Tool Configuration got put on a separate
configuration page, like what has happened earlier with the Global Security
Configuration.
Those pages are implementations of ManagementLink which extends Action. So
you could try to just return that management link from your
TransientActionFactory if the user has admin access.

/B

On Wed, May 4, 2016 at 10:26 PM, Martin Weber 
wrote:

> Hi all,
>
> I want to create a HTML-link on the job configuration page that directly
> points to the corresponding tool installation section on *global*
> configuration page. (Well, yes, this is teamcity inspired:-)
>
> I know that
> '${rootURL}/configure'
> points to the config page, but how do I get the anchor on that page that
> directly points to (for example) 'Maven installations' section?
>
> From the breadcumb navigation on the config page, the URL would be
> 'http://localhost:8080/jenkins/configure#section45' on my jenkins
> instance,
> but that seems to be very instance-specific.
>
> In my case, I would like to get the URL of the config section contributed
> by
> Java class "hudson.plugins.cmake.CmakeTool extends ToolInstallation".
>
> TIA,
> Martin
>
> --
> Cd wrttn wtht vwls s mch trsr.
>
>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/4219326.MqEhROkAH0%40linux
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS3QjDFpZXBmT2Ajm64T4H3XoY4wiQd7EiH-xzBbOx_1_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Newbie developer questions

[Robert Sandell]

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
>code without any overview/design document to start is daunting.
>
> 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 correct?
>

No, not really. But it's trying to use some of those principles that each
object can have a view.


> 3) Jenkins UI screens are implemented in a similar way to UI widgets,
> mentioned in (2) ?
>
> 4) Where do I find the mapping between Jenkins URLs and screens? It seems
> to me a library
> used Stapler is used (it is the entry point class defined in
>  in web.xml),
> but I am not sure how it is configured
>

See http://stapler.kohsuke.org/


>
> 5) Where is Jenkins web UI index page (.jelly and Java class ?) in code?
>

https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/Jenkins.java
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/Jenkins.java#L4309
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/Jenkins.java#L4361
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AllView.java
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/model/View/index.jelly


>
> 6) Where is the Jenkins API entry point (class) ?
>

https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/Jenkins.java#L1126
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Api.java


>
> 7) Why there are hudson and jenkins packages? code in 'hudson' package
> uses different
> standards / base (Jenkins or third-party) code, it is code which Jenkins
> currently share with
> the Hudson project or it is "just" a matter of pending renaming?
>
> 8) What exactly is the scope of the code in
> core/src/main/java/jenkins/model/ ? afaik in MVC,
> all non UI-specific codeis in "model" layer, so things like 
> core/src/main/java/scm/,
>
> core/src/main/java/security/ and core/src/main/java/tasks/ would also
> belong to the 'model'
> layer and would be in a 'model' Java package.
>
> 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?
>
> 10) Build data structure (eg which attributes are retrieved) obtained via
> Jenkins API is
> implicitly inferred from somewhere or there is a explicit mapping defined
> somewhere?
>
> 11) I'd like to create a plugin which parses every job console output and
> if it finds some
> special keyword/expression (eg "Job output"), it gets the string that
> comes after it,
> formats it and adds that to a "output" attribute returned by the Jenkins
> API (and if
> possible, shown as a separate field in the build metadata in the Jenkins
> web UI).
> Is it possible? Is there any plugin extension point which would allow such
> a feature?
> Could you give me pointers in how to implement it?
>
>
> Any help is welcome.
>
> Regards,
> Alan Evangelista
>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/572BAEE8.5080402%40linux.vnet.ibm.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS30dYi9tnbqHu%3DRBXTC7ZW%2BeAjdjgpj3%3D6-z5WTTqdt_Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Maven Plugin (a new release)

[Manuel Jesús Recena Soto]

Hello Olivier,

(replies inline)

2016-05-06 6:56 GMT+02:00 Olivier Lamy :
> Hi,
> No worries.
> I usually try to be as secret/quiet as possible!! :-)

I'm used to use the nicknames, I'm a oldschool ;)

> BTW we are in an opensource world so as long as you have committer karma you
> can do it as well :-)

I know it, but I prefer to ask first.

> Anyway I can try next week to cut a release (as I will be off from thursday
> next week, if you don't see any release you will have to wait one more week
> :-))

Thanks so much.

> Cheers
> Oli
>
> On 5 May 2016 at 04:58, Manuel Jesús Recena Soto  wrote:
>>
>> I'm sorry, I mean Olivier Lamy ;-)
>>
>> I was not sure what was your real name.
>>
>> On May 4, 2016 20:00, "Manuel Jesús Recena Soto"  wrote:
>>>
>>> Hello Olamy,
>>>
>>> Do you plan to cut a new release of Maven Plugin?
>>>
>>> I'd like to see this PR in a new release:
>>> https://github.com/jenkinsci/maven-plugin/pull/62
>>>
>>> Regards,
>>>
>>> --
>>> Manuel Recena Soto
>>> * manuelrecena.com [/blog]
>>> * linkedin.com/in/recena
>>
>> --
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CABa-Uoe%2BDNkxMLsJi1eXYZO%3DeidKkmjavHPbqD%3DkUoMf_22A0w%40mail.gmail.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> Olivier Lamy
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPoyBqT4BaPdoVC45PDg29v2%3D6%3Da9kgq_txjj9daHzBt7exLEw%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Manuel Recena Soto
* manuelrecena.com [/blog]
* linkedin.com/in/recena

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CABa-Uoe%2B-jJrwOrn9c1Tgs7eU4t0xnbyxDkpdyVPS70mSE%2B3nQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.