Hosting request for logentries plugin
Hi, Would it be possible to fork https://github.com/logentries/logentries-jenkins into the jenkinsci GitHub organization? This is a plugin for forwarding console output to logentries.com. I would like commit access to this repository. My GitHub handle is stbutler11. Thanks, Stuart Butler -- 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/groups/opt_out.
Re: Jenkins CLI: ssh key and ssh agent
No relationship at all. My patch is for the Jenkins CLI jar that you can download on your machine to interact with Jenkins through command line. You can authenticate using an ssh key pair, but you have to enter your private key password at each command. Note anymore with my patch which interact with a potentially local ssh agent. Cheers, Reynald On Saturday, August 3, 2013 at 23:08 , Stephen Connolly wrote: How does this relate to the ssh-agent plugin? On Saturday, 3 August 2013, Reynald Borer wrote: I've made a first patch that works fine with OpenSSH agent. I'm going to try to test it with Pageant on Windows, as it seems to be supported. I'll then make a pull request if my tests are successful. If you want to have a look at my change in the mean time: https://github.com/rborer/jenkins/commit/281dd560fdcb6a526deedcb83c9e83e1eff3947b BTW, I had to use jsch-agent-proxy (https://github.com/ymnk/jsch-agent-proxy) as a new dependency as it provides communication with SSH agents (ssh2 library build 217 only add interfaces for agent authentication…). I hope it's fine to add a new dependency, the jar size increase from 2.5 to 3.9 mb. Cheers, Reynald On Friday, August 2, 2013 at 18:36 , Reynald Borer wrote: Great, thanks for the merge, I guess you've done the hardest part with subversion. I'll see for its inclusion in the CLI. Cheers, Reynald @+, Reynald On Friday, August 2, 2013 at 10:48 , nicolas de loof wrote: released org.jenkins-ci:trilead-ssh2:build217-jenkins-2 2013/8/2 nicolas de loof nicolas.del...@gmail.com Sounds good to me I'm looking into updating svnkit fork to 1.7.10 and need build217 as dependency as well But searching for source code to merge, I notice http://www.ganymed.ethz.ch/ssh2/ only provide outdated build 210, it has a link to http://www.cleondris.ch/ where I only can find build 250 : http://www.cleondris.ch/opensource/ssh2/, but this one has been repackaged as ch.ethz.ssh2 svnkit is using a custom version http://svn.svnkit.com/repos/3rdparty/com.trilead.ssh2/tags/1.0.0-build217/ that uses gradle so I guess I have to use the later, but not trivial to merge with build system changed Le mardi 18 juin 2013 13:13:51 UTC+2, Reynald Borer a écrit : Hi, I'm reposting this to the dev mailing-list which is probably a more appropriate list. Let me know what you think of my proposal. Regards, Reynald On Fri, Jun 14, 2013 at 5:50 PM, Reynald Borer reynal...@gmail.com wrote: Hi, I'm probably not the only one interested in having Jenkins CLI being able to use an existing ssh agent instead of prompting for the key passphrase at every action. I've had a quick look at the code and haven't found anything about that. Luckily, it seems that the trilead ssh2 library released build 217 with ssh agent support a few days ago (according to http://svn.svnkit.com/repos/3rdparty/com.trilead.ssh2/trunk/HISTORY.txt). So I'm wondering if it would be possible to merge this new feature in the fork of this library for Jenkins on https://github.com/jenkinsci/trilead-ssh2. I'm then willing to help in implementing this feature in the CLI. Best regards, Reynald -- 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/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/groups/opt_out. -- 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/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
Re: Encoding for generated sources in jenkins-core
As a workaround I replaced the unicode quotes by regular quotes in Messages.properties and Messages_ja.properties (patch for core is attached). On Sat, Aug 3, 2013 at 11:52 AM, Rusi Filipov rfili...@gmail.com wrote: Thank you for the insight Jesse. Please verify whether the file is actually valid in UTF-8 encoding, or if not, what encoding it is in. And what operating system do you use? I am wondering if there is an issue with the platform default encoding. My laptop has the following Environment: - Windows 7, English - JDK 1.7.0_25 - Maven 3.0.5 - Git Bash 1.8.3 - Intellij IDEA 12.1.4 jrunscript -e 'println(java.lang.System.getProperty(file.encoding))' This outputs Cp1252. I have been digging deeper into this. When I compile the project in the Terminal I see this output: fidel@ARULCO /d/ccd/workshop/jenkins/core (cleanup) $ mvn clean compile ... [INFO] --- build-helper-maven-plugin:1.7:add-source (add-source) @ jenkins-core --- [INFO] Source directory: d:\ccd\workshop\jenkins\core\target\generated-sources\antlr added. [INFO] Source directory: d:\ccd\workshop\jenkins\core\target\generated-sources\localizer added. ... [INFO] --- maven-localizer-plugin:1.14:generate (default) @ jenkins-core --- ... [INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ jenkins-core --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 916 source files to d:\ccd\workshop\jenkins\core\target\classes [WARNING] /d:/ccd/workshop/jenkins/core/target/generated-sources/taglib-interface/lib/LayoutTagLib.java:[730,36] unmappable character for encoding UTF-8 ... [WARNING] /d:/ccd/workshop/jenkins/core/target/generated-sources/localizer/hudson/scheduler/Messages.java:[33,36] unmappable character for encoding UTF-8 ... The compiler warnings about unmappable characters in LayoutTagLib.java and in Messages.java indicate an encoding issue. When I open these two files in Notepad++ he detects them as UTF-8 without BOM. But when I try to generate the sources in the Terminal (mvn clean generate-sources) and launch a subsequent build of the module inside Intellij (Make Project) it results in compile errors: D:\ccd\workshop\jenkins\core\target\generated-sources\localizer\hudson\scheduler\Messages.java error: unmappable character for encoding UTF-8 @Kohsuke maybe we could retire this questionable Maven plugin and just use a JSR 269 processor? That would pick up the right encoding for Java sources without hassle, and would have some ancillary benefits; e.g. 269-aware IDEs may immediately offer code completion on Messages.java methods as soon as you save changes to Messages.properties, without requiring a Maven build. It would be slightly tricky to enumerate all the available Messages.properties files, since JSR 269 does not offer this capability, but you could work around that by checking explicitly for Messages.properties resource in each package for which a root element was encountered in the round environment. This seems a questionable plugin indeed. I could not find this plugin's home page and mvn localizer:help produced an error message saying he does not know the 'help' goal, which regular Maven plugins should support. Furthermore, I could not trigger its execution in Intellij during the 'generate-sources' phase, even when I set this explicitly in the plugin's configuration in the POM. So this basically makes Rebuild Project inside Intellij impossible and forces the developer to use both Terminal and IDE for this basic task. But even with a Terminal, the encoding issues from above emerge so I cannot compile the module. Not as good as it should be, but I will try to find a workaround for this... -- 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/groups/opt_out. messages_encoding.patch Description: Binary data
How to compile the Groovy files in Intellij?
When I try to build the core module in Intellij I get two kinds of
compilation errors:
D:\cache\idea\system\compiler\core.e95d7d7c\.generated\groovyStubs\jenkins-core\production\jenkins\widgets\BuildQueueWidget\index.java
Error(1, 9) The package jenkins.widgets.BuildQueueWidget collides with a
type
This stub for the Groovy script is automatically generated by Intellij for
Java/Groovy cross-compilation. The generated file looks like this:
package jenkins.widgets.BuildQueueWidget;
public class index extends groovy.lang.Script {
public static void main(java.lang.String[] args) {
return ;
}
public java.lang.Object run() {
return null;
}
}
There is indeed a class jenkins.widgets.BuildQueueWidget with the same name
as the namespace.
Here Intellij offers me to exclude this Groovy file from stub generation.
Should I do it?
There is another type of error that I also receive:
D:\cache\idea\system\compiler\core.e95d7d7c\.generated\groovyStubs\jenkins-core\production\jenkins\util\groovy\AbstractGroovyViewModule.java
Error (38, 8) FormTagLib cannot be resolved to a type
All of this is very confusing. This is the third day I am trying to get
started working with the sources and it adds some frustration, given that I
am experienced with maven and Intellij. Is there a description about how
exactly one must configure Intellij in order build the 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/groups/opt_out.
Re: Release plugin repository commit access request
Done. Welcome aboard! Ulli Am 03.08.2013 um 23:00 schrieb Bulat Shakirzyanov mallluh...@gmail.com: Hi Jenkins devs! I recently submitted a pull request to release-plugin repository that adds support of Matrix Jobs. https://github.com/jenkinsci/release-plugin/pull/5 Given there hasn't been any response to it in 10 days, I would like to volunteer to merge that change, prepare a new release and go over other outstanding pull requests in that repository. My github username is avalanche123 Cheers, -- Bulat Shakirzyanov | Software Alchemist a: about.me/avalanche123 e: mallluh...@gmail.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/groups/opt_out. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: New Jenkins plugin:Allow the user to choose matrix combinations
Feel free to use it. Read the wiki for instructions if you still got any questions I can help you. Good Luck On Saturday, August 3, 2013 3:54:14 PM UTC+3, de...@ikedam.jp wrote: I'm interested in this plugin. What is the current status of forking ? On Sunday, July 28, 2013 6:28:45 PM UTC+9, Omer Shem-Tov wrote: Hi, I developed a new plugin for jenkins: The plugin is inspired by Matrix Reloded Plugin, but it can be used from first build. It basically add a new type of parameter called Matrix Combinations Parameter to a Matrix project and once you configure your project to use it and click the build now you'll get a table of check boxes with the different permutations of the axes. The user click the build now and the user choice is transferred to the combinations filter of the project so only the chosen combinations will run. The plugin was tested and should be inserted in our production jenkins and used on a daily basis. You can see the code in my git hub https://github.com/omer727/Matrix-Combinations-Jenkins-Plugin Pay attention: this is the first plugin I developed for Jenkins, but I hope you'll like it. I can add a wiki page if there will be demand Thanks, Omer -- 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/groups/opt_out.
Re: Encoding for generated sources in jenkins-core
Hi, FWIW, .properties files are by definition encoded (and parsed as) in iso-8859-1 (see http://docs.oracle.com/javase/6/docs/api/java/util/Properties.html). The platform encoding shouldn't have any impact, if so then this might be a bug somewhere. Cheers Le 4 août 2013 12:43, Rusi Filipov rfili...@gmail.com a écrit : As a workaround I replaced the unicode quotes by regular quotes in Messages.properties and Messages_ja.properties (patch for core is attached). On Sat, Aug 3, 2013 at 11:52 AM, Rusi Filipov rfili...@gmail.com wrote: Thank you for the insight Jesse. Please verify whether the file is actually valid in UTF-8 encoding, or if not, what encoding it is in. And what operating system do you use? I am wondering if there is an issue with the platform default encoding. My laptop has the following Environment: - Windows 7, English - JDK 1.7.0_25 - Maven 3.0.5 - Git Bash 1.8.3 - Intellij IDEA 12.1.4 jrunscript -e 'println(java.lang.System.getProperty(file.encoding))' This outputs Cp1252. I have been digging deeper into this. When I compile the project in the Terminal I see this output: fidel@ARULCO /d/ccd/workshop/jenkins/core (cleanup) $ mvn clean compile ... [INFO] --- build-helper-maven-plugin:1.7:add-source (add-source) @ jenkins-core --- [INFO] Source directory: d:\ccd\workshop\jenkins\core\target\generated-sources\antlr added. [INFO] Source directory: d:\ccd\workshop\jenkins\core\target\generated-sources\localizer added. ... [INFO] --- maven-localizer-plugin:1.14:generate (default) @ jenkins-core --- ... [INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ jenkins-core --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 916 source files to d:\ccd\workshop\jenkins\core\target\classes [WARNING] /d:/ccd/workshop/jenkins/core/target/generated-sources/taglib-interface/lib/LayoutTagLib.java:[730,36] unmappable character for encoding UTF-8 ... [WARNING] /d:/ccd/workshop/jenkins/core/target/generated-sources/localizer/hudson/scheduler/Messages.java:[33,36] unmappable character for encoding UTF-8 ... The compiler warnings about unmappable characters in LayoutTagLib.java and in Messages.java indicate an encoding issue. When I open these two files in Notepad++ he detects them as UTF-8 without BOM. But when I try to generate the sources in the Terminal (mvn clean generate-sources) and launch a subsequent build of the module inside Intellij (Make Project) it results in compile errors: D:\ccd\workshop\jenkins\core\target\generated-sources\localizer\hudson\scheduler\Messages.java error: unmappable character for encoding UTF-8 @Kohsuke maybe we could retire this questionable Maven plugin and just use a JSR 269 processor? That would pick up the right encoding for Java sources without hassle, and would have some ancillary benefits; e.g. 269-aware IDEs may immediately offer code completion on Messages.java methods as soon as you save changes to Messages.properties, without requiring a Maven build. It would be slightly tricky to enumerate all the available Messages.properties files, since JSR 269 does not offer this capability, but you could work around that by checking explicitly for Messages.properties resource in each package for which a root element was encountered in the round environment. This seems a questionable plugin indeed. I could not find this plugin's home page and mvn localizer:help produced an error message saying he does not know the 'help' goal, which regular Maven plugins should support. Furthermore, I could not trigger its execution in Intellij during the 'generate-sources' phase, even when I set this explicitly in the plugin's configuration in the POM. So this basically makes Rebuild Project inside Intellij impossible and forces the developer to use both Terminal and IDE for this basic task. But even with a Terminal, the encoding issues from above emerge so I cannot compile the module. Not as good as it should be, but I will try to find a workaround for this... -- 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/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/groups/opt_out.
Re: Release plugin repository commit access request
Thank you sir! Bulat On Aug 4, 2013, at 6:10, Ulli Hafner ullrich.haf...@gmail.com wrote: Done. Welcome aboard! Ulli Am 03.08.2013 um 23:00 schrieb Bulat Shakirzyanov mallluh...@gmail.com: Hi Jenkins devs! I recently submitted a pull request to release-plugin repository that adds support of Matrix Jobs. https://github.com/jenkinsci/release-plugin/pull/5 Given there hasn't been any response to it in 10 days, I would like to volunteer to merge that change, prepare a new release and go over other outstanding pull requests in that repository. My github username is avalanche123 Cheers, -- *Bulat Shakirzyanov* | Software Alchemist *a: *about.me/avalanche123 *e:* mallluh...@gmail.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/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/groups/opt_out.
Re: Problem with exclusion list in Email-ext plugin, v2.30.2
@slide: that would be great if fixed in the next release. Thanks! On Saturday, August 3, 2013 12:14:23 AM UTC-4, slide wrote: If I remember correctly there is an issue with the feature, I think I fixed it for the next release. I can't seem to find the information right now, but my internet connection is currently horrible. slide On Fri, Aug 2, 2013 at 11:06 AM, Ken kennet...@gmail.com javascript:wrote: Version 2.29 of the Email-ext plugin added a global user exclusion list (issue #17503) -- very useful! Even using this list though, I'm still getting email sent to a build pc that shouldn't receive email. I've tried both forms of bui...@domain.comjavascript: and buildpc in the Excluded Committers area but no luck. Is there additional logging I could turn on for this plugin or for Jenkins that might help figure out why the exclusion list isn't working? 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 javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- Website: http://earl-of-code.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/groups/opt_out.
Release not showing up + repo questions
Hello all. I'm new to releasing on jenkins-ci.org so this may be a newbie mistake. I've successfully ran 'mvn release:prepare release:perform', but the plugin does not appear in http://repo.jenkins-ci.org/releases/org/jvnet/hudson/plugins/ or http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ However, it is showing up here: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/owasp/dependency-check/dependency-check-jenkins-plugin/1.0.1/ Repo: https://github.com/jeremylong/dependency-check-jenkins Forked: https://github.com/jenkinsci/dependency-check-plugin Github ID: stevespringett What am I doing wrong? Also, what is the relationship between the original repo (which I commit to), the forked repo (not exactly sure why it's there), and the release that I upload (built from the original repo)? I've made changes to the original repo, but the changes are not showing up in forked repo. So I guess I need a pull request? What purpose does this actually serve if the plugin I'm building and uploading is being built from the original repo? Thanks in advance --Steve -- 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/groups/opt_out.
Are there any workaround for bug [JENKINS-18080], it's about Connection refused while using JNLP (windows7 as slave)
Hi guys, Jenkins ver. 1.509.2 My jenkins was deployed on linux, while I add one node(named onePc) and want to use JNLP to connect to the master. Firstly, I've done this basic configuration 1) set the Jenkins URL on 'configuration system' page as 'http://192.168.1.22' 2) set 'Enable security' and use random TCP port for JNLP slave agents Then, on the slave pc (win7), run javaws http://192.168.1.22/computer/onePc/slave-agent.jnlp I can see the java6 was running but after 3 times trying, pop up a dialog as bug [ https://issues.jenkins-ci.org/browse/JENKINS-18080JENKINS-18080]https://issues.jenkins-ci.org/browse/JENKINS-18080 Are there any workaround for this issue ? -- 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/groups/opt_out.
