[JIRA] [git-parameter] (JENKINS-23188) Tag List Empty
Mike . commented on JENKINS-23188 Tag List Empty The git repo is hosted by our company. Unfortunately, SSH is not an option as only https can be used to access repos (via the smart http protocol). As I said: all other places where jenkins accesses our git repo work fine, so I guess there has to be some working example code around... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17825) Configure Job page makes IE10 crash down completely
Steven Christou commented on JENKINS-17825 Configure Job page makes IE10 crash down completely I created a pull request for this issue: https://github.com/jenkinsci/jenkins/pull/1358 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-24194) Build Pipeline Plugin: build cards in run are not aligned
Rostislav Svoboda created JENKINS-24194 Build Pipeline Plugin: build cards in run are not aligned Issue Type: Bug Affects Versions: current Assignee: Rostislav Svoboda Components: build-pipeline Created: 11/Aug/14 6:48 AM Project: Jenkins Priority: Major Reporter: Rostislav Svoboda This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-24059) NullPointerException on non-existent downstream builds
SCM/JIRA link daemon commented on JENKINS-24059 NullPointerException on non-existent downstream builds Code changed in jenkins User: Robert Sandell Path: src/main/java/com/sonyericsson/jenkins/plugins/bfa/model/FailureCauseBuildAction.java http://jenkins-ci.org/commit/build-failure-analyzer-plugin/39c6e9f00d3cead862d61530de694526118c1053 Log: Merge pull request #23 from ederst/master JENKINS-24059 Fixed NullPointerException on missing downstream project Compare: https://github.com/jenkinsci/build-failure-analyzer-plugin/compare/36165db74950...39c6e9f00d3c This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17116) gracefull job termination
Sandor Balazsi commented on JENKINS-17116 gracefull job termination Is there any progress on this issue? We are using jenkins to start a java based test framework. This tool has a couple of java shutdown hook defined that must be executed on the termination of java process. Due to this problem jenkins does not wait for the proper termination of our java process. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-20492) Re-Execute promotion button is gone
Rene Kok commented on JENKINS-20492 Re-Execute promotion button is gone Fix promoted-builds-2.18-20140807.061532-2.hpi worked for me. thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-24195) Faster permission lookups when having many unused AD-groups
Fredrik Persson created JENKINS-24195 Faster permission lookups when having many unused AD-groups Issue Type: Improvement Assignee: Unassigned Components: active-directory Created: 11/Aug/14 7:34 AM Description: The permission lookups gets slow when having (too) many registered AD-groups for the users. For many authorization strategies, there is only a small set of groups that are actually being used. It is therefore unnecessary to iterate over all registered AD-groups when we know that no rules for most groups will be found anyway. We are implementing a feature to make it optional for Jenkins to ignore Active Directory groups that are not being used by the active Authorization Strategy. Project: Jenkins Priority: Minor Reporter: Fredrik Persson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-24194) Build Pipeline Plugin: build cards in run are not aligned
Rostislav Svoboda updated JENKINS-24194 Build Pipeline Plugin: build cards in run are not aligned Change By: Rostislav Svoboda (11/Aug/14 7:53 AM) Description: BuildPipelinePlugin:buildcardsinrunarenotalignedItwouldbebettertohavecardsalignedtotheleftandexpandedtothefullwidth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-24194) Build Pipeline Plugin: build cards in run are not aligned
Rostislav Svoboda commented on JENKINS-24194 Build Pipeline Plugin: build cards in run are not aligned https://github.com/jenkinsci/build-pipeline-plugin/pull/50 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-24194) Build Pipeline Plugin: build cards in run are not aligned
Rostislav Svoboda commented on JENKINS-24194 Build Pipeline Plugin: build cards in run are not aligned For the record: we have quite long pipelines - 5 levels we have long job names and the length vary current align to the centre makes orientation in build cards quite unpleasant This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20815) Show Failed Status While the Build is Still In Progress
Pim Verkerk edited a comment on JENKINS-20815 Show Failed Status While the Build is Still In Progress I have the same issue on jenkins ver. 1.548. I could not find any issues with shared workspaces. My best guess is a hiccup in the connection between master/slave. Maybe this causes some issues on the master when deciding the status of a job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-24171) BFA is blindly adding text to gzipped log
Jaroslav Henner
commented on JENKINS-24171
BFA is blindly adding text to gzipped log
We are just using gzip on the log files. As written in the https://issues.jenkins-ci.org/browse/JENKINS-2551. Something like
{{
gzip /var/lib/jenkins/jobs/sync-images-rhel-7v0/builds/25/log
}}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-24171) BFA is blindly adding text to gzipped log
Jaroslav Henner edited a comment on JENKINS-24171 BFA is blindly adding text to gzipped log We are just using gzip on the log files. As written in the https://issues.jenkins-ci.org/browse/JENKINS-2551. Something like # gzip /var/lib/jenkins/jobs/sync-images-rhel-7v0/builds/25/log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20815) Show Failed Status While the Build is Still In Progress
Daniel Beck commented on JENKINS-20815 Show Failed Status While the Build is Still In Progress Needs to be reproduced with a recent version of Jenkins (e.g. 1.570+ or current LTS). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-24195) Faster permission lookups when having many unused AD-groups
Fredrik Persson commented on JENKINS-24195 Faster permission lookups when having many unused AD-groups Pull request: https://github.com/jenkinsci/active-directory-plugin/pull/10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-24171) BFA is blindly adding text to gzipped log
Daniel Beck updated JENKINS-24171 BFA is blindly adding text to gzipped log Assuming to be an issue with BFA opening log file non-gzipped until proven otherwise. Change By: Daniel Beck (11/Aug/14 10:27 AM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-9741) Copy artifact loses file permissions
ikedam commented on JENKINS-9741 Copy artifact loses file permissions What's the status of this issue? Copyartifact looks preserve file permissions. FilePathCopyMethod without enabling flatten still breaks file permissions, but there's no way for users to use FilePathCopyMethod. I think I can fix that, but there's no way to test that. Anyway, even if there are users who want FilePathCopyMethod fixed, another issue should be created. I plan to close this issue with 'Fixed'. Please let me know if there is still a problem to fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-24171) BFA is blindly adding text to gzipped log
Jaroslav Henner commented on JENKINS-24171 BFA is blindly adding text to gzipped log Daniel, I don't really know how this "feature" it is implemented, but I smell it is problem on both sides BFA should not append plaintext to compressed stream Jenkins should not hang when displaying gzipped log with trailing garbage at the end. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22654) Multi-configuration projects display with wrong Delivery Pipeline Stage Name
Justin Mason commented on JENKINS-22654 Multi-configuration projects display with wrong Delivery Pipeline Stage Name Yes, looks great! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-24171) BFA is blindly adding text to gzipped log
Daniel Beck commented on JENKINS-24171 BFA is blindly adding text to gzipped log Makes sense. Probably needs to throw on 0 returned from gz.skip(int) unless the parameter is also 0. However this seems to be a separate issue (robustness in the face of invalid input) and should be filed separately. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-24171) BFA is blindly adding text to gzipped log
Daniel Beck edited a comment on JENKINS-24171 BFA is blindly adding text to gzipped log Makes sense. Probably needs to throw on 0 returned from gz.skip(int) unless the parameter is also 0. However this seems to be a separate issue (robustness in the face of invalid input) and should be filed separately, as the solutions are independent (i.e. fixing BFA does not seem to depend on core fixes or something like that). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-24196) When gzipped log contains trailing garbage, the GET on the log enters endless loop.
Jaroslav Henner created JENKINS-24196 When gzipped log contains trailing garbage, the GET on the log enters endless loop. Issue Type: Bug Affects Versions: current Assignee: Tomas Westling Components: build-failure-analyzer Created: 11/Aug/14 11:32 AM Description: Jenkins has ability to diplay gunzip gzipped logs on the fly (https://issues.jenkins-ci.org/browse/JENKINS-2551) though doesn't natively compress the logs. The BFA doesn't expect that the logs can be compressed and appends a plaintext to the end log: diff (hexdump -C /var/lib/jenkins/jobs/sync-images-rhel-7v0/builds/25/log.gz.previous) (hexdump -C /var/lib/jenkins/jobs/sync-images-rhel-7v0/builds/25/log.gz) 2800,2801c2800,2805 aef0 07 81 6b fd bf f2 2a 01 00 |..k...*..| aef9 aef0 07 81 6b fd bf f2 2a 01 00 5b 42 46 41 5d 20 53 |..k...*..BFA S| af00 63 61 6e 6e 69 6e 67 20 62 75 69 6c 64 20 66 6f |canning build fo| af10 72 20 6b 6e 6f 77 6e 20 63 61 75 73 65 73 2e 2e |r known causes..| af20 2e 0a 2e 2e 0a 5b 42 46 41 5d 20 44 6f 6e 65 2e |.BFA Done.| af30 20 32 73 0a | 2s.| af34 This then breaks the displaying of the logs in the sense that every GET results in one core continuously loaded in endless loop. "Handling GET /job/sync-images-rhel-7v0/24/console : RequestHandlerThread10" daemon prio=10 tid=0x7f55c400b000 nid=0x3b4e runnable 0x7f56077f8000 java.lang.Thread.State: RUNNABLE at org.kohsuke.stapler.framework.io.LargeText$GzipAwareSession.skip(LargeText.java:437) at org.kohsuke.stapler.framework.io.LargeText.writeLogTo(LargeText.java:211) at hudson.console.AnnotatedLargeText.writeHtmlTo(AnnotatedLargeText.java:156) at hudson.model.Run.writeLogTo(Run.java:1351) 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:606) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24) at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.WhitespaceTag.doTag(WhitespaceTag.java:48) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at
[JIRA] [core] (JENKINS-24196) When gzipped log contains trailing garbage, the GET on the log enters endless loop.
Jaroslav Henner updated JENKINS-24196 When gzipped log contains trailing garbage, the GET on the log enters endless loop. Change By: Jaroslav Henner (11/Aug/14 11:33 AM) Component/s: core Component/s: build-failure-analyzer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant] (JENKINS-1640) Environment variables not passed through to Ant tasks
Stefan Thurnherr
commented on JENKINS-1640
Environment variables not passed through to Ant tasks
Ok I tried both ${env.PATH} and ${env.USER}, where both PATH and USER are listed under "Environment variables" at jenkins-instance/systemInfo. Used in an echo task they resolve correctly and print out the same (for USER) or similar value (for PATH: jdk location gets prefixed) as shown under jenkins-instance/systemInfo.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23263) Move hudson.tasks.junit to a bundled plugin
Jesse Glick assigned JENKINS-23263 to Jesse Glick Move hudson.tasks.junit to a bundled plugin Change By: Jesse Glick (11/Aug/14 12:05 PM) Assignee: OlegNenashev JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23263) Move hudson.tasks.junit to a bundled plugin
Jesse Glick started work on JENKINS-23263 Move hudson.tasks.junit to a bundled plugin Change By: Jesse Glick (11/Aug/14 12:05 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24175) Create some functional tests to test the l:icon tag to img translation
SCM/JIRA link daemon commented on JENKINS-24175 Create some functional tests to test the l:icon tag to img translation Code changed in jenkins User: tfennelly Path: test/src/test/java/lib/layout/IconTest.java test/src/test/resources/lib/layout/IconTest/01_testIcons.jelly test/src/test/resources/lib/layout/IconTest/02_testBallColorTd.jelly test/src/test/resources/lib/layout/IconTest/03_testTask.jelly http://jenkins-ci.org/commit/jenkins/51af70f2165a1662c4f962cbfeee625d01e1d929 Log: FIXED JENKINS-24175 Some functional tests for the icon tag This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24175) Create some functional tests to test the l:icon tag to img translation
SCM/JIRA link daemon resolved JENKINS-24175 as Fixed Create some functional tests to test the l:icon tag to img translation Change By: SCM/JIRA link daemon (11/Aug/14 12:25 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkinswalldisplay] (JENKINS-21900) Progress indicator does not function properly in certain conditions
Christian Pelster assigned JENKINS-21900 to Christian Pelster Progress indicator does not function properly in certain conditions Change By: Christian Pelster (11/Aug/14 12:38 PM) Assignee: ChristianPelster This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [walldisplay] (JENKINS-24192) Add HTTP Date response header to Jetty
Christian Pelster commented on JENKINS-24192 Add HTTP Date response header to Jetty As a temporary fix I will pass the server date via the plugins API to the walldisplay until this is sorted out This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkinswalldisplay] (JENKINS-21900) Progress indicator does not function properly in certain conditions
Christian Pelster commented on JENKINS-21900 Progress indicator does not function properly in certain conditions As a temporary fix I will pass the server date via the plugins API to the walldisplay until this is sorted out This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prescmbuildstep] (JENKINS-24197) extending inheritance plugin with support for preSCMbuildstep
Asmund Ostvold created JENKINS-24197 extending inheritance plugin with support for preSCMbuildstep Issue Type: New Feature Assignee: Unassigned Components: prescmbuildstep, project-inheritance Created: 11/Aug/14 12:43 PM Description: I want project-inheritance to support the preSCMbuildstep plugin. preSCMbuildstep extend: public class PreSCMBuildStepsWrapper extends BuildWrapper function: public void preCheckout(AbstractBuild build, Launcher launcher, BuildListener listener) I am willing to give it a try but am looking for comparable/commit code to read. If you feel you are want to implement this yourself I will be glad and can contribute with testing. Project: Jenkins Priority: Major Reporter: Asmund Ostvold This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [foofoo] (JENKINS-24198) Frequent Stackoverflow
Robin Rosenberg created JENKINS-24198 Frequent Stackoverflow Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: foofoo Created: 11/Aug/14 12:59 PM Description: Aug 11, 2014 2:51:33 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: job.buildHealthReports in /. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor153.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:276) at org.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92) at com.sun.proxy.$Proxy45.projectView(Unknown Source) at lib.JenkinsTagLib$projectView$0.call(Unknown Source) at hudson.model.View.main.run(main.groovy:14) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:74) at
[JIRA] [core] (JENKINS-22525) incompatible InnerClasses attribute error in IBM J9 VM
Jesse Glick commented on JENKINS-22525 incompatible InnerClasses attribute error in IBM J9 VM @dantran because it was committed toward 1.576. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-20276) Native Library Error after upgrading ssh-agent from 1.3 to 1.4
stephenconnolly commented on JENKINS-20276 Native Library Error after upgrading ssh-agent from 1.3 to 1.4 Yes!!! Ok, so that reproduces the issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng] (JENKINS-24176) Test result trend breaks lazy-loading
Jesse Glick commented on JENKINS-24176 Test result trend breaks lazy-loading You could use only the last 10 builds, though this would give less a useful graph: you might as well display information for builds you have at hand. The only “pro” I can think of is that the behavior is more consistent because it would always be showing the last 10 (or however many) builds regardless of what Jenkins had been doing before. Note that the build history widget loads the most recent 30 builds when you view the job index page, so these would usually be in memory anyway. The JENKINS-23945 fix, for JUnit results, is to display the trend for loaded builds. (More precisely, for all builds starting with the most recent and continuing backwards so long as they exist on disk and are loaded in memory.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Marc Reder commented on JENKINS-23779 Layout in 1.572 is broken in IE9 I still got this problem with 1.575 and IE8 on Win7 x86 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24175) Create some functional tests to test the l:icon tag to img translation
dogfood commented on JENKINS-24175 Create some functional tests to test the l:icon tag to img translation Integrated in jenkins_main_trunk #3598 FIXED JENKINS-24175 Some functional tests for the icon tag (Revision 51af70f2165a1662c4f962cbfeee625d01e1d929) Result = SUCCESS tom.fennelly : 51af70f2165a1662c4f962cbfeee625d01e1d929 Files : test/src/test/resources/lib/layout/IconTest/01_testIcons.jelly test/src/test/java/lib/layout/IconTest.java test/src/test/resources/lib/layout/IconTest/02_testBallColorTd.jelly test/src/test/resources/lib/layout/IconTest/03_testTask.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-24199) Post Build trigger parameterized job does not resolve variables used for job name
Lorelei McCollum created JENKINS-24199 Post Build trigger parameterized job does not resolve variables used for job name Issue Type: Bug Assignee: huybrechts Attachments: triggerjob.png Components: parameterized-trigger Created: 11/Aug/14 1:39 PM Description: When using the trigger parameterized build in a jenkins job, we like to use a variable for the job name and then that variable is part of the current jobs parameters So we build a job with paramters, pass it the name of the job to trigger inside the build section. This works great inside the build section, we can specify $JobName on the projects to build line However if we try to do the same thing in the PostBuild section it does not resolve the variable names. We would like it to also do variable resolution in post build trigger parameterized job You can see in the picture, this is what we would like to do, but it does not resolve the variable $JobName $JobName is a build variable of this current job. If we put this block into the Build section it does work, only post build has the problem Environment: Jenkins Ubuntu server 1.574 Project: Jenkins Priority: Minor Reporter: Lorelei McCollum This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-20276) Native Library Error after upgrading ssh-agent from 1.3 to 1.4
stephenconnolly
commented on JENKINS-20276
Native Library Error after upgrading ssh-agent from 1.3 to 1.4
Ok, I think I have the root cause.
The issue here is that Java, by default, can end up having the 32-bit library paths in the java.library.path system property and there is a bug in JNR's Platform.Linux:
@Override
public String locateLibrary(final String libName, ListString libraryPath) {
FilenameFilter filter = new FilenameFilter() {
Pattern p = Pattern.compile("lib" + libName + "\\.so\\.[0-9]+$");
String exact = "lib" + libName + ".so";
public boolean accept(File dir, String name) {
return p.matcher(name).matches() || exact.equals(name);
}
};
ListFile matches = new LinkedListFile();
for (String path : libraryPath) {
File[] files = new File(path).listFiles(filter);
if (files != null files.length 0) {
matches.addAll(Arrays.asList(files));
}
}
//
// Search through the results and return the highest numbered version
// i.e. libc.so.6 is preferred over libc.so.5
//
int version = 0;
String bestMatch = null;
for (File file : matches) {
String path = file.getAbsolutePath();
if (bestMatch == null path.endsWith(".so")) {
bestMatch = path;
version = 0;
} else {
String num = path.substring(path.lastIndexOf(".so.") + 4);
try {
if (Integer.parseInt(num) = version) {
bestMatch = path;
}
} catch (NumberFormatException e) {
} // Just skip if not a number
}
}
return bestMatch != null ? bestMatch : mapLibraryName(libName);
}
The bug being that it will return the last match is all the matches have the same version (I suspect it is that (Integer.parseInt(num) = version) should be (Integer.parseInt(num) version) but I am not currently sure, as I have yet to dig into this fully)
So what you need to ensure is that the library paths (if they include a mix of 64bit and 32bit libraries) are a palindrome, now the search path is a combination of four system properties in order:
jnr.ffi.library.path
jaffl.library.path
jna.library.path
java.library.path
So what you want to do is see what the combined path for all of those is... and then (since you are here because there is a 32bit lib on that path) reverse the path and append it to java.library.path
A quicker fix is to just remove the 32-bit folders from java.library.path
By way of example, if I go to the System Information page for my CentOS 6.5 slave, I see that it says:
java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
So I can either set the JVM options for that slave to include -Djava.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib:/lib:/lib64:/usr/lib64:/usr/java/packages/lib/amd64 (which is the palindrome trick) or I can simply remove the 32-bit directories from -Djava.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64
Either of these fixes the issue
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator created JENKINS-24200 All builds fail with E175002 Issue Type: Bug Assignee: Unassigned Components: subversion Created: 11/Aug/14 1:57 PM Description: ERROR: Failed to check out path to Subversion repository org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS path to Subversion repository failed None of the suggestions I've seen is any help. Environment: Windows Project: Jenkins Priority: Major Reporter: System Administrator This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-3982) Option to quietly skip publisher if test reports do not exist
Jesse Glick updated JENKINS-3982 Option to quietly skip publisher if test reports do not exist Probably better handled with the Conditional Build Step plugin, etc. Change By: Jesse Glick (11/Aug/14 1:57 PM) Summary: PublishJUnit Optiontoquietlyskippublisherif test resultreport reportsdonotexist This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator commented on JENKINS-24200 All builds fail with E175002 I upgraded Visual SVN Server to 2.7.7 and now I get this error on every job in Jenkins. I am able to check projects out with TortoiseSVN, I am able to log in to the Visual SVN website directly through a browser. I have a Windows Server with the Jenkins site on. If I try to configure the job to check files out I get this error message when supplying credentials. I've tried via the Job Configuration page and the Credentials page. The slave nodes are unable to checkout either. I have seen suggestions to add -Dsvnkit.http.sslProtocols="SSLv3 to the service, it said to add it to the jar command but the service on the slave nodes is an executable. I followed some instructions and added it to the slave config XML, that didn't work. (http://www.tikalk.com/alm/jenkins-svn-integration-bugs-and-workarounds) Some suggest running svn from the command line but the machines don't have it. I tried installing Tortoise and running it from there, I got the Subversion\auth folder they were talking about but it still doesn't work. Another said to modify the subversion config but didn't say where that is. Any helpful suggestions gratefully received, if you need more info let me know. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator edited a comment on JENKINS-24200 All builds fail with E175002 I upgraded Visual SVN Server to 2.7.7 and now I get this error on every job in Jenkins. I am able to check projects out with TortoiseSVN, I am able to log in to the Visual SVN website directly through a browser. I have a Windows Server with the Jenkins site on. If I try to configure the job to check files out I get this error message when supplying credentials. I've tried via the Job Configuration page and the Credentials page. The slave nodes are unable to checkout either. I have seen suggestions to add -Dsvnkit.http.sslProtocols="SSLv3 to the service, it said to add it to the jar command but the service on the slave nodes is an executable. I followed some instructions and added it to the slave config XML, that didn't work. (http://www.tikalk.com/alm/jenkins-svn-integration-bugs-and-workarounds) When I do svn checkout path to project I can check the files out but I don't get asked about a certificate. Some suggest running svn from the command line but the machines don't have it. I tried installing Tortoise and running it from there, I got the Subversion\auth folder they were talking about but it still doesn't work. Another said to modify the subversion config but didn't say where that is. Any helpful suggestions gratefully received, if you need more info let me know. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [next-executions] (JENKINS-23919) show also for poll SCM triggers
Michael Keppler commented on JENKINS-23919 show also for poll SCM triggers Sorry for the late answer. Yes, this should be sufficient for my use case. Thanks a lot. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-24201) All jnlp nodes go offline; require master reboot, sometimes followed by slave reboot.
James Noonan created JENKINS-24201 All jnlp nodes go offline; require master reboot, sometimes followed by slave reboot. Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: crash_aug_7_1930.log Components: master-slave Created: 11/Aug/14 2:18 PM Description: The Jenkins Master reports that all its JNLP (and all our nodes are such) are offline. On the nodes, they report that they are connected. The only way out is to restart the Master. Of the 6 (or so) times this has occurred, 1/2 the time all the slaves need to have their slave process restarted to recover. We also see cases where after a restarting Jenkins, it recovers for a short time. Then the problem re-occurs. However, if it's running 10-minutes after a restart, we seem to be fine for 3-4 days. We were running on version 565 when this first occurred. We ran fine for 3-months. What changed for us is that we increased the number of nodes. We now have 93 nodes, up from about 50. There was also an increase in the number of jobs. We use the vSphere Cloud Plugin. However, we changed one slave to use ssh instead of jnlp. The problem was resolved for this slave, and it is not disconnected when the problem occurs. We did not find the same for a vsphere/jnlp slave where we removed the vsphere configuration. (Well, recreated the slave without vsphere). This seems to be similar to: https://issues.jenkins-ci.org/browse/JENKINS-24155 https://issues.jenkins-ci.org/browse/JENKINS-24050 https://issues.jenkins-ci.org/browse/JENKINS-22714 https://issues.jenkins-ci.org/browse/JENKINS-22932 https://issues.jenkins-ci.org/browse/JENKINS-23384 We have examined the VM logs, the network logs and the firewalls. There is no obvious issue. I'm attaching the err.log of one of the incidents. Though it is clear that there is a problem with the slave connections, there is no clear 'cause'. Environment: Jenkins Native Install on Windows Server 2012, running on VM Sphere. Jenkins ver. 1.565.1 (Also, 1.563 and 1.570) Project: Jenkins Labels: slave Priority: Critical Reporter: James Noonan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator edited a comment on JENKINS-24200 All builds fail with E175002 I upgraded Visual SVN Server to 2.7.7 and now I get this error on every job in Jenkins. I am able to check projects out with TortoiseSVN, I am able to log in to the Visual SVN website directly through a browser. I have a Windows Server with the Jenkins site on. If I try to configure the job to check files out I get this error message when supplying credentials. I've tried via the Job Configuration page and the Credentials page. The slave nodes are unable to checkout either. I have seen suggestions to add -Dsvnkit.http.sslProtocols="SSLv3 to the service, it said to add it to the jar command but the service on the slave nodes is an executable. I followed some instructions and added it to the slave config XML, that didn't work. (http://www.tikalk.com/alm/jenkins-svn-integration-bugs-and-workarounds) When I do svn checkout path to project I can check the files out but I don't get asked about a certificate. (I'm using the SVN from Tortoise for that.) Some suggest running svn from the command line but the machines don't have it without installing something like TortoiseSVN. I tried installing Tortoise and running it from there, I got the Subversion\auth folder they were talking about but it still doesn't work. Another said to modify the subversion config but didn't say where that is. Any helpful suggestions gratefully received, if you need more info let me know. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-24201) All jnlp nodes go offline; require master reboot, sometimes followed by slave reboot.
James Noonan updated JENKINS-24201 All jnlp nodes go offline; require master reboot, sometimes followed by slave reboot. Change By: James Noonan (11/Aug/14 2:23 PM) Attachment: thread_growth.png Description: TheJenkinsMasterreportsthatallitsJNLP(andallournodesaresuch)areoffline.Onthenodes,theyreportthattheyareconnected.TheonlywayoutistorestarttheMaster.Ofthe6(orso)timesthishasoccurred,1/2thetimealltheslavesneedtohavetheirslaveprocessrestartedtorecover.WealsoseecaseswhereafterarestartingJenkins,itrecoversforashorttime.Thentheproblemre-occurs.However,ifitsrunning10-minutesafterarestart,weseemtobefinefor3-4days.Wewererunningonversion565whenthisfirstoccurred.Weranfinefor3-months.Whatchangedforusisthatweincreasedthenumberofnodes.Wenowhave93nodes,upfromabout50.Therewasalsoanincreaseinthenumberofjobs.WeusethevSphereCloudPlugin.However,wechangedoneslavetousesshinsteadofjnlp.Theproblemwasresolvedforthisslave,anditisnotdisconnectedwhentheproblemoccurs.Wedidnotfindthesameforavsphere/jnlpslavewhereweremovedthevsphereconfiguration.(Well,recreatedtheslavewithoutvsphere).Thisseemstobesimilarto:https://issues.jenkins-ci.org/browse/JENKINS-24155https://issues.jenkins-ci.org/browse/JENKINS-24050https://issues.jenkins-ci.org/browse/JENKINS-22714https://issues.jenkins-ci.org/browse/JENKINS-22932https://issues.jenkins-ci.org/browse/JENKINS-23384WehaveexaminedtheVMlogs,thenetworklogsandthefirewalls.Thereisnoobviousissue.Imattachingtheerr.logofoneoftheincidents.Thoughitisclearthatthereisaproblemwiththeslaveconnections,thereisnoclearcause. Iveattachedathreadgraphoftheproblem.Normally,Jenkinsrunsatabout200threads._AFTER_theproblemoccurs,threadgrowthoccurslinearlyuntilreboot.Inthegraph,weseetherewasaproblemonFridaynight,asactivitydiedoff.AfteraSatservicerestart,weseetheproblemoccuragain6-hourslater,withcorrespondingthreadgrowth.WesuspectthatifonlytheJenkinsServiceisrestarted,thetimetonextoccurrenceislower.Also,weconfiguresomenodestoturnoffwhenidle.However,thoughweoriginallysuspectedthistobeapossiblecause,wehavenotfoundanythingtofurthercollaboratethistheory. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Joshua Moody commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception I am seeing this as well. jenkins 1.575, 1.574 ghprb - 1.13, 1.13-1 GitHub Plugin - 1.9, 1.9.1 GitHub API plugin - 1.56 RE: more logs - I see the same logs as Frank K. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-24201) All jnlp nodes go offline; require master reboot, sometimes followed by slave reboot.
James Noonan updated JENKINS-24201 All jnlp nodes go offline; require master reboot, sometimes followed by slave reboot. Change By: James Noonan (11/Aug/14 2:48 PM) Attachment: Threaddump[Jenkins].htm Attachment: jnlp_output.log Description: TheJenkinsMasterreportsthatallitsJNLP(andallournodesaresuch)areoffline.Onthenodes,theyreportthattheyareconnected.TheonlywayoutistorestarttheMaster.Ofthe6(orso)timesthishasoccurred,1/2thetimealltheslavesneedtohavetheirslaveprocessrestartedtorecover.WealsoseecaseswhereafterarestartingJenkins,itrecoversforashorttime.Thentheproblemre-occurs.However,ifitsrunning10-minutesafterarestart,weseemtobefinefor3-4days.Wewererunningonversion565whenthisfirstoccurred.Weranfinefor3-months.Whatchangedforusisthatweincreasedthenumberofnodes.Wenowhave93nodes,upfromabout50.Therewasalsoanincreaseinthenumberofjobs.WeusethevSphereCloudPlugin.However,wechangedoneslavetousesshinsteadofjnlp.Theproblemwasresolvedforthisslave,anditisnotdisconnectedwhentheproblemoccurs.Wedidnotfindthesameforavsphere/jnlpslavewhereweremovedthevsphereconfiguration.(Well,recreatedtheslavewithoutvsphere).Thisseemstobesimilarto:https://issues.jenkins-ci.org/browse/JENKINS-24155https://issues.jenkins-ci.org/browse/JENKINS-24050https://issues.jenkins-ci.org/browse/JENKINS-22714https://issues.jenkins-ci.org/browse/JENKINS-22932https://issues.jenkins-ci.org/browse/JENKINS-23384WehaveexaminedtheVMlogs,thenetworklogsandthefirewalls.Thereisnoobviousissue.I mattaching vettached theerr.logofoneoftheincidents.Thoughitisclearthatthereisaproblemwiththeslaveconnections,thereisnoclearcause.Iveattachedathreadgraphoftheproblem. (Differentoccurence). Normally,Jenkinsrunsatabout200threads._AFTER_theproblemoccurs,threadgrowthoccurslinearlyuntilreboot.Inthegraph,weseetherewasaproblemonFridaynight,asactivitydiedoff.AfteraSatservicerestart,weseetheproblemoccuragain6-hourslater,withcorrespondingthreadgrowth.WesuspectthatifonlytheJenkinsServiceisrestarted,thetimetonextoccurrenceislower.Also,weconfiguresomenodestoturnoffwhenidle.However,thoughweoriginallysuspectedthistobeapossiblecause,wehavenotfoundanythingtofurthercollaboratethistheory. ThisgraphwasobtainedusingtheJavaMelodyPlugin;Wehavedisabledthisbuttheproblemhasre-occurred.(https://wiki.jenkins-ci.org/display/JENKINS/Monitoring)Iveattachedathreaddump.Again,Icannotseeanythingamissheremyself,butthisisnotmyareaofexpertise.Thethreaddumpisnotfromthesameincidentattheattachedlog.Iveattachedtheoutputfromoneofthejnlpslaves.ThereisaSEVEREerrorreportedattheslave,thoughitseemstorecover.Thisisnotfromthesametimeastheerrorlog. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-20276) Native Library Error after upgrading ssh-agent from 1.3 to 1.4
SCM/JIRA link daemon resolved JENKINS-20276 as Fixed Native Library Error after upgrading ssh-agent from 1.3 to 1.4 Change By: SCM/JIRA link daemon (11/Aug/14 2:52 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-20276) Native Library Error after upgrading ssh-agent from 1.3 to 1.4
SCM/JIRA link daemon commented on JENKINS-20276 Native Library Error after upgrading ssh-agent from 1.3 to 1.4 Code changed in jenkins User: Stephen Connolly Path: pom.xml http://jenkins-ci.org/commit/ssh-agent-plugin/f01905a36986880b94fb0e8ca368e37b11547149 Log: FIXED JENKINS-20276 Use a patched version of jnr-ffi While we await the merge of https://github.com/jnr/jnr-ffi/pull/23 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-20276) Native Library Error after upgrading ssh-agent from 1.3 to 1.4
stephenconnolly commented on JENKINS-20276 Native Library Error after upgrading ssh-agent from 1.3 to 1.4 1.4.2 has the fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-24201) All jnlp nodes go offline; require master reboot, sometimes followed by slave reboot.
James Noonan updated JENKINS-24201 All jnlp nodes go offline; require master reboot, sometimes followed by slave reboot. Change By: James Noonan (11/Aug/14 2:57 PM) Description: TheJenkinsMasterreportsthatallitsJNLP(andallournodesaresuch)areoffline.Onthenodes,theyreportthattheyareconnected.TheonlywayoutistorestarttheMaster.Ofthe6(orso)timesthishasoccurred,1/2thetimealltheslavesneedtohavetheirslaveprocessrestartedtorecover.WealsoseecaseswhereafterarestartingJenkins,itrecoversforashorttime.Thentheproblemre-occurs.However,ifitsrunning10-minutesafterarestart,weseemtobefinefor3-4days.Wewererunningonversion565whenthisfirstoccurred.Weranfinefor3-months.Whatchangedforusisthatweincreasedthenumberofnodes.Wenowhave93nodes,upfromabout50.Therewasalsoanincreaseinthenumberofjobs.WeusethevSphereCloudPlugin.However,wechangedoneslavetousesshinsteadofjnlp.Theproblemwasresolvedforthisslave,anditisnotdisconnectedwhentheproblemoccurs.Wedidnotfindthesameforavsphere/jnlpslavewhereweremovedthevsphereconfiguration.(Well,recreatedtheslavewithoutvsphere).Thisseemstobesimilarto:https://issues.jenkins-ci.org/browse/JENKINS-24155https://issues.jenkins-ci.org/browse/JENKINS-24050https://issues.jenkins-ci.org/browse/JENKINS-22714https://issues.jenkins-ci.org/browse/JENKINS-22932https://issues.jenkins-ci.org/browse/JENKINS-23384WehaveexaminedtheVMlogs,thenetworklogsandthefirewalls.Thereisnoobviousissue.Iveattachedtheerr.logofoneoftheincidents.Thoughitisclearthatthereisaproblemwiththeslaveconnections,thereisnoclearcause.Iveattachedathreadgraphoftheproblem.(Differentoccurence).Normally,Jenkinsrunsatabout200threads._AFTER_theproblemoccurs,threadgrowthoccurslinearlyuntilreboot.Inthegraph,weseetherewasaproblemonFridaynight,asactivitydiedoff.AfteraSatservicerestart,weseetheproblemoccuragain6-hourslater,withcorrespondingthreadgrowth.WesuspectthatifonlytheJenkinsServiceisrestarted,thetimetonextoccurrenceislower,thanifwerestartthejenkinsmasterhostmachine.Also,weconfiguresomenodestoturnoffwhenidle.However,thoughweoriginallysuspectedthistobeapossiblecause,wehavenotfoundanythingtofurthercollaboratethistheory.ThisgraphwasobtainedusingtheJavaMelodyPlugin;Wehavedisabledthisbuttheproblemhasre-occurred.(https://wiki.jenkins-ci.org/display/JENKINS/Monitoring)Iveattachedathreaddump.Again,Icannotseeanythingamissheremyself,butthisisnotmyareaofexpertise.Thethreaddumpisnotfromthesameincidentattheattachedlog.Iveattachedtheoutputfromoneofthejnlpslaves.ThereisaSEVEREerrorreportedattheslave,thoughitseemstorecover.Thisisnotfromthesametimeastheerrorlog. Intheerrorlog,Ibelievethatthisisthefirstsignoftheissue: Aug07,20147:30:20PMorg.jenkinsci.remoting.nio.NioChannelHubrunWARNING:Communicationproblemjava.io.IOException:Anexistingconnectionwasforciblyclosedbytheremotehost atsun.nio.ch.SocketDispatcher.read0(NativeMethod) atsun.nio.ch.SocketDispatcher.read(UnknownSource)Justpriortothis,aremoteslavesuccessfullycompletesajob.Ibelievethattheci-25b-linuxmessagesjustbeforethismessagesisnotrelated,asthisslavewasdisplayingproblemsinthetimeleadinguptothecrash. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-23645) Archiving artifacts does not preserve timestamps if filter is **
Timmy Brolin edited a comment on JENKINS-23645 Archiving artifacts does not preserve timestamps if filter is ** I was using java 1.6. Have now upgraded to 1.8. Makes no difference. Currently using Jenkins version 1.565. Will look into upgrading to the latest version tomorrow. CopyArtefact is version 1.31 I have however noticed the following: My setup is a 32bit windows 7 Jenkins master, and a 64bit windows 7 Jenkins slave. I run a multi-configuration job, and archive the results from all configurations. After the job is done, I manually check the archive folders in the jenkins master. The timestamps for the configurations that ran on the slave are fine. It is only the timestamps for the configurations that ran in the master which are incorrect. So the problem seems to be connected to running on 32bit windows, or to jobs running on the jenkins master... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-23645) Archiving artifacts does not preserve timestamps if filter is **
Timmy Brolin commented on JENKINS-23645 Archiving artifacts does not preserve timestamps if filter is ** I was using java 1.6. Have now upgraded to 1.8. Makes no difference. Currently using Jenkins version 1.565. Will look into upgrading to the latest version tomorrow. I have however noticed the following: My setup is a 32bit windows 7 Jenkins master, and a 64bit windows 7 Jenkins slave. I run a multi-configuration job, and archive the results from all configurations. After the job is done, I manually check the archive folders in the jenkins master. The timestamps for the configurations that ran on the slave are fine. It is only the timestamps for the configurations that ran in the master which are incorrect. So the problem seems to be connected to running on 32bit windows, or to jobs running on the jenkins master... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng] (JENKINS-24176) Test result trend breaks lazy-loading
SCM/JIRA link daemon resolved JENKINS-24176 as Fixed Test result trend breaks lazy-loading Change By: SCM/JIRA link daemon (11/Aug/14 3:09 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng] (JENKINS-24176) Test result trend breaks lazy-loading
SCM/JIRA link daemon commented on JENKINS-24176 Test result trend breaks lazy-loading Code changed in jenkins User: Nalin Makar Path: src/main/java/hudson/plugins/testng/TestNGProjectAction.java http://jenkins-ci.org/commit/testng-plugin-plugin/04fbebb13fba94bb40f695dd807908a81d19bb6a Log: Merge branch 'JENKINS-24176-lazy-load' of https://github.com/jglick/testng-plugin-plugin into jglick-JENKINS-24176-lazy-load This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng] (JENKINS-24176) Test result trend breaks lazy-loading
SCM/JIRA link daemon commented on JENKINS-24176 Test result trend breaks lazy-loading Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/testng/TestNGProjectAction.java http://jenkins-ci.org/commit/testng-plugin-plugin/feddedd3e7fa00c22cb7950661380c8f1520c5e6 Log: FIXED JENKINS-24176 Avoid loading builds from disk just to display test result trend. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng] (JENKINS-24176) Test result trend breaks lazy-loading
Nalin Makar commented on JENKINS-24176 Test result trend breaks lazy-loading Thanks for the information. I have merged the pull request and will do a release sometime today. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24012) Messages in RabbitMQ's queue was consumed but unacknowledged
SCM/JIRA link daemon commented on JENKINS-24012 Messages in RabbitMQs queue was consumed but unacknowledged Code changed in jenkins User: rinrinne Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/impls/RabbitMQMessageListenerImpl.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/impls/RabbitMQMessageListenerImplTest.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/5c25e280a39e555fb8f5d68276b897708afd674d Log: Wrong cast in RabbitMQ implementation Header values in RabbitMQ message is not String but library defined ByteArray. So it cannot be cast. Fix for JENKINS-24012 Task-Url: https://issues.jenkins-ci.org/browse/JENKINS-24012 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-21181) Build pipeline creating stack trace after logging on as non-admin user
Roel Kramer commented on JENKINS-21181 Build pipeline creating stack trace after logging on as non-admin user I have the same problem. My configuration is: Jenkins ver. 1.570 Build pipe line plugin: 1.4.3 Role-based Authorization Strategy: 2.2.0 avax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.570.jar!/hudson/model/View/index.jelly:42:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.570.jar!/lib/hudson/projectView.jelly:66:22: d:invokeBody null at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
[JIRA] [p4] (JENKINS-24005) Pin build at Perforce Label does not support variable expansion
Paul Allen closed JENKINS-24005 as Fixed Pin build at Perforce Label does not support variable expansion 1.0.10 Change By: Paul Allen (11/Aug/14 3:21 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Tom FENNELLY commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Hi Marc... I think your comment is more relevant to JENKINS-23921 (IE8) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23882) Long build startup
Paul Allen closed JENKINS-23882 as Fixed Long build startup 1.0.10 Change By: Paul Allen (11/Aug/14 3:22 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24101) Poll Watching Label Continually Triggering
Paul Allen closed JENKINS-24101 as Fixed Poll Watching Label Continually Triggering Fixed in 1.0.10 Please reopen if you find any issues. Change By: Paul Allen (11/Aug/14 3:24 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23921) new divs layout doesn't work with IE8
Tom FENNELLY commented on JENKINS-23921 new divs layout doesnt work with IE8 I think I have a solution to this issue (using respond.js - polyfills support for CSS3 media queries). Seems to work fine on the IE8 instance I'm testing against. Running tests now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-21181) Build pipeline creating stack trace after logging on as non-admin user
Roel Kramer edited a comment on JENKINS-21181 Build pipeline creating stack trace after logging on as non-admin user I have the same problem. My configuration is: Jenkins ver. 1.570 Build pipe line plugin: 1.4.3 Role-based Authorization Strategy: 2.2.0 RHEL: 6.5 avax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.570.jar!/hudson/model/View/index.jelly:42:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.570.jar!/lib/hudson/projectView.jelly:66:22: d:invokeBody null at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at
[JIRA] [p4] (JENKINS-24105) Test failures on windows
Paul Allen commented on JENKINS-24105 Test failures on windows This is a know p4 admin stop issue on Windows. I might need to add a delay as the process can hang around and lock files. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [foofoo] (JENKINS-24198) Frequent Stackoverflow
Robin Rosenberg
updated JENKINS-24198
Frequent Stackoverflow
Change By:
Robin Rosenberg
(11/Aug/14 3:28 PM)
Description:
IgetthiserrormessagewheneverIviewthejoblist
{noformat}Aug11,20142:51:33PMhudson.ExpressionFactory2$JexlExpressionevaluateWARNING:Caughtexceptionevaluating:job.buildHealthReportsin/.Reason:java.lang.reflect.InvocationTargetExceptionjava.lang.reflect.InvocationTargetException atsun.reflect.GeneratedMethodAccessor153.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:606) atorg.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) atorg.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) atorg.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) atorg.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) atorg.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) atorg.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) atorg.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) atorg.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) athudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) atorg.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) atorg.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) atorg.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) atorg.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) atorg.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) atorg.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) atorg.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) atorg.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:276) atorg.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92) atcom.sun.proxy.$Proxy45.projectView(UnknownSource) atlib.JenkinsTagLib$projectView$0.call(UnknownSource) athudson.model.View.main.run(main.groovy:14) atorg.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:74) atorg.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:62) atorg.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
[JIRA] [master-slave] (JENKINS-24201) All jnlp nodes go offline; require master reboot, sometimes followed by slave reboot.
evernat commented on JENKINS-24201 All jnlp nodes go offline; require master reboot, sometimes followed by slave reboot. As a side note, and since you have a high number of slaves, you may be aware that the monitoring plugin asks basic data from slaves, each minute by default. Since you also have what seems like communication issues with the slaves, you may note that you can keep the monitoring plugin but disable this "periodic monitoring of slaves" if you want (even at runtime). See Release notes for v1.52. This will not fix the communication issues with the slaves, but this may help to reduce the calls to the slaves and perhaps delay the time when the issue appears. If the issue is not related to the master-slave communication, this will of course not change anything. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24202) Pin Build at Label Does not Sync at the CL of the Label
Ryan Hummer created JENKINS-24202 Pin Build at Label Does not Sync at the CL of the Label Issue Type: Bug Affects Versions: current Assignee: Paul Allen Components: p4 Created: 11/Aug/14 3:48 PM Description: When triggering a job manually or via SCM Polling, the CL the job syncs it is not what the label has it's revision field set to. We use static labels so just the revision field is tagged for the label. The SCM Polling log correctly identifies all the CL's upto and including the CL that the label is tagged at. SCM Polling Log: Started on Aug 7, 2014 3:18:48 PM Polling SCM changes on rsmsnbuild114 P4: Polling with client: rsmsnbuild114 P4: Polling with label/change: latest_build_label ... found change: 978011 ... removing all the found CL#'s ... found change: 978233 Done. Took 1 min 0 sec Changes found Log from Job triggered by the SCM Polling: 15:19:48 Started by an SCM change 15:19:48 EnvInject - Loading node environment variables. 15:19:49 Building remotely on rsmsnbuild116 in workspace c:\trees 15:19:54 SCM Task: cleanup workspace: RSMSNBUILD116 15:19:54 SCM Task: syncing files at change: 979452 15:19:54 ... sync c:\trees/...@979452 15:19:54 ... force update false 15:19:54 ... bypass have false As you can see the CL of the label is 978233, while the job is actually syncing to 979452. Which is not desitred Project: Jenkins Priority: Critical Reporter: Ryan Hummer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23921) new divs layout doesn't work with IE8
SCM/JIRA link daemon commented on JENKINS-23921 new divs layout doesnt work with IE8 Code changed in jenkins User: tfennelly Path: core/src/main/resources/lib/layout/layout.jelly war/src/main/webapp/scripts/msie.js war/src/main/webapp/scripts/respond.js http://jenkins-ci.org/commit/jenkins/986a7a452e422a7fde2b8cd52c3d3f86345c0d53 Log: FIXED JENKINS-23921 new divs layout doesn't work with IE8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23921) new divs layout doesn't work with IE8
SCM/JIRA link daemon resolved JENKINS-23921 as Fixed new divs layout doesnt work with IE8 Change By: SCM/JIRA link daemon (11/Aug/14 3:48 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23921) new divs layout doesn't work with IE8
Tom FENNELLY commented on JENKINS-23921 new divs layout doesnt work with IE8 So I guess this fix should appear in 1.577 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24203) SCM Polling Throwing an exception
Ryan Hummer created JENKINS-24203 SCM Polling Throwing an exception Issue Type: Bug Affects Versions: current Assignee: Paul Allen Components: p4 Created: 11/Aug/14 3:50 PM Description: I am seeing this from our SCM Polling: Started on Aug 11, 2014 10:48:48 AM Polling SCM changes on rsmsnbuild114 P4: Polling with client: null ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@3b1c0865s1_databuild_ps4 com.perforce.p4java.exception.NullPointerError: Null client name passed to IServer.getClient() at com.perforce.p4java.impl.mapbased.server.Server.getClient(Server.java:2384) at org.jenkinsci.plugins.p4.client.ClientHelper.clientLogin(ClientHelper.java:57) at org.jenkinsci.plugins.p4.client.ClientHelper.init(ClientHelper.java:45) at org.jenkinsci.plugins.p4.PerforceScm.compareRemoteRevisionWith(PerforceScm.java:160) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1603) at hudson.model.AbstractProject._poll(AbstractProject.java:1573) at hudson.model.AbstractProject.poll(AbstractProject.java:1491) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) I first noticed it when looking at the polling log while a Job was in-flight. I am now seeing it with no Job running. Project: Jenkins Priority: Major Reporter: Ryan Hummer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24203) SCM Polling Throwing an exception
Paul Allen commented on JENKINS-24203 SCM Polling Throwing an exception Please can you confirm if this is 1.0.10 or the development (SNAPSHOT) version. There is a situation when polling could fail if there are no previous builds. If you try the Build Now button, does the polling log report a fail on subsequent polling? Thanks, Paul This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-24204) Archiving Maven artifacts fails if jenkins-cli is used to modify job config while job is running
Gianni ONeill created JENKINS-24204 Archiving Maven artifacts fails if jenkins-cli is used to modify job config while job is running Issue Type: Bug Assignee: Unassigned Components: maven Created: 11/Aug/14 3:59 PM Description: Steps to reproduce:- 1) Run a job which uses the maven plugin and has a "Deploy artifacts to maven repository" Post-build step 2) while the job is running use the jenkins-cli update-job command to change the job configuration (the configuration doesn't need to actually change. Calling update-job with the same config will also trigger the problem) When Jenkins attempts to deploy the artifacts it will give the error: Archiving artifacts [ERROR] No artifacts are recorded. Is this a Maven project? What seems to be happening is that the api call causes the cache in the AbstractLazyLoadRunMap for the module to get reloaded from disk. Meaning that when the build number check in MavenModuleSetBuild (line 486) actually looks at the last completed build, rather than the currently executing build and therefore returns false. Environment: Jenkins version: 1.572 OS: debian wheezy x64 maven-plugin: 2.5 Project: Jenkins Priority: Major Reporter: Gianni ONeill This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22654) Multi-configuration projects display with wrong Delivery Pipeline Stage Name
Patrik Boström commented on JENKINS-22654 Multi-configuration projects display with wrong Delivery Pipeline Stage Name Created PR https://github.com/Diabol/delivery-pipeline-plugin/pull/78 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24203) SCM Polling Throwing an exception
Ryan Hummer
updated JENKINS-24203
SCM Polling Throwing an exception
Change By:
Ryan Hummer
(11/Aug/14 4:01 PM)
Description:
IamseeingthisfromourSCMPolling:{quote}StartedonAug11,201410:48:48AMPollingSCMchangesonrsmsnbuild114P4:Pollingwithclient:nullERROR:FailedtorecordSCMpollingforhudson.model.FreeStyleProject@3b1c0865[
s1_databuild_ps4
job
]com.perforce.p4java.exception.NullPointerError:NullclientnamepassedtoIServer.getClient() atcom.perforce.p4java.impl.mapbased.server.Server.getClient(Server.java:2384) atorg.jenkinsci.plugins.p4.client.ClientHelper.clientLogin(ClientHelper.java:57) atorg.jenkinsci.plugins.p4.client.ClientHelper.init(ClientHelper.java:45) atorg.jenkinsci.plugins.p4.PerforceScm.compareRemoteRevisionWith(PerforceScm.java:160) athudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) athudson.scm.SCM.poll(SCM.java:373) athudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1603) athudson.model.AbstractProject._poll(AbstractProject.java:1573) athudson.model.AbstractProject.poll(AbstractProject.java:1491) athudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439) athudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468) athudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) atjava.util.concurrent.Executors$RunnableAdapter.call(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor.runWorker(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) atjava.lang.Thread.run(UnknownSource){quote}IfirstnoticeditwhenlookingatthepollinglogwhileaJobwasin-flight.IamnowseeingitwithnoJobrunning.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-24204) Archiving Maven artifacts fails if jenkins-cli is used to modify job config while job is running
Gianni ONeill
updated JENKINS-24204
Archiving Maven artifacts fails if jenkins-cli is used to modify job config while job is running
Change By:
Gianni ONeill
(11/Aug/14 4:03 PM)
Description:
Stepstoreproduce:-1)RunajobwhichusesthemavenpluginandhasaDeployartifactstomavenrepositoryPost-buildstep2)whilethejobisrunningusethejenkins-cliupdate-jobcommandtochangethejobconfiguration(theconfigurationdoesntneedtoactuallychange.Callingupdate-jobwiththesameconfigwillalsotriggertheproblem)WhenJenkinsattemptstodeploytheartifactsitwillgivetheerror:{noformat}Archivingartifacts[ERROR]Noartifactsarerecorded.IsthisaMavenproject?{noformat}WhatseemstobehappeningisthattheapicallcausesthecacheintheAbstractLazyLoadRunMapforthemoduletogetreloadedfromdisk.Meaningthat
when
thebuildnumbercheckinMavenModuleSetBuild(line486)actuallylooksatthelastcompletedbuild,ratherthanthecurrentlyexecutingbuildandthereforereturnsfalse.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
David Tanner updated JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Change By: David Tanner (11/Aug/14 4:07 PM) Affects Version/s: current Component/s: github Component/s: ghprb This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
David Tanner
commented on JENKINS-23641
Builds are failing due to GitHubCommitNotifier exception
This is something happening in the github plugin. Is it only happening when there isn't a previous build?
https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/com/cloudbees/jenkins/GitHubCommitNotifier.java
Bar.java
@Override
public boolean perform(AbstractBuild?, ? build, Launcher launcher, BuildListener listener) throws InterruptedException, IOException {
BuildData buildData = build.getAction(BuildData.class);
String sha1 = ObjectId.toString(buildData.getLastBuiltRevision().getSha1());
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step] (JENKINS-24205) Cannot COPY or ADD files during create image
Jarrod Kahn created JENKINS-24205 Cannot COPY or ADD files during create image Issue Type: Bug Affects Versions: current Assignee: vjuranek Components: docker-build-step Created: 11/Aug/14 4:14 PM Description: I am having trouble using the COPY and ADD commands in my Dockerfile, for some reason when I do something like this: ADD . /container/dir or ADD whatever.txt /container/dir or COPY . /container/dir The only thing it adds/copies is the Dockerfile, and not the rest of the contents of the build context. I've been poking around the source, but I cannot pinpoint what the issue could be. Caveat: My docker host is running on a different IP, and the jenkins instance is running inside a container on that host, but I'd think the docker REST client should still work in this case. Project: Jenkins Priority: Major Reporter: Jarrod Kahn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step] (JENKINS-24205) Cannot COPY or ADD files during create image
Jarrod Kahn commented on JENKINS-24205 Cannot COPY or ADD files during create image To me, it looks like the plugin is sending the whole dir, but I am not sure of the client implementation. https://github.com/jenkinsci/docker-build-step-plugin/blob/master/src/main/java/org/jenkinsci/plugins/dockerbuildstep/cmd/CreateImageCommand.java#L103 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-24201) All jnlp nodes go offline; require master reboot, sometimes followed by slave reboot.
James Noonan commented on JENKINS-24201 All jnlp nodes go offline; require master reboot, sometimes followed by slave reboot. Thank you evernat. We have disabled the monitoring plugin. Since disabling, the problem has re-occurred. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-1902) Provide Ability to Customize RSS Feed
russ k commented on JENKINS-1902 Provide Ability to Customize RSS Feed Any progress or related threads? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Joshua Moody commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception re: previous build Interesting. I had to blow away my workspace for a completely unrelated reason. Every build since has failed (b/c a vagrant box cannot be provisioned) and ended with the NPE describe above. Despite having several (failing) runs, I always see: "First time build. Skipping changelog." after the pull from GitHub. So, maybe it is only happening when there isn't a previous build. I will push on this a little harder later today. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23921) new divs layout doesn't work with IE8
dogfood commented on JENKINS-23921 new divs layout doesnt work with IE8 Integrated in jenkins_main_trunk #3600 FIXED JENKINS-23921 new divs layout doesn't work with IE8 (Revision 986a7a452e422a7fde2b8cd52c3d3f86345c0d53) Result = SUCCESS tom.fennelly : 986a7a452e422a7fde2b8cd52c3d3f86345c0d53 Files : war/src/main/webapp/scripts/respond.js war/src/main/webapp/scripts/msie.js core/src/main/resources/lib/layout/layout.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodeofflinenotification] (JENKINS-17917) Global configration of Node Offline Email doesn't work
Walter Kacynski closed JENKINS-17917 as Duplicate Global configration of Node Offline Email doesnt work Change By: Walter Kacynski (11/Aug/14 5:08 PM) Status: Open Closed Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-23160) Newly added module locations' / additional credentials' Add credential button does not work
SCM/JIRA link daemon commented on JENKINS-23160 Newly added module locations / additional credentials Add credential button does not work Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/com/cloudbees/jenkins/plugins/sshagent/SSHAgentBuildWrapper.java src/main/resources/com/cloudbees/jenkins/plugins/sshagent/Messages.properties src/main/resources/com/cloudbees/jenkins/plugins/sshagent/SSHAgentBuildWrapper/CredentialHolder/config.jelly src/main/resources/com/cloudbees/jenkins/plugins/sshagent/SSHAgentBuildWrapper/config.jelly http://jenkins-ci.org/commit/ssh-agent-plugin/3bc16fd5ecad520345f0c6d7095aed4098c2fd61 Log: Add support for multiple credentials (subject to JENKINS-23160 until we upgrade the credentials plugin dependency) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22525) incompatible InnerClasses attribute error in IBM J9 VM
Daniel Beck commented on JENKINS-22525 incompatible InnerClasses attribute error in IBM J9 VM Literally one click away: "Upcoming changes" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sbt] (JENKINS-22718) Getting a NullPointerException if sbt-launch.jar is not executable
Steven Goldsmith commented on JENKINS-22718 Getting a NullPointerException if sbt-launch.jar is not executable The new location is actually /usr/share/sbt-launcher-packaging/bin for sbt launcher version 0.13.5. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24206) Support for workflow plugins
Michael Rose created JENKINS-24206 Support for workflow plugins Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: p4, workflow Created: 11/Aug/14 5:18 PM Description: The new workflow-plugin for Jenkins looks like it may be just what we need to describe the tasks of a build process quickly and flexibly while also consolidating the outputs of the build into one place so that it is easy for end-users to find the information that they are looking for (e.g. console output, test results, build artifacts). I would like to try this plugin out to see if it lives up to the praise that Kohsuke and Jesse were giving it at their Boston conference. Unfortunately (as far as I know; correct me if I'm wrong), neither of the Perforce plugins currently support the workflow-plugin and with the release of the new P4 plugin, there is little appetite for any further development against the legacy plugin. Could the p4 plugin be updated to support the workflow-plugin? For information on what needs to be done to make this happen, see: https://github.com/jenkinsci/workflow-plugin/blob/master/scm-step/README.md Project: Jenkins Priority: Major Reporter: Michael Rose This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sbt] (JENKINS-22718) Getting a NullPointerException if sbt-launch.jar is not executable
Steven Goldsmith edited a comment on JENKINS-22718 Getting a NullPointerException if sbt-launch.jar is not executable The new location is actually /usr/share/sbt-launcher-packaging/bin for sbt launcher version 0.13.5. Even after you sudo chmod a+x /usr/share/sbt-launcher-packaging/bin/sbt-launch.jar you still get: FATAL: null java.lang.NullPointerException at org.jvnet.hudson.plugins.SbtPluginBuilder.buildCmdLine(SbtPluginBuilder.java:159) at org.jvnet.hudson.plugins.SbtPluginBuilder.perform(SbtPluginBuilder.java:111) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1710) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-24207) Use Perforce Jobs attached to changelist to track JIRA issues
John Versic created JENKINS-24207 Use Perforce Jobs attached to changelist to track JIRA issues Issue Type: Improvement Assignee: Unassigned Components: jira Created: 11/Aug/14 5:21 PM Description: The current JIRA plugin appears to search for issues in the change description. In the case of using Perforce, jobs relating to the issues are attached and not part of the change description. See: http://stackoverflow.com/questions/2276984/problem-with-hudson-jira-perforce-integration Project: Jenkins Priority: Major Reporter: John Versic This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sbt] (JENKINS-22718) Getting a NullPointerException if sbt-launch.jar is not executable
Steven Goldsmith edited a comment on JENKINS-22718 Getting a NullPointerException if sbt-launch.jar is not executable The new location is actually /usr/share/sbt-launcher-packaging/bin for sbt launcher version 0.13.5. chmod a+r /usr/share/sbt-launcher-packaging/bin/sbt-launch.jar is not required since it's already set, but you still get: FATAL: null java.lang.NullPointerException at org.jvnet.hudson.plugins.SbtPluginBuilder.buildCmdLine(SbtPluginBuilder.java:159) at org.jvnet.hudson.plugins.SbtPluginBuilder.perform(SbtPluginBuilder.java:111) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1710) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14752) SCM Polling / Max # of concurrent polling = 1 hangs github polling
Rob Duff commented on JENKINS-14752 SCM Polling / Max # of concurrent polling = 1 hangs github polling Something similar is happening with me, although it has nothing to do with the "max # of concurrent polling" setting in my case. The ssh process gets hung up when it runs "git-upload-pack". It seems to happen when we're grabbing the same repo on another executor on the same machine at the exact same time. It makes me think that this is the same issue as what you're seeing, but manifested by different means. Another problem we get when we grab the same repo on the same machine at the same time is https://issues.jenkins-ci.org/browse/JENKINS-24179. I won't go so far as to say that they are the same issue, but it has some potential to be somehow related. If that is the case, then it might be a git/ssh concurrency issue and not so much of a Jenkins issue. But I can't reproduce this outside of Jenkins yet, so... I can't really say for sure. I'd be interested to know if the other cases happen to have the same repo accessed at the same time on the same machine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-23645) Archiving artifacts does not preserve timestamps if filter is **
Daniel Beck commented on JENKINS-23645 Archiving artifacts does not preserve timestamps if filter is ** Makes sense. FilePath.copyRecursiveTo(DirScanner,FilePath,String) behaves differently when it's a master local copy: In that case, it simply copies the files over using IOUtils.mkdirs/Util.copyFile (which in turn uses org.apache.tools.ant.taskdefs.Copy without preservelastmodified). In the remote case, it creates a Tar archive and transfers it over the remoting channel, extracting on the master. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22654) Multi-configuration projects display with wrong Delivery Pipeline Stage Name
Patrik Boström resolved JENKINS-22654 as Fixed Multi-configuration projects display with wrong Delivery Pipeline Stage Name Merged to master Change By: Patrik Boström (11/Aug/14 5:36 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
