[JIRA] (JENKINS-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Marty Falatic created JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: systemInfo.txt Components: git Created: 13/Mar/13 6:12 AM Description: If a recursive symlink is present in one's git repo the new git/git-client plugins will fail badly as shown below. While having such a symlink may not be ideal, until git 1.3.0/ git-client 1.0.4 Jenkins did not have problems with it (nor have I had any other git client or tool fail because of this symlink). This appears to be specifically related to changes in the new git 1.3.0 plugin or its dependency git-client 1.0.4. Downgrading to the git 1.2.0 plugin and manually downgrading to the git-client 1.0.3 plugin was enough to remove this issue entirely. The problems seems specific to jgit. Note that I'm using Jenkins 1.505 and all other plugins are up-to-date. The details below contrast the working and broken builds (the only difference is the versions of the git plugins and their effects). A normal build (when using git 1.2.0 and git-client 1.0.3): Retriggered by user myself for Gerrit: http://gerritserver/710 Building on master in workspace /var/lib/jenkins/jobs/puppet/workspace Checkout:workspace / /var/lib/jenkins/jobs/puppet/workspace - hudson.remoting.LocalChannel@1307e9af Using strategy: Gerrit Trigger Last Built Revision: Revision b3f2bd79784969bd18866ff666f0ab46136ff196 (mybranch) Using shallow clone Wiping out workspace first. Cloning the remote Git repository Cloning repository git://gitserver/puppet git --version git version 1.7.9.5 Fetching upstream changes from origin Commencing build of Revision b3f2bd79784969bd18866ff666f0ab46136ff196 (mybranch) Checking out Revision b3f2bd79784969bd18866ff666f0ab46136ff196 (mybranch) workspace $ /bin/bash -ex /tmp/hudson3918244826320546803.sh --== ...and so on to a successful build ==-- Build break (when using git 1.3.0 and git-client 1.0.4): Retriggered by user myself for Gerrit: http://gerritserver/710 Building on master in workspace /var/lib/jenkins/jobs/puppet/workspace Checkout:workspace / /var/lib/jenkins/jobs/puppet/workspace - hudson.remoting.LocalChannel@6f0bc962 Using strategy: Gerrit Trigger Last Built Revision: Revision b3f2bd79784969bd18866ff666f0ab46136ff196 (mybranch) Using shallow clone Wiping out workspace first. Cloning the remote Git repository Cloning repository git://gitserver/puppet git --version git version 1.7.9.5 Commencing build of Revision b3f2bd79784969bd18866ff666f0ab46136ff196 (mybranch) Checking out Revision b3f2bd79784969bd18866ff666f0ab46136ff196 (mybranch) FATAL: Could not checkout b3f2bd79784969bd18866ff666f0ab46136ff196 hudson.plugins.git.GitException: Could not checkout b3f2bd79784969bd18866ff666f0ab46136ff196 at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:68) at hudson.plugins.git.GitAPI.checkout(GitAPI.java:208) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1273) at hudson.plugins.git.GitSCM.access$1100(GitSCM.java:57) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1232) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1208) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1208) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at
[JIRA] (JENKINS-17037) Null pointer exception when publishing results
justinas Urbanavicius commented on JENKINS-17037 Null pointer exception when publishing results I'm actually using phpunit 3.7, so you are saying that phpunit3 is not compatible with clover. Shouldn't it just skip the clover generation instead of an error, and put out some kind of a warning that unsupported format ? instead of exception and failing the build 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] (JENKINS-15560) Lazy loading cause’s http links from other html pages into Jenkins do not work properly
Christian Grobauer commented on JENKINS-15560 Lazy loading cause’s http links from other html pages into Jenkins do not work properly Here is what happens at our Jenkins: If we try to access e.g. a console output using the complete URL (pasting the URL to a browser, not navigating to the console output via the Jenkins page) the 404 error occurs. If we once navigate to the build via Jenkins, pasting the complete URL to a browser works again. 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] (JENKINS-17013) Git plugin fails with NPE (Jenkins 1.502, 1.503)
Nicolas De Loof resolved JENKINS-17013 as Fixed Git plugin fails with NPE (Jenkins 1.502, 1.503) Change By: Nicolas De Loof (13/Mar/13 8:41 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] (JENKINS-17187) Add columns to the main view that show the number of warnings
Ulli Hafner created JENKINS-17187 Add columns to the main view that show the number of warnings Issue Type: New Feature Assignee: Ulli Hafner Components: analysis-collector, analysis-core Created: 13/Mar/13 8:49 AM Description: Jenkins provides an extension point to add new columns to the list views. The analysis plug-ins should also provide new columns for: number of warnings plug-in status Project: Jenkins Priority: Minor Reporter: Ulli Hafner 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] (JENKINS-17164) Failed to record SCM polling for hudson.model.FreeStyleProject
Nicolas De Loof commented on JENKINS-17164 Failed to record SCM polling for hudson.model.FreeStyleProject Seems to be a conflict between git-client plugin, and (old) git plugin, as hudson.plugins.git.Branch was moved from git to git-client. Please double check you have git plugin 1.3.0 and git-client 1.0.4 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] (JENKINS-14575) SCM checkout retry count not working
Nicolas De Loof commented on JENKINS-14575 SCM checkout retry count not working git plugin 1.3.0 uses JGit to fetch (in combination with git-client 1.0.4), can you give it a try ? 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] (JENKINS-14201) Git submodules checked out in wrong place
Nicolas De Loof commented on JENKINS-14201 Git submodules checked out in wrong place git plugin 1.3.0 uses JGit to fetch remote, can you please give it a try an report this issue still is relevant ? 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] (JENKINS-14078) Fetch stopped working
Nicolas De Loof resolved JENKINS-14078 as Fixed Fetch stopped working rev-parse is now implemented with JGit, so this issue should be fixed as well (not system dependent anymore) Change By: Nicolas De Loof (13/Mar/13 8:56 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] (JENKINS-16075) Lint icon not shown when selecting a particular build
Christopher Orr commented on JENKINS-16075 Lint icon not shown when selecting a particular build Hi Mark, I'll take a look. Could you please paste the URL of the image which fails to load? 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] (JENKINS-10437) git plugin crashes using multiple repositories
Nicolas De Loof resolved JENKINS-10437 as Fixed git plugin crashes using multiple repositories git plugin now uses JGit (via git-client plugin), so this issue probably is fixed or at least reports a more useful error message, to diagnose a configuration issue Change By: Nicolas De Loof (13/Mar/13 9:18 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] (JENKINS-17124) ShowDiffs omits some configuration changes
Kathi Stutz commented on JENKINS-17124 ShowDiffs omits some configuration changes Fix will be included in next release (probably in April). 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] (JENKINS-13053) Jenkins doxygen plugin 0.10 - NoSuchMethodError issue
evernat resolved JENKINS-13053 as Wont Fix Jenkins doxygen plugin 0.10 - NoSuchMethodError issue Indeed, the plugin currently requires Java6. For example, here: https://github.com/jenkinsci/doxygen-plugin/blob/master/src/main/java/hudson/plugins/doxygen/DoxygenDirectoryParser.java#L141 I suppose that the compatibility with Java5 is now won't fix. Change By: evernat (13/Mar/13 10:04 AM) Status: Open Resolved Resolution: WontFix 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] (JENKINS-9589) SSH sessions kept open by Subversion checkout
evernat commented on JENKINS-9589 SSH sessions kept open by Subversion checkout Is it still a problem with recent versions of Jenkins and of the subversion 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] (JENKINS-17176) The Restrict matrix execution to subset Groovy filter is not evaluate
cjo9900 commented on JENKINS-17176 The Restrict matrix execution to subset Groovy filter is not evaluate Comments from the pull request This should not be evaluated here as the MatrixSubsetAction filter should be referring to the triggered matrix project, so in most cases this will return false as the AXIS that the matrix project has will not be available which are the normal cases for checking. So it can only reliably be checked in the Matrix project build. Actual evaluation takes place in the Matrix build in https://github.com/jenkinsci/parameterized-trigger-plugin/blob/master/src/main/java/hudson/plugins/parameterizedtrigger/matrix/MatrixBuildListenerImpl.java Thanks but for the evaluation, this Class is not called during the process. Should be called from DefaultMatrixExecutionStrategyImpl.java in a Matrix project from the static function in the hudson.matrix.listeners.MatrixBuildListener class. https://github.com/jenkinsci/jenkins/blob/6d95e3680c8edf49c2353633dd9c1a7072440989/core/src/main/java/hudson/matrix/DefaultMatrixExecutionStrategyImpl.java#L123 Sure but in my case, I have a freestyle project with a parameterized trigger configurations in post-build action to determine which build to launch next. I have to evaluate the Groovy filter which is never done in that case. 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] (JENKINS-17188) groovy-html.template missing catch block
Sebastian Kolb
created JENKINS-17188
groovy-html.template missing catch block
Issue Type:
Bug
Affects Versions:
current
Assignee:
Alex Earl
Attachments:
groovy-html.template
Components:
email-ext
Created:
13/Mar/13 10:17 AM
Description:
In the "MAVEN ARTIFACTS" section there is no }catch(e){..} block for a try{..} block that causes the exception
[[ Exception while replacing SCRIPT. Please report this as a bug. ]] {{ groovy.lang.GroovyRuntimeException: Failed to parse template script (your template may contain an error or be trying to use expressions not currently supported): startup failed: SimpleTemplateScript18.groovy: 146: expecting '}', found '' @ line 146, column 40. /* Generated by SimpleTemplateEngine */ ^ 1 error }}
Attached fixed template file.
Project:
Jenkins
Priority:
Major
Reporter:
Sebastian Kolb
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] (JENKINS-17189) Test results for the 'api' package hijacked by jenkins api documentation
francisdb created JENKINS-17189 Test results for the api package hijacked by jenkins api documentation Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: junit Created: 13/Mar/13 10:24 AM Description: My project has a package 'api' containing tests http://ci.carambla.com/job/myProject/lastCompletedBuild/testReport/ The Test Result report shows the package but I can not navigate into the reports for this package. http://ci.carambla.com/job/myProject/lastCompletedBuild/testReport/api/ ends up at the jenkins api documentation http://ci.carambla.com/job/myProject/lastCompletedBuild/testReport/api/ApiTest/testEditCar/ shows a 404 page Project: Jenkins Priority: Minor Reporter: francisdb 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] (JENKINS-17189) Test results for the 'api' package hijacked by jenkins api documentation
francisdb updated JENKINS-17189 Test results for the api package hijacked by jenkins api documentation Change By: francisdb (13/Mar/13 10:25 AM) Description: Myprojecthasapackageapicontainingtestshttp://ci. carambla project .com/job/myProject/lastCompletedBuild/testReport/TheTestResultreportshowsthepackagebutIcannotnavigateintothereportsforthispackage.http://ci. carambla project .com/job/myProject/lastCompletedBuild/testReport/api/endsupatthejenkinsapidocumentationhttp://ci. carambla project .com/job/myProject/lastCompletedBuild/testReport/api/ApiTest/testEditCar/showsa404page 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] (JENKINS-17176) The Restrict matrix execution to subset Groovy filter is not evaluate
cjo9900 commented on JENKINS-17176 The Restrict matrix execution to subset Groovy filter is not evaluate From your use case it seems that you want to run the filter against the current build variables to allow/prevent the downstream build to trigger. If this is the case you should look at the run condition branch and create a groovy run condition. https://github.com/jenkinsci/parameterized-trigger-plugin/pull/17 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] (JENKINS-17037) Null pointer exception when publishing results
SCM/JIRA link daemon commented on JENKINS-17037 Null pointer exception when publishing results Code changed in jenkins User: Seiji Sogabe Path: src/main/java/org/jenkinsci/plugins/cloverphp/CloverCoverageParser.java src/main/java/org/jenkinsci/plugins/cloverphp/CloverPublisher.java http://jenkins-ci.org/commit/cloverphp-plugin/c70e441c6671816e2085c7e12d513512e2a85ab6 Log: JENKINS-17037 added message if clover xml is incompatible with clover style Compare: https://github.com/jenkinsci/cloverphp-plugin/compare/d55c91f13092...c70e441c6671 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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] (JENKINS-8636) TestLink Plugin FATAL: Error creating test project
Ruslan Strazhnyk updated JENKINS-8636 TestLink Plugin FATAL: Error creating test project Change By: Ruslan Strazhnyk (13/Mar/13 11:24 AM) Environment: HudsonrunningonLinux(Ubuntu10.04LTS)withTestLink(1.9RC1)onthesamebox. Jenkinsver.1.499,TestLink1.9.5andTestlinkplugin3.1.8 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] (JENKINS-16835) jenkins.war version 1.500: windows slave connection issue
Josh Sinfield commented on JENKINS-16835 jenkins.war version 1.500: windows slave connection issue Hi Alben, I recently upgraded from 1.491 to 1.504 and it caused issues with communication to the slave. in 1.498 there was a security update for encrypting configuration data etc. : https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04 This means you have to re-key all your configuration files (see your Manage Jenkins page of your installation). I also had to replace the slave.jar, and add the "-secret xxx " option to the jenkins-slave.xml configuration on the slave ( where is the secret token). These can both be obtained from the manage nodes configuration page. After restarting the Node and Master they both connected together OK. Cheers, Josh 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] (JENKINS-17190) Help for Content Token Reference in plugin email-ext is in cryptic format
Klaus Weyers created JENKINS-17190 Help for Content Token Reference in plugin email-ext is in cryptic format Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: mailconfig-2.jpg Components: plugin Created: 13/Mar/13 11:55 AM Description: in configure project page, click on help-icon for "Content Token Reference": then HTML-Text is displayed as unformatted raw ascii, not as HTML. Environment: email-ext 2.27.1, Jenkins 1.505 on Windows XP, Firefox 19.0.2, java.version 1.6.0_26 Project: Jenkins Priority: Minor Reporter: Klaus Weyers 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] (JENKINS-17191) Default Content in plugin email-ext does not evaluate environment-variable with ${ENV, var}
Klaus Weyers
created JENKINS-17191
Default Content in plugin email-ext does not evaluate environment-variable with ${ENV, var}
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Attachments:
mailconfig-3.jpg
Components:
plugin
Created:
13/Mar/13 12:06 PM
Description:
Content Token Reference for Default Content allows use of environment-variables with ${ENV, var} where "var" is the name of the environment-variable. This does not work - at least not for subversion-Tags defined via build-parameters. ${ENV} displays all variables, but {$ENV,Branch_or_Tag} (where Branch_or_Tag is a build-parameter) is not evaluated and displayed wrong.
Environment:
email-ext 2.27.1, Jenkins 1.505 on Windows XP, Firefox 19.0.2, java.version 1.6.0_26
Project:
Jenkins
Priority:
Minor
Reporter:
Klaus Weyers
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] (JENKINS-13060) Can not access by --prefix value even if --prefix is set
evernat commented on JENKINS-13060 Can not access by --prefix value even if --prefix is set Is it reproduced with a recent Jenkins version? 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] (JENKINS-17192) Add support for phpunit3 coverage
justinas Urbanavicius created JENKINS-17192 Add support for phpunit3 coverage Issue Type: New Feature Affects Versions: current Assignee: sogabe Components: cloverphp-plugin Created: 13/Mar/13 12:34 PM Description: Please consider adding support for PHPUnit 3.x version, it's been available quite some time now, i doubt anyone is still using PHPUnit 2 Environment: Windows server 2008 R2 x64 Project: Jenkins Labels: plugin clover phpunit Priority: Major Reporter: justinas Urbanavicius 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] (JENKINS-17193) Missing Delete button
justinas Urbanavicius created JENKINS-17193 Missing Delete button Issue Type: Bug Affects Versions: current Assignee: sogabe Attachments: Capture.PNG Components: cloverphp-plugin Created: 13/Mar/13 12:39 PM Description: if "Publish clover PHP coverage report" added as post build action, there is no way to remove it, the delete button is missing. Environment: Windows Server 2008 R2 x64 Project: Jenkins Labels: delete button post-build Priority: Minor Reporter: justinas Urbanavicius 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] (JENKINS-17192) Add support for phpunit3 coverage
sogabe commented on JENKINS-17192 Add support for phpunit3 coverage PHPUnit3 has been already supported. You can use it with exec task in build.xml. CloverPHP plugin doe not support PHPunit2/3 task in phing build.xml. 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] (JENKINS-17194) Allow grouping of build jobs
Roland Gruber created JENKINS-17194 Allow grouping of build jobs Issue Type: New Feature Assignee: Unassigned Components: jenkinswalldisplay Created: 13/Mar/13 1:21 PM Description: The radiator view plugin allows to group the jobs by prefix. This should be possible also in wall plugin. Otherwise, it is not possible to generate a page for hundreds of jobs. E.g. jobs "foo_1" and "foo_2" will be grouped to "foo". Project: Jenkins Priority: Major Reporter: Roland Gruber 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] (JENKINS-15626) java.lang.IllegalArgumentException: CloverPublisher is ambiguous; matches both org.jenkinsci.plugins.cloverphp.CloverPublisher and hudson.plugins.clover.CloverPublisher
SCM/JIRA link daemon resolved JENKINS-15626 as Fixed java.lang.IllegalArgumentException: CloverPublisher is ambiguous; matches both org.jenkinsci.plugins.cloverphp.CloverPublisher and hudson.plugins.clover.CloverPublisher Change By: SCM/JIRA link daemon (13/Mar/13 1:32 PM) 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] (JENKINS-15626) java.lang.IllegalArgumentException: CloverPublisher is ambiguous; matches both org.jenkinsci.plugins.cloverphp.CloverPublisher and hudson.plugins.clover.CloverPublisher
SCM/JIRA link daemon commented on JENKINS-15626 java.lang.IllegalArgumentException: CloverPublisher is ambiguous; matches both org.jenkinsci.plugins.cloverphp.CloverPublisher and hudson.plugins.clover.CloverPublisher Code changed in jenkins User: Seiji Sogabe Path: src/main/java/org/jenkinsci/plugins/cloverphp/CloverBuildAction.java src/main/java/org/jenkinsci/plugins/cloverphp/CloverPHPPublisher.java src/main/java/org/jenkinsci/plugins/cloverphp/CloverProjectAction.java src/main/java/org/jenkinsci/plugins/cloverphp/CloverPublisher.java src/main/resources/org/jenkinsci/plugins/cloverphp/CloverPHPPublisher/config.jelly src/main/resources/org/jenkinsci/plugins/cloverphp/CloverPHPPublisher/config.properties src/main/resources/org/jenkinsci/plugins/cloverphp/CloverPHPPublisher/config_ja.properties src/main/resources/org/jenkinsci/plugins/cloverphp/CloverPublisher/config.jelly src/main/resources/org/jenkinsci/plugins/cloverphp/CloverPublisher/config.properties src/main/resources/org/jenkinsci/plugins/cloverphp/CloverPublisher/config_ja.properties src/main/resources/org/jenkinsci/plugins/cloverphp/Messages.properties src/main/resources/org/jenkinsci/plugins/cloverphp/Messages_ja.properties src/test/java/org/jenkinsci/plugins/cloverphp/ConfigurationRoundtripTest.java http://jenkins-ci.org/commit/cloverphp-plugin/4e26c8a4a822b76bd13b146258c8feca31638517 Log: FIXED JENKINS-15626 Conflict with standard clover plugin You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Edward Hartwell Goose created JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 13/Mar/13 2:12 PM Description: I just upgraded our git-client-plugin from 1.0.2 to 1.0.4 and now get an InvalidTagNameException. We were running Jenkins 1.505. The exception implies I've created a tag, which I certainly haven't, so I'm not sure how the issue is occurring. I'm assuming the issue is because the tag it believes it is receiving contains spaces. Here's the stacktrace: Using strategy: Default Last Built Revision: Revision b6db3c79b4f208e6989e4f10f00f564d189b7590 (origin/develop) Fetching changes from 1 remote Git repository Commencing build of Revision 8862b04b711a283d4e53962cc60e9b4203807d3a (origin/develop) Checking out Revision 8862b04b711a283d4e53962cc60e9b4203807d3a (origin/develop) FATAL: org.eclipse.jgit.api.errors.InvalidTagNameException: tag name jenkins-WOW - Dev-872 is invalid hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.InvalidTagNameException: tag name jenkins-WOW - Dev-872 is invalid at org.jenkinsci.plugins.gitclient.JGitAPIImpl.tag(JGitAPIImpl.java:179) at hudson.plugins.git.GitAPI.tag(GitAPI.java:220) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1239) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1196) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1196) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.eclipse.jgit.api.errors.InvalidTagNameException: tag name jenkins-WOW - Dev-872 is invalid at org.eclipse.jgit.api.TagCommand.processOptions(TagCommand.java:198) at org.eclipse.jgit.api.TagCommand.call(TagCommand.java:112) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.tag(JGitAPIImpl.java:175) ... 14 more Project: Jenkins Labels: plugin exception Priority: Major Reporter: Edward Hartwell Goose 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] (JENKINS-16720) Android SDK installation fails
brianjriddle commented on JENKINS-16720 Android SDK installation fails I can verify that it looks like the check SdkInstaller.java String all = sdk.getSdkToolsVersion() looks like it runs only on the master and not on the slave where the tools are installed. Tried to build on both a macosx slave and an linux slave with no success getting the sdk to install. Switched over to running this on master and it works. I have seen some mention of running commands like this on the slave via an jenkins api call. 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] (JENKINS-13753) plink call in build.bat file doesn't execute remote shell script
Robin Gatter
commented on JENKINS-13753
plink call in build.bat file doesnt execute remote shell script
I have an extremely similar problem: plink won't run under Jenkins, but the same (java) code runs fine in my IDE (IntelliJ). This is completely blocking black box tests that I want to write. Here is the complete Junit test code:
package com.itrsgroup.openaccess.testing.framework;
import static org.junit.Assert.assertEquals;
import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStream;
import java.io.InputStreamReader;
import org.junit.Test;
public class TempTest
{
private class StreamReader extends Thread {
private final InputStream inputStream;
public StreamReader(final InputStream in) {
inputStream = in;
}
public void run() {
try {
BufferedReader input = new BufferedReader(new InputStreamReader(inputStream));
String line;
while( (line = input.readLine()) != null ) {
System.out.println(line);
}
}
catch(IOException e) {
System.out.println("StreamReader IOException " + e.getMessage());
}
}
}
@Test
public void testStderrMergedToStdout()
{
int errorCode = -1;
String cmd[] = {"\"C:\\Program Files (x86)\\PuTTY\\plink.exe\"",
"rgatter@192.168.220.83",
"$SCRIPTS/testoutput.sh"};
try {
Process process = new ProcessBuilder(cmd).redirectErrorStream(true).start();
StreamReader outputStream = new StreamReader(process.getInputStream());
outputStream.start();
errorCode = process.waitFor();
System.out.println("Error code: " + errorCode);
}
catch(IOException e) {
System.out.println("I/O exception");
}
catch(InterruptedException e) {
System.out.println("Interrupted exception");
}
assertEquals(errorCode, 0);
}
}
Here is the output when run in IntelliJ:
stdout message
stderr message
Error code: 0
Process finished with exit code 0
Here is the output when run under Jenkins:
---
T E S T S
---
Running com.itrsgroup.openaccess.testing.framework.TempTest
and that's the lot - the test code hangs at this point.
I can successfully start other executables (e.g. cmd.exe), but careful monitoring has shown that plink.exe doesn't even start under Jenkins and the process running this code just hangs forever. I'm running Jenkins 1.505 as a service on Windows 7 64-bit, and I've changed the service properties so that it uses my own login credentials. Using plink -V gives "plink: Development snapshot 2008-12-11:r8371", which I believe to be the latest release.
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] (JENKINS-17188) groovy-html.template missing catch block
Alex Earl commented on JENKINS-17188 groovy-html.template missing catch block Doh, that's what I get for trying to do the fix quick. Thanks for the patch, I'll push soon and do another release. 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] (JENKINS-16521) Multi-Project Throttle Categories don't work with Matrix jobs
Wael Darwich commented on JENKINS-16521 Multi-Project Throttle Categories dont work with Matrix jobs I tried 1.7.1 but had the same unwanted behaviour as 1.7.2! 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] (JENKINS-14201) Git submodules checked out in wrong place
Arkadiy Shapkin commented on JENKINS-14201 Git submodules checked out in wrong place I have same issue after installing Analysis Collector Plugin and PMD 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] (JENKINS-14605) Simple means to obtain logged in user's id
stanislav bashkirtsev commented on JENKINS-14605 Simple means to obtain logged in users id I'm trying to use these methods while debugging one of plugins, but it returns SYSTEM. Can you give me a hint here - in what situations that SYSTEM is returned? 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] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
Max Burdge commented on JENKINS-11024 Some commands dont work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others I would also like a solution or workaround for this issue. 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] (JENKINS-10503) Option to bypass proxy for JIRA Plugin
Nicolas De Loof commented on JENKINS-10503 Option to bypass proxy for JIRA Plugin Jira plugin uses Axis 1.x that don't let plugin configure a Proxy object. Seems the only option to set proxy is system properties. 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] (JENKINS-17192) Add support for phpunit3 coverage
sogabe commented on JENKINS-17192 Add support for phpunit3 coverage use type attribute as follows. phpunit printsummary="true" codecoverage="true" formatter todir="reports" type="clover" outfile="coverage.xml" / This plugin only parse clover-style coverage report. 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] (JENKINS-13753) plink call in build.bat file doesn't execute remote shell script
Robin Gatter commented on JENKINS-13753 plink call in build.bat file doesnt execute remote shell script Just discovered I wasn't after all using the most recent vesion of plink.exe, but same problem exists with latest verson (Release 0.62). 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] (JENKINS-14575) SCM checkout retry count not working
Moshe Immerman commented on JENKINS-14575 SCM checkout retry count not working I tried git plugin and this seems to have made things worse: I now get this exception when cloning on a windows 2003 machine: FATAL: Invalid path: installation/full/service.vmoptions org.eclipse.jgit.dircache.InvalidPathException: Invalid path: installation/full/service.vmoptions at org.eclipse.jgit.dircache.DirCacheCheckout.processEntry(DirCacheCheckout.java:526) at org.eclipse.jgit.dircache.DirCacheCheckout.preScanTwoTrees(DirCacheCheckout.java:248) at org.eclipse.jgit.dircache.DirCacheCheckout.doCheckout(DirCacheCheckout.java:405) at org.eclipse.jgit.dircache.DirCacheCheckout.checkout(DirCacheCheckout.java:391) at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:240) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:64) at hudson.plugins.git.GitAPI.checkout(GitAPI.java:208) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1261) at hudson.plugins.git.GitSCM.access$1200(GitSCM.java:57) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1220) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1196) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:60) at java.lang.Thread.run(Unknown Source) On a windows 2008 server the clone process stalls after: Using strategy: Default Fetching changes from 1 remote Git repository Ubuntu based servers in the same multi configuration build are cloning fine. 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] (JENKINS-13598) jenkins-multijob-plugin - Multijob plugin throws exception when trying to get cancelled job
Alex Nickolaevsky commented on JENKINS-13598 jenkins-multijob-plugin - Multijob plugin throws exception when trying to get cancelled job Can't reproduce the issue but improved the canceled future evaluation. 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] (JENKINS-13598) jenkins-multijob-plugin - Multijob plugin throws exception when trying to get cancelled job
Alex Nickolaevsky resolved JENKINS-13598 as Fixed jenkins-multijob-plugin - Multijob plugin throws exception when trying to get cancelled job Can't reproduce the issue but improved the canceled future evaluation. Change By: Alex Nickolaevsky (13/Mar/13 3:36 PM) Status: Reopened 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] (JENKINS-14201) Git submodules checked out in wrong place
Arkadiy Shapkin edited a comment on JENKINS-14201 Git submodules checked out in wrong place I have same issue after installing Analysis Collector Plugin and PMD Plugin Jenkins run git fetch for submodule with wrong working directory. Git plugin 1.1.9 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] (JENKINS-17196) Add an action that allows to reset the reference build
Ulli Hafner created JENKINS-17196 Add an action that allows to reset the reference build Issue Type: New Feature Assignee: Ulli Hafner Components: analysis-core Created: 13/Mar/13 3:39 PM Description: Currently, the evaluation of new and fixed warnings is based on a reference build. I.e., as soon as a build gets unstable due to a warnings threshold being hit the job remains unstable until the new warnings are fixed. Sometimes it make sense to reset the build status. I.e., the reference build should be removed so that in the next build the result will be stable. Project: Jenkins Priority: Minor Reporter: Ulli Hafner 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] (JENKINS-13598) jenkins-multijob-plugin - Multijob plugin throws exception when trying to get cancelled job
Alex Nickolaevsky edited a comment on JENKINS-13598 jenkins-multijob-plugin - Multijob plugin throws exception when trying to get cancelled job Tested on java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.6) 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] (JENKINS-15560) Lazy loading cause’s http links from other html pages into Jenkins do not work properly
Kohsuke Kawaguchi commented on JENKINS-15560 Lazy loading cause’s http links from other html pages into Jenkins do not work properly Does the server console report any errors/warnings? I'm afraid as it stands now, this ticket is too vague to let us act on it. 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] (JENKINS-10068) Ability to remove a Promotion on a promoted build
Bruce Edge commented on JENKINS-10068 Ability to remove a Promotion on a promoted build Definitely want this too. Accidental promotions are currently permanent. Is there any manual procedure to remove promotions? 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] (JENKINS-9233) Builds hang on jabber notification when XMPP server is not responding
Jeff Stewart commented on JENKINS-9233 Builds hang on jabber notification when XMPP server is not responding Is there any news about this bug? Our company IM server went down last night and brought production to a standstill. Seems IM messages should be queued and threaded as to not halt the build(s) if there's a hiccup in the network, or an unstable IM server specified. I personally wouldn't consider a failed IM notification a "build breaker". I would consider a hung Jenkins server due to a deadlock in a low priority notification routine a much bigger issue. Jenkins 1.504 Instant Messenger Plugin 1.25 Jabber Plugin 1.25 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] (JENKINS-4861) Post-build deployment of Maven artifacts does not work with scpexe-type repository
Raúl Wegmann reopened JENKINS-4861 Post-build deployment of Maven artifacts does not work with scpexe-type repository We can reproduce this error with Jenkins ver. 1.505 (using Maven 3). Please ask if you need further information. Change By: Raúl Wegmann (13/Mar/13 3:58 PM) Resolution: CannotReproduce Status: Resolved Reopened 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] (JENKINS-13341) Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to fail
Jakub Czaplicki commented on JENKINS-13341 Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to fail Just had an identical issue and switching to Oracle's JDK (1.7) indeed fixed it. 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] (JENKINS-4861) Post-build deployment of Maven artifacts does not work with scpexe-type repository
Raúl Wegmann commented on JENKINS-4861 Post-build deployment of Maven artifacts does not work with scpexe-type repository Here is the current stack trace: ERROR: Failed to deploy artifacts: Could not transfer artifact com.example.util:lib-util-core:jar:2.0.0.0.0-20130313.100035-11 from/to lib-deploy-snapshots (scpexe://maven.example.com/maven/snapshots/): Exit code: 2 - /bin/sh: 1: cd: can't cd to /srv/jenkins/jobs/libj-util_trunk_ci/modules/com.example.util-util-core/builds/2013-03-13_10-58-15/archive/com.example.util/lib-util-core/2.0.0.0.0-SNAPSHOT org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to deploy artifacts: Could not transfer artifact com.example.util:lib-util-core:jar:2.0.0.0.0-20130313.100035-11 from/to lib-deploy-snapshots (scpexe://maven.example.com/maven/snapshots/): Exit code: 2 - /bin/sh: 1: cd: can't cd to /srv/jenkins/jobs/libj-util_trunk_ci/modules/com.example.util-util-core/builds/2013-03-13_10-58-15/archive/com.example.util/lib-util-core/2.0.0.0.0-SNAPSHOT at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:141) at hudson.maven.reporters.MavenArtifactRecord.deploy(MavenArtifactRecord.java:190) at hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:176) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:786) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:947) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:733) at hudson.model.Run.execute(Run.java:1592) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.sonatype.aether.deployment.DeploymentException: Failed to deploy artifacts: Could not transfer artifact com.example.util:lib-util-core:jar:2.0.0.0.0-20130313.100035-11 from/to lib-deploy-snapshots (scpexe://maven.example.com/maven/snapshots/): Exit code: 2 - /bin/sh: 1: cd: can't cd to /srv/jenkins/jobs/libj-util_trunk_ci/modules/com.example.util-util-core/builds/2013-03-13_10-58-15/archive/com.example.util/lib-util-core/2.0.0.0.0-SNAPSHOT at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:280) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:443) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137) ... 11 more Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not transfer artifact com.example.util:lib-util-core:jar:2.0.0.0.0-20130313.100035-11 from/to lib-deploy-snapshots (scpexe://maven.example.com/maven/snapshots/): Exit code: 2 - /bin/sh: 1: cd: can't cd to /srv/jenkins/jobs/libj-util_trunk_ci/modules/com.example.util-util-core/builds/2013-03-13_10-58-15/archive/com.example.util/lib-util-core/2.0.0.0.0-SNAPSHOT at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:951) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:941) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:837) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:467) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:274) ... 14 more Caused by: org.apache.maven.wagon.TransferFailedException: Exit code: 2 - /bin/sh: 1: cd: can't cd to /srv/jenkins/jobs/libj-util_trunk_ci/modules/com.example.util-util-core/builds/2013-03-13_10-58-15/archive/com.example.util/lib-util-core/2.0.0.0.0-SNAPSHOT at org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeScpCommand(ScpExternalWagon.java:321) at org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:403) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:811) ... 16 more It is trying to cd into /srv/jenkins/jobs/libj-util_trunk_ci/modules/com.example.util-util-core/, while the
[JIRA] (JENKINS-15799) loosing matrix sub builds
Kohsuke Kawaguchi resolved JENKINS-15799 as Fixed loosing matrix sub builds I tested Jenkins 1.485 in the debugger on Ubuntu and observed the lazy loading behaviour. Through the forced GC and accessing pages, I was able to cause Jenkins to discard records and reloads them on demand, and it worked correctly for me. I did notice that JENKINS-15587 would have caused a problem on Windows with the symlink support on. Based on the original reporter's environment and Zvi Karov's environment, which are both Windows that's capable of supporting symlinks, I'm marking this as a duplicate of JENKINS-15587. The fix for JENKINS-15587 is scheduled for 1.507. If you continue to see this problem post 1.507, please reopen the ticket but be sure to provide the following information: OS on your master If Windows, whether you see symlinks in the builds directory any suspicious warning/error messages in the server console output that points to a load failure of build records. Change By: Kohsuke Kawaguchi (13/Mar/13 4:50 PM) 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] (JENKINS-15533) Jobs disappearing with Jenkins 1.485 and 1.486
Kohsuke Kawaguchi updated JENKINS-15533 Jobs disappearing with Jenkins 1.485 and 1.486 Change By: Kohsuke Kawaguchi (13/Mar/13 4:51 PM) Assignee: huybrechts KohsukeKawaguchi Component/s: parameterized-trigger 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] (JENKINS-15533) Envinject plugin incompatibility with Jenkins 1.485
Kohsuke Kawaguchi
commented on JENKINS-15533
Envinject plugin incompatibility with Jenkins 1.485
According to the stack trace, what seems to be happening is that the EnvInjectAction.build field is referring to another build object (IOW, not the one that the action is associated with.) In such case, a part of the referenced AbstractBuil}}d object gets sucked into the serialized build.xml, but it's missing some critical transient fields (such as {{Run.project), and that causes this NPE. That's the root cause.
What made the difference between 1.485 and 1.486 is probably that 1.485 recovered gracefully from this failure by letting the job load OK (even though some build records failed to load), and 1.486 didn't do that.
Writing a test to verify this.
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] (JENKINS-15533) Envinject plugin incompatibility with Jenkins 1.485
Kohsuke Kawaguchi commented on JENKINS-15533 Envinject plugin incompatibility with Jenkins 1.485 With a bit of experiment, I found that SerializationMethodInvoker catches this exception and turns it into ObjectAccessException, so such a NPE gets handled gracefully. The stack trace from the current version of Jenkins is as follows. The stack trace is likely bit different for 1.486, but the basic flow of the event will be the same. RunMap.retrieve catches IOException: Mar 13, 2013 10:40:58 AM hudson.model.RunMap retrieve WARNING: could not load /tmp/hudson2161128827066568119test/jobs/test0/builds/1 hudson.util.IOException2: Unable to read /tmp/hudson2161128827066568119test/jobs/test0/builds/2013-03-13_10-40-57/build.xml at hudson.XmlFile.unmarshal(XmlFile.java:170) at hudson.model.Run.reload(Run.java:307) at hudson.model.Run.init(Run.java:296) at hudson.model.AbstractBuild.init(AbstractBuild.java:182) at hudson.model.Build.init(Build.java:103) at hudson.model.FreeStyleBuild.init(FreeStyleBuild.java:41) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1106) at hudson.model.AbstractProject$1.create(AbstractProject.java:306) at hudson.model.AbstractProject$1.create(AbstractProject.java:304) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:629) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:368) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:526) at hudson.model.AbstractProject.getBuildByNumber(AbstractProject.java:1028) at hudson.model.AbstractProject$getBuildByNumber.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) at hudson.model.RunMapTest.testRuntimeExceptionInUnmarshalling(RunMapTest.groovy:53) 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:601) at junit.framework.TestCase.runTest(TestCase.java:176) at org.jvnet.hudson.test.HudsonTestCase.runTest(HudsonTestCase.java:440) at junit.framework.TestCase.runBare(TestCase.java:141) at org.jvnet.hudson.test.HudsonTestCase.runBare(HudsonTestCase.java:296) at junit.framework.TestResult$1.protect(TestResult.java:122) at junit.framework.TestResult.runProtected(TestResult.java:142) at junit.framework.TestResult.run(TestResult.java:125) at junit.framework.TestCase.run(TestCase.java:129) at junit.framework.TestSuite.runTest(TestSuite.java:255) at junit.framework.TestSuite.run(TestSuite.java:250) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) at org.junit.runner.JUnitCore.run(JUnitCore.java:160) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:76) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:195) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:63) 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:601) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) Caused by: com.thoughtworks.xstream.converters.ConversionException: Could not call hudson.model.RunMapTest$BombAction.readResolve() : null : Could not call hudson.model.RunMapTest$BombAction.readResolve() : null Debugging information message : Could not call
[JIRA] (JENKINS-13703) AJP support does not respect the specs. breaks with SSL
Jesse Glick updated JENKINS-13703 AJP support does not respect the specs. breaks with SSL Change By: Jesse Glick (13/Mar/13 5:52 PM) Component/s: core Component/s: www 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] (JENKINS-15533) Envinject plugin incompatibility with Jenkins 1.485
SCM/JIRA link daemon commented on JENKINS-15533 Envinject plugin incompatibility with Jenkins 1.485 Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java test/src/test/groovy/hudson/model/RunMapTest.groovy http://jenkins-ci.org/commit/jenkins/c7ad5e97060d71e82073c1ccbf824a21e8998746 Log: JENKINS-15533 testing if the lazy loading can gracefully tolerate a RuntimeException during unmarshalling. At least in the current version this working as expected You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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] (JENKINS-15533) Envinject plugin incompatibility with Jenkins 1.485
Kohsuke Kawaguchi resolved JENKINS-15533 as Cannot Reproduce Envinject plugin incompatibility with Jenkins 1.485 I'm tentatively closing this as INCOMPLETE until additional stack traces and error messages are provided. To the extent that's tested on my system, this is a relatively isolated incident with core and envinject. Change By: Kohsuke Kawaguchi (13/Mar/13 5:53 PM) Status: Open Resolved Resolution: CannotReproduce 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] (JENKINS-13703) AJP support does not respect the specs. breaks with SSL
Jesse Glick resolved JENKINS-13703 as Duplicate AJP support does not respect the specs. breaks with SSL Seems a duplicate of JENKINS-5753. Change By: Jesse Glick (13/Mar/13 5:54 PM) Status: Open Resolved Resolution: Duplicate 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] (JENKINS-14201) Git submodules checked out in wrong place
Arkadiy Shapkin commented on JENKINS-14201 Git submodules checked out in wrong place Problem was solved after updating to latest Jenkins 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] (JENKINS-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Craig Newell created JENKINS-17198 Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 13/Mar/13 6:10 PM Description: The jGIT client has lots of repository compatibility issues as compared to the normal command line git client. Updating to git-client 1.0.4 results in: Building remotely on mac mini 1 in workspace /Users/jenkins/workspace/Fuji Checkout:Fuji / /Users/jenkins/workspace/Fuji - hudson.remoting.Channel@c27576:mac mini 1 Using strategy: Default Last Built Revision: Revision 88877737299f64f83e8230928e8b2db4ebe1826b (origin/master) Fetching changes from 1 remote Git repository Commencing build of Revision 124296a2ae55606a975ed1888c4e030dd9e0f3e4 (origin/master) Checking out Revision 124296a2ae55606a975ed1888c4e030dd9e0f3e4 (origin/master) FATAL: Could not checkout 124296a2ae55606a975ed1888c4e030dd9e0f3e4 hudson.plugins.git.GitException: Could not checkout 124296a2ae55606a975ed1888c4e030dd9e0f3e4 at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:68) at hudson.plugins.git.GitAPI.checkout(GitAPI.java:208) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1273) at hudson.plugins.git.GitSCM.access$1100(GitSCM.java:57) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1232) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1208) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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:680) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files: support/tools/relink/macholib/MachO.py whereas the normal command line git client is happy with the repository. Can we get a work around of a configuration setting to say use either the command line git client or jGIT? Environment: git-client 1.0.2 Project: Jenkins Priority: Blocker Reporter: Craig Newell 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] (JENKINS-8713) Display skipped test messages in results
Michael Clarke started work on JENKINS-8713 Display skipped test messages in results Change By: Michael Clarke (13/Mar/13 6:22 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] (JENKINS-8713) Display skipped test messages in results
Michael Clarke assigned JENKINS-8713 to Michael Clarke Display skipped test messages in results Change By: Michael Clarke (13/Mar/13 6:22 PM) Assignee: MichaelClarke 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] (JENKINS-17199) import statement doesn't work Build flow DSL
Kohsuke Kawaguchi created JENKINS-17199 import statement doesnt work Build flow DSL Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow Created: 13/Mar/13 6:50 PM Description: Looks like the plugin is doing string manipulation on the user-written script, which makes the import statement illegal since it won't be the first in the script. I know a better way to do it, so I'd like to fix this. This is more of a reminder to myself. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi 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] (JENKINS-17200) SCM.TAG permission not eagerly loaded
Jesse Glick created JENKINS-17200 SCM.TAG permission not eagerly loaded Issue Type: Bug Assignee: Jesse Glick Components: core Created: 13/Mar/13 6:53 PM Description: In order to be included in Permission.getAll(), a Permission needs to be initialized in a static block inside an @Extension or otherwise definitely loaded during startup. The visible symptom is that you might configure an authorization strategy such as matrix with all permissions granted, then go back later and see SCM/Tag missing, because it was unknown earlier. Project: Jenkins Labels: permissions Priority: Major Reporter: Jesse Glick 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] (JENKINS-15533) Envinject plugin incompatibility with Jenkins 1.485
dogfood commented on JENKINS-15533 Envinject plugin incompatibility with Jenkins 1.485 Integrated in jenkins_main_trunk #2367 JENKINS-15533 testing if the lazy loading can gracefully tolerate a RuntimeException during unmarshalling. (Revision c7ad5e97060d71e82073c1ccbf824a21e8998746) Result = UNSTABLE kohsuke : c7ad5e97060d71e82073c1ccbf824a21e8998746 Files : test/src/test/groovy/hudson/model/RunMapTest.groovy core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java 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] (JENKINS-17201) SCM Sync page does not match current version (options explanations missing)
Charles Wilson created JENKINS-17201 SCM Sync page does not match current version (options explanations missing) Issue Type: Improvement Affects Versions: current Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 13/Mar/13 7:14 PM Description: https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin shows only the SVN repository URL no 'none' or 'git' no 'never bother me' no 'display status' ... Environment: Windows Server 2008 R2 Project: Jenkins Labels: scm plugin configuration Priority: Trivial Reporter: Charles Wilson 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] (JENKINS-16075) Lint icon not shown when selecting a particular build
Mark Wigzell commented on JENKINS-16075 Lint icon not shown when selecting a particular build a href=""img height="24" style="margin: 2px;" alt="" width="24" src="" //a a href=""Lint Issues/a/divdiv class="task" You can see that the ref to /static/06707550 is doubled. 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] (JENKINS-17202) no events fired on config changes in http://localhost:8080/computer/%28master%29/configure
Khai Do created JENKINS-17202 no events fired on config changes in http://localhost:8080/computer/%28master%29/configure Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 13/Mar/13 7:53 PM Description: No events get fired when user updates master computer properties from this page: http://localhost:8080/computer/%28master%29/configure I've tried getting events from ComputerListener and SaveableListener but none of the events in these listeners get fired for the update. Evens will get fired when changes to master are made from http://localhost:8080/configure Environment: Ubuntu quantal Jenkins ver 1.502 java 1.6 maven 3 Project: Jenkins Labels: configuration listener events Priority: Minor Reporter: Khai Do 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] (JENKINS-17203) save happens after ComputerListener onConfigurationChange event
Khai Do created JENKINS-17203 save happens after ComputerListener onConfigurationChange event Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 13/Mar/13 8:02 PM Description: When i make a configuration change the change doesn't get save until after the onConfigurationChange event exits. I think it should be the opposite.. Save the configuration first then fire the event. That way I can at least query what changed and do something. Environment: ubuntu quantal maven 3 java 1.6 jenkins 1.502 Project: Jenkins Labels: listener api configuration Priority: Major Reporter: Khai Do 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] (JENKINS-17204) GIT fetch failing since update to Jenkins 1.505
cray fellow created JENKINS-17204 GIT fetch failing since update to Jenkins 1.505 Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 13/Mar/13 8:37 PM Description: Jenkins 1.505 Jenkins GIT plugin 1.3.0 Jenkins GIT client plugin 1.0.4 Git projects are all accepting the git URL and the clone is succeeding, easily verified by checking the contents of the workspaces. However, once the plugin attempts to fetch changes, this is happening consistently: Building in workspace /mnt/jenkins/jobs/nativeDependencyBase/workspace Checkout:workspace / /mnt/jenkins/jobs/nativeDependencyBase/workspace - hudson.remoting.LocalChannel@39e6697e Using strategy: Default selected Git installation does not exists. Using Default Last Built Revision: Revision 2a2765e4045956a91be3d9bff4f19feaffa8ffc0 (origin/master) Fetching changes from 1 remote Git repository ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.TransportException: g...@github.com:myuser/myproject.git: UnknownHostKey: github.com. RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48 at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:212) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:230) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:793) at hudson.plugins.git.GitSCM.access$000(GitSCM.java:57) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:976) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:942) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:942) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1101) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1567) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.eclipse.jgit.api.errors.TransportException: g...@github.com:myuser/myproject.git: UnknownHostKey: github.com. RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48 at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:137) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:208) ... 17 more Caused by: org.eclipse.jgit.errors.TransportException: g...@github.com:myuser/myproject.git: UnknownHostKey: github.com. RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48 at org.eclipse.jgit.transport.JschConfigSessionFactory.getSession(JschConfigSessionFactory.java:142) at org.eclipse.jgit.transport.SshTransport.getSession(SshTransport.java:121) at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.init(TransportGitSsh.java:248) at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1104) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) ... 18 more Caused by: com.jcraft.jsch.JSchException: UnknownHostKey: github.com. RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48 at com.jcraft.jsch.Session.checkHost(Session.java:718) at com.jcraft.jsch.Session.connect(Session.java:313) at org.eclipse.jgit.transport.JschConfigSessionFactory.getSession(JschConfigSessionFactory.java:116) ... 25 more ERROR: Could not fetch from any repository FATAL: Could not fetch from any repository hudson.plugins.git.GitException: Could not fetch from any
[JIRA] (JENKINS-17053) Warn user about variable names with . (dot)
Joris van der Pol
commented on JENKINS-17053
Warn user about variable names with . (dot)
Gregory,
variables are a confusing lot in Jenkins, since there is a lot of variation among plugins and the ways they are handled. I try to use the java property style with dots to group properties.
The simplest example I came up with is the following:
Parameterize the build with a string parameter called 'version.name'.
In the 'execute windows batch command' build step you can use %version.name%.
The parameterized build trigger plugin can handle the same situation. I'm not sure on 'execute shell' build step, since I have not used it before. Maybe it is possible to have a duplicate variable which replaces the dot for an underscore. I saw the build-name-setter plugin use another way: ${ENV,var="VARIABLENAME"}.
With kind regards,
Joris
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] (JENKINS-17204) GIT fetch failing since update to Jenkins 1.505
cray fellow updated JENKINS-17204 GIT fetch failing since update to Jenkins 1.505 Change By: cray fellow (13/Mar/13 8:40 PM) Description: Jenkins1.505JenkinsGITplugin1.3.0JenkinsGITclientplugin1.0.4GitprojectsareallacceptingthegitURLandthecloneissucceeding,easilyverifiedbycheckingthecontentsoftheworkspaces. However Icangototheworkspaceatthecommandlineanddothingssuchas:sudo-uuserJenkinsRunsAsgitpullsudo-uuserJenkinsRunsAsgitaddsomeFilesudo-uuserJenkinsRunsAsgitcommit-mtestingsudo-uuserJenkinsRunsAsgitpushandallofthosework , once whichtomerulesoutansshkeyissue.ThecloneinJenkinsevenworks,butsomehowitisnotusing the keyswhendoingthepartitcallsFetchingchanges.Oncethe pluginattemptstofetchchanges duringabuild ,thisishappeningconsistently:Buildinginworkspace/mnt/jenkins/jobs/nativeDependencyBase/workspaceCheckout:workspace//mnt/jenkins/jobs/nativeDependencyBase/workspace-hudson.remoting.LocalChannel@39e6697eUsingstrategy:DefaultselectedGitinstallationdoesnotexists.UsingDefaultLastBuiltRevision:Revision2a2765e4045956a91be3d9bff4f19feaffa8ffc0(origin/master)Fetchingchangesfrom1remoteGitrepositoryERROR:Problemfetchingfromorigin/origin-couldbeunavailable.Continuinganywayhudson.plugins.git.GitException:org.eclipse.jgit.api.errors.TransportException:g...@github.com:myuser/myproject.git:UnknownHostKey:github.com.RSAkeyfingerprintis16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48 atorg.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:212) athudson.plugins.git.GitAPI.fetch(GitAPI.java:230) athudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:793) athudson.plugins.git.GitSCM.access$000(GitSCM.java:57) athudson.plugins.git.GitSCM$2.invoke(GitSCM.java:976) athudson.plugins.git.GitSCM$2.invoke(GitSCM.java:942) athudson.FilePath.act(FilePath.java:865) athudson.FilePath.act(FilePath.java:838) athudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:942) athudson.plugins.git.GitSCM.checkout(GitSCM.java:1101) athudson.model.AbstractProject.checkout(AbstractProject.java:1353) athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) athudson.model.Run.execute(Run.java:1567) athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:237)Causedby:org.eclipse.jgit.api.errors.TransportException:g...@github.com:myuser/myproject.git:UnknownHostKey:github.com.RSAkeyfingerprintis16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48 atorg.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:137) atorg.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:208) ...17moreCausedby:org.eclipse.jgit.errors.TransportException:g...@github.com:myuser/myproject.git:UnknownHostKey:github.com.RSAkeyfingerprintis16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48 atorg.eclipse.jgit.transport.JschConfigSessionFactory.getSession(JschConfigSessionFactory.java:142) atorg.eclipse.jgit.transport.SshTransport.getSession(SshTransport.java:121) atorg.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.init(TransportGitSsh.java:248) atorg.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147) atorg.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) atorg.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) atorg.eclipse.jgit.transport.Transport.fetch(Transport.java:1104) atorg.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) ...18moreCausedby:com.jcraft.jsch.JSchException:UnknownHostKey:github.com.RSAkeyfingerprintis16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48 atcom.jcraft.jsch.Session.checkHost(Session.java:718) atcom.jcraft.jsch.Session.connect(Session.java:313) atorg.eclipse.jgit.transport.JschConfigSessionFactory.getSession(JschConfigSessionFactory.java:116) ...25moreERROR:CouldnotfetchfromanyrepositoryFATAL:Couldnotfetchfromanyrepositoryhudson.plugins.git.GitException:Couldnotfetchfromanyrepository athudson.plugins.git.GitSCM$2.invoke(GitSCM.java:981) athudson.plugins.git.GitSCM$2.invoke(GitSCM.java:942)
[JIRA] (JENKINS-15014) TestFlight automatically replaces old builds
lacostej
resolved JENKINS-15014 as Cannot Reproduce
TestFlight automatically replaces old builds
I can't reproduce this.
The code in the plugin is (was also in 1.3.1) pretty simple and the parameter replace is only passed as True if the argument was set to true
entity.addPart("replace", new StringBody(replace ? "True" : "False"));
I cannot see how this can go wrong... If you still have the problem, please try with the latest plugin version.
Change By:
lacostej
(13/Mar/13 8:41 PM)
Status:
Open
Resolved
Resolution:
CannotReproduce
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] (JENKINS-17205) TestFlight upload if Replace argument used when deploying APKs
lacostej created JENKINS-17205 TestFlight upload if Replace argument used when deploying APKs Issue Type: Bug Assignee: Unassigned Components: testflight Created: 13/Mar/13 8:43 PM Description: I've put an ugly workaround (874512bfb33ffbd2d12e20e631f80ec18d24096b) to prevent the argument to be passed when deploying APKs. I also reported the isseu to testgflight. The workaround will have to be removed when issue fixed on testflight side. Project: Jenkins Priority: Major Reporter: lacostej 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] (JENKINS-17205) TestFlight upload fails if Replace argument used when deploying APKs
lacostej updated JENKINS-17205 TestFlight upload fails if Replace argument used when deploying APKs Change By: lacostej (13/Mar/13 8:44 PM) Summary: TestFlightupload fails ifReplaceargumentusedwhendeployingAPKs 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] (JENKINS-13490) Passing multiline text parameter to ant broken (windows)
pixman20
commented on JENKINS-13490
Passing multiline text parameter to ant broken (windows)
I am having the same issue. The only workaround for me is using the 'Execute Batch command' to execute Ant manually, which means I don't get the benefits of the 'Execute Ant' build step plugin.
In my situation, I want to have a job where users can enter the ClearCase config spec they want to use for that build (with Base ClearCase plugin) and the SCM uses that parameter for the build. I had that working correctly, but unfortunately the Ant step is then pasting in the large multi-line config spec into the Ant command line.
I do not know why parameterized builds automatically pass values through to Ant (or Maven) at all, as I would expect this to be up to the user to do -Dmy.ant.property=${MY_BUILD_PARAMETER}
Perhaps this can be changed to use a checkbox ('Automatically populate build parameters') that defaults to true to not break backwards compatibility, but allows us to turn it off.
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] (JENKINS-17206) Want to disable the drop-downs
Ken Beal created JENKINS-17206 Want to disable the drop-downs Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: ui-changes Created: 13/Mar/13 8:52 PM Description: The specific use case: I want to copy the job name from the main page, so that in an email it will show the text and also be a hyperlink to the job. However, when the drop-down pops up, it stops the highlighting and starts it from where the cursor currently is, so if I've dragged through and highlighted half the name, when the drop-down appears, that half will be un-highlighted, and as I continue dragging it'll highlight the other half of the name. This thus requires rapid dragging which is making this far less usable than it used to be, before the drop-downs were imposed. Environment: Windows, Chrome Project: Jenkins Priority: Major Reporter: Ken Beal 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] (JENKINS-17204) GIT fetch failing since update to Jenkins 1.505
Christian Pelster commented on JENKINS-17204 GIT fetch failing since update to Jenkins 1.505 Same for me with the exact same versions 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] (JENKINS-17204) GIT fetch failing since update to Jenkins 1.505
Luke D commented on JENKINS-17204 GIT fetch failing since update to Jenkins 1.505 I've been banging my head against the wall for two days now trying to solve this. 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] (JENKINS-17199) import statement doesn't work Build flow DSL
SCM/JIRA link daemon resolved JENKINS-17199 as Fixed import statement doesnt work Build flow DSL Change By: SCM/JIRA link daemon (13/Mar/13 9:14 PM) 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] (JENKINS-17199) import statement doesn't work Build flow DSL
SCM/JIRA link daemon commented on JENKINS-17199 import statement doesnt work Build flow DSL Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/groovy/com/cloudbees/plugins/flow/FlowDSL.groovy src/test/groovy/com/cloudbees/plugins/flow/BindingTest.groovy src/test/groovy/com/cloudbees/plugins/flow/BuildTest.groovy http://jenkins-ci.org/commit/build-flow-plugin/f10be22bdc7693e3e12137ae8fab1fe05788b3a7 Log: FIXED JENKINS-17199 To inject DSL into the script being parsed, the common technique used elsewhere (for example in Spring bean builder Groovy DSL) is to set the DSL object as a delegate. This avoids the need to do string manipulation, and there's no ExpandoMetaClass hack necessary. I'v moved the bindings to FlowDelegate. This resolves the conflict between "build" as a variable and "build" as a function (since binding gets found more quickly it tries to evaluate that variable as a Callable), and it'll also make it easier for people to find all the available DSL methods/variables in one place. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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] (JENKINS-17029) update-center.json seems to be broken
Craig de Stigter commented on JENKINS-17029 update-center.json seems to be broken Same issue here after upgrade to 1.505 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] (JENKINS-17204) GIT fetch failing since update to Jenkins 1.505
cray fellow commented on JENKINS-17204 GIT fetch failing since update to Jenkins 1.505 Hey guys, I tried downgrading everything and same exact thing. HOWEVER! I put -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true into my JAVA_OPTS and restarted Tomcat to force the git client NOT to use JGit, and it worked! The issue must have to do with how JGit gets the SSH/shell session. It must not be looking in the right ~/.ssh folder. I hope this helps you guys too. 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] (JENKINS-17204) GIT fetch failing since update to Jenkins 1.505
cray fellow updated JENKINS-17204 GIT fetch failing since update to Jenkins 1.505 Change By: cray fellow (13/Mar/13 9:21 PM) Priority: Major Blocker 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] (JENKINS-17199) import statement doesn't work Build flow DSL
Kohsuke Kawaguchi commented on JENKINS-17199 import statement doesnt work Build flow DSL Created https://github.com/jenkinsci/build-flow-plugin/pull/21 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] (JENKINS-17204) GIT fetch failing since update to Jenkins 1.505
Luke D commented on JENKINS-17204 GIT fetch failing since update to Jenkins 1.505 cray fellow: You did it! If you're ever in central California, look me up and I'll buy you a beer. For those of you who are used to starting Jenkins from terminal, here's the command that made it work for me (with the important bit starting after the java and before the -jar): nohup java -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true -jar ~/Documents/jenkins.war --httpPort=8081 --ajp13Port=8010 /tmp/jenkins.log 21 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] (JENKINS-13125) HTTP Content-Range Header one byte past file length
Eric Blom commented on JENKINS-13125 HTTP Content-Range Header one byte past file length Like Rolland, we are also running in to this problem on 1.480.3. 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] (JENKINS-17207) Automatically install JDK 6 does not list update 43
Zygimantas Augilius created JENKINS-17207 Automatically install JDK 6 does not list update 43 Issue Type: Bug Assignee: Unassigned Components: core Created: 13/Mar/13 9:41 PM Description: In Manage, under JDK, check "Install automatically." Under "Install from java.sun.com" expand the "version" drop down. It does not show version 6u43, though it is available from oracle. Project: Jenkins Priority: Major Reporter: Zygimantas Augilius 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] (JENKINS-13125) HTTP Content-Range Header one byte past file length
Eric Blom reopened JENKINS-13125 HTTP Content-Range Header one byte past file length I hope I'm not causing a problem here by reopening this issue as I just registered for an account here and might be violating protocol. However, like Roland we still see this issue in v1.480.3. Change By: Eric Blom (13/Mar/13 9:44 PM) Resolution: Fixed Status: Resolved Reopened 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] (JENKINS-17204) GIT fetch failing since update to Jenkins 1.505
cray fellow commented on JENKINS-17204 GIT fetch failing since update to Jenkins 1.505 I have now re-upgraded to Jenkins 1.505, GIT plugin 1.3.0, GIT client 1.04 and can confirm the above tweak still does the git fetch without issue. Cheers! 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] (JENKINS-15589) build URL in failed emails is broken
Kohsuke Kawaguchi commented on JENKINS-15589 build URL in failed emails is broken I'm marking this bug as closed as a duplicate of JENKINS-15587. Accessing the build via URL does trigger the lazy loading (in fact there's no way to access any build without trigering a loading). Then later through other code path you manage to have the build in question loaded. So the only plausible explanation that I have is that one is using symlinks, and the other was using build ID to load. On symlink-enabled Windows, the former would hit JENKINS-15587, while the latter doesn't. 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] (JENKINS-15583) building builds (running builds) do not show up anymore in the list of builds of a job (json API)
SCM/JIRA link daemon commented on JENKINS-15583 building builds (running builds) do not show up anymore in the list of builds of a job (json API) Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/model/Job.java core/src/main/java/hudson/util/RunList.java http://jenkins-ci.org/commit/jenkins/fe9f676028773df181f0b9ec823b3cdd08d5cf3d Log: FIXED JENKINS-15583 Report 100 recent builds in the JSON API, including in-progress builds. Not reporting all the builds since this would nullify the lazy loading effect. Will introduce a pagenation API that supports retrieval. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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] (JENKINS-15583) building builds (running builds) do not show up anymore in the list of builds of a job (json API)
SCM/JIRA link daemon resolved JENKINS-15583 as Fixed building builds (running builds) do not show up anymore in the list of builds of a job (json API) Change By: SCM/JIRA link daemon (13/Mar/13 10:19 PM) 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] (JENKINS-15333) Unable to see build history after upgrade
Kohsuke Kawaguchi resolved JENKINS-15333 as Incomplete Unable to see build history after upgrade There have been several fall out issues that stem from JENKINS-8754 (see the issues linked from that), and some critical fixes such as JENKINS-15587 is just getting into 1.507. This ticket is clearly related to this, but it just doesn't have enough details for us to act on. Because many of those issues have been fixed since this issue has been reported, I'm marking this closed as INCOMPLETE. If you continue to see problems post 1.507, please open separate tickets and include the stack trace from the server console output, as well as your OS and whether the symlink support is enabled. Change By: Kohsuke Kawaguchi (13/Mar/13 10:33 PM) Status: Open Resolved Assignee: KohsukeKawaguchi Resolution: Incomplete 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] (JENKINS-8713) Display skipped test messages in results
SCM/JIRA link daemon commented on JENKINS-8713 Display skipped test messages in results Code changed in jenkins User: Michael Clarke Path: core/src/main/java/hudson/tasks/junit/CaseResult.java core/src/main/resources/hudson/tasks/junit/CaseResult/index.jelly http://jenkins-ci.org/commit/jenkins/3b58cd294f8266f2e4dc80356bf172c37769030e Log: FIXED JENKINS-8713 Display test skipped messages in test results 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] (JENKINS-8713) Display skipped test messages in results
SCM/JIRA link daemon commented on JENKINS-8713 Display skipped test messages in results Code changed in jenkins User: Michael Clarke Path: changelog.html http://jenkins-ci.org/commit/jenkins/2aa0293858d50b064128a9a74f4d25d3f5c4a5c8 Log: JENKINS-8713 Add changelog entry Compare: https://github.com/jenkinsci/jenkins/compare/fe9f67602877...2aa0293858d5 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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.
