Re: slowness with jenkins 1.490
On 20. nov. 2012 14:42, ohad shai wrote: I also happened on 1.491 On Tuesday, November 20, 2012 2:30:22 PM UTC+2, ohad shai wrote: Hi, I upgraded from jenkins 1.482 to 1.490. I am using a war file directly. I noticed a huge slowness when loading the main web page and also some other jobs pages. Does anyone know about that issue? is it possible that this was already fixed? Thanks, Ohad. I have experienced the same issue. The main web page is very slow sometimes. Loading another page seems ok. For me it seems like it is only the main page. I am not sure if it happened after a special version of Jenkins or if it was after I installed the DropDown ViewsTabBar Plugin. We run version 1.491 now. Reagards Per A.
Re: New release of Dependency Graph View Plugin with experimental Javascript visualisation
I have tried 0.8. Looks promising, but still needs some work: 1) Can the layout algorithm be changed in jsplumb? Graphiz layout looks much nicer. 2) The ability to create new links/delete existing ones in jsplumb diagram should be disable-able - I understand the intention, but it is very easy to make a mistake on a cluttered diagram. I managed to accidentally create a circular dependency (a job starts itself as a downstream project) which should not be allowed at all. 3) Should jobs look like this - a blank rectangle with scroll bars? (see attached) On 11/14/12, Stefan Wolf glowwo...@gmail.com wrote: Could you try the just released version 0.6? On Wednesday, November 14, 2012 7:11:08 AM UTC-3, vladsed wrote: Jsplumb page does not show any links - only the jobs. I am using Jenkins 1.482 and Chrome 23.0.1271.64 m on Windows 7. Regards, Vladimir On 11/13/12, Stefan Wolf glow...@gmail.com javascript: wrote: Hi together, I just released a new version of the https://wiki.jenkins-ci.org/display/JENKINS/Dependency+Graph+View+Plugin. This version includes an experimental visualisation via jsPlumb based on work by domi. Since I am pretty new to javascript it would be very helpful to get some feedback on this functionally, both from end-users and from developers. So please send your comments, feature and pull requests! Best regards, Stefan attachment: jsplumb_job.png
Query about running different job steps on different slaves
Hi, Can anyone let me know if it is possible to execute different build steps on different slaves from within a single job? Is there any plugin that supports that? If not, what can be the workaround to achieve the same? Any help would be greatly appreciated. Thanks, Alok
Re: Query about running different job steps on different slaves
As far as I know, there is no plugin that lets you run individual build steps on a different slave than the one that job originally started on. But there ways to mimic this behavior. We do something like this in our own tests. One job starts up; it has a parameter that indicates another slave on which to run parts of the test. The original job (we call it the master job), then uses the Parameterized Trigger Plugin's build step plus the NodeLabel Plugin parameter to start another job (called a slave job) on the slave in question. The ParamTrig build step can be set to wait until the slave job is finished running - that gives us sequential behavior: steps run on the master, then on the slave, then on the master. Sometimes, we have to have steps running in parallel on the master and slave. In that case, the ParamTrig build step can also start the job on the slave then immediately return to its own steps. Synching the two executions can be difficult and tricky On Wednesday, November 21, 2012 6:18:29 AM UTC-8, alok kumar wrote: Hi, Can anyone let me know if it is possible to execute different build steps on different slaves from within a single job? Is there any plugin that supports that? If not, what can be the workaround to achieve the same? Any help would be greatly appreciated. Thanks, Alok
Re: Query about running different job steps on different slaves
You are welcome to follow-up / vote for these JIRA issues :) JENKINS-15397 2012/11/21 Jason Swager j.a.swa...@gmail.com As far as I know, there is no plugin that lets you run individual build steps on a different slave than the one that job originally started on. But there ways to mimic this behavior. We do something like this in our own tests. One job starts up; it has a parameter that indicates another slave on which to run parts of the test. The original job (we call it the master job), then uses the Parameterized Trigger Plugin's build step plus the NodeLabel Plugin parameter to start another job (called a slave job) on the slave in question. The ParamTrig build step can be set to wait until the slave job is finished running - that gives us sequential behavior: steps run on the master, then on the slave, then on the master. Sometimes, we have to have steps running in parallel on the master and slave. In that case, the ParamTrig build step can also start the job on the slave then immediately return to its own steps. Synching the two executions can be difficult and tricky On Wednesday, November 21, 2012 6:18:29 AM UTC-8, alok kumar wrote: Hi, Can anyone let me know if it is possible to execute different build steps on different slaves from within a single job? Is there any plugin that supports that? If not, what can be the workaround to achieve the same? Any help would be greatly appreciated. Thanks, Alok -- A.C. Linards L.
Re: Call for volunteers to work on security issues
I finally come back to this and added all those that volunteered. ... except Michael, where Google didn't let me. It said you opted out of being added/invited to a group. Any other e-mail address I can use to add you there? On 09/22/2012 10:29 AM, Kohsuke Kawaguchi wrote: Occasionally people discover vulnerabilities in Jenkins. Because of the nature of the problem, we need a closed-door venue to discuss and work on the fixes. We discussed about improving this process in the last project meeting [1], and as per the consensus, I created a new private mailing list [2]. This list will be used to discuss the fixes and vulnerabilities until the fix gets released. It receive notifications for tickets filed in the SECURITY project in JIRA [4]. This e-mail is a call for volunteers who would be willing to work on the security related issues. Because of the nature of the problem, we can't just add everyone like we do on our other repositories, but we do need several people on it to reduce the bus factor [5]. I request that only those who are interested in actually working on the fix to apply. We'd also like to require that you place CLA [6] before you apply. [1] http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-09-19-18.00.html [2] https://groups.google.com/forum/#!forum/jenkinsci-cert [3] https://wiki.jenkins-ci.org/display/JENKINS/Security+Advisories [4] https://issues.jenkins-ci.org/browse/SECURITY [5] http://en.wikipedia.org/wiki/Bus_factor [6] https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-ContributorLicenseAgreement%28CLA%29 -- Kohsuke Kawaguchi http://kohsuke.org/
Re: Call for volunteers to work on security issues
We haven't really thought of this all out, but I'd imagine we'll be doing it like Drupal does [1] --- interacting with the plugin maintainer to work on the fix. jenkinsci-c...@googlegroups.com supports anyone to post so it should be easy to run an e-mail thread with the plugin maintainer + the list. [1] https://www.acquia.com/blog/keeping-drupal-secure On 09/26/2012 03:04 PM, Bap wrote: Quoting Slide slide.o@gmail.com: How will this work in regards to plugins that might have security issues? Will the same pull request system be done so that the plugin maintainer can manage the releases and repo content? I'd suggest, that if a security report was submitted for a plugin, the first action of the security team should be to directly contact the maintainer of the plugin. The maintainer is likely to be in the best position to understand and fix the issue. -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins
Re: [ANN] Wiki moderators spam removal tool
Thanks. I added Michael and domi. On 11/18/2012 02:45 AM, domi wrote: I'm in: my Id for the wiki is is 'domi' /Domi On 18.11.2012, at 01:15, Kohsuke Kawaguchi k...@kohsuke.org wrote: I created a new group in Wiki called moderators that has a permission to delete pages. I've also packaged the spam remover tool [1], which can be used by moderators to detect spam pages and delete them en mass. If you are interested in joining this effort, please let me know your jenkins-ci.org account ID, so that I can add you to the group. (Thanks to larrys and orrc for pushing this effort.) [1] https://wiki.jenkins-ci.org/display/JENKINS/Wiki+Spams -- Kohsuke Kawaguchi -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins
Re: [ANN] Wiki moderators spam removal tool
On 11/18/2012 12:55 AM, Michael Clarke wrote: Kohsuke, I'll volunteer for this. On a semi-related note, did anything get progressed with the Security Issues group you're previously asked for volunteers for. I'd offered to assist on that and have submitted a CLA but never heard anything back (and notice there are 4 CLA pull requests still outstanding [1]) I just finally came around and handled it, but I couldn't add you. See my previous e-mail on that thread. Thanks, Michael [1] https://github.com/jenkinsci/infra-cla/pulls On 18 November 2012 00:15, Kohsuke Kawaguchi k...@kohsuke.org mailto:k...@kohsuke.org wrote: I created a new group in Wiki called moderators that has a permission to delete pages. I've also packaged the spam remover tool [1], which can be used by moderators to detect spam pages and delete them en mass. If you are interested in joining this effort, please let me know your jenkins-ci.org http://jenkins-ci.org account ID, so that I can add you to the group. (Thanks to larrys and orrc for pushing this effort.) [1] https://wiki.jenkins-ci.org/display/JENKINS/Wiki+Spams -- Kohsuke Kawaguchi -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins
Managing Plugin versions in Jira
Hi guys, Is there a way to add versions to plugin on issues.jenkins-ci.org what we have today is current, and if I would like to specify fixed in or Target versions current doesn't help much now does it :) Thanks HP
Re: Request for hosting
Done. https://github.com/jenkinsci/buddycloud-plugin Welcome aboard! On 11/20/2012 07:24 AM, Lloyd wrote: Hi all, I'd like to request hosting for my jenkins plugin which posts a message to a buddycloud channel. It is currently hosted in my github repo here: https://github.com/lloydwatkin/buddycloud-for-jenkins Cheers, Lloyd. -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins
Request for hosting
I've created a plugin that integrate with VMware vFabric Application Director. It allows deployments and end to end environment provisioning through Application Director. My github ID is jfullam. The following git repo can be forked: https://github.com/jfullam/jenkins-application-director Thanks!
Re: plugin changelog
Incidentally, I've been thinking about this problem for a while.
I think this should be split into several pieces.
- One that periodically run and generates what tickets are fixed in
what releases for all plugins across the board.
Update center backend [1] can generate all plugins, then
GAV-repo mapping [2] can map each release into tags, then all.git [3]
can be used to list up git commits between them.
This process should produce a folder hierarchy like
/{pluginName}/{version}/
- resolved/
- JENKINS-.json
- JENKINS-1135.json
- ...
- rev-list.txt
- ...
This process should work incrementally, and the output should be
committed to a dedicated repository.
Splitting things out in multiple files would allow us to manually
tweak them if we need to.
- we'll keep the workspace of this on wiki.jenkins-ci.org
- The jenkins-plugin-info macro gets updated to render this.
Making data available would allow other interesting use, such as update
center improvements to show what's new in place, and so on.
[1] https://github.com/jenkinsci/backend-update-center2/
[2] https://wiki.jenkins-ci.org/display/JENKINS/GAV-Repository+mapping
[3] http://git.jenkins-ci.org/?p=all.git;a=summary
On 11/20/2012 12:35 AM, nicolas de loof wrote:
Hi folks,
plugin changelog today is manually managed and in many case not updated
as a plugin is released.
I'd like to suggest we introduce some automation
proposal is to setup a confluence macro (as we have for plugin-info) to
auto generate plugin history from a CHANGELOG file in git repository
please note I don't know anything about confluence marco, but based on
what has been done with plugin-info this seems to be very powerfull, so
shouldn't be so complex
wdyt ?
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins
