[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs
Eyal Edri created JENKINS-12972: --- Summary: Add option to run 'git bisect' to find which commit added new bugs Key: JENKINS-12972 URL: https://issues.jenkins-ci.org/browse/JENKINS-12972 Project: Jenkins Issue Type: New Feature Components: findbugs Reporter: Eyal Edri Assignee: Ulli Hafner Priority: Minor Today, when you run find-bugs plug-in triggered by a git commit, you can't know exactly which commit added those bugs. It becomes especially difficult to know when a high volume of commits is pushed at once. find-bugs plug-in could have a new option to tick in the 'advanced section', which will do a 'git bisect' on the git commits that caused a new bug and display/email to commiter who did it. that would simply and automate the process of finding who wrote the bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12741) Improve support for multi-config Jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-12741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159808#comment-159808 ] SCM/JIRA link daemon commented on JENKINS-12741: Code changed in jenkins User: Ross Rowe Path: pom.xml src/main/java/hudson/plugins/sauce_ondemand/BrowserAxis.java src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandBuildWrapper.java src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandReportFactory.java src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandReportPublisher.java http://jenkins-ci.org/commit/sauce-ondemand-plugin/8333bba01eb33d412228d074d95afcea5e15b5cd Log: JENKINS-12741 Made Sauce Connect closing logic work when invoked by a slave. Added -Darguments to BrowserAxis. Extract Sauce Session Id from build log if not present in test output Improve support for multi-config Jobs - Key: JENKINS-12741 URL: https://issues.jenkins-ci.org/browse/JENKINS-12741 Project: Jenkins Issue Type: Bug Components: sauce-ondemand Reporter: Ross Rowe Assignee: Ross Rowe The current Sauce Connect logic ensures that only a single Sauce Connect instance is active per Job. For multi-config Jobs, this means that each Job waits until previous Jobs have finished. The plugin should be updated such that a single Sauce Connect instance is active for all multi-config Job instances. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9679) NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
[ https://issues.jenkins-ci.org/browse/JENKINS-9679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hiroyoshi kasai updated JENKINS-9679: - Environment: Jenkins 1.411 / MacOS X / JDK 1.6.0_24 Jenkins 1.412 / Master: Ubuntu 10.04, / Slave: Windows Server 2008 x64, JDK 1.6.0_20 Jenkins 1.424.2 / Master: CentOS 5.5, / Slave: Windows Server 2008 R2 x64, JDK 1.6.0_21 was: Jenkins 1.411 / MacOS X / JDK 1.6.0_24 Jenkins 1.412 / Master: Ubuntu 10.04, / Slave: Windows Server 2008 x64, JDK 1.6.0_20 NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option --- Key: JENKINS-9679 URL: https://issues.jenkins-ci.org/browse/JENKINS-9679 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: Jenkins 1.411 / MacOS X / JDK 1.6.0_24 Jenkins 1.412 / Master: Ubuntu 10.04, / Slave: Windows Server 2008 x64, JDK 1.6.0_20 Jenkins 1.424.2 / Master: CentOS 5.5, / Slave: Windows Server 2008 R2 x64, JDK 1.6.0_21 Reporter: Olivier Mansion When launching a headless slave, a NoClassDefFoundError on org/apache/commons/codec/binary/Base64 is raised when specifying the -jnlpCredential option: $ java -jar slave.jar -jnlpUrl url -jnlpCredentials user:password Exception in thread main java.lang.NoClassDefFoundError: org/apache/commons/codec/binary/Base64 at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:221) at hudson.remoting.Launcher.run(Launcher.java:192) at hudson.remoting.Launcher.main(Launcher.java:168) Caused by: java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64 at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) ... 3 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12055) NPE: Failed to record SCM polling. Using Jenkins 1.424.1 (LTS).
[ https://issues.jenkins-ci.org/browse/JENKINS-12055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Per Christian Moen resolved JENKINS-12055. -- Resolution: Fixed This has been fixed in 1.424.3. Looks like the fix was committed to issue JENKINS-11592. NPE: Failed to record SCM polling. Using Jenkins 1.424.1 (LTS). --- Key: JENKINS-12055 URL: https://issues.jenkins-ci.org/browse/JENKINS-12055 Project: Jenkins Issue Type: Bug Components: gerrit-trigger, maven, subversion Reporter: Per Christian Moen Priority: Blocker Stack trace from Jenkins: Dec 9, 2011 5:03:40 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling java.lang.NullPointerException at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:172) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1095) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:355) at hudson.scm.SCM.poll(SCM.java:372) at hudson.model.AbstractProject.poll(AbstractProject.java:1324) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12928) Job name Enforcer
[ https://issues.jenkins-ci.org/browse/JENKINS-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159810#comment-159810 ] domi commented on JENKINS-12928: This is now implemented: https://github.com/jenkinsci/jenkins/commit/a2d9bac03da99d739ecf7ce0be9ba793b93d2c88 I added a new ExtensionPoint: 'jenkins.model.ProjectNamingStrategy' and two implementations: - Default (no restriction, same as today) - Pattern (takes a regular expression to restrict the possible names) ...will be in 1.454 Job name Enforcer - Key: JENKINS-12928 URL: https://issues.jenkins-ci.org/browse/JENKINS-12928 Project: Jenkins Issue Type: New Feature Components: core Reporter: Daniel Petisme Fix For: current The aim of this feature is to be able to add constraints on job's name. For instance a simple use case is to be sure the jobs created follow a naming convention. This feature comes from the following thread in the jenkins-developer ML. [https://groups.google.com/forum/?hl=fr#!topic/jenkinsci-dev/rsxUpaNAe18] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12928) Job name Enforcer
[ https://issues.jenkins-ci.org/browse/JENKINS-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] domi resolved JENKINS-12928. Assignee: domi Resolution: Fixed Job name Enforcer - Key: JENKINS-12928 URL: https://issues.jenkins-ci.org/browse/JENKINS-12928 Project: Jenkins Issue Type: New Feature Components: core Reporter: Daniel Petisme Assignee: domi Fix For: current The aim of this feature is to be able to add constraints on job's name. For instance a simple use case is to be sure the jobs created follow a naming convention. This feature comes from the following thread in the jenkins-developer ML. [https://groups.google.com/forum/?hl=fr#!topic/jenkinsci-dev/rsxUpaNAe18] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job
[ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159811#comment-159811 ] gbois commented on JENKINS-12427: - I'm afraid I can't reproduce your problem. It's OK in my environment. Could you try in your side to isolate the problem with a simple case/job and with a cron to 1 minute? BuildResultTrigger Plug-in not triggering job -- Key: JENKINS-12427 URL: https://issues.jenkins-ci.org/browse/JENKINS-12427 Project: Jenkins Issue Type: Bug Components: buildresult-trigger, buildresulttrigger Affects Versions: current Environment: Linux, 2.6.26-amd64 debian_version 5.0.6 Jenkins BuildResultTrigger Plug-in 0.4 Jenkins ver. 1.440 Reporter: S P Assignee: gbois Attachments: TEST-Trigger.config.xml, TEST-TRY.config-2.xml, TEST-TRY.config.xml Jenkins with the buildResultTrigger plugin is unable to trigger a job Two jobs are setup, 1. TEST-TRIGGER is a basic job that always passes (from jenkins log) INFO | jvm 2| 2012/01/17 10:47:31 | 17/01/2012 10:47:31 AM hudson.model.Run run INFO | jvm 2| 2012/01/17 10:47:31 | INFO: TEST-Trigger #7 main build action completed: SUCCESS 2. TEST-TRY is a basic job configured to Monitor build results of TEST-Trigger. This job is able to run with success when trigger manually (from jenkins log) INFO | jvm 2| 2012/01/17 10:48:51 | 17/01/2012 10:48:51 AM hudson.model.Run run INFO | jvm 2| 2012/01/17 10:48:51 | INFO: TEST-TRY #2 main build action completed: SUCCESS However, a success result from TEST-TRIGGER does not fire the TEST-TRY job. Both jobs configurations are attached -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12973) Doxygen Plugin shows 404 error. Points to {OUTPUT_DIRECTORY} instead of {OUTPUT_DIRECTORY}/html
Roland Schulz created JENKINS-12973:
---
Summary: Doxygen Plugin shows 404 error. Points to
{OUTPUT_DIRECTORY} instead of {OUTPUT_DIRECTORY}/html
Key: JENKINS-12973
URL: https://issues.jenkins-ci.org/browse/JENKINS-12973
Project: Jenkins
Issue Type: Bug
Components: doxygen
Affects Versions: current
Reporter: Roland Schulz
Assignee: gbois
The doxygen plugin parses the doxyfile correctly and also publishes correctly.
But when one tries to view the doxygen Jenkins reports a 404 error. One has to
append /html to the URL to make it work. The plugin detected the output
directory correctly from the OUTPUT_DIRECTOR option but didn't append the
/html. My Doxyfile has HTML_OUTPUT not set and thus doxygen takes the default
html.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12974) Use hard links if possible, for local copies
Gergely Nagy created JENKINS-12974: -- Summary: Use hard links if possible, for local copies Key: JENKINS-12974 URL: https://issues.jenkins-ci.org/browse/JENKINS-12974 Project: Jenkins Issue Type: Improvement Components: copyartifact Environment: *nix Reporter: Gergely Nagy Assignee: Alan Harder Priority: Minor Please consider using hard links on systems which allow it, for transfers on local filesystems. My motivation: save space. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12974) Use hard links if possible, for local copies
[ https://issues.jenkins-ci.org/browse/JENKINS-12974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gergely Nagy updated JENKINS-12974: --- Description: Please consider using hard links on systems which allow it, for transfers on local filesystems. This behaviour could be configurable. My motivation is to save space. Thanks for listening, let me know what you think.. and if I could help. was: Please consider using hard links on systems which allow it, for transfers on local filesystems. My motivation: save space. Use hard links if possible, for local copies Key: JENKINS-12974 URL: https://issues.jenkins-ci.org/browse/JENKINS-12974 Project: Jenkins Issue Type: Improvement Components: copyartifact Environment: *nix Reporter: Gergely Nagy Assignee: Alan Harder Priority: Minor Please consider using hard links on systems which allow it, for transfers on local filesystems. This behaviour could be configurable. My motivation is to save space. Thanks for listening, let me know what you think.. and if I could help. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-1152) Mail server rejecting emails from hudson
[ https://issues.jenkins-ci.org/browse/JENKINS-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159812#comment-159812 ] evernat commented on JENKINS-1152: -- it seems that Jenkins still uses javamail 1.4 https://github.com/jenkinsci/jenkins/blob/master/core/pom.xml Mail server rejecting emails from hudson Key: JENKINS-1152 URL: https://issues.jenkins-ci.org/browse/JENKINS-1152 Project: Jenkins Issue Type: Bug Components: mail Affects Versions: current Environment: Platform: All, OS: All Reporter: typerlc When sending emails from hudson, my mail server (postfix, but I'm sure others will behave similarly too) rejects the message because the smtp HELO message isn't being sent. This is because the system property mail.smtp.localhost hasn't been set before sending the email. This is described in the javadocs for com.sun.mail.smtp. See also: http://forum.java.sun.com/thread.jspa?threadID=482673messageID=2252508. The solution is to add some code in hudson.tasks.Mailer.createSession() like: props.put(mail.smtp.localhost, localServerName); I guess some code to pull the localServerName out of config would be needed to. In theory, a work around might be setting a system property when running hudson, but I've not been able to make this work yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12975) Configure screen broken (javascript error: findMatchingInput)
Allan Beaufour created JENKINS-12975: Summary: Configure screen broken (javascript error: findMatchingInput) Key: JENKINS-12975 URL: https://issues.jenkins-ci.org/browse/JENKINS-12975 Project: Jenkins Issue Type: Bug Components: gui Affects Versions: current Environment: Jenkins ver. 1.451, Ubuntu 10.04 Reporter: Allan Beaufour Attachments: Configure System [Jenkins].jpg I can no longer Configure my Jenkins install. When I hit /configure the Loading indicator never disappears (see screenshot). The javascript console has this error: [[ Uncaught TypeError: Object #Object has no method 'findMatchingInput' (anonymous function) e.targetUrlhudson-behavior.js:338 registerValidatorhudson-behavior.js:343 applybehavior.js:73 (anonymous function)behavior.js:79 Behaviour.applySubtreebehavior.js:68 Behaviour.applybehavior.js:54 (anonymous function)behavior.js:49 window.onload ]] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12779) Error when try to run all jobs in a view
[ https://issues.jenkins-ci.org/browse/JENKINS-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159816#comment-159816 ] Simon Westcott commented on JENKINS-12779: -- Hi Alper, I've not been able to replicate this yet. Could you tell me what version of bulk builder you're using and the full name of the view you're attempting to build? Thanks. Error when try to run all jobs in a view Key: JENKINS-12779 URL: https://issues.jenkins-ci.org/browse/JENKINS-12779 Project: Jenkins Issue Type: Bug Components: bulk-builder Affects Versions: current Environment: Ubuntu 10.04 Server Reporter: Alper Tekinap Assignee: Simon Westcott When try to run all jobs in a view it gives an error like: Status Code: 500 Exception: Stacktrace: java.lang.IllegalArgumentException: No enum const class org.jvnet.hudson.plugins.bulkbuilder.model.BuildType.ON at java.lang.Enum.valueOf(Enum.java:214) at org.jvnet.hudson.plugins.bulkbuilder.model.BuildType.valueOf(BuildType.java:31) at org.jvnet.hudson.plugins.bulkbuilder.BulkBuilderAction.doBuild(BulkBuilderAction.java:93) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477) at org.kohsuke.stapler.Stapler.service(Stapler.java:159) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) 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 winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:244) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.lang.Thread.run(Thread.java:636) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12968) Bulk-Builder does not passed parameters to builds
[ https://issues.jenkins-ci.org/browse/JENKINS-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159815#comment-159815 ] dogfood commented on JENKINS-12968: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_bulk-builder #61|http://ci.jenkins-ci.org/job/plugins_bulk-builder/61/] [Fixes JENKINS-12968] Fixed regression and added test (finally figure out how to!) (Revision 9ebc3cd4342dd5356ce61c5ffaab169b28fdd3fa) Result = SUCCESS Simon Westcott : Files : * src/test/java/org/jvnet/hudson/plugins/bulkbuilder/model/BuilderTest.java * src/main/java/org/jvnet/hudson/plugins/bulkbuilder/BulkBuilderAction.java Bulk-Builder does not passed parameters to builds - Key: JENKINS-12968 URL: https://issues.jenkins-ci.org/browse/JENKINS-12968 Project: Jenkins Issue Type: Bug Components: bulk-builder Affects Versions: current Reporter: Chris Stylianou Assignee: Simon Westcott When using the webform or directly through the external interface, parameters are not being passed to the build jobs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12968) Bulk-Builder does not passed parameters to builds
[ https://issues.jenkins-ci.org/browse/JENKINS-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Westcott resolved JENKINS-12968. -- Resolution: Fixed Resolved on master Bulk-Builder does not passed parameters to builds - Key: JENKINS-12968 URL: https://issues.jenkins-ci.org/browse/JENKINS-12968 Project: Jenkins Issue Type: Bug Components: bulk-builder Affects Versions: current Reporter: Chris Stylianou Assignee: Simon Westcott When using the webform or directly through the external interface, parameters are not being passed to the build jobs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12798) Plugin does not generate test-reports
[ https://issues.jenkins-ci.org/browse/JENKINS-12798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159818#comment-159818 ] Sami Tikka commented on JENKINS-12798: -- Please provide more details. E.g. a sample build output which fails to produce test-reports file is needed. Also, please report which OS X version you are using and which Xcode. What version of Jenkins and what version of the Xcode plugin? Plugin does not generate test-reports - Key: JENKINS-12798 URL: https://issues.jenkins-ci.org/browse/JENKINS-12798 Project: Jenkins Issue Type: Bug Components: xcode Affects Versions: current Environment: Mac OSX Reporter: Robert Labus Fix For: current A plugin should parse a build output and produce test-reports file, but it's simply not doing it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12968) Bulk-Builder does not passed parameters to builds
[ https://issues.jenkins-ci.org/browse/JENKINS-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159819#comment-159819 ] Simon Westcott commented on JENKINS-12968: -- Version 1.5 is available @ http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jvnet/hudson/plugins/bulk-builder/1.5/. This should be available in the update center within 24/48hrs. Bulk-Builder does not passed parameters to builds - Key: JENKINS-12968 URL: https://issues.jenkins-ci.org/browse/JENKINS-12968 Project: Jenkins Issue Type: Bug Components: bulk-builder Affects Versions: current Reporter: Chris Stylianou Assignee: Simon Westcott When using the webform or directly through the external interface, parameters are not being passed to the build jobs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12968) Bulk-Builder does not passed parameters to builds
[ https://issues.jenkins-ci.org/browse/JENKINS-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Westcott closed JENKINS-12968. Bulk-Builder does not passed parameters to builds - Key: JENKINS-12968 URL: https://issues.jenkins-ci.org/browse/JENKINS-12968 Project: Jenkins Issue Type: Bug Components: bulk-builder Affects Versions: current Reporter: Chris Stylianou Assignee: Simon Westcott When using the webform or directly through the external interface, parameters are not being passed to the build jobs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12912) URLTtrigger does not poll on jobs which are tied to disconnected slaves
[
https://issues.jenkins-ci.org/browse/JENKINS-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159820#comment-159820
]
SCM/JIRA link daemon commented on JENKINS-12912:
Code changed in jenkins
User: Gregory Boissinot
Path:
src/main/java/org/jenkinsci/lib/xtrigger/AbstractTrigger.java
http://jenkins-ci.org/commit/xtrigger-lib/092bff99c4861ae91949a15e85a1adfd1fc4a238
Log:
Fix JENKINS-12912
URLTtrigger does not poll on jobs which are tied to disconnected slaves
---
Key: JENKINS-12912
URL: https://issues.jenkins-ci.org/browse/JENKINS-12912
Project: Jenkins
Issue Type: Bug
Components: urltrigger
Environment: Jenkins 1.451
URLTrigger Plugin 0.10, 0.14
Reporter: OHTAKE Tomohiro
Assignee: gbois
Since 0.10, URLTtrigger does not poll on jobs which are tied to disconnected
slaves even if there are available executors on master.
URLTrigger Plugin 0.9 makes master poll the URL even if the jobs are tied to
slaves.
If there are changes in URL, a slave that is tied to the job wakes up and
runs the job.
URLTrigger 0.9 says that polling has been done on slaves, but master polles.
{code:title=URLTrigger Log (0.14, job which is tied to disconnected slaves)}
Polling for the job aa
Searching a node to run the polling for the label ''.
Can't find any complete active node for the polling action. Maybe slaves are
not yet active at this time or the number of executor of the master is 0.
Checking again in next polling schedule.
{code}
{code:title=URLTrigger Log (0.14, job which is not tied to any slaves)}
Polling for the job bb
Polling on master.
Polling started on Feb 28, 2012 10:22:42 AM
Invoking the url:
http://aaa.invalid/bb
Inspecting the content
Polling complete. Took 0.12 sec.
No changes.
{code}
{code:title=URLTrigger Log (0.9, job which is tied to disconnected slaves)}
Polling started on Feb 28, 2012 10:51:04 AM
Searching a node to run the polling for the label ''.
Invoking the url:
http://aaa.invalid/bb
Inspecting the content
Polling complete. Took 0.14 sec
No changes.
{code}
Workarounds:
* Downgrade URLTrigger Plugin to 0.9
* Do not tie jobs which uses Use URLTrigger
** Create a job that uses URLTrigger and do not tie the job to any slaves.
** Configure the job to build other projects in its post-build actions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12912) URLTtrigger does not poll on jobs which are tied to disconnected slaves
[
https://issues.jenkins-ci.org/browse/JENKINS-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159821#comment-159821
]
SCM/JIRA link daemon commented on JENKINS-12912:
Code changed in jenkins
User: Gregory Boissinot
Path:
pom.xml
src/main/java/org/jenkinsci/plugins/urltrigger/URLTrigger.java
src/main/resources/org/jenkinsci/plugins/urltrigger/URLTrigger/config.jelly
src/test/java/org/jenkinsci/plugins/urltrigger/URLTriggerTest.java
http://jenkins-ci.org/commit/urltrigger-plugin/c39c8880172d178842074fee2d0d47c3610e50bf
Log:
Fix JENKINS-12912
URLTtrigger does not poll on jobs which are tied to disconnected slaves
---
Key: JENKINS-12912
URL: https://issues.jenkins-ci.org/browse/JENKINS-12912
Project: Jenkins
Issue Type: Bug
Components: urltrigger
Environment: Jenkins 1.451
URLTrigger Plugin 0.10, 0.14
Reporter: OHTAKE Tomohiro
Assignee: gbois
Since 0.10, URLTtrigger does not poll on jobs which are tied to disconnected
slaves even if there are available executors on master.
URLTrigger Plugin 0.9 makes master poll the URL even if the jobs are tied to
slaves.
If there are changes in URL, a slave that is tied to the job wakes up and
runs the job.
URLTrigger 0.9 says that polling has been done on slaves, but master polles.
{code:title=URLTrigger Log (0.14, job which is tied to disconnected slaves)}
Polling for the job aa
Searching a node to run the polling for the label ''.
Can't find any complete active node for the polling action. Maybe slaves are
not yet active at this time or the number of executor of the master is 0.
Checking again in next polling schedule.
{code}
{code:title=URLTrigger Log (0.14, job which is not tied to any slaves)}
Polling for the job bb
Polling on master.
Polling started on Feb 28, 2012 10:22:42 AM
Invoking the url:
http://aaa.invalid/bb
Inspecting the content
Polling complete. Took 0.12 sec.
No changes.
{code}
{code:title=URLTrigger Log (0.9, job which is tied to disconnected slaves)}
Polling started on Feb 28, 2012 10:51:04 AM
Searching a node to run the polling for the label ''.
Invoking the url:
http://aaa.invalid/bb
Inspecting the content
Polling complete. Took 0.14 sec
No changes.
{code}
Workarounds:
* Downgrade URLTrigger Plugin to 0.9
* Do not tie jobs which uses Use URLTrigger
** Create a job that uses URLTrigger and do not tie the job to any slaves.
** Configure the job to build other projects in its post-build actions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )
[
https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159824#comment-159824
]
Nikolay Myakushkin commented on JENKINS-12916:
--
Thank you Bruno, for efficiency.
And thanks for your great tool.
Nick
Can't assign testng results to the testlink by Test Methode Name(only by
Java Class )
--
Key: JENKINS-12916
URL: https://issues.jenkins-ci.org/browse/JENKINS-12916
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: WinXP: Jenkins (org.jenkins-ci.main:jenkins-war:1.449),
Jenkins TestLink Plugin (3.0.2), TestNG Lib (6.4),TestLink 1.9.3 (Prague)
Reporter: Nikolay Myakushkin
Assignee: Bruno P. Kinoshita
Attachments: testlink-3.1-alpha2.hpi
I'm using testlink plugin for my project. It is very useful and easy to use.
Thanks to the authors. But I have some suggestion.
1.As I understand, test results from testng-results.xml are mapped to the
tests only by Java Class Custom field. Do I have any way to map them by
test-methode?
2.And one more question: I'm using dataproviders in my tests. Do I have any
mechanism to map the pairs (test-methode,dataprovider Object[]) to the tests.
I mean if I have
@DataProvider(name = test1)
public Object[][] createData1() {
return new Object[][] {
{ Cedric, new Integer(36) },
{ Anne, new Integer(37)},
};
}
//This test method declares that its data should be supplied by the Data
Provider
//named test1
@Test(dataProvider = test1)
public void verifyData1(String n1, Integer n2) {
AssertJUnit.assertTrue( n1.equals(Anne));
}
And I have 2 test in Testlink: 1. for { Cedric, new Integer(36) }, 2. for
{ Anne, new Integer(37)}.
And the results should map to each test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
