[JIRA] [disk-usage] (JENKINS-24182) Disk Usage plugin throws severe exception in latest release and prevents maven jobs from loading
Per J. Lund commented on JENKINS-24182 Disk Usage plugin throws severe exception in latest release and prevents maven jobs from loading Just wanted to say that we experience the same problem. Downgrading brings back the jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24173) Show Views TabBar in pipeline default view
Patrik Boström resolved JENKINS-24173 as Fixed Show Views TabBar in pipeline default view Merged to master Change By: Patrik Boström (10/Aug/14 9:49 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] [core] (JENKINS-22685) Jenkins cannot restart Windows service
Johnson Birdman commented on JENKINS-22685 Jenkins cannot restart Windows service I still have the same service restarting problem in 1.565.1 (Java Version 7 Update 67), so I can't consider it fixed. As for now I'm staying on 1.554.2 without this 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] [parameterized-trigger] (JENKINS-23927) Parameterized trigger should be able to optionally retry failed blocked builds
ikedam commented on JENKINS-23927 Parameterized trigger should be able to optionally retry failed blocked builds Retrying feature sounds useful not only for parameterized-trigger plugin but also for any build steps. How about creating a new plugin to retry any build steps? Anyway, the disign of Jenkins and parameterized-trigger plugin is not optimized for complex moduled projects like what you try. workflow-plugin may help you. Please have a look. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-14108) Multiple parameterized upstreams with joined in one blocked while.. job result in multiple executions rather one only
ikedam commented on JENKINS-14108 Multiple parameterized upstreams with joined in one blocked while.. job result in multiple executions rather one only This looks a current designated behavior of Jenkins. When triggerd a job with different parameters, Jenkins should trigger builds for each parameters, and shouldn't merge them. It's recommended to use Promoted Builds plugin or Join plugin for this scenario. Anyway, this issue is very old, and I'm afraid there are no longer users interested in this issue. (And I don't think this is still a blocker.) I plan to close this issue with "Won't Fix" in a month. Please let me know if anyone still looks this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-timeout] (JENKINS-7832) Hudson build time is calculated from the time job enters the queue while it should be when job actually starts to run
ikedam commented on JENKINS-7832 Hudson build time is calculated from the time job enters the queue while it should be when job actually starts to run Is this problem still reproduced? As @km said, this shouldn't be triggered by build-timeout plugin for its design, and it seems something strange happen in communication between the master and slaves. I need more information to say what's the root cause, and please let me know you can still reproduce 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] [build-timeout] (JENKINS-10439) IOException while archiving AND wrong build status
ikedam commented on JENKINS-10439 IOException while archiving AND wrong build status Let me know: how often it happens? It can be always reproduced if you set short timeout? If it rarely happens, it may be caused by another operator clicking the abort link manually. No abort operation message is output to console log since Jenkins 1.426 (JENKINS-5754). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [conditional-buildstep] (JENKINS-23752) MSBuild Warnings link displays twice on builds if added as conditional build step
Dominik Bartholdi commented on JENKINS-23752 MSBuild Warnings link displays twice on builds if added as conditional build step which project type do you have this problem? maven? freestyle? both? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23273) RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
Daniel Beck
commented on JENKINS-23273
RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
Tommy McNeely:
Are you sure about the symbolic links? My man chmod states (emphasis mine):
-H If the -R option is specified, symbolic links on the command line are followed. (Symbolic links encountered in the tree traversal are not followed.)
-h If the file is a symbolic link, change the user ID and/or the group ID of the link itself.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22876) Support for Promoted Builds Plugin
Patrik Boström commented on JENKINS-22876 Support for Promoted Builds Plugin Created PR: https://github.com/Diabol/delivery-pipeline-plugin/pull/77 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22876) Support for Promoted Builds Plugin
Patrik Boström assigned JENKINS-22876 to Patrik Boström Support for Promoted Builds Plugin Change By: Patrik Boström (10/Aug/14 6:04 PM) Assignee: PatrikBoström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22876) Support for Promoted Builds Plugin
Patrik Boström started work on JENKINS-22876 Support for Promoted Builds Plugin Change By: Patrik Boström (10/Aug/14 6:04 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkinswalldisplay] (JENKINS-23620) The periodic refresh shows loading jobs..
A Huxtable commented on JENKINS-23620 The periodic refresh shows loading jobs.. My analysis of the issue is the problem started here (with the help of git bisect): https://github.com/jenkinsci/walldisplay-plugin/commit/69e9fe2e26fd6559ea5b6b5b313dfbcf07fd0305 So 0.6.25 It appears to occur when the repaint interval is set to less than the update interval, so sometimes the plugin can be unlucky and the update it's various API requests haven't finished by the time the repaint comes along to redraw everything. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22654) Multi-configuration projects display with wrong Delivery Pipeline Stage Name
Patrik Boström updated JENKINS-22654 Multi-configuration projects display with wrong Delivery Pipeline Stage Name Had a look at the issue. Is this a good solution for the above example? Change By: Patrik Boström (10/Aug/14 7:57 PM) Attachment: JENKINS-22654-suggested-solution.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] (JENKINS-22654) Multi-configuration projects display with wrong Delivery Pipeline Stage Name
Patrik Boström commented on JENKINS-22654 Multi-configuration projects display with wrong Delivery Pipeline Stage Name Suggested fix is in this branch: https://github.com/Diabol/delivery-pipeline-plugin/tree/JENKINS-22654_multi_configuration_stage_task_names This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
跟单位里的美乳人妻在家激情照
跟单位里的美乳人妻在家激情照 复制打开 km5jj5iatq.hioem.com?ivfug8r79b -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-23645) Archiving artifacts does not preserve timestamps if filter is **
ikedam commented on JENKINS-23645 Archiving artifacts does not preserve timestamps if filter is ** Please report your versions of Java, Jenkins, and copyartifact plugin. It is a known issue that timestamps are not preserved in Winsows. It is rather a limitation of Java on Windows. (see JENKINS-11073, JENKINS-13515). If you use Java = 1.6, please try Java 1.7 (and the latest LTE version of Jenkins) and see the problem reproduces. But I'm not sure why the filter affects the behavior. You'd better check the owner and permissions of the workspace folder of that job. Jenkins might fail to change the attributes of files directly under the workspace folder for its permission. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [walldisplay] (JENKINS-24192) Add HTTP Date response header to Jetty
Joshua Wherrett created JENKINS-24192 Add HTTP Date response header to Jetty Issue Type: Bug Affects Versions: current Assignee: Christian Pelster Components: walldisplay Created: 11/Aug/14 1:24 AM Description: Embedded jetty doesn't appear to send Date in the HTTP response header. This is used by some plugins (Wall Display) to get Server time (see: https://issues.jenkins-ci.org/browse/JENKINS-21900). Is it possible to turn this on same as they did for Camel? (https://issues.apache.org/jira/i#browse/CAMEL-7360) Environment: Jenkins 1.574 running embedded Jetty webserver on RHEL 6. Fix Versions: current Project: Jenkins Labels: plugin jenkins Priority: Major Reporter: Joshua Wherrett This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-24193) Github Pull Request Builder plugin uses github account email instead of the custom route email
Eric Ackerson created JENKINS-24193 Github Pull Request Builder plugin uses github account email instead of the custom route email Issue Type: Bug Assignee: Unassigned Components: github Created: 11/Aug/14 2:25 AM Description: When trying to send an email to the author of a github pull request, the ghprbActualCommitAuthorEmail variable is set to the user's github email address instead of the custom route that they have set for the github project Due Date: 15/Aug/14 12:00 AM Project: Jenkins Priority: Major Reporter: Eric Ackerson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [conditional-buildstep] (JENKINS-23752) MSBuild Warnings link displays twice on builds if added as conditional build step
David Ruhmann commented on JENKINS-23752 MSBuild Warnings link displays twice on builds if added as conditional build step Using the freestyle project 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] [conditional-buildstep] (JENKINS-23752) MSBuild Warnings link displays twice on builds if added as conditional build step
David Ruhmann commented on JENKINS-23752 MSBuild Warnings link displays twice on builds if added as conditional build step However, I have checked and if I do a similar publisher conditional on a maven project type, the same issue exists. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22525) incompatible InnerClasses attribute error in IBM J9 VM
dan tran commented on JENKINS-22525 incompatible InnerClasses attribute error in IBM J9 VM dont see it at 1.575 http://jenkins-ci.org/changelog. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng] (JENKINS-24176) Test result trend breaks lazy-loading
Nalin Makar commented on JENKINS-24176 Test result trend breaks lazy-loading Jesse, What would be the pros/cons of just doing something similar to MethodResult.populateDataSetBuilder and loading the last 10 builds to generate the trend graph? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
