Deprecating the Jenkow-plugin?

[Baptiste Mathus]

Hi,

See https://wiki.jenkins-ci.org/display/JENKINS/Jenkow+Plugin

I propose to deprecate this plugin for the following reasons:

   - His author added a comment stating:
   The Jenkow plugin is not under active development any more.
   

   - This plugin hasn't been released nor committed for more than 2+ years
   - There are only 7 installations in the world
   - There're far more active alternatives today with the workflow and even
   build flow plugin.

I'll proceed on roughly 48h from now if nobody objects (~sunday).

*Please note that adding the deprecation label will have the effect that
the Jenkow plugin will not be visible anymore from the Update Center.*

Cheers

-- 
Baptiste

-- 
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/CANWgJS78WJ98UYofG2CAi_4m5MR_EMF62aqrj91F%3DtipoQDJ5w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Deprecating the Jenkow-plugin?

[Slide]

+1

On Fri, Nov 20, 2015, 07:29 Baptiste Mathus  wrote:

> Hi,
>
> See https://wiki.jenkins-ci.org/display/JENKINS/Jenkow+Plugin
>
> I propose to deprecate this plugin for the following reasons:
>
>- His author added a comment stating:
>The Jenkow plugin is not under active development any more.
>
> 
>- This plugin hasn't been released nor committed for more than 2+
>years
>- There are only 7 installations in the world
>- There're far more active alternatives today with the workflow and
>even build flow plugin.
>
> I'll proceed on roughly 48h from now if nobody objects (~sunday).
>
> *Please note that adding the deprecation label will have the effect that
> the Jenkow plugin will not be visible anymore from the Update Center.*
>
> Cheers
>
> --
> Baptiste
>
> --
> 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/CANWgJS78WJ98UYofG2CAi_4m5MR_EMF62aqrj91F%3DtipoQDJ5w%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/CAPiUgVehbe-CSMLuZAz8Nci-c3%2B8ar8Y5fkAHQSCp1FuKoTNtw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Pull Request for compress-buildlog-plugin

[uwe schaefer]

Hi

according to the instructions, i'd like to drop a mail to the group, in 
order to hint for a somewhat stale pull request on the above mentioned 
plugin repo:

https://github.com/jenkinsci/compress-buildlog-plugin/pull/2

We're using this snapshot in-house for quite a while, so i am sure it works 
with our setup, but i'd love to have someone take a look at my changes 
before merging. (it is very little code)
Whatever i can do to help with the process - just let me know.

thanks

-- 
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/fe7059ab-6158-4487-b556-2a8efdf863fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: best ide

[Stephen Connolly]

There are really only three IDEs for Java: Eclipse, IntelliJ and NetBeans

For developing and debugging Jenkins, in my experience, keep as far away
from Eclipse as possible... but that is just my experience.

On 20 November 2015 at 07:44, tahoma tahrir  wrote:

> What is the best IDE for developing and debuging jenkins plugin?
>
> --
> 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/cb3e1e4a-2814-4bed-9a00-74dd56189ea3%40googlegroups.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/CA%2BnPnMzXqjbpz8gt6e2gJdM%3DXwnyU9ER7Cs6obbK7nM8gx41cA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Why doesn't this jelly page show the configuration

[Kanstantsin Shautsou]

I mean not shared code, but exactly code related to plugin lifecycle in 
'Plugin' class as it obvious place. With annotations in different parts of 
code you can't handle sequence of actions during start/stop. Spreading many 
start/stop/post-init hooks with annotations in different classes makes not 
obvious lifecycle, that's why using such Plugin class looks ok for me. 
If people don't know right extension points, then javadoc should only 
reference imho. 


On Wednesday, November 18, 2015 at 11:31:41 PM UTC+3, Jesse Glick wrote:
>
> On Wed, Nov 18, 2015 at 1:21 PM, Kanstantsin Shautsou 
>  wrote: 
> > I thought it is right entry Point if somebody wants to use some plugin 
> specific actions as it obvious entry point for plugin 
>
> Maybe I am not understanding what you wrote, but why do you need to 
> extend `Plugin` at all if you just want a class where you can put some 
> general-purpose code used throughout the plugin? 
>
> > I also thought that start/postInitialize is used to get earlier actions 
> for magic actions (i.e. alias XStream entries). 
>
> You can do such things in `@Initializer`. (Sometimes people use 
> `static` blocks in `Descriptor`s, in the particular case of XStream 
> aliases pertaining to the corresponding `Describable`, though that 
> idiom might break if we implement JENKINS-22050.) 
>

