[JIRA] [git] (JENKINS-21401) NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013
SCM/JIRA link daemon commented on JENKINS-21401 NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013 Code changed in jenkins User: Nicolas De loof Path: pom.xml src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/main/java/org/jenkinsci/plugins/gitclient/Netrc.java src/test/java/org/jenkinsci/plugins/gitclient/NetrcTest.java http://jenkins-ci.org/commit/git-client-plugin/6bc60c026f019c15d96d6d2e8e9d804300640413 Log: Merge pull request #116 from olivierdagenais/JENKINS-21401_UseNTCredentialsForTfsGit JENKINS-21401 Add support for NTLM authentication, such as TFS 2013 Git servers Compare: https://github.com/jenkinsci/git-client-plugin/compare/682b654eb2a8...6bc60c026f01 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-status] (JENKINS-21920) Can't take node offline
Aleksey Maksimov created JENKINS-21920 Cant take node offline Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: slave-status Created: 22/Feb/14 9:47 AM Description: I am trying to take master node temporarily offline. After I provide the reason and click "Mark this node temporarily offline" I get NPE: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at
[JIRA] [sloccount] (JENKINS-21921) Lazy loaded report details are never released
Michal Turek created JENKINS-21921 Lazy loaded report details are never released Issue Type: Improvement Affects Versions: current Assignee: npiguet Components: sloccount Created: 22/Feb/14 10:09 AM Description: SloccountResult.lazyLoad() caches the data to a member variable. The class is loaded during Jenkins startup (all build.xml files) and never released so Java garbage collector has no chance to trash the lazy loaded details since the reference exists forever. This is kind of a memory leak. Consider to make "private SloccountReport report" member transient and to use readResolve() from Java Serialization to transform legacy data instead of calling convertLegacyData() in getStatistics(). Found during a work on Cppcheck's JENKINS-17363. Environment: Version 1.15, introduced in 1.11 Fix Versions: current Project: Jenkins Priority: Major Reporter: Michal Turek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21921) Lazy loaded report details are never released
Michal Turek assigned JENKINS-21921 to Michal Turek Lazy loaded report details are never released Change By: Michal Turek (22/Feb/14 10:09 AM) Assignee: npiguet MichalTurek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dynamicparameter] (JENKINS-18972) About class loader of Dynamic Choice Parameter (Scriptler) (Version 0.2.0)
Dominik Bartholdi updated JENKINS-18972 About class loader of Dynamic Choice Parameter (Scriptler) (Version 0.2.0) Change By: Dominik Bartholdi (22/Feb/14 10:20 AM) Assignee: DimitarPopov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dynamicparameter] (JENKINS-21071) Using Scriptlers in Dynamic Build Parameters AND Build-Steps executs the wrong Scriptler in the Build-Step
Dominik Bartholdi updated JENKINS-21071 Using Scriptlers in Dynamic Build Parameters AND Build-Steps executs the wrong Scriptler in the Build-Step Change By: Dominik Bartholdi (22/Feb/14 10:19 AM) Assignee: DominikBartholdi DimitarPopov Component/s: dynamicparameter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dynamicparameter] (JENKINS-19578) Multi-select feature at Dynamic parameter plugin
Dominik Bartholdi updated JENKINS-19578 Multi-select feature at Dynamic parameter plugin Change By: Dominik Bartholdi (22/Feb/14 10:21 AM) Assignee: LucieVotypkova DimitarPopov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21922) Remote access API
Michal Turek created JENKINS-21922 Remote access API Issue Type: Improvement Affects Versions: current Assignee: Michal Turek Components: sloccount Created: 22/Feb/14 10:23 AM Description: Implement Remote access API to SLOCCount plugin, it should be quite simple but very powerful for providing the data in json and xml formats. Export the statistics per language stored in build.xml together with total number of lines. See Cppcheck plugin CppcheckResult.getApi(), @ExportedBean and @Exported. https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API Environment: All Project: Jenkins Priority: Minor Reporter: Michal Turek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scriptler] (JENKINS-19988) Changes to script parameters in Run Script window affect permanent definitions
SCM/JIRA link daemon commented on JENKINS-19988 Changes to script parameters in Run Script window affect permanent definitions Code changed in jenkins User: imod Path: src/main/java/org/jenkinsci/plugins/scriptler/ScriptlerManagment.java src/main/java/org/jenkinsci/plugins/scriptler/config/Script.java src/main/java/org/jenkinsci/plugins/scriptler/util/ScriptHelper.java http://jenkins-ci.org/commit/scriptler-plugin/5c1d2f0af8cc88773507e6755215e75c9d9a4bdc Log: FIXED JENKINS-19988 Changes to script parameters in Run Script window affect permanent definitions Compare: https://github.com/jenkinsci/scriptler-plugin/compare/787238b685a9...5c1d2f0af8cc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scriptler] (JENKINS-19988) Changes to script parameters in Run Script window affect permanent definitions
SCM/JIRA link daemon resolved JENKINS-19988 as Fixed Changes to script parameters in Run Script window affect permanent definitions Change By: SCM/JIRA link daemon (22/Feb/14 10:23 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scriptler] (JENKINS-14964) Add ability to call script from REST API
Dominik Bartholdi resolved JENKINS-14964 as Fixed Add ability to call script from REST API integrated into 1.7 Change By: Dominik Bartholdi (22/Feb/14 10:50 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21923) Provide icons for build causes
Łukasz Jąder created JENKINS-21923 Provide icons for build causes Issue Type: Improvement Assignee: Unassigned Components: core, gui Created: 22/Feb/14 12:13 PM Description: Every cause should have icon asociated with it - this would enable three awesome visual enhancements: 1. every build could have trigger badge 2. there could be custom column which shows last build trigger cause with icon 3. every build for prject could show cause 48px icon on its run page Now ideas 1. and 2. are implemented using custom plugin Build Trigger Badge Plugin Idea 3 will greatly improve visual identification of build: a) if build was started by user Example1 there would be user profile icon. b) if build was started by timer Example2 there wuld be 'clock' icon hourglass.svg Provided icons should be in all common sizes in Jenkins (48, 32, 24, 16) Related discussion https://groups.google.com/forum/#!msg/jenkinsci-dev/Qh4XkVbu6ug/22iCrmPQ8xEJ Project: Jenkins Labels: jenkins enhancement Priority: Major Reporter: Łukasz Jąder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-21924) Run groovy script for matrix parent builds
ikedam created JENKINS-21924 Run groovy script for matrix parent builds Issue Type: Improvement Assignee: ikedam Components: groovy-postbuild Created: 22/Feb/14 12:24 PM Description: I want to run the postbuild groovy script also for matrix parent build. This can be done using MatrixAggregator. Project: Jenkins Priority: Major Reporter: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-21714) More data from REST API
Michal Turek commented on JENKINS-21714 More data from REST API Hi Robert, can you describe your use case, please? Did you consider to store the Cppcheck report to the build artifacts and access this file instead? It is a XML file suitable for parsing, it contains even more information than the plugin itself and it can be simply downloaded from a defined URL. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-17540) ConversionException reading build.xml
Michal Turek started work on JENKINS-17540 ConversionException reading build.xml Change By: Michal Turek (22/Feb/14 1:44 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-17540) ConversionException reading build.xml
Michal Turek assigned JENKINS-17540 to Michal Turek ConversionException reading build.xml Change By: Michal Turek (22/Feb/14 1:44 PM) Assignee: GregoryBoissinot MichalTurek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-17540) ConversionException reading build.xml
Michal Turek commented on JENKINS-17540 ConversionException reading build.xml I would like to fix the issue, but I am not unfortunately able to reproduce it. I tried on Debian GNU Linux, Jessie: Development run Latest plugin version compiled from sources and executed using "mvn hpi:run", Jenkins 1.447. Classic Jenkins 1.510 executed using "export JENKINS_HOME=home java -jar jenkins.war". Cppcheck plugin 1.14 installed using update center. I checked differences between 1.13 and 1.14 and they are identical in this area. Part of build.xml in build_xml_snippet.txt is correct. The issue source in stacktrace.txt is: Caused by: com.thoughtworks.xstream.mapper.CannotResolveClassException: com.thalesgroup.hudson.plugins.cppcheck.model.CppcheckWorkspaceFile This class is part of the plugin, maybe broken installation? Or it can be somehow related to class loader, class in a different package and http://stackoverflow.com/questions/10438124/xstream-cannotresolveclassexception. Questions: Anything that indicates broken plugin installation? Can you provide output of "find home -name CppcheckWorkspaceFile.class" from jenkins home directory? It should be "home/plugins/cppcheck/WEB-INF/classes/com/thalesgroup/hudson/plugins/cppcheck/model/CppcheckWorkspaceFile.class" Is it a new plugin installation or upgrade? From which version? Linux or Windows? Anything specific in configuration? Can you reproduce the issue and optionally provide full jenkins home directory? Anything other? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-17540) ConversionException reading build.xml
Michal Turek edited a comment on JENKINS-17540 ConversionException reading build.xml I would like to fix the issue, but I am not unfortunately able to reproduce it. I tried on Debian GNU Linux, Jessie: Development run Latest plugin version compiled from sources and executed using "mvn hpi:run", Jenkins 1.447. Classic Jenkins 1.510 executed using "export JENKINS_HOME=home java -jar jenkins.war". Cppcheck plugin 1.14 installed using update center. I checked differences between 1.13 and 1.14 and they are identical in this area. Part of build.xml in build_xml_snippet.txt is correct. The issue source in stacktrace.txt is: Caused by: com.thoughtworks.xstream.mapper.CannotResolveClassException: com.thalesgroup.hudson.plugins.cppcheck.model.CppcheckWorkspaceFile This class is part of the plugin, maybe broken installation? Or it can be somehow related to class loader, class in a different package and http://stackoverflow.com/questions/10438124/xstream-cannotresolveclassexception. Questions: Anything that indicates broken plugin installation? Can you provide output of "find home -name CppcheckWorkspaceFile.class" from jenkins home directory? It should be "home/plugins/cppcheck/WEB-INF/classes/com/thalesgroup/hudson/plugins/cppcheck/model/CppcheckWorkspaceFile.class" Is it a new plugin installation or upgrade? From which version? Linux or Windows? Anything specific in configuration? Can you reproduce the issue and optionally provide full jenkins home directory? Anything other? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20989) PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered
Horia Constantin commented on JENKINS-20989 PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered I am also interested in a fix for this. I've just forked the jenkins repo and I'm still trying to get my head around the project setup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [codahale-metrics-librato] (JENKINS-21894) Codahale Metrics Librato plugin doesn't work
Cyrille Le Clerc resolved JENKINS-21894 as Fixed Codahale Metrics Librato plugin doesnt work Done. Change By: Cyrille Le Clerc (22/Feb/14 4:31 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-21346) Not working with cppcheck 1.63
Michal Turek assigned JENKINS-21346 to Michal Turek Not working with cppcheck 1.63 Change By: Michal Turek (22/Feb/14 6:40 PM) Assignee: GregoryBoissinot MichalTurek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-21346) Not working with cppcheck 1.63
Michal Turek started work on JENKINS-21346 Not working with cppcheck 1.63 Change By: Michal Turek (22/Feb/14 6:40 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-21346) Not working with cppcheck 1.63
Michal Turek commented on JENKINS-21346 Not working with cppcheck 1.63 Hi, I have just compiled and tried cppcheck 1.63 with latest version of the plugin and everything works for me. The output is not identical to cppcheck 1.61, but the file format is the same. I have Debian GNU/Linux. How do you execute Cppcheck? Parsing of both new and old XML format produce no exception. ./cppcheck --enable=all --inconclusive --xml --xml-version=2 DIRECTORY 2 cppcheck.xml ./cppcheck --enable=all --inconclusive --xml DIRECTORY 2 cppcheck.xml What version of plugin do you use? What platform (Linux/Windows)? Can you attach the report file generated by Cppcheck that causes the issue? Thanks, Michal This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-17450) warning and performance not counted
Michal Turek commented on JENKINS-17450 warning and performance not counted Latest version of the plugin adds "Warning" and "Performance" issues to totals and also displays them on the graph. The described behavior may be caused by unwanted advanced configuration on configuration page. Can you confirm that? But the graph doesn't consider "No Category" and whole plugin doesn't work with "portability" severity. --errorlist Print a list of all possible error messages in XML format. ./cppcheck --xml --xml-version=2 --errorlist | grep severity | sed 's/.*severity="//' | sed 's/" msg=.*//' | sort -u error information performance portability style warning This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-17450) warning and performance not counted
Michal Turek assigned JENKINS-17450 to Michal Turek warning and performance not counted Change By: Michal Turek (22/Feb/14 7:11 PM) Assignee: GregoryBoissinot MichalTurek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-17450) warning and performance not counted
Michal Turek started work on JENKINS-17450 warning and performance not counted Change By: Michal Turek (22/Feb/14 7:11 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [svn-tag] (JENKINS-21925) jenkins svn tagging plugin 1.16 is broken afte upgrade to Jenkins 1.550
gloppyuser created JENKINS-21925 jenkins svn tagging plugin 1.16 is broken afte upgrade to Jenkins 1.550 Issue Type: Bug Assignee: k2nakamura Components: svn-tag Created: 22/Feb/14 9:45 PM Description: After upgrading to Jenkins 1.550, Jenkins SVN tagging plugin is failing in copy step. I suspect that it might be related to how SCM credentials are now stored. Subversion copy failed. svn: E200015: OPTIONS failed Build step 'Perform Subversion tagging on successful build' marked build as failure Due Date: 28/Feb/14 12:00 AM Environment: Jenkins 1.550 Jenkins SVN tagging plugin 1.16 Project: Jenkins Priority: Major Reporter: gloppyuser This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [svn-tag] (JENKINS-21925) jenkins svn tagging plugin 1.16 is broken after upgrade to Jenkins 1.550
gloppyuser updated JENKINS-21925 jenkins svn tagging plugin 1.16 is broken after upgrade to Jenkins 1.550 Change By: gloppyuser (22/Feb/14 9:45 PM) Summary: jenkinssvntaggingplugin1.16isbroken afte after upgradetoJenkins1.550 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21168) Git core.symlinks option not correctly auto-detected on Windows
Sebastian Schuberth commented on JENKINS-21168 Git core.symlinks option not correctly auto-detected on Windows Thanks for your explanations about the JGit implementation, I got it now. I did some more tests and realized the issue is somehow related to the custom version of Git for Windows that I'm using (mingwGitDevEnv, see 1). I can confirm that everything is fine if I clone the sandbox repository at 2 (which contains several Linux links) with msysgit 1.8.4 3. But if I use mingwGitDevEnv for cloning it fails like at 4. However, here comes the funny part: If I just create a build step where I clone the sandbox repository using mingwGitDevEnv manually, i.e. by directly invoking the mingwGitDevEnv Git executable instead of the Jenkins Git plugin doing it, it works again (see 5). So there must be something that the plugin is doing different than I when calling git.exe for cloning. Any idea what that could be? 1 https://github.com/sschuberth/mingwGitDevEnv 2 https://github.com/sschuberth/sandbox 3 http://mingwgitdevenv.cloudapp.net/view/Playground/job/sandbox/7/console 4 http://mingwgitdevenv.cloudapp.net/view/Playground/job/sandbox/8/console 5 http://mingwgitdevenv.cloudapp.net/view/Playground/job/sandbox/9/console This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue
Oleg Nenashev updated JENKINS-21044 Throttle Concurrent Builds blocking Jenkins queue Added the local build with a probable fix. https://github.com/jenkinsci/throttle-concurrent-builds-plugin/pull/13 I've tried about 10 restarts with big queues, but the issue has not been reproduced. BTW, it would be great to have a light-weight unit test. Change By: Oleg Nenashev (22/Feb/14 10:13 PM) Attachment: throttle-concurrents.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Alex Earl commented on JENKINS-21861 option to include attachment with console.txt from failed slaves I'm trying to figure out what logs you are looking to have included...when I attach the normal build log and that build was run on a slave, I get the full console output just like I do when run on master. I already fixed the issue with the file being named just "log" it will now be named "build.log" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-timeout] (JENKINS-21926) Write regression tests for build-timeout plugin
ikedam created JENKINS-21926 Write regression tests for build-timeout plugin Issue Type: Task Assignee: ikedam Components: build-timeout Created: 23/Feb/14 1:37 AM Description: There are too few tests for build-timeout plugin. This makes it difficult to refactor. Project: Jenkins Priority: Major Reporter: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21041) Impossible to keeps sending mails to people who broke the build
Alex Earl commented on JENKINS-21041 Impossible to keeps sending mails to people who broke the build Sorry, I meant "1st Failure" to developers and "Still Failing" to culprits (you have to select developers as well to make it work...that is until 2.38). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Alex Earl commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Could this have anything to do with this code? https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractBuild.java#L728 It's using String's instead of User's This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Alex Earl commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification I think this code in Mailer could be an issue as well. https://github.com/jenkinsci/mailer-plugin/blob/41de8d6ada29693073b2c122a367be112ae55663/src/main/java/hudson/tasks/MailAddressResolver.java#L137 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
cowwoc
updated JENKINS-16332
Leading and trailing underscores are added to commiters email address, unable to send build notification
Guys,
I've managed to produce a minimal testcase for this bug.
Extract testcase.zip into $JENKINS_HOME/jobs
Run the job
You should get this output:
Started by user Gili Tzabari
[EnvInject] - Loading node environment variables.
Building remotely on MacOS X 10.8 in workspace /Users/builds/.jenkins/workspace/Test
[Test] $ /usr/local/bin/hg showconfig paths.default
ERROR: Workspace reports paths.default as https://bbs.darktech.org/code/test/
which looks different than https://cow...@bitbucket.org/cowwoc/test
so falling back to fresh clone rather than incremental update
$ /usr/local/bin/hg clone --rev default --noupdate https://cow...@bitbucket.org/cowwoc/test /Users/builds/.jenkins/workspace/Test
adding changesets
adding manifests
adding file changes
added 19 changesets with 19 changes to 2 files
[Test] $ /usr/local/bin/hg update --rev default
2 files updated, 0 files merged, 0 files removed, 0 files unresolved
[Test] $ /usr/local/bin/hg log --rev . --template {node}
[Test] $ /usr/local/bin/hg log --rev . --template {rev}
[Test] $ /usr/local/bin/hg log --rev 6ddb7626f1d05f3e67a4c92fa255ba32a5406020
changeset: 18:6ddb7626f1d0
tag: tip
user:Getcho Getchev getcho.getc...@gmail.com
date:Fri Feb 21 23:40:41 2014 +0200
summary: added line 10
[Test] $ /usr/local/bin/hg log --template "changeset node='{node}' author='{author|xmlescape}' rev='{rev}' date='{date}'msg{desc|xmlescape}/msgadded{file_adds|stringify|xmlescape}/addeddeleted{file_dels|stringify|xmlescape}/deletedfiles{files|stringify|xmlescape}/filesparents{parents}/parents/changeset\n" --rev default:0 --follow --prune 6ddb7626f1d05f3e67a4c92fa255ba32a5406020 --encoding UTF-8 --encodingmode replace
[Test] $ /bin/sh -xe /var/folders/ht/zq3sdm6s55j4cv6gvjtkc8vmgp/T/hudson4438504154854395225.sh
+ ./test.sh
/var/folders/ht/zq3sdm6s55j4cv6gvjtkc8vmgp/T/hudson4438504154854395225.sh: line 2: ./test.sh: No such file or directory
Build step 'Execute shell' marked build as failure
Invalid address: Getcho Getchev _getcho.getchev@gmail.com_
Invalid address: Gili Tzabari _gili.tzabari@gmail.com_
An attempt to send an e-mail to empty list of recipients, ignored.
Finished: FAILURE
Change By:
cowwoc
(23/Feb/14 6:05 AM)
Attachment:
testcase.zip
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-19433) ownership plugin does not find owner's email - although it's defined in his/her profile
Oleg Nenashev commented on JENKINS-19433 ownership plugin does not find owners email - although its defined in his/her profile The main risk: authentication plugins may configure the Mailer's property on their own (e.g. ActiveDirectory), so the field may differ from a user's expectations. If a user relies on e-mail suffix, in most cases he don't need to care about a garbage in the Mailer's user property BTW, the approach you propose is a correct way even if it causes some regressions. Hence I propose to just put a notification in change history of the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman commented on JENKINS-21861 option to include attachment with console.txt from failed slaves Thank you for looking into this! On your system you probably run job on jenkins "master" machine, hence its console contains all job output. Jenkins can be configured to run jobs on "slaves" nodes only (master is not in use), so master serves for launching jobs only but real work is done by slaves and only slaves console contain job`s output. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman updated JENKINS-21861 option to include attachment with console.txt from failed slaves multi-slave jenkins config, no master used. Change By: Mike Dubman (23/Feb/14 6:24 AM) Attachment: multi-slave-config-Capture.JPG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-21740) Columns with value of a variable from script
dor cohen commented on JENKINS-21740 Columns with value of a variable from script Hi Fred, There could be anything in it, either a string or number (integer/float). The value would be decided by the script. Is it possible to make the value to stay after that the job has been completed? The value that is displayed should be taken from the last job being executed. Thank you. Best regards, Dor. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
