[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
Daniel Beck 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 ikedam: I think this issue could have merit if the build timeout plugin does not take into account that the flyweight parent build for e.g. Maven or Matrix projects starts immediately (due to use of one-off executors), while the real (module / configuration) build needs to wait until an executor becomes available. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
Daniel Beck commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported It concerns me a bit that only Marnix Klooster got the timeout exception. Otherwise this would be a straightforward config 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] [core] (JENKINS-24514) Weak Filesystem Permissions
Soren Hansen commented on JENKINS-24514 Weak Filesystem Permissions Debian policy says that package upgrades must take care of preserving user changes to conffiles. However, if there are no changes (i.e. /etc/default/jenkins hasn't been changed by a user after installing Jenkins), it will simply get overwritten by a new version of /etc/default/jenkins during upgrades. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [chucknorris] (JENKINS-25084) Chuck is no longer since Jenkins update
Guillaume Kulakowski created JENKINS-25084 Chuck is no longer since Jenkins update Issue Type: Bug Assignee: Unassigned Attachments: screenshot-sol-mtp-pic1 groupinfra com 2014-10-10 09-54-49.png Components: chucknorris Created: 10/Oct/14 7:55 AM Description: Hi, since last updates of Jenkins, I have a Chuck's quote on my page but I do not have Chuck's photo. I thinks that this plugin is no longuer compatible with Jenkins. Environment: RHEL6 / Jenkins ver. 1.583 / ChuckNorris Plugin 0.5 Project: Jenkins Priority: Minor Reporter: Guillaume Kulakowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-25066) "Build on the same node" option triggers runs on node with same label and not on identical node
Tobias Del Fabro updated JENKINS-25066 "Build on the same node" option triggers runs on node with same label and not on identical node Attached the file. Change By: Tobias Del Fabro (10/Oct/14 7:56 AM) Attachment: build.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-25085) email-ext showPaths does not work with p4-plugin
swolk
created JENKINS-25085
email-ext showPaths does not work with p4-plugin
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4
Created:
10/Oct/14 8:34 AM
Description:
We use email-ext plugin for email notification. For some reason changes are blank when specifying: ${CHANGES_SINCE_LAST_SUCCESS, showPaths=true}. If I just do ${CHANGES_SINCE_LAST_SUCCESS}. showPaths works with perforce-plugin, so that's why I think there may be a bug here.
Environment:
Jenkins ver. 1.565.2
Email-ext 2.38.2
P4 1.0.15
Project:
Jenkins
Priority:
Critical
Reporter:
swolk
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-25085) email-ext showPaths does not work with p4-plugin
swolk updated JENKINS-25085 email-ext showPaths does not work with p4-plugin Change By: swolk (10/Oct/14 8:36 AM) Attachment: showPaths=true.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-25085) email-ext showPaths does not work with p4-plugin
swolk updated JENKINS-25085 email-ext showPaths does not work with p4-plugin Change By: swolk (10/Oct/14 8:36 AM) Attachment: no_showPaths.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cloudbees-folder] (JENKINS-25078) Default health metric is potentially expensive
Nicolas De Loof commented on JENKINS-25078 Default health metric is potentially expensive I wonder we could use a simple workaround to have Job / Folders job property to maintain health status, only updated on build completion, vs re-computing any time page is accessed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cloudbees-folder] (JENKINS-25078) Default health metric is potentially expensive
Nicolas De Loof edited a comment on JENKINS-25078 Default health metric is potentially expensive I wonder we could use a simple workaround to have a Job / Folders property for health status, only updated on build completion, vs re-computing any time page is accessed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [perfectomobile] (JENKINS-25086) Perfecto Mobile won't Install
Anton Gillert created JENKINS-25086 Perfecto Mobile won't Install Issue Type: Bug Assignee: Unassigned Attachments: exceptions.txt, Jenkins_not_working.txt, Jenkins_not_working_plugins_sort.txt, Jenkins_working.txt, Jenkins_working_plugins_sort.txt Components: perfectomobile Created: 10/Oct/14 10:28 AM Description: I've 2 Jenkins instances running on two Ubuntu 14.04 machines (both up to date as of now). On one which is running on a public cloud i can install the perfectomobile 2.20.1.2 plugin and use as expected on the other machine, a virtualbox VM running locally I get some exceptions which prevent me to use perfecto mobile. it installs the plugin, all files get dumped on my disk, but jenkins can't initialize the plugin on me local machine. I've not proxies or other fancy network setup. I've attached listings of installed plugins and versions of both jenkins instances. the only difference is that on the machine on which perfecto is not working the Copy Artifact Plugin is installed. further more I attached the stack trace extracted from jenkins log: Environment: Ubuntu 14.04 Jenkins 1.583 java version "1.7.0_65" OpenJDK Runtime Environment (IcedTea 2.5.2) (7u65-2.5.2-3~14.04) Project: Jenkins Priority: Major Reporter: Anton Gillert This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-13804) radioBlocks contained in repeatable are not shown correctly anymore / affects plot plugin
Daniel Beck resolved JENKINS-13804 as Duplicate radioBlocks contained in repeatable are not shown correctly anymore / affects plot plugin Appears to be a duplicate of JENKINS-22583 Change By: Daniel Beck (10/Oct/14 10:50 AM) 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] [youtrack] (JENKINS-24333) No action for executing command from build step
Wolfgang Ziegler
commented on JENKINS-24333
No action for executing command from build step
Thanks a lot for implementing this!
Sry, it took me a while to come back to this, but I tested it now. I used 1.6.1 as I figured it's already included in there.
The configuration options look good to me, however I had some troubles configuring it properly for my needs. I have two problems:
I'd need the build changelog in a variable, such that I can add it to the comment and to "find issues ids in text". Google told me ${CHANGES} should be there, but that does not work for me. Any idea how I could access the build changelog?
I tried manually inserting issue ids in the "find issues ids in text" by inputting "#XYZ-123 something" in there, but it tried to send the command to "XYZ" instead of "XYZ". So looks like the issue parsing does not work properly here?
Lastly, a minor issue, but I noted there is "and and" in the following help text:
>Text to search for issues ids for which the command will be applied. If both search query and and issue in text is set, the command will be applied to the union of the two.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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 reopened JENKINS-7832 Hudson build time is calculated from the time job enters the queue while it should be when job actually starts to run I haven't tested a maven project. "Module Builds" in the screenshot indicates that was a maven project. I'll try that. Build-timeout isn't triggered for matrix panents. Though I don't know how maven projects work, it looks that build-timeout shouldn't work for maven parent. Change By: ikedam (10/Oct/14 11:31 AM) Resolution: Cannot Reproduce Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-25087) Unable to execute BPT on remote UFT machine with Quality Center 11.52
Antonio Boogaers created JENKINS-25087 Unable to execute BPT on remote UFT machine with Quality Center 11.52 Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 10/Oct/14 11:53 AM Description: Please assign this ticket to Ofir. Thanks! I'm able to execute tests remotely using Lab Management (ALM 11.52 Patch 3 full version), but somehow I'm continuously receiving the following error when trying to execute an automated BPT test case without the Lab Management integration: Error Message Error : Cannot run test. Please check Testing Tool setup. Could not lock the host. Another test may be running. Try later Standard Output 10-10-2014 11:30:02 Running: [1]IE_Basic 10-10-2014 11:30:02 Running test: [1]IE_Basic, Test id: 1, Test instance id: 1 Test: [1]IE_Basic, Id: 1, Execution status: Running Test: [1]IE_Basic, Id: 1, Execution status: Error, Message: Cannot run test. Please check Testing Tool setup. Could not lock the host. Another test may be running. Try later 10-10-2014 11:30:06 Test complete: [1]IE_Basic I've been testing the integration with all possible scenarios from the job configuration, but still no solution. Looking forward to a timely solution and/or further assistance. Many thanks! Environment: Jenkins core: v1.554.1 HP Application Automation Tools: v3.0.5 HP ALM-QC 11.52 Patch 3 HP UFT 11.53 Patch 2 Project: Jenkins Priority: Major Reporter: Antonio Boogaers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22792) Downstream Builds missing downstream multi-configuration build
Daniel Beck updated JENKINS-22792 Downstream Builds missing downstream multi-configuration build 'Critical' means: Crashes, loss of data, severe memory leak. Reducing priority. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22792) Downstream Builds missing downstream multi-configuration build
Daniel Beck commented on JENKINS-22792 Downstream Builds missing downstream multi-configuration build Needs to be reproduced on a less outdated version. 1.565.x or 1.58x would be great right now. If you could provide detailed and complete instructions how this can be reproduced on these versions would also help in investigating 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] [ldap] (JENKINS-20051) Winstone goes down on 1.509.4 (due to LDAP issues?)
Daniel Beck updated JENKINS-20051 Winstone goes down on 1.509.4 (due to LDAP issues?) Seems to be LDAP alone; assuming core only due to use of former 'www' component. Change By: Daniel Beck (10/Oct/14 12:12 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-17796) Maven 2/3 _-Project Job Unable to commit files svn: E155004
epikur2412 commented on JENKINS-17796 Maven 2/3 _-Project Job Unable to commit files svn: E155004 a direct call "mvn -B -Dresume=false release:prepare release:perform" as "Execute windows batch command" does not lock any space. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [analysis-collector] (JENKINS-24940) New Warnings link in Static Analysis results shows all warnings
Kevin Formsma updated JENKINS-24940 New Warnings link in Static Analysis results shows all warnings Change By: Kevin Formsma (10/Oct/14 12:34 PM) Attachment: newWarnings.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [analysis-collector] (JENKINS-24940) New Warnings link in Static Analysis results shows all warnings
Kevin Formsma updated JENKINS-24940 New Warnings link in Static Analysis results shows all warnings Change By: Kevin Formsma (10/Oct/14 12:34 PM) Attachment: build_history.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [analysis-collector] (JENKINS-24940) New Warnings link in Static Analysis results shows all warnings
Kevin Formsma updated JENKINS-24940 New Warnings link in Static Analysis results shows all warnings Change By: Kevin Formsma (10/Oct/14 12:35 PM) Attachment: allWarnings.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [analysis-collector] (JENKINS-24940) New Warnings link in Static Analysis results shows all warnings
Kevin Formsma commented on JENKINS-24940 New Warnings link in Static Analysis results shows all warnings I was able to reproduce this again. It seems to occur when the build with the New Warnings identified is not the most recent build. I've attached a screenshot showing build history, then all warnings page, as well as new warnings page which incorrectly lists all warnings. Is there state for this that is maintained within the workspace? For this project, the workspace is wiped between builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-25026) Console output stops populating after several seconds
Martin Schayna
commented on JENKINS-25026
Console output stops populating after several seconds
It happens for all job types, I have pure Java Maven jobs (e.g. "mvn clean compile test") and some Grails jobs ("grails prod war"). No weird things I hope, I'll try to attach screencast.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-25026) Console output stops populating after several seconds
Martin Schayna updated JENKINS-25026 Console output stops populating after several seconds Screencast demonstrating bug, currently running job was Maven test goal. Change By: Martin Schayna (10/Oct/14 1:33 PM) Attachment: console-error-screencast.gif This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-23828) Build Pipeline View doesn't show build user id on Downstream Projects
Livia Guimaraes updated JENKINS-23828 Build Pipeline View doesn't show build user id on Downstream Projects Change By: Livia Guimaraes (10/Oct/14 2:01 PM) Attachment: pipelinesisres.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-23828) Build Pipeline View doesn't show build user id on Downstream Projects
Livia Guimaraes updated JENKINS-23828 Build Pipeline View doesn't show build user id on Downstream Projects Change By: Livia Guimaraes (10/Oct/14 2:06 PM) Attachment: build65.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-25026) Console output stops populating after several seconds
Daniel Beck commented on JENKINS-25026 Console output stops populating after several seconds The screencast is very nice, thank you. And the behavior demonstrated is very weird. Does this happen for all jobs, all builds? Is Jenkins accessed through a reverse proxy? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [flexible-publish] (JENKINS-25017) BuildTrigger in Flexible Publish doesn't work since Jenkins 1.501
wernight commented on JENKINS-25017 BuildTrigger in Flexible Publish doesn't work since Jenkins 1.501 Thanks for taking a look. I cannot use "Parameterized Trigger" from within a Flexible block (I see no such option). Using just Parameterized Trigger works, but it's unconditional. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [m2release] (JENKINS-25088) M2ReleaseAction/index.jelly fails to define required permission
Jesse Glick created JENKINS-25088 M2ReleaseAction/index.jelly fails to define required permission Issue Type: Bug Assignee: teilo Components: m2release Created: 10/Oct/14 2:17 PM Description: In an incognito browsing tab go to https://jenkins.ci.cloudbees.com/job/plugins/job/m2release-plugin/m2release/. This page is displayed even though you are anonymous and would not be offered the link to get here. Actually trying to submit the form will fail, but still. The fix is to specify the permission attribute on l:layout. Project: Jenkins Labels: security Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-25089) Automated emails send from mailer-plugin should include headers identifying them as automated
Brian Egge created JENKINS-25089 Automated emails send from mailer-plugin should include headers identifying them as automated Issue Type: Bug Assignee: Unassigned Components: mailer-plugin Created: 10/Oct/14 2:22 PM Description: Emails, which are automated should include an Auto-submitted header. Mail servers are then required to NOT send automated responses in response to these emails. http://tools.ietf.org/html/rfc3834 Automatic responses SHOULD NOT be issued in response to any message which contains an Auto-Submitted header field (see below), where that field has any value other than "no". The proposed patch INCLUDES the 'Auto-Submitted' on all outbound emails created by the plugin. This header is defined as follows: 5. The Auto-Submitted header field The purpose of the Auto-Submitted header field is to indicate that the message was originated by an automatic process, or an automatic responder, rather than by a human; and to facilitate automatic filtering of messages from signal paths for which automatically generated messages and automatic responses are not desirable. ... The auto-generated keyword: SHOULD be used on messages generated by automatic (often periodic) processes (such as UNIX "cron jobs") which are not direct responses to other messages, The Jenkins mailer-plugin creates emails by an automatic process and therefore SHOULD contain this header. Project: Jenkins Labels: plugin Priority: Minor Reporter: Brian Egge This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-25089) Automated emails send from mailer-plugin should include headers identifying them as automated
Brian Egge resolved JENKINS-25089 as Fixed Automated emails send from mailer-plugin should include headers identifying them as automated The fix has been merged into the trunk: https://github.com/jenkinsci/mailer-plugin/commit/11142e5f43e55d5bb0f5dd2c8297e737cf122307 Change By: Brian Egge (10/Oct/14 2:27 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] [docker-build-publish] (JENKINS-24338) Issues with docker permissions
obazoud commented on JENKINS-24338 Issues with docker permissions Got the same problem. 14:28:32 Run integration tests... 14:28:32 Run Test Kitchen... 14:28:32 -> Cleaning up any prior instances of 14:28:32 -> Destroying ... 14:28:32 14:28:32Usage: docker inspect CONTAINER|IMAGE [CONTAINER|IMAGE...] 14:28:32 14:28:32Return low-level information on a container or image 14:28:32 14:28:32 -f, --format=""Format the output using the given go template. 14:28:32Finished destroying (0m0.06s). 14:28:32 -> Testing 14:28:32 -> Creating ... 14:28:322014/10/10 14:28:32 Post http:///var/run/docker.sock/build?rm=1&t=: dial unix /var/run/docker.sock: permission denied 14:28:32 -> Destroying ... Works fine in a shell, got the problem in freejob style created by job dsl. This job runs Test kitchen (Chef) jenkins user is a member of the docker group # ls -la /var/run/docker.sock srw-rw. 1 root docker 0 10 oct. 14:19 /var/run/docker.sock This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22151) Plugin extension point for additional configuration
Daniel Spilker assigned JENKINS-22151 to Daniel Spilker Plugin extension point for additional configuration Change By: Daniel Spilker (10/Oct/14 2:57 PM) Assignee: Justin Ryan Daniel Spilker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22151) Plugin extension point for additional configuration
Daniel Spilker commented on JENKINS-22151 Plugin extension point for additional configuration This issue is (among other things) blocked by JENKINS-25007. The Gradle JPI plugin does not publish the JAR, but other plugins need the JAR to use the extension classes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [mock-slave] (JENKINS-25090) Mock slaves should use a consistent remoteFS after restart
Jesse Glick created JENKINS-25090 Mock slaves should use a consistent remoteFS after restart Issue Type: Bug Assignee: Jesse Glick Components: mock-slave Created: 10/Oct/14 3:00 PM Description: For testing durable tasks you need to have a consistent workspace (so, remoteFS) even after Jenkins is restarted. Currently the remoteFS is random, to avoid conflicts. Should rather be based on the slave name plus the Jenkins instance ID or something like this. Project: Jenkins Labels: workflow Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Manni Heumann commented on JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' I have a feeling that this is triggered when the jenkins url contains a port number. I just tried accessing my jenkins instance through a SSH tunnel (something that used to work until we upgraded to 1.583) and promptly ran into the problem. Logging in using our normal, intra-net, URL works just fine. HTTP/1.1 302 Found Set-Cookie: JSESSIONID.3a3afa59=1osdlnih6c42p1kkmc0uhgrmmz;Path=/tools/jenkins;Secure;HttpOnly Expires: Thu, 01 Jan 1970 00:00:00 GMT Location: http://127.0.0.2:8080/tools/jenkins/;jsessionid=1osdlnih6c42p1kkmc0uhgrmmz Content-Length: 0 Server: Jetty(8.y.z-SNAPSHOT) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24914) Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)
SCM/JIRA link daemon commented on JENKINS-24914 Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc) Code changed in jenkins User: Daniel Beck Path: core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/adf8305f8b128c856a6de33409595fe14e01fd73 Log: [FIXED JENKINS-24914] Don't block indefinitely every other month This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24914) Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)
SCM/JIRA link daemon resolved JENKINS-24914 as Fixed Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc) Change By: SCM/JIRA link daemon (10/Oct/14 3:25 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-24914) Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)
SCM/JIRA link daemon commented on JENKINS-24914 Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc) Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/d045618e0a009cae321f6b048a7507ec0b3b8eac Log: Merge pull request #1421 from daniel-beck/JENKINS-24914 [FIXED JENKINS-24914] Don't block indefinitely every other month Compare: https://github.com/jenkinsci/jenkins/compare/657d7151b149...d045618e0a00 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [timestamper] (JENKINS-25091) Timestamper Elapsed time only showing System clock time
David Brown created JENKINS-25091 Timestamper Elapsed time only showing System clock time Issue Type: Bug Assignee: stevengbrown Components: timestamper Created: 10/Oct/14 3:32 PM Description: Perhaps this is user error - I hope so. I'm trying to test the "Elapsed time" option. I see the system time against my Console Output, but when I change the radio-set option to Elapsed time nothing happens. I've tried refreshing the page but all I see is System clock time. I have left the two default time format options unchanged in the System configs. Am I doing something wrong or is this a bug please? Simply having the system timestamp is an improvement from before, but I am curious to see if the Elapsed time option would be more helpful to me. Environment: Jenkins version 1.554 Timestamper version 1.5.14 Project: Jenkins Labels: timestamp Priority: Minor Reporter: David Brown This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cloudbees-folder] (JENKINS-25078) Default health metric is potentially expensive
Jesse Glick commented on JENKINS-25078 Default health metric is potentially expensive Job.cachedBuildHealthReportsBuildNumber/cachedBuildHealthReports is already supposed to do this, but it is not enough to prevent expensive calculations on some renders. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-23301) Cannot connect to Docker using unix protocol
Jesse Glick edited a comment on JENKINS-23301 Cannot connect to Docker using unix protocol Sounds like docker-java might do this: https://github.com/docker-java/docker-java/issues/20 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24926) Connection to slave constantly breaks, java process can only be kill -9-ed
Johannes Wienke commented on JENKINS-24926 Connection to slave constantly breaks, java process can only be kill -9-ed Thanks for the hint. Without disabling the ping, how frequent should I see something in this log? Because right now I see nothing since I added that logger a few minutes ago, but the server is currently also in the state that the mac slave is disconnected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-4995) Support windows AMI's in EC2 plugin
Bryan Garretson commented on JENKINS-4995 Support windows AMI's in EC2 plugin I'm trying to utilize this plugin for both Linux and Windows slave provisioning. Linux of course functions just fine. For my Windows machines, I am running into an infinite loop during the WinRM ping() process (I think). The firewall on my build agent is wide open and I've verified WinRM availability in my configuration with a separate instance in the same EC2 availability zone, so I think an exception is occurring somewhere in the ping() loop but I don't have access to detailed log info or a stack trace. I am willing to help develop and test Windows utilization, but could use some pointers on how to move forward or any troubleshooting you can suggest This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-flow] (JENKINS-25092) Build flow with ConcurrentModificationException when cancelling jobs
Johannes Wienke
created JENKINS-25092
Build flow with ConcurrentModificationException when cancelling jobs
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
build-flow
Created:
10/Oct/14 3:54 PM
Description:
A build-flow job failed with the following output when I stopped it and some of its underlying jobs manually during execution.
Started by user jwienke
Schedule job distribution-prepare.nightly
Build distribution-prepare.nightly #68 started
distribution-prepare.nightly #68 completed
parallel {
ignore(ABORTED) {
ignore(ABORTED) {
ignore(ABORTED) {
Schedule job rsbag-manual-master-toolkit-nightly
Schedule job pyscxml-master-toolkit-nightly
Schedule job vdemo-master-toolkit-nightly
ignore(ABORTED) {
parallel {
Schedule job cbf-0.1-toolkit-nightly
ignore(ABORTED) {
Schedule job icewing-trunk-toolkit-nightly
ignore(ABORTED) {
Schedule job kdl-master-toolkit-nightly
parallel {
ignore(ABORTED) {
Schedule job rosetta-cl-master-toolkit-nightly
ignore(ABORTED) {
parallel {
Schedule job nemomath-trunk-toolkit-nightly
ignore(ABORTED) {
ignore(ABORTED) {
Schedule job rsc-master-toolkit-nightly
Schedule job spread-trunk-toolkit-nightly
Build rsc-master-toolkit-nightly #576 started
Build rosetta-cl-master-toolkit-nightly #565 started
Build nemomath-trunk-toolkit-nightly #570 started
Build kdl-master-toolkit-nightly #530 started
Build icewing-trunk-toolkit-nightly #238 started
Build cbf-0.1-toolkit-nightly #232 started
Build pyscxml-master-toolkit-nightly #428 started
Build vdemo-master-toolkit-nightly #537 started
Build rsbag-manual-master-toolkit-nightly #570 started
Build spread-trunk-toolkit-nightly #551 started
spread-trunk-toolkit-nightly #551 completed : ABORTED
// ABORTED ignored
}
rosetta-cl-master-toolkit-nightly #565 completed : ABORTED
// ABORTED ignored
}
parallel {
ignore(ABORTED) {
ignore(ABORTED) {
Schedule job rosetta-yarp-cl-master-toolkit-nightly
Schedule job rosetta-esrap-util-cl-master-toolkit-nightly
}
Aborted by jwienke
rsc-master-toolkit-nightly #576 completed : ABORTED
// ABORTED ignored
[JIRA] [teamconcert] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
Heather Fraser-Dube commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source Hi James, Sorry for the delay. Things have been a bit busy here and unfortunately I am away next week. I've looked over our code in this area but don't see anything obvious. The problem is at a lower level than us, but I don't quite understand what would trigger it. So a bunch of questions... Does this only happen for 1 user's personal build or is it randomly affecting all personal builds? If it affects just 1 (or a given set of) user, can you check their workspace and see if its visible to the user that the Jenkins job is configured to use. Also see if there are missing or extra components from what is normally in the build workspace. If there are extra components, are they visible to the user that the Jenkins job is configured to use. I don't think this is the problem, but I want to rule it out too. The sandbox is where the RTC repository workspace is to be loaded. Its defined on the Source Control tab of the build definition as the Load directory. If you set the path to ".", it will end up being in the Jenkins job's workspace. I am interested in knowing if you use any special features wrt loading (i.e. in the build definition, do you have delete directory before loading checked? Is Create folders for components checked?) When it happens, can you look at the job's log. I am interested in all the messages that are related to the check out (or possibly corrupted metadata). It will also help to understand how far it got during the load. I think that they would follow the "RTC Checkout : Source control setup" message. Does the build result have an activity for Fetching Files... If so, was it completed? Does trying to cancel the build help when this happens? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24914) Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)
dogfood commented on JENKINS-24914 Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc) Integrated in jenkins_main_trunk #3735 [FIXED JENKINS-24914] Don't block indefinitely every other month (Revision adf8305f8b128c856a6de33409595fe14e01fd73) Result = SUCCESS daniel-beck : adf8305f8b128c856a6de33409595fe14e01fd73 Files : core/src/main/java/jenkins/model/Jenkins.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22792) Downstream Builds missing downstream multi-configuration build
Daniel Beck updated JENKINS-22792 Downstream Builds missing downstream multi-configuration build Change By: Daniel Beck (10/Oct/14 5:04 PM) Priority: Critical Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [chucknorris] (JENKINS-25084) Chuck is no longer since Jenkins update
Daniel Beck updated JENKINS-25084 Chuck is no longer since Jenkins update Blocker bug priority in the context of this plugin, I think. Change By: Daniel Beck (10/Oct/14 5:10 PM) Priority: Minor Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [yaml-project] (JENKINS-25100) Find a way to improve our flyweights' presentation in the build queue
Matthew Moore created JENKINS-25100 Find a way to improve our flyweights' presentation in the build queue Issue Type: Improvement Assignee: Matthew Moore Components: yaml-project Created: 10/Oct/14 5:27 PM Description: We use a flyweight job for the outer job of the DSL. When a lot of these get run, these tend to clog up the build queue view. It would be nice if we could tidy up the presentation of these, so that it didn't seem so cluttered. Project: Jenkins Priority: Minor Reporter: Matthew Moore This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-4995) Support windows AMI's in EC2 plugin
Francis Upton commented on JENKINS-4995 Support windows AMI's in EC2 plugin @Bryan, it would be great to get your help on this. Can't give you any hints right this minute. Let me look into things and get back to you. Ping me again early next week if you don't hear from me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-25106) Minimum number of slaves for cloud
Kohsuke Kawaguchi created JENKINS-25106 Minimum number of slaves for cloud Issue Type: Improvement Assignee: Francis Upton Components: ec2 Created: 10/Oct/14 6:13 PM Description: I was talking to an user, and he said he likes EC2 plugin except he wants to be able to maintain minimum number of slaves always on, so that he won't take the hit of provisioning a new slave. EC2 plugin already allows manual provisioning of an instance, so this seems doable. It would launch new instances automatically if the current count is less than minimum. Retention strategy needs to also change so that slaves don't go away below the minimum count. The part that I'm not sure about is if this can be done below EC2 plugin, so that the logic can be reused by other cloud-like plugins. Project: Jenkins Priority: Minor Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
SCM/JIRA link daemon resolved JENKINS-22358 as Fixed Jenkins 1.556 gives 'Error 404 Not Found' Change By: SCM/JIRA link daemon (10/Oct/14 6:22 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
SCM/JIRA link daemon commented on JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html war/pom.xml http://jenkins-ci.org/commit/jenkins/3addbabf8afae39022440d63216a360233dabc80 Log: [FIXED JENKINS-22358] Integrated the newer version of Winstone This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [support-core] (JENKINS-25108) capture slave launch backlogs
Kohsuke Kawaguchi created JENKINS-25108 capture slave launch backlogs Issue Type: Improvement Assignee: Steven Christou Components: support-core Created: 10/Oct/14 6:25 PM Description: $JENKIN_HOME/slaves/*/slave.log.[0-9]+ records past 10 or so launch logs. Support core should capture them all, not just the current launch log (which is rarely useful.) Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs] (JENKINS-23344) TFS plugin does not create label as trigger value is not saved in config
Chad Strauch commented on JENKINS-23344 TFS plugin does not create label as trigger value is not saved in config I submitted a pull request that seems to have fixed to issue. https://github.com/jenkinsci/tfs-plugin/pull/29 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
dogfood commented on JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' Integrated in jenkins_main_trunk #3737 [FIXED JENKINS-22358] (Revision 3addbabf8afae39022440d63216a360233dabc80) Result = SUCCESS kohsuke : 3addbabf8afae39022440d63216a360233dabc80 Files : war/pom.xml changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24887) Workflow support of Copyartifact
Jesse Glick updated JENKINS-24887 Workflow support of Copyartifact Change By: Jesse Glick (10/Oct/14 7:32 PM) Labels: workflow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
SCM/JIRA link daemon commented on JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation Code changed in jenkins User: Ryan Campbell Path: core/src/main/java/hudson/diagnosis/OldDataMonitor.java test/src/test/java/hudson/diagnosis/OldDataMonitorTest.java http://jenkins-ci.org/commit/jenkins/423b51a43a3c2f469d12695c5fddcda52e97159e Log: JENKINS-24763 Prevent thread starvation in OldDataMonitor by reducing scope of synchronization This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
SCM/JIRA link daemon commented on JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/a8262d503e6af11feebac6005360d4db7639aff4 Log: [FIXED JENKINS-24763] Noting merge of #1402. Compare: https://github.com/jenkinsci/jenkins/compare/3addbabf8afa...a8262d503e6a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
SCM/JIRA link daemon resolved JENKINS-24763 as Fixed Long running OldDataMonitor.doDiscard() results in thread starvation Change By: SCM/JIRA link daemon (10/Oct/14 7:31 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-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
SCM/JIRA link daemon commented on JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/diagnosis/OldDataMonitor.java test/src/test/java/hudson/diagnosis/OldDataMonitorTest.java http://jenkins-ci.org/commit/jenkins/ef6c04244744670650fb36a4482e74daf2094f26 Log: Merge branch 'JENKINS-24763' of github.com:recampbell/jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-24225) Provide a stats page to display data for a given set of job(s) and period: job, rate of failure, reason for failure, category of failure
J John edited a comment on JENKINS-24225 Provide a stats page to display data for a given set of job(s) and period: job, rate of failure, reason for failure, category of failure Nice feature to have This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-25109) Navigating between indication
J John created JENKINS-25109 Navigating between indication Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer Created: 10/Oct/14 7:39 PM Description: A mechanism to step to a previous/next failure or have a sub page in the console output for quick navigation. Environment: build failure analyzer, Project: Jenkins Labels: BFA navigation Priority: Major Reporter: J John This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ownership-plugin] (JENKINS-22869) [ownership] - Low-impact NPE in jenkins/configure due to the missing data
Oleg Nenashev updated JENKINS-22869 [ownership] - Low-impact NPE in jenkins/configure due to the missing data Change By: Oleg Nenashev (10/Oct/14 8:14 PM) Summary: [ownership] - Low-impact NPE in jenkins/configure due to the missing data This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [jclouds-jenkins] (JENKINS-25110) Update Jclouds to 1.8.0
arun suresh created JENKINS-25110 Update Jclouds to 1.8.0 Issue Type: Improvement Assignee: arun suresh Components: jclouds-jenkins Created: 10/Oct/14 8:28 PM Description: Jclouds plugin currently uses Jclouds 1.7.3 which is outdated and does not have some of the bug fixes for Softlayer provider. Jclouds plugin needs to be updated to use the latest Jclouds version. Project: Jenkins Priority: Minor Reporter: arun suresh This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
dogfood commented on JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation Integrated in jenkins_main_trunk #3738 JENKINS-24763 Prevent thread starvation in OldDataMonitor by reducing scope of synchronization (Revision 423b51a43a3c2f469d12695c5fddcda52e97159e) [FIXED JENKINS-24763] Noting merge of #1402. (Revision a8262d503e6af11feebac6005360d4db7639aff4) Result = SUCCESS Ryan Campbell : 423b51a43a3c2f469d12695c5fddcda52e97159e Files : test/src/test/java/hudson/diagnosis/OldDataMonitorTest.java core/src/main/java/hudson/diagnosis/OldDataMonitor.java Jesse Glick : a8262d503e6af11feebac6005360d4db7639aff4 Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cppcheck] (JENKINS-24834) CPP check report background colours not displaying for new or resolved issues since upgrade
Michal Turek closed JENKINS-24834 as Fixed CPP check report background colours not displaying for new or resolved issues since upgrade Change By: Michal Turek (10/Oct/14 8:58 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] [cppcheck] (JENKINS-24037) CPPCheck Plugin: You need "worspace" message instead of "workspace"
Michal Turek closed JENKINS-24037 as Fixed CPPCheck Plugin: You need "worspace" message instead of "workspace" Change By: Michal Turek (10/Oct/14 8:57 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] [cppcheck] (JENKINS-23575) Post-Build-Step "Publish Cppcheck results" not available in job generator project
Michal Turek resolved JENKINS-23575 as Fixed Post-Build-Step "Publish Cppcheck results" not available in job generator project The issue is related to a particular version of Jenkins core together with quite old version of IE so I'm closing this task for Cppcheck plugin. Please open a new Jenkins core task if you want to continue with any investigation. Change By: Michal Turek (10/Oct/14 8:57 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [support-core] (JENKINS-25108) capture slave launch backlogs
SCM/JIRA link daemon commented on JENKINS-25108 capture slave launch backlogs Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/com/cloudbees/jenkins/support/impl/JenkinsLogs.java src/test/java/com/cloudbees/jenkins/support/SupportActionTest.java http://jenkins-ci.org/commit/support-core-plugin/b5f5b10f00dfb1916e678b8c0083a40b75dd75a8 Log: JENKINS-25108 Added a test Compare: https://github.com/jenkinsci/support-core-plugin/compare/536583973fec...b5f5b10f00df This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cppcheck] (JENKINS-23575) Post-Build-Step "Publish Cppcheck results" not available in job generator project
Michal Turek closed JENKINS-23575 as Fixed Post-Build-Step "Publish Cppcheck results" not available in job generator project Change By: Michal Turek (10/Oct/14 8:57 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] [cppcheck] (JENKINS-24007) Put a warning about report in legacy format to build log
Michal Turek closed JENKINS-24007 as Fixed Put a warning about report in legacy format to build log Change By: Michal Turek (10/Oct/14 8:57 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] [support-core] (JENKINS-25108) capture slave launch backlogs
SCM/JIRA link daemon resolved JENKINS-25108 as Fixed capture slave launch backlogs Change By: SCM/JIRA link daemon (10/Oct/14 8:58 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] [cppcheck] (JENKINS-23247) Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin.
Michal Turek closed JENKINS-23247 as Fixed Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin. Change By: Michal Turek (10/Oct/14 8:58 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] [support-core] (JENKINS-25108) capture slave launch backlogs
SCM/JIRA link daemon commented on JENKINS-25108 capture slave launch backlogs Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/com/cloudbees/jenkins/support/impl/JenkinsLogs.java http://jenkins-ci.org/commit/support-core-plugin/1c3337638f7af22d68c13872f5c997a022d1e5cb Log: [FIXED JENKINS-25108] The current implementation was only looking at the current connection of current slaves. In this new implementation, we capture log files from the current and the past connections of current and past slaves that have since then disappeared, such as a cloud. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Michal Turek commented on JENKINS-24076 Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) Please see comments in your pull request, they should be solved before merge. https://github.com/jenkinsci/cppcheck-plugin/pull/24 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [multijob-plugin] (JENKINS-25111) Ability to Copy Artifacts from a Phase Job
Ray Sennewald created JENKINS-25111 Ability to Copy Artifacts from a Phase Job Issue Type: New Feature Assignee: Ray Sennewald Components: multijob-plugin Created: 10/Oct/14 9:23 PM Description: We have MultiJob Projects setup in which we do a build in the first phase and test in the second phase. We want to grab the artifact from the first phase as part of the current MultiJob Build in the second phase as well as at the end of the MultiJob itself. It would be great if MultiJob Plugin could add support for this as Copy Artifact Plugin prefers this code to live in MultiJob Plugin as its specific for it. Project: Jenkins Priority: Major Reporter: Ray Sennewald This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [svnmerge] (JENKINS-14725) Build promotion leads to "Upstream Subversion URL is not specified"
Shibu Thampi commented on JENKINS-14725 Build promotion leads to "Upstream Subversion URL is not specified" We are facing the same issue on our project. Has anyone been able to get around 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] [gradle] (JENKINS-24682) Gradle Wrapper not working when gradle version was previously selected
SCM/JIRA link daemon commented on JENKINS-24682 Gradle Wrapper not working when gradle version was previously selected Code changed in jenkins User: Mario Mohr Path: src/main/java/hudson/plugins/gradle/Gradle.java src/main/java/hudson/plugins/gradle/GradleInstallation.java http://jenkins-ci.org/commit/gradle-plugin/ace07ad4e0a801fcb3afb37a907b83b21586e3a7 Log: [FIXED JENKINS-24682] Jenkins gradle installations are ignored if gradle wrapper is selected This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-24682) Gradle Wrapper not working when gradle version was previously selected
SCM/JIRA link daemon commented on JENKINS-24682 Gradle Wrapper not working when gradle version was previously selected Code changed in jenkins User: Gregory Boissinot Path: src/main/java/hudson/plugins/gradle/Gradle.java src/main/java/hudson/plugins/gradle/GradleInstallation.java http://jenkins-ci.org/commit/gradle-plugin/8730d78a456cad424db4061a272adb4b9631e9f3 Log: Merge pull request #23 from mamohr/JENKINS-24682 [FIXED JENKINS-24682] Compare: https://github.com/jenkinsci/gradle-plugin/compare/763256601be2...8730d78a456c This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-24682) Gradle Wrapper not working when gradle version was previously selected
SCM/JIRA link daemon resolved JENKINS-24682 as Fixed Gradle Wrapper not working when gradle version was previously selected Change By: SCM/JIRA link daemon (10/Oct/14 9:53 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-16327) Pages with CodeMirror editors are impossibly wide
Daniel Beck updated JENKINS-16327 Pages with CodeMirror editors are impossibly wide However, it's not as bad due to presence of workaround. Change By: Daniel Beck (10/Oct/14 9:57 PM) Priority: Major Trivial Labels: gui user-experience This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16327) Pages with CodeMirror editors are impossibly wide
Daniel Beck reopened JENKINS-16327 Pages with CodeMirror editors are impossibly wide I have no idea what I was thinking when I resolved this. My apologies. My comment just means there's a simple workaround, not that this isn't a bug. Change By: Daniel Beck (10/Oct/14 9:56 PM) Resolution: Not A Defect Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-8965) Send mail on a failed promotion
Lucas Meadows commented on JENKINS-8965 Send mail on a failed promotion +1. It would be really helpful if failed promotions could trigger an email. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-8965) Send mail on a failed promotion
Steve Mitchell commented on JENKINS-8965 Send mail on a failed promotion This can be done using the log parser and extended email plugins as follows: 1. Have your promotion execute an external script 2. Have the script, upon failure, print out an error message 3. Configure parsing rules for the log parser to recognize the error message and flag it as an error 4. Configure the extended email plugin to send the "promotion failed" email using a FAIL trigger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-8965) Send mail on a failed promotion
Steve Mitchell edited a comment on JENKINS-8965 Send mail on a failed promotion This can be done using the log parser and extended email plugins as follows: 1. Have your promotion execute an external script 2. Have the script, upon failure, print out an error message but not return any error code (i.e. catch the error) 3. Configure parsing rules for the log parser to recognize the error message and flag it as an error 4. Configure the extended email plugin to send the "promotion failed" email using a FAIL trigger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
Kanstantsin Shautsou commented on JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Please try wih maven-plugin-2.7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
Kanstantsin Shautsou edited a comment on JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Please try with maven-plugin-2.7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-19584) Ability to redirect user to configuration screen when erroneous data is saved
Jesse Glick updated JENKINS-19584 Ability to redirect user to configuration screen when erroneous data is saved Change By: Jesse Glick (11/Oct/14 1:32 AM) Labels: api form-data 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] [ssh-slaves] (JENKINS-20108) SSH slaves can block for a long time in NativePRNG
Kohsuke Kawaguchi
commented on JENKINS-20108
SSH slaves can block for a long time in NativePRNG
There are some pretty important dots missing here.
NativePRNG$RandomIO.implNextBytes() does unfortunately use a global lock, and this method gets called every time SecureRandom is used to generate more bytes. So one can imagine if lots of threads want to do this, the lock gets contended and slows down.
But NativePRNG$RandomIO.implNextBytes() doesn't use /dev/random by itself. It delegates to sun.security.provider.SecureRandom#engineNextBytes() (which is what getMixRandom() returns), then it reads from /dev/urandom (happen in ensureBufferValid) and XOR bytes.
// get pseudo random bytes
// read from /dev/urandom and XOR with bytes generated by the
// mixing SHA1PRNG
private void implNextBytes(byte[] data) {
synchronized (LOCK_GET_BYTES) {
try {
getMixRandom().engineNextBytes(data);
int len = data.length;
int ofs = 0;
while (len > 0) {
ensureBufferValid();
int bufferOfs = urandomBuffer.length - buffered;
while ((len > 0) && (buffered > 0)) {
data[ofs++] ^= urandomBuffer[bufferOfs++];
len--;
buffered--;
}
}
} catch (IOException e) {
throw new ProviderException("nextBytes() failed", e);
}
}
}
And sun.security.provider.SecureRandom#engineNextBytes() only uses seeder.engineNextBytes() once to create the initial hidden state, which means in the call path of NativePRNG.engineNextBytes() this only happens once in JVM. The rest is just SHA1 digest computation:
/**
* Generates a user-specified number of random bytes.
*
* @param bytes the array to be filled in with random bytes.
*/
public synchronized void engineNextBytes(byte[] result) {
int index = 0;
int todo;
byte[] output = remainder;
if (state == null) {
byte[] seed = new byte[DIGEST_SIZE];
SeederHolder.seeder.engineNextBytes(seed);
state = digest.digest(seed);
}
...
}
So whatever that seeder does (such as possibly accessing /dev/random and blocking), it can't impact the overall performance once!
What seems to be actually happening is that the {{-Djava.security.egd=file:/dev/./urandom}} property causes SecureRandomSpi to switch to the instance of sun.security.provider.SecureRandom, not sun.security.provider.NativePRNG, which entirely bypasses reading /dev/urandom and just go straight to SHA1 computation. This happens in sun.security.provider.SunEntries
static void putEntries(Map map) {
/*
* SecureRandom
*
* Register these first to speed up "new SecureRandom()",
* which iterates through the list of algorithms
*/
// register the native PRNG, if available
// if user selected /dev/urandom, we put it before SHA1PRNG,
// otherwise after it
boolean nativeAvailable = NativePRNG.isAvailable();
boolean useUrandom = seedSource.equals(URL_DEV_URANDOM);
if (nativeAvailable && useUrandom) {
map.put("SecureRandom.NativePRNG",
"sun.security.provider.NativePRNG");
}
map.put("SecureRandom.SHA1PRNG",
"sun.security.provider.SecureRandom");
if (nativeAvailable && !useUrandom) {
map.put("SecureRandom.NativePRNG",
"sun.security.provider.NativePRNG");
}
You can see the effect of this in the following simple program:
public class Foo {
public static void main(String[] args) throws Exception {
SecureRandom s = new SecureRandom();
System.out.println(s.getProvider());
Field f = s.getClass().getDeclaredField("secureRandomSpi");
f.setAccessible(true);
Object spi = f.get(s);
System.out.println(spi);
}
}
java.security.egd=file:/dev/./urandom
SUN version 1.6
sun.security.provider.SecureRandom@398020cc
java.security.egd=null
SUN version 1.6
sun.security.provider.NativePRNG@2bf14ceb
All this is doing is to bypass a global lock (and stop using /dev/urandom altogether), and yes, I can definitely see why that is a boon to the performance, but this has nothing to do with /dev/random blocking. The switch doesn't cause JVM to use /dev/urandom instead of /dev/random. It just bypasses both.
[JIRA] [ssh-slaves] (JENKINS-20108) SSH slaves can block for a long time in NativePRNG
Kohsuke Kawaguchi commented on JENKINS-20108 SSH slaves can block for a long time in NativePRNG Among other things, this means the suggestion to increase entropy of the system (such as the likes of haveged) is likely irrelevant. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18762) Build number environment variable is not propagated when run inside a conditional build step
SCM/JIRA link daemon commented on JENKINS-18762 Build number environment variable is not propagated when run inside a conditional build step Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/CopyArtifact.java http://jenkins-ci.org/commit/copyartifact-plugin/581c57e7068bca29cdbfcdb15419ac7d8e3b1fa4 Log: [FIXED JENKINS-16028] [FIXED JENKINS-18762] Adds EnvAction to hold COPYARTIFACT_BUILD_NUMBER_XXX when it's needed. It was added when a build starts and the build has copyartifact, which doesn't work for maven-project and copyartifacts wrapped in other builders. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18804) NPE TriggeredBuildSelector during CopyArtifact
SCM/JIRA link daemon resolved JENKINS-18804 as Fixed NPE TriggeredBuildSelector during CopyArtifact Change By: SCM/JIRA link daemon (11/Oct/14 5:16 AM) 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] [copyartifact] (JENKINS-16028) COPYARTIFACT_BUILD_NUMBER_ is not set when copyartifact plugin is ran as Maven pre-build
SCM/JIRA link daemon commented on JENKINS-16028 COPYARTIFACT_BUILD_NUMBER_ is not set when copyartifact plugin is ran as Maven pre-build Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/CopyArtifact.java http://jenkins-ci.org/commit/copyartifact-plugin/581c57e7068bca29cdbfcdb15419ac7d8e3b1fa4 Log: [FIXED JENKINS-16028] [FIXED JENKINS-18762] Adds EnvAction to hold COPYARTIFACT_BUILD_NUMBER_XXX when it's needed. It was added when a build starts and the build has copyartifact, which doesn't work for maven-project and copyartifacts wrapped in other builders. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18804) NPE TriggeredBuildSelector during CopyArtifact
SCM/JIRA link daemon commented on JENKINS-18804 NPE TriggeredBuildSelector during CopyArtifact Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/TriggeredBuildSelector.java src/test/java/hudson/plugins/copyartifact/TriggeredBuildSelectorTest.java src/test/java/hudson/plugins/copyartifact/testutils/RemoveUpstreamBuilder.java http://jenkins-ci.org/commit/copyartifact-plugin/22eb37c9763a1a67ebd199dbe507edabfc190068 Log: Merge pull request #46 from ikedam/feature/JENKINS-18804_FixNPEonTriggeredBuildSelector JENKINS-18804 Fix NPE in TriggeredBuildSelector Compare: https://github.com/jenkinsci/copyartifact-plugin/compare/9f7f31b6bfec...22eb37c9763a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16028) COPYARTIFACT_BUILD_NUMBER_ is not set when copyartifact plugin is ran as Maven pre-build
SCM/JIRA link daemon commented on JENKINS-16028 COPYARTIFACT_BUILD_NUMBER_ is not set when copyartifact plugin is ran as Maven pre-build Code changed in jenkins User: ikedam Path: src/test/java/hudson/plugins/copyartifact/CopyArtifactTest.java src/test/java/hudson/plugins/copyartifact/testutils/WrapperBuilder.java http://jenkins-ci.org/commit/copyartifact-plugin/6ccfac85e2f41a1152688408889849fb6c38f6b3 Log: JENKINS-16028 JENKINS-18762 Added tests to reproduce JENKINS-16028 (environment variables are not set in maven prebuild), JENKINS-18762 (environment variables are not set when wrapped in another builder). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18762) Build number environment variable is not propagated when run inside a conditional build step
SCM/JIRA link daemon commented on JENKINS-18762 Build number environment variable is not propagated when run inside a conditional build step Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/CopyArtifact.java src/test/java/hudson/plugins/copyartifact/CopyArtifactTest.java src/test/java/hudson/plugins/copyartifact/testutils/WrapperBuilder.java http://jenkins-ci.org/commit/copyartifact-plugin/c11b82688863105971e00cc27ad0501af436d903 Log: Merge pull request #47 from ikedam/feature/JENKINS-16028_EnvActionWhenNeeded JENKINS-16028 JENKINS-18762 Adds EnvAction when it's needed Compare: https://github.com/jenkinsci/copyartifact-plugin/compare/22eb37c9763a...c11b82688863 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18804) NPE TriggeredBuildSelector during CopyArtifact
SCM/JIRA link daemon commented on JENKINS-18804 NPE TriggeredBuildSelector during CopyArtifact Code changed in jenkins User: ikedam Path: src/test/java/hudson/plugins/copyartifact/TriggeredBuildSelectorTest.java src/test/java/hudson/plugins/copyartifact/testutils/RemoveUpstreamBuilder.java http://jenkins-ci.org/commit/copyartifact-plugin/72435901fdaea4c9202a771b752f205e6eb69462 Log: JENKINS-18804 Added a test to reproduce JENKINS-18804. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
