[JIRA] [git] (JENKINS-23675) The git plugin is not working correctly when the repository url has job parameter and any repository credentials
SCM/JIRA link daemon resolved JENKINS-23675 as Fixed The git plugin is not working correctly when the repository url has job parameter and any repository credentials Change By: SCM/JIRA link daemon (11/Jul/14 7:29 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23675) The git plugin is not working correctly when the repository url has job parameter and any repository credentials
SCM/JIRA link daemon commented on JENKINS-23675 The git plugin is not working correctly when the repository url has job parameter and any repository credentials Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/397646b8034e63f1d6f8c783e9fd3a9df16c57a4 Log: Merge pull request #239 from elvysborges/2.2.x [FIXED JENKINS-23675] Expand parameters on repository url Compare: https://github.com/jenkinsci/git-plugin/compare/b3c63a02b4af...397646b8034e This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23675) The git plugin is not working correctly when the repository url has job parameter and any repository credentials
SCM/JIRA link daemon commented on JENKINS-23675 The git plugin is not working correctly when the repository url has job parameter and any repository credentials Code changed in jenkins User: Elvys Borges Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/7fbd682693f143b628e16e5776d5e8e4b7590b6f Log: [FIXED JENKINS-23675] Expand parameters on repository url before associate one url to one credential This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23665) Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password
Torsten Schlabach resolved JENKINS-23665 as Fixed Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password As mentioned before, please look at https://github.com/jenkinsci/winstone/pull/16 for the implementation. Change By: Torsten Schlabach (11/Jul/14 7:31 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Martin Schröder commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Hi Alex, hi everyone else. We've seen the issue on this tracker and have added it to our internal bug tracking system, as soon as it appeared. Unfortunately, a big product roll-out is binding up all of our resources since the start of the year. That means, that we can't fully focus on external bug reports, as long as we can't replicate them in our setup. We had used the "Role-Based Permission Plugin" earlier, but switched to a different in-house permission plugin, making replication problematic. Even when we used the other plugin, we did not see an issue like this. As far as security permissions go, the Inheritance Plugin behaves exactly like any other Project, since it leaves permission handling to the "Project" superclass. The obvious caveat to this is of course, that permissions do not "trickle-down" to inherited projects. Job permissions must match a job (or its name) exactly, no inheritance is applied on them. The weirdest thing about the issue described in the bug report is, that the screenshot shows the "Build" options in the side-panel. Those check exactly the same permissions that are needed for actually scheduling the build. We'll try to replicate this issue and see if we can indeed find a problem. Best regards, Martin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-21739) links to robot framework report files are invalid when inside a folder
Ninian commented on JENKINS-21739 links to robot framework report files are invalid when inside a folder Any chance of getting a release produced with this fix in it? It would be a big help for us, and it looks a fairly low risk change for other users. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up on IBM Java
Martin Kutter commented on JENKINS-22525 A Slave disappears every time Jenkins boots up on IBM Java I opened a support request at IBM. I'll update the issue when appropriate. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extra-columns] (JENKINS-23756) Column suggestion for Extra Column plugin
Rupen Anjaria created JENKINS-23756 Column suggestion for Extra Column plugin Issue Type: Improvement Assignee: Fred G Components: extra-columns Created: 11/Jul/14 9:00 AM Description: I would like to request to modify Extra column plugin to have a configuration to show column which shows SVN path (repository URL available in build). This will help to know which repository path the Jenkin job is pointing to. Project: Jenkins Priority: Major Reporter: Rupen Anjaria This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-23314) LR Scenario does not return SLA information in results
greg sanchez commented on JENKINS-23314 LR Scenario does not return SLA information in results I encountered the same issue, is there any workaround? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-6203) Git plugin uses default encoding to read change log file
Jörgen Lundberg commented on JENKINS-6203 Git plugin uses default encoding to read change log file We also have this problem. We're running Jenkins as a Windows server and I added -Dfile.encoding=UTF-8 to the start-up parameters and restarted the service. The log messages till shows the UTF-8 characters instead of for example å ä ö. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Oleg Nenashev edited a comment on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration JENKINS-21021 is a similar issue. I suppose that there is nothing to do inside ownership and role-strategy plugins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22654) Multi-configuration projects display with wrong Delivery Pipeline Stage Name
Patrik Boström commented on JENKINS-22654 Multi-configuration projects display with wrong Delivery Pipeline Stage Name Thanks for the clarification! When I tried to reproduce I configured job TestStart to trigger downstream project TestMulti instead of the two axis. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23694) git clean does not work (failed to fetch)
Daniel Neus commented on JENKINS-23694 git clean does not work (failed to fetch) ok, i tried this again with following output: ... > git reset --hard > git clean -fdx FATAL: Failed to fetch from https://github.com/boostorg/boost.git hudson.plugins.git.GitException: Failed to fetch from https://github.com/boostorg/boost.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:622) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:854) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:879) at hudson.model.AbstractProject.checkout(AbstractProject.java:1252) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:624) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:530) at hudson.model.Run.execute(Run.java:1732) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Caused by: hudson.plugins.git.GitException: Command "git clean -fdx" returned status code 1: stdout: stderr: warning: failed to remove boost/accumulators ... the first "git clean -fdx" is failing and therefore i'm not seeing the next step "git submodule foreach --recursive git reset --hard". maybe there is a problem with this on windows nodes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23726) Extended choice parameters not captured with python jenkinsapi invocation
Michael Davis updated JENKINS-23726 Extended choice parameters not captured with python jenkinsapi invocation Change By: Michael Davis (11/Jul/14 10:07 AM) Description: When invoking a job with extended choice parameters via jenkinsapi in Python, the extended choice parameters are not captured by Jenkins but the normal parameters are. - I will attach a traffic capture when I get to a computer. - I'm afraid I can't do this due to security reasons. If more information is required I'll be happy to provide it. Jenkins: 1.545Extended Choice Parameter: 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] [delivery-pipeline] (JENKINS-22654) Multi-configuration projects display with wrong Delivery Pipeline Stage Name
Justin Mason commented on JENKINS-22654 Multi-configuration projects display with wrong Delivery Pipeline Stage Name Yes – that seems to work ok, but does not allow differentiation between the axes. Our use case is to fan out from a build step to a set of deploy steps; deploy service X, service Y, service Z. Right now we just have a set of manually-duplicated, hand-edited jobs, but it'd be much cleaner if a multi-config build could be used, defining X, Y, Z as the values of the service_name axis. Being a continuous delivery pipeline, those deploy steps have a manual approval, so (for example) for a given build we could decide to push the button for "deploy X" and "deploy Z" only, hence building the top-level job (and allowing all sub-jobs to build as a result) wouldn't work for us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23757) Provide a switch (defaulting to on) that prevents installation of plugins requiring a newer Jenkins
stephenconnolly created JENKINS-23757 Provide a switch (defaulting to on) that prevents installation of plugins requiring a newer Jenkins Issue Type: New Feature Assignee: Unassigned Components: core Created: 11/Jul/14 10:17 AM Description: The update center is (perhaps badly) designed to alert users of newer versions of plugins that they have installed but which require a newer version of Jenkins as an incentive to upgrade Jenkins While there are some plugins that may indeed run correctly on older versions of Jenkins than they were built on (so people may legitimately need an out to install a version that claims to require a newer version of Jenkins) in 99.9% of cases users do not want to install a plugin where: the plugin (claims it) needs a newer version of Jenkins the plugin depends on another plugin the dependent plugin is not optional and not installed in the user's Jenkins and the version(s) available from the update center(s) all require a newer version of Jenkins the dependent plugin is installed (optional or non-optional dependency), but it is an older version than specified and the version(s) available from the update center(s) all require a newer version of Jenkins So this RFE would disable the checkbox for those plugins that are providing a compatibility warning. The feature could then be disabled by clicking a checkbox either on the Advanced tab or in the global configuration. Project: Jenkins Priority: Minor Reporter: stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23758) Enhance the update center metadata format to allow listing multiple versions of plugins and core
stephenconnolly
created JENKINS-23758
Enhance the update center metadata format to allow listing multiple versions of plugins and core
Issue Type:
New Feature
Assignee:
Unassigned
Components:
core
Created:
11/Jul/14 10:36 AM
Description:
Currently the update center metadata only permits listing one version of Jenkins core and one version of every plugin. It would be nice if we could advertise not just the latest version of Jenkins / each plugin but also some other versions within the metadata. For example currently the update center will list something like
{
"core":{
"buildDate":"...",
"name":"core",
"sha1":"...",
"url":"...",
"version":"..."
},
"plugins":{
"async-http-client":{
"buildDate":"...",
"dependencies":[...],
"developers":[...],
"excerpt":"...",
"labels":["library"],
"name":"async-http-client",
"requiredCore":"1.424",
"sha1":"...",
"title":"...",
"url":"...",
"version":"1.7.8",
"wiki":"..."
},
...
},
...
}
In order to retain backwards compatibility, it would likely be necessary to introduce the extension as child elements... but care needs to be taken in order to preserve the signature verification semantics... the general idea would be to extend to something like:
{
"core":{
"buildDate":"...",
"name":"core",
"sha1":"...",
"url":"...",
"version":"1.571",
"history":{
"1.570":{
"sha1":"...",
"url":"..."
},
"1.569":{
"sha1":"...",
"url":"..."
},
...
}
},
"plugins":{
"async-http-client":{
"buildDate":"...",
"dependencies":[...],
"developers":[...],
"excerpt":"...",
"labels":["library"],
"name":"async-http-client",
"requiredCore":"1.424",
"sha1":"...",
"title":"...",
"url":"...",
"version":"1.7.8",
"wiki":"...",
"history":{
"1.7.7":{
"dependencies":[...],
"requiredCore":"...",
"sha1":"...",
"url":"..."
},
"1.7.7":{
"dependencies":[...],
"requiredCore":"...",
"sha1":"...",
"url":"..."
},
...
}
},
...
},
...
}
Where each history entry would be keyed by the version and contain a map of values that are a delta from the main entry (so that if requiredCore is the same as the main entry we don't list it... obviously sha1 and url are always going to be different and some values such as developers, title, etc probably don't need to be provided in the history as it is reasonably safe to assume that the current version is what matters... but that is a decision for the system generating the metadata... the principle should be that the format lists the delta.
The format change would enable a lot more flexibility in plugin installation strategies available within Jenkins... the risk is that the metadata format change may make it impossible for older versions of Jenkins to upgrade so great care is required when making the format change... perhaps the simplest way is to make Jenkins core support reading the new format first and then change to the new format once the number of Jenkins instances accessing the OSS update centers that report an older version of Jenkins falls below a specific threshold (i.e. 5%)
Project:
Jenkins
Priority:
Major
Reporter:
stephenconnolly
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
[JIRA] [testng] (JENKINS-19217) Change class names to not contain package names on result pages (increases readability)
Paul Danyliuk commented on JENKINS-19217 Change class names to not contain package names on result pages (increases readability) Ugh... You should have made this configurable. Since, you know, http://xkcd.com/1172/ (I used to sort the table with results to spot similar issues in tests from adjacent packages) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis edited a comment on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Hi Martin, Thanks for your reply. To reproduce the reported issue, all you need is: 1. Install the Role Strategy Plugin 2. Install the Inheritance Plugin 3. Create Abstract inheritance project, lets call it projA, with parameter paramA, over-writable. 4. Create Inheritance project, lets call it project_final, that extends projA and overwrite inheritance parameter reference paramA. 5. Make sure user TEST_USER has no build privileges in Manage Roles, then create a Project Role with pattern project_.* and enable the job build permissions. 6. assign that role to TEST_USER via the assign roles page. 7. sign in as TEST_USER and you will see the build with parameters button in p which when you click you get user TEST_USER has no job/build permissions. Even when I set the pattern in step 5 to .* ie everything, I still get the same error, as initially I thought that someone building project_final would require build rights for projA (sounded more like a bug rather than anything else but still) I will try and have a look in the code to see what is happening. Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Hi Martin, Thanks for your reply. To reproduce the reported issue, all you need is: 1. Install the Role Strategy Plugin 2. Install the Inheritance Plugin 3. Create Abstract inheritance project, lets call it projA, with patameter paramA, overwritable. 4. Create Inheritance project, lets call it project_final, that extends projA and overwrite inheritance parameter reference paramA. 5. Make sure user TEST_USER hasno build privileges in Manage Roles, then create a Project Role with pattern project_.* and enable the job build permissions. 6. assign that role to TEST_USER via the assign roles page. 7. sign in as TEST_USER and you will see the build with parameters button in p which when you click you get user TEST_USER has no job/build permissions. Even when I set the pattern in step 5 to .* ie everything, I still get the same error, as initially I thought that someone building project_final would require build rights for projA (sounded more like a bug rather than anything else but still) I will try and have a look in the code to see what is happening. Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng] (JENKINS-19217) Change class names to not contain package names on result pages (increases readability)
Paul Danyliuk edited a comment on JENKINS-19217 Change class names to not contain package names on result pages (increases readability) Ugh... You should have made this configurable. Since, you know, http://xkcd.com/1172/ (I used to sort the table with results to spot similar issues in tests from adjacent packages — like, we have a package with REST API test classes, Selenium test classes etc, and now it's all mixed up) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration I also forgot to mention that I am using afitz/jenkins-inheritance-plugin which contains bugfixes I really need related to scm polling etc. The issue reported is also present in the master i-m-c/jenkins-inheritance-plugin so no difference here, I just thought to mention 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] [testng] (JENKINS-19217) Change class names to not contain package names on result pages (increases readability)
Paul Danyliuk edited a comment on JENKINS-19217 Change class names to not contain package names on result pages (increases readability) Ugh... You should have made this configurable. Since, you know, http://xkcd.com/1172/ I used to sort the table with results to spot similar issues in tests from adjacent packages — like, we have a package with REST API test classes, Selenium test classes etc. Now it's like sorting the dates where day comes before month. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-6203) Git plugin uses default encoding to read change log file
Jörgen Lundberg commented on JENKINS-6203 Git plugin uses default encoding to read change log file It was my bad. I didn't realize the log was written to disk. So, the utf-8 setting works for all builds done after the server restart. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-17431) 500 Internal Server Error on attempt to run a build
Aurelien TISNE commented on JENKINS-17431 500 Internal Server Error on attempt to run a build Hello, We have a repository full of revisions without date. I suspect it is due to the use of svndumpfilter. Builds are blocked. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Martin Schröder commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration It's very curious, because the reproduction steps outlined by you closely mirror what we did, when we still used the "Role Strategy Plugin". But since the issue seems really easy to replicate (thanks for the detailed guide, by the way!), we should be able to track down this issue. As for using the afitz/jenkins-inheritance-plugin branch, that's okay. Our own code-base is using a related patch to the one in his branch, so it shouldn't be a problem. When we get a bit more breathing room after the roll-out is done, we'll publish all those changes that have occurred in out internal codebase. At the moment, we simply lack the time to properly test the openly published releases. After all, testing for an internal project is always easier than testing for the rest of the world. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Oleg Nenashev commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration @Martin See the stacktrace above. The issue is caused by getProjectByName(), which invokes the permission check on the job. If any SecurityStrategy tries to access job properties, there will be an infinite cycle This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23680) New instance types not handled
Craig Bass stopped work on JENKINS-23680 New instance types not handled Change By: Craig Bass (11/Jul/14 1:32 PM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23680) New instance types not handled
Craig Bass commented on JENKINS-23680 New instance types not handled @divide a PR is available that resolved 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] [ec2] (JENKINS-23680) New instance types not handled
Craig Bass started work on JENKINS-23680 New instance types not handled Change By: Craig Bass (11/Jul/14 1:33 PM) Status: Open In 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Hi Martin, I am seeing the exact same issue when using the Jenkins core "Project-based Matrix Authorization Strategy". So we can clearly rule out this being an issue of the Role-Based Strategy Plugin. Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Hi Oleg, So what do you propose in doing ? All the code does is call the Jenkins.getItem method which in turn check for read permissions. That looks sensible to me. What do you think ? Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-18951) Problems with too long paths
Mark Waite closed JENKINS-18951 as Won't Fix Problems with too long paths Change By: Mark Waite (11/Jul/14 1:52 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-23314) LR Scenario does not return SLA information in results
Terri Calderone commented on JENKINS-23314 LR Scenario does not return SLA information in results if you use the percentile response time SLA, it will print out the goal and actual values. However, I am disappointed the transaction name is not included in any output. That is key to looking at what failed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23758) Enhance the update center metadata format to allow listing multiple versions of plugins and core
Jesse Glick commented on JENKINS-23758 Enhance the update center metadata format to allow listing multiple versions of plugins and core I think compatibility can be addressed by just exposing the new format on a new URL. The current *.json is anyway confusing since it is actually JSONP, not JSON. We could produce a new URL convention with an expanded format, in actual JSON (which core can now consume since it has the option to download from the master rather than through the browser). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23757) Provide a switch (defaulting to on) that prevents installation of plugins requiring a newer Jenkins
Jesse Glick resolved JENKINS-23757 as Duplicate Provide a switch (defaulting to on) that prevents installation of plugins requiring a newer Jenkins Change By: Jesse Glick (11/Jul/14 2:17 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Martin Schröder commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration @Oleg We previously already had a bug, that caused a deadlock on getProperties(), that was also caused by a zealous property check on a seemingly innocuous function call. That was solved by adding a suitable locking mechanism. As such, it is possible that we not only run into a deadlock or infinite loop, but also into a simple permission check issue. After all, to determine if a Job can be built, it must look if the settings it inherits from its parent make sense; thus it needs to retrieve the properties of its parents. We'll try to trace this bug in a debugging session based on your stacktrace and Alex's replication guide. We'll keep you posted once we've fixed it. Of course, since the code is open source, you can also try to dig into it. We are certainly no strangers to "external" patch submissions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Martin Schröder edited a comment on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration @Oleg We previously already had a bug, that caused a deadlock on getProperties(), that was also caused by a zealous property check on a seemingly innocuous function call. That was solved by adding a suitable locking mechanism. As such, it is possible that the code might not just risk a deadlock or infinite loop, but also might run into the simple permission check issue from this ticket. After all, to determine if a Job can be built, it must look if the settings it inherits from its parent make sense; thus it needs to retrieve the properties of its parents. We'll try to trace this bug in a debugging session based on your stacktrace and Alex's replication guide. We'll keep you posted once we've fixed it. Of course, since the code is open source, you can also try to dig into it. We are certainly no strangers to "external" patch submissions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-environment] (JENKINS-23759) Installation from repository on RedHat Fails
Mike Tarkowski created JENKINS-23759 Installation from repository on RedHat Fails Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-environment Created: 11/Jul/14 2:31 PM Description: After installing jenkins without receiving any error messages, then starting jenkins from the command line, no log file is created and jenkins is not listening on the assigned port. There is no error in any server log. Steps to repeat wget -O /etc/yum.repos.d/jenkins.repo http://pkg.jenkins-ci.org/redhat/jenkins.repo rpm --import http://pkg.jenkins-ci.org/redhat/jenkins-ci.org.key yum install jenkins Changed the 2 below ports after confirming they were free. vi /etc/sysconfig/jenkins JENKINS_AJP_PORT="8007" JENKINS_AJP_PORT="-1" service jenkins start - server responded with, "OK" service jenkins status - server responded with, "jenkins dead but pid file exists" During installation /var/log/jenkins directory was created with owner and group of jenkins. No log file created. Created from yum install /var/log/jenkins /var/run/jenkins.pid /var/lib/jenkins /usr/lib/jenkins /usr/lib/jenkins/jenkins.war /usr/sbin/rcjenkins /var/cache/jenkins /etc/logrotate.d/jenkins /etc/rc.d/init.d/jenkins /etc/sysconfig/jenkins vi /etc/passwd - shows the below line jenkins:x:496:494:Jenkins Continuous Build server:/var/lib/jenkins:/bin/false java -version java version "1.6.0_30" Also tried using java version 1.7 but experienced the same results. Environment: Red Hat Enterprise Linux Server release 6.5 (Santiago) Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:1 Core(s) per socket:1 Socket(s): 2 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family:6 Model: 26 Stepping: 5 CPU MHz: 2933.436 BogoMIPS: 5866.87 Hypervisor vendor: VMware Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 8192K NUMA node0 CPU(s): 0,1 Project: Jenkins Priority: Major Reporter: Mike Tarkowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22395) Run.delete (from LogRotator) failing with "...looks to have already been deleted"
Jesse Glick updated JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted" Change By: Jesse Glick (11/Jul/14 2:49 PM) Labels: exception lazy-loading log-rotator lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23621) Jenkins using out of date SVN library format 29
Cody Fyler commented on JENKINS-23621 Jenkins using out of date SVN library format 29 Same issue with latest TortoiseSVN... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-12875) "No valid crumb was included in the request" errors all around
Dave Augustus commented on JENKINS-12875 "No valid crumb was included in the request" errors all around I can confirm that this also occurs on Centos 6.5 with Nginx 1.6 using Firefox. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23660) Attached log in Jenkins email incomplete
SCM/JIRA link daemon commented on JENKINS-23660 Attached log in Jenkins email incomplete Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/AttachmentUtils.java http://jenkins-ci.org/commit/email-ext-plugin/bdece53fad4d1fd5d1c65b74e28e7150a5139b67 Log: Fix JENKINS-23660 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23660) Attached log in Jenkins email incomplete
Alex Earl resolved JENKINS-23660 as Fixed Attached log in Jenkins email incomplete Reworked how the log data source retrieves the log content from core to loop until the whole log is retrieved. Change By: Alex Earl (11/Jul/14 3:21 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] [p4] (JENKINS-23760) Workspace Name Format cannot contain spaces
Charles McLouth
created JENKINS-23760
Workspace Name Format cannot contain spaces
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
p4
Created:
11/Jul/14 3:21 PM
Description:
With a Jenkins Project Name that includes spaces ex: Test Build Job
And the default Workspace Name Format: jenkins-${node}-${project}
Produces a java null pointer exception when running the build:
Started by user anonymous
Building in workspace /var/lib/jenkins/workspace/Test Build Job
Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.
Error detected at line 1.
Wrong number of words for field 'Client'.
Unable to run sync workspace: java.lang.NullPointerException
Finished: FAILURE
Project:
Jenkins
Priority:
Major
Reporter:
Charles McLouth
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-23691) Support regex/replace attribute in ${CHANGES} token to modify changes message
Alex Earl
resolved JENKINS-23691 as Fixed
Support regex/replace attribute in ${CHANGES} token to modify changes message
Fixed via pull request 93
Change By:
Alex Earl
(11/Jul/14 3:21 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] [email-ext] (JENKINS-23619) Email Template Testing should support managed files as well
Alex Earl resolved JENKINS-23619 as Fixed Email Template Testing should support managed files as well Fixed via pull request Change By: Alex Earl (11/Jul/14 3:22 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] [email-ext] (JENKINS-11693) When matrix job kills children for a failed job emails from email-ext are sometimes not sent
Alex Earl commented on JENKINS-11693 When matrix job kills children for a failed job emails from email-ext are sometimes not sent What version of email-ext is being used? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23458) NullPointerException if Before Build reciepients is empty
Alex Earl commented on JENKINS-23458 NullPointerException if Before Build reciepients is empty @Jan, did you restart Jenkins after upgrading email-ext? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ios-device-connector] (JENKINS-22883) Building the xcode project on real iOS devices.
Stephane Prohaszka commented on JENKINS-22883 Building the xcode project on real iOS devices. What do you mean ? You can choose the target sdk which can be for iOS, OSX or iOS simulator. Do you talk about installing and running the application on an iPhone as a result of a successful build ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23757) Provide a switch (defaulting to on) that prevents installation of plugins requiring a newer Jenkins
stephenconnolly reopened JENKINS-23757 Provide a switch (defaulting to on) that prevents installation of plugins requiring a newer Jenkins Well I disagree that it is a duplicate... we can disagree as to whether the switch is necessary... but the switch feature makes this not a duplicate but actually a related issue Change By: stephenconnolly (11/Jul/14 3:34 PM) Resolution: Duplicate Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22395) Run.delete (from LogRotator) failing with "...looks to have already been deleted"
SCM/JIRA link daemon commented on JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted" Code changed in jenkins User: Jesse Glick Path: test/src/test/java/jenkins/model/lazy/LazyBuildMixInTest.java http://jenkins-ci.org/commit/jenkins/b7ec8578f938864af9c8dbfb73a54d67f972d694 Log: JENKINS-22395 Taking advantage of BuildReference.clear (just introduced in b6226ad) to simplify test by not requiring a custom build reference holder just to simulate GC. Confirmed that dropLinksAfterGC and dropLinksAfterGC2 both fail in the expected way (b1a.nextBuild == b2) after commenting out the call to createReference().clear() in dropLinks. (Also that they fail as expected in assertNotSame if the reference is not cleared 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] [subversion] (JENKINS-23761) "No route to host" in scm access for multi-conf jobs
Henri Gomez created JENKINS-23761 "No route to host" in scm access for multi-conf jobs Issue Type: Bug Assignee: Unassigned Components: subversion Created: 11/Jul/14 4:17 PM Description: I get more and more random errors on multi-conf jobs where many slaves are triggered at same time to build native packages (freestyle). at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:706) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:14) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:9) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:777) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:99) ... 14 more Caused by: svn: E175002: OPTIONS /svn/ecd-catalog/trunk/cifortify-sca failed at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97) ... 34 more Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS request failed on '/svn/ecd-catalog/trunk/cifortify-sca' svn: E175002: No route to host at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:777) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 33 more Caused by: svn: E175002: OPTIONS request failed on '/svn/ecd-catalog/trunk/cifortify-sca' at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:775) ... 34 more Caused by: svn: E175002: No route to host at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:109) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:528) ... 34 more Caused by: java.net.NoRouteToHostException: No route to host at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:570) at org.tmatesoft.svn.core.internal.util.SVNSocketConnection.run(SVNSocketConnection.java:57) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) ... 5 more Finished: FAILURE Of course host is up and accessible from slaves. I did svn checkout directly from slaves using native svn 1.7 without problems. Subversion server is using CollabNet 4.0.10 and SSL (using valid certificate). I tried various SVN operations (forcing checkout, update) but no more luck. This is a serious show stopper especially by its randomly nature, ie on 10 slaves, only one will be in trouble. Environment: Jenkins LTS 1.544.3, Subversion Plugin 2.4, CollabNet 4.0.10 (SSL) Project: Jenkins Priority: Major
[JIRA] [subversion] (JENKINS-23761) "No route to host" in scm access for multi-conf jobs
Henri Gomez updated JENKINS-23761 "No route to host" in scm access for multi-conf jobs Change By: Henri Gomez (11/Jul/14 4:18 PM) Affects Version/s: current Environment: Jenkins LTS 1.544.3, Subversion Plugin 2.4, CollabNet 4.0.10 (SSL) . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-11693) When matrix job kills children for a failed job emails from email-ext are sometimes not sent
jpschewe commented on JENKINS-11693 When matrix job kills children for a failed job emails from email-ext are sometimes not sent When the issue was filed it was the current version of email-ext. I'm currently at 2.37.2 on Jenkins 1.532.2. I haven't seen this happen recently. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-11693) When matrix job kills children for a failed job emails from email-ext are sometimes not sent
Alex Earl resolved JENKINS-11693 as Cannot Reproduce When matrix job kills children for a failed job emails from email-ext are sometimes not sent Change By: Alex Earl (11/Jul/14 4:28 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-11693) When matrix job kills children for a failed job emails from email-ext are sometimes not sent
Alex Earl commented on JENKINS-11693 When matrix job kills children for a failed job emails from email-ext are sometimes not sent Ok, I'll close it out. Reopen if it comes back. I was never able to reproduce it. For future bugs, please put a specific release number. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22395) Run.delete (from LogRotator) failing with "...looks to have already been deleted"
dogfood commented on JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted" Integrated in jenkins_main_trunk #3509 JENKINS-22395 Taking advantage of BuildReference.clear (just introduced in b6226ad) to simplify test by not requiring a custom build reference holder just to simulate GC. (Revision b7ec8578f938864af9c8dbfb73a54d67f972d694) Result = SUCCESS Jesse Glick : b7ec8578f938864af9c8dbfb73a54d67f972d694 Files : test/src/test/java/jenkins/model/lazy/LazyBuildMixInTest.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] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Alex Earl commented on JENKINS-21861 option to include attachment with console.txt from failed slaves I can't reproduce this issue no matter what I have tried. The logs are correctly zipped up and attached. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-23762) Adding a mixin class to Job leaks memory from every DSL run
Jesse Glick
created JENKINS-23762
Adding a mixin class to Job leaks memory from every DSL run
Issue Type:
Bug
Assignee:
Justin Ryan
Components:
job-dsl-plugin
Created:
11/Jul/14 4:41 PM
Description:
A user reported an exhaustion of the permanent generation. jmap -histo:live showed that there were several hundred GroovyClassLoader instances in heap, and further analysis tracked down the problem to usage of the Job DSL plugin with Groovy mixins.
If you have a DSL
job {
name 'generated'
description("generated on ${new Date()}")
}
then each time you run it, a new GroovyClassLoader is added to the heap. These do not seem to get collected easily, since they are held via a SoftReference in Groovy somewhere, but this /script forces soft references to be cleared:
for (i = 1; ; i *= 2) {
System.gc();
new Object[i];
}
After running that, just one GroovyClassLoader remains, held from ASTTransformationVisitor.compUnit—an apparent memory leak in Groovy, but at least limited to holding the loader from one build at a time.
If I change the DSL to be
javaposse.jobdsl.dsl.Job.description2 = {String d ->
description(d);
}
job {
name 'generated'
description2 "generated on ${new Date()}"
}
(recommended monkey-patching) then I see the same behavior. But if I change the DSL to be
class JobMixin {
public Object description2(String d) {
return description(d.toUpperCase());
}
}
javaposse.jobdsl.dsl.Job.mixin(JobMixin);
job {
name 'generated'
description2 "generated on ${new Date()}"
}
then I get one GroovyClassLoader per run of the DSL, and they do not get collected even after forcing full GC. Besides the leak of one from ASTTransformationVisitor.compUnit, the rest are leaked in
this - value: groovy.lang.GroovyClassLoader #3
<- parent - class: groovy.util.GroovyScriptEngine$ScriptClassLoader, value: groovy.lang.GroovyClassLoader #3
<- delegate - class: groovy.lang.GroovyClassLoader$InnerLoader, value: groovy.util.GroovyScriptEngine$ScriptClassLoader #3
<- - class: JobMixin, value: groovy.lang.GroovyClassLoader$InnerLoader #3
<- cachedClass - class: org.codehaus.groovy.reflection.CachedClass, value: JobMixin class JobMixin
<- mixinClass - class: org.codehaus.groovy.reflection.MixinInMetaClass, value: org.codehaus.groovy.reflection.CachedClass #150
<- key - class: java.util.LinkedHashMap$Entry, value: org.codehaus.groovy.reflection.MixinInMetaClass #3
<- [5] - class: java.util.HashMap$Entry[], value: java.util.LinkedHashMap$Entry #7716
<- table - class: java.util.LinkedHashMap, value: java.util.HashMap$Entry[] #7123
<- map - class: java.util.LinkedHashSet, value: java.util.LinkedHashMap #1581
<- mixinClasses - class: groovy.lang.ExpandoMetaClass, value: java.util.LinkedHashSet #45
<- strongMetaClass - class: org.codehaus.groovy.reflection.ClassInfo, value: groovy.lang.ExpandoMetaClass #1
<- $staticClassInfo - class: javaposse.jobdsl.dsl.Job, value: org.codehaus.groovy.reflection.ClassInfo #320
<- [353] - class: java.lang.Object[], value: javaposse.jobdsl.dsl.Job class Job
<- elementData - class: java.util.Vector, value: java.lang.Object[] #8736
<- classes - class: hudson.PluginFirstClassLoader, value: java.util.Vector #192
(The analysis of root GC references was done using the NetBeans Profiler; VisualVM has the same tool.)
Suggested resolutions:
Document this bug and close without fixing.
Clear mixinClasses from every built-in DSL class after every DSL run. (Possibly a race condition, if you are running multiple DSLs at once.)
Prevent DSLs from adding mixins, just throwing some informative error. (Again this would prevent a possible race condition in the current system: there seems to be nothing preventing unrelated DSLs from clashing over definitions.)
Load DSL classes like Job in their own class loader for each DSL run, rather than loading them from the plugin class loader. That would ensure isolation betw
[JIRA] [core] (JENKINS-23763) Cannot use jsonp with buildWithParameters
françois auger
created JENKINS-23763
Cannot use jsonp with buildWithParameters
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
11/Jul/14 4:49 PM
Description:
Hi all,
I'm facing a problem (bug ?) using buildWithParameter and jsonp (with angular) :
I try to start my job with parameter and then get the response as jsonp :
First i call my url throught jsonp. In angular it looks like to :
$http.jsonp("http://jenkins-server.com/jenkins/view/myJob/job/myJob/buildWithParameters?token=myToken&jsonp=test&BUILD_JOB_NAME=foo")
I cannot set the header in jsonp and i see the "default" header is :
Accept:/
The build starts sucessfully but i get a 302 http response and response data are xml and not json as expected.
Any help is greatly appreciated.
Thx
Project:
Jenkins
Priority:
Major
Reporter:
françois auger
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [mansion-cloud] (JENKINS-23764) MansionComputer removed before build can run
recampbell created JENKINS-23764 MansionComputer removed before build can run Issue Type: Bug Assignee: Unassigned Components: mansion-cloud Created: 11/Jul/14 4:55 PM Description: In Jenkins versions > 1.532, MansionComputers are terminated immediately after coming online, before they can be assigned buildable items from the queue. This happens if the computer takes longer to connect than MansionRetentionStrategy#TIMEOUT The root cause is hudson.model.Executor#getIdleStartMilliseconds() uses Computer#getConnectTime() to determine idleness if no jobs have been run. However, Computer#connectTime is set when the computer starts connecting. The solution is to track onlineTime for a MansionComputer and to use that when calculating idleness. Project: Jenkins Priority: Major Reporter: recampbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mansion-cloud] (JENKINS-23764) MansionComputer removed before build can run
SCM/JIRA link daemon commented on JENKINS-23764 MansionComputer removed before build can run Code changed in jenkins User: Ryan Campbell Path: src/main/java/com/cloudbees/jenkins/plugins/mtslavescloud/MansionComputer.java src/main/java/com/cloudbees/jenkins/plugins/mtslavescloud/MansionRetentionStrategy.java http://jenkins-ci.org/commit/mansion-cloud-plugin/f9b8bd35d23f7079b5964f7c6eaccd9e9dc8486a Log: JENKINS-23764 Use MansionComputer#onlineTime for more accurate idleness check. Computer#connectTime is set when the computer starts connecting. If MansionRetentionStrategy is run immediately after MansionComputer completes connecting, the MansionComputer#getIdleStartMilliseconds() will reflect the time that it took to completely connect the MansionComputer instead of the time that it was actually idle. Compare: https://github.com/jenkinsci/mansion-cloud-plugin/compare/e886de6e1a6c...f9b8bd35d23f This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mansion-cloud] (JENKINS-23676) Nodes go offine shortly after build starts
SCM/JIRA link daemon commented on JENKINS-23676 Nodes go offine shortly after build starts Code changed in jenkins User: Ryan Campbell Path: src/main/java/com/cloudbees/jenkins/plugins/mtslavescloud/MansionRetentionStrategy.java http://jenkins-ci.org/commit/mansion-cloud-plugin/ac1b9409c818cfadd9275adb2d95ca1665ae77ba Log: JENKINS-23676 Add logging and potential workaround for MansionComputers going offline during builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18065) AbstractLazyLoadRunMap.iterator() calls .all()
Jesse Glick assigned JENKINS-18065 to Kohsuke Kawaguchi AbstractLazyLoadRunMap.iterator() calls .all() Change By: Jesse Glick (11/Jul/14 6:02 PM) Assignee: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18065) AbstractLazyLoadRunMap.iterator() calls .all()
Jesse Glick started work on JENKINS-18065 AbstractLazyLoadRunMap.iterator() calls .all() Change By: Jesse Glick (11/Jul/14 6:02 PM) Status: Open In 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] [build-flow] (JENKINS-22779) Build-Flow plugin problems in latest version (0.11.1)
Mike Chmielewski commented on JENKINS-22779 Build-Flow plugin problems in latest version (0.11.1) Like Ben, I am on 0.12, Jenkins v.1.567, and email sending and job description post build actions are busted. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-23754) As a user, I would like to consult a report of plugins and plugin versions used during a run of the Acceptance Test Harness
Scott Hebert started work on JENKINS-23754 As a user, I would like to consult a report of plugins and plugin versions used during a run of the Acceptance Test Harness Change By: Scott Hebert (11/Jul/14 6:08 PM) Status: Open In 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] [cppcheck] (JENKINS-17450) "warning" and "performance" not counted
Michal Turek
commented on JENKINS-17450
"warning" and "performance" not counted
Oh, I understand now. Legacy XML v1 format uses severities that are not compatible with new XML v2. There is the following mapping in the plugin code.
if ("possible error".equals(cppcheckFile.getSeverity())) {
warningSeverityList.add(cppcheckFile);
} else if ("style".equals(cppcheckFile.getSeverity())) {
styleSeverityList.add(cppcheckFile);
} else if ("possible style".equals(cppcheckFile.getSeverity())) {
performanceSeverityList.add(cppcheckFile);
} else if ("error".equals(cppcheckFile.getSeverity())) {
errorSeverityList.add(cppcheckFile);
} else {
noCategorySeverityList.add(cppcheckFile);
}
allErrors.add(cppcheckFile);
You should always use XML v2. Cppcheck for example reports less issues with XML v1 than with XML v2 for the same analyzed code.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand] (JENKINS-17687) Sauce-ondemand times out every time
hinling yeung commented on JENKINS-17687 Sauce-ondemand times out every time just updated to the latest version and now i got this log: Starting Sauce OnDemand SSH tunnel on master node Launching Sauce Connect on se2.sv2.trulia.com Time out while waiting for Sauce Connect to start, please check the Sauce Connect log FATAL: com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Time out while waiting for Sauce Connect to start, please check the Sauce Connect log com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectException: com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Time out while waiting for Sauce Connect to start, please check the Sauce Connect log at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:284) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectStarter.call(SauceOnDemandBuildWrapper.java:562) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:164) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:535) at hudson.model.Run.execute(Run.java:1732) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Caused by: com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Time out while waiting for Sauce Connect to start, please check the Sauce Connect log at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:272) ... 8 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] [google-storage] (JENKINS-23670) Please add option to remove prefix from local path when performing Classic Upload
Steven Shipton updated JENKINS-23670 Please add option to remove prefix from local path when performing Classic Upload Changed from request to bug report as this is breaking 3rd party services which use the path. I.e. they interpret the \ as folders and not part of the filename Change By: Steven Shipton (11/Jul/14 6:16 PM) Issue Type: Improvement Bug This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-17450) "warning" and "performance" not counted
Michal Turek resolved JENKINS-17450 as Won't Fix "warning" and "performance" not counted Rejected, the issue can't occur without manual modification of the input report. Change By: Michal Turek (11/Jul/14 6:16 PM) Status: Reopened Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-17450) "warning" and "performance" not counted
Michal Turek closed JENKINS-17450 as Won't Fix "warning" and "performance" not counted Change By: Michal Turek (11/Jul/14 6:17 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow] (JENKINS-22779) Build-Flow plugin problems in latest version (0.11.1)
Mike Chmielewski commented on JENKINS-22779 Build-Flow plugin problems in latest version (0.11.1) FYI, found it was fixed by checking the "Use workspace" checkbox in the build flow job configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-18065) AbstractLazyLoadRunMap.iterator() calls .all()
Kohsuke Kawaguchi
commented on JENKINS-18065
AbstractLazyLoadRunMap.iterator() calls .all()
The problematic part is this:
at jenkins.model.lazy.AbstractLazyLoadRunMap.all(AbstractLazyLoadRunMap.java:617)
at jenkins.model.lazy.AbstractLazyLoadRunMap.entrySet(AbstractLazyLoadRunMap.java:277)
at java.util.AbstractMap$2$1.(Unknown Source)
at java.util.AbstractMap$2.iterator(Unknown Source)
at hudson.util.RunList.iterator(RunList.java:97)
In looking at the code, what's going on is that RunList calls job.getBuilds():
public RunList(View view) {// this is a type unsafe operation
Set jobs = new HashSet();
for (TopLevelItem item : view.getItems())
jobs.addAll(item.getAllJobs());
List> runLists = new ArrayList>();
for (Job job : jobs) {
runLists.add(job.getBuilds());
}
this.base = combine(runLists);
}
and job.getBuilds() does this:
public RunList getBuilds() {
return RunList.fromRuns(_getRuns().values());
}
... which results in RunMap.values() which is implemented by AbstractMap, which calls ALLRM.entrySet(), that calls all().
ALLRM.entrySet() impl must be smarter, or job.getBuilds() need to avoid calling values().
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [mansion-cloud] (JENKINS-23676) Nodes go offine shortly after build starts
recampbell resolved JENKINS-23676 as Fixed Nodes go offine shortly after build starts Change By: recampbell (11/Jul/14 6:56 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] [mansion-cloud] (JENKINS-23764) MansionComputer removed before build can run
recampbell resolved JENKINS-23764 as Fixed MansionComputer removed before build can run Change By: recampbell (11/Jul/14 6:57 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] [websphere-deployer] (JENKINS-22393) Problem deploying EAR to WAS 7
Greg Peters resolved JENKINS-22393 as Fixed Problem deploying EAR to WAS 7 Currently fixed in test. Will publish this change. Change By: Greg Peters (11/Jul/14 7:02 PM) Status: In Progress Resolved Assignee: Greg Peters Fix Version/s: current 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] [websphere-deployer] (JENKINS-22393) Problem deploying EAR to WAS 7
Greg Peters started work on JENKINS-22393 Problem deploying EAR to WAS 7 Change By: Greg Peters (11/Jul/14 7:01 PM) Status: Open In 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] [core] (JENKINS-18065) AbstractLazyLoadRunMap.iterator() calls .all()
SCM/JIRA link daemon commented on JENKINS-18065 AbstractLazyLoadRunMap.iterator() calls .all() Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/util/RunList.java core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java core/src/main/java/jenkins/model/lazy/LazyLoadRunMapEntrySet.java core/src/test/java/jenkins/model/lazy/AbstractLazyLoadRunMapTest.java http://jenkins-ci.org/commit/jenkins/54c084613f83f9b7a02957eb98dbd8dc661d1c9c Log: [FIXED JENKINS-18065] made ALLRM.entrySet() smarter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-18065) AbstractLazyLoadRunMap.iterator() calls .all()
SCM/JIRA link daemon resolved JENKINS-18065 as Fixed AbstractLazyLoadRunMap.iterator() calls .all() Change By: SCM/JIRA link daemon (11/Jul/14 7:03 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-22393) Problem deploying EAR to WAS 7
Greg Peters commented on JENKINS-22393 Problem deploying EAR to WAS 7 Thank you Flo! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22395) Run.delete (from LogRotator) failing with "...looks to have already been deleted"
SCM/JIRA link daemon commented on JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted" Code changed in jenkins User: Kohsuke Kawaguchi Path: test/src/test/java/jenkins/model/lazy/LazyBuildMixInTest.java http://jenkins-ci.org/commit/jenkins/02e9f36dac05e533f7dc28325def85d4d937fb9e Log: JENKINS-22395 correcting the control test As I step-executed the code, I discovered b2.getPreviousBuild() was getting invoked between BRHF.drop(b1) and b2.dropLinks() call, in PeepholePermalink.RunListenerImpl.onDeleted() because Run.delete() calls RunListener.fireDeleted(this). Thus in effect the sequence of the call order was as follows: assertEquals(1, BRHF.drop(b1)); b2.getPreviousBuild(); // happens indirectly in PeepholePermalink b2.delete(); FreeStyleBuild b1a = b2.getPreviousBuild(); This defeats the purpose of the fix, because in this call sequence, by b2.dropLinks() as implemented before f1430a2 will correctly fix up b1a.nextBuildR to b3. For the test to work as intended, it is important that b2.previousBuildR.get()==null during dropLinks(). That is what causes b2.getPreviousBuild() in the next line to go load b1a, and sets up b1a.nextBuildR to b2, and trigger the assertion error. Added a code to remove all RunListeners. With this change, the test now fails without the fix in f1430a2. (cherry picked from commit 7b1b50c85a6a4bdb75f1ae5b40885afa45f96b82) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22395) Run.delete (from LogRotator) failing with "...looks to have already been deleted"
SCM/JIRA link daemon commented on JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted" Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/jenkins/model/lazy/LazyBuildMixIn.java http://jenkins-ci.org/commit/jenkins/921001d5245c4f441023e8ca16351e7ca84dabb2 Log: JENKINS-22395 more diagnostics Just in case the previous fix didn't address the root cause of ZD-11985 (and given the time it takes for changes like this to land in LTS), I'm adding additional diagnostics that let us track how previous/next builds are getting discovered (cherry picked from commit aa8e0b4f0e312ba4ef9c647ccf2c093793a9bece) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22395) Run.delete (from LogRotator) failing with "...looks to have already been deleted"
SCM/JIRA link daemon commented on JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted" Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/jenkins/model/lazy/BuildReference.java core/src/main/java/jenkins/model/lazy/LazyBuildMixIn.java http://jenkins-ci.org/commit/jenkins/ad65cecc7825693af7378d1d223966bac40ef37a Log: [FIXED JENKINS-22395] redoing the fix in f1430a2 Based on the last few commits, I proved that the original fix in f1430a2 doesn't really address the problem. That is, once b2 is deleted, and after sufficient garbage collection, we can make b2.previousBuild.get() be null, and then b2.getPreviousBuild().getNextBuild() ends up incorrectly returning b2. In this commit, I roll back that part of f1430a2, and then fix the problem differently. I started thinking that the main problem we are trying to fix here is that the deleted build object should be unreferenceable. That is, it should behave almost as if the object has already been GCed. The easiest way to do this is to clear a BuildReference object, since we always use the same BuildReference object for all inbound references. This change allows us to clear BuildReference. Code like b2.getPreviousBuild() will continue to try to update b1.nextBuildR to b2, but it will only end up wiping out the field, only to have b1.getNextBuild() recompute the correct value. This fix makes both test cases pass in LazyBuildMixInTest. (cherry picked from commit b6226ad2d1a332cb661ceb5c5f5b673771118e14) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22395) Run.delete (from LogRotator) failing with "...looks to have already been deleted"
SCM/JIRA link daemon commented on JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted" Code changed in jenkins User: Jesse Glick Path: cli/pom.xml core/pom.xml plugins/pom.xml pom.xml test/pom.xml war/pom.xml http://jenkins-ci.org/commit/jenkins/87df95af49f290cd16f6179d70bc05df411c91ac Log: Setting version: 1.565.1.JENKINS-22395-dropLinks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22395) Run.delete (from LogRotator) failing with "...looks to have already been deleted"
SCM/JIRA link daemon commented on JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted" Code changed in jenkins User: Jesse Glick Path: test/src/test/java/jenkins/model/lazy/LazyBuildMixInTest.java http://jenkins-ci.org/commit/jenkins/63e806efb6c6ba38c5043e1916ff4f19d425ea0e Log: JENKINS-22395 Taking advantage of BuildReference.clear (just introduced in b6226ad) to simplify test by not requiring a custom build reference holder just to simulate GC. Confirmed that dropLinksAfterGC and dropLinksAfterGC2 both fail in the expected way (b1a.nextBuild == b2) after commenting out the call to createReference().clear() in dropLinks. (Also that they fail as expected in assertNotSame if the reference is not cleared at all.) (cherry picked from commit b7ec8578f938864af9c8dbfb73a54d67f972d694) Compare: https://github.com/jenkinsci/jenkins/compare/87df95af49f2^...63e806efb6c6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22395) Run.delete (from LogRotator) failing with "...looks to have already been deleted"
SCM/JIRA link daemon commented on JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted" Code changed in jenkins User: Kohsuke Kawaguchi Path: test/src/test/java/jenkins/model/lazy/LazyBuildMixInTest.java http://jenkins-ci.org/commit/jenkins/4910863dbdb944f249fa86c4ca583e53c736ed69 Log: JENKINS-22395 I'm not sure if I understand how the original fix in PR #1190 (f1430a2) addresses the problem. My understanding is of the problem is as follows: someone deletes 'b2' but holds on to its reference (could be different threads) someone calls b2.getPreviousBuild() if b2.previousBuildR is null, then this triggers the loading of b1, and that process sets up a bi-di link via b1<>b2 via b1.nextBuildR <> b2.previousBuildR this makes b1.getNextBuild() incorrectly return b2 Presumably f1430a2 addresses this somehow, but I think I can induce this situation in other ways, which is what dropLinksAfterGC2() does. In this test, initial state: b1 <> b2 <> b3 we load everyone and connect them all up after deleting b2: b1 <> b3 ^^ b2 b1 and b3 points each other, and b2 still refers to each side after dropping b1: b2 --> b3 now, here, when I do b2.getPreviousBuild(), it loads b1a and it sets b1a.nextBuildR to b2. b1a <-> b2 --> b3 So I claim this is a proof that the fix is incomplete, even for the problem JENKINS-22395 has discovered. I don't think that the problem is for the dropLinks call to fail to patch up references. The problem is that b2.getPreviousBuild() forcing b1 to point to b2, because if b2 is deleted and assumed to be invalid, then no matter what bX this method will find you never want bX.nextBuildR to point to b2. (cherry picked from commit 53e95ee517259e1e10d7209bcbaa4314397c1f40) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clover] (JENKINS-23055) Allow Parameter interpolation for Clover path and file name
Pawel Faron commented on JENKINS-23055 Allow Parameter interpolation for Clover path and file name I highly agree it would be great to have at least Jenkins' environment variables (e.g. BUILD_NUMBER) interpolation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22154) Add option to temporary deactivate the plugin in the project settings
SCM/JIRA link daemon commented on JENKINS-22154 Add option to temporary deactivate the plugin in the project settings Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.groovy src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherTest.java http://jenkins-ci.org/commit/email-ext-plugin/aedbab2e9230fcfc5c9e242a5389df044204bac8 Log: Fix JENKINS-22154 - Add disable at project level This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22154) Add option to temporary deactivate the plugin in the project settings
Alex Earl resolved JENKINS-22154 as Fixed Add option to temporary deactivate the plugin in the project settings Added option to disable at the project level. Change By: Alex Earl (11/Jul/14 7:55 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18065) AbstractLazyLoadRunMap.iterator() calls .all()
dogfood commented on JENKINS-18065 AbstractLazyLoadRunMap.iterator() calls .all() Integrated in jenkins_main_trunk #3511 [FIXED JENKINS-18065] made ALLRM.entrySet() smarter (Revision 54c084613f83f9b7a02957eb98dbd8dc661d1c9c) Result = SUCCESS kohsuke : 54c084613f83f9b7a02957eb98dbd8dc661d1c9c Files : core/src/test/java/jenkins/model/lazy/AbstractLazyLoadRunMapTest.java core/src/main/java/hudson/util/RunList.java changelog.html core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java core/src/main/java/jenkins/model/lazy/LazyLoadRunMapEntrySet.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] [accelerated-build-now] (JENKINS-23765) Adding option to disable or hide Statements coverage.
Pawel Faron created JENKINS-23765 Adding option to disable or hide Statements coverage. Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: accelerated-build-now Created: 11/Jul/14 8:07 PM Description: This plug-in is recommended by Bullseye system: http://howto.praqma.net/jenkins/bullseye . But the Bullseye doesn't support the statement coverage, so it would be great to have the option to disable the statement coverage presentation. Project: Jenkins Priority: Minor Reporter: Pawel Faron This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22395) Run.delete (from LogRotator) failing with "...looks to have already been deleted"
Jesse Glick commented on JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted" Testing build of https://github.com/jenkinsci/jenkins/compare/1.565.1-rc1...JENKINS-22395-dropLinks-backport uploaded: http://repo.jenkins-ci.org/public/org/jenkins-ci/main/jenkins-war/1.565.1.JENKINS-22395-dropLinks/jenkins-war-1.565.1.JENKINS-22395-dropLinks.war This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-18866) Symlink prevens backup from ThinBackup
Bart Bialek commented on JENKINS-18866 Symlink prevens backup from ThinBackup I have the same problem with Jenkins 1.550 and thinBackup 1.7: Jul 11, 2014 4:22:43 PM org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork backupNow SEVERE: Cannot perform a backup. Please be sure jenkins/hudson has write privileges in the configured backup path '/var/lib/jenkins/backups'. java.io.FileNotFoundException: Source '/var/lib/jenkins/jobs/Cron_AWD_Sitemap_Generation/builds/lastFailedBuild' does not exist at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:866) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:814) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupBuildFiles(HudsonBackup.java:280) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupBuildsFor(HudsonBackup.java:263) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJob(HudsonBackup.java:202) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobsDirectory(HudsonBackup.java:190) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobs(HudsonBackup.java:169) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backup(HudsonBackup.java:136) at org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork.backupNow(ThinBackupPeriodicWork.java:87) at org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink$1.execute(ThinBackupMgmtLink.java:76) at org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:54) at java.lang.Thread.run(Thread.java:722) The lastFailed build link points to a non existant file: /var/lib/jenkins/jobs/Cron_AWD_Sitemap_Generation/builds/lastFailedBuild -> -1 There are many other jobs that have these broken symlinks. I will manually remove them, but it would be nice for thinBackup to ignore them 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] [core] (JENKINS-18065) AbstractLazyLoadRunMap.iterator() calls .all()
SCM/JIRA link daemon commented on JENKINS-18065 AbstractLazyLoadRunMap.iterator() calls .all() Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/model/lazy/LazyLoadRunMapEntrySet.java http://jenkins-ci.org/commit/jenkins/da57ad5c30b1c9ca8365f869638abd29c8fb5896 Log: JENKINS-18065 54c0846 amendment: presumably RunMap.entrySet().iterator().next().setValue(…) should be illegal. Compare: https://github.com/jenkinsci/jenkins/compare/54c084613f83...da57ad5c30b1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23766) For "Invoke Top-Level Maven Targets" default to --batch-mode
Eric Griswold created JENKINS-23766 For "Invoke Top-Level Maven Targets" default to --batch-mode Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: maven Created: 11/Jul/14 9:28 PM Description: When invoking build steps from the "invoke top-level maven targets", I always add "--batch-mode" in the "goals" field to keep the console output from containing useless progress dross while downloading artifacts. It would be really nice if this were the default. Environment: n/a Project: Jenkins Priority: Minor Reporter: Eric Griswold This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-22346) jenkins cli command with key fails with - java.io.EOFException
Jesse Glick assigned JENKINS-22346 to Kohsuke Kawaguchi jenkins cli command with key fails with - java.io.EOFException Change By: Jesse Glick (11/Jul/14 9:36 PM) Assignee: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18065) AbstractLazyLoadRunMap.iterator() calls .all()
SCM/JIRA link daemon commented on JENKINS-18065 AbstractLazyLoadRunMap.iterator() calls .all() Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/util/RunList.java core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java core/src/main/java/jenkins/model/lazy/LazyLoadRunMapEntrySet.java core/src/test/java/jenkins/model/lazy/AbstractLazyLoadRunMapTest.java http://jenkins-ci.org/commit/jenkins/b227250a63beab888a25c2a781b6fe8e493284d3 Log: [FIXED JENKINS-18065] made ALLRM.entrySet() smarter (cherry picked from commit 54c084613f83f9b7a02957eb98dbd8dc661d1c9c) Conflicts: changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18065) AbstractLazyLoadRunMap.iterator() calls .all()
SCM/JIRA link daemon commented on JENKINS-18065 AbstractLazyLoadRunMap.iterator() calls .all() Code changed in jenkins User: Jesse Glick Path: core/src/test/java/jenkins/model/lazy/AbstractLazyLoadRunMapTest.java core/src/test/java/jenkins/model/lazy/FakeMap.java http://jenkins-ci.org/commit/jenkins/c3e73296b5af0a4aaa06a3bdf867ac50fe211888 Log: JENKINS-18065 Uncommenting original test. The actual implementation does not behave as nicely as one would hope, for a few reasons: 1. isEmpty actually tries to load the newestBuild, rather than simply checking whether there is some idOnDisk. Arguably this is necessary, since there could be an unloadable build record, in which case it would be technically correct for the map to be considered empty. 2. Loading AbstractLazyLoadRunMap.newestBuild calls search(MAX_VALUE, DESC), which behaves oddly, by doing a binary search, and thus perhaps loading lg(|map|) entries. You would think that it would suffice to check for the last member of idOnDisk in index.byId. 3. The iterator eagerly loads the next value before hasNext has even been called. Looks bad in a test, though it probably has little practical impact since most callers would be calling hasNext soon afterward anyway. Might cause one extra build record to be loaded unnecessarily from a limited RunList. (cherry picked from commit 2f58ceb1a66c8ed621fa2562c5ed3445b29ea200) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