-- 
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/e8596a6c-10b9-4cc9-a3f3-13c48858c549%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Deprecating the Jenkow-plugin?

[Andrew Bayer]

+1
On Nov 20, 2015 09:56, "Slide"  wrote:

> +1
>
> On Fri, Nov 20, 2015, 07:29 Baptiste Mathus  wrote:
>
>> Hi,
>>
>> See https://wiki.jenkins-ci.org/display/JENKINS/Jenkow+Plugin
>>
>> I propose to deprecate this plugin for the following reasons:
>>
>>- His author added a comment stating:
>>The Jenkow plugin is not under active development any more.
>>
>> 
>>- This plugin hasn't been released nor committed for more than 2+
>>years
>>- There are only 7 installations in the world
>>- There're far more active alternatives today with the workflow and
>>even build flow plugin.
>>
>> I'll proceed on roughly 48h from now if nobody objects (~sunday).
>>
>> *Please note that adding the deprecation label will have the effect that
>> the Jenkow plugin will not be visible anymore from the Update Center.*
>>
>> Cheers
>>
>> --
>> Baptiste
>>
>> --
>> 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/CANWgJS78WJ98UYofG2CAi_4m5MR_EMF62aqrj91F%3DtipoQDJ5w%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/CAPiUgVehbe-CSMLuZAz8Nci-c3%2B8ar8Y5fkAHQSCp1FuKoTNtw%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/CAPbPdOYY3SO9-qtoxtXmF0TMO0T_hSrYZMAzmS9b%3Dz%3D7VcHS-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Why doesn't this jelly page show the configuration

['Jesse Glick' via Jenkins Developers]

On Fri, Nov 20, 2015 at 7:58 AM, Kanstantsin Shautsou
 wrote:
> With annotations in different parts of
> code you can't handle sequence of actions during start/stop. Spreading many
> start/stop/post-init hooks with annotations in different classes makes not
> obvious lifecycle

Nothing is stopping you from adding multiple `@Initializer`s (and/or
`@Terminator`s) in a single class if you find that clearest, though in
my experience each `@Initializer` is usually best placed in a class
related to its actual function, which is likely unrelated to any
others that happen to be present in the same plugin. So I do not buy
this as an argument for retaining `Plugin`.

-- 
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/CANfRfr3PKpKYbRnZ2yEHFHWCt4qCc7Lwr_GRcuowcc6PUD3hxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Why doesn't this jelly page show the configuration

[Kanstantsin Shautsou]

Ok. Fill PR with reference to this thread?

On Friday, November 20, 2015 at 9:23:00 PM UTC+3, Jesse Glick wrote:
>
> On Fri, Nov 20, 2015 at 7:58 AM, Kanstantsin Shautsou 
>  wrote: 
> > With annotations in different parts of 
> > code you can't handle sequence of actions during start/stop. Spreading 
> many 
> > start/stop/post-init hooks with annotations in different classes makes 
> not 
> > obvious lifecycle 
>
> Nothing is stopping you from adding multiple `@Initializer`s (and/or 
> `@Terminator`s) in a single class if you find that clearest, though in 
> my experience each `@Initializer` is usually best placed in a class 
> related to its actual function, which is likely unrelated to any 
> others that happen to be present in the same plugin. So I do not buy 
> this as an argument for retaining `Plugin`. 
>

-- 
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/10edf0fb-f4bf-4c8a-b1a6-02888d371e0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upgrading Plugin to use Credentials

['Jesse Glick' via Jenkins Developers]

On Thu, Nov 19, 2015 at 6:19 PM, Gavin Mogan  wrote:
> Is there a way to setup a parent default credential? (job -> folder -> global)

There is not currently any support for per-job credentials
(JENKINS-27398), but per-folder credentials are routine. The user may
configure credentials at the system level, a folder (or subfolder…),
or as part of the user account. Standard Credentials plugin APIs will
automatically search in the correct providers, if called with
appropriate arguments.

-- 
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/CANfRfr006fgGEg8TihOWQcKeGx8K6F2tjFfWwDApw2xhfc7U%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: best ide

['Jesse Glick' via Jenkins Developers]

On Fri, Nov 20, 2015 at 5:15 AM, Stephen Connolly
 wrote:
> For developing and debugging Jenkins, in my experience, keep as far away
> from Eclipse as possible

I have also heard of a lot of problems, but some people do it anyway.

Dedicated plugins exist for Jenkins plugin development in both IDEA
and NetBeans. I maintain the NetBeans integration. File » New Project
offers a new Jenkins plugin as an option, or File » Open Project and
navigate to the root directory of an existing one; when open, Debug »
Debug Project to launch `hpi:run` with the JPDA debugger connected,
etc.

-- 
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/CANfRfr2O4MQUo7RuoDwJ4iRTiTOd%2BJBTcg8L69VY30nwR9E1tQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

build-user-var-plugin: request for pull-request review, or plugin adoption

[Martin d'Anjou]

Hello Gavriil,

CC: jenkinsci-dev

Are you still the maintainer of the 
https://wiki.jenkins-ci.org/display/JENKINS/Build+User+Vars+Plugin ?


If so, I would like you to review some pull-requests to address this issue:
https://issues.jenkins-ci.org/browse/JENKINS-26953

The pull-requests links are in the issue link above.

If you are no longer interested in being the maintainer of the plugin, 
please let me know, I will adopt it.


Best Regards,
Martin d'Anjou

--
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/564F9627.3050802%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Request for hosting: Git Relasenotes Plugin

[Tomas Bjerre]

Repo: https://github.com/tomasbjerre/git-releasenotes-plugin
Username: tomasbjerre
JenkinsCI username: tomasbjerre

I made a pre-release here with some screenshots:
https://github.com/tomasbjerre/git-releasenotes-plugin/releases

This plugin may look similar to Git Changelog Plugin, and I actually would 
have taken that name if it was not already taken. But its very different 
when you look at it.

The basic idea is to use a Mustache template to render the changelog. This 
makes it very flexible! The changelog can:

 * Be stored to a file in workspace
 * Be rendered as summary of the build job
 * Be posted to a MediaWiki page!

Hope you like it!

-Tomas

-- 
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/06fbe64c-c228-47da-a5cd-b8d070dc16a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Deprecating the Jenkow-plugin?

[Christopher Orr]

On 20/11/15 15:29, Baptiste Mathus wrote:
> *Please note that adding the deprecation label will have the effect that
> the /Jenkow plugin/ will not be visible anymore from the Update Center.*

Note that this also means that the infobox will stop being populated soon.

Therefore the deprecation notice on the wiki page, which says "The code
is still available", won't be helpful, as the GitHub link will soon
disappear.

Just something to think about if you're considering making a standard
wiki macro for this stuff (I briefly saw an IRC conversation on that
topic earlier) :)

>From the good old Nabaztag example [0], a macro would probably need
something like this as configuration fields:

* Last known source code URL
* Archive link (just needs the artifact ID)
* Reason for removal (optional)
* Alternative plugins (optional)

Regards,
Chris

[0]:https://wiki.jenkins-ci.org/display/JENKINS/Nabaztag+Plugin

-- 
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/564F8B4C.7020007%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Pull Request for compress-buildlog-plugin

[Daniel Beck]

I'll take a look.

On 20.11.2015, at 15:23, uwe schaefer  wrote:

> Hi
> 
> according to the instructions, i'd like to drop a mail to the group, in order 
> to hint for a somewhat stale pull request on the above mentioned plugin repo:
> 
> https://github.com/jenkinsci/compress-buildlog-plugin/pull/2
> 
> We're using this snapshot in-house for quite a while, so i am sure it works 
> with our setup, but i'd love to have someone take a look at my changes before 
> merging. (it is very little code)
> Whatever i can do to help with the process - just let me know.
> 
> thanks
> 
> -- 
> 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/fe7059ab-6158-4487-b556-2a8efdf863fc%40googlegroups.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/AF6E57E1-6229-48D6-8382-A978FC19C54F%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: request document for jenkins plugin develop

[Ullrich Hafner]

https://wiki.jenkins-ci.org/display/JENKINS/Extend+Jenkins

> Am 20.11.2015 um 08:41 schrieb tahoma tahrir :
> 
> hi, i am beginning to developing jenkins plugin. i need pdf document for 
> that. where can i get it?
> 
> --
> 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/8f53875a-af18-49e6-a043-c0b3307b253d%40googlegroups.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/12090987-F25F-4844-9C03-7638B80B63A7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail