Re: Discussion: Refactoring of JENKINS project in JIRA
On 10.06.2014, at 07:09, Oleg Nenashev o.v.nenas...@gmail.com wrote: https://github.com/jenkinsci/ant-plugin Sorry about that. Confused it with the Maven build step that's part of core. -- 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: DotCi - plugin hosting request
KK challenged me at FOSDEM to prototype a way to store projects and builds in something like Mongo since XStream has JSON support. Although I haven't produced any code yet, I have been studying the areas in core that might be affected and have some suggestions on new ExtensionPoints that should at least get us started towards having plugins provide new ways of project and build storage. Robert Sandell Software Tools Engineer - SW Environment and Product Configuration Sony Mobile Communications -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Andrew Bayer Sent: den 10 juni 2014 00:57 To: jenkinsci-dev@googlegroups.com Subject: Re: DotCi - plugin hosting request Yeah, wow - this is amazing stuff. I'd really love to see the DbBackedProject/Build stuff available outside of the .ci.yml stuff - I'm currently accumulating masses of information on builds using https://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer to gather a ton of information on every build (not just failing ones now) for metrics analysis, but being able to store the whole thing in Mongo would be a dream. I know that hurts Kohsuke's love for XML, but yeah. =) A. On Sun, Jun 1, 2014 at 11:05 AM, Kohsuke Kawaguchi k...@kohsuke.org wrote: Turns out this was because the repository didn't end in -plugin. I've improved the code to look at pom.xml. And that created https://jenkins.ci.cloudbees.com/job/plugins/job/DotCi/ 2014-06-01 10:48 GMT-07:00 Kohsuke Kawaguchi k...@kohsuke.org: This is supposed to happen automatically now that your repo is in the jenkinsci org. Let me look into why that's not happening. 2014-05-30 14:57 GMT-07:00 Surya Gaddipati suryapraka...@gmail.com: On a sidenote it would be great if we could set this up at https://jenkins.ci.cloudbees.com/ at some point so we can set commit statuses on github prs in in jenkins plugin github projects. It would be great to use jenkinsci 'build-passing' badges instead of travisci :). On Tuesday, May 20, 2014 11:36:30 AM UTC-5, Surya Gaddipati wrote: https://github.com/groupon/DotCi github usename: suryagaddipati -- 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 -- 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. -- 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: Commit access to https://github.com/jenkinsci/dimensionsscm-plugin
Hi, Let me know if I need to provide anything beyond my GitHub ID dconneely to be added as a committer to the jenkinsci/dimensionsscm-plugin repository. Tim Payne (current maintainer) has asked me to request this and he can confirm. Cheers, David. On Monday, 2 June 2014, David Conneely david.conne...@gmail.com wrote: Hi Jenkins Developers, I work with Tim Payne, the maintainer of the Dimensions SCM plugin, and he has asked that I send a request to this list for commit access to the https://github.com/jenkinsci/dimensionsscm-plugin repository. My GitHub ID is dconneely. Many thanks in advance, David Conneely. -- 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. -- 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: Commit access to https://github.com/jenkinsci/dimensionsscm-plugin
Hi Would someone with the appropriate privileges be able to help David out with this, please? Thanks! On 10 Jun 2014, at 09:18, David Conneely david.conne...@gmail.commailto:david.conne...@gmail.com wrote: Hi, Let me know if I need to provide anything beyond my GitHub ID dconneely to be added as a committer to the jenkinsci/dimensionsscm-plugin repository. Tim Payne (current maintainer) has asked me to request this and he can confirm. Cheers, David. On Monday, 2 June 2014, David Conneely david.conne...@gmail.commailto:david.conne...@gmail.com wrote: Hi Jenkins Developers, I work with Tim Payne, the maintainer of the Dimensions SCM plugin, and he has asked that I send a request to this list for commit access to the https://github.com/jenkinsci/dimensionsscm-plugin repository. My GitHub ID is dconneely. Many thanks in advance, David Conneely. -- 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.comjavascript:_e(%7B%7D,'cvml','jenkinsci-dev%2bunsubscr...@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.commailto: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 - Load Impact load testing plugin
Thanks Ulli! /Ragnar -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Plugin-hosting-request-Load-Impact-load-testing-plugin-tp4704851p4705784.html Sent from the Jenkins dev mailing list archive at Nabble.com. -- 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: Parameter Separator Plugin hosting
Created https://github.com/jenkinsci/parameter-separator-plugin Sorry for the delay. Welcome aboard! Ulli Am 10.06.2014 um 03:30 schrieb Mike Chmielewski c...@mikec.123mail.org: Any hope of this getting hosted? - Original message - From: Mike Chmielewski c...@mikec.123mail.org To: jenkinsci-dev@googlegroups.com Subject: Fwd: Re: Parameter Separator Plugin hosting Date: Mon, 19 May 2014 21:44:58 -0400 So I've changed it to return a dummy ParameterValue with the generated name as the value. If anyone is interested in taking my code and merging it with theirs, feel free. Otherwise, I hope the new version can be hosted on the Jenkins site. - Original message - From: Mike Chmielewski c...@mikec.123mail.org To: Oleg Nenashev o.v.nenas...@gmail.com, jenkinsci-dev@googlegroups.com Subject: Re: Parameter Separator Plugin hosting Date: Mon, 19 May 2014 09:29:54 -0400 Thanks Oleg! This is my first rudimentary attempt, which is why I went the plugin route. I have no idea where in the Jenkins core code to put this, which is what I assume you are recommending in your first point? I can certainly investigate. I will absolutely fix the NPE issue. Would converting the null returns to empty strings or the name of the parameter instance work? The values are likely never going to be used, since this parameter' is really just for creating UI element. - Original message - From: Oleg Nenashev o.v.nenas...@gmail.com To: jenkinsci-dev@googlegroups.com Cc: c...@mikec.123mail.org Subject: Re: Parameter Separator Plugin hosting Date: Mon, 19 May 2014 02:49:59 -0700 (PDT) Hi Mike, I'd recommend to merge the plugin's code somewhere. I think the feature does not require a separate plugin The plugin will cause massive Executor failures if somebody triggers a job with your parameter from CLI or MultiJob plugin. See https://issues.jenkins-ci.org/browse/JENKINS-15094 If you want to use the current approach, I kindly ask you to wait till the fix of the referenced issue Best regards, Oleg Nenashev понедельник, 19 мая 2014 г., 6:26:46 UTC+4 пользователь Mike Chmielewski написал: I have a really basic plugin that allows one to separate logical groups of parameters on the build parameters page, to (hopefully) make it easier to read/ parse a list of options. It uses an hr/ tag, and allows global customization of the styling. It's all hosted on github, so feel free to fork it (it's MIT licensed). Github Repository: parameter-separator-plugin Github ID: olhado -- Mike Chmielewski co...@mikec.123mail.org -- Mike Chmielewski i...@mikec.123mail.org -- 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. -- Mike Chmielewski c...@mikec.123mail.org -- 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: Commit access to https://github.com/jenkinsci/dimensionsscm-plugin
Done. Welcome aboard! Ulli Am 10.06.2014 um 10:18 schrieb David Conneely david.conne...@gmail.com: Hi, Let me know if I need to provide anything beyond my GitHub ID dconneely to be added as a committer to the jenkinsci/dimensionsscm-plugin repository. Tim Payne (current maintainer) has asked me to request this and he can confirm. Cheers, David. On Monday, 2 June 2014, David Conneely david.conne...@gmail.com wrote: Hi Jenkins Developers, I work with Tim Payne, the maintainer of the Dimensions SCM plugin, and he has asked that I send a request to this list for commit access to the https://github.com/jenkinsci/dimensionsscm-plugin repository. My GitHub ID is dconneely. Many thanks in advance, David Conneely. -- 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. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: New servlet container for Jenkins CI
On Thu, Jun 5, 2014 at 2:12 PM, Kohsuke Kawaguchi kkawagu...@cloudbees.com wrote: I started java -jar jenkins.war just as a convenience, but […] more than 80% of the installation base is running on this container today. FYI, many of the large companies CloudBees has a support customers run Jenkins via native packages, typically RPM, and these use the built-in container. So making it fast by default is definitely laudable. As to mismatch with hpi:run, this is definitely a concern—although there is no reason hpi:run (and hudson-dev:run, used by jenkinsci/jenkins/war) could not be switched to Undertow as well, especially if it started a bit faster. Generally speaking we ought to be running acceptance tests in a variety of containers to catch container-specific problems: at least Jetty, Undertow, and Tomcat, and at least during LTS RC testing (may be too expensive to do more often than that). -- 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: Solidifying acceptance-test-harness API
On Thu, Jun 5, 2014 at 5:16 PM, Ulli Hafner ullrich.haf...@gmail.com wrote: it feels quite unusual to make the Assert class the topmost class of our inheritance hierarchy Agreed, extending a class (or implementing an interface) to get static methods (resp. constants) is poor style when a static wildcard import would suffice. -- 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: Why doesn't copying an hpi file to JENKINS_HOME/plugins/ work?
On Mon, Jun 9, 2014 at 12:10 AM, Code ekkapo...@gmail.com wrote: curl -O http://updates.jenkins-ci.org/latest/chucknorris.hpi Try saving as chucknorris.jpi. -- 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: Is there an extension point for listening to login events
On Mon, Jun 9, 2014 at 12:44 PM, Surya Gaddipati suryapraka...@gmail.com wrote: I would like to implement an housekeeping method on user when he/she logs in. Is there a extension point I can use to listen to to login events? Yes. SecurityListener. -- 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: People using the LDAP plugin to connect to Active Directory
On Sun, Jun 8, 2014 at 1:35 PM, ogondza ogon...@gmail.com wrote: We _do_ want to know that version under test work on its own and not only if you upgrade your config from some earlier version. It is nice to verify this, but the plugin maintainer is often passively verifying this as they work on changes anyway, and it is much less important than verifying that everything still works after an upgrade. If we start using config xml to configure/verify we are introducing another interface that can and will change. As we have to keep all our page objects there will be more breakage due to changes in SUT than before I think you only need to update the code generating the XML configs if and when a new test needs to work with new config options. such tests will be close to useless a year from now as it will be performing upgrades most users already performed. Not necessarily true. Just because someone is running a newer version of core or a plugin already does not mean they have resaved a particular kind of configuration using a new format introduced by that version. And plenty of people are running rather old plugin releases, I am afraid. One way or another we will need to be testing a variety of configuration upgrades. (Some in-plugin integration tests already do so using @LocalData of course.) But a lot of tests are not “about” this topic; they are really testing some behavior which does not have much to do with a particular storage format version. So picking an overall harness infrastructure based on the ease of writing configuration upgrade tests is probably overkill. That said, I would much rather write tests which used a simple DSL for configuring Jenkins and some jobs and slaves etc. in a particular way as either XML or in-process Java/Groovy calls than have to set up everything from scratch using the current page objects, which are painfully slow to run and prone to irrelevant failures. Obviously the web driver is useful for the limited number of tests which are actually written to check the configuration UI. As a general comment, I would really like to see ATH live on a continuum with in-plugin unit and integration tests, rather than using a totally different mechanism with no overlap as today. Specifically I would like to be able to · Include acceptance tests in a plugin source repository, or otherwise rapidly rerun those tests after incremental changes to plugin source. · To be able to use Docker fixtures from JenkinsRule or other tests. (This system seems to have no important dependencies on the rest of ATH and ought to be a standalone project that could be used as a org.junit.Rule by any JUnit 4.x test.) · Use core/plugin Java API calls to set up a test but then use HtmlUnit and/or Selenium with page objects to run certain parts. -- 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: Discussion: Refactoring of JENKINS project in JIRA
On Tue, Jun 10, 2014 at 3:34 AM, Daniel Beck m...@beckweb.net wrote: Confused it with the Maven build step that's part of core. (but which ought to be a plugin too) -- 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: DotCi - plugin hosting request
Jesse, you do know that only I may call KK with I told you so style taunts ;-) On 10 June 2014 15:45, Jesse Glick jgl...@cloudbees.com wrote: On Tue, Jun 10, 2014 at 3:49 AM, Sandell, Robert robert.sand...@sonymobile.com wrote: KK challenged me at FOSDEM to prototype a way to store projects and builds in something like Mongo since XStream has JSON support. So KK are you backing away from your decision to go with SQL in db-plugin? We need to have some strategic decision about how build records will be stored in the future. (The current one-XML-file-per-build scheme is the source of many serious performance problems with Jenkins. Lazy loading did not really help, because many legitimate queries require historical information, and now instead of doing all the I/O work once during startup we are reloading builds again and again from HTTP service threads.) -- 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: Refreshing the Jenkins UI
Apologies if this has been brought up already, but all my emails contain the
orbs, my email-ext template currently has,
IMG SRC=${rooturl}static/images/32x32/(blue.gif/red.gif/yellow.gif) /
Would converting to a js/css orb blow this away? I tried adding this to an
email and (unsurprisingly) Outlook doesn't show anything. Not even a yellow
square.
div
style=width:32px;height:32px;display:inline-block;border-radius:50%;background:yellow;background-image:
radial-gradient(circle at 3px 3px, white 0%, #FFB738 100%); /
-Andrew
-Original Message-
From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On
Behalf Of Kohsuke Kawaguchi
Sent: Monday, June 09, 2014 7:46 PM
To: jenkinsci-dev@googlegroups.com
Subject: Re: Refreshing the Jenkins UI
OK, great.
So maybe not for the form changes, but I think the idea is still generally
useful to answer the question Daniel Beck raised (below) in a satisfactory way:
Forcing all plugins that use affected core resources to choose between
looking outdated and requiring the latest and greatest as minimum
compatible version would be a bad idea.
With the compatibility plugin, plugins can look consistent regardless of
Jenkins versions they run on, without forcing the latest greatest as the
minimum required version.
(And in 100 or so releases, plugins can drop this plugin as a requirement and
simply start relying on the new core.)
On 06/09/2014 04:30 PM, Stephen Connolly wrote:
Ha! I got quite far retaining compatibility... There are a few plugins
that copypaste the tags rather than using the tag directly (eg some of
the ones I wrote do that to work around bugs in the core tags in eg
1.424 or 1.460) given those baselines are quite old I suspect just
reverting back to using tags directly would be sufficient to get all
plugins working either side of the big UI switch to divs...
You can see some of our progress in the div-fanatic-experiment branch...
Still need to fix structured form submission mind you ;-)
On Monday, 9 June 2014, Kohsuke Kawaguchi kkawagu...@cloudbees.com
mailto:kkawagu...@cloudbees.com wrote:
I suspect we need a compatibility plugin like this anyway to hide
the layout changes (div vs table) and so on.
On 06/09/2014 03:47 PM, Kohsuke Kawaguchi wrote:
I assume we are only talking about the flashing orb here ---
other icons
(say the terminal icon) are just fine with them being images, and
whatever animations you might require (like fading, etc) can be done
with img+css.
As for the compatibility issue, what if we produce a plugin that
encapsulates the fallback behaviour?
For the flashing ball images, the said plugin can define a tag
file like:
c:ball icon=${run.iconColor} size=24 /
... and the tag can expand to img (if running on today's
Jenkins) or
div (if running on tomorrow's Jenkins)
On 06/06/2014 10:33 AM, Tom Fennelly wrote:
All the icons in Jenkins are hardcoded as images in the
Jelly scripts.
We were hoping to move away from this (ala Doony) by
using CSS + some
Javascript (for the animation). Seems like this is not
possible to do
without getting into screen-scraping hacks
https://github.com/tfennelly/__jenkins/blob/orb-orb/core/src/__main/resources/lib/layout/orb.__js#L80
https://github.com/tfennelly/jenkins/blob/orb-orb/core/src/main/resources/lib/layout/orb.js#L80
because the imgs are used out in plugins too (not just in
the core
Jenkins code) e.g. the maven plugin.
I guess this means we're stuck with using images Vs CSS
+Javascript ?
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins
--
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
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
mailto:jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe
Re: DotCi - plugin hosting request
In DotCi builds are still stored as xml in mongodb with some fields like pusher, sha, branch, status etc stored as json attributes for querying . I tried serializing builds into pure json instead of xml but ran into tons of issues with plugins and I was not sure what plugins were doing out in the wild so I stuck with xml. We run ~3000 builds per day and we can't do aggressive pruning of builds because of SOX requirements, this caused us huge performance issues like startup time of over 50 minutes ( this was a while ago, not sure if lazy loading helps here). One option was that each team gets its own jenkins server but this was maintenance nightmare. Using mongodb and not loading all builds in memory all the time brought down startup time to within couple of minutes. Out Jenkins instance is fairly snappy despite having 100's of thousands of builds, for example 'my pull requests view' is a query to mongodb on pusher field and doesn't involve traversing all the builds in memory. On Tuesday, May 20, 2014 11:36:30 AM UTC-5, Surya Gaddipati wrote: https://github.com/groupon/DotCi github usename: suryagaddipati -- 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: Is there an extension point for listening to login events
Yes. SecurityListener. Danke. Exactly what I was after. On Monday, June 9, 2014 11:44:38 AM UTC-5, Surya Gaddipati wrote: I would like to implement an housekeeping method on user when he/she logs in. Is there a extension point I can use to listen to to login events? -- 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: DotCi - plugin hosting request
On Tue, Jun 10, 2014 at 11:27 AM, Surya Gaddipati suryapraka...@gmail.com wrote: 'my pull requests view' is a query to mongodb on pusher field and doesn't involve traversing all the builds in memory. Exactly, we need to be able to able to write various specialized views (or remote API endpoints, or RSS/Atom feeds, …) which run some kind of database query without having to load actual hudson.model.Run objects into memory. No exotic use cases need to be invoked here; just showing regular build history, test result summaries, etc. demonstrate the problem. The main workaround we have been using after lazy-loading was introduced in 1.485 is to just truncate results past, say, 20 or 100 builds counting from the most recent. In a few cases we keep separate ad-hoc caches of crucial information, like PeepholePermalink does. But just fixing bugs in the specified behavior of AbstractLazyLoadRunMap is hard enough, never mind dealing with the flood of problems caused by core or plugin features unintentionally loading all builds and thus thrashing the server. -- 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: DotCi - plugin hosting request
Oh It would be nice to store build logs in mongdb too ( i had a working prototype at some point but it was buggy). This would allow scaling jenkins and deployment on platforms like Heroku, which I think would be a great win for Jenkins. On Tuesday, May 20, 2014 11:36:30 AM UTC-5, Surya Gaddipati wrote: https://github.com/groupon/DotCi github usename: suryagaddipati -- 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.
Permission denied pushing plugin to GitHub
Hello, I'm trying to push a new version of the visualworks-store-plugin to GitHub and getting a permission denied error. The repository is https://github.com/jenkinsci/visualworks-store-plugin and my GitHub user name is randycoulman. This is the first time I've tried pushing to GitHub since the repository was forked from my original. Was I given proper commit permissions? There was an older thread on the list where someone else had the same problem, and lack of commit permissions was the cause. Thanks! Randy -- Randy Coulman Email: rcoul...@gmail.com Home: http://randycoulman.com Twitter: @randycoulman GitHub: randycoulman -- 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: DotCi - plugin hosting request
On Tue, Jun 10, 2014 at 12:16 PM, Surya Gaddipati
suryapraka...@gmail.com wrote:
It would be nice to store build logs in mong[o]db too
Well I think the existing ${Run.rootDir}/log works well enough, since
you do not need to index the contents, just stream it on demand.
--
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 request change-assembly-version-plugin
Hi, I made a new plugin for .Net in Jenkins. The plugin change the version of AssemblyInfo.cs from .Net Projects. I have searched and don't find anything like this, so I made a plugin for change default assemblyversion files. I want to share my plugin with Jenkins community and like I read in the wiki this is the place to request for a github repos right? If not send me to the correct place. The name of the plugin is : change-assembly-version-plugin. and my github user: lkobus (or my mail: leonardo.ko...@gmail.com) Regards Kobus, Leonardo -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/New-Plugin-request-change-assembly-version-plugin-tp4705393.html Sent from the Jenkins dev mailing list archive at Nabble.com. -- 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: Permission denied pushing plugin to GitHub
On Tue, Jun 10, 2014 at 12:36 PM, Randy Coulman rcoul...@gmail.com wrote: I'm trying to push a new version of the visualworks-store-plugin to GitHub and getting a permission denied error. Try again; there was a GH outage. -- 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: Why doesn't copying an hpi file to JENKINS_HOME/plugins/ work?
FYI if you don't have Java installed on the machine that is wanting to make the call to add the plugin, you can do it via the SSH mechanism too. See https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+SSH Richard. On Wed, Jun 11, 2014 at 3:07 PM, Code ekkapo...@gmail.com wrote: I changed to use jenkins-cli.jar as you suggested and it works as I expected. On Monday, June 9, 2014 11:17:39 AM UTC+7, Mark Waite wrote: If you're already scripting, and you're installing a plugin from the update center, couldn't just just as easily use the command line interface? For example, I use the command: java -jar jenkins-cli.jar -s http://wheezy64b:8080/ install-plugin git git-client https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI gives more instructions on using the command line interface. Mark Waite On Sun, Jun 8, 2014 at 10:10 PM, Code ekka...@gmail.com wrote: My goal is to create a script to automatically install and setup jenkins on a linux instance (CentOs.) Jenkins document https://wiki.jenkins-ci.org/display/JENKINS/Plugins says I can manually install a plugin by copying the hpi/jpi file to plugins directory. I tried to do that by using the following commands *cd /var/lib/jenkins/plugins* *curl -O http://updates.jenkins-ci.org/latest/chucknorris.hpi http://updates.jenkins-ci.org/latest/chucknorris.hpi* then I checked and the file was there. So, I restarted the service (*service jenkins restart*.) After the website was back online, I went to JENKINS_URL/pluginManager/installed but checknorris wasn't there. I would like to know what I did wrong and how I can fix this issue. 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-de...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Thanks! Mark Waite -- 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.
