[JIRA] [maven-plugin] (JENKINS-26472) Jenkins maven-project plugin doesn't support reactor module exclusion
Andreas Horst commented on JENKINS-26472 Jenkins maven-project plugin doesn't support reactor module exclusion Yes, actually I agree with you. I was kind of hit by the Stockholm Syndrome and did not think about simply switching to the regular job type. 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-plugin] (JENKINS-27270) Support jobs organized under folders
Stephan Pauxberger resolved JENKINS-27270 as Fixed Support jobs organized under folders Merged (should be in 0.8.11) Change By: Stephan Pauxberger (23/Mar/15 8:46 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-27539) NPE when using jobs with the same name in different folders
Stephan Pauxberger resolved JENKINS-27539 as Fixed NPE when using jobs with the same name in different folders Merged (should be in 0.8.11) Change By: Stephan Pauxberger (23/Mar/15 8:46 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-27100) Regressions in 1.12 and 1.13
Brice Ruzand commented on JENKINS-27100 Regressions in 1.12 and 1.13 For myself, I build the plug-in from the sources, install the hpi manually and everything is working well. 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] [sauce-ondemand-plugin] (JENKINS-27111) Sauce Connect intermittently fails to launch
Alex White commented on JENKINS-27111 Sauce Connect intermittently fails to launch Thanks Ross, I have logged a support ticket, although, we are not running through a proxy as our connection is direct. I have noticed that there is a sauce-ondemand plugin update which I am installing to see if this will resolve 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] [gradle-jpi-plugin] (JENKINS-27451) All .properties files are being compiled by localizer, rather than just Messages.properties
Daniel Spilker resolved JENKINS-27451 as Fixed All .properties files are being compiled by localizer, rather than just Messages.properties Change By: Daniel Spilker (23/Mar/15 9:37 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-27451) All .properties files are being compiled by localizer, rather than just Messages.properties
Daniel Spilker closed JENKINS-27451 as Fixed All .properties files are being compiled by localizer, rather than just Messages.properties Released in 0.10.1. Change By: Daniel Spilker (23/Mar/15 9:37 AM) Status: Resolved Closed 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-publish-plugin] (JENKINS-25690) Pull base docker image to make sure it's up to date
Michael Neale resolved JENKINS-25690 as Fixed Pull base docker image to make sure it's up to date Change By: Michael Neale (23/Mar/15 10:25 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-11853) Duplicate build numbers in the Build History
Holger Schmidt commented on JENKINS-11853 Duplicate build numbers in the Build History We had the same issue on v1.480.3. My analyzis showed the following: The actual job was copied via the Jenkins UI. After a Jenkins reboot the wrong job history showed up. This wrong history was the old history from the original Job. The build folder of the new job practically contained the build history of the original and the new job. Since the old job had the higher build number those were taken by the Jenkins UI. This also explains the older date 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-27541) Connection disconnected when use HA-Proxy to route ports
Xiaokun Hou created JENKINS-27541 Connection disconnected when use HA-Proxy to route ports Issue Type: Bug Assignee: Unassigned Components: core Created: 23/Mar/15 10:38 AM Description: I deployed jenkins in mesos cluster. And to make sure, slave are always connected to a stable url. I used HA-proxy to route the url to a fixed one. (main url and JNLP port). It works for little job. But for some long running job, job will failed because of disconnection between master and slave. Error are, java.io.EOFException at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:616) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Environment: Ubuntu Master and Windows Slave. Project: Jenkins Priority: Blocker Reporter: Xiaokun Hou 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] [ec2-plugin] (JENKINS-26797) Zombie instance created by the EC2 plugins
Christoph Beckmann commented on JENKINS-26797 Zombie instance created by the EC2 plugins Had a SNAPSHOT version running in our production systems for over 3 days. No zombies instances in last 3 days. Still waiting for merge: https://github.com/jenkinsci/ec2-plugin/pull/140 SNAPSHOT version with fix available under: https://buildhive.cloudbees.com/job/jenkinsci/job/ec2-plugin/99/org.jenkins-ci.plugins$ec2/ 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-plugin] (JENKINS-26787) Upgrade p4java to 2014.1
Paul Allen commented on JENKINS-26787 Upgrade p4java to 2014.1 Hi Brandon, I have been out on vacation for the last week and just catching up on all the email. You are welcome to use Perforce support as they will always be available. If it is a plugin specific issue as I'm the main developer they will likely have to ask me for assistance. I had a closer look at your forum post and the error does not look like it originates from Perforce or the plugin. Do you have a broker running or set the configurables 'minClient' and 'minClientMessage'? If you raise a Support ticket please reference the Jenkins Issue URL and forum link to help the support team. Kind regards, 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] [sauce-ondemand-plugin] (JENKINS-27111) Sauce Connect intermittently fails to launch
Alex White edited a comment on JENKINS-27111 Sauce Connect intermittently fails to launch Thanks Ross, I have logged a support ticket, although, we are not running through a proxy as our connection is direct. I have noticed that there is a sauce-ondemand plugin update which I am installing to see if this will resolve the issue. edit: 1.121 has resolved 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] [build-name-setter-plugin] (JENKINS-27542) Pass parent job name to triggered jobs
Jo Shields created JENKINS-27542 Pass parent job name to triggered jobs Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: build-name-setter-plugin Created: 23/Mar/15 12:07 PM Description: I have a job monitoring a git repository, which triggers jobs which are not looking at git. I currently rename builds on the git job to the abbreviated sha1. I would like to rename the child jobs too. I can't use a parameter file or environment variable, as the file i have created with the hash in it doesn't exist until after the copy artefact plugin has operated, during the build steps - which is too late. There should be a simple PARENT_JOB_NAME variable I can use. Project: Jenkins Priority: Minor Reporter: Jo Shields 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] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Peter Kline commented on JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin We changed the branch specifier to various things with no luck. Not sure if its the same as the bug you mention but after downgrading to 2.3.2 (was the automatic selection in the plugin manager) The output now changed to include a second poll line and it now works: Started on Mar 23, 2015 8:39:04 AM Using strategy: Default [poll] Last Built Revision: Revision 50f93f0d454e1361d54224c2510b8bbe10c031d6 (refs/remotes/origin/release_team1) > /usr/bin/git --version # timeout=10 > /usr/bin/git -c core.askpass=true ls-remote -h git@thoroughbred:flt/root.git refs/heads/release_team1 # timeout=10 [poll] Latest remote head revision is: 7a55640ade424c9f730b21d06e483f1ed2626975 Done. Took 1.5 sec Changes found 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] [git-plugin] (JENKINS-27543) GIT_COMMIT contains branch name instead of SHA1 (conflict with documentation)
Mario Camou created JENKINS-27543 GIT_COMMIT contains branch name instead of SHA1 (conflict with documentation) Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 23/Mar/15 12:46 PM Description: We have a build triggered by Git branch */master. The documentation at https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin states that the GIT_COMMIT variable contains the SHA of the commit used to trigger the build. However, in our case the value of GIT_COMMIT is 'master'. We need to have the actual SHA for some of our automation. Environment: Jenkins version 1.585 Relevant plugins: git 2.2.7 git-client 1.11.0 Project: Jenkins Priority: Minor Reporter: Mario Camou 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] [repo-plugin] (JENKINS-17913) Need to evaluate ${param} in any configuration fields
Makson Lee
commented on JENKINS-17913
Need to evaluate ${param} in any configuration fields
So when would the fix be available in release version?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-26740) Failed to set Jenkins Identity header on email. java.lang.NullPointerException
podskalsky commented on JENKINS-26740 Failed to set Jenkins Identity header on email. java.lang.NullPointerException the problem is still existing at Mailer 1.15 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-plugin] (JENKINS-26472) Jenkins maven-project plugin doesn't support reactor module exclusion
Maxsoel Alberton commented on JENKINS-26472 Jenkins maven-project plugin doesn't support reactor module exclusion Hi, I should set sub-projects to build in place of sub-project that isn't to build. That's right? 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-23272) java.io.IOException: remote file operation failed remote slave Unable to delete
podskalsky assigned JENKINS-23272 to Unassigned java.io.IOException: remote file operation failed remote slave Unable to delete I'm not a maintainer Change By: podskalsky (23/Mar/15 1:09 PM) Assignee: podskalsky 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-27525) Invoke top-level Maven targets fails for Maven 3.3.1 on Windows machine
twolfart commented on JENKINS-27525 Invoke top-level Maven targets fails for Maven 3.3.1 on Windows machine The reasone for the change from .bat do .cmd is MNG-5776. 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] [cobertura-plugin] (JENKINS-27544) Underscores in Floats
Basti Funck created JENKINS-27544 Underscores in Floats Issue Type: Bug Assignee: stephenconnolly Components: cobertura-plugin Created: 23/Mar/15 1:34 PM Description: If in a java source file a float literal is written with underscores like "12_000.0f", the jenkins build fails because Corbertura throws an exception: net.sourceforge.cobertura.javancss.parser.ParseException: Encountered " ".0f "" at line 90, column 111. Was expecting one of: "instanceof" ... ")" ... "," ... "=" ... ">" ... "<" ... "?" ... "==" ... "<=" ... ">=" ... "!=" ... "||" ... "&&" ... "++" ... "--" ... "+" ... "-" ... "*" ... "/" ... "&" ... "|" ... "^" ... "%" ... "+=" ... "-=" ... "*=" ... "/=" ... "&=" ... "|=" ... "^=" ... "%=" ... "<<=" ... ">>=" ... ">>>=" ... ">" ... at net.sourceforge.cobertura.javancss.parser.JavaParser.generateParseException(JavaParser.java:11869) at net.sourceforge.cobertura.javancss.parser.JavaParser.jj_consume_token(JavaParser.java:11730) at net.sourceforge.cobertura.javancss.parser.JavaParser.Arguments(JavaParser.java:3539) at net.sourceforge.cobertura.javancss.parser.JavaParser.PrimarySuffix(JavaParser.java:3434) at net.sourceforge.cobertura.javancss.parser.JavaParser.PrimaryExpression(JavaParser.java:3307) at net.sourceforge.cobertura.javancss.parser.JavaParser.PostfixExpression(JavaParser.java:3254) at net.sourceforge.cobertura.javancss.parser.JavaParser.UnaryExpressionNotPlusMinus(JavaParser.java:3162) at net.sourceforge.cobertura.javancss.parser.JavaParser.UnaryExpression(JavaParser.java:3096) at net.sourceforge.cobertura.javancss.parser.JavaParser.MultiplicativeExpression(JavaParser.java:3016) at net.sourceforge.cobertura.javancss.parser.JavaParser.AdditiveExpression(JavaParser.java:2988) at net.sourceforge.cobertura.javancss.parser.JavaParser.ShiftExpression(JavaParser.java:2955) at net.sourceforge.cobertura.javancss.parser.JavaParser.RelationalExpression(JavaParser.java:2919) at net.sourceforge.cobertura.javancss.parser.JavaParser.InstanceOfExpression(JavaParser.java:2906) at net.sourceforge.cobertura.javancss.parser.JavaParser.AssigmentExpression(JavaParser.java:2889) at net.sourceforge.cobertura.javancss.parser.JavaParser.EqualityExpression(JavaParser.java:2817) at net.sourceforge.cobertura.javancss.parser.JavaParser.AndExpression(JavaParser.java:2792) at net.sourceforge.cobertura.javancss.parser.JavaParser.ExclusiveOrExpression(JavaParser.java:2776) at net.sourceforge.cobertura.javancss.parser.JavaParser.InclusiveOrExpression(JavaParser.java:2760) at net.sourceforge.cobertura.javancss.parser.JavaParser.ConditionalAndExpression(JavaParser.java:2743) at net.sourceforge.cobertura.javancss.parser.JavaParser.ConditionalOrExpression(JavaParser.java:2726) at net.sourceforge.cobertura.javancss.parser.JavaParser.ConditionalExpression(JavaParser.java:2710) at net.sourceforge.cobertura.javancss.parser.JavaParser._expression_(JavaParser.java:2654) at net.sourceforge.cobertura.javancss.parser.JavaParser.VariableInitializer(JavaParser.java:1697) at net.sourceforge.cobertura.javancss.parser.JavaParser.VariableDeclarator(JavaParser.java:1626) at net.sourceforge.cobertura.javancss.parser.JavaParser.LocalVariableDeclaration(JavaParser.java:3941) at net.sourceforge.cobertura.javancss.parser.JavaParser.BlockStatement(JavaParser.java:3862) at net.sourceforge.cobertura.javancss.parser.JavaParser.Block(JavaParser.java:3855) at net.sourceforge.cobertura.javancss.parser.JavaParser.Statement(JavaParser.java:3684) at net.sourceforge.cobertura.javancss.parser.JavaParser.ForStatement(JavaParser.java:4370) at net.sourceforge.cobertura.javancss.parser.JavaParser.Statement(JavaParser.java:3735) at net.sourceforge.cobertura.javancss.parser.JavaParser.BlockStatement(JavaParser.java:3906) at net.sourceforge.cobertura.javancss.parser.JavaParser.Block(JavaParser.java:3855) at net.sourceforge.cobertura.javancss.parser.JavaParser.Statement(JavaParser.java:3684) at net.
[JIRA] [performance-plugin] (JENKINS-27100) Regressions in 1.12 and 1.13
Francis O'Briant commented on JENKINS-27100 Regressions in 1.12 and 1.13 We were having some trouble with some of the tests failing. We ended up downgrading to 1.11 since we needed it back up quickly. 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-plugin] (JENKINS-27545) ghprbPullLink incorrectly links to https://api.github.com/repos/.....
Trevor Baker created JENKINS-27545 ghprbPullLink incorrectly links to https://api.github.com/repos/. Issue Type: Bug Assignee: Honza Brázdil Components: ghprb-plugin Created: 23/Mar/15 1:43 PM Description: The ghprbPullLink is incorrectly linking to api.github.com is some circumstances. Incorrect: https://api.github.com/repos/org-here/repo-here/pulls/1234 The prior behavior which is correct for our usage: https://github.com/org-here/repo-here/pull/1234 Different builds show either result depending on how it was triggered. It seems when the build starts via a "retest this please" regex match we get the incorrect url. When the build is triggered by an initial pull request it is correct and can be resolved. Environment: ghprb 1.16-8 Jenkins ver. 1.605 Project: Jenkins Priority: Minor Reporter: Trevor Baker 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] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Peter Kline resolved JENKINS-27491 as Duplicate kicking off of build via curl command not working in 1.16.1 version of plugin Dup of JENKINS-27332. Downgrade to 2.3.2 of the git plugin worked Change By: Peter Kline (23/Mar/15 1:49 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [compress-artifacts-plugin] (JENKINS-27522) Unable to compress artifacts with non-IBM437 characters in filename
SCM/JIRA link daemon commented on JENKINS-27522 Unable to compress artifacts with non-IBM437 characters in filename Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/plugins/compress_artifacts/ZipStorage.java src/test/java/org/jenkinsci/plugins/compress_artifacts/ZipStorageTest.java http://jenkins-ci.org/commit/compress-artifacts-plugin/74c1a8cc5490c763134bc2060fdd7dfea3b5d6c5 Log: [FIXED JENKINS-27522] Archive artifacts with non-ascii chars in path 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] [compress-artifacts-plugin] (JENKINS-27522) Unable to compress artifacts with non-IBM437 characters in filename
SCM/JIRA link daemon resolved JENKINS-27522 as Fixed Unable to compress artifacts with non-IBM437 characters in filename Change By: SCM/JIRA link daemon (23/Mar/15 2:37 PM) Status: In Progress 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-27546) Load the output of /script asynchronously not to discard the script in case of request timeout
Oliver Gondža created JENKINS-27546 Load the output of /script asynchronously not to discard the script in case of request timeout Issue Type: Improvement Assignee: Unassigned Components: core Created: 23/Mar/15 2:42 PM Project: Jenkins Priority: Minor Reporter: Oliver Gondža 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] [workflow-plugin] (JENKINS-27531) Stack overflow in WorkflowRun.reload after run ID migration
SCM/JIRA link daemon resolved JENKINS-27531 as Fixed Stack overflow in WorkflowRun.reload after run ID migration Change By: SCM/JIRA link daemon (23/Mar/15 2:58 PM) Status: In Progress 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] [workflow-plugin] (JENKINS-27531) Stack overflow in WorkflowRun.reload after run ID migration
SCM/JIRA link daemon commented on JENKINS-27531 Stack overflow in WorkflowRun.reload after run ID migration Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunTest.java aggregator/src/test/resources/org/jenkinsci/plugins/workflow/WorkflowRunTest/loadMigratedBuildRecord.zip job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java http://jenkins-ci.org/commit/workflow-plugin/bdf1260dcafaf43bac23ec5d76f01916bc432e64 Log: [FIXED JENKINS-27531] In 1.597+ Run.getId() is not reliable while it is still being loaded. 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] [workflow-plugin] (JENKINS-27531) Stack overflow in WorkflowRun.reload after run ID migration
SCM/JIRA link daemon commented on JENKINS-27531 Stack overflow in WorkflowRun.reload after run ID migration Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunTest.java aggregator/src/test/resources/org/jenkinsci/plugins/workflow/WorkflowRunTest/loadMigratedBuildRecord.zip job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java http://jenkins-ci.org/commit/workflow-plugin/b5617c56c3a03553cebffadcb188b788d0299869 Log: Merge pull request #97 from jglick/StackOverflowError-JENKINS-27531 JENKINS-27531 Run.id-related error in 1.597+ Compare: https://github.com/jenkinsci/workflow-plugin/compare/f9c921341006...b5617c56c3a0 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] [performance-plugin] (JENKINS-27547) Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException
Igor Iric created JENKINS-27547 Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException Issue Type: Bug Assignee: Manuel Carrasco Components: performance-plugin Created: 23/Mar/15 3:02 PM Description: After Jmeter Performance tests are run and success... When I go to Performance Trend Per Test Case, pictures of graphs are missing and when I click on missing picture to see Performance Trend for selected case i get this error and evil Jenkins. javax.servlet.ServletException: java.lang.Error: Unresolved compilation problem: Messages cannot be resolved at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 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:79) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecu
[JIRA] [job-dsl-plugin] (JENKINS-27548) Sporadic IOException: Failed to persist config
Andrew Kujtan created JENKINS-27548 Sporadic IOException: Failed to persist config Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 23/Mar/15 3:29 PM Description: When creating the projects, I am getting sporadic failures in the jenkins error log as seen below. Jobs then fail to be updated. INFO: createOrUpdateConfig for WebContent Mar 23, 2015 10:29:12 AM javaposse.jobdsl.plugin.JenkinsJobManagement updateExistingItem WARNING: Error writing updated item to file. java.io.IOException: Failed to persist config.xml at hudson.model.AbstractItem.updateByXml(AbstractItem.java:646) at javaposse.jobdsl.plugin.JenkinsJobManagement.updateExistingItem(JenkinsJobManagement.java:378) at javaposse.jobdsl.plugin.JenkinsJobManagement.createOrUpdateConfig(JenkinsJobManagement.java:123) at javaposse.jobdsl.dsl.DslScriptLoader.extractGeneratedJobs(DslScriptLoader.java:120) at javaposse.jobdsl.dsl.DslScriptLoader.runDslEngine(DslScriptLoader.java:97) at javaposse.jobdsl.plugin.ExecuteDslScripts.perform(ExecuteDslScripts.java:203) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:203) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1751) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:230) at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:191) at jenkins.util.xml.XMLUtils.safeTransform(XMLUtils.java:48) at hudson.model.AbstractItem.updateByXml(AbstractItem.java:641) ... 14 more Caused by: java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:430) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:383) at org.xml.sax.helpers.NewInstance.newInstance(NewInstance.java:82) at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:228) ... 17 more Environment: 1.605 Win64 Job DSL 1.30 Project: Jenkins Priority: Critical Reporter: Andrew Kujtan 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-27549) Job loading can be broken by a NPE in a build trigger
Yoann Dubreuil created JENKINS-27549 Job loading can be broken by a NPE in a build trigger Issue Type: Bug Assignee: Yoann Dubreuil Components: core Created: 23/Mar/15 4:10 PM Description: AbstractProject.onLoad() is failing to catch runtime exceptions from Trigger.start(). A bug in a plugin can therefore break job loading, like in JENKINS-27438 Environment: 1.605 Project: Jenkins Labels: robustness jenkins Priority: Major Reporter: Yoann Dubreuil 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-19743) Massive parallel builds sometimes cause errors in LogRotation
Nebu Kadnezar updated JENKINS-19743 Massive parallel builds sometimes cause errors in LogRotation We've built a Jenkins test project where we can reproduce the issue. Following requirements and project setup describes how you we can reproduce the error deterministically. Software requirements: Jenkins version 1.598 Build Flow Plugin version 0.9.1 Java version 1.7.0_72 C# Script execution engine version 3.8.10.0 C# Script BuildFlowPluginTest.cs Test environment: Jenkins master runs on a virtual machine with Windows 7 SP1 32 bit 8 Jenkins slaves physical machines with Windows7 SP1 64 bit 6 Jenkins slaves virtual machines with Windows 7 SP1 32 bit Jenkins projects We have two Jenkins Build Flow projects: StressTest_Job StressTest_Job_2 Both are executing the same StressTest_SubJob. Create a Build Flow project StressTest_Job and StressTestJob_2 with following configuration like on the screenshots (see attached StressTest_Job_config_1 - StressTest_Job_config_3). Create a Jenkins project job similar to the screenshots (see attached StressTest_SubJob_config_1 - StressTest_SubJob_config_3). The only difference to our configuration is the section "Source Code Management". Set this configuration to "None" and add on the section "Build\Command" a copy command which copies the "BuildFlowPluginTest.cs" to the Jenkins slave workspace for execution. Sample command code for the build section (Windows batch): @echo off xcopy /e "\\Server\project\ BuildFlowPluginTest.cs" %workspace% ping %Parameter% -n 10 cscs BuildFlowPluginTest.cs 1 ping %Parameter% -n 10 See also the attached C# script BuildFlowPluginTest.cs code. Change By: Nebu Kadnezar (23/Mar/15 4:14 PM) Attachment: BuildFlowPluginTest.cs Attachment: StressTest_Job_config_1.png Attachment: StressTest_Job_config_2.png Attachment: StressTest_Job_config_3.png Attachment: StressTest_SubJob_config_1.png Attachment: StressTest_SubJob_config_2.png Attachment: StressTest_SubJob_config_3.png 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-plugin] (JENKINS-27270) Support jobs organized under folders
James FitzGibbon commented on JENKINS-27270 Support jobs organized under folders I built the 0.8.11 snapshot and this does fix the problem. One small quirk though: I have a job structure like this: cookbooks/foo cookbooks/bar workers/cookbooks/style workers/cookbooks/unit workers/cookbooks/integration With this regex: cookbooks/(.+) All of these jobs show up in the view. I would have only expected foo and bar to be there. Anchoring the regex: ^cookbooks/(.+) Produces the desired results, but I'm unclear why the non-anchored pattern worked. I tested out the above on the regexplanet tester (http://www.regexplanet.com/advanced/java/index.html) and it works the way I expected it to (only foo and bar match whether the regex is anchored or not). Thanks for the quick update though. 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-plugin] (JENKINS-27550) Error communicating to server! Server Error
Serge Kalinin created JENKINS-27550 Error communicating to server! Server Error Issue Type: Bug Assignee: Patrik Boström Attachments: stacktrace.text Components: delivery-pipeline-plugin Created: 23/Mar/15 4:49 PM Description: We have simple setup, jenkins ver. 1.596.1, some test jobs and delivery pipeline plugin. After adding to pipline one or more builds and saving this, we can see at view screen message "Error communicating to server! Server Error". At console i see many attempts to get http://jenkins-test/view/test/api/json?_=1427128942050 (number changes any time). When i open that link i get stacktrace, i'll attach txt file with it Project: Jenkins Priority: Major Reporter: Serge Kalinin 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-plugin] (JENKINS-27550) Error communicating to server! Server Error
Serge Kalinin updated JENKINS-27550 Error communicating to server! Server Error Change By: Serge Kalinin (23/Mar/15 5:05 PM) Description: We have simple setup, jenkins ver. 1.596.1 and delivery pipe plugin ver. 0.8.10, some test jobs and delivery pipeline plugin . After adding to pipline one or more builds and saving this, we can see at view screen message "Error communicating to server! Server Error". At console i see many attempts to get http://jenkins-test/view/test/api/json?_=1427128942050 (number changes any time). When i open that link i get stacktrace, i'll attach txt file with it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-27550) Error communicating to server! Server Error
Serge Kalinin updated JENKINS-27550 Error communicating to server! Server Error Change By: Serge Kalinin (23/Mar/15 5:04 PM) Description: We have simple setup, jenkins ver. 1.596.1 and delivery pipe plugin ver. 0.8.10 , some test jobs and delivery pipeline plugin. After adding to pipline one or more builds and saving this, we can see at view screen message "Error communicating to server! Server Error". At console i see many attempts to get http://jenkins-test/view/test/api/json?_=1427128942050 (number changes any time). When i open that link i get stacktrace, i'll attach txt file with it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [python-plugin] (JENKINS-12483) Make Python Plugin work with Conditional BuildStep Plugin
Shane Gannon commented on JENKINS-12483 Make Python Plugin work with Conditional BuildStep Plugin Still a nice feature to support. Another workaround is the the scons plugin which run python code. 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] [python-plugin] (JENKINS-12483) Make Python Plugin work with Conditional BuildStep Plugin
Shane Gannon edited a comment on JENKINS-12483 Make Python Plugin work with Conditional BuildStep Plugin Still a nice feature to support. Another workaround is the the scons plugin which runs python code. 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] [ec2-plugin] (JENKINS-24359) Allow more than one cloud definition per region, to support multiple accounts using the same region.
Alex Gray commented on JENKINS-24359 Allow more than one cloud definition per region, to support multiple accounts using the same region. Can this guy be merged in? We have a separate account for each environment (all us-east-1), so we would benefit from this fix tremendously! Thanks for fixing this! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27447) LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page
Daryl Spartz commented on JENKINS-27447 LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page I built 2.3.6-snapshot (from master branch) and installed on our test system. The "oops" page still occurs: ... Caused by: java.lang.NullPointerException at java.text.SimpleDateFormat.parse(SimpleDateFormat.java:1439) at java.text.DateFormat.parse(DateFormat.java:364) at hudson.plugins.git.GitChangeSet.getTimestamp(GitChangeSet.java:209) 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-plugin] (JENKINS-26612) svn: absolutely unacceptably SLOW
Tim Jaacks updated JENKINS-26612 svn: absolutely unacceptably SLOW Change By: Tim Jaacks (23/Mar/15 5:39 PM) Priority: Major Critical 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] [shiningpanda-plugin] (JENKINS-27551) tox builder no longer working with tox 1.9.1 because pip is too old and upstream tox does not include the dependency
Vladimir Lu created JENKINS-27551 tox builder no longer working with tox 1.9.1 because pip is too old and upstream tox does not include the dependency Issue Type: Bug Assignee: Unassigned Components: shiningpanda-plugin Created: 23/Mar/15 5:53 PM Description: See https://bitbucket.org/hpk42/tox/issue/228/tox-doesnt-work-with-older-pip-versions for the description of the breakage. Two things that can be done: Bump the version of virtualenv and pip used in the plugin (should be done anyway IMO) Allow to specify the exact version of tox to use - and/or allow the usage of system tox This change basically renders our tox builds unusable until upstream fixes their problem, which is not great in an environment where all the versions are usually fixed. It would be very very nice to allow the system python (i.e. the python that is going to be used by the tox builder) to be used for all these packages as that would put the burden of maintaining their versions not on the plugin author but on the user of jenkins. Happy to create a pull request if that's what's necessary Project: Jenkins Priority: Major Reporter: Vladimir Lu 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] [hockeyapp-plugin] (JENKINS-27552) If deleting older verions, provide option for sorting
Brantone created JENKINS-27552 If deleting older verions, provide option for sorting Issue Type: Bug Assignee: Unassigned Components: hockeyapp-plugin Created: 23/Mar/15 6:17 PM Description: The default behaviour for HockeyApp is to sort by "version" to delete older versions, while normally this is fine, it causes a headache if going back to update a hotfix version and a lot of work has continued on Trunk/Mainline. Per : http://support.hockeyapp.net/kb/api/api-versions#delete-multiple-versions Can change the sort option to "date" Project: Jenkins Priority: Minor Reporter: Brantone 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] [sonar] (JENKINS-27553) ERROR: Publisher hudson.plugins.sonar.SonarPublisher aborted due to exception
Karthikeyan Krishnasamy created JENKINS-27553 ERROR: Publisher hudson.plugins.sonar.SonarPublisher aborted due to exception Issue Type: Bug Assignee: Sonar Team Components: sonar Created: 23/Mar/15 6:18 PM Description: Hi, We are trying to run sonar analysis report for our project. We are getting Classnot found exception. ERROR: Publisher hudson.plugins.sonar.SonarPublisher aborted due to exception java.lang.NoClassDefFoundError: hudson/maven/local_repo/PerJobLocalRepositoryLocator at hudson.plugins.sonar.SonarPublisher.executeSonar(SonarPublisher.java:354) at hudson.plugins.sonar.SonarPublisher.perform(SonarPublisher.java:309) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.ClassNotFoundException: hudson.maven.local_repo.PerJobLocalRepositoryLocator at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1375) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1078) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ... 11 more Please let me know what could be the cause of this issue. Environment: Jenkins ver. 1.585 JDK 1.6 Project: Jenkins Priority: Major Reporter: Karthikeyan Krishnasamy 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-plugin] (JENKINS-26612) svn: absolutely unacceptably SLOW
Daniel Beck edited a comment on JENKINS-26612 svn: absolutely unacceptably SLOW Pablob P I'm not even sure how to down grade to older version. Go to https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin, click the "archives" link, select any version from the list to download it (2.4.5, probably). Then, follow the instructions on https://wiki.jenkins-ci.org/display/JENKINS/Plugins#Plugins-Installingaspecificversion It would still be helpful to know whether this only affects 2.5, or also the older 2.4.x releases… 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-plugin] (JENKINS-26612) svn: absolutely unacceptably SLOW
Daniel Beck commented on JENKINS-26612 svn: absolutely unacceptably SLOW Pablob P I'm not even sure how to down grade to older version. Go to https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin, click the "archives" link, select any version from the list to download it (2.4.5, probably). Then, follow the instructions on https://wiki.jenkins-ci.org/display/JENKINS/Plugins (the wiki doesn't work for me right now, I don't know whether my edits took hold. Short version: Upload on the Advanced tab of the plugin manager in Jenkins.) It would still be helpful to know whether this only affects 2.5, or also the older 2.4.x releases… 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] [job-dsl-plugin] (JENKINS-26744) Support ALWAYS Continuation Condition in Multi-Phase Jobs
Christian Goetze commented on JENKINS-26744 Support ALWAYS Continuation Condition in Multi-Phase Jobs I guess if I want this fixed, I need to fork and contribute, eh? Can I buy you a beer instead, please 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-27549) Job loading can be broken by a NPE in a build trigger
Jesse Glick updated JENKINS-27549 Job loading can be broken by a NPE in a build trigger Change By: Jesse Glick (23/Mar/15 7:23 PM) Labels: jenkins robustness 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-27468) Jenkins exposes internal port on redirections
Pavel Batanov commented on JENKINS-27468 Jenkins exposes internal port on redirections I've deployed an old version of jenkins. Tried 1.596 and 1.590. Both had the same. But I think I get a clue. Nginx as a reverse proxy (http://nginx.org/ru/docs/http/ngx_http_proxy_module.html#proxy_redirect) by default replaces (in my case) http://10.0.0.19:8080/ to https://build.example.com/ as reverse proxy should do. But by some reason nginx get https://build.example.com:8080/ instead of http://10.0.0.19:8080/ so the replacements does not really occur Manually adding section proxy_redirecthttps://build.example.com:8080/ https://build.example.com/; helps to get rid of this bug. I'll try further investigations to be sure. 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] [ldap-plugin] (JENKINS-23214) LDAP Plugin occasionally does not connect LDAP server
Mark Nejman commented on JENKINS-23214 LDAP Plugin occasionally does not connect LDAP server No updates as far as I can tell. I did add the com.sun.jndi.ldap.connect.timeout and com.sun.jndi.ldap.read.timeout parameters though, with values of 5 and 10 respectively. I think it has helped. I'm not experiencing this issue as frequently. 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-27468) Jenkins exposes internal port on redirections
Pavel Batanov commented on JENKINS-27468 Jenkins exposes internal port on redirections I've tried to make extended loggin of upstream (jenkins) server and logs really says me that Jenkins return https://build.example.com:8080/log/ for Location header. Could this be a JRE bug, for example, as soon it is the same even for very old versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27554) IllegalStateException printed after canceling build
Jesse Glick created JENKINS-27554 IllegalStateException printed after canceling build Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 23/Mar/15 8:15 PM Description: ... jenkins.util.ErrorLoggingScheduledThreadPoolExecutor afterExecute WARNING: failure in task not wrapped in SafeTimerTask java.lang.IllegalStateException: Already completed at org.jenkinsci.plugins.workflow.cps.CpsStepContext.onFailure(CpsStepContext.java:310) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:201) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:155) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: hudson.AbortException: script returned exit code 143 ... 9 more Probably this is a logic error in DurableTaskStep.Execution.stop: it should cancel any pending task, or at least set recurrencePeriod to 0 and have run exit early in that case. At any rate, the mistake seems harmless and CpsStepContext is overreacting. Better to log the ISE at FINE and ignore the call to onFailure (or onSuccess). Project: Jenkins Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent-plugin] (JENKINS-27555) ssh-agent plugin leaking file descriptors leaving behind jenkinsXXXXXX.jnr socket files
Tommy McNeely updated JENKINS-27555 ssh-agent plugin leaking file descriptors leaving behind jenkinsXX.jnr socket files Change By: Tommy McNeely (23/Mar/15 8:27 PM) Environment: CentOS 6.6, Java OpenJDK 1.7.0_75, Jenkins 1.596.1 (LTS) , SSH Agent Plugin 1.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] [ssh-agent-plugin] (JENKINS-27555) ssh-agent plugin leaking file descriptors leaving behind jenkinsXXXXXX.jnr socket files
Tommy McNeely commented on JENKINS-27555 ssh-agent plugin leaking file descriptors leaving behind jenkinsXX.jnr socket files Relevant detail I left out in my lengthy description... This issue started on March 4th according to the files... [root@ft-itjenkins-02 ~]# ls -latr /var/run/jenkins | head total 2996 drwxr-x---. 3 jenkins jenkins4096 Feb 20 2014 winstone.tmp drwxr-x---. 2 jenkins jenkins4096 Feb 4 22:06 jna srw---. 1 jenkins jenkins 0 Mar 4 21:23 jenkins5912106282973635660.jnr srw---. 1 jenkins jenkins 0 Mar 4 22:23 jenkins5463392623696270964.jnr srw---. 1 jenkins jenkins 0 Mar 4 23:23 jenkins2098827338802571701.jnr srw---. 1 jenkins jenkins 0 Mar 5 00:23 jenkins3456221189267055906.jnr srw---. 1 jenkins jenkins 0 Mar 5 01:23 jenkins858389491894252767.jnr srw---. 1 jenkins jenkins 0 Mar 5 02:23 jenkins2735831486601947560.jnr srw---. 1 jenkins jenkins 0 Mar 5 03:23 jenkins3814786706214604225.jnr ... which happens to be when we updated to 1.596.1 [root@ft-itjenkins-02 ~]# grep jenkins /var/log/yum.log Jan 14 21:32:48 Updated: jenkins-1.580.2-1.1.noarch Jan 28 23:16:02 Updated: jenkins-1.580.3-1.1.noarch Mar 04 20:33:30 Updated: jenkins-1.596.1-1.1.noarch Probably not a coincidence ~tommy 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] [bitbucket-approve-plugin] (JENKINS-27019) unstable builds must not approve a commit
Björn Hurling resolved JENKINS-27019 as Fixed unstable builds must not approve a commit Fixed in 1.0.2 Change By: Björn Hurling (23/Mar/15 8: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.
[JIRA] [core] (JENKINS-27468) Jenkins exposes internal port on redirections
Daniel Beck commented on JENKINS-27468 Jenkins exposes internal port on redirections Jenkins (or rather Stapler) redirects to /log/ when you open /log. So it's not the application. This is passed on to Jetty, which is used by Jenkins by default since 1.535 or so. It adds the root URL to the response path in Response#sendRedirect(String). println org.kohsuke.stapler.Stapler.currentRequest.rootURL would probably be interesting as well. Unfortunately, debugging Winstone-Stapler in Jenkins is a mess, since Jenkins uses a different version of Jetty when debugging 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-plugin] (JENKINS-27539) NPE when using jobs with the same name in different folders
Patrik Boström closed JENKINS-27539 as Fixed NPE when using jobs with the same name in different folders Released in 0.8.11 Change By: Patrik Boström (23/Mar/15 8:49 PM) Status: Resolved Closed 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-plugin] (JENKINS-27270) Support jobs organized under folders
Patrik Boström commented on JENKINS-27270 Support jobs organized under folders Released in 0.8.11 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-plugin] (JENKINS-27270) Support jobs organized under folders
Patrik Boström closed JENKINS-27270 as Fixed Support jobs organized under folders Change By: Patrik Boström (23/Mar/15 8:59 PM) Status: Resolved Closed 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-plugin] (JENKINS-27550) Error communicating to server! Server Error
Patrik Boström commented on JENKINS-27550 Error communicating to server! Server Error Do you have junit plugin installed and enabled? If so which version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-27550) Error communicating to server! Server Error
Serge Kalinin commented on JENKINS-27550 Error communicating to server! Server Error JUnit installed but not enabled, version 1.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] [delivery-pipeline-plugin] (JENKINS-27550) Error communicating to server! Server Error
Patrik Boström commented on JENKINS-27550 Error communicating to server! Server Error Enable JUnit, it should work then. 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-plugin] (JENKINS-27550) Error communicating to server! Server Error
Serge Kalinin commented on JENKINS-27550 Error communicating to server! Server Error Yep, that fix problem, 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] [delivery-pipeline-plugin] (JENKINS-27550) Error communicating to server! Server Error
Serge Kalinin edited a comment on JENKINS-27550 Error communicating to server! Server Error Yep, that fixed problem, 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] [sbt-plugin] (JENKINS-27264) Latest 1.5 SBT Plugin does not work
Jonathan Kelly commented on JENKINS-27264 Latest 1.5 SBT Plugin does not work I'm seeing this as well. Is there any update? 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] [git-plugin] (JENKINS-27556) Restart causes resetting git repository setting of the Job
Artem Zinnatullin created JENKINS-27556 Restart causes resetting git repository setting of the Job Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 23/Mar/15 9:44 PM Description: I made clean install of Jenkins 1.605 on clean Ubuntu Server 14.10, then I configured one Job, which uses: Git repo via https (Open Source project on GitHub) and GitHub Pull Request Builder Plugin. After each restart of Jenkins service (even after upgrade to Jenkins 1.606) Job's configuration of Source Code Management got reset. So I have to fill it every time after Jenkins restart. If I open Job configuration after restart, I see that all settings saved normally, but Source Code Management selected as "none" and all Git repository options will be empty after selecting "Git" Environment: Ubuntu Server 14.10 x64 java -version java version "1.8.0_40" Java(TM) SE Runtime Environment (build 1.8.0_40-b25) Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode) Jenkins versions affected: 1.605, 1.606 Project: Jenkins Priority: Major Reporter: Artem Zinnatullin 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-26092) executors.jelly interface underspecified
Jesse Glick resolved JENKINS-26092 as Won't Fix executors.jelly interface underspecified Javadoc already confirms that the implementation must have an executorCell.jelly, so the fallback body does not matter much. (It is used for AbstractBuild and WorkflowRun, both of which currently meet its requirements.) Too much work to refactor Jelly code with no compile-time safety. Some of the unchecked calls are anyway on Queue.SubTask rather than Queue.Executable. Change By: Jesse Glick (23/Mar/15 9:49 PM) Status: Open Resolved Resolution: Won't 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] [maven-plugin] (JENKINS-12259) NullPointerException in maven-plugin: Maven3Builder / ExecutedMojo (1.445)
J Knurek commented on JENKINS-12259 NullPointerException in maven-plugin: Maven3Builder / ExecutedMojo (1.445) I'm getting what looks to be the same issue in v1.598 [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) . I'm running mvn clean package site using version 2.9 of Maven Integration plugin; maven version 3.1.1 As mentioned in JENKINS-12358 this also works for me in a freestyle job, just not with the Maven plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-12259) NullPointerException in maven-plugin: Maven3Builder / ExecutedMojo (1.445)
J Knurek edited a comment on JENKINS-12259 NullPointerException in maven-plugin: Maven3Builder / ExecutedMojo (1.445) I'm getting what looks to be the same issue in v1.598 [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) . I'm running `mvn clean package site` using version 2.9 of Maven Integration plugin; maven version 3.1.1 As mentioned in JENKINS-12358 this also works for me in a freestyle job, just not with the Maven plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27557) Jenkins 1.605 update is not working now
emma li created JENKINS-27557 Jenkins 1.605 update is not working now Issue Type: Bug Assignee: Unassigned Components: core Created: 24/Mar/15 2:37 AM Description: No plugin is displayed in the available tab of the plugin management page. If clicking the Check Now button in the advanced tab, it says: Signature verification failed in update site 'default' And the following is found in log file: ERROR: Signature verification failed in update site 'default' (show details)java.security.cert.CertPathValidatorException: timestamp check failed at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:159) at sun.security.provider.certpath.PKIXCertPathValidator.doValidate(PKIXCertPathValidator.java:351) at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:191) at java.security.cert.CertPathValidator.validate(CertPathValidator.java:279) at org.jvnet.hudson.crypto.CertificateUtil.validatePath(CertificateUtil.java:93) at jenkins.util.JSONSignatureValidator.verifySignature(JSONSignatureValidator.java:76) at hudson.model.UpdateSite.verifySignature(UpdateSite.java:219) at hudson.model.UpdateSite.updateData(UpdateSite.java:198) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:170) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:890) 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.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46) at org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:183) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.
[JIRA] [git-plugin] (JENKINS-27447) LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page
Mark Waite commented on JENKINS-27447 LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page That's quite surprising. Since the null pointer exception is two layers inside the Java source code, it would be a great help for diagnosis if you could catch that null pointer exception and display the date string that was being parsed when the null pointer exception happened. 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-27558) job build fatal error on creating/compressing archive files with a "Failed to parse POMs" message
james todd created JENKINS-27558 job build fatal error on creating/compressing archive files with a "Failed to parse POMs" message Issue Type: Bug Assignee: Unassigned Components: core Created: 24/Mar/15 3:26 AM Description: in creating a simple maven job: git clone mvn compile package i get the following fatal error: ERROR: Failed to parse POMs de.schlichtherle.truezip.io.InputException: java.io.IOException: java.io.FileNotFoundException: /app/jenkins/workspace/common develop/modules/client/com.foo.analytics/common-client/20150323183039-SNAPSHOT/common-client-20150323183039-SNAPSHOT.pom (No such file or directory) at de.schlichtherle.truezip.io.Streams.cat(Streams.java:258) at de.schlichtherle.truezip.io.Streams.copy(Streams.java:71) at de.schlichtherle.truezip.file.TFile.cp(TFile.java:2744) at de.schlichtherle.truezip.file.TFile.cp(TFile.java:2817) at org.jenkinsci.plugins.compress_artifacts.ZipStorage.archive(ZipStorage.java:77) at org.jenkinsci.plugins.compress_artifacts.CompressingArtifactManager.archive(CompressingArtifactManager.java:50) at hudson.maven.MavenBuild$ProxyImpl.performArchiving(MavenBuild.java:483) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:851) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Environment: jenkins 1.596.2 lts os: Red Hat 4.4.7-9 jdk: 1.7, 1.8 container: none plugins: standard mix Project: Jenkins Priority: Blocker Reporter: james todd 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] [patch-parameter-plugin] (JENKINS-27169) Patch parameter plugin's patch code is OS dependent which fails to patch cross platform files
Charles Chan commented on JENKINS-27169 Patch parameter plugin's patch code is OS dependent which fails to patch cross platform files H Shah, any updates? 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] [s3-plugin] (JENKINS-26903) S3 plugin missing http jars
Charles Chan commented on JENKINS-26903 S3 plugin missing http jars Anyone try the plugin? Did it resolve the problem? 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-plugin] (JENKINS-27559) NullPointerException in Revision.containsBranchName with Gerrit Trigger choosing strategy and build any branch
Dan C
updated JENKINS-27559
NullPointerException in Revision.containsBranchName with Gerrit Trigger choosing strategy and build any branch
Change By:
Dan C
(24/Mar/15 5:37 AM)
Description:
Job is configured to use Git with Gerrit Trigger choosing strategy. Remote name is gerrit, refspec is:
{{
+refs/heads/*:refs/remotes/gerrit/* $GERRIT_REFSPEC
}}
. Configured to merge with
{{
$GERRIT_BRANCH
}}
and calculate changelog against
{{
$GERRIT_BRANCH
}}
.When using the Gerrit Trigger choosing strategy, "branches to build" is meaningless, so I left it at the default "**". However that causes the following NPE.Changing the "branches to build" to a valid branch name like "master" fixes the problem.{code}Retriggered by user dcallagh for Gerrit: http://gerrit.beaker-project.org/4092 in silent mode.[EnvInject] - Loading node environment variables.Building in workspace /var/lib/jenkins/jobs/restraint-review-checks/workspaceselected Git installation does not exists. Using Default > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.gerrit.url ssh://jenk...@gerrit.beaker-project.org:29418/restraint # timeout=10Fetching upstream changes from ssh://jenk...@gerrit.beaker-project.org:29418/restraint > git --version # timeout=10using GIT_SSH to set credentials > git -c core.askpass=true fetch --tags --progress ssh://jenk...@gerrit.beaker-project.org:29418/restraint +refs/heads/*:refs/remotes/gerrit/* refs/changes/92/4092/1 > git rev-parse 918d97ecf9cf9fac9ff26a15531e975bde64f4ed^{commit} # timeout=10FATAL: nulljava.lang.NullPointerException at hudson.plugins.git.Revision.containsBranchName(Revision.java:104) at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:57) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:925) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1017) at hudson.scm.SCM.checkout(SCM.java:484) at hudson.model.AbstractProject.checkout(AbstractProject.java:1270) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) at hudson.model.Run.execute(Run.java:1751) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)Finished: FAILURE{code}
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-plugin] (JENKINS-27559) NullPointerException in Revision.containsBranchName with Gerrit Trigger choosing strategy and build any branch
Dan C
created JENKINS-27559
NullPointerException in Revision.containsBranchName with Gerrit Trigger choosing strategy and build any branch
Issue Type:
Bug
Assignee:
rsandell
Components:
gerrit-trigger-plugin
Created:
24/Mar/15 5:36 AM
Description:
Job is configured to use Git with Gerrit Trigger choosing strategy. Remote name is gerrit, refspec is: +refs/heads/:refs/remotes/gerrit/ $GERRIT_REFSPEC. Configured to merge with $GERRIT_BRANCH and calculate changelog against $GERRIT_BRANCH.
When using the Gerrit Trigger choosing strategy, "branches to build" is meaningless, so I left it at the default "**". However that causes the following NPE.
Changing the "branches to build" to a valid branch name like "master" fixes the problem.
Retriggered by user dcallagh for Gerrit: http://gerrit.beaker-project.org/4092 in silent mode.
[EnvInject] - Loading node environment variables.
Building in workspace /var/lib/jenkins/jobs/restraint-review-checks/workspace
selected Git installation does not exists. Using Default
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.gerrit.url ssh://jenk...@gerrit.beaker-project.org:29418/restraint # timeout=10
Fetching upstream changes from ssh://jenk...@gerrit.beaker-project.org:29418/restraint
> git --version # timeout=10
using GIT_SSH to set credentials
> git -c core.askpass=true fetch --tags --progress ssh://jenk...@gerrit.beaker-project.org:29418/restraint +refs/heads/*:refs/remotes/gerrit/* refs/changes/92/4092/1
> git rev-parse 918d97ecf9cf9fac9ff26a15531e975bde64f4ed^{commit} # timeout=10
FATAL: null
java.lang.NullPointerException
at hudson.plugins.git.Revision.containsBranchName(Revision.java:104)
at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:57)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:925)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1017)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1270)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531)
at hudson.model.Run.execute(Run.java:1751)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Finished: FAILURE
Environment:
Jenkins 1.605, Git plugin 2.3.5, Gerrit Trigger plugin 2.12.0
Project:
Jenkins
Priority:
Minor
Reporter:
Dan C
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-27468) Jenkins exposes internal port on redirections
Pavel Batanov commented on JENKINS-27468 Jenkins exposes internal port on redirections println org.kohsuke.stapler.Stapler.currentRequest.rootURL gives me an exception (truncated output below) groovy.lang.MissingPropertyException: No such property: rootURL for class: org.kohsuke.stapler.RequestImpl at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.callsite.GetEffectivePojoPropertySite.getProperty(GetEffectivePojoPropertySite.java:63) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:227) at Script1.run(Script1.groovy:1) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589) at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:139) at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:111) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.util.RemotingDiagnostics.executeGroovy(RemotingDiagnostics.java:108) at jenkins.model.Jenkins._doScript(Jenkins.java:3556) at jenkins.model.Jenkins.doScript(Jenkins.java:3533) 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-27468) Jenkins exposes internal port on redirections
Pavel Batanov
commented on JENKINS-27468
Jenkins exposes internal port on redirections
I've tried to dig more data for you
def a = org.kohsuke.stapler.Stapler.currentRequest
a.properties.each { println "$it.key -> $it.value" }
println org.kohsuke.stapler.Stapler.currentRequest.dump()
rootPath -> https://build.example.com:8080
inputStream -> script=def+a+%3D+org.kohsuke.stapler.Stapler.currentRequest%0D%0A%0D%0Aa.properties.each+%7B+println+%22%24it.key+-%3E+%24it.value%22+%7D%0D%0A%0D%0Aprintln+org.kohsuke.stapler.Stapler.currentRequest.dump%28%29&json=%7B%22script%22%3A+%22def+a+%3D+org.kohsuke.stapler.Stapler.currentRequest%5Cn%5Cna.properties.each+%7B+println+%5C%22%24it.key+-%3E+%24it.value%5C%22+%7D%5Cn%5Cnprintln+org.kohsuke.stapler.Stapler.currentRequest.dump%28%29%22%2C+%22%22%3A+%22a.properties.each+%7B+println+%5C%22%24it.key+-%3E+%24it.value%5C%22+%7D%22%7D&Submit=%D0%97%D0%B0%D0%BF%D1%83%D1%81%D1%82%D0%B8%D1%82%D1%8C
boundObjectTable -> org.kohsuke.stapler.bind.BoundObjectTable@257cd29f
stapler -> org.kohsuke.stapler.Stapler@784402ca
servletContext -> ServletContext@w.{,file:/var/cache/jenkins/war/},/var/cache/jenkins/war
scheme -> https
requestedSessionIdFromCookie -> true
requestURLWithQueryString -> https://build.example.com:8080/script
cookies -> [javax.servlet.http.Cookie@25e7d7f3, javax.servlet.http.Cookie@1812a5f6, javax.servlet.http.Cookie@704dc5d2, javax.servlet.http.Cookie@1f69798, javax.servlet.http.Cookie@645a7d29]
locale -> ru
userPrincipal -> null
contentLength -> 599
pathInfo -> /script
parameterMap -> [script:[def a = org.kohsuke.stapler.Stapler.currentRequest
a.properties.each { println "$it.key -> $it.value" }
println org.kohsuke.stapler.Stapler.currentRequest.dump()], json:[{"script": "def a = org.kohsuke.stapler.Stapler.currentRequest\n\na.properties.each { println \"$it.key -> $it.value\" }\n\nprintln org.kohsuke.stapler.Stapler.currentRequest.dump()", "": "a.properties.each { println \"$it.key -> $it.value\" }"}], Submit:[Запустить]]
serverName -> build.example.com
servletPath ->
serverPort -> 8080
restOfPath ->
headerNames -> org.eclipse.jetty.http.HttpFields$3@110d0372
attributeNames -> java.util.Collections$2@6d5d3a1c
requestedSessionIdFromURL -> false
class -> class org.kohsuke.stapler.RequestImpl
requestedSessionId -> tl3fk9twzq7t5b8ukd04pqu5
bindInterceptor -> org.kohsuke.stapler.BindInterceptor@18b57f9f
pathTranslated -> /var/cache/jenkins/war/script
authType -> null
queryString -> null
localAddr -> 10.0.0.19
webApp -> org.kohsuke.stapler.WebApp@3923c5c
localName -> 10.0.0.19
originalRequestURI -> /script
method -> POST
requestURIWithQueryString -> /script
protocol -> HTTP/1.0
remotePort -> 58921
locales -> java.util.Collections$2@75b8bdd8
session -> org.eclipse.jetty.server.session.HashedSession:tl3fk9twzq7t5b8ukd04pqu5@867691593
originalRestOfPath ->
dispatcherType -> REQUEST
requestURL -> https://build.example.com:8080/script
ancestors -> [hudson.model.Hudson@60a541a0]
asyncSupported -> false
submittedForm -> [script:def a = org.kohsuke.stapler.Stapler.currentRequest
a.properties.each { println "$it.key -> $it.value" }
println org.kohsuke.stapler.Stapler.currentRequest.dump(), :a.properties.each { println "$it.key -> $it.value" }]
requestedSessionIdValid -> true
contextPath ->
_javascript_ProxyCall -> false
secure -> true
remoteHost -> 85.30.254.43
remoteUser -> null
localPort -> 8080
referer -> https://build.example.com/script
remoteAddr -> 85.30.254.43
contentType -> application/x-www-form-urlencoded
parameterNames -> java.util.Collections$2@6ff9c725
characterEncoding -> UTF-8
asyncStarted -> false
requestedSessionIdFromUrl -> false
requestURI -> /script
request -> com.marvelution.jenkins.plugins.jira.filter.OAuthFilter$RequestWrapper@77818791
"$it.key -> $it.value" }
println org.kohsuke.stapler.Stapler.currentRequest.dump(), :a.properties.each { println "$it.key -> $it.value" }] parsedFormData=null bindInterceptor=org.kohsuke.stapler.BindInterceptor@18b57f9f request=com.marvelution.jenkins.plugins.jira.filter.OAuthFilter$RequestWrapper@77818791>
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
