[JIRA] (JENKINS-13475) Matrix Authorization Strategy for anonymous with read permission caused connection problem
Alexey Larsky created JENKINS-13475: --- Summary: Matrix Authorization Strategy for anonymous with read permission caused connection problem Key: JENKINS-13475 URL: https://issues.jenkins-ci.org/browse/JENKINS-13475 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Reporter: Alexey Larsky I use anonymous permission for read rss feed. Since Jenkins 1.459 its behavios change: Matrix Authorization Strategy with permission anonymous::Overall::read and anonymous::Job::read caused connection problem with anonymous permission -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13474) Failed to parse form data
[
https://issues.jenkins-ci.org/browse/JENKINS-13474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastian_bergmann resolved JENKINS-13474.
--
Resolution: Cannot Reproduce
Repeated the same steps that lead to the error and I was not able to reproduce
it. Weird.
> Failed to parse form data
> -
>
> Key: JENKINS-13474
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13474
> Project: Jenkins
> Issue Type: Bug
> Components: core
>Affects Versions: current
> Environment: Jenkins 1.460
>Reporter: sebastian_bergmann
>
> Failed to parse form data. Please report this problem as a bug
> JSON={"":" type=\"image/svg+xml\" width=\"500\"><\/embed>\n src=\"ws/build/pdepend/dependencies.svg\" type=\"image/svg+xml\"
> width=\"500\"><\/embed>","builder":{"antOpts":"","buildFile":"","kind":"hudson.tasks.Ant","properties":"","stapler-class":"hudson.tasks.Ant","targets":""},"core:apply":"","description":" height=\"300\" src=\"ws/build/pdepend/overview-pyramid.svg\"
> type=\"image/svg+xml\" width=\"500\"><\/embed>\n src=\"ws/build/pdepend/dependencies.svg\" type=\"image/svg+xml\"
> width=\"500\"><\/embed>","displayNameOrNull":"","htmlpublisher-HtmlPublisher":{"reportTargets":[{"keepAll":true,"reportDir":"build/api","reportFiles":"index.html","reportName":"API
>
> Documentation"},{"keepAll":true,"reportDir":"build/code-browser","reportFiles":"index.html","reportName":"Code
>
> Browser"}]},"hudson-plugins-ansicolor-AnsiColorBuildWrapper":{},"hudson-plugins-checkstyle-CheckStylePublisher":{"canComputeNew":{"failedNewAll":"","failedNewHigh":"","failedNewLow":"","failedNewNormal":"","unstableNewAll":"","unstableNewHigh":"","unstableNewLow":"","unstableNewNormal":"","useDeltaValues":false},"canRunOnFailed":true,"defaultEncoding":"","failedTotalAll":"","failedTotalHigh":"","failedTotalLow":"","failedTotalNormal":"","healthy":"","pattern":"build/logs/checkstyle.xml","shouldDetectModules":false,"thresholdLimit":"low","unHealthy":"","unstableTotalAll":"","unstableTotalHigh":"","unstableTotalLow":"","unstableTotalNormal":""},"hudson-plugins-dry-DryPublisher":{"canComputeNew":{"failedNewAll":"","failedNewHigh":"","failedNewLow":"","failedNewNormal":"","unstableNewAll":"","unstableNewHigh":"","unstableNewLow":"","unstableNewNormal":"","useDeltaValues":false},"canRunOnFailed":true,"defaultEncoding":"","failedTotalAll":"","failedTotalHigh":"","failedTotalLow":"","failedTotalNormal":"","healthy":"","highThreshold":"50","normalThreshold":"25","pattern":"build/logs/pmd-cpd.xml","shouldDetectModules":false,"thresholdLimit":"low","unHealthy":"","unstableTotalAll":"","unstableTotalHigh":"","unstableTotalLow":"","unstableTotalNormal":""},"hudson-plugins-jdepend-JDependRecorder":{"configuredJDependFile":"build/logs/jdepend.xml"},"hudson-plugins-plot-PlotPublisher":{"plots":[{"csvFileName":"123.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"A
> - Lines of code","useDescr":false,"yaxis":"Lines of
> Code"},{"csvFileName":"1107599928.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"B
> -
> Structures","useDescr":false,"yaxis":"Count"},{"csvFileName":"523405415.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"G
> - Average Length","useDescr":false,"yaxis":"Average Non-Comment Lines of
> Code"},{"csvFileName":"186376189.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"H
> - Relative Cyclomatic Complexity","useDescr":false,"yaxis":"Cyclomatic
> Complexity by
> Structure"},{"csvFileName":"594356163.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"D
> - Types of
> Classes","useDescr":false,"yaxis":"Count"},{"csvFileName":"1019987862.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"E
> - Types of
> Methods","useDescr":false,"yaxis":"Count"},{"csvFileName":"217648577.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"F
> - Types of
> Constants","useDescr":false,"yaxis":"Count"},{"csvFileName":"174807245.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv","fileType":{"displayTableFlag":false,"exclusionValues":"Classes,Methods,Functions,Test
> Clases,Test
> Methods","inclusionFlag":"INCLUDE_BY_STRING","url":"","value":"csv"}},"style":"line","title":"C
> -
> Testing","useDescr":false,"yaxis":"Count"}]},"hudson-plugins-pmd-PmdPublisher":{"canComputeNew":{"failedNewAll":"","failedNewHigh":"","failedNewLow":"","failedNewNormal":"","unstableNewAll":"","unstableNewHigh":"","unstableNewLow":"","unstableNewNormal":"","u
[JIRA] (JENKINS-13474) Failed to parse form data
[
https://issues.jenkins-ci.org/browse/JENKINS-13474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastian_bergmann closed JENKINS-13474.
> Failed to parse form data
> -
>
> Key: JENKINS-13474
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13474
> Project: Jenkins
> Issue Type: Bug
> Components: core
>Affects Versions: current
> Environment: Jenkins 1.460
>Reporter: sebastian_bergmann
>
> Failed to parse form data. Please report this problem as a bug
> JSON={"":" type=\"image/svg+xml\" width=\"500\"><\/embed>\n src=\"ws/build/pdepend/dependencies.svg\" type=\"image/svg+xml\"
> width=\"500\"><\/embed>","builder":{"antOpts":"","buildFile":"","kind":"hudson.tasks.Ant","properties":"","stapler-class":"hudson.tasks.Ant","targets":""},"core:apply":"","description":" height=\"300\" src=\"ws/build/pdepend/overview-pyramid.svg\"
> type=\"image/svg+xml\" width=\"500\"><\/embed>\n src=\"ws/build/pdepend/dependencies.svg\" type=\"image/svg+xml\"
> width=\"500\"><\/embed>","displayNameOrNull":"","htmlpublisher-HtmlPublisher":{"reportTargets":[{"keepAll":true,"reportDir":"build/api","reportFiles":"index.html","reportName":"API
>
> Documentation"},{"keepAll":true,"reportDir":"build/code-browser","reportFiles":"index.html","reportName":"Code
>
> Browser"}]},"hudson-plugins-ansicolor-AnsiColorBuildWrapper":{},"hudson-plugins-checkstyle-CheckStylePublisher":{"canComputeNew":{"failedNewAll":"","failedNewHigh":"","failedNewLow":"","failedNewNormal":"","unstableNewAll":"","unstableNewHigh":"","unstableNewLow":"","unstableNewNormal":"","useDeltaValues":false},"canRunOnFailed":true,"defaultEncoding":"","failedTotalAll":"","failedTotalHigh":"","failedTotalLow":"","failedTotalNormal":"","healthy":"","pattern":"build/logs/checkstyle.xml","shouldDetectModules":false,"thresholdLimit":"low","unHealthy":"","unstableTotalAll":"","unstableTotalHigh":"","unstableTotalLow":"","unstableTotalNormal":""},"hudson-plugins-dry-DryPublisher":{"canComputeNew":{"failedNewAll":"","failedNewHigh":"","failedNewLow":"","failedNewNormal":"","unstableNewAll":"","unstableNewHigh":"","unstableNewLow":"","unstableNewNormal":"","useDeltaValues":false},"canRunOnFailed":true,"defaultEncoding":"","failedTotalAll":"","failedTotalHigh":"","failedTotalLow":"","failedTotalNormal":"","healthy":"","highThreshold":"50","normalThreshold":"25","pattern":"build/logs/pmd-cpd.xml","shouldDetectModules":false,"thresholdLimit":"low","unHealthy":"","unstableTotalAll":"","unstableTotalHigh":"","unstableTotalLow":"","unstableTotalNormal":""},"hudson-plugins-jdepend-JDependRecorder":{"configuredJDependFile":"build/logs/jdepend.xml"},"hudson-plugins-plot-PlotPublisher":{"plots":[{"csvFileName":"123.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"A
> - Lines of code","useDescr":false,"yaxis":"Lines of
> Code"},{"csvFileName":"1107599928.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"B
> -
> Structures","useDescr":false,"yaxis":"Count"},{"csvFileName":"523405415.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"G
> - Average Length","useDescr":false,"yaxis":"Average Non-Comment Lines of
> Code"},{"csvFileName":"186376189.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"H
> - Relative Cyclomatic Complexity","useDescr":false,"yaxis":"Cyclomatic
> Complexity by
> Structure"},{"csvFileName":"594356163.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"D
> - Types of
> Classes","useDescr":false,"yaxis":"Count"},{"csvFileName":"1019987862.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"E
> - Types of
> Methods","useDescr":false,"yaxis":"Count"},{"csvFileName":"217648577.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"F
> - Types of
> Constants","useDescr":false,"yaxis":"Count"},{"csvFileName":"174807245.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv","fileType":{"displayTableFlag":false,"exclusionValues":"Classes,Methods,Functions,Test
> Clases,Test
> Methods","inclusionFlag":"INCLUDE_BY_STRING","url":"","value":"csv"}},"style":"line","title":"C
> -
> Testing","useDescr":false,"yaxis":"Count"}]},"hudson-plugins-pmd-PmdPublisher":{"canComputeNew":{"failedNewAll":"","failedNewHigh":"","failedNewLow":"","failedNewNormal":"","unstableNewAll":"","unstableNewHigh":"","unstableNewLow":"","unstableNewNormal":"","useDeltaValues":false},"canRunOnFailed":true,"defaultEncoding":"","failedTotalAll":"","failedTotalHigh":"","failedTotalLow":"","failedTotalNor
[JIRA] (JENKINS-13474) Failed to parse form data
sebastian_bergmann created JENKINS-13474:
Summary: Failed to parse form data
Key: JENKINS-13474
URL: https://issues.jenkins-ci.org/browse/JENKINS-13474
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Environment: Jenkins 1.460
Reporter: sebastian_bergmann
Failed to parse form data. Please report this problem as a bug
JSON={"":"<\/embed>\n<\/embed>","builder":{"antOpts":"","buildFile":"","kind":"hudson.tasks.Ant","properties":"","stapler-class":"hudson.tasks.Ant","targets":""},"core:apply":"","description":"<\/embed>\n<\/embed>","displayNameOrNull":"","htmlpublisher-HtmlPublisher":{"reportTargets":[{"keepAll":true,"reportDir":"build/api","reportFiles":"index.html","reportName":"API
Documentation"},{"keepAll":true,"reportDir":"build/code-browser","reportFiles":"index.html","reportName":"Code
Browser"}]},"hudson-plugins-ansicolor-AnsiColorBuildWrapper":{},"hudson-plugins-checkstyle-CheckStylePublisher":{"canComputeNew":{"failedNewAll":"","failedNewHigh":"","failedNewLow":"","failedNewNormal":"","unstableNewAll":"","unstableNewHigh":"","unstableNewLow":"","unstableNewNormal":"","useDeltaValues":false},"canRunOnFailed":true,"defaultEncoding":"","failedTotalAll":"","failedTotalHigh":"","failedTotalLow":"","failedTotalNormal":"","healthy":"","pattern":"build/logs/checkstyle.xml","shouldDetectModules":false,"thresholdLimit":"low","unHealthy":"","unstableTotalAll":"","unstableTotalHigh":"","unstableTotalLow":"","unstableTotalNormal":""},"hudson-plugins-dry-DryPublisher":{"canComputeNew":{"failedNewAll":"","failedNewHigh":"","failedNewLow":"","failedNewNormal":"","unstableNewAll":"","unstableNewHigh":"","unstableNewLow":"","unstableNewNormal":"","useDeltaValues":false},"canRunOnFailed":true,"defaultEncoding":"","failedTotalAll":"","failedTotalHigh":"","failedTotalLow":"","failedTotalNormal":"","healthy":"","highThreshold":"50","normalThreshold":"25","pattern":"build/logs/pmd-cpd.xml","shouldDetectModules":false,"thresholdLimit":"low","unHealthy":"","unstableTotalAll":"","unstableTotalHigh":"","unstableTotalLow":"","unstableTotalNormal":""},"hudson-plugins-jdepend-JDependRecorder":{"configuredJDependFile":"build/logs/jdepend.xml"},"hudson-plugins-plot-PlotPublisher":{"plots":[{"csvFileName":"123.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"A
- Lines of code","useDescr":false,"yaxis":"Lines of
Code"},{"csvFileName":"1107599928.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"B
-
Structures","useDescr":false,"yaxis":"Count"},{"csvFileName":"523405415.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"G
- Average Length","useDescr":false,"yaxis":"Average Non-Comment Lines of
Code"},{"csvFileName":"186376189.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"H
- Relative Cyclomatic Complexity","useDescr":false,"yaxis":"Cyclomatic
Complexity by
Structure"},{"csvFileName":"594356163.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"D
- Types of
Classes","useDescr":false,"yaxis":"Count"},{"csvFileName":"1019987862.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"E
- Types of
Methods","useDescr":false,"yaxis":"Count"},{"csvFileName":"217648577.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv"},"style":"line","title":"F
- Types of
Constants","useDescr":false,"yaxis":"Count"},{"csvFileName":"174807245.csv","group":"phploc","numBuilds":"100","series":{"file":"build/logs/phploc.csv","fileType":{"displayTableFlag":false,"exclusionValues":"Classes,Methods,Functions,Test
Clases,Test
Methods","inclusionFlag":"INCLUDE_BY_STRING","url":"","value":"csv"}},"style":"line","title":"C
-
Testing","useDescr":false,"yaxis":"Count"}]},"hudson-plugins-pmd-PmdPublisher":{"canComputeNew":{"failedNewAll":"","failedNewHigh":"","failedNewLow":"","failedNewNormal":"","unstableNewAll":"","unstableNewHigh":"","unstableNewLow":"","unstableNewNormal":"","useDeltaValues":false},"canRunOnFailed":true,"defaultEncoding":"","failedTotalAll":"","failedTotalHigh":"","failedTotalLow":"","failedTotalNormal":"","healthy":"","pattern":"build/logs/pmd.xml","shouldDetectModules":false,"thresholdLimit":"low","unHealthy":"","unstableTotalAll":"","unstableTotalHigh":"","unstableTotalLow":"","unstableTotalNormal":""},"hudson-plugins-violations-ViolationsPublisher":{"encoding":"default","fauxProjectPath":"","limit":"100","max":["999","999","999","999","999","999","999","999","999","999","999","999","999","999","999"],"min":["10","10","10","10","10","10","10","10","10","10","10","10","10","10","10"],"pattern
[JIRA] (JENKINS-13044) Ant multiple properties delimited by spaces parsed as a single property
[ https://issues.jenkins-ci.org/browse/JENKINS-13044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161672#comment-161672 ] Devin Greene commented on JENKINS-13044: Is there any known work-around for this? > Ant multiple properties delimited by spaces parsed as a single property > --- > > Key: JENKINS-13044 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13044 > Project: Jenkins > Issue Type: Bug > Components: ant >Affects Versions: current > Environment: SunOS ldnwebv10 5.10 Generic_120012-14 i86pc i386 i86pc > Solaris > Jenkins STABLE 1.424.3 >Reporter: Ed Randall > > Configuring an Ant task on a job with multiple properties on 1 line separated > by a space, ie.: > name1=value1 name2=value2 > Results at execution time in: > ant ... "-Dname1=value1 name2=value2" > This is not expected, what I would expect from the documentation is: > -Dname1=value1 -Dname2=value2 > etc. > eg. > Properties: offline=1 user.prefs.dir=/home/hudson/config/Bedrock-DEV-config > user.bedrock.properties=bedrock-quicktest.properties > console log: > [Bedrock-DEV-GF-EL-03-quick-test] $ > /home/hudson/tools/apache-ant-1.7.1/bin/ant > -DUPSTREAM_BUILD_TAG=jenkins-Bedrock-DEV-GF-EL-01-compile-2656 > -DP4_CHANGELIST_PARAM=322808 "-Doffline=1 > user.prefs.dir=/home/hudson/config/Bedrock-DEV-config > user.bedrock.properties=bedrock-quicktest.properties" hudson.quicktests > Buildfile: build.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13472) java.lang.IllegalArgumentException: Can't parse
[
https://issues.jenkins-ci.org/browse/JENKINS-13472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Murrell updated JENKINS-13472:
Description:
Using version 2.5 of the Jenkins promoted builds plugin I get the following
when I try to promote a build that has no previous promotions:
{code}
java.lang.IllegalArgumentException: Can't parse
at hudson.matrix.Combination.fromString(Combination.java:218)
at hudson.matrix.MatrixProject.getItem(MatrixProject.java:568)
at hudson.matrix.MatrixProject.getItem(MatrixProject.java:90)
at jenkins.model.Jenkins.getItem(Jenkins.java:2158)
at jenkins.model.Jenkins.getItem(Jenkins.java:2179)
at
hudson.plugins.promoted_builds.conditions.ManualCondition.doApprove(ManualCondition.java:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:485)
at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)
at
winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync
[JIRA] (JENKINS-13473) Links Between Maven Multi-Module Site's
ahhughes created JENKINS-13473: -- Summary: Links Between Maven Multi-Module Site's Key: JENKINS-13473 URL: https://issues.jenkins-ci.org/browse/JENKINS-13473 Project: Jenkins Issue Type: Improvement Components: maven Affects Versions: current Environment: unknown. Reporter: ahhughes When building a maven site for a multi-module project the html content is built into the following ./target/site/* ./module-a/target/site/* ./module-a/target/site/* However, when the site is deployed it is restructured as: ./*.html ./module-a/*.html ./module-b/*.html Since the filesystem's are not the same, the href links will be broken on at least one (the first one) href='./module-a/blah.html' != href='../../module-a/target/site/blah.html' Currently the jenkin 'maven generated site' link (per maven job) provides a link to the broken parent/root pom's site. All links to child modules, and those in between child modules are broken. To fix this, I would suggest that the maven support automatically set the parameters (relative to the jenkins workspace) for site:stage and/or site:stage-deploy so that the site is built/deployed with a destination that will be hosted/published by jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13472) java.lang.IllegalArgumentException: Can't parse
Brian Murrell created JENKINS-13472:
---
Summary: java.lang.IllegalArgumentException: Can't parse
Key: JENKINS-13472
URL: https://issues.jenkins-ci.org/browse/JENKINS-13472
Project: Jenkins
Issue Type: Bug
Components: promoted-builds
Affects Versions: current
Environment: Jenkins 1.458
Reporter: Brian Murrell
Priority: Blocker
Using version 2.5 of the Jenkins promoted builds plugin I get the following
when I try to promote a build that has no previous promotions:
{code}
java.lang.IllegalArgumentException: Can't parse
at hudson.matrix.Combination.fromString(Combination.java:218)
at hudson.matrix.MatrixProject.getItem(MatrixProject.java:568)
at hudson.matrix.MatrixProject.getItem(MatrixProject.java:90)
at jenkins.model.Jenkins.getItem(Jenkins.java:2158)
at jenkins.model.Jenkins.getItem(Jenkins.java:2179)
at
hudson.plugins.promoted_builds.conditions.ManualCondition.doApprove(ManualCondition.java:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:485)
at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)
at
winstone.RequestH
[JIRA] (JENKINS-13471) Tests listed in incorrect namespace
Marcus Bristol created JENKINS-13471:
Summary: Tests listed in incorrect namespace
Key: JENKINS-13471
URL: https://issues.jenkins-ci.org/browse/JENKINS-13471
Project: Jenkins
Issue Type: Bug
Components: nunit
Affects Versions: current
Reporter: Marcus Bristol
Assignee: redsolo
Attachments: nunit-results.xml
Unit test results are occasionally put under different namespaces, depending on
the type of the tests.
The issue is in the transform file {{nunit-to-junit.xsl}}.
Specifically, the cause is due to the {{firstTestName}} variable. The original
is:
{code:xml}
{code}
The "fixed" version is:
{code:xml}
{code}
This fixes my current issue, but I don't know if it introduces any new (or old)
issues.
I have attached an example nunit results file that will generate the error (one
of the 3 {{Inflector.OrdinalizeTests}} testsuites has the name {{Inflector}}
rather than {{Inflector.OrdinalizeTests}})
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13470) Violations Plugin supported type Pyflakes
[ https://issues.jenkins-ci.org/browse/JENKINS-13470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161671#comment-161671 ] cactusman commented on JENKINS-13470: - In my local, we respond to this feature. Please wait until commit. > Violations Plugin supported type Pyflakes > - > > Key: JENKINS-13470 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13470 > Project: Jenkins > Issue Type: New Feature > Components: violations >Reporter: cactusman >Assignee: cactusman > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13470) Violations Plugin supported type Pyflakes
[ https://issues.jenkins-ci.org/browse/JENKINS-13470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] cactusman updated JENKINS-13470: Assignee: cactusman (was: peterkittreilly) > Violations Plugin supported type Pyflakes > - > > Key: JENKINS-13470 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13470 > Project: Jenkins > Issue Type: New Feature > Components: violations >Reporter: cactusman >Assignee: cactusman > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13470) Violations Plugin supported type Pyflakes
cactusman created JENKINS-13470: --- Summary: Violations Plugin supported type Pyflakes Key: JENKINS-13470 URL: https://issues.jenkins-ci.org/browse/JENKINS-13470 Project: Jenkins Issue Type: New Feature Components: violations Reporter: cactusman Assignee: peterkittreilly -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10544) "shelve project" button missing on some projects
[ https://issues.jenkins-ci.org/browse/JENKINS-10544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161670#comment-161670 ] Kyle Leinen commented on JENKINS-10544: --- I am also seeing this on my Jenkins instance (v1.460) running RHEL. Is anyone looking into this? > "shelve project" button missing on some projects > > > Key: JENKINS-10544 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10544 > Project: Jenkins > Issue Type: Bug > Components: shelve-project-plugin >Reporter: Peter Pawlowski >Assignee: ashlux > Attachments: config.xml > > > With the Shelve Plugin version 1.2, on many Jenkins versions, we have seen > the "Shelve Project" button missing on some projects. > We haven't been able to see any pattern. Most of our projects are matrix > builds, and we've seen this issue on some matrix projects but not others. > I don't know what to look for or what other info we might provide to help > investigate this issue -- ask for anything and I'll do my best to provide it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13467) WARNING: Failed to advertise the service to DNS multi-cast
[ https://issues.jenkins-ci.org/browse/JENKINS-13467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161662#comment-161662 ] whren edited comment on JENKINS-13467 at 4/16/12 10:58 PM: --- Face the same issue with 1.459 and 1.460 on debian 6.0.4 x64, standalone : Launched with -Dhudson.DNSMultiCast.disabled=true KO on HTTP_HOST=debian-amd64-chef (which resolve to 127.0.0.1) OK on HTTP_HOST=0.0.0.0 Stacktrace : Apr 16, 2012 8:21:02 PM hudson.DNSMultiCast WARNING: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.(URL.java:617) at java.net.URL.(URL.java:480) at java.net.URL.(URL.java:429) at hudson.DNSMultiCast.(DNSMultiCast.java:45) at jenkins.model.Jenkins.(Jenkins.java:787) at hudson.model.Hudson.(Hudson.java:81) at hudson.model.Hudson.(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) Caused by: java.lang.NullPointerException at java.net.URL.(URL.java:522) ... 7 more Apr 16, 2012 8:21:02 PM hudson.WebAppMain$2 run INFO: Jenkins is fully up and running was (Author: whren): Face the same issue with 1.459 and 1.460 on debian 6.0.4 x64, standalone, no plugins, no auth : Launched with -Dhudson.DNSMultiCast.disabled=true OK on first run after fresh install, app accessible on http://ip:port KO on later runs, app not accessible on http://ip:port Stacktrace : Apr 16, 2012 8:21:02 PM hudson.DNSMultiCast WARNING: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.(URL.java:617) at java.net.URL.(URL.java:480) at java.net.URL.(URL.java:429) at hudson.DNSMultiCast.(DNSMultiCast.java:45) at jenkins.model.Jenkins.(Jenkins.java:787) at hudson.model.Hudson.(Hudson.java:81) at hudson.model.Hudson.(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) Caused by: java.lang.NullPointerException at java.net.URL.(URL.java:522) ... 7 more Apr 16, 2012 8:21:02 PM hudson.WebAppMain$2 run INFO: Jenkins is fully up and running > WARNING: Failed to advertise the service to DNS multi-cast > --- > > Key: JENKINS-13467 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13467 > Project: Jenkins > Issue Type: Bug > Components: jenkins-plugin-runtime >Affects Versions: current > Environment: Jenkins ver. 1.459 on Linux CentOS 6 >Reporter: Samuel Lopez >Assignee: Sami Tikka >Priority: Minor > > WARNING: Failed to advertise the service to DNS multi-cast > java.net.MalformedURLException > at java.net.URL.(URL.java:617) > at java.net.URL.(URL.java:480) > at java.net.URL.(URL.java:429) > at hudson.DNSMultiCast.(DNSMultiCast.java:45) > at jenkins.model.Jenkins.(Jenkins.java:787) > at hudson.model.Hudson.(Hudson.java:81) > at hudson.model.Hudson.(Hudson.java:77) > at hudson.WebAppMain$2.run(WebAppMain.java:217) > Caused by: java.lang.NullPointerException > at java.net.URL.(URL.java:522) > ... 7 more > Apr 13, 2012 12:25:26 AM hudson.WebAppMain$2 run > INFO: Jenkins is fully up and running -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12433) Publish Over CIFS Plugin - Interactive Help Not Displayed - "ERROR: Failed to load help file: Not Found"
[ https://issues.jenkins-ci.org/browse/JENKINS-12433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bap reassigned JENKINS-12433: - Assignee: bap (was: Slide-O-Mix) > Publish Over CIFS Plugin - Interactive Help Not Displayed - "ERROR: Failed to > load help file: Not Found" > > > Key: JENKINS-12433 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12433 > Project: Jenkins > Issue Type: Bug > Components: publish-over-cifs >Affects Versions: current > Environment: Jenkins ver. 1.424.2 > Tomcat Version: 7.0.23 > JVM Version: 1.7.0_02-b13 > OS: Windows Server 2008 R2 >Reporter: Dan Oster >Assignee: bap >Priority: Minor > Attachments: project_config__cifs_publishers.png, > system_config__cifs_shares.png, system_config__global_properties.png > > > Clicking any of the help "?" icons displays "ERROR: Failed to load help file: > Not Found". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13230) Not able to use Jenkins Environment Variables and variables injected through Env Inject plugin when executing commands over ssh in Publish over SSH plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161669#comment-161669 ] bap commented on JENKINS-13230: --- @gbois I was just explaining to Suresh why the variables were not restored - the publish over plugins would need to be "EnvInject aware" and have code written to specifically access the stored variables. Thanks for the code - but it is the publish over plugins that don't know how to read and restore the variables not me ;-) > Not able to use Jenkins Environment Variables and variables injected through > Env Inject plugin when executing commands over ssh in Publish over SSH plugin > -- > > Key: JENKINS-13230 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13230 > Project: Jenkins > Issue Type: Bug > Components: publish-over-ssh >Affects Versions: current > Environment: RHEL 5.5 >Reporter: suresh kukalakuntla >Assignee: bap > > I am trying to use Jenkins environment variables and variables injected > through Env Inject plugin in Execute section of 'Send build artifacts over > SSH'. It does not recognize them. It does recognize the build parameters and > replaces them with the values. When I look at the 'Injected environment > variables' I see all the variables I want to use. Not sure if I have to do > anything different to be able to use those variables. > In Job configuration I checked 'Prepare an environment for the run' and 'Keep > Jenkins Environment Variables', 'Keep Jenkins Build Variables'. > I have an 'Evaluated Groovy script' that sets 'MODULE_HOME' based on build > time parameter MODULE_NAME. > Please let me know how to proceed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13230) Not able to use Jenkins Environment Variables and variables injected through Env Inject plugin when executing commands over ssh in Publish over SSH plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161668#comment-161668 ] gbois commented on JENKINS-13230: - @bap EnvInject variables are build process environment variables, jenkins variables and build variables (parameterized, jenkins build variables, all contributions). publih-over-ssh has to be aware of EnvInject with the following code. * Get EnvInjetAction EnvInjectActionRetriever#getEnvInjectAction(build) * Get Environment variables in the EnvInjectAction EnvInjectAction#getEnvMap() * Use these variables to resolve your values > Not able to use Jenkins Environment Variables and variables injected through > Env Inject plugin when executing commands over ssh in Publish over SSH plugin > -- > > Key: JENKINS-13230 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13230 > Project: Jenkins > Issue Type: Bug > Components: publish-over-ssh >Affects Versions: current > Environment: RHEL 5.5 >Reporter: suresh kukalakuntla >Assignee: bap > > I am trying to use Jenkins environment variables and variables injected > through Env Inject plugin in Execute section of 'Send build artifacts over > SSH'. It does not recognize them. It does recognize the build parameters and > replaces them with the values. When I look at the 'Injected environment > variables' I see all the variables I want to use. Not sure if I have to do > anything different to be able to use those variables. > In Job configuration I checked 'Prepare an environment for the run' and 'Keep > Jenkins Environment Variables', 'Keep Jenkins Build Variables'. > I have an 'Evaluated Groovy script' that sets 'MODULE_HOME' based on build > time parameter MODULE_NAME. > Please let me know how to proceed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13315) Build Keeper plugin: support keeping all unstable, failing runs
[ https://issues.jenkins-ci.org/browse/JENKINS-13315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161667#comment-161667 ] SCM/JIRA link daemon commented on JENKINS-13315: Code changed in jenkins User: bap2000 Path: pom.xml src/main/java/org/jenkins_ci/plugins/build_keeper/RunConditionPolicy.java src/main/resources/org/jenkins_ci/plugins/build_keeper/Messages.properties src/main/resources/org/jenkins_ci/plugins/build_keeper/RunConditionPolicy/config.jelly src/main/resources/org/jenkins_ci/plugins/build_keeper/RunConditionPolicy/config.properties src/main/resources/org/jenkins_ci/plugins/build_keeper/RunConditionPolicy/help-keepBuildIfEvalFails.html src/main/resources/org/jenkins_ci/plugins/build_keeper/RunConditionPolicy/help-runCondition.jelly http://jenkins-ci.org/commit/build-keeper-plugin/a75b6ea76f9f29a8529820f8bf386a5af7876e56 Log: Add a policy that evaluates RunConditions [FIXED JENKINS-13315] (Use "Current build status" with Best set to Unstable and Worst set to Failed ... or Pending or Aborted) > Build Keeper plugin: support keeping all unstable, failing runs > --- > > Key: JENKINS-13315 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13315 > Project: Jenkins > Issue Type: Improvement > Components: build-keeper-plugin >Affects Versions: current >Reporter: Steve Roth >Assignee: bap >Priority: Minor > > First off, thanks for this very helpful plugin. > I use this plugin to monitor for systemic stability issues and keep the > relevant build artifacts when issues are found. Then when I have time, I > review these artifacts and identify the most common issues. > One feature which would really help this use-case, which I think may be a > minor change, would be to add > 'keep all unstable and failing builds'. > There may also be use-cases for: > 'keep all unstable builds'. > 'keep all failing builds'. > But for our particular case, we'd ideally want to be able to use 'keep all > unstable and failing builds'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13315) Build Keeper plugin: support keeping all unstable, failing runs
[ https://issues.jenkins-ci.org/browse/JENKINS-13315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13315. Resolution: Fixed > Build Keeper plugin: support keeping all unstable, failing runs > --- > > Key: JENKINS-13315 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13315 > Project: Jenkins > Issue Type: Improvement > Components: build-keeper-plugin >Affects Versions: current >Reporter: Steve Roth >Assignee: bap >Priority: Minor > > First off, thanks for this very helpful plugin. > I use this plugin to monitor for systemic stability issues and keep the > relevant build artifacts when issues are found. Then when I have time, I > review these artifacts and identify the most common issues. > One feature which would really help this use-case, which I think may be a > minor change, would be to add > 'keep all unstable and failing builds'. > There may also be use-cases for: > 'keep all unstable builds'. > 'keep all failing builds'. > But for our particular case, we'd ideally want to be able to use 'keep all > unstable and failing builds'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13469) Prototype.Selector is undefined
James Lee created JENKINS-13469: --- Summary: Prototype.Selector is undefined Key: JENKINS-13469 URL: https://issues.jenkins-ci.org/browse/JENKINS-13469 Project: Jenkins Issue Type: Bug Components: conditional-buildstep Affects Versions: current Environment: IE 8, IE 9, Firefox 11. Reporter: James Lee Assignee: domi Priority: Blocker Try to add 2 or more conditional steps, without success. Can only add 1. Firefox error console showed the following: Prototype.Selector is undefined Source File: http://localhost/static/c5afde5e/scripts/behavior.js Line: 132 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13387) Convert "Delete this build" buttons into links in the sidepanel
[ https://issues.jenkins-ci.org/browse/JENKINS-13387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161666#comment-161666 ] dogfood commented on JENKINS-13387: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_main_trunk #1665|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1665/] [FIXED JENKINS-13387] Converted "Delete this build" buttons into links in the sidepanel, added (Revision be88e0120fef6d5837ef9adf9b7803cbdde88b30) Result = SUCCESS Fred G : [be88e0120fef6d5837ef9adf9b7803cbdde88b30|https://github.com/jenkinsci/jenkins/commit/be88e0120fef6d5837ef9adf9b7803cbdde88b30] Files : * core/src/main/resources/hudson/model/AbstractBuild/index.jelly * core/src/main/resources/hudson/matrix/MatrixBuild/delete_ja.properties * core/src/main/resources/hudson/model/Run/delete.jelly * core/src/main/resources/hudson/model/Run/delete.properties * core/src/main/resources/hudson/matrix/MatrixBuild/delete.jelly * core/src/main/resources/hudson/model/AbstractBuild/sidepanel.jelly * core/src/main/resources/hudson/matrix/MatrixBuild/delete_de.properties * core/src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll_de.properties > Convert "Delete this build" buttons into links in the sidepanel > --- > > Key: JENKINS-13387 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13387 > Project: Jenkins > Issue Type: Improvement > Components: gui, ui-changes >Reporter: Fred G >Assignee: Fred G > Labels: gui > Attachments: DeleteBuildButtons_MatrixBuild.png, > DeleteBuildButtons_MatrixConfig.png, DeleteBuildLinks_MatrixBuild.png, > DeleteBuildLinks_MatrixConfig.png > > > The "Delete this build" buttons on build pages and also the "Delete this > build and all configurations of this build" buttons on matrix build pages > should be converted to links in the sidepanel of the respective pages (see > Screenshots). > This simplifies the user experience of deleting an object (see the "Delete > Project" link in the sidepanel of project pages). > Having the links in the sidepanel also makes them accessible through the > newly added context menus that came with the breadcrumbs. > Recent discussion about this topic: > https://github.com/jenkinsci/jenkins/pull/403 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13389) Move "View as plain text" link on console output page from top right to the sidepanel.
[ https://issues.jenkins-ci.org/browse/JENKINS-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161665#comment-161665 ] dogfood commented on JENKINS-13389: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_main_trunk #1665|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1665/] [FIXED JENKINS-13389] Moved "View as plain text" link on console output page from top right to (Revision 7681ab09828251640d2ca1508eef1027fb8afa9c) Result = SUCCESS Fred G : [7681ab09828251640d2ca1508eef1027fb8afa9c|https://github.com/jenkinsci/jenkins/commit/7681ab09828251640d2ca1508eef1027fb8afa9c] Files : * core/src/main/resources/hudson/model/Run/console_ko.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_pl.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_lv.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_lt.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_ca.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_fr.properties * core/src/main/resources/hudson/model/Run/console.jelly * core/src/main/resources/hudson/model/Run/console_tr.properties * core/src/main/resources/hudson/model/Run/console_sk.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_he.properties * core/src/main/resources/hudson/model/Run/console_fr.properties * core/src/main/resources/hudson/model/Run/console_de.properties * core/src/main/resources/hudson/model/Run/console_fi.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_zh_TW.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_ko.properties * core/src/main/resources/hudson/model/Run/console_lt.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_hi_IN.properties * core/src/main/resources/hudson/model/Run/console_hi_IN.properties * core/src/main/resources/hudson/model/Run/console_zh_TW.properties * core/src/main/resources/hudson/model/Run/console_zh_CN.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_tr.properties * core/src/main/resources/hudson/model/Run/console_ca.properties * core/src/main/resources/hudson/model/Run/console_nb_NO.properties * core/src/main/resources/hudson/model/Run/console_is.properties * core/src/main/resources/hudson/model/Run/console_pt_PT.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_it.properties * core/src/main/resources/hudson/model/Run/console_nl.properties * core/src/main/resources/hudson/model/Run/console_uk.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_es.properties * core/src/main/resources/hudson/model/Run/console_bg.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_pt_PT.properties * core/src/main/resources/hudson/model/Run/console_da.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_el.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_sk.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_eo.properties * core/src/main/resources/hudson/model/Run/console_eo.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_fi.properties * core/src/main/resources/hudson/model/Run/console_es.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_sv_SE.properties * core/src/main/resources/hudson/model/Run/console_pl.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_ja.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_de.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks.jelly * core/src/main/resources/hudson/model/AbstractBuild/tasks_nb_NO.properties * core/src/main/resources/hudson/model/Run/console_cs.properties * core/src/main/resources/hudson/model/Run/console_it.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_ro.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_ru.properties * core/src/main/resources/hudson/model/Run/console_hu.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_pt_BR.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_cs.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_da.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_bg.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_zh_CN.properties * core/src/main/resources/hudson/model/Run/console_ru.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_nl.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_hu.properties * core/src/main/resources/hudson/model/Run/console_sv_SE.properties * core/src/main/resources/hudson/model/AbstractBuild/tasks_is.properties * core/src/main/resources/hudson/model/Run/console_he.properties * core/src/main/resources/hudson/model/Run/console_ro.properties * core/src/main/resources/hudson/model/Ru
[JIRA] (JENKINS-13454) Optimize the plugin manager
[ https://issues.jenkins-ci.org/browse/JENKINS-13454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161664#comment-161664 ] dogfood commented on JENKINS-13454: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_main_trunk #1665|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1665/] [FIXED JENKINS-13454] Optimize the plugin manager (Revision e465f7202e42b0cb196e98c2e21abedcb85e60d4) Result = SUCCESS unknown : [e465f7202e42b0cb196e98c2e21abedcb85e60d4|https://github.com/jenkinsci/jenkins/commit/e465f7202e42b0cb196e98c2e21abedcb85e60d4] Files : * core/src/main/java/hudson/model/UpdateSite.java > Optimize the plugin manager > --- > > Key: JENKINS-13454 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13454 > Project: Jenkins > Issue Type: Improvement > Components: update-center > Environment: Jenkins 1.459, Oracle JDK 1.7, Windows XP >Reporter: evernat >Assignee: evernat > Attachments: monitoring.png > > > In "Manage Jenkins", the plugin manager (aka update center) is rather slow. > Slow is about 3 to 6 seconds on my windows laptop. > The http requests of the plugin manager are mostly the slowest of all, as can > be seen in the joined screenshot of the monitoring plugin. > The screenshot also shows that those http requests have a high cpu usage. > The cause of the issue is that for each plugin, the > UpdateSite.getPlugin(String) and getData() methods read and parse all the > plugins data from the "updates/default.json" file each time. > So the more plugins are available, the slower it is. > I will submit a pull request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13463) Upgraded to 1.21 and now cannot copy from Matrix Builds
[ https://issues.jenkins-ci.org/browse/JENKINS-13463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161663#comment-161663 ] Paul Wakefield commented on JENKINS-13463: -- Unfortunatley I cant be 100% sure, I think it was 1.20. I have another instance working fine at 1.18. I would have to look back through our backup logs to try and be certain. Ive just tried a roll back of the jenkins version to eliminate that without success, just gone back to 1.447. > Upgraded to 1.21 and now cannot copy from Matrix Builds > --- > > Key: JENKINS-13463 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13463 > Project: Jenkins > Issue Type: Bug > Components: copyartifact >Affects Versions: current > Environment: openSUSE 11.2 >Reporter: Paul Wakefield >Assignee: Alan Harder >Priority: Blocker > > Everything was working fine, updated copyartifact to latest and now get the > following: > Unable to find project for artifact copy: > LiDCOHostingSDK/platform=QNX,release=debug > This may be due to incorrect project name or permission settings; see help > for project name in job configuration. > Build step 'Copy artifacts from another project' marked build as failure > No Configuration changes. > Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13467) WARNING: Failed to advertise the service to DNS multi-cast
[ https://issues.jenkins-ci.org/browse/JENKINS-13467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161662#comment-161662 ] whren edited comment on JENKINS-13467 at 4/16/12 8:30 PM: -- Face the same issue with 1.459 and 1.460 on debian 6.0.4 x64, standalone, no plugins, no auth : Launched with -Dhudson.DNSMultiCast.disabled=true OK on first run after fresh install, app accessible on http://ip:port KO on later runs, app not accessible on http://ip:port Stacktrace : Apr 16, 2012 8:21:02 PM hudson.DNSMultiCast WARNING: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.(URL.java:617) at java.net.URL.(URL.java:480) at java.net.URL.(URL.java:429) at hudson.DNSMultiCast.(DNSMultiCast.java:45) at jenkins.model.Jenkins.(Jenkins.java:787) at hudson.model.Hudson.(Hudson.java:81) at hudson.model.Hudson.(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) Caused by: java.lang.NullPointerException at java.net.URL.(URL.java:522) ... 7 more Apr 16, 2012 8:21:02 PM hudson.WebAppMain$2 run INFO: Jenkins is fully up and running was (Author: whren): Face the same issue with 1.459 and 1.460 on debian 6.0.4 x64 : Launched with -Dhudson.DNSMultiCast.disabled=true OK on first run after fresh install KO on later runs Stacktrace : Apr 16, 2012 8:21:02 PM hudson.DNSMultiCast WARNING: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.(URL.java:617) at java.net.URL.(URL.java:480) at java.net.URL.(URL.java:429) at hudson.DNSMultiCast.(DNSMultiCast.java:45) at jenkins.model.Jenkins.(Jenkins.java:787) at hudson.model.Hudson.(Hudson.java:81) at hudson.model.Hudson.(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) Caused by: java.lang.NullPointerException at java.net.URL.(URL.java:522) ... 7 more Apr 16, 2012 8:21:02 PM hudson.WebAppMain$2 run INFO: Jenkins is fully up and running > WARNING: Failed to advertise the service to DNS multi-cast > --- > > Key: JENKINS-13467 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13467 > Project: Jenkins > Issue Type: Bug > Components: jenkins-plugin-runtime >Affects Versions: current > Environment: Jenkins ver. 1.459 on Linux CentOS 6 >Reporter: Samuel Lopez >Assignee: Sami Tikka >Priority: Minor > > WARNING: Failed to advertise the service to DNS multi-cast > java.net.MalformedURLException > at java.net.URL.(URL.java:617) > at java.net.URL.(URL.java:480) > at java.net.URL.(URL.java:429) > at hudson.DNSMultiCast.(DNSMultiCast.java:45) > at jenkins.model.Jenkins.(Jenkins.java:787) > at hudson.model.Hudson.(Hudson.java:81) > at hudson.model.Hudson.(Hudson.java:77) > at hudson.WebAppMain$2.run(WebAppMain.java:217) > Caused by: java.lang.NullPointerException > at java.net.URL.(URL.java:522) > ... 7 more > Apr 13, 2012 12:25:26 AM hudson.WebAppMain$2 run > INFO: Jenkins is fully up and running -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13467) WARNING: Failed to advertise the service to DNS multi-cast
[ https://issues.jenkins-ci.org/browse/JENKINS-13467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161662#comment-161662 ] whren commented on JENKINS-13467: - Face the same issue with 1.459 and 1.460 on debian 6.0.4 x64 : Launched with -Dhudson.DNSMultiCast.disabled=true OK on first run after fresh install KO on later runs Stacktrace : Apr 16, 2012 8:21:02 PM hudson.DNSMultiCast WARNING: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.(URL.java:617) at java.net.URL.(URL.java:480) at java.net.URL.(URL.java:429) at hudson.DNSMultiCast.(DNSMultiCast.java:45) at jenkins.model.Jenkins.(Jenkins.java:787) at hudson.model.Hudson.(Hudson.java:81) at hudson.model.Hudson.(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) Caused by: java.lang.NullPointerException at java.net.URL.(URL.java:522) ... 7 more Apr 16, 2012 8:21:02 PM hudson.WebAppMain$2 run INFO: Jenkins is fully up and running > WARNING: Failed to advertise the service to DNS multi-cast > --- > > Key: JENKINS-13467 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13467 > Project: Jenkins > Issue Type: Bug > Components: jenkins-plugin-runtime >Affects Versions: current > Environment: Jenkins ver. 1.459 on Linux CentOS 6 >Reporter: Samuel Lopez >Assignee: Sami Tikka >Priority: Minor > > WARNING: Failed to advertise the service to DNS multi-cast > java.net.MalformedURLException > at java.net.URL.(URL.java:617) > at java.net.URL.(URL.java:480) > at java.net.URL.(URL.java:429) > at hudson.DNSMultiCast.(DNSMultiCast.java:45) > at jenkins.model.Jenkins.(Jenkins.java:787) > at hudson.model.Hudson.(Hudson.java:81) > at hudson.model.Hudson.(Hudson.java:77) > at hudson.WebAppMain$2.run(WebAppMain.java:217) > Caused by: java.lang.NullPointerException > at java.net.URL.(URL.java:522) > ... 7 more > Apr 13, 2012 12:25:26 AM hudson.WebAppMain$2 run > INFO: Jenkins is fully up and running -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13468) Would like to create/use a central "catalog" . . .
Frank Merrow created JENKINS-13468: -- Summary: Would like to create/use a central "catalog" . . . Key: JENKINS-13468 URL: https://issues.jenkins-ci.org/browse/JENKINS-13468 Project: Jenkins Issue Type: New Feature Components: scriptler Environment: Windows . . . Reporter: Frank Merrow Assignee: domi We have a large and growing number of Jenkins instances . . . We don't have many Groovy script, but rather than carrying them around by hand, it would be nice to be able to put them in once place (network share for instance) and access them from any Jenkins. Note this isn't exactly like your public repositories, because I don't want to have to import them . . . while certain scripts might be local to a given Jenkins, for the global Jenkins script . . . if they are changed in one Jenkins, I would like that update to appear for all Jenkins attached to the repository. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13389) Move "View as plain text" link on console output page from top right to the sidepanel.
[ https://issues.jenkins-ci.org/browse/JENKINS-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13389. Resolution: Fixed > Move "View as plain text" link on console output page from top right to the > sidepanel. > -- > > Key: JENKINS-13389 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13389 > Project: Jenkins > Issue Type: Improvement > Components: gui, ui-changes >Reporter: Fred G >Assignee: Fred G >Priority: Minor > Labels: gui > Attachments: ViewAsPlainText_Link.png > > > To clean up the Jenkins UI, all "actions" should be links in the sidepanel > menu on the left side of the screen. > The "View as plain text" link that appears on the top right corner of the > console output page should be > moved to the sidepanel (see screenshot). > The link should only appear when the console output page is shown (similiar > to the "Wipe out workspace"-link > which only appears when the workspace is selected). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13389) Move "View as plain text" link on console output page from top right to the sidepanel.
[ https://issues.jenkins-ci.org/browse/JENKINS-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161661#comment-161661 ] SCM/JIRA link daemon commented on JENKINS-13389: Code changed in jenkins User: Andrew Bayer Path: core/src/main/resources/hudson/model/AbstractBuild/tasks.jelly core/src/main/resources/hudson/model/AbstractBuild/tasks_bg.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_ca.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_cs.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_da.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_de.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_el.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_eo.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_es.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_fi.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_fr.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_he.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_hi_IN.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_hu.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_is.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_it.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_ja.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_ko.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_lt.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_lv.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_nb_NO.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_nl.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_pl.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_pt_BR.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_pt_PT.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_ro.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_ru.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_sk.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_sv_SE.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_tr.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_uk.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_zh_CN.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_zh_TW.properties core/src/main/resources/hudson/model/Run/console.jelly core/src/main/resources/hudson/model/Run/console_bg.properties core/src/main/resources/hudson/model/Run/console_ca.properties core/src/main/resources/hudson/model/Run/console_cs.properties core/src/main/resources/hudson/model/Run/console_da.properties core/src/main/resources/hudson/model/Run/console_de.properties core/src/main/resources/hudson/model/Run/console_el.properties core/src/main/resources/hudson/model/Run/console_eo.properties core/src/main/resources/hudson/model/Run/console_es.properties core/src/main/resources/hudson/model/Run/console_fi.properties core/src/main/resources/hudson/model/Run/console_fr.properties core/src/main/resources/hudson/model/Run/console_he.properties core/src/main/resources/hudson/model/Run/console_hi_IN.properties core/src/main/resources/hudson/model/Run/console_hu.properties core/src/main/resources/hudson/model/Run/console_is.properties core/src/main/resources/hudson/model/Run/console_it.properties core/src/main/resources/hudson/model/Run/console_ja.properties core/src/main/resources/hudson/model/Run/console_ko.properties core/src/main/resources/hudson/model/Run/console_lt.properties core/src/main/resources/hudson/model/Run/console_lv.properties core/src/main/resources/hudson/model/Run/console_nb_NO.properties core/src/main/resources/hudson/model/Run/console_nl.properties core/src/main/resources/hudson/model/Run/console_pl.properties core/src/main/resources/hudson/model/Run/console_pt_BR.properties core/src/main/resources/hudson/model/Run/console_pt_PT.properties core/src/main/resources/hudson/model/Run/console_ro.properties core/src/main/resources/hudson/model/Run/console_ru.properties core/src/main/resources/hudson/model/Run/console_sk.properties core/src/main/resources/hudson/model/Run/console_sv_SE.properties core/src/main/resources/hudson/model/Run/console_tr.properties core/src/main/resources/hudson/model/Run/console_uk.properties core/src/main/resources/hudson/model/Run/console_zh_CN.properties core/src/main/resources/hudson/model/Run/console_zh_TW.properties http://jenkins-ci.org/commit/jenkins/246be7caeb79ca3d276852e7bee5aff4abb5 Log: Merge pull request #432 from fredg02/consolePageLink [FIXED JENKINS-13389] Mov
[JIRA] (JENKINS-13389) Move "View as plain text" link on console output page from top right to the sidepanel.
[ https://issues.jenkins-ci.org/browse/JENKINS-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161660#comment-161660 ] SCM/JIRA link daemon commented on JENKINS-13389: Code changed in jenkins User: Fred G Path: core/src/main/resources/hudson/model/AbstractBuild/tasks.jelly core/src/main/resources/hudson/model/AbstractBuild/tasks_bg.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_ca.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_cs.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_da.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_de.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_el.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_eo.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_es.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_fi.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_fr.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_he.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_hi_IN.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_hu.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_is.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_it.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_ja.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_ko.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_lt.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_lv.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_nb_NO.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_nl.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_pl.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_pt_BR.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_pt_PT.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_ro.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_ru.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_sk.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_sv_SE.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_tr.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_uk.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_zh_CN.properties core/src/main/resources/hudson/model/AbstractBuild/tasks_zh_TW.properties core/src/main/resources/hudson/model/Run/console.jelly core/src/main/resources/hudson/model/Run/console_bg.properties core/src/main/resources/hudson/model/Run/console_ca.properties core/src/main/resources/hudson/model/Run/console_cs.properties core/src/main/resources/hudson/model/Run/console_da.properties core/src/main/resources/hudson/model/Run/console_de.properties core/src/main/resources/hudson/model/Run/console_el.properties core/src/main/resources/hudson/model/Run/console_eo.properties core/src/main/resources/hudson/model/Run/console_es.properties core/src/main/resources/hudson/model/Run/console_fi.properties core/src/main/resources/hudson/model/Run/console_fr.properties core/src/main/resources/hudson/model/Run/console_he.properties core/src/main/resources/hudson/model/Run/console_hi_IN.properties core/src/main/resources/hudson/model/Run/console_hu.properties core/src/main/resources/hudson/model/Run/console_is.properties core/src/main/resources/hudson/model/Run/console_it.properties core/src/main/resources/hudson/model/Run/console_ja.properties core/src/main/resources/hudson/model/Run/console_ko.properties core/src/main/resources/hudson/model/Run/console_lt.properties core/src/main/resources/hudson/model/Run/console_lv.properties core/src/main/resources/hudson/model/Run/console_nb_NO.properties core/src/main/resources/hudson/model/Run/console_nl.properties core/src/main/resources/hudson/model/Run/console_pl.properties core/src/main/resources/hudson/model/Run/console_pt_BR.properties core/src/main/resources/hudson/model/Run/console_pt_PT.properties core/src/main/resources/hudson/model/Run/console_ro.properties core/src/main/resources/hudson/model/Run/console_ru.properties core/src/main/resources/hudson/model/Run/console_sk.properties core/src/main/resources/hudson/model/Run/console_sv_SE.properties core/src/main/resources/hudson/model/Run/console_tr.properties core/src/main/resources/hudson/model/Run/console_uk.properties core/src/main/resources/hudson/model/Run/console_zh_CN.properties core/src/main/resources/hudson/model/Run/console_zh_TW.properties http://jenkins-ci.org/commit/jenkins/7681ab09828251640d2ca1508eef1027fb8afa9c Log: [FIXED JENKINS-13389] Moved "View as plain text" link on console output page from to
[JIRA] (JENKINS-13454) Optimize the plugin manager
[ https://issues.jenkins-ci.org/browse/JENKINS-13454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161659#comment-161659 ] SCM/JIRA link daemon commented on JENKINS-13454: Code changed in jenkins User: Andrew Bayer Path: core/src/main/java/hudson/model/UpdateSite.java http://jenkins-ci.org/commit/jenkins/ca3ad78017f64c6f3fec10dd9ba335ff770b57f3 Log: Merge pull request #441 from evernat/master [FIXED JENKINS-13454] Optimize the plugin manager Compare: https://github.com/jenkinsci/jenkins/compare/37fbcf4...ca3ad78 > Optimize the plugin manager > --- > > Key: JENKINS-13454 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13454 > Project: Jenkins > Issue Type: Improvement > Components: update-center > Environment: Jenkins 1.459, Oracle JDK 1.7, Windows XP >Reporter: evernat >Assignee: evernat > Attachments: monitoring.png > > > In "Manage Jenkins", the plugin manager (aka update center) is rather slow. > Slow is about 3 to 6 seconds on my windows laptop. > The http requests of the plugin manager are mostly the slowest of all, as can > be seen in the joined screenshot of the monitoring plugin. > The screenshot also shows that those http requests have a high cpu usage. > The cause of the issue is that for each plugin, the > UpdateSite.getPlugin(String) and getData() methods read and parse all the > plugins data from the "updates/default.json" file each time. > So the more plugins are available, the slower it is. > I will submit a pull request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13454) Optimize the plugin manager
[ https://issues.jenkins-ci.org/browse/JENKINS-13454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13454. Resolution: Fixed > Optimize the plugin manager > --- > > Key: JENKINS-13454 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13454 > Project: Jenkins > Issue Type: Improvement > Components: update-center > Environment: Jenkins 1.459, Oracle JDK 1.7, Windows XP >Reporter: evernat >Assignee: evernat > Attachments: monitoring.png > > > In "Manage Jenkins", the plugin manager (aka update center) is rather slow. > Slow is about 3 to 6 seconds on my windows laptop. > The http requests of the plugin manager are mostly the slowest of all, as can > be seen in the joined screenshot of the monitoring plugin. > The screenshot also shows that those http requests have a high cpu usage. > The cause of the issue is that for each plugin, the > UpdateSite.getPlugin(String) and getData() methods read and parse all the > plugins data from the "updates/default.json" file each time. > So the more plugins are available, the slower it is. > I will submit a pull request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13387) Convert "Delete this build" buttons into links in the sidepanel
[ https://issues.jenkins-ci.org/browse/JENKINS-13387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161656#comment-161656 ] SCM/JIRA link daemon commented on JENKINS-13387: Code changed in jenkins User: Fred G Path: core/src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll_de.properties core/src/main/resources/hudson/matrix/MatrixBuild/delete.jelly core/src/main/resources/hudson/matrix/MatrixBuild/delete_de.properties core/src/main/resources/hudson/matrix/MatrixBuild/delete_ja.properties core/src/main/resources/hudson/model/AbstractBuild/index.jelly core/src/main/resources/hudson/model/AbstractBuild/sidepanel.jelly core/src/main/resources/hudson/model/Run/delete.jelly core/src/main/resources/hudson/model/Run/delete.properties http://jenkins-ci.org/commit/jenkins/be88e0120fef6d5837ef9adf9b7803cbdde88b30 Log: [FIXED JENKINS-13387] Converted "Delete this build" buttons into links in the sidepanel, added German translations for "Delete Build" links in Matrix Builds > Convert "Delete this build" buttons into links in the sidepanel > --- > > Key: JENKINS-13387 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13387 > Project: Jenkins > Issue Type: Improvement > Components: gui, ui-changes >Reporter: Fred G >Assignee: Fred G > Labels: gui > Attachments: DeleteBuildButtons_MatrixBuild.png, > DeleteBuildButtons_MatrixConfig.png, DeleteBuildLinks_MatrixBuild.png, > DeleteBuildLinks_MatrixConfig.png > > > The "Delete this build" buttons on build pages and also the "Delete this > build and all configurations of this build" buttons on matrix build pages > should be converted to links in the sidepanel of the respective pages (see > Screenshots). > This simplifies the user experience of deleting an object (see the "Delete > Project" link in the sidepanel of project pages). > Having the links in the sidepanel also makes them accessible through the > newly added context menus that came with the breadcrumbs. > Recent discussion about this topic: > https://github.com/jenkinsci/jenkins/pull/403 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13387) Convert "Delete this build" buttons into links in the sidepanel
[ https://issues.jenkins-ci.org/browse/JENKINS-13387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161657#comment-161657 ] SCM/JIRA link daemon commented on JENKINS-13387: Code changed in jenkins User: Andrew Bayer Path: core/src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll_de.properties core/src/main/resources/hudson/matrix/MatrixBuild/delete.jelly core/src/main/resources/hudson/matrix/MatrixBuild/delete_de.properties core/src/main/resources/hudson/matrix/MatrixBuild/delete_ja.properties core/src/main/resources/hudson/model/AbstractBuild/index.jelly core/src/main/resources/hudson/model/AbstractBuild/sidepanel.jelly core/src/main/resources/hudson/model/Run/delete.jelly core/src/main/resources/hudson/model/Run/delete.properties http://jenkins-ci.org/commit/jenkins/37fbcf4da2926f95098044f3abf5fff7707a806c Log: Merge pull request #431 from fredg02/convertLinks [FIXED JENKINS-13387] Converted "Delete this build" buttons into links in the sidepanel Compare: https://github.com/jenkinsci/jenkins/compare/32e798d...37fbcf4 > Convert "Delete this build" buttons into links in the sidepanel > --- > > Key: JENKINS-13387 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13387 > Project: Jenkins > Issue Type: Improvement > Components: gui, ui-changes >Reporter: Fred G >Assignee: Fred G > Labels: gui > Attachments: DeleteBuildButtons_MatrixBuild.png, > DeleteBuildButtons_MatrixConfig.png, DeleteBuildLinks_MatrixBuild.png, > DeleteBuildLinks_MatrixConfig.png > > > The "Delete this build" buttons on build pages and also the "Delete this > build and all configurations of this build" buttons on matrix build pages > should be converted to links in the sidepanel of the respective pages (see > Screenshots). > This simplifies the user experience of deleting an object (see the "Delete > Project" link in the sidepanel of project pages). > Having the links in the sidepanel also makes them accessible through the > newly added context menus that came with the breadcrumbs. > Recent discussion about this topic: > https://github.com/jenkinsci/jenkins/pull/403 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13454) Optimize the plugin manager
[ https://issues.jenkins-ci.org/browse/JENKINS-13454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161658#comment-161658 ] SCM/JIRA link daemon commented on JENKINS-13454: Code changed in jenkins User: unknown Path: core/src/main/java/hudson/model/UpdateSite.java http://jenkins-ci.org/commit/jenkins/e465f7202e42b0cb196e98c2e21abedcb85e60d4 Log: [FIXED JENKINS-13454] Optimize the plugin manager > Optimize the plugin manager > --- > > Key: JENKINS-13454 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13454 > Project: Jenkins > Issue Type: Improvement > Components: update-center > Environment: Jenkins 1.459, Oracle JDK 1.7, Windows XP >Reporter: evernat >Assignee: evernat > Attachments: monitoring.png > > > In "Manage Jenkins", the plugin manager (aka update center) is rather slow. > Slow is about 3 to 6 seconds on my windows laptop. > The http requests of the plugin manager are mostly the slowest of all, as can > be seen in the joined screenshot of the monitoring plugin. > The screenshot also shows that those http requests have a high cpu usage. > The cause of the issue is that for each plugin, the > UpdateSite.getPlugin(String) and getData() methods read and parse all the > plugins data from the "updates/default.json" file each time. > So the more plugins are available, the slower it is. > I will submit a pull request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13387) Convert "Delete this build" buttons into links in the sidepanel
[ https://issues.jenkins-ci.org/browse/JENKINS-13387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13387. Resolution: Fixed > Convert "Delete this build" buttons into links in the sidepanel > --- > > Key: JENKINS-13387 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13387 > Project: Jenkins > Issue Type: Improvement > Components: gui, ui-changes >Reporter: Fred G >Assignee: Fred G > Labels: gui > Attachments: DeleteBuildButtons_MatrixBuild.png, > DeleteBuildButtons_MatrixConfig.png, DeleteBuildLinks_MatrixBuild.png, > DeleteBuildLinks_MatrixConfig.png > > > The "Delete this build" buttons on build pages and also the "Delete this > build and all configurations of this build" buttons on matrix build pages > should be converted to links in the sidepanel of the respective pages (see > Screenshots). > This simplifies the user experience of deleting an object (see the "Delete > Project" link in the sidepanel of project pages). > Having the links in the sidepanel also makes them accessible through the > newly added context menus that came with the breadcrumbs. > Recent discussion about this topic: > https://github.com/jenkinsci/jenkins/pull/403 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13460) Environment variables not explanded for "Remote Directory" configuration
[
https://issues.jenkins-ci.org/browse/JENKINS-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161655#comment-161655
]
bap commented on JENKINS-13460:
---
The Remote directory configured in the global configuration (Manage Jenkins)
does not support variable substitution.
The Remote directory in a job configuration does.
You should be able to set the global Remote directory to / and then use the
variable in the job configuration (where Exec command is configured)
> Environment variables not explanded for "Remote Directory" configuration
>
>
> Key: JENKINS-13460
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13460
> Project: Jenkins
> Issue Type: Bug
> Components: publish-over-ssh
>Reporter: Bertrand Latinville
>Assignee: bap
>Priority: Minor
> Labels: deployment, plugin
>
> I'm using publish over ssh to send file on a remote folder
> and Exec commands.
> As the folder where I put the files may change in the future I defined a
> Jenkins environment variable: REMOTE_LOCATION.
> I'd like to use this variable in SSH publish over configuration and in the
> Exec command of the job.
> I configured ssh publish over plugin with Remote Directory set to
> ${REMOTE_LOCATION}
> I get this error :
> ERROR: Exception when publishing, exception message [Failed to change to
> remote directory [${REMOTE_LOCATION}]]
> Build step 'Send build artifacts over SSH' changed build result to UNSTABLE
> I checked that the variable is set properly by echo ${REMOTE_LOCATION} in the
> Exec command.
> Variables should be expanded in the "Remote Directory" configuration field.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13230) Not able to use Jenkins Environment Variables and variables injected through Env Inject plugin when executing commands over ssh in Publish over SSH plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161654#comment-161654 ] bap commented on JENKINS-13230: --- All environment variables are restored - the variables that envInject provides are build variables, not environment variables. The publish over plugins are not aware of the EnvInject plugin, so do not know how to read and restore the variables that it had added to a build. > Not able to use Jenkins Environment Variables and variables injected through > Env Inject plugin when executing commands over ssh in Publish over SSH plugin > -- > > Key: JENKINS-13230 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13230 > Project: Jenkins > Issue Type: Bug > Components: publish-over-ssh >Affects Versions: current > Environment: RHEL 5.5 >Reporter: suresh kukalakuntla >Assignee: bap > > I am trying to use Jenkins environment variables and variables injected > through Env Inject plugin in Execute section of 'Send build artifacts over > SSH'. It does not recognize them. It does recognize the build parameters and > replaces them with the values. When I look at the 'Injected environment > variables' I see all the variables I want to use. Not sure if I have to do > anything different to be able to use those variables. > In Job configuration I checked 'Prepare an environment for the run' and 'Keep > Jenkins Environment Variables', 'Keep Jenkins Build Variables'. > I have an 'Evaluated Groovy script' that sets 'MODULE_HOME' based on build > time parameter MODULE_NAME. > Please let me know how to proceed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13143) Can't connect on host using a port greater than 999
[ https://issues.jenkins-ci.org/browse/JENKINS-13143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bap closed JENKINS-13143. - Please re-open if you can connect to an ssh service running on port 999, but not when you change the port to 1000. > Can't connect on host using a port greater than 999 > --- > > Key: JENKINS-13143 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13143 > Project: Jenkins > Issue Type: Bug > Components: publish-over-ssh >Reporter: Frédéric Camblor >Assignee: bap >Priority: Critical > > I configured publish-over-ssh plugin (v1.6) on my current jenkins, with port > 2232, and it fails to connect. > Using port 22 (on another host) works fine though. > When I use verbose mode on the plugin, I have : > SSH: Connecting from host [jenkins-slave-ubuntu3] > SSH: Connecting with configuration [XXX nightly] ... > SSH: Creating session: username [xxx], hostname [X.X.X.X], port [2,232] > SSH: Connecting session ... > ERROR: Exception when publishing, exception message [Failed to connect > session for config [XXX nightly]. Message [java.net.ConnectException: > Connection refused]] > I think the "2,232" is the cause of the problem :-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13143) Can't connect on host using a port greater than 999
[ https://issues.jenkins-ci.org/browse/JENKINS-13143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bap resolved JENKINS-13143. --- Resolution: Cannot Reproduce > Can't connect on host using a port greater than 999 > --- > > Key: JENKINS-13143 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13143 > Project: Jenkins > Issue Type: Bug > Components: publish-over-ssh >Reporter: Frédéric Camblor >Assignee: bap >Priority: Critical > > I configured publish-over-ssh plugin (v1.6) on my current jenkins, with port > 2232, and it fails to connect. > Using port 22 (on another host) works fine though. > When I use verbose mode on the plugin, I have : > SSH: Connecting from host [jenkins-slave-ubuntu3] > SSH: Connecting with configuration [XXX nightly] ... > SSH: Creating session: username [xxx], hostname [X.X.X.X], port [2,232] > SSH: Connecting session ... > ERROR: Exception when publishing, exception message [Failed to connect > session for config [XXX nightly]. Message [java.net.ConnectException: > Connection refused]] > I think the "2,232" is the cause of the problem :-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12891) Use a temporary name for the uploading files
[
https://issues.jenkins-ci.org/browse/JENKINS-12891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161652#comment-161652
]
bap commented on JENKINS-12891:
---
This approach is only useful if you are only uploading a single large file.
If you are updating a directory, then you will want the entire directory update
to be atomic, otherwise some users/application may see some files from the
previous version and some from the current one.
This will probably require OS specific commands/flags (eg 'ln') or stoping
services whilst the copy is in progress.
Should the files be copied to a temporary location (where) to minimise service
downtime, or should the service/ access be stopped so that the files can be
uploaded in place because the disk space is limited.
I'm not sure there is a sensible default behaviour to support this - it is up
to you where you upload your files and scripts, and what you do before and
after they have been transferred.
> Use a temporary name for the uploading files
>
>
> Key: JENKINS-12891
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12891
> Project: Jenkins
> Issue Type: Improvement
> Components: publish-over-ssh
>Affects Versions: current
>Reporter: Artem V. Navrotskiy
>Assignee: bap
>
> Now when downloading large files for a long time at the destination may not
> be a complete file. This can lead to various problems.
> To avoid this problem you need to load it under a temporary name and then
> rename the.
> For example:
> {code}
> sftp> put bigfile.bin bigfile.bin~tmp123
> sftp> rename bigfile.bin~tmp123 bigfile.bin
> {code}
> Now you need to do:
> - Script to rename a file in the working directory;
> - Upload renamed files by ssh;
> - Using "Exec command" to change cuurent directory to upload directory
> (JENKINS-12890) and rename files back.
> This workaround looks like ugly :(
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12890) Current path of "Exec command" is not related for "Remote directory"
[ https://issues.jenkins-ci.org/browse/JENKINS-12890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161651#comment-161651 ] bap commented on JENKINS-12890: --- correct. The remote directory can be used as a convenient default location for files, or, if Exec is disabled, can be used to ensure that files can only be uploaded under this path. There is no way to provide a universal mechanism to change directory. The "shell" of the user that you log in with could be anything - including a home grown script > Current path of "Exec command" is not related for "Remote directory" > > > Key: JENKINS-12890 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12890 > Project: Jenkins > Issue Type: Bug > Components: publish-over-ssh >Affects Versions: current >Reporter: Artem V. Navrotskiy >Assignee: bap > > Scripts, added by "Exec command" started in remote user home path. > You can not specify a script that runs in the directory where the files were > uploaded without explicitly specifying the full path in the script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13111) Plugin activation cause a NullPointerException
[ https://issues.jenkins-ci.org/browse/JENKINS-13111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bap closed JENKINS-13111. - > Plugin activation cause a NullPointerException > -- > > Key: JENKINS-13111 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13111 > Project: Jenkins > Issue Type: Bug > Components: pegdown-formatter-plugin >Affects Versions: current > Environment: Debian x64 >Reporter: Sébastien Heurtematte >Assignee: bap > Attachments: stacktrace-monitoring.log, > stacktrace-without-monitoring.log > > > NullPointerException in the jenkins 1.455 > I have different stacktrace depends on monitoring plugin or not -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12882) Master stays offline if once low disk space occured
[ https://issues.jenkins-ci.org/browse/JENKINS-12882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161649#comment-161649 ] Leandro Santiago commented on JENKINS-12882: This bug (and also the above procedure) still happens in Jenkins 1.460. I tested in a Debian testing 64-bit with jenkins packages from jenkins website. > Master stays offline if once low disk space occured > --- > > Key: JENKINS-12882 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12882 > Project: Jenkins > Issue Type: Bug > Components: master-slave >Affects Versions: current >Reporter: Jan Hoppe >Priority: Blocker > > After deleting files or/and decreasing DiskSpace variables Jenkins master > stays offline! > The offline information is permanently stored in config.xml in jenkins > install dir. > It's like > class="hudson.node_monitors.DiskSpaceMonitorDescriptor$DiskSpace"> > 1011720192 > true > > > hudson.node_monitors.MonitorMarkedNodeOffline > > ... > Delete those lines from the file an start jenkins again, everything is fine! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161650#comment-161650 ] Amir Isfy commented on JENKINS-13227: - Desperately need fix... > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13466) Custom environment variables not available when build started by an SCM change
[
https://issues.jenkins-ci.org/browse/JENKINS-13466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161648#comment-161648
]
gbois commented on JENKINS-13466:
-
I think environment variables defined in node properties are not available in
AbstractBuild.getEnvironment(TaskListener) method.
I think it doesn't work in your use case because you have maybe created your
own launcher.
Therefore, the following code is not available
for (NodeProperty nodeProperty:
Hudson.getInstance().getGlobalNodeProperties()) {
Environment environment =
nodeProperty.setUp(AbstractBuild.this, l, listener);
if (environment != null) {
buildEnvironments.add(environment);
}
}
for (NodeProperty nodeProperty:
Computer.currentComputer().getNode().getNodeProperties()) {
Environment environment =
nodeProperty.setUp(AbstractBuild.this, l, listener);
if (environment != null) {
buildEnvironments.add(environment);
}
}
located in AbstractBuild#createLauncher() method
A better alternative is to use the great EnvInject plugin :)
With it, in your SCM code, just get the EnvInjectAction and its captured
environment variables (used in my forked SCM clearcase plugin).
> Custom environment variables not available when build started by an SCM change
> --
>
> Key: JENKINS-13466
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13466
> Project: Jenkins
> Issue Type: Bug
> Components: scm-sync-configuration
> Environment: not applicable
>Reporter: Robin Jarry
>Assignee: Frédéric Camblor
> Labels: envinronment-variables, polling
> Attachments: custom-env-master.jpg, custom-env-slave.jpg
>
>
> Hi there,
> I may have found a sneaky bug. Custom environment variables can be defined by
> the user into the general & nodes config:
> !custom-env-master.jpg!
> !custom-env-slave.jpg!
> When a build is triggered by an SCM change, those variables are not available
> for SCM plugins.
> Let's say that I have a field in my SCM plugin configured with this value:
> *$\{JOB_NAME\}\_$\{HOSTNAME}\_$\{NODE_TYPE\}* If the build is triggered by an
> SCM change I get this error:
> {code}
> Started by an SCM change
> Building remotely on vmo426
> [ClearCase] ### Begin source code retrieval ###
> cleartool error: Illegal characters found in view name : ${NODE_TYPE}. An
> environment variable may have not been resolved.
> Finished: FAILURE
> {code}
> Here is the code snipet from my plugin that does that:
> {code:Java}
> @Override
> public boolean checkout(AbstractBuild build, Launcher launcher, FilePath
> workspace,
> BuildListener listener, File changelogFile) throws IOException,
> InterruptedException
> {
> try {
> logger.log("### Begin source code retrieval ###");
> String resolvedViewName =
> build.getEnvironment(listener).expand(this.viewName);
>
> Pattern pattern = Pattern.compile("(\\$\\{.+?\\})");
> Matcher matcher = pattern.matcher(resolvedViewName);
> if (matcher.find()) {
> String message = "Illegal characters found in view name : %s. " +
> "An environment variable may have not been resolved.";
> throw new ClearToolError(String.format(message, matcher.group()));
> }
> {code}
> I removed *$\{NODE_TYPE\}* from my SCM configuration to let the build
> continue. And the user custom environment variables seem to be injected into
> the build environment after the SCM checkout.
> {code}
> Started by an SCM change
> Building remotely on vmo426
> [ClearCase] ### Begin source code retrieval ###
> ...
> [ClearCase] === End source code retrieval ===
> [polling_linux] $ /bin/sh -xe /tmp/hudson7589128551511062241.sh
> + env
> ...
> NODE_TYPE=SLAVE
> ...
> {code}
> Could this be fixed? :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9258) "Remember me on this computer", still getting asked to log in after a few hours
[ https://issues.jenkins-ci.org/browse/JENKINS-9258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161647#comment-161647 ] Nick Parrish commented on JENKINS-9258: --- We see this a lot at our company, too. We are using Jenkins 1.458 and use the Active Directory plugin for authentication. We have seen it with clients on various OS / browsers. I, too, looked at the cookies on my machine with firecookie, and the "Expires" value for ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE seems valid (it expires a couple weeks from now). We run Jenkins on port 8080, but forward port 80 to 8080 using iptables, but no client uses 8080 (that I know of). > "Remember me on this computer", still getting asked to log in after a few > hours > --- > > Key: JENKINS-9258 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9258 > Project: Jenkins > Issue Type: Bug > Components: core > Environment: Debian Squeeze on Linux qa01 2.6.26-2-vserver-amd64 #1 > SMP Tue Jan 25 06:09:17 UTC 2011 x86_64 GNU/Linux >Reporter: mfn > Fix For: current > > > When clicking the "Remember me on this computer" during login, after some > time the user is logged out. > I'm using Active Directory as Security Realm. > Example protocol: > I logged in at 09:19 and checked the "Remember me on this computer" checkbox. > At 10:10 I freshly opened the jenkins front page again and I was logged it. > At 11:38 again, and I found myself logged out. > All tests were conducted with Firefox 4, accepting cookies and such. > This is reproducible on an installation via Debian package. At the time of > writing the version number is 1.405 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13467) WARNING: Failed to advertise the service to DNS multi-cast
Samuel Lopez created JENKINS-13467: -- Summary: WARNING: Failed to advertise the service to DNS multi-cast Key: JENKINS-13467 URL: https://issues.jenkins-ci.org/browse/JENKINS-13467 Project: Jenkins Issue Type: Bug Components: jenkins-plugin-runtime Affects Versions: current Environment: Jenkins ver. 1.459 on Linux CentOS 6 Reporter: Samuel Lopez Assignee: Sami Tikka Priority: Minor WARNING: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.(URL.java:617) at java.net.URL.(URL.java:480) at java.net.URL.(URL.java:429) at hudson.DNSMultiCast.(DNSMultiCast.java:45) at jenkins.model.Jenkins.(Jenkins.java:787) at hudson.model.Hudson.(Hudson.java:81) at hudson.model.Hudson.(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) Caused by: java.lang.NullPointerException at java.net.URL.(URL.java:522) ... 7 more Apr 13, 2012 12:25:26 AM hudson.WebAppMain$2 run INFO: Jenkins is fully up and running -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13332) OutOfMemoryError from Perforce polling
[ https://issues.jenkins-ci.org/browse/JENKINS-13332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161646#comment-161646 ] Tim Drury commented on JENKINS-13332: - it has not occurred again > OutOfMemoryError from Perforce polling > -- > > Key: JENKINS-13332 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13332 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: Windows Server 2008, Jenkins 1.450, Perforce plugin > 1.3.7, Jenkins JVM 1.6.0_26 64-bit -Xmx=1280mb (at time of crash - it's been > increased); 1 master, 2 slaves, all SCM polling on master; See attached > jenkins-info.txt >Reporter: Tim Drury > Labels: outofmemoryerror, perforce, scm > Attachments: jenkins-info.txt > > > Our QA noticed no new builds for 2 days. When I checked the polling log of > one project it was: > Perforce Polling Log > Started on Apr 1, 2012 7:00:38 PM > Looking for changes... > Using master > Using master perforce client: jenkins_me-main > ERROR: Failed to record SCM polling > java.lang.OutOfMemoryError: Java heap space > I did not follow the Jenkins wiki process :(. If this happens again, I'll > use it to get more information. Here is the stack trace: > Apr 1, 2012 7:48:48 PM hudson.triggers.SCMTrigger$Runner runPolling > SEVERE: Failed to record SCM polling > java.lang.OutOfMemoryError: Java heap space > at hudson.remoting.FastPipedInputStream.(FastPipedInputStream.java:78) > at hudson.remoting.FastPipedInputStream.(FastPipedInputStream.java:66) > at > hudson.plugins.perforce.HudsonP4RemoteExecutor.exec(HudsonP4RemoteExecutor.java:97) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:321) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:54) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1208) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:903) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1323) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > We do keep Jenkins running without periodic reboots so I'm thinking there may > be a memory leak somewhere as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13463) Upgraded to 1.21 and now cannot copy from Matrix Builds
[ https://issues.jenkins-ci.org/browse/JENKINS-13463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161645#comment-161645 ] Alan Harder commented on JENKINS-13463: --- What version of the plugin did you upgrade from? > Upgraded to 1.21 and now cannot copy from Matrix Builds > --- > > Key: JENKINS-13463 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13463 > Project: Jenkins > Issue Type: Bug > Components: copyartifact >Affects Versions: current > Environment: openSUSE 11.2 >Reporter: Paul Wakefield >Assignee: Alan Harder >Priority: Blocker > > Everything was working fine, updated copyartifact to latest and now get the > following: > Unable to find project for artifact copy: > LiDCOHostingSDK/platform=QNX,release=debug > This may be due to incorrect project name or permission settings; see help > for project name in job configuration. > Build step 'Copy artifacts from another project' marked build as failure > No Configuration changes. > Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13466) Custom environment variables not available when build started by an SCM change
[
https://issues.jenkins-ci.org/browse/JENKINS-13466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Jarry updated JENKINS-13466:
--
Description:
Hi there,
I may have found a sneaky bug. Custom environment variables can be defined by
the user into the general & nodes config:
!custom-env-master.jpg!
!custom-env-slave.jpg!
When a build is triggered by an SCM change, those variables are not available
for SCM plugins.
Let's say that I have a field in my SCM plugin configured with this value:
*$\{JOB_NAME\}\_$\{HOSTNAME}\_$\{NODE_TYPE\}* If the build is triggered by an
SCM change I get this error:
{code}
Started by an SCM change
Building remotely on vmo426
[ClearCase] ### Begin source code retrieval ###
cleartool error: Illegal characters found in view name : ${NODE_TYPE}. An
environment variable may have not been resolved.
Finished: FAILURE
{code}
Here is the code snipet from my plugin that does that:
{code:Java}
@Override
public boolean checkout(AbstractBuild build, Launcher launcher, FilePath
workspace,
BuildListener listener, File changelogFile) throws IOException,
InterruptedException
{
try {
logger.log("### Begin source code retrieval ###");
String resolvedViewName =
build.getEnvironment(listener).expand(this.viewName);
Pattern pattern = Pattern.compile("(\\$\\{.+?\\})");
Matcher matcher = pattern.matcher(resolvedViewName);
if (matcher.find()) {
String message = "Illegal characters found in view name : %s. " +
"An environment variable may have not been resolved.";
throw new ClearToolError(String.format(message, matcher.group()));
}
{code}
I removed *$\{NODE_TYPE\}* from my SCM configuration to let the build continue.
And the user custom environment variables seem to be injected into the build
environment after the SCM checkout.
{code}
Started by an SCM change
Building remotely on vmo426
[ClearCase] ### Begin source code retrieval ###
...
[ClearCase] === End source code retrieval ===
[polling_linux] $ /bin/sh -xe /tmp/hudson7589128551511062241.sh
+ env
...
NODE_TYPE=SLAVE
...
{code}
Could this be fixed? :)
was:
Hi there,
I may have found a sneaky bug. Custom environment variables can be defined by
the user into the general & nodes config:
!custom-env-master.jpg!
!custom-env-slave.jpg!
When a build is triggered by an SCM change, those variables are not available
for SCM plugins.
Let's say that I have a field in my SCM plugin configured with this value:
*$\{JOB_NAME\}_$\{HOSTNAME}_$\{NODE_TYPE\}* If the build is triggered by an SCM
change I get this error:
{code}
Started by an SCM change
Building remotely on vmo426
[ClearCase] ### Begin source code retrieval ###
cleartool error: Illegal characters found in view name : ${NODE_TYPE}. An
environment variable may have not been resolved.
Finished: FAILURE
{code}
Here is the code snipet from my plugin that does that:
{code:Java}
@Override
public boolean checkout(AbstractBuild build, Launcher launcher, FilePath
workspace,
BuildListener listener, File changelogFile) throws IOException,
InterruptedException
{
try {
logger.log("### Begin source code retrieval ###");
String resolvedViewName =
build.getEnvironment(listener).expand(this.viewName);
Pattern pattern = Pattern.compile("(\\$\\{.+?\\})");
Matcher matcher = pattern.matcher(resolvedViewName);
if (matcher.find()) {
String message = "Illegal characters found in view name : %s. " +
"An environment variable may have not been resolved.";
throw new ClearToolError(String.format(message, matcher.group()));
}
{code}
I removed *$\{NODE_TYPE\}* from my SCM configuration to let the build continue.
And the user custom environment variables seem to be injected into the build
environment after the SCM checkout.
{code}
Started by an SCM change
Building remotely on vmo426
[ClearCase] ### Begin source code retrieval ###
...
[ClearCase] === End source code retrieval ===
[polling_linux] $ /bin/sh -xe /tmp/hudson7589128551511062241.sh
+ env
...
NODE_TYPE=SLAVE
...
{code}
Could this be fixed? :)
> Custom environment variables not available when build started by an SCM change
> --
>
> Key: JENKINS-13466
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13466
> Project: Jenkins
> Issue Type: Bug
> Components: scm-sync-configuration
> Environment: not applicable
>Reporter: Robin Jarry
>Assignee: Frédéric Camblor
> Labels: envinronment-variables, polling
> Attachments: custom-env-master.jpg, custom-env-slave.jpg
>
>
> Hi there,
> I may have found a sneaky bug. Custom environm
[JIRA] (JENKINS-13466) Custom environment variables not available when build started by an SCM change
Robin Jarry created JENKINS-13466:
-
Summary: Custom environment variables not available when build
started by an SCM change
Key: JENKINS-13466
URL: https://issues.jenkins-ci.org/browse/JENKINS-13466
Project: Jenkins
Issue Type: Bug
Components: scm-sync-configuration
Environment: not applicable
Reporter: Robin Jarry
Assignee: Frédéric Camblor
Attachments: custom-env-master.jpg, custom-env-slave.jpg
Hi there,
I may have found a sneaky bug. Custom environment variables can be defined by
the user into the general & nodes config:
!custom-env-master.jpg!
!custom-env-slave.jpg!
When a build is triggered by an SCM change, those variables are not available
for SCM plugins.
Let's say that I have a field in my SCM plugin configured with this value:
*$\{JOB_NAME\}_$\{HOSTNAME}_$\{NODE_TYPE\}* If the build is triggered by an SCM
change I get this error:
{code}
Started by an SCM change
Building remotely on vmo426
[ClearCase] ### Begin source code retrieval ###
cleartool error: Illegal characters found in view name : ${NODE_TYPE}. An
environment variable may have not been resolved.
Finished: FAILURE
{code}
Here is the code snipet from my plugin that does that:
{code:Java}
@Override
public boolean checkout(AbstractBuild build, Launcher launcher, FilePath
workspace,
BuildListener listener, File changelogFile) throws IOException,
InterruptedException
{
try {
logger.log("### Begin source code retrieval ###");
String resolvedViewName =
build.getEnvironment(listener).expand(this.viewName);
Pattern pattern = Pattern.compile("(\\$\\{.+?\\})");
Matcher matcher = pattern.matcher(resolvedViewName);
if (matcher.find()) {
String message = "Illegal characters found in view name : %s. " +
"An environment variable may have not been resolved.";
throw new ClearToolError(String.format(message, matcher.group()));
}
{code}
I removed *$\{NODE_TYPE\}* from my SCM configuration to let the build continue.
And the user custom environment variables seem to be injected into the build
environment after the SCM checkout.
{code}
Started by an SCM change
Building remotely on vmo426
[ClearCase] ### Begin source code retrieval ###
...
[ClearCase] === End source code retrieval ===
[polling_linux] $ /bin/sh -xe /tmp/hudson7589128551511062241.sh
+ env
...
NODE_TYPE=SLAVE
...
{code}
Could this be fixed? :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13332) OutOfMemoryError from Perforce polling
[ https://issues.jenkins-ci.org/browse/JENKINS-13332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161644#comment-161644 ] Rob Petti commented on JENKINS-13332: - Any more updates on this? > OutOfMemoryError from Perforce polling > -- > > Key: JENKINS-13332 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13332 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: Windows Server 2008, Jenkins 1.450, Perforce plugin > 1.3.7, Jenkins JVM 1.6.0_26 64-bit -Xmx=1280mb (at time of crash - it's been > increased); 1 master, 2 slaves, all SCM polling on master; See attached > jenkins-info.txt >Reporter: Tim Drury > Labels: outofmemoryerror, perforce, scm > Attachments: jenkins-info.txt > > > Our QA noticed no new builds for 2 days. When I checked the polling log of > one project it was: > Perforce Polling Log > Started on Apr 1, 2012 7:00:38 PM > Looking for changes... > Using master > Using master perforce client: jenkins_me-main > ERROR: Failed to record SCM polling > java.lang.OutOfMemoryError: Java heap space > I did not follow the Jenkins wiki process :(. If this happens again, I'll > use it to get more information. Here is the stack trace: > Apr 1, 2012 7:48:48 PM hudson.triggers.SCMTrigger$Runner runPolling > SEVERE: Failed to record SCM polling > java.lang.OutOfMemoryError: Java heap space > at hudson.remoting.FastPipedInputStream.(FastPipedInputStream.java:78) > at hudson.remoting.FastPipedInputStream.(FastPipedInputStream.java:66) > at > hudson.plugins.perforce.HudsonP4RemoteExecutor.exec(HudsonP4RemoteExecutor.java:97) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:321) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:54) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1208) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:903) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1323) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > We do keep Jenkins running without periodic reboots so I'm thinking there may > be a memory leak somewhere as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13063) Test report does not include all matching result xml files
[ https://issues.jenkins-ci.org/browse/JENKINS-13063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161643#comment-161643 ] Philip Corlatan commented on JENKINS-13063: --- I tried it, but in my case the update did not help. > Test report does not include all matching result xml files > -- > > Key: JENKINS-13063 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13063 > Project: Jenkins > Issue Type: Bug > Components: junit >Reporter: Philip Corlatan > > We are using the option "Publish test results" for all our build jobs > and are specifiying the following pattern for "Test results in XML format:" > "\_test/results/TEST\_*.xml" > When our ant build script is completed, there are the following files > available matching this pattern: > _test/results/TEST_hmm.xml > _test/results/TEST_mssql2008.xml > _test/results/TEST_oracle11g.xml > _test/results/TESTS-TestSuites > Since we updated to Jenkins 1.454, the file > "_test/results/TEST_oracle11g.xml" will not be included anymore in the > resulting test report (JOB/builds/TIMESTAMP/junitResult.xml) for all our > builds. > Only "TEST_hmm.xml" and "TEST_mssql2008.xml" are considered. > Symptoms: > - The build succeeds even if some of our Oracle tests fail > - The test result trend graph shows the wrong number of test > The listed files are all available in the specified directory and the HTML > test report, which we create additionally, includes all test results. > An update to Jenkins 1.455 did not help. > Please let me know if you need any further information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11839) Do not update mantis entry for all downstream jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-11839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161642#comment-161642 ] dogfood commented on JENKINS-11839: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_mantis #64|http://ci.jenkins-ci.org/job/plugins_mantis/64/] [FIXED JENKINS-11839] Do not update mantis entry for all downstream jobs (Revision 06cfccb9d272ca0923001418e1a3c4c671f5693a) Result = SUCCESS Seiji Sogabe : Files : * src/main/java/hudson/plugins/mantis/Updater.java > Do not update mantis entry for all downstream jobs > -- > > Key: JENKINS-11839 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11839 > Project: Jenkins > Issue Type: Bug > Components: mantis >Affects Versions: current > Environment: Jenkins 1.440 > Mantis-Plugin 0.20 > Mantis: 1.2.8 >Reporter: Jens H >Assignee: sogabe > > I do have a set of jobs depending on each other. > If I have a Mantis-ID in a commit message in "Project A" the Mantis issue is > updated correctly from this project. But all other projects depending on > "Project A" will also update this Mantis issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11839) Do not update mantis entry for all downstream jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-11839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161641#comment-161641 ] SCM/JIRA link daemon commented on JENKINS-11839: Code changed in jenkins User: Seiji Sogabe Path: src/main/java/hudson/plugins/mantis/Updater.java http://jenkins-ci.org/commit/mantis-plugin/06cfccb9d272ca0923001418e1a3c4c671f5693a Log: [FIXED JENKINS-11839] Do not update mantis entry for all downstream jobs > Do not update mantis entry for all downstream jobs > -- > > Key: JENKINS-11839 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11839 > Project: Jenkins > Issue Type: Bug > Components: mantis >Affects Versions: current > Environment: Jenkins 1.440 > Mantis-Plugin 0.20 > Mantis: 1.2.8 >Reporter: Jens H >Assignee: sogabe > > I do have a set of jobs depending on each other. > If I have a Mantis-ID in a commit message in "Project A" the Mantis issue is > updated correctly from this project. But all other projects depending on > "Project A" will also update this Mantis issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11839) Do not update mantis entry for all downstream jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-11839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-11839. Resolution: Fixed > Do not update mantis entry for all downstream jobs > -- > > Key: JENKINS-11839 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11839 > Project: Jenkins > Issue Type: Bug > Components: mantis >Affects Versions: current > Environment: Jenkins 1.440 > Mantis-Plugin 0.20 > Mantis: 1.2.8 >Reporter: Jens H >Assignee: sogabe > > I do have a set of jobs depending on each other. > If I have a Mantis-ID in a commit message in "Project A" the Mantis issue is > updated correctly from this project. But all other projects depending on > "Project A" will also update this Mantis issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11839) Do not update mantis entry for all downstream jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-11839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161640#comment-161640 ] sogabe commented on JENKINS-11839: -- OK. I'll release it in a short time. > Do not update mantis entry for all downstream jobs > -- > > Key: JENKINS-11839 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11839 > Project: Jenkins > Issue Type: Bug > Components: mantis >Affects Versions: current > Environment: Jenkins 1.440 > Mantis-Plugin 0.20 > Mantis: 1.2.8 >Reporter: Jens H >Assignee: sogabe > > I do have a set of jobs depending on each other. > If I have a Mantis-ID in a commit message in "Project A" the Mantis issue is > updated correctly from this project. But all other projects depending on > "Project A" will also update this Mantis issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13465) Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0
Bruno Antunes created JENKINS-13465:
---
Summary: Unable perform release: ClassCastException:
net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0
Key: JENKINS-13465
URL: https://issues.jenkins-ci.org/browse/JENKINS-13465
Project: Jenkins
Issue Type: Bug
Components: m2release
Affects Versions: current
Reporter: Bruno Antunes
Assignee: teilo
Having m2release plugin installed on Hudson 2.2.0, it generates the following
error when we try to perform a release (testing with dryRun)
Apr 16, 2012 2:31:16 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet Stapler threw exception
java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to
net.sf.json.JSONObject
at
org.jvnet.hudson.plugins.m2release.M2ReleaseAction.doSubmit(M2ReleaseAction.java:239)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
...
Examining the source code, for M2ReleaseAction, it happens because there are
not values in the form data for the parameter named "parameter"
M2ReleaseAction Code:
public void doSubmit(StaplerRequest req, StaplerResponse resp) ... {
...
JSONArray a = JSONArray.fromObject(formData.get("parameter"));
for (Object o : a) {
JSONObject jo = (JSONObject) o;
...
In order to solve this, check that we have "parameter"; or check for a possible
JSONNull object:
Possible Fix:
JSONArray a = JSONArray.fromObject(formData.get("parameter"));
for (Object o : a) {
if (o instanceof JSONObject) {
JSONObject jo = (JSONObject) o;
...
}
...
Note: The plugin is installed on Hudson with the workaround described in
#JENKINS-12991
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13063) Test report does not include all matching result xml files
[ https://issues.jenkins-ci.org/browse/JENKINS-13063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161639#comment-161639 ] kbond commented on JENKINS-13063: - Looks the be the same issue, I will try out the latest release. > Test report does not include all matching result xml files > -- > > Key: JENKINS-13063 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13063 > Project: Jenkins > Issue Type: Bug > Components: junit >Reporter: Philip Corlatan > > We are using the option "Publish test results" for all our build jobs > and are specifiying the following pattern for "Test results in XML format:" > "\_test/results/TEST\_*.xml" > When our ant build script is completed, there are the following files > available matching this pattern: > _test/results/TEST_hmm.xml > _test/results/TEST_mssql2008.xml > _test/results/TEST_oracle11g.xml > _test/results/TESTS-TestSuites > Since we updated to Jenkins 1.454, the file > "_test/results/TEST_oracle11g.xml" will not be included anymore in the > resulting test report (JOB/builds/TIMESTAMP/junitResult.xml) for all our > builds. > Only "TEST_hmm.xml" and "TEST_mssql2008.xml" are considered. > Symptoms: > - The build succeeds even if some of our Oracle tests fail > - The test result trend graph shows the wrong number of test > The listed files are all available in the specified directory and the HTML > test report, which we create additionally, includes all test results. > An update to Jenkins 1.455 did not help. > Please let me know if you need any further information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
[ https://issues.jenkins-ci.org/browse/JENKINS-12235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161638#comment-161638 ] Richard Taylor commented on JENKINS-12235: -- We have started getting this reciently. Difficult to search but I think about version 1.455. * If there is no obvious fix can the exception be caught so that it does fail an otherwise successful build? I think this would be an adequate workaround for most people, atm this issue is causing random builds to fail which is a significant annoyance for the developers. Thanks. Rich. > FATAL, Unable to delete script file, IOException2, remote file operation > failed, unexpected termination of channel > -- > > Key: JENKINS-12235 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12235 > Project: Jenkins > Issue Type: Bug > Components: core, master-slave >Reporter: Ghenadie Dumitru > Attachments: jenkins_fatal_io_exception.txt > > > Below is the stacktrace. > It happened when I ran two jobs on a master. After running a while, both jobs > crashed with this exception. > I think this might be caused by a small flip-flop connectivity of the > network, but I didn't noticed any disconnection. > Another cause may be the huge load of jenkins: > PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND > > > > 25942 hudson15 0 6902m 5.8g 5720 S 0.3 74.3 401:22.30 java > Does the jenkins runs its own garbage collector at some specified time? > We have to restart every few days because it's getting slower and slower > until hangs out. > FATAL: Unable to delete script file /tmp/hudson8303731085225956739.sh > hudson.util.IOException2: remote file operation failed: > /tmp/hudson8303731085225956739.sh at > hudson.remoting.Channel@30e472f4:build@autom-1 > at hudson.FilePath.act(FilePath.java:781) > at hudson.FilePath.act(FilePath.java:767) > at hudson.FilePath.delete(FilePath.java:1022) > at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:92) > at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) > at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:695) > at hudson.model.Build$RunnerImpl.build(Build.java:178) > at hudson.model.Build$RunnerImpl.doRun(Build.java:139) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:461) > at hudson.model.Run.run(Run.java:1404) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:230) > Caused by: hudson.remoting.ChannelClosedException: channel is already closed > at hudson.remoting.Channel.send(Channel.java:499) > at hudson.remoting.Request.call(Request.java:110) > at hudson.remoting.Channel.call(Channel.java:681) > at hudson.FilePath.act(FilePath.java:774) > ... 13 more > Caused by: java.io.IOException: Unexpected termination of the channel > at hudson.remoting.Channel$ReaderThread.run(Channel.java:1115) > Caused by: java.io.EOFException > at > java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2554) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) > at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109) > FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: > Unexpected termination of the channel > hudson.remoting.RequestAbortedException: > hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected > termination of the channel > at hudson.remoting.Request.call(Request.java:149) > at hudson.remoting.Channel.call(Channel.java:681) > at > hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) > at $Proxy29.join(Unknown Source) > at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:859) > at hudson.Launcher$ProcStarter.join(Launcher.java:345) > at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82) > at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) > at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:695) > at hudson.model.Build$Runn
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161637#comment-161637 ] Guillaume Bilodeau commented on JENKINS-13227: -- The problem is still there in version 2.3 > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13333) Clicking test result links in IE8 when you have JavaScript debugging on produces an error.
[ https://issues.jenkins-ci.org/browse/JENKINS-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] alexlombardi updated JENKINS-1: --- Description: When you drill down to look at NUnit Test results for builds and JavaScript debugging is enabled in IE8 it produces an object not found error (see attached document). UPDATE: This error also occurs when you try to bring up information for a user that is tied to the "RECENT CHANGES" output. was:When you drill down to look at NUnit Test results for builds and JavaScript debugging is enabled in IE8 it produces an object not found error (see attached document). > Clicking test result links in IE8 when you have JavaScript debugging on > produces an error. > -- > > Key: JENKINS-1 > URL: https://issues.jenkins-ci.org/browse/JENKINS-1 > Project: Jenkins > Issue Type: Bug > Components: nunit >Affects Versions: current > Environment: Running Jenkins as a Windows Service on a server. >Reporter: alexlombardi >Assignee: redsolo > Attachments: Error.doc > > > When you drill down to look at NUnit Test results for builds and JavaScript > debugging is enabled in IE8 it produces an object not found error (see > attached document). > UPDATE: This error also occurs when you try to bring up information for a > user that is tied to the "RECENT CHANGES" output. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-5413) SCM polling on slaves getting hung
[ https://issues.jenkins-ci.org/browse/JENKINS-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161636#comment-161636 ] Christian Wolfgang commented on JENKINS-5413: - We have solved our problems now. It turned out, that the underlying framework for the plugin threw RuntimeExceptions which were not catched all the time. After we handled those exceptions the slaves stopped hanging. > SCM polling on slaves getting hung > -- > > Key: JENKINS-5413 > URL: https://issues.jenkins-ci.org/browse/JENKINS-5413 > Project: Jenkins > Issue Type: Bug > Components: master-slave >Affects Versions: current >Reporter: Dean Yu > Attachments: hung_scm_pollers_02.PNG, threads.vetted.txt, > thread_dump_02.txt > > > This is to track the problem originally reported here: > http://n4.nabble.com/Polling-hung-td1310838.html#a1310838 > The referenced thread is relocated to > http://jenkins.361315.n4.nabble.com/Polling-hung-td1310838.html > What the problem boils down to is that many remote operations are performed > synchronously causing the channel object to be locked while a response > returns. In situations where a lengthy remote operations is using the > channel, SCM polling can be blocked waiting for the monitor on the channel to > be released. In extreme situations, all the polling threads can wind up > waiting on object monitors for the channel objects, preventing further > processing of polling tasks. > Furthermore, if the slave dies, the locked channel object still exists in the > master JVM. If no IOException is thrown to indicate the termination of the > connection to the pipe, the channel can never be closed because > Channel.close() itself is a sychronized operation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13063) Test report does not include all matching result xml files
[ https://issues.jenkins-ci.org/browse/JENKINS-13063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161635#comment-161635 ] Philip Corlatan commented on JENKINS-13063: --- I'm currently checking if this issue is a duplicate of JENKINS-13214 (which has been fixed for the current release) and will give feedback today. > Test report does not include all matching result xml files > -- > > Key: JENKINS-13063 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13063 > Project: Jenkins > Issue Type: Bug > Components: junit >Reporter: Philip Corlatan > > We are using the option "Publish test results" for all our build jobs > and are specifiying the following pattern for "Test results in XML format:" > "\_test/results/TEST\_*.xml" > When our ant build script is completed, there are the following files > available matching this pattern: > _test/results/TEST_hmm.xml > _test/results/TEST_mssql2008.xml > _test/results/TEST_oracle11g.xml > _test/results/TESTS-TestSuites > Since we updated to Jenkins 1.454, the file > "_test/results/TEST_oracle11g.xml" will not be included anymore in the > resulting test report (JOB/builds/TIMESTAMP/junitResult.xml) for all our > builds. > Only "TEST_hmm.xml" and "TEST_mssql2008.xml" are considered. > Symptoms: > - The build succeeds even if some of our Oracle tests fail > - The test result trend graph shows the wrong number of test > The listed files are all available in the specified directory and the HTML > test report, which we create additionally, includes all test results. > An update to Jenkins 1.455 did not help. > Please let me know if you need any further information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9494) Configure System hangs with "LOADING" gray div covering top half of settings
[ https://issues.jenkins-ci.org/browse/JENKINS-9494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161634#comment-161634 ] Tim Aerdts commented on JENKINS-9494: - I found this problem as well, at first I thought it was because I installed the following plugin: https://wiki.jenkins-ci.org/display/JENKINS/Create+Job+Advanced+Plugin But it was because I had a ' character in my job's name. > Configure System hangs with "LOADING" gray div covering top half of settings > > > Key: JENKINS-9494 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9494 > Project: Jenkins > Issue Type: Bug > Components: infrastructure >Affects Versions: current > Environment: OpenJDK Runtime Environment (IcedTea6 1.9.7) > (6b20-1.9.7-0ubuntu1) > OpenJDK Client VM (build 19.0-b09, mixed mode, sharing) > AWS EC2 cloud instance machine > package installed by the recommended apt-get instructions on jenkins-ci.org. > apt-show says: > "Package: jenkins > Priority: extra > Section: devel > Installed-Size: 37480 > Maintainer: Kohsuke Kawaguchi > Architecture: all > Version: 1.404 > Replaces: hudson > Depends: daemon, adduser, psmisc, java2-runtime > Conflicts: hudson > Filename: binary/jenkins_1.404_all.deb > Size: 38056418 > MD5sum: 84529c04673ebe58208b4d0820853e54 > SHA1: 1c5df6bd354395edac88e136d9503ee8c92d60f3 > SHA256: 25270ed4f113423754c4fab03e48d13396896d98f087e8980e11e61bd97ff711 > Description: Continuous integration system written in Java > Jenkins is an extensible continuous engine written in Java. > Homepage: https://jenkins-ci.org/ > " > Note despite this 1.404, Jenkins actually displays 1.407 in its footer >Reporter: Jay Levitt >Priority: Critical > > I am setting up Jenkins for the first time. I've successfully gone into the > configure system screen before, because I was able to set up matrix user > permissions as outlined in the Standard Security guide. I wanted to add an > environment variable to set the time, but now I'm unable, because the page > load never completes. I'm new to java, but happy to troubleshoot and try > things if you tell me what logs to look at. This is NOT running under TomCat. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13461) "Add Build Step" -> "Execute shell" gives a 403 (Forbidden) error (js console)
[ https://issues.jenkins-ci.org/browse/JENKINS-13461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161633#comment-161633 ] Glenn Roberts commented on JENKINS-13461: - disabling "Prevent Cross Site Request Forgery Exploits" seems to have done the trick - see here: https://issues.jenkins-ci.org/browse/JENKINS-9142 > "Add Build Step" -> "Execute shell" gives a 403 (Forbidden) error (js console) > -- > > Key: JENKINS-13461 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13461 > Project: Jenkins > Issue Type: Bug > Components: ant, campfire, cvs, git, github, javadoc, maven, > ssh-slaves, subversion, translation >Affects Versions: current > Environment: client: OSX Chrome 18.0.1025.151 > server: Ubuntu 10.04 (Latest 2.6 (2.6.39.1-linode34)) >Reporter: Glenn Roberts >Assignee: jenslukowski >Priority: Blocker > > I just upgraded to Jenkins 1.460, and cannot add a new job that requires an > "Execute shell" build step. > Job setup and JS error: > http://imgur.com/a/ayizb > Full error text: > POST > http://mrpink.siyelo.com/$stapler/bound/5d4c76df-d4df-45cf-8373-3be5c3e31694/render > 403 (Forbidden) > Ajax.Request.Object.extend.requestprototype.js:1057 > Ajax.Request.Object.extend.initializeprototype.js:1019 > (anonymous function)prototype.js:37 > methods.each.proxy.(anonymous function)bind.js:27 > renderOnDemandhudson-behavior.js:435 > (anonymous function)hudson-behavior.js:547 > YAHOO.util.CustomEvent.notifyevent-min.js:7 > YAHOO.util.CustomEvent.fireevent-min.js:7 > emenu-min.js:7 > _addListener.nevent-min.js:7 > System Properties > === > Name ↓ > Value > executable-war/usr/share/jenkins/jenkins.war > file.encoding ANSI_X3.4-1968 > file.encoding.pkg sun.io > file.separator/ > hudson.diyChunkingtrue > java.awt.graphicsenv sun.awt.X11GraphicsEnvironment > java.awt.headless true > java.awt.printerjob sun.print.PSPrinterJob > java.class.path /usr/share/jenkins/jenkins.war > java.class.version50.0 > java.endorsed.dirs/usr/lib/jvm/java-6-openjdk/jre/lib/endorsed > java.ext.dirs > /usr/lib/jvm/java-6-openjdk/jre/lib/ext:/usr/java/packages/lib/ext > java.home /usr/lib/jvm/java-6-openjdk/jre > java.io.tmpdir/tmp > java.library.path > /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/java/packages/lib/i386:/usr/lib/jni:/lib:/usr/lib > java.runtime.name OpenJDK Runtime Environment > java.runtime.version 1.6.0_20-b20 > java.specification.name Java Platform API Specification > java.specification.vendor Sun Microsystems Inc. > java.specification.version1.6 > java.vendor Sun Microsystems Inc. > java.vendor.url http://java.sun.com/ > java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi > java.version 1.6.0_20 > java.vm.info mixed mode, sharing > java.vm.name OpenJDK Client VM > java.vm.specification.nameJava Virtual Machine Specification > java.vm.specification.vendor Sun Microsystems Inc. > java.vm.specification.version 1.0 > java.vm.vendorSun Microsystems Inc. > java.vm.version 19.0-b09 > javax.accessibility.assistive_technologies > org.GNOME.Accessibility.JavaBridge > jna.platform.library.path /usr/lib:/lib > line.separator > mail.smtp.sendpartial true > mail.smtp.starttls.enable true > mail.smtps.sendpartialtrue > os.arch i386 > os.name Linux > os.version2.6.39.1-linode34 > path.separator: > sun.arch.data.model 32 > sun.boot.class.path > /usr/lib/jvm/java-6-openjdk/jre/lib/resources.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/rt.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/jsse.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/jce.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/charsets.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/netx.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/plugin.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/rhino.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/modules/jdk.boot.jar:/usr/lib/jvm/java-6-openjdk/jre/classes > sun.boot.library.path /usr/lib/jvm/java-6-openjdk/jre/lib/i386 > sun.cpu.endianlittle > sun.cpu.isalist > sun.io.unicode.encoding UnicodeLittle > sun.java.launcher SUN_STANDARD > sun.jnu.encoding ANSI_X3.4-1968 > sun.management.compiler HotSpot Client Compiler > sun.os.patch.levelunknown > user.country US > user.dir / > user.home /var/lib/jenkins > user.language en > user.name jenkins > user.timezone Africa/Johannesburg > Environment Variables > Name ↓ > Value > AUTOFEATURE true > CLICOLOR 1 > EDITORmate -w > GIT_EDITORma
[JIRA] (JENKINS-13464) Using Other Views filter, I'm getting a stack overflow error after update to Jenkins 1.459
Vincent Latombe created JENKINS-13464: - Summary: Using Other Views filter, I'm getting a stack overflow error after update to Jenkins 1.459 Key: JENKINS-13464 URL: https://issues.jenkins-ci.org/browse/JENKINS-13464 Project: Jenkins Issue Type: Bug Components: view-job-filters Reporter: Vincent Latombe Assignee: jacob_robertson Priority: Blocker Attachments: StackOverflow.txt Due to https://github.com/jenkinsci/jenkins/commit/85e13303f8cfbebeb7dab347fda8ccf4069070b6 , any view using Other Views filter now gets a StackOverflowError. The reason is that it uses a wrong way of retrieving the referenced view, by getting first 'all' the views. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13463) Upgraded to 1.21 and now cannot copy from Matrix Builds
Paul Wakefield created JENKINS-13463: Summary: Upgraded to 1.21 and now cannot copy from Matrix Builds Key: JENKINS-13463 URL: https://issues.jenkins-ci.org/browse/JENKINS-13463 Project: Jenkins Issue Type: Bug Components: copyartifact Affects Versions: current Environment: openSUSE 11.2 Reporter: Paul Wakefield Assignee: Alan Harder Priority: Blocker Everything was working fine, updated copyartifact to latest and now get the following: Unable to find project for artifact copy: LiDCOHostingSDK/platform=QNX,release=debug This may be due to incorrect project name or permission settings; see help for project name in job configuration. Build step 'Copy artifacts from another project' marked build as failure No Configuration changes. Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13462) xUnit doesnot work with PHPUnit JUnit Log
Thomas Z created JENKINS-13462: -- Summary: xUnit doesnot work with PHPUnit JUnit Log Key: JENKINS-13462 URL: https://issues.jenkins-ci.org/browse/JENKINS-13462 Project: Jenkins Issue Type: Bug Components: xunit Affects Versions: current Environment: Debian squeeze Reporter: Thomas Z Assignee: gbois Hi, i detected a problem with the current xUnit version (1.4.3) when i try to parse JUnit log files when using phpunit 3.6.X (I have tried that with diffrent versions). The build is always marked as stable which in my case is not correct. Here is the console-output: [] [exec] Time: 28 seconds, Memory: 17.50Mb [exec] [exec] There was 1 failure: [exec] [exec] 1) unit_RankedMatchTest::testFoo [exec] Failed asserting that false is true. [] [xUnit] [INFO] - [PHPUnit-3.4 (default)] - 1 test report file(s) were found with the pattern 'trunk/build/phpunit/junit.xml' relative to '/var/lib/jenkins/jobs/foo/workspace' for the testing framework 'PHPUnit-3.4 (default)'. [xUnit] [INFO] - Check 'Failed Tests' threshold. [xUnit] [INFO] - Check 'Skipped Tests' threshold. [xUnit] [INFO] - Setting the build status to SUCCESS [xUnit] [INFO] - Stopping recording. When i looked into the JUnit log file which i generated with "phpunit --log-junit " i can still see the failure: [...] unit_FoobarTest::testFoo Failed asserting that false is true. /raid/hudson_jobs/foo/workspace/trunk/test/phpunit/unit/proxies/FoobarTest.php:8 [...] I hope you can help me with this. Let me know if you need more information. Regards, Thomas -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13461) "Add Build Step" -> "Execute shell" gives a 403 (Forbidden) error (js console)
Glenn Roberts created JENKINS-13461: --- Summary: "Add Build Step" -> "Execute shell" gives a 403 (Forbidden) error (js console) Key: JENKINS-13461 URL: https://issues.jenkins-ci.org/browse/JENKINS-13461 Project: Jenkins Issue Type: Bug Components: ant, campfire, cvs, git, github, javadoc, maven, ssh-slaves, subversion, translation Affects Versions: current Environment: client: OSX Chrome 18.0.1025.151 server: Ubuntu 10.04 (Latest 2.6 (2.6.39.1-linode34)) Reporter: Glenn Roberts Assignee: jenslukowski Priority: Blocker I just upgraded to Jenkins 1.460, and cannot add a new job that requires an "Execute shell" build step. Job setup and JS error: http://imgur.com/a/ayizb Full error text: POST http://mrpink.siyelo.com/$stapler/bound/5d4c76df-d4df-45cf-8373-3be5c3e31694/render 403 (Forbidden) Ajax.Request.Object.extend.requestprototype.js:1057 Ajax.Request.Object.extend.initializeprototype.js:1019 (anonymous function)prototype.js:37 methods.each.proxy.(anonymous function)bind.js:27 renderOnDemandhudson-behavior.js:435 (anonymous function)hudson-behavior.js:547 YAHOO.util.CustomEvent.notifyevent-min.js:7 YAHOO.util.CustomEvent.fireevent-min.js:7 emenu-min.js:7 _addListener.nevent-min.js:7 System Properties === Name ↓ Value executable-war /usr/share/jenkins/jenkins.war file.encoding ANSI_X3.4-1968 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenvsun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/share/jenkins/jenkins.war java.class.version 50.0 java.endorsed.dirs /usr/lib/jvm/java-6-openjdk/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-6-openjdk/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-6-openjdk/jre java.io.tmpdir /tmp java.library.path /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/java/packages/lib/i386:/usr/lib/jni:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version1.6.0_20-b20 java.specification.name Java Platform API Specification java.specification.vendor Sun Microsystems Inc. java.specification.version 1.6 java.vendor Sun Microsystems Inc. java.vendor.url http://java.sun.com/ java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi java.version1.6.0_20 java.vm.infomixed mode, sharing java.vm.nameOpenJDK Client VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendorSun Microsystems Inc. java.vm.specification.version 1.0 java.vm.vendor Sun Microsystems Inc. java.vm.version 19.0-b09 javax.accessibility.assistive_technologies org.GNOME.Accessibility.JavaBridge jna.platform.library.path /usr/lib:/lib line.separator mail.smtp.sendpartial true mail.smtp.starttls.enable true mail.smtps.sendpartial true os.arch i386 os.name Linux os.version 2.6.39.1-linode34 path.separator : sun.arch.data.model 32 sun.boot.class.path /usr/lib/jvm/java-6-openjdk/jre/lib/resources.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/rt.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/jsse.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/jce.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/charsets.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/netx.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/plugin.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/rhino.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/modules/jdk.boot.jar:/usr/lib/jvm/java-6-openjdk/jre/classes sun.boot.library.path /usr/lib/jvm/java-6-openjdk/jre/lib/i386 sun.cpu.endian little sun.cpu.isalist sun.io.unicode.encoding UnicodeLittle sun.java.launcher SUN_STANDARD sun.jnu.encodingANSI_X3.4-1968 sun.management.compiler HotSpot Client Compiler sun.os.patch.level unknown user.countryUS user.dir/ user.home /var/lib/jenkins user.language en user.name jenkins user.timezone Africa/Johannesburg Environment Variables Name ↓ Value AUTOFEATURE true CLICOLOR1 EDITOR mate -w GIT_EDITOR mate -wl1. GREP_OPTIONS--color=auto HISTCONTROL erasedups HISTSIZE5 HOME/var/lib/jenkins HOUND_PASSWORD houndyhound123 HOUND_USERNAME ho...@hound.cc JENKINS_HOME/var/lib/jenkins LD_LIBRARY_PATH /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386 LOGNAME jenkins LSCOLORSExFxCxDxBxegedabagacad MAIL/var/mail/jenkins PATH /usr/local/bin:/usr/local/sbin:/usr/local/mysql/bin:/var/lib/jenkins/Scripts/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/var/lib/jenkins/.rvm/bin PS1
[JIRA] (JENKINS-13460) Environment variables not explanded for "Remote Directory" configuration
Bertrand Latinville created JENKINS-13460:
-
Summary: Environment variables not explanded for "Remote
Directory" configuration
Key: JENKINS-13460
URL: https://issues.jenkins-ci.org/browse/JENKINS-13460
Project: Jenkins
Issue Type: Bug
Components: publish-over-ssh
Reporter: Bertrand Latinville
Assignee: bap
Priority: Minor
I'm using publish over ssh to send file on a remote folder
and Exec commands.
As the folder where I put the files may change in the future I defined a
Jenkins environment variable: REMOTE_LOCATION.
I'd like to use this variable in SSH publish over configuration and in the
Exec command of the job.
I configured ssh publish over plugin with Remote Directory set to
${REMOTE_LOCATION}
I get this error :
ERROR: Exception when publishing, exception message [Failed to change to remote
directory [${REMOTE_LOCATION}]]
Build step 'Send build artifacts over SSH' changed build result to UNSTABLE
I checked that the variable is set properly by echo ${REMOTE_LOCATION} in the
Exec command.
Variables should be expanded in the "Remote Directory" configuration field.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11839) Do not update mantis entry for all downstream jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-11839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161632#comment-161632 ] Jens H commented on JENKINS-11839: -- The Snapshot seems to do the right thing for me. > Do not update mantis entry for all downstream jobs > -- > > Key: JENKINS-11839 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11839 > Project: Jenkins > Issue Type: Bug > Components: mantis >Affects Versions: current > Environment: Jenkins 1.440 > Mantis-Plugin 0.20 > Mantis: 1.2.8 >Reporter: Jens H >Assignee: sogabe > > I do have a set of jobs depending on each other. > If I have a Mantis-ID in a commit message in "Project A" the Mantis issue is > updated correctly from this project. But all other projects depending on > "Project A" will also update this Mantis issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11839) Do not update mantis entry for all downstream jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-11839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161632#comment-161632 ] Jens H edited comment on JENKINS-11839 at 4/16/12 8:59 AM: --- Test successful. The Snapshot seems to do the right thing for me. was (Author: nigjo): The Snapshot seems to do the right thing for me. > Do not update mantis entry for all downstream jobs > -- > > Key: JENKINS-11839 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11839 > Project: Jenkins > Issue Type: Bug > Components: mantis >Affects Versions: current > Environment: Jenkins 1.440 > Mantis-Plugin 0.20 > Mantis: 1.2.8 >Reporter: Jens H >Assignee: sogabe > > I do have a set of jobs depending on each other. > If I have a Mantis-ID in a commit message in "Project A" the Mantis issue is > updated correctly from this project. But all other projects depending on > "Project A" will also update this Mantis issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161631#comment-161631 ] Dmitry Teterevyatnikov commented on JENKINS-11381: -- Due to released SVNKit, do you have any plans to update Subversion plugin? > Subversion Plugin does not support Subversion 1.7 > - > > Key: JENKINS-11381 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 > Project: Jenkins > Issue Type: Improvement > Components: subversion >Reporter: soundworker >Priority: Blocker > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12823) Clean up temporary config files at the very end, not before post-build
[ https://issues.jenkins-ci.org/browse/JENKINS-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161630#comment-161630 ] dogfood commented on JENKINS-12823: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_config-file-provider-plugin #36|http://ci.jenkins-ci.org/job/plugins_config-file-provider-plugin/36/] [FIXED JENKINS-12823] Clean up temporary config files at the very end, not before post-build (Revision 4de756a2338d2f87135c56ea5c9741f92cfcd976) Result = SUCCESS imod : Files : * src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/ManagedFilesEnvironment.java * src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/CleanTempFilesRunListener.java * src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/ManagedFileUtil.java * src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/ConfigFileBuildWrapper.java * src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/CleanTempFilesAction.java > Clean up temporary config files at the very end, not before post-build > -- > > Key: JENKINS-12823 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12823 > Project: Jenkins > Issue Type: New Feature > Components: config-file-provider >Reporter: oeuftete >Assignee: domi > > It would be nice if Config File Provider temporary configuration files stuck > around for the entire lifetime of a job execution, instead of being cleaned > up before the post-build tasks. I just tried to use a maven settings file in > a Sonar post-build action, but the temporary file was gone by that time. I > confirmed it did exist during the build process (by cat-ting it in a regular > build step). > I've worked around this by having the plugin put the file in an explicit > location in the workspace for now, and using it from there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13236) start identical job with different parameters in parallel execution
[ https://issues.jenkins-ci.org/browse/JENKINS-13236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13236. --- Resolution: Not A Defect There is a checkbox "Execute concurrent builds if necessary" in job configuration page. I enable the checkbox and run jobs in parallel with different branches. > start identical job with different parameters in parallel execution > --- > > Key: JENKINS-13236 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13236 > Project: Jenkins > Issue Type: New Feature > Components: core >Reporter: ttgtg ttgtg > Labels: build, parallel > > Have the option for a job to run several instances in parallel. > The use case: > We have a job that gets the branch name as an input and then it builds the > project and run the test. > If two or more developers want to build different branches the first one > blocks the others. The build and test take a lot of time but with many nodes > we can do several in parallel. > There may be a problem with this option if the jobs use the same workspace, > but on our setup the workspace is set by time and date with the branch name > to prevent this problem. > As this option has potential for destruction it should be under the advance > options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13236) start identical job with different parameters in parallel execution
[ https://issues.jenkins-ci.org/browse/JENKINS-13236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro updated JENKINS-13236: -- Component/s: (was: build-pipeline) > start identical job with different parameters in parallel execution > --- > > Key: JENKINS-13236 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13236 > Project: Jenkins > Issue Type: New Feature > Components: core >Reporter: ttgtg ttgtg > Labels: build, parallel > > Have the option for a job to run several instances in parallel. > The use case: > We have a job that gets the branch name as an input and then it builds the > project and run the test. > If two or more developers want to build different branches the first one > blocks the others. The build and test take a lot of time but with many nodes > we can do several in parallel. > There may be a problem with this option if the jobs use the same workspace, > but on our setup the workspace is set by time and date with the branch name > to prevent this problem. > As this option has potential for destruction it should be under the advance > options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12823) Clean up temporary config files at the very end, not before post-build
[ https://issues.jenkins-ci.org/browse/JENKINS-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161628#comment-161628 ] SCM/JIRA link daemon commented on JENKINS-12823: Code changed in jenkins User: imod Path: src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/CleanTempFilesAction.java src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/CleanTempFilesRunListener.java src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/ConfigFileBuildWrapper.java src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/ManagedFileUtil.java src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/ManagedFilesEnvironment.java http://jenkins-ci.org/commit/config-file-provider-plugin/4de756a2338d2f87135c56ea5c9741f92cfcd976 Log: [FIXED JENKINS-12823] Clean up temporary config files at the very end, not before post-build > Clean up temporary config files at the very end, not before post-build > -- > > Key: JENKINS-12823 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12823 > Project: Jenkins > Issue Type: New Feature > Components: config-file-provider >Reporter: oeuftete >Assignee: domi > > It would be nice if Config File Provider temporary configuration files stuck > around for the entire lifetime of a job execution, instead of being cleaned > up before the post-build tasks. I just tried to use a maven settings file in > a Sonar post-build action, but the temporary file was gone by that time. I > confirmed it did exist during the build process (by cat-ting it in a regular > build step). > I've worked around this by having the plugin put the file in an explicit > location in the workspace for now, and using it from there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12823) Clean up temporary config files at the very end, not before post-build
[ https://issues.jenkins-ci.org/browse/JENKINS-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12823. Resolution: Fixed > Clean up temporary config files at the very end, not before post-build > -- > > Key: JENKINS-12823 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12823 > Project: Jenkins > Issue Type: New Feature > Components: config-file-provider >Reporter: oeuftete >Assignee: domi > > It would be nice if Config File Provider temporary configuration files stuck > around for the entire lifetime of a job execution, instead of being cleaned > up before the post-build tasks. I just tried to use a maven settings file in > a Sonar post-build action, but the temporary file was gone by that time. I > confirmed it did exist during the build process (by cat-ting it in a regular > build step). > I've worked around this by having the plugin put the file in an explicit > location in the workspace for now, and using it from there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13385) Jenkins stop working after upgrade
[ https://issues.jenkins-ci.org/browse/JENKINS-13385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13385. --- Resolution: Fixed Will be fixed in 1.462. See JENKINS-13448. > Jenkins stop working after upgrade > -- > > Key: JENKINS-13385 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13385 > Project: Jenkins > Issue Type: Bug > Components: git >Affects Versions: current >Reporter: wernight >Assignee: Nicolas De Loof >Priority: Blocker > > After upgrading Jenkins to 1.459 I got this exception which is removed as > soon as I disable Git plugin 1.1.16: > SEVERE: Failed to create Guice container from all the plugins > com.google.common.collect.ComputationException: > java.lang.TypeNotPresentException: Type > hudson.plugins.view.dashboard.DashboardPortlet not present > at > com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) > at com.google.inject.internal.FailableCache.get(FailableCache.java:49) > at > com.google.inject.internal.MembersInjectorStore.get(MembersInjectorStore.java:66) > at > com.google.inject.internal.ConstructorInjectorStore.createConstructor(ConstructorInjectorStore.java:73) > at > com.google.inject.internal.ConstructorInjectorStore.access$000(ConstructorInjectorStore.java:29) > at > com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:36) > at > com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:33) > at com.google.inject.internal.FailableCache$1.apply(FailableCache.java:38) > at > com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) > at > com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) > at > com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) > at > com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) > at > com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) > at com.google.inject.internal.FailableCache.get(FailableCache.java:49) > at > com.google.inject.internal.ConstructorInjectorStore.get(ConstructorInjectorStore.java:49) > at > com.google.inject.internal.ConstructorBindingImpl.initialize(ConstructorBindingImpl.java:127) > at > com.google.inject.internal.InjectorImpl.initializeBinding(InjectorImpl.java:506) > at > com.google.inject.internal.AbstractBindingProcessor$Processor$1.run(AbstractBindingProcessor.java:171) > at > com.google.inject.internal.ProcessedBindingData.initializeBindings(ProcessedBindingData.java:44) > at > com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:123) > at > com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107) > at com.google.inject.Guice.createInjector(Guice.java:94) > at com.google.inject.Guice.createInjector(Guice.java:71) > at hudson.ExtensionFinder$GuiceFinder.(ExtensionFinder.java:280) > 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:532) > at java.lang.Class.newInstance0(Class.java:372) > at java.lang.Class.newInstance(Class.java:325) > at net.java.sezpoz.IndexItem.instance(IndexItem.java:181) > at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:616) > at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:591) > at hudson.ExtensionFinder._find(ExtensionFinder.java:149) > at > hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:289) > at hudson.ExtensionList.load(ExtensionList.java:278) > at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) > at hudson.ExtensionList.iterator(ExtensionList.java:138) > at > hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:282) > at hudson.ExtensionList.load(ExtensionList.java:278) > at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) > at hudson.ExtensionList.iterator(ExtensionList.java:138) > at hudson.ExtensionList.get(ExtensionList.java:129) > at > hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:86) > at sun.reflect.NativeMethodAccesso
[JIRA] (JENKINS-13381) Jenkins stopped after updating plugins
[ https://issues.jenkins-ci.org/browse/JENKINS-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13381. --- Resolution: Fixed Will be fixed in 1.462. See JENKINS-13448. > Jenkins stopped after updating plugins > -- > > Key: JENKINS-13381 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13381 > Project: Jenkins > Issue Type: Bug > Components: analysis-collector, core, git >Affects Versions: current > Environment: Ubuntu Server 64 bits >Reporter: Rafael Tavares >Assignee: Nicolas De Loof > Labels: git, jenkins, plugins > > Hi, > I was updating my plugins then after update I can't access anymore my > jenkins. I get the following error: > > [!] Erro > org.jvnet.hudson.reactor.ReactorException: java.lang.Error: > java.lang.reflect.InvocationTargetException > at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) > at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) > at jenkins.model.Jenkins.executeReactor(Jenkins.java:849) > at jenkins.model.Jenkins.(Jenkins.java:761) > at hudson.model.Hudson.(Hudson.java:81) > at hudson.model.Hudson.(Hudson.java:77) > at hudson.WebAppMain$2.run(WebAppMain.java:217) > Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException > at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) > at > hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) > at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) > at jenkins.model.Jenkins$6.runTask(Jenkins.java:838) > at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) > at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) > ... 8 more > Caused by: java.lang.NullPointerException > at hudson.plugins.git.GitTool.onLoaded(GitTool.java:74) > ... 13 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12966) gitTool crashes Jenkins startup
[ https://issues.jenkins-ci.org/browse/JENKINS-12966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-12966. --- Resolution: Fixed Will be fixed in 1.462. See JENKINS-13448. > gitTool crashes Jenkins startup > --- > > Key: JENKINS-12966 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12966 > Project: Jenkins > Issue Type: Bug > Components: core, git > Environment: Jenkins 1.452 > Red Hat Enterprise Linux Server release 6.2 (Santiago) > Linux 2.6.32-220.4.1.el6.x86_64 #1 SMP Thu Jan 19 14:50:54 EST > 2012 x86_64 x86_64 x86_64 GNU/Linux >Reporter: Darren Weber >Assignee: Nicolas De Loof >Priority: Blocker > Labels: git, startup > > org.jvnet.hudson.reactor.ReactorException: java.lang.Error: > java.lang.reflect.InvocationTargetException > at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) > at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) > at jenkins.model.Jenkins.executeReactor(Jenkins.java:824) > at jenkins.model.Jenkins.(Jenkins.java:736) > at hudson.model.Hudson.(Hudson.java:81) > at hudson.model.Hudson.(Hudson.java:77) > at hudson.WebAppMain$2.run(WebAppMain.java:217) > Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException > at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) > at > hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) > at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) > at jenkins.model.Jenkins$5.runTask(Jenkins.java:813) > at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) > at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) > ... 8 more > Caused by: java.lang.NullPointerException > at hudson.plugins.git.GitTool.onLoaded(GitTool.java:74) > ... 13 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13394) Jenkins won't start, PerforceToolinstallation NPE
[ https://issues.jenkins-ci.org/browse/JENKINS-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13394. --- Resolution: Fixed Will be fixed in 1.462. See JENKINS-13448. > Jenkins won't start, PerforceToolinstallation NPE > - > > Key: JENKINS-13394 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13394 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: Linux, Jenkins 1.457 and 1.458 >Reporter: NetAppBlueDevil >Assignee: Rob Petti > Attachments: jenkins.log > > > Did my regular updating of plugins. Went from 1.3.10 to 1.3.12 for perforce, > now Jenkins produces this stack trace in the browser. The only way I can get > it to start up completely is to disable the perforce plugin. Backing out to > 1.3.10 did not resolve the problem. I think there is something now not right > in some config somewhere that is not being corrected on plugin install. > Help ... > org.jvnet.hudson.reactor.ReactorException: java.lang.Error: > java.lang.reflect.InvocationTargetException > at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) > at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) > at jenkins.model.Jenkins.executeReactor(Jenkins.java:849) > at jenkins.model.Jenkins.(Jenkins.java:761) > at hudson.model.Hudson.(Hudson.java:81) > at hudson.model.Hudson.(Hudson.java:77) > at hudson.WebAppMain$2.run(WebAppMain.java:217) > Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException > at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) > at > hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) > at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) > at jenkins.model.Jenkins$6.runTask(Jenkins.java:838) > at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) > at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) > 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:619) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) > ... 8 more > Caused by: java.lang.NullPointerException > at > hudson.plugins.perforce.PerforceToolInstallation.onLoaded(PerforceToolInstallation.java:66) > ... 13 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
