Re: Update center is switched to v3.
One of the side-effects of this is that somebody running 1.553 May end up thinking that there's not much benefit in upgrading as all their plugins are up to date and it's just a new 1.645 core that is available. I think we need to start adding a flag to the metadata that says newer updates available with Jenkins X (Not much help to older Jenkins, but the sooner we add support, the better) On Thursday, November 6, 2014, Kohsuke Kawaguchi k...@kohsuke.org wrote: I've just switched over http://updates.jenkins-ci.org/ from the previous v2 layout from the new v3 layout. To my testing everything is working as expected, but if you see any hiccup or regressions in the next few days, let me know. This is a backend change that's invisible from Jenkins instances out there. The main motivation of this change is to serve the not exactly the latest but works with your Jenkins version of plugins from UC for older versions of Jenkins out there. This in turn allows plugin developers to adopt newer core features more aggressively, because doing so doesn't cut off users of earlier versions. They still see some version available for them to install. I'm using JENKINS-6097 https://issues.jenkins-ci.org/browse/JENKINS-6097 to track this. This is a pain we started to feel as we try to update plugins to be workflow-capable, which requires us to depend on 1.580. UC v3 attains this goal by generating 8 update sites for different version ranges, and use the version Jenkins reports to serve the best site. Previously we only had two, one for mainline and the other for LTS. As was with v2, The landing URL http://updates.jenkins-ci.org/update-center.json.html is always the same, so that you don't have to change update center config when you move from one version to another. I've captured some more details in here https://github.com/jenkinsci/backend-update-center2/blob/v3/site/README.md if anyone is interested. -- Kohsuke Kawaguchi -- 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 javascript:_e(%7B%7D,'cvml','jenkinsci-dev%2bunsubscr...@googlegroups.com'); . For more options, visit https://groups.google.com/d/optout. -- Sent from my phone -- 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. For more options, visit https://groups.google.com/d/optout.
New plugin developer
I would like to make some additions to an existing plugin. Looks like I need a user in repo.jenkins-ci.org. Can I please get one? My github account is https://github.com/rkonda And I am a little unsure of how the plugin development works. There is a github repo already that builds the maven package that's a jenkins plugin. I would think that I will fork the github repository, then import it into intellij (got that working nicely). Then there ought to be a way to run the plugin in debug mode that will start jenkins on my localhost, where in, I can install the plugin from my local store (not sure if this is automated), and then when a job is run, I ought to be able to hit a breakpoint. Is this all nicely documented somewhere? I looked at things like https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial but I am not sure if I am on the right track. I might be. Rajesh -- 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. For more options, visit https://groups.google.com/d/optout.
OWASP Markup Formatter Plugin
Can I get more information on the use and goals of https://wiki.jenkins-ci.org/display/JENKINS/OWASP+Markup+Formatter+Plugin ? Where can I find an explanation on the concepts of the OWASP Markup Formatter ? -- 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. For more options, visit https://groups.google.com/d/optout.
Re: OWASP Markup Formatter Plugin
https://www.owasp.org ? /B On Thu, Nov 6, 2014 at 9:57 AM, Stefan Lecho stle...@gmail.com wrote: Can I get more information on the use and goals of https://wiki.jenkins-ci.org/display/JENKINS/OWASP+Markup+Formatter+Plugin ? Where can I find an explanation on the concepts of the OWASP Markup Formatter ? -- 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. 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. For more options, visit https://groups.google.com/d/optout.
Re: Plugin usage statistics
Thanks Dominik for your reply. I already found the pages you mentioned - but they do not display all the information I am looking for... I guess I will create my own statistics then. Cheers, 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. For more options, visit https://groups.google.com/d/optout.
Just introducing my first RAD Studio Plugin
I just joined this group and am writing my first Jenkins plugin which I call RAD Studio Plugin. The project is already hosted on Bitbucket(!) as a Mercurial(!) repository at https://bitbucket.org/kazssym/jenkins-bds-plugin. If you are interested in continuous integration for RAD Studio projects, just send me your feedback. FYI, it is not yet a standalone Builder plugin but should be thought of as an add-on for MSBuild Plugin. It just allows you to set up environment variables for several RAD Studio versions by exposing them as Jenkins variables. I tried to direcctly set environment variables in a Builder for later invocation of MSBuild Plugin but I could not figure out the way to do it. So it is now based on BuildWrapper instead. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Plugin usage statistics
Feel free to sen PullRequests… Domi On 06.11.2014, at 12:29, martoe martin.ehrnhoe...@gmail.com wrote: Thanks Dominik for your reply. I already found the pages you mentioned - but they do not display all the information I am looking for... I guess I will create my own statistics then. Cheers, 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. 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. For more options, visit https://groups.google.com/d/optout.
Re: Update center is switched to v3.
This change might have caused issues with the plugin-info-macro on confluence. Cannot Load Update Center error 404 loading update-center.json https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin Domi On 06.11.2014, at 07:19, Kohsuke Kawaguchi k...@kohsuke.org wrote: I've just switched over http://updates.jenkins-ci.org/ from the previous v2 layout from the new v3 layout. To my testing everything is working as expected, but if you see any hiccup or regressions in the next few days, let me know. This is a backend change that's invisible from Jenkins instances out there. The main motivation of this change is to serve the not exactly the latest but works with your Jenkins version of plugins from UC for older versions of Jenkins out there. This in turn allows plugin developers to adopt newer core features more aggressively, because doing so doesn't cut off users of earlier versions. They still see some version available for them to install. I'm using JENKINS-6097 to track this. This is a pain we started to feel as we try to update plugins to be workflow-capable, which requires us to depend on 1.580. UC v3 attains this goal by generating 8 update sites for different version ranges, and use the version Jenkins reports to serve the best site. Previously we only had two, one for mainline and the other for LTS. As was with v2, The landing URL is always the same, so that you don't have to change update center config when you move from one version to another. I've captured some more details in here if anyone is interested. -- Kohsuke Kawaguchi -- 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. 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. For more options, visit https://groups.google.com/d/optout.
Re: New plugin developer
Am 06.11.2014 um 09:47 schrieb Rajesh K rkondapurcha...@gmail.com: I would like to make some additions to an existing plugin. Looks like I need a user in repo.jenkins-ci.org. Can I please get one? Please use https://jenkins-ci.org/account/ My github account is https://github.com/rkonda And I am a little unsure of how the plugin development works. There is a github repo already that builds the maven package that's a jenkins plugin. I would think that I will fork the github repository, then import it into intellij (got that working nicely). Then there ought to be a way to run the plugin in debug mode that will start jenkins on my localhost, where in, I can install the plugin from my local store (not sure if this is automated), and then when a job is run, I ought to be able to hit a breakpoint. Is this all nicely documented somewhere? I looked at things like https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial but I am not sure if I am on the right track. I might be. Most information is covered in the wiki: https://wiki.jenkins-ci.org/display/JENKINS/Extend+Jenkins There is also a section about debugging… Rajesh -- 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. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Update center is switched to v3.
On Thu, Nov 6, 2014 at 3:24 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: One of the side-effects of this is that somebody running 1.553 May end up thinking that there's not much benefit in upgrading as all their plugins are up to date and it's just a new 1.645 core that is available. Is this a real risk? If I am running Ubuntu 10.04 LTS, I am not going to see very many updates offered from apt-get upgrade. But I am not likely to interpret that as meaning that the community of Linux software developers has gone on sabbatical. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Update center is switched to v3.
On Thu, Nov 6, 2014 at 7:06 AM, domi d...@fortysix.ch wrote: This change might have caused issues with the plugin-info-macro on confluence. While we are on the topic, it would be nice if this macro were updated to · Note the availability of any newer alpha/beta release, not just the latest “stable” release. · List the latest release for each update center line. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: OWASP Markup Formatter Plugin
On Thu, Nov 6, 2014 at 3:57 AM, Stefan Lecho stle...@gmail.com wrote: Where can I find an explanation on the concepts of the OWASP Markup Formatter ? http://javadoc.jenkins-ci.org/hudson/markup/MarkupFormatter.html https://github.com/jenkinsci/antisamy-markup-formatter-plugin https://www.owasp.org/index.php/OWASP_Java_HTML_Sanitizer_Project -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Update center is switched to v3.
I just checked and it is showing the masthead correctly, so I assume this was a transient problem. 2014-11-06 4:06 GMT-08:00 domi d...@fortysix.ch: This change might have caused issues with the plugin-info-macro on confluence. *Cannot Load Update Center* error 404 loading update-center.json https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin Domi On 06.11.2014, at 07:19, Kohsuke Kawaguchi k...@kohsuke.org wrote: I've just switched over http://updates.jenkins-ci.org/ from the previous v2 layout from the new v3 layout. To my testing everything is working as expected, but if you see any hiccup or regressions in the next few days, let me know. This is a backend change that's invisible from Jenkins instances out there. The main motivation of this change is to serve the not exactly the latest but works with your Jenkins version of plugins from UC for older versions of Jenkins out there. This in turn allows plugin developers to adopt newer core features more aggressively, because doing so doesn't cut off users of earlier versions. They still see some version available for them to install. I'm using JENKINS-6097 https://issues.jenkins-ci.org/browse/JENKINS-6097 to track this. This is a pain we started to feel as we try to update plugins to be workflow-capable, which requires us to depend on 1.580. UC v3 attains this goal by generating 8 update sites for different version ranges, and use the version Jenkins reports to serve the best site. Previously we only had two, one for mainline and the other for LTS. As was with v2, The landing URL http://updates.jenkins-ci.org/update-center.json.html is always the same, so that you don't have to change update center config when you move from one version to another. I've captured some more details in here https://github.com/jenkinsci/backend-update-center2/blob/v3/site/README.md if anyone is interested. -- Kohsuke Kawaguchi -- 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. 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. For more options, visit https://groups.google.com/d/optout. -- Kohsuke Kawaguchi -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Update center is switched to v3.
I'm seeing the plugin-info-macro on Confluence generate wrong plugin version information on https://wiki.jenkins-ci.org/display/JENKINS/Dimensions+Plugin even though it was showing correctly as of yesterday. This may be because the version shown in the wiki page is what is now listed in http://updates.jenkins-ci.org/update-center.json (which is an old release from 2011), instead of the latest release (October 2014) which is correctly listed in http://updates.jenkins-ci.org/current/update-center.json and http://updates.jenkins-ci.org/update-center.json?version=1.549 (1.549 is version of parent POM I'm now using). Cheers, David. On Thursday, 6 November 2014 15:38:06 UTC, Kohsuke Kawaguchi wrote: I just checked and it is showing the masthead correctly, so I assume this was a transient problem. 2014-11-06 4:06 GMT-08:00 domi do...@fortysix.ch javascript:: This change might have caused issues with the plugin-info-macro on confluence. *Cannot Load Update Center* error 404 loading update-center.json https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin Domi On 06.11.2014, at 07:19, Kohsuke Kawaguchi k...@kohsuke.org javascript: wrote: I've just switched over http://updates.jenkins-ci.org/ from the previous v2 layout from the new v3 layout. To my testing everything is working as expected, but if you see any hiccup or regressions in the next few days, let me know. This is a backend change that's invisible from Jenkins instances out there. The main motivation of this change is to serve the not exactly the latest but works with your Jenkins version of plugins from UC for older versions of Jenkins out there. This in turn allows plugin developers to adopt newer core features more aggressively, because doing so doesn't cut off users of earlier versions. They still see some version available for them to install. I'm using JENKINS-6097 https://issues.jenkins-ci.org/browse/JENKINS-6097 to track this. This is a pain we started to feel as we try to update plugins to be workflow-capable, which requires us to depend on 1.580. UC v3 attains this goal by generating 8 update sites for different version ranges, and use the version Jenkins reports to serve the best site. Previously we only had two, one for mainline and the other for LTS. As was with v2, The landing URL http://updates.jenkins-ci.org/update-center.json.html is always the same, so that you don't have to change update center config when you move from one version to another. I've captured some more details in here https://github.com/jenkinsci/backend-update-center2/blob/v3/site/README.md if anyone is interested. -- Kohsuke Kawaguchi -- 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 javascript:. 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-de...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- Kohsuke Kawaguchi -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Error on wiki page of plugin: Cannot Load Update Center
Seems to have been a transient error.
On 06.11.2014, at 11:15, Dimitri Tenenbaum dim.tb...@gmail.com wrote:
Output of {jenkins-plugin-info} macro :
Plugin Information
Cannot Load Update Center
error 404 loading update-center.json
See: https://wiki.jenkins-ci.org/display/JENKINS/VncRecorder+Plugin
It worked all the time and there were no new changes on the wiki page.
Anybody have an idea how to fix the problem?
BR, Dimitri Tenenbaum
--
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.
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.
For more options, visit https://groups.google.com/d/optout.
Re: Plugin hosting request: jenkins-pushover-notifier
Hi Mzeher I am not able to install this pushover plugin , can you please help me understand and install the plugin with some basic steps. thanks Deepesh On Monday, April 1, 2013 7:59:25 AM UTC+1, mzehrer wrote: Hi Uli, thank you! Who takes care of the builds? Best, Michael On Sunday, March 31, 2013 6:44:39 PM UTC+2, Ullrich Hafner wrote: Yes. However, if your request is send at a weekend it is good to remind us again since not everybody is working at the weekend;-) The repository is created: https://github.com/jenkinsci/pushover-notifier-plugin A build needs to be set up by someone with more permissions :-) Ulli Am 31.03.2013 um 16:27 schrieb mzehrer mize...@gmail.com: Is posting here still the right procedure? On Saturday, March 9, 2013 5:30:10 PM UTC+1, mzehrer wrote: Hi, This is a plugin hosting request. 1) We are getting ready for the first release of the plugin, please setup a fork: https://github.com/mzehrer/jenkins-pushover-notifier 2) Please setup a build hive account/project for this pluign: https://buildhive.cloudbees.com/job/mzehrer/job/jenkins-pushover-notifier/ 3) My github account: https://github.com/mzehrer 4) My jenkins jira account https://issues.jenkins-ci.org/secure/ViewProfile.jspa mzehrer Best regards, Michael -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/d/optout.
