[JIRA] [build-timeout] (JENKINS-21910) Absolute build-timeout doesn't work on a simple sleep job
Aleksandra Fedorova commented on JENKINS-21910 Absolute build-timeout doesnt work on a simple sleep job I've restarted our Jenkins instance several times and install certain unrelated plugins, and now the issue is not reproducible anymore. I have no idea how can I debug this, so I guess we should just close the issue for now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-17439) Perforce Quick Clean Does Not Remove All Build Files; Fails to Halt the Build
Alexey Larsky commented on JENKINS-17439 Perforce Quick Clean Does Not Remove All Build Files; Fails to Halt the Build Update p4proxy 2010.2/341251 to 2013.3/740675 solve the issue. Before update p4proxy (2010.2/341251) version was less then p4d version (2011.1/428451). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-21910) Absolute build-timeout doesn't work on a simple sleep job
Oleg Nenashev commented on JENKINS-21910 Absolute build-timeout doesnt work on a simple sleep job OK, please attach build logs if you experience the issue again. I also recommend to use LTS versions of Jenkins like 1.509.x or 1.532.x, because they are much more stable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-21910) Absolute build-timeout doesn't work on a simple sleep job
Oleg Nenashev resolved JENKINS-21910 as Cannot Reproduce Absolute build-timeout doesnt work on a simple sleep job Change By: Oleg Nenashev (17/Mar/14 6:39 AM) Status: Open Resolved Assignee: KohsukeKawaguchi Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22142) No autocompletion and NullPointerException when using 'Copy Existing Job'
Florian P commented on JENKINS-22142 No autocompletion and NullPointerException when using Copy Existing Job All my plugins are up-to-date (as of 2014-03-17) and Jenkins is at 1.554. Restarting does not solve the issue for 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] [sctmexecutor] (JENKINS-22198) Plugin cannot find target service sccentities with SCTM 15
Sebastian Kornexl started work on JENKINS-22198 Plugin cannot find target service sccentities with SCTM 15 Change By: Sebastian Kornexl (17/Mar/14 7:33 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sctmexecutor] (JENKINS-22198) Plugin cannot find target service sccentities with SCTM 15
Sebastian Kornexl commented on JENKINS-22198 Plugin cannot find target service sccentities with SCTM 15 Can you please try specifying the service URL as: http://host/services withtout the Services1.0? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cifs] (JENKINS-22217) Integrate with Jenkins Credentials Management
Markus KARG created JENKINS-22217 Integrate with Jenkins Credentials Management Issue Type: New Feature Assignee: Alex Earl Components: cifs Created: 17/Mar/14 7:53 AM Description: Would be great if the "Publish over CIFS" plugin would not provide its own authentication configuration, but simply integrate with the Jenkins Credentials Management. So admins can have all the credentials in one central place, and be assured that the same safety is guaranteed as with Jenkins itself. Project: Jenkins Priority: Major Reporter: Markus KARG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cifs] (JENKINS-22218) Connecting CIFS share is very, very slow
Markus KARG created JENKINS-22218 Connecting CIFS share is very, very slow Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: cifs Created: 17/Mar/14 7:57 AM Description: Pressing the "Test Connection" button needs several minutes to say that the connection was successful. Also connecting at runtime needs very, very long time. Feels like some kind of incompatibility with W2K8R2 DC / W2K8R2 Share. The same share and DC work fast and nearly instantly reacting when using SMBFS on the Debian-driven master; it's really only the CIFS plugin which is so slow. Would be great if this could be fixed. I am willing to provide more information and do some tests, once I am exactly told what to do. Environment: LTS 1.532.2 (Master on Debian Wheezy; Slave on Windows 7); Share is on Windows Server 2008 R2; DC is Windows Server 2008 R2. Project: Jenkins Priority: Major Reporter: Markus KARG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-14122) Build Executors on Nodes enter infinite hang
Martin Schröder commented on JENKINS-14122 Build Executors on Nodes enter infinite hang Update: We've now encountered this very same bug again. Our servers are still on 1.509.3, pending full internal testing and release of the new LTS version (1.532.2). Therefore, we can only report that the bug still exists, but is as always very rarely triggered. Incidence rate has slowed down to roughly once in 6 months. We will post an update if it appears in the new LTS version too, once we have deployed it. But, given the rarity of the bug, it might be another 6 months until we can post an update. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14122) Build Executors on Nodes enter infinite hang
Martin Schröder edited a comment on JENKINS-14122 Build Executors on Nodes enter infinite hang Update: We've now encountered this very same bug again. Our servers are still on 1.509.3, pending full internal testing and release of the new LTS version (1.532.2). Therefore, we can only report that the bug still exists, but is (as reported before) very rarely triggered. Incidence rate has slowed down to roughly once in 6 months. We will post an update if it appears in the new LTS version too, once we have deployed it. But, given the rarity of the bug, it might be another 6 months until we can post an update. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cifs] (JENKINS-22219) Publish over CIFS complains that field is empty, but actually it is filled out AND WORKS!
Markus KARG
created JENKINS-22219
Publish over CIFS complains that field is empty, but actually it is filled out AND WORKS!
Issue Type:
Bug
Affects Versions:
current
Assignee:
Alex Earl
Components:
cifs
Created:
17/Mar/14 9:10 AM
Description:
Plugin configuration always complains that CIFS share is needed ("Required. Cannot contain ' " \") but actually the name is given. It seems there is a bug in the field validation, i. e. it does not really check whether something is provided.
This worked in LTS 1.509, but only happens since I upgraded to LTS 1.532.2!
Environment:
LTS 1.532.2
Project:
Jenkins
Priority:
Major
Reporter:
Markus KARG
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-lint] (JENKINS-22206) FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found on Windows 7 with JDK 7
Christopher Orr resolved JENKINS-22206 as Duplicate FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found on Windows 7 with JDK 7 This seems to be a duplicate of JENKINS-14689 — the problem appears not to be in the Lint or Static Analysis plugins, rather than a Java / classloading issue. It seems making sure your slave.jar is up-to-date could help. Change By: Christopher Orr (17/Mar/14 9:15 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] [core] (JENKINS-22142) No autocompletion and NullPointerException when using 'Copy Existing Job'
Croesus Kall commented on JENKINS-22142 No autocompletion and NullPointerException when using Copy Existing Job Same problem here. Running jenkins 1.553, all plugins are up-to-date This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-22202) ghprb always send a comment to GitHub
Troels Nørgaard commented on JENKINS-22202 ghprb always send a comment to GitHub We are facing the same issues and decided to make a pull-request for a config property to control this issue. However we have yet received feedback - input is much appreciated: https://github.com/janinko/ghprb/pull/126. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-18377) Performance problem when listing many jobs
Croesus Kall commented on JENKINS-18377 Performance problem when listing many jobs I still have this problem - so I wouldn't say it was obsolete. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs] (JENKINS-22102) NodeJS plugin does not remember the saved NodeJS Installation
Marc Günther commented on JENKINS-22102 NodeJS plugin does not remember the saved NodeJS Installation BTW, the popup in the "Provide Node npm bin/ folder to PATH" works perfectly fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-18377) Performance problem when listing many jobs
Oleg Nenashev commented on JENKINS-18377 Performance problem when listing many jobs Fixes in the core (JENKINS-18721) are available since 1.532. It partially resolves the issue, but I confirm that there are many improvements to be done inside the plugin. I'm going to keep the issue. BTW, the priority could be decreased if there is no critical performance complains. As a workaround, you can use RoleMacros (e.g. from the Ownership plugin). They greatly reduce the calculation speed due to the internal caching This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
michael soukup commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Under Windows you can use findstr findstr "" %appdata%\Subversion\auth\svn.simple\* unfortunately findstr is way not as flexible as grep, so you cannot print the lines following realmstring but only the line that contains it. This is why I chose to look for the "" instead. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cifs] (JENKINS-22218) Connecting CIFS share is very, very slow
Markus KARG commented on JENKINS-22218 Connecting CIFS share is very, very slow Just noticed that it connects lightning fast when using a local user account defined in the CIFS server itself. Hence, the delay only happens when using a domain user defined in the W2K8R2 DC! Maybe this helps to find out what the cause is or how a tweak could look like? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink] (JENKINS-22220) TestLink Plugin is not executing testng method and showing Not Run in jenkins excution report
Dattatrya More created JENKINS-0 TestLink Plugin is not executing testng method and showing Not Run in jenkins excution report Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: ConceptTest.java, Jenkins_TestLink_Test_execution_result.png, TC000-1_Login_test.png, TC000-2_Registration_test.png, TestLink_Configuration_abd_test_execution.png, TestLink_custum_Field.png Components: testlink, testng Created: 17/Mar/14 10:34 AM Description: TestLink Plugin is not executing testng method and showing Not Run in jenkins execution report Following are testlink, jenkins and testlink plug in versions that used for configuration. TestLink 1.9.9 Jenkins ver. 1.523 Jenkins TestLink Plugin - 3.10 Created testlink project,testplan and custom fields, refer attachments for details. In test suite, 2 test cases are present Login test which uses following java class to execute com.mycompany.myproject.testscripts.ConceptTest and for this used custom field is - TestMethod java class com.mycompany.myproject.testscripts.ConceptTest contains several testng methods refer attached source file eg login, registration etc Registration test used following value for custom field TestMethod: com.mycompany.myproject.testscripts.ConceptTest#TestLinkTest11 Actual registration test script present in testng method - TestLinkTest11 After executing above configuration jenkins and testlink test execution result says - Not run in result screen. refer screenshots for reference Project: Jenkins Labels: plugin Priority: Major Reporter: Dattatrya More This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-reports] (JENKINS-21703) Cucumber Test results plugin
Andrey Regentov commented on JENKINS-21703 Cucumber Test results plugin Just the same here. Maybe it is connected with "scenario outline" vs "scenario". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cifs] (JENKINS-22218) Connecting CIFS share is very, very slow
Markus KARG commented on JENKINS-22218 Connecting CIFS share is very, very slow I have verified that it is definitively NOT the type of CIFS target which plays a role, as I was able to reproduce the problem by using CIFS shared on Windows 7 and XP. The problem happens with both, and both work lightning fast with local user accounts. Hence, the problem really is located on the W2K8R2DC. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-16961) memory leak in Build Pipeline plugin (BuildForm)
Marc Günther commented on JENKINS-16961 memory leak in Build Pipeline plugin (BuildForm) Any progress on this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-reports] (JENKINS-21703) Cucumber Test results plugin
Andrey Regentov edited a comment on JENKINS-21703 Cucumber Test results plugin Just the same here. Maybe it is connected with "scenario outline" vs "scenario". See jenkins-21835 for details. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs] (JENKINS-21256) Findbug: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
David Frank commented on JENKINS-21256 Findbug: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory sorry - have not test system to test pre-releases; but now that it has been released I can confirm that FindBugsPublisher 4.56 on jenkins 1.554 works fine. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release] (JENKINS-15983) Possibility to define a custom SCM tag in project config
Anders Hammar commented on JENKINS-15983 Possibility to define a custom SCM tag in project config I think that any tagNameFormat of the m-release-p should be respected. Haven't checked the pull request for this ticket, but if is a configuration on build porject level I think using tagNameFormat is much better. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-15983) Possibility to define a custom SCM tag in project config
Anders Hammar edited a comment on JENKINS-15983 Possibility to define a custom SCM tag in project config Any tagNameFormat config of the m-release-p is respected. But if you select "Specify custom SCM tag" it is not shown as the default. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22039) git init is failing with a file exists error
Mark Waite commented on JENKINS-22039 git init is failing with a file exists error I believe the failure case you're detecting is for the case when a "fast remote poll" is used with the command line git implementation. The git-client-plugin needs to create a temporary local git repository for its operations, but makes the mistake of not generating a completely unique directory name. I assume JGit works reliably because it creates the temporary directory with a unique name each time. The problem will likely only be visible on Windows due to the more restrictive file locking rules of the Windows file system. The problem is not detected by any of the unit tests in the git-client-plugin because it is in an authentication area and there are currently no authentication tests for the git-client-plugin. I hope to learn enough about authentication in the git-client-plugin to create many tests for it, but it has been very slow progress. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22221) Make emulator timezone configurable
Per Henden
created JENKINS-1
Make emulator timezone configurable
Issue Type:
New Feature
Affects Versions:
current
Assignee:
Christopher Orr
Components:
android-emulator
Created:
17/Mar/14 12:51 PM
Description:
My app makes certain date/time checks and it would be useful to be able to set the timezone for the emulator in the Android Emulator Plugin's configuration.
A more generic solution could be to configure a list of properties (with values) that are set after the emulator has booted.
For now, as a workaround, I do "adb -s ${ANDROID_SERIAL} shell setprop persist.sys.timezone 'Europe/Amsterdam'" after the emulator has booted, and before my app is installed and runs its tests.
Project:
Jenkins
Priority:
Minor
Reporter:
Per Henden
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22039) git init is failing with a file exists error
Mark Waite edited a comment on JENKINS-22039 git init is failing with a file exists error I believe the failure case you're detecting is for the case when a "fast remote poll" is used with the command line git implementation. The git-client-plugin needs to create a temporary local git repository for its operations, but makes the mistake of not generating a completely unique directory name. I assume JGit works reliably because it creates the temporary directory with a unique name each time. The problem will likely only be visible on Windows due to the more restrictive file locking rules of the Windows file system. The problem is not detected by any of the unit tests in the git-client-plugin because it is in an authentication area and there are currently no authentication tests for the git-client-plugin. I hope to learn enough about authentication in the git-client-plugin to create many tests for it, but it has been very slow progress. If you want to test my theory, you should be able to cause the problem to be consistently repeatable if you create a plain file named ".git" in your system temporary directory. Something like C:\ echo "hello world" %TEMP%\.git Once that plain file is created, I believe the attempt to call "git init" for remote polling using command line git will fail consistently. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22039) git init is failing with a file exists error
Mark Waite edited a comment on JENKINS-22039 git init is failing with a file exists error I believe the failure case you're detecting is for the case when a "fast remote poll" is used with the command line git implementation. The git-client-plugin needs to create a temporary local git repository for its operations, but makes the mistake of not generating a completely unique directory name. I assume JGit works reliably because it creates the temporary directory with a unique name each time. The problem will likely only be visible on Windows due to the more restrictive file locking rules of the Windows file system. The problem is not detected by any of the unit tests in the git-client-plugin because it is in an authentication area and there are currently no authentication tests for the git-client-plugin. I hope to learn enough about authentication in the git-client-plugin to create many tests for it, but it has been very slow progress. If you want to test my theory, you should be able to cause the problem to be consistently repeatable if you create a plain file named ".git" in your system temporary directory. Something like C:\ echo "hello world" %TEMP%\.git Once that plain file is created, I believe the attempt to call "git init" for remote polling using command line git will fail consistently. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Mark Waite resolved JENKINS-21952 as Fixed Git Plugin fails to resolve tags containing a slash since 2.0.1 Fix should be visible in the next git-plugin after 2.0.4 Change By: Mark Waite (17/Mar/14 1:08 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] [extensible-choice-parameter] (JENKINS-22222) Extend name pattern to use dots too
Sven Appenrodt created JENKINS-2 Extend name pattern to use dots too Issue Type: Task Affects Versions: current Assignee: Unassigned Components: extensible-choice-parameter Created: 17/Mar/14 1:09 PM Description: After the parameterized trigger plugin wants to exchange all choices to extensible choices we have to change many properties in our jobs. But that's OK. Problem: Because of many of our properties containing dots we have to overwork half of our build process. Suggestion: Please check if the name of a property can contain . too. Environment: rely on https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin#ParameterizedTriggerPlugin-Backwardcompatibilitywithversion2.22 Project: Jenkins Priority: Minor Reporter: Sven Appenrodt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cifs] (JENKINS-22223) Integrate with Maven plugin
Markus KARG created JENKINS-3 Integrate with Maven plugin Issue Type: New Feature Affects Versions: current Assignee: Alex Earl Components: cifs Created: 17/Mar/14 1:14 PM Description: Due to the tight integration of Maven with Jenkins, it would be pretty cool if the Publish-Over-CIFS plugin would learn to get a list of all artifacts from Maven, and add these automatically to the files to copy. This would take away the burden that the files to publish have to be provided manually in the job description, and open the way for dynamic file lists (i. e. Maven decides when building what the current files to copy are). Since by default Maven adds a version suffix to files, this is much cleaner than adding a wildcard in the job description. Project: Jenkins Priority: Major Reporter: Markus KARG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22039) git init is failing with a file exists error
Mark Waite edited a comment on JENKINS-22039 git init is failing with a file exists error I believe the failure case you're detecting is for the case when a "fast remote poll" is used with the command line git implementation. The git-client-plugin needs to create a temporary local git repository for its operations, but makes the mistake of not generating a completely unique directory name. I assume JGit works reliably because it creates the temporary directory with a unique name each time. The problem will likely only be visible on Windows due to the more restrictive file locking rules of the Windows file system. The problem is not detected by any of the unit tests in the git-client-plugin because it is in an authentication area and there are currently no authentication tests for the git-client-plugin. I hope to learn enough about authentication in the git-client-plugin to create many tests for it, but it has been very slow progress. If you want to test my theory, you should be able to cause the problem to be consistently repeatable if you create a plain file named ".git" in your system temporary directory. Something like C:\ echo "hello world" %TEMP%\.git Once that plain file is created, I believe the attempt to call "git init" for remote polling using command line git will fail consistently. I confirmed that a similar failure mode can be created on Unix variants by creating a plain file named /tmp/.git to which the Jenkins process user cannot write: $ sudo touch /tmp/.git This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extensible-choice-parameter] (JENKINS-22222) Extend name pattern to use dots too
Sven Appenrodt commented on JENKINS-2 Extend name pattern to use dots too Hint: getting triggerd by the parameterized trigger plugin whith having a choice "foo.bar" works, only the validation check for this field fails. Didn't tested accessing the choice via e.g. groovy... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-22224) one job configuration change results in three Job Config History entries
Marc Günther created JENKINS-4 one job configuration change results in three Job Config History entries Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage, jobconfighistory Created: 17/Mar/14 1:42 PM Description: Every time I make a configuration change to a job, I get three entries in the Job Config History view: removal of the config for disk-usage plugin actual change I made add of the config of disk-usage again The removed and re-added line looks like this: hudson.plugins.disk__usage.DiskUsageProperty plugin="disk-usage@0.23"/ Expected: 1. and 3. should not happen.. Project: Jenkins Priority: Minor Reporter: Marc Günther This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-9505) Add description as release #${release.version}
Anders Hammar
commented on JENKINS-9505
Add description as release #${release.version}
You get this info on the release badge, isn't that enough?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium] (JENKINS-12842) Allow to pass proxy and other system properties to selenium grid
Michael Bannister commented on JENKINS-12842 Allow to pass proxy and other system properties to selenium grid I've recently had to significantly increase the heap size for my main Jenkins process (running under Tomcat) and I've noticed that the Hub gets launched with the same environment and therefore the same JVM args (so it's being allocated massively more heap than it needs). I'd love to find a way round this! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cifs] (JENKINS-22223) Integrate with Maven plugin
Alex Earl assigned JENKINS-3 to Unassigned Integrate with Maven plugin Change By: Alex Earl (17/Mar/14 2:06 PM) Assignee: AlexEarl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cifs] (JENKINS-22219) Publish over CIFS complains that field is empty, but actually it is filled out AND WORKS!
Alex Earl assigned JENKINS-22219 to Unassigned Publish over CIFS complains that field is empty, but actually it is filled out AND WORKS! Change By: Alex Earl (17/Mar/14 2:06 PM) Assignee: AlexEarl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cifs] (JENKINS-22217) Integrate with Jenkins Credentials Management
Alex Earl assigned JENKINS-22217 to Unassigned Integrate with Jenkins Credentials Management Change By: Alex Earl (17/Mar/14 2:06 PM) Assignee: AlexEarl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cifs] (JENKINS-22218) Connecting CIFS share is very, very slow
Alex Earl assigned JENKINS-22218 to Unassigned Connecting CIFS share is very, very slow Change By: Alex Earl (17/Mar/14 2:07 PM) Assignee: AlexEarl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-22224) one job configuration change results in three Job Config History entries
Marc Günther
updated JENKINS-4
one job configuration change results in three Job Config History entries
Change By:
Marc Günther
(17/Mar/14 2:17 PM)
Description:
EverytimeImakeaconfigurationchangetoajob,IgetthreeentriesintheJobConfigHistoryview:#removaloftheconfigfor{{disk-usage}}plugin#actualchangeImade#
add
addition
oftheconfigof{{disk-usage}}againTheremovedandre-addedlinelookslikethis:{code}hudson.plugins.disk__usage.DiskUsagePropertyplugin=disk-usage@0.23/{code}Expected:1.and3.shouldnothappen..
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Jesse Glick commented on JENKINS-21905 intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream There is no relevant logging. Fixing this would really hinge on finding a fully reproducible test case. Or, someone with detailed knowledge of jzlib would need to inject low-level diagnostics, as we did for JENKINS-20618 and JENKINS-20114. Unfortunately an EOFException is very generic and I cannot think of a diagnostic other than capturing the entire stream to that point, which would be unacceptable from a performance standpoint. (How large are your artifacts?) It would be nice to use the standard gzip support in the JRE. Unfortunately, that seems to cause occasional 100% CPU freezes that were a major issue for many Jenkins users (worse than issues like this). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22064) Git Repository Browser URL not saved anymore
andrew stern commented on JENKINS-22064 Git Repository Browser URL not saved anymore I tried the workaround since I'm having the same issue after upgrading to the current versions and it didn't work. The information being provided by my webview into git is no longer showing up in my Jenkins build display under changes. It was working before the change and adding it back into the file didn't fix the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-17262) Remotely triggered build with parameters failing with extended choice parameters
amirkibbar commented on JENKINS-17262 Remotely triggered build with parameters failing with extended choice parameters just ran into this issue, here's the response from the jenkins cli when activating a build with a choice parameter: CLI parameter submission is not supported for the class com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition type. Please file a bug report for this I'm using Jenkins 1.555 and Extended Choice Parameter Plug-In 0.30 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22212) No e-mail sent after failed build triggered from another build
ikedam commented on JENKINS-22212 No e-mail sent after failed build triggered from another build "Developers" extracts users to send a mail from changelog. Please look at change logs of downstream (deployment) build. Does it properly report changes as upstream build? If no change logs are recorded in the downstream build, "Developers" does not work correct. "Culprits" provides extraction from upstream builds by setting system property hudson.upstreamCulprits to true. It can be set by launching your Jenkins as java -Dhudson.upstreamCulprits=true jenkins.jar Please see https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties for more details. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22064) Git Repository Browser URL not saved anymore
Marc Günther commented on JENKINS-22064 Git Repository Browser URL not saved anymore I guess you need to "Reload Configuration" after editing the file. I never use "Reload Configuration" myself, though, as it has been a constant source of problems in the past. Another workaround might be to switch back to "(Auto)", as long as you have at least one untouched project with the same repository left. Yet another solution would be a small Groovy script, which calculates the correct browser URL based on the repo URL. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22064) Git Repository Browser URL not saved anymore
Alexander Ost commented on JENKINS-22064 Git Repository Browser URL not saved anymore This was working fine still with git-plugin version 2.0 and git-client-plugin version 1.6.0. Probably the problem is related to this commit: https://github.com/jenkinsci/git-plugin/commit/7abfafcf58addbce2c268dbfed1910a90d4fe2a3 I'm not enough into Jenkins coding to fix this myself quickly, but Nicolas is already listed as assignee here (thanks!). I hope it's an easy fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cifs] (JENKINS-22225) Doesn't copy files with blanks in file name
Markus KARG created JENKINS-5 Doesnt copy files with blanks in file name Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: cifs Created: 17/Mar/14 2:38 PM Description: When there is a blank in the file name, the plugin does not find the file to copy. I confirm that the following workaround is working well: Replace blank by asterisk wildcard. Project: Jenkins Priority: Critical Reporter: Markus KARG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22211) Parallel stages display distorted
Johan Bloemberg commented on JENKINS-22211 Parallel stages display distorted We experience the same issue with our pipeline. Version 0.7.1. Using trigger parameterized build if that would make a difference. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22211) Parallel stages display distorted
Johan Bloemberg updated JENKINS-22211 Parallel stages display distorted Change By: Johan Bloemberg (17/Mar/14 2:50 PM) Attachment: ScreenShot2014-03-17at15.49.16.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-21009) Allow manual trigger
Johan Bloemberg commented on JENKINS-21009 Allow manual trigger +1, I would love to see this feature. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud] (JENKINS-22025) VM cannot be started repeatedly with vSphere plugin
Jerry Maloney commented on JENKINS-22025 VM cannot be started repeatedly with vSphere plugin Eric Lordahl, that was, in fact, my problem. I didn't have VMware tools installed and so the VM did not have an IP assigned. Thanks for the help! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cifs] (JENKINS-22225) Doesn't copy files with blanks in file name
Alex Earl assigned JENKINS-5 to Unassigned Doesnt copy files with blanks in file name Change By: Alex Earl (17/Mar/14 3:01 PM) Assignee: AlexEarl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mesos] (JENKINS-22054) Failed to instantiate class org.jenkinsci.plugins.mesos.MesosCloud from
Marcelo Labardini commented on JENKINS-22054 Failed to instantiate class org.jenkinsci.plugins.mesos.MesosCloud from This has prevented me from using the Mesos-Jenkins integration...please help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extensible-choice-parameter] (JENKINS-22222) Extend name pattern to use dots too
ikedam commented on JENKINS-2 Extend name pattern to use dots too It depends on how to use it. If used in shell or windows batch, it would does not work correct. Current parameter name check is performed under the rule of bash (alphabets, numbers, underscore). Though I haven't tested yet, it would work correct in almost other cases even the configuration page displays an error. Groovy scripts would also work well as they access build variables as a map object. I'll ask Jenkins developers whether there is a guideline about parameter names, and consider what's the best way. For now, I think followings are good for your case. Test parameters with dots work correct in your environments. Error messages in configuration pages are just informational, and Extensible Choice Parameter does not kick those values even in future releases. But I cannot ensure Jenkins itself accepts any values even in future reases... I still recommend you to use bash-like parameter names if you can easily adapt it. There may be a day you want to access those values from bash scripts or windows batches. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter] (JENKINS-22226) Triggering a build with a parameterized node label is stuck in Pending - waiting for executors...
Justin Huot created JENKINS-6 Triggering a build with a parameterized node label is stuck in Pending - waiting for executors... Issue Type: Bug Affects Versions: current Assignee: Dominik Bartholdi Components: nodelabelparameter, parameterized-trigger, parameters Created: 17/Mar/14 3:28 PM Description: When trying to manually build a Multi-configuration project with parameters the build never gets past the Queue phase. Attempted to create a 2nd project that will trigger the multi-configuration project on a different node from master and same result. If parameters are removed the build will run on all nodes selected without issue. Job Config: Checked - Parameterized Name: HOST_NAME Default Nodes: master Possible Nodes: Selected Nodes Allow multi node selection concurrent builds Node eligibility: Ignore Offline Nodes Checked - Execute concurrent builds if necessary No Advanced Project Options (Restrict, Quiet, Retry, Blocking, Custom) Source Code Management: GIT Configuration Matrix Slaves - Name: label Node/Label: Individual Nodes (Valid Nodes selected) Build: Powershell Scripts Post Build: Editable Email Notification (Default Settings) Queue Message: #4 (pending—Waiting for next available executor on Node Name) [NodeParameterValue: HOST_NAME=Node Name All the Executors are open and other jobs can be ran on the selected Nodes. Project: Jenkins Labels: Parameterized Node 1.555 Priority: Major Reporter: Justin Huot This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22212) No e-mail sent after failed build triggered from another build
Alexander Obuhovich commented on JENKINS-22212 No e-mail sent after failed build triggered from another build "Developers" extracts users to send a mail from changelog. Please look at change logs of downstream (deployment) build. Does it properly report changes as upstream build? Nope it doesn't. The downstream job has "No Changes" in the "Changes" tab on the each build page. If a downstream job has no SCM integration, then I wonder how the upstream job, that has it can pass that info to downstream job. Setting up a SCM integration for downstream job isn't a good idea, since I use a single downstream job to deploy probjects from different other jobs, where each has own SVN project path. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build
Alexander Obuhovich edited a comment on JENKINS-22212 No e-mail sent after failed build triggered from another build "Developers" extracts users to send a mail from changelog. Please look at change logs of downstream (deployment) build. Does it properly report changes as upstream build? Nope it doesn't. The downstream job has "No Changes" in the "Changes" tab on the each build page. If a downstream job has no SCM integration, then I wonder how the upstream job, that has it can pass that info to downstream job. Setting up a SCM integration for downstream job isn't a good idea, since I use a single downstream job to deploy probjects from different other jobs, where each has own SVN project path. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build
Alexander Obuhovich edited a comment on JENKINS-22212 No e-mail sent after failed build triggered from another build "Developers" extracts users to send a mail from changelog. Please look at change logs of downstream (deployment) build. Does it properly report changes as upstream build? Nope it doesn't. The downstream job has "No Changes" in the "Changes" tab on the each build page. If a downstream job has no SCM integration, then I wonder how the upstream job, that has it can pass that info to downstream job. Setting up a SCM integration for downstream job isn't a good idea, since I use a single downstream job to deploy probjects from different other jobs, where each has own SVN project path. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build
Alexander Obuhovich commented on JENKINS-22212 No e-mail sent after failed build triggered from another build Please see https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties for more details. The "Culprits" isn't exactly same user list as one in "Developers". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sctmexecutor] (JENKINS-22198) Plugin cannot find target service sccentities with SCTM 15
Mitch Myers commented on JENKINS-22198 Plugin cannot find target service sccentities with SCTM 15 The URL, http://host/services does work. Thanks for the help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22227) invalid update-center.json is provided
Bernhard Berbuir created JENKINS-7 invalid update-center.json is provided Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 17/Mar/14 3:52 PM Description: The JSON file provided by both update center URLs: Update Center Update Center LTS is invalid. It contains updateCenter.post( as the first line and ); as the last line but must only contain the second line, which is valid JSON. Environment: all Project: Jenkins Priority: Blocker Reporter: Bernhard Berbuir This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [security] (JENKINS-22228) Cannot save setting on configure global security page
Sidharth Arora created JENKINS-8 Cannot save setting on configure global security page Issue Type: Bug Assignee: Unassigned Components: security Created: 17/Mar/14 3:58 PM Description: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at
[JIRA] [security] (JENKINS-22228) Cannot save setting on configure global security page
Sidharth Arora commented on JENKINS-8 Cannot save setting on configure global security page Jenkins Version is 1.551 and i do not have the Trac plugin installed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [security] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
m_broida commented on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session I apologize for not reading the earlier posts in more detail. I added the LogRecorder and the logger as described above. When I logout and back in, this (among other detail) shows in the log: Mar 17, 2014 3:49:09 PM FINE org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices loginSuccess Added remember-me cookie for user 'michael.broida', expiry: 'Mon Mar 31 15:49:09 GMT 2014' So its set to expire in two weeks: Mar 31 - Mar 17 = 14 days. My system time was about 10:49AM (US CDT) and the Jenkins Master node time was: 3:49:09PM (UTC). So those line up correctly: US CDT = UTC-5. I see log entries like this one cleansed, apparently every time I click a Jenkins link: Mar 17, 2014 3:49:09 PM FINE org.acegisecurity.ui.rememberme.RememberMeProcessingFilter doFilter SecurityContextHolder not populated with remember-me token, as it already contained: 'org.acegisecurity.providers.UsernamePasswordAuthenticationToken@f05122ff: Username: org.acegisecurity.userdetails.User@0: Username: michael.broida; Password: PROTECTED; Enabled: true; AccountNonExpired: true; credentialsNonExpired: true; AccountNonLocked: true; Granted Authorities: authenticated, USER, admin; Password: PROTECTED; Authenticated: true; Details: org.acegisecurity.ui.WebAuthenticationDetails@957e: RemoteIpAddress: nn.nn.nn.nn; SessionId: 178z3b1pbslvm1hyjg8qchd6wo; Granted Authorities: authenticated, USER, admin' Chrome shows an ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE cookie with same Mar 31 expiration as above. We'll see if Jenkins logs me out in the next couple of hours This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-16278) Remember me on this computer does not work, cookie is not accepted in new session
Jesse Glick updated JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session Change By: Jesse Glick (17/Mar/14 4:19 PM) Labels: 1.480.3-fixed security Component/s: core Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22064) Git Repository Browser URL not saved anymore
Mark Waite commented on JENKINS-22064 Git Repository Browser URL not saved anymore There is a pull request ( https://github.com/jenkinsci/git-plugin/pull/211 ) for a test which I believe shows the problem, but that is only a test, and I can't be sure it actually exercises the bug until the bug is 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-21191) Add support of views without automatic refresh
Jesse Glick updated JENKINS-21191 Add support of views without automatic refresh Change By: Jesse Glick (17/Mar/14 4:28 PM) Labels: api jellyview This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-16343) Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.
Angel Williams commented on JENKINS-16343 Access to the Subversion repository doesnt work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error. I am currently using: Jenkins 1.546 with Subversion Plugin: 2.2 and Credentials Plugin: 1.1 I was able to fix the builds so they at least downloaded by opending tortoiseSVN on each Node and saving the password for the Repository. At least now I have builds. Which means I have to store credentials on systems for this to work and that is not good especially since it is my credentials. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-16343) Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.
Angel Williams edited a comment on JENKINS-16343 Access to the Subversion repository doesnt work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error. I am currently using: Jenkins 1.546 with Subversion Plugin: 2.2 and Credentials Plugin: 1.1 I was able to fix the builds so they at least downloaded by opending tortoiseSVN on each Node and saving the password for the Repository. At least now I have builds. Which means I have to store credentials on systems for this to work and that is not good especially since it is my credentials. I tried going to current Jenkins 1.554 recently but all my Windows Slaves no longer connected so I need to make sure any upgrades are going to work because I do not want to store credentials on all the slave machines. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22229) Build from properties file fails if workspace does not exist
Caleb Mayeux
created JENKINS-9
Build from properties file fails if workspace does not exist
Issue Type:
Bug
Affects Versions:
current
Assignee:
huybrechts
Components:
parameterized-trigger
Created:
17/Mar/14 4:43 PM
Description:
Due to a change implemented in JENKINS-21013(FileBuildParameters.java: ~100), if the workspace does not exist, the attempt to read parameters from that file is skipped. However, there is nothing that restricts the parameter file to be in the workspace, so the check is inaccurately flagging that the parameter file doesn't need to be searched for.
I place parameter files in ${WORKSPACE}/.. so that I could use the workspace cleanup plugin along with the trigger parameterized build plugin. Since the workspace is cleaned up on jobs first, now the parameterized build trigger skips the check and doesn't read the parameter file, even though it exists. I would think this is a fairly typical use case scenario, but have no evidence to support this.
It would be nice if that check was taken out, so parameter files could once again be anywhere on the build slave.
Environment:
RHEL 5.5, Jenkins 1.551, parameterized trigger 2.23 and later.
Project:
Jenkins
Priority:
Minor
Reporter:
Caleb Mayeux
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-21579) Very slow resource loading from UberClassLoader
Steve Roth commented on JENKINS-21579 Very slow resource loading from UberClassLoader I cannot say with certainty, but I think this started appearing in 1.553. I dont think I have seen this since reverting to 1.552. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [postbuildscript] (JENKINS-22230) PostBuildScript updates job configuration every time job runs
Jakub Czaplicki created JENKINS-22230 PostBuildScript updates job configuration every time job runs Issue Type: Bug Assignee: Gregory Boissinot Components: postbuildscript Created: 17/Mar/14 5:11 PM Description: When a Post-build Action is added to a job, its configuration is being updated by user SYSTEM every time the job runs. The updated value is always time. An example of how the job config diff looks like: 36 generatedtrue/generated 37 exposedToEnvironmentfalse/exposedToEnvironment 38 value -39 time1394798774448/time +39 time1394800224909/time 40 timezoneEurope/London/timezone 41 /value 42 checkedfalse/checked Another example: 39 generatedtrue/generated 40 exposedToEnvironmentfalse/exposedToEnvironment 41 value - 42time1395074512487/time + 42time1395074516623/time 43timezoneEurope/London/timezone 44 /value 45 checkedfalse/checked ... 56 parent class="metadata-tree" reference="../../.."/ 57 generatedtrue/generated 58 exposedToEnvironmentfalse/exposedToEnvironment - 59 valuejakub/value + 59 valueSYSTEM/value 60/metadata-string 61metadata-string 62 namefull-name/name 62 namefull-name/name 64 parent class="metadata-tree" reference="../../.."/ 65 generatedtrue/generated 66 exposedToEnvironmentfalse/exposedToEnvironment - 67 valuejakub/value + 67 valueSYSTEM/value 68/metadata-string 69 /children 70/metadata-tree This causes the "SCM Sync configuration plugin" repository to grow very quickly, and it also makes difficult to work out when a configuration has been changed by a user and not SYSTEM. Is it a bug ? Is it an expected behaviour ? If so how can I disable it ? Is it the PostBuildScriptListener class that's responsible for this ? publishers.remove(curPublisher.getClass()); publishers.add(curPublisher); We're currently using PostBuildScript version 0.10. Project: Jenkins Labels: postbuildscript Priority: Major Reporter: Jakub Czaplicki This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20235) No GUI option to change default view
SCM/JIRA link daemon commented on JENKINS-20235 No GUI option to change default view Code changed in jenkins User: Daniel Beck Path: src/main/java/com/cloudbees/hudson/plugins/folder/Folder.java src/main/resources/com/cloudbees/hudson/plugins/folder/Folder/configure.jelly http://jenkins-ci.org/commit/cloudbees-folder-plugin/08d327b3648641942ae89e23ba7f4db562f864a0 Log: FIXED JENKINS-20235 JENKINS-20006 Configurable default view Conflicts: src/main/java/com/cloudbees/hudson/plugins/folder/Folder.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] [cloudbees-folder] (JENKINS-20235) No GUI option to change default view
SCM/JIRA link daemon commented on JENKINS-20235 No GUI option to change default view Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/com/cloudbees/hudson/plugins/folder/Folder.java src/main/resources/com/cloudbees/hudson/plugins/folder/Folder/configure.jelly http://jenkins-ci.org/commit/cloudbees-folder-plugin/9cbac2d026e315f41b7b4b2e51ca6d73b5a0092f Log: Merge pull request #7 from daniel-beck/stable FIXED JENKINS-20523 JENKINS-20235 JENKINS-20006 for current LTS Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/4e62463c4411...9cbac2d026e3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20006) Use an actual AllView
SCM/JIRA link daemon commented on JENKINS-20006 Use an actual AllView Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/com/cloudbees/hudson/plugins/folder/Folder.java src/main/resources/com/cloudbees/hudson/plugins/folder/Folder/configure.jelly http://jenkins-ci.org/commit/cloudbees-folder-plugin/9cbac2d026e315f41b7b4b2e51ca6d73b5a0092f Log: Merge pull request #7 from daniel-beck/stable FIXED JENKINS-20523 JENKINS-20235 JENKINS-20006 for current LTS Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/4e62463c4411...9cbac2d026e3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-remote-trigger] (JENKINS-22231) Allow parameterized remote trigger to be a post-build action
Caleb Mayeux created JENKINS-22231 Allow parameterized remote trigger to be a post-build action Issue Type: Improvement Assignee: Maurice W. Components: parameterized-remote-trigger Created: 17/Mar/14 5:14 PM Description: Currently parameterized remote trigger plugin can run a remote job as a build step. It would be pretty nice if it could be a post-build action as well as a build step, like the vanilla parameterized trigger plugin. This can of course be worked around, but it'd still be nice. Awesome plugin, by the way! Environment: RHEL 5.5, Jenkins 1.551, parameterized-remote-trigger plugin 2.1 Project: Jenkins Priority: Major Reporter: Caleb Mayeux This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20006) Use an actual AllView
SCM/JIRA link daemon commented on JENKINS-20006 Use an actual AllView Code changed in jenkins User: Daniel Beck Path: src/main/java/com/cloudbees/hudson/plugins/folder/Folder.java src/main/resources/com/cloudbees/hudson/plugins/folder/Folder/configure.jelly http://jenkins-ci.org/commit/cloudbees-folder-plugin/08d327b3648641942ae89e23ba7f4db562f864a0 Log: FIXED JENKINS-20235 JENKINS-20006 Configurable default view Conflicts: src/main/java/com/cloudbees/hudson/plugins/folder/Folder.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] [cloudbees-folder] (JENKINS-20523) Implement ModelObjectWithChildren
SCM/JIRA link daemon commented on JENKINS-20523 Implement ModelObjectWithChildren Code changed in jenkins User: Daniel Beck Path: src/main/java/com/cloudbees/hudson/plugins/folder/Folder.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/4398ffb28dd8ed3954a4bb4884cdbfcb948f3f62 Log: FIXED JENKINS-20523 Provide views list in breadcrumb bar Conflicts: src/main/java/com/cloudbees/hudson/plugins/folder/Folder.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] [cloudbees-folder] (JENKINS-20523) Implement ModelObjectWithChildren
SCM/JIRA link daemon commented on JENKINS-20523 Implement ModelObjectWithChildren Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/com/cloudbees/hudson/plugins/folder/Folder.java src/main/resources/com/cloudbees/hudson/plugins/folder/Folder/configure.jelly http://jenkins-ci.org/commit/cloudbees-folder-plugin/9cbac2d026e315f41b7b4b2e51ca6d73b5a0092f Log: Merge pull request #7 from daniel-beck/stable FIXED JENKINS-20523 JENKINS-20235 JENKINS-20006 for current LTS Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/4e62463c4411...9cbac2d026e3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fstrigger] (JENKINS-22232) FS Trigger not triggers in copied jobs that have FS Trigger originally
Vasile Baluta created JENKINS-22232 FS Trigger not triggers in copied jobs that have FS Trigger originally Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: fstrigger Created: 17/Mar/14 5:18 PM Description: FS Trigger not triggers in copied jobs that have FS Trigger originally. I run version 0.38. Project: Jenkins Priority: Major Reporter: Vasile Baluta This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter] (JENKINS-22233) Since update to Jenkins 1.555 and Prioritysorter 2.6 the option Job priority disapeared in job-config
Christoph Moser created JENKINS-22233 Since update to Jenkins 1.555 and Prioritysorter 2.6 the option Job priority disapeared in job-config Issue Type: Bug Assignee: bklarson Components: prioritysorter Created: 17/Mar/14 5:21 PM Environment: Jenkins 1.555, Prioritysorter 2.6, master is running on ubuntu, JDK7 is installed Project: Jenkins Priority: Blocker Reporter: Christoph Moser This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22234) Build pipeline doesn't handle permissions very well
jpschewe created JENKINS-22234 Build pipeline doesnt handle permissions very well Issue Type: Bug Assignee: Unassigned Components: build-pipeline Created: 17/Mar/14 5:29 PM Description: I have a build pipeline that shows jobs that are all restricted. The anynomous user cannot see any of them. When I visit my Jenkins page and I'm not logged in I get an exception instead of a blank page. This means that users that aren't logged in always see an error until they login and jobs that are visible to anynomous users can't be viewed because all they see is this exception in the main part of the page. A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/nfs/homes/hudson/.hudson/war/WEB-INF/lib/jenkins-core-1.532.2.jar!/hudson/model/View/index.jelly:42:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/nfs/homes/hudson/.hudson/war/WEB-INF/lib/jenkins-core-1.532.2.jar!/lib/hudson/projectView.jelly:66:22: d:invokeBody Please login to access job people_tracker-feature-branches at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:135) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at
[JIRA] [email-ext] (JENKINS-18157) Email Template Testing can't find passed Jelly script file
Angel Williams commented on JENKINS-18157 Email Template Testing cant find passed Jelly script file Has this been fixed I am havving issues but need Windows nodes to connect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22235) Starting jenkins with https
TJ Bryant created JENKINS-22235 Starting jenkins with https Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 17/Mar/14 5:46 PM Description: I installed jenkins on redhat per these instructions. https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Red+Hat+distributions Using this page as a guideline: https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins?showComments=trueshowCommentArea=true#addcomment I am trying to start jenkins with this command to use https: sudo service jenkins start --httpPort=-1 --htpsPort=443 I get a usage error: Usage: service option | --status-all | [ service_name [ command | --full-restart ] ] Is the documentation out of date? Am I doing something incorrect to use port 443? Project: Jenkins Priority: Major Reporter: TJ Bryant This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-18157) Email Template Testing can't find passed Jelly script file
Alex Earl commented on JENKINS-18157 Email Template Testing cant find passed Jelly script file Yes, it was fixed. I'm not sure what it has to do with nodes at all... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-18157) Email Template Testing can't find passed Jelly script file
Angel Williams commented on JENKINS-18157 Email Template Testing cant find passed Jelly script file where is the directory $Jenkins_Home/email-templates.. its been soo long I can't find it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-22077) Allow automatic install of Maven 3.2.1
Bob Tiernay commented on JENKINS-22077 Allow automatic install of Maven 3.2.1 Just following up on this. If I can manually change the link, that would be great, thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-18157) Email Template Testing can't find passed Jelly script file
Alex Earl commented on JENKINS-18157 Email Template Testing cant find passed Jelly script file $JENKINS_HOME is on your Jenkins server. Usually its $HOME/.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] [junit] (JENKINS-22236) LinkageError when using Maven 3.2.1 with Jenkins 1.555
Julian Payne created JENKINS-22236 LinkageError when using Maven 3.2.1 with Jenkins 1.555 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: junit, maven2 Created: 17/Mar/14 6:01 PM Description: When using Maven 3.2.1 with Jenkins 1.555 the unit tests block with a LinkageError like this: Running asf.artifact.ArtifactHandlerManagerTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.149 sec - in asf.artifact.ArtifactHandlerManagerTest Exception in thread "Thread-11" java.lang.LinkageError: org.apache.maven.surefire.shade.org.apache.maven.shared.utils.io.IOUtil at java.lang.ClassLoader.defineClassImpl(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:364) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:154) at java.net.URLClassLoader.defineClass(URLClassLoader.java:777) at java.net.URLClassLoader.access$400(URLClassLoader.java:96) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1225) at java.security.AccessController.doPrivileged(AccessController.java:366) at java.net.URLClassLoader.findClass(URLClassLoader.java:660) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:389) at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227) at org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.StreamPumper.run(StreamPumper.java:95) Once this error occurs the Jenkins job blocks. I do not get these errors if I run the unit tests directly with Maven 3.2.1 I could not find anything of interest in the Manage Jenkins - Jenkins log Environment: Maven 3.2.1, Jenkins 1.555 Project: Jenkins Labels: jenkins Priority: Critical Reporter: Julian Payne This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-18157) Email Template Testing can't find passed Jelly script file
Angel Williams edited a comment on JENKINS-18157 Email Template Testing cant find passed Jelly script file where is the directory $Jenkins_Home/email-templates.. its been soo long I can't find it Well that is because between build 1.504 which was working for Jenkins and now 1.546 The Email-templates directory is gone. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim] (JENKINS-5359) Adopting push rather than pull model for claim
rggjan commented on JENKINS-5359 Adopting push rather than pull model for claim Ah, you're right! 7824 is what I was thinking of... thanks for the correction This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-19081) Download update center from master by default
SCM/JIRA link daemon resolved JENKINS-19081 as Fixed Download update center from master by default Change By: SCM/JIRA link daemon (17/Mar/14 6:27 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19081) Download update center from master by default
SCM/JIRA link daemon commented on JENKINS-19081 Download update center from master by default Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/485cc150eaa3d25dc64bc214a3f8a74194969069 Log: FIXED JENKINS-19081 Noting merge of #1144. Compare: https://github.com/jenkinsci/jenkins/compare/db4f60303aad...485cc150eaa3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-19081) Download update center from master by default
SCM/JIRA link daemon commented on JENKINS-19081 Download update center from master by default Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/model/DownloadService.java core/src/main/java/hudson/model/UpdateCenter.java core/src/main/java/hudson/model/UpdateSite.java core/src/main/java/hudson/util/FormValidation.java core/src/main/java/jenkins/security/DownloadSettings.java core/src/main/resources/hudson/PluginManager/advanced.jelly core/src/main/resources/hudson/model/UpdateCenter/PageDecoratorImpl/footer.jelly core/src/main/resources/jenkins/security/DownloadSettings/config.groovy core/src/main/resources/jenkins/security/DownloadSettings/help-checkSignature.html core/src/main/resources/jenkins/security/DownloadSettings/help-useBrowser.html core/src/main/resources/jenkins/security/Messages.properties test/src/test/java/hudson/model/DownloadServiceTest.java http://jenkins-ci.org/commit/jenkins/1ac77750e93f9a1970fecbecdf7f84279d0a62b9 Log: FIXED JENKINS-19081 Offer the option of downloading metadata directly from the server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22237) Gradle available versions should be in descending order.
Allister MacLeod created JENKINS-22237 Gradle available versions should be in descending order. Issue Type: Improvement Assignee: Gregory Boissinot Components: gradle Created: 17/Mar/14 6:31 PM Description: On the "Configure Jenkins" page, when adding a new Gradle installation, the list selector with available versions starts with the oldest Gradle version and has the newest (1.11 at time of writing) at the bottom. The initial default is the topmost, and therefore oldest, item. I think this order should be reversed, since when I am adding a Gradle installer, I am more likely to want a recent version. Newest-first would also be more consistent with other build tool plugins, such as Maven and Ant. Project: Jenkins Labels: gradle Priority: Trivial Reporter: Allister MacLeod This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
