[JIRA] [maven-plugin] (JENKINS-25137) Allow installation of latest maven
twolfart created JENKINS-25137 Allow installation of latest maven Issue Type: New Feature Assignee: Unassigned Components: maven-plugin Created: 14/Oct/14 6:29 AM Description: It seems that there's a problem with the availability of the latest maven version in jenkins. Current available Version is 3.2.3 (website), Jenkins provides 3.2.2 Various tickets show that missing the latest version occurs from time to time: JENKINS-23826 JENKINS-22077 JENKINS-17220 JENKINS-8389 Is the reason maybe that the installers are taken from "archive" (which is very complete), and not from the official apache mirrors (which lists only the latest ones)? An improvement would be to have the possibility to use the latest maven version available. Project: Jenkins Priority: Major Reporter: twolfart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-5253) artifacts archiving: add option for treating patterns in case insensitive way
Daniel Beck commented on JENKINS-5253 artifacts archiving: add option for treating patterns in case insensitive way It's consistent with existing UI, so makes sense. A few more options and an approach like Git plugin's additional behaviors would make more sense, but that's still off a bit IMO. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19584) Ability to redirect user to configuration screen when erroneous data is saved
Daniel Beck commented on JENKINS-19584 Ability to redirect user to configuration screen when erroneous data is saved One other commonly false positive form validation error are the FilePath.checkFileMask related errors in e.g. Archive Artifacts, which often (no workspace) make no sense at all. Maybe don't disable Save/Apply, but require an explicit confirmation like "There are outstanding validation errors. (If possible enumerate the failing options.) Try to save anyway?". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-16802) Using Apache proxysettings breaks several GUI functions
Daniel Beck resolved JENKINS-16802 as Cannot Reproduce Using Apache proxysettings breaks several GUI functions No response to comment asking for updated information in six months, so resolving as Cannot Reproduce. If this occurs on recent Jenkins versions, and you followed the instructions how to set up the reverse proxy in the Jenkins wiki, please just file a new issue. Thanks! Change By: Daniel Beck (14/Oct/14 6:59 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11163) Pages fail to load properly in Firefox with HTTP pipelining enabled
Daniel Beck commented on JENKINS-11163 Pages fail to load properly in Firefox with HTTP pipelining enabled Is this still an issue in recent Jenkins versions that are now based on embedded Jetty (since 1.535)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-2452) Cannot install slave agent as Windows service
Daniel Beck commented on JENKINS-2452 Cannot install slave agent as Windows service Is this still an unresolved issue? Note that being able to only install one slave is tracked elsewhere. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-23409) Crashing api at depth 0
Tomas Westling resolved JENKINS-23409 as Fixed Crashing api at depth 0 Fixed in 1.10.2 Change By: Tomas Westling (14/Oct/14 7:18 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-23409) Crashing api at depth 0
Tomas Westling commented on JENKINS-23409 Crashing api at depth 0 Fixed in 1.10.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [msbuild] (JENKINS-22344) Command Line Arguments: /p:PublishFolder does not work with UNC format to publish to remote server
Akhil Aggarwal reopened JENKINS-22344 Command Line Arguments: /p:PublishFolder does not work with UNC format to publish to remote server This issue is not fixed in MSBuild plugin 1.24 Backslash is still getting truncated at the beginning of the network location. Change By: Akhil Aggarwal (14/Oct/14 7:27 AM) Resolution: Fixed 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-11543) UTF-8 encoding issue of build parameters as soon as including File parameter
SCM/JIRA link daemon commented on JENKINS-11543 UTF-8 encoding issue of build parameters as soon as including File parameter Code changed in jenkins User: Oliver Gondža Path: test/src/test/java/hudson/model/ParametersTest.java http://jenkins-ci.org/commit/jenkins/30715dfd46d8b9987635c6a39cdd21c55d0bcc87 Log: JENKINS-11543 Unit test (cherry picked from commit 75f5d2180f7340ce2efd4f41c8670afb049eb530) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-11163) Pages fail to load properly in Firefox with HTTP pipelining enabled
Karel Vervaeke commented on JENKINS-11163 Pages fail to load properly in Firefox with HTTP pipelining enabled I can't reproduce this with firefox 32.0.something vs Jenkins 1.580. I couldn't find the flag in chrome (but I didn't look very hard). Tested this very briefly, it would recommend getting someone an additional party to confirm this before closing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-11163) Pages fail to load properly in Firefox with HTTP pipelining enabled
Karel Vervaeke edited a comment on JENKINS-11163 Pages fail to load properly in Firefox with HTTP pipelining enabled I can't reproduce this with firefox 32.0.something vs Jenkins 1.580. I couldn't find the flag in chrome (but I didn't look very hard). Tested this very briefly, it would recommend getting an additional opinion to confirm this before closing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-24917) Default background-color: #FFF on tables and table elements isn't overridden by build-pipeline background-color
milki mlk updated JENKINS-24917 Default background-color: #FFF on tables and table elements isnt overridden by build-pipeline background-color Change By: milki mlk (14/Oct/14 7:36 AM) Environment: Jenkins1.581BuildPipelinePlugin1.4.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-9911) JNLP slave JVM options are ignored
Daniel Beck commented on JENKINS-9911 JNLP slave JVM options are ignored Did anyone try this recently? Did it work? From a cursory reading of the sources, this appears to still be unresolved as of 1.584 or so: https://github.com/jenkinsci/windows-slave-installer-module/blob/master/src/main/java/org/jenkinsci/modules/windows_slave_installer/WindowsSlaveInstaller.java#L97 https://github.com/jenkinsci/windows-slave-installer-module/blob/master/src/main/resources/org/jenkinsci/modules/windows_slave_installer/jenkins-slave.xml No VMARGS are set, so no way to add anything between -Xrs and -jar. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-18608) When updating a plugin, check versions of dependencies
Daniel Beck commented on JENKINS-18608 When updating a plugin, check versions of dependencies This already happens, so what is this issue for? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-24917) Default background-color: #FFF on tables and table elements isn't overridden by build-pipeline background-color
Daniel Beck commented on JENKINS-24917 Default background-color: #FFF on tables and table elements isnt overridden by build-pipeline background-color This has been resolved in core (https://github.com/jenkinsci/jenkins/commit/4eefff9f95570ed8be4b98ab4ae683004dc65de8) towards 1.586. Sorry about that! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Jennifer Hofmeister edited a comment on JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. I've been experiencing the error with every checkout attempt, not only externals, and it's persistent. Windows 7 master and slaves. Jenkins 1.565.2 (official latest stable) and Subversion 2.4.3. I decided to upgrade from 1.561/2.0 after encountering some SVN external issues that suddenly occurred (J refused to check out and then complained things were missing). Although it seems like a pure Subversion issue, downgrading Subversion plugin to 2.0 and 1.5.4 didn't help. Eventually, I upgraded it back to 2.4.3 and manually reconfigured all affected jobs in the above way ... but needless to say, that was a drag^^ Edit: I found out that Jenkins sometimes tries to connect to the SVN server without actually giving credentials. Here's from the svn server's connection log: " 190.10.210.20 - jenkins 25/Sep/2014:15:09:06 +0200 ... 190.10.210.20 - jenkins 25/Sep/2014:15:09:06 +0200 ... 190.10.210.20 - - 25/Sep/2014:15:09:06 +0200 ... 190.10.210.20 - - 25/Sep/2014:15:09:06 +0200 ... First two checkouts succeeded, last two didn't. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-16316) global variable not updated
Guy Shaanan
reopened JENKINS-16316
global variable not updated
Not sure if it is the same bug or a new one:
When you have a build parameter, and you try to inject a value to it, the value is not injected.
Ways to reproduce:
JOB #1
--
1. Add build parameter called BRANCH (or whatever name you like)
2. Add shell script with echo "BRANCH=test" build.prop
3. Inject build.prop using the envinject plugin
4. echo ${BRANCH}
this echos blank value (or the default value set to parameter) instead of "test"
JOB #2
---
1. remove the parameter named BRANCH.
Rest of the steps (2-4) remain the same:
2. Add shell script with echo "BRANCH=test" build.prop
3. Inject build.prop using the envinject plugin
4. echo ${BRANCH}
this echos "test"
We've upgraded Jenkins to 1.584 and envinject plugin to 1.90 and this behavior happens.
Job #1 and Job #2 should both echo "test" to the screen.
This was working before the upgrade we did (I don't remember which plugin version we had previously).
Thanks.
Change By:
Guy Shaanan
(14/Oct/14 8:02 AM)
Resolution:
Fixed
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] [crowd2] (JENKINS-16703) Too many periodic requests to Crowd server
Kanstantsin Shautsou commented on JENKINS-16703 Too many periodic requests to Crowd server Try remove group restriction... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-25138) Weird The label _some_jmeter_label caused the build to fail during comparizon
Thomas Mortagne created JENKINS-25138 Weird The label _some_jmeter_label caused the build to fail during comparizon Issue Type: Bug Assignee: Manuel Carrasco Components: performance-plugin Created: 14/Oct/14 8:15 AM Description: I attached an example. As you can see in the log I set 0% everywhere in "Use Relative thresholds for build comparison" to make sure it's not failing because of that but I still get a failure without any information on why it failed. Also does not always fail on the same label. You can see the job on http://ci.xwiki.org/job/xwiki-enterprise-test-jmeter/. Environment: Performance plugin 1.11 Jenkins 1.565.3 Project: Jenkins Priority: Minor Reporter: Thomas Mortagne This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-25138) Weird The label _some_jmeter_label caused the build to fail during comparizon
Thomas Mortagne updated JENKINS-25138 Weird The label _some_jmeter_label caused the build to fail during comparizon Change By: Thomas Mortagne (14/Oct/14 8:17 AM) Attachment: log.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [deploy-plugin] (JENKINS-25139) [Deploy plugin] Need to parameterize for glassfish 3.x containter's properties
Thanh Ho
created JENKINS-25139
[Deploy plugin] Need to parameterize for glassfish 3.x containters properties
Issue Type:
Improvement
Assignee:
Unassigned
Components:
deploy-plugin
Created:
14/Oct/14 8:40 AM
Description:
I have a need to deploy ear file to different glassfish 3.x containters. For now, I have to create individual jobs for each container.
May I request dev team to enhance the deploy plugin to enable the ability to parameterize for glassfish the container's properties. Then I can input something like this ${GLASSFISH_HOME}, ${GLASSFISH_HOST} for glassfish home and hostname
Thanks and best regards,
Thanh
Project:
Jenkins
Labels:
plugin
Priority:
Major
Reporter:
Thanh Ho
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [jiratestresultreporter] (JENKINS-25140) JiraTestResultReporter.JiraReporter aborted due to exception error.
Praveen Lakshmanan created JENKINS-25140 JiraTestResultReporter.JiraReporter aborted due to exception error. Issue Type: Bug Assignee: Unassigned Components: jiratestresultreporter Created: 14/Oct/14 8:50 AM Description: I configured JIRA plugin with Jenkins, I'm getting this error after build get completed. Could anyone explain how can I fix this issue. Please check this URL, which I have configured like this for JIRA test result reporter: http://maplesteve.com/2013/03/24/create-jira-issues-from-jenkins/ Error: JiraTestResultReporter INFO Examining test results... ERROR: Publisher JiraTestResultReporter.JiraReporter aborted due to exception java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; at JiraTestResultReporter.JiraReporter.perform(JiraReporter.java:105) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1770) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Versions: Jenkins ver. 1.580 JiraTestResultReporter plugin 1.0.4 JIRA: 6.4 Project: Jenkins Priority: Blocker Reporter: Praveen Lakshmanan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-19179) Matrix sub-jobs get disabled
SCM/JIRA link daemon resolved JENKINS-19179 as Fixed Matrix sub-jobs get disabled Change By: SCM/JIRA link daemon (14/Oct/14 8:53 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-19179) Matrix sub-jobs get disabled
SCM/JIRA link daemon commented on JENKINS-19179 Matrix sub-jobs get disabled Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/matrix/MatrixConfiguration.java src/main/resources/hudson/matrix/Messages.properties http://jenkins-ci.org/commit/matrix-project-plugin/c5ed324690b68eaa636da879dae801e5f323178f Log: Merge pull request #5 from synopsys-arc-oss/JENKINS-19179 FIXED JENKINS-19179 - Prevent the disabling of Matrix Configurations Compare: https://github.com/jenkinsci/matrix-project-plugin/compare/b888102cb7dc...c5ed324690b6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jiratestresultreporter] (JENKINS-25140) JiraTestResultReporter.JiraReporter aborted due to exception error.
Praveen Lakshmanan updated JENKINS-25140 JiraTestResultReporter.JiraReporter aborted due to exception error. Change By: Praveen Lakshmanan (14/Oct/14 8:51 AM) Description: IconfiguredJIRApluginwithJenkins,Imgettingthiserrorafterbuild get gets completed.CouldanyoneexplainhowcanIfixthisissue.PleasecheckthisURL,whichIhaveconfiguredlikethisforJIRAtestresultreporter:http://maplesteve.com/2013/03/24/create-jira-issues-from-jenkins/Error:[JiraTestResultReporter][INFO]Examiningtestresults...ERROR:PublisherJiraTestResultReporter.JiraReporterabortedduetoexceptionjava.lang.NoSuchMethodError:hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; atJiraTestResultReporter.JiraReporter.perform(JiraReporter.java:105) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) athudson.model.Build$BuildExecution.post2(Build.java:183) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) athudson.model.Run.execute(Run.java:1770) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:89) athudson.model.Executor.run(Executor.java:240)Versions:Jenkinsver.1.580JiraTestResultReporterplugin1.0.4JIRA:6.4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-25085) email-ext showPaths does not work with p4-plugin
Paul Allen commented on JENKINS-25085 email-ext showPaths does not work with p4-plugin I'll see what I can implement. My concern is that I don't want to store 1000s files in the Jenkins XML like the old plugin. As the data is in Perforce, all I have been storing is the change numbers, then I can look the files up as needed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-25123) Configuration Slicing plugin 1.39 does not support build timeout plugin 1.14
Jochen Ehret commented on JENKINS-25123 Configuration Slicing plugin 1.39 does not support build timeout plugin 1.14 Hi Daniel, I've installed version 1.11 of the build timeout plugin and it works fine with the slicing plugin 1.39. I'll lower the priority of this bug accordingly. Thanks again and best regards, Jochen. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25134) Enhance 'Auto cleanup and sync' populate option to not remove private repository directory
Paul Allen commented on JENKINS-25134 Enhance Auto cleanup and sync populate option to not remove private repository directory I think your requested is related to JENKINS-23974 I'm looking for a neat solution, I don't necessarily want to reimplement the old plugin. Have you tried a workspace exclusionary mapping? e.g. //depot/my_proj/... //workspace/... -//depot/my_proj/.repository //workspace/.repository This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-25123) Configuration Slicing plugin 1.39 does not support build timeout plugin 1.14
Jochen Ehret updated JENKINS-25123 Configuration Slicing plugin 1.39 does not support build timeout plugin 1.14 Change By: Jochen Ehret (14/Oct/14 9:15 AM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
SCM/JIRA link daemon commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users Code changed in jenkins User: ninian Path: src/main/webapp/help-sendEmails.html http://jenkins-ci.org/commit/claim-plugin/425b1979c31f25d7f360489344e832cced13ba4c Log: JENKINS-7824: Correct text for email help This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
SCM/JIRA link daemon commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users Code changed in jenkins User: ninian Path: src/main/resources/hudson/plugins/claim/ClaimColumn/column.jelly http://jenkins-ci.org/commit/claim-plugin/0dd4449b9f1d6d49d608190e558cb86048b1abbf Log: JENKINS-7824: Correct indentation for change to add assigned by field This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
SCM/JIRA link daemon commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users Code changed in jenkins User: ninian Path: src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.jelly src/main/webapp/help-sendEmails.html http://jenkins-ci.org/commit/claim-plugin/231ef9f6ad00a509406ca04a23954cb9cca45f42 Log: JENKINS-7824: Allow users to drop claims assigned to them by 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] [claim] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
SCM/JIRA link daemon commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users Code changed in jenkins User: ninian Path: src/main/java/hudson/plugins/claim/AbstractClaimBuildAction.java src/main/java/hudson/plugins/claim/ClaimTestAction.java src/main/java/hudson/plugins/claim/ClaimedBuildsReport.java src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.jelly src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.properties src/main/resources/hudson/plugins/claim/ClaimColumn/column.jelly src/main/resources/hudson/plugins/claim/ClaimColumn/column.properties src/main/resources/hudson/plugins/claim/Messages.properties src/main/webapp/help-assignee.html src/test/java/hudson/plugins/claim/ClaimTest.java http://jenkins-ci.org/commit/claim-plugin/69dd1a8827220bdd2d3456e8744f8ce1e3003d92 Log: JENKINS-7824: Add a record of who assigned the build failure and display 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] [claim] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
SCM/JIRA link daemon commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users Code changed in jenkins User: ki82 Path: pom.xml src/main/java/hudson/plugins/claim/AbstractClaimBuildAction.java src/main/java/hudson/plugins/claim/ClaimBuildAction.java src/main/java/hudson/plugins/claim/ClaimConfig.java src/main/java/hudson/plugins/claim/ClaimEmailer.java src/main/java/hudson/plugins/claim/ClaimTestAction.java src/main/java/hudson/plugins/claim/ClaimTestDataPublisher.java src/main/java/hudson/plugins/claim/ClaimedBuildsReport.java src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.jelly src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.properties src/main/resources/hudson/plugins/claim/ClaimColumn/column.jelly src/main/resources/hudson/plugins/claim/ClaimColumn/column.properties src/main/resources/hudson/plugins/claim/ClaimConfig/config.jelly src/main/resources/hudson/plugins/claim/ClaimConfig/config.properties src/main/resources/hudson/plugins/claim/Messages.properties src/main/webapp/help-assignee.html src/main/webapp/help-sendEmails.html src/test/java/hudson/plugins/claim/ClaimEmailerTest.java src/test/java/hudson/plugins/claim/ClaimTest.java http://jenkins-ci.org/commit/claim-plugin/10c6cf1221cab49bc9e59914a33aed3df5a0e6f3 Log: Merge pull request #13 from ninian/master JENKINS-7824: Add 'assigned by' field and optional emails Compare: https://github.com/jenkinsci/claim-plugin/compare/dcefc3d941f9...10c6cf1221ca This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
SCM/JIRA link daemon commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users Code changed in jenkins User: ninian Path: src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.jelly src/main/resources/hudson/plugins/claim/ClaimColumn/column.jelly http://jenkins-ci.org/commit/claim-plugin/45c067c337238053d12f87873c8369b6da768d42 Log: JENKINS-7824: use spaces rather than tabs in jelly files modified to add assigned by details This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
Christian Åkerström resolved JENKINS-7824 as Fixed Claim plugin: Allow assigning builds/tests to other users Released in 2.4 today. Change By: Christian Åkerström (14/Oct/14 9:36 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rebuild] (JENKINS-22836) Rebuild Last link out of date
SCM/JIRA link daemon commented on JENKINS-22836 Rebuild Last link out of date Code changed in jenkins User: Robert Sandell Path: src/main/java/com/sonyericsson/rebuild/RebuildLastCompletedBuildAction.java src/test/java/com/sonyericsson/rebuild/RebuildValidatorTest.java http://jenkins-ci.org/commit/rebuild-plugin/93a3385991f827cb7d775a525b4c097385d026e2 Log: Merge pull request #27 from andresoderlind/ISSUE-J-22836 JENKINS-22836 Rebuild Last link out of date Compare: https://github.com/jenkinsci/rebuild-plugin/compare/6465b86cd755...93a3385991f8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-18608) When updating a plugin, check versions of dependencies
Jesse Glick commented on JENKINS-18608 When updating a plugin, check versions of dependencies See my first comment: if the dependency update is missing, Jenkins silently ignores 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] [envinject] (JENKINS-16316) global variable not updated
Jesse Glick resolved JENKINS-16316 as Fixed global variable not updated Guy Shaanan: Not sure if it is the same bug or a new one Then file a new bug report, and link it to this one as possibly related. Change By: Jesse Glick (14/Oct/14 10:26 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19584) Ability to redirect user to configuration screen when erroneous data is saved
Jesse Glick commented on JENKINS-19584 Ability to redirect user to configuration screen when erroneous data is saved If there is no workspace, validateFileMask reports ok() as you would expect. The error status should be reserved for cases where the validation method is reasonably sure something is actually wrong. However any logic driven off FormValidation would really have to look for warnings, too, since for example a blank required field is normally shown as a warning rather than an error under the expectation that the user is about to fill it in and just has not gotten there yet and showing a red mark on a freshly loaded form is impolite. Not sure if we can defer validation checks until after the field has gotten focus, or if we could introduce a status which is logically like ERROR yet is displayed in a more toned-down UI that merely indicates that a field is required, not that you did something wrong. I like the idea of showing a dialog when Save (or Apply) is clicked, which shows a list of outstanding warnings and errors. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24521) Update jna from 3.3.0-jenkins to 4.1.0 (or newer)
SCM/JIRA link daemon commented on JENKINS-24521 Update jna from 3.3.0-jenkins to 4.1.0 (or newer) Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jvnet/hudson/Windows.java http://jenkins-ci.org/commit/extras-memory-monitor/d7f3f13f3832c890f611174e99fc700a84f41731 Log: Merge pull request #5 from rodrigc/master Update to use JNA 4.1.0. JENKINS-24521 Compare: https://github.com/jenkinsci/extras-memory-monitor/compare/3fef06ffe299...d7f3f13f3832 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24521) Update jna from 3.3.0-jenkins to 4.1.0 (or newer)
SCM/JIRA link daemon commented on JENKINS-24521 Update jna from 3.3.0-jenkins to 4.1.0 (or newer) Code changed in jenkins User: Craig Rodrigues Path: pom.xml src/main/java/org/jvnet/hudson/Windows.java http://jenkins-ci.org/commit/extras-memory-monitor/5c4f38d2b9e70dffc22bcd488c292710335bfe14 Log: Update to use JNA 4.1.0. JENKINS-24521 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-5253) artifacts archiving: add option for treating patterns in case insensitive way
Dominique Brice commented on JENKINS-5253 artifacts archiving: add option for treating patterns in case insensitive way Pull request created. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-25011) Promoted Builds does not work with CloudBees Folder plugin
Jesse Glick updated JENKINS-25011 Promoted Builds does not work with CloudBees Folder plugin Change By: Jesse Glick (14/Oct/14 10:49 AM) Labels: folders This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-25011) Promoted Builds does not work with CloudBees Folder plugin
Jesse Glick commented on JENKINS-25011 Promoted Builds does not work with CloudBees Folder plugin The first part of the initially reported bug is somehow related to authentication. Pull #47/#48 would likely not help; these seem to be addressing an unrelated (possibly unfiled) bug, about the default value of a promotion parameter. The second part, about cloudbees-folders-plus, is also probably an unrelated issue, and not necessarily in promoted-builds at all. Reporter, for issues specific to Jenkins Enterprise plugins please just file a support ticket so the problem can be analyzed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-25011) Promoted Builds does not work with CloudBees Folder plugin
Jesse Glick edited a comment on JENKINS-25011 Promoted Builds does not work with CloudBees Folder plugin The first part of the initially reported bug is somehow related to authentication. Pull #47/#48 would likely not help; these seem to be addressing an unrelated (possibly unfiled) bug, about the default value of a promotion parameter. The second part, about cloudbees-folders-plus, is also probably an unrelated issue, and not necessarily in promoted-builds at all. Reporter, for issues specific to Jenkins Enterprise plugins please just file a support ticket so the problem can be analyzed. (Or even if not specific to Jenkins Enterprise and you just want to ensure you get helped.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-25141) Can't inject value to build parameter
Guy Shaanan
created JENKINS-25141
Cant inject value to build parameter
Issue Type:
Bug
Assignee:
Gregory Boissinot
Components:
envinject
Created:
14/Oct/14 11:26 AM
Description:
Possibly related to: JENKINS-16316
When you have a build parameter, and you try to inject a value to it, the value is not injected.
Ways to reproduce:
JOB #1 - broken
--
1. Add build parameter called BRANCH (or whatever name you like)
2. Add shell script with
echo "BRANCH=test" build.prop
3. Inject build.prop using the envinject plugin
4. Add shell script with
echo ${BRANCH}
this echos empty value (or the default value set to the parameter) instead of "test"
JOB #2 - Good
---
1. remove the parameter named BRANCH.
Rest of the steps (2-4) remain the same:
2. Add shell script with echo
"BRANCH=test" build.prop
3. Inject build.prop using the envinject plugin
4. Add shell script with
echo ${BRANCH}
this echos "test"
Job #1 and Job #2 should both echo "test" to the screen.
This was working before we did Jenkins + plugin upgrade. (I don't remember which plugin version we had previously).
Thanks.
Environment:
Jenkins: 1.548
Plugin: 1.90
Project:
Jenkins
Priority:
Major
Reporter:
Guy Shaanan
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [view-job-filters] (JENKINS-25142) The view style loss when there are many view tabs
jun feng created JENKINS-25142 The view style loss when there are many view tabs Issue Type: Bug Assignee: Jacob Robertson Attachments: 2014-09-09_17-03-36.jpg Components: view-job-filters Created: 14/Oct/14 11:27 AM Description: 1. login Jenkins 2. create many views 3. check the view tabs，please see the attachment the version 1.574 is right，after version 1.574 is wrong Environment: After version 1.574 Project: Jenkins Priority: Major Reporter: jun feng This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
Marnix Klooster commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported @Daniel Beck: Today I'm adding the --httpKeepAliveTimeout=60 flag, and we'll see what happens. Still, this timeout cannot be the whole story: the report sounds like the problem does not occur with 1.532.3 and before, while it does occur with 1.554.3 and later. (The fact that for me, a remote 1.456 also triggers the problem might be an outlier...?) If the default for httpKeepAliveTimeout has not changed (and I think it is already 5000 for quite some time), and multiple users' networks didn't simultaneously and suddenly deteriorate, then there has to be some other cause. Right? Finally, we also have seen this problem occurring with 1.565.1 on our local LAN, which is when we got the timeout exception. I'm pretty sure our local LAN not have any real networking problems, but I could be wrong of course, and the timeout occurring on 1.565.1 could be a coincidence which could equally have happened on 1.532.3. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [view-job-filters] (JENKINS-25142) The view style loss when there are many view tabs
jun feng updated JENKINS-25142 The view style loss when there are many view tabs Change By: jun feng (14/Oct/14 11:31 AM) Attachment: 2014-09-09_17-05-47.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [firefox-extension-buildmonitor] (JENKINS-14881) Icons are not displayed (correctly) in Firefox Add-on Build Monitor
Lucas Ventura Carro commented on JENKINS-14881 Icons are not displayed (correctly) in Firefox Add-on Build Monitor Same here, but Jenkins is version 1.572, and other computer in same network, works as expected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [firefox-extension-buildmonitor] (JENKINS-14881) Icons are not displayed (correctly) in Firefox Add-on Build Monitor
Lucas Ventura Carro edited a comment on JENKINS-14881 Icons are not displayed (correctly) in Firefox Add-on Build Monitor Same here, but Jenkins is version 1.572, and other computer in same network, works as expected. I don't know how to see the debug logs to add more information,... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [firefox-extension-buildmonitor] (JENKINS-14881) Icons are not displayed (correctly) in Firefox Add-on Build Monitor
Lucas Ventura Carro edited a comment on JENKINS-14881 Icons are not displayed (correctly) in Firefox Add-on Build Monitor Same here, but Jenkins is version 1.572, and other computer in same network, works as expected. I don't know how to see the debug logs to add more information,... Updated info: I've changed the downloading.png by the error.png icon inside .jar file, and it is showed correctly. As far as I can do This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [firefox-extension-buildmonitor] (JENKINS-14881) Icons are not displayed (correctly) in Firefox Add-on Build Monitor
Lucas Ventura Carro edited a comment on JENKINS-14881 Icons are not displayed (correctly) in Firefox Add-on Build Monitor Same here, but latests Firefox 32.0.3 and Jenkins is version 1.572. Other computer in same network with same Firefox, works as expected. I don't know how to see the debug logs to add more information,... Updated info: I've changed the downloading.png by the error.png icon inside .jar file, and it is showed correctly. As far as I can do This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [firefox-extension-buildmonitor] (JENKINS-14881) Icons are not displayed (correctly) in Firefox Add-on Build Monitor
Lucas Ventura Carro edited a comment on JENKINS-14881 Icons are not displayed (correctly) in Firefox Add-on Build Monitor Same here, but environment is Firefox 32.0.3, Windows 7 and Jenkins 1.572. Other computer in same network with same Firefox, works as expected. I don't know how to see the debug logs to add more information,... Updated info: I've changed the downloading.png by the error.png icon inside .jar file, and it is showed correctly. As far as I can do This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber] (JENKINS-25143) 'no such file or directory' error while saving configure page
Zeinab Abbasi created JENKINS-25143 no such file or directory error while saving configure page Issue Type: Bug Assignee: kutzi Components: jabber Created: 14/Oct/14 11:58 AM Description: I was trying to set user/pass for jabber notification plugin and I got this: Oct 14, 2014 7:23:58 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: descriptor.nickname in /configure. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
[JIRA] [github] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella commented on JENKINS-25127 Hook uninstalled if job is in a subfolder I don't have a Java development environment, but I would be very much interested in testing a fix if someone can provide 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] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
Leandro Lucarella commented on JENKINS-24954 Test PASSed comments added even if Published Jenkins URL I can confirm it's NOT fixed in 16-3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
Marco Krikke commented on JENKINS-24954 Test PASSed comments added even if Published Jenkins URL +1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23583) Column Test Result has incorrect link
Diogo Campos commented on JENKINS-23583 Column Test Result has incorrect link It seems that this only happens for views using a regex to match jobs. Jobs selected individually from checkboxes do not have this problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-22383) Failure found during the build process of RTRT using windows batch command
Satya Asati updated JENKINS-22383 Failure found during the build process of RTRT using windows batch command Change By: Satya Asati (14/Oct/14 12:56 PM) Description: WhenweexecutedtheRTRTunittestscriptusingWindowsbatchcommandasmentionedbelow ButatbuildphasewegotfailurewhichisduetoWindowsbatchcommandandwhenweareperformpostbuildaction-PublishjunittestreportusingXRDfilegeneratedbyRTRTtool.Wearegettingerrorwhichisalsomentionedinbelowerrormessage.Sopleasehelpustoresolvethisissue.StartedbyuseranonymousBuildinginworkspaceD:\CleaninglocalDirectoryROOT/SOURCECheckingouthttp://sreublr213.eu.labinal.snecma/svn/carmeq/trunk/SOURCEatrevision2014-03-27T17:48:03.285+0530Atrevision24nochangeforhttp://sreublr213.eu.labinal.snecma/svn/carmeq/trunk/SOURCEsincethepreviousbuild[]$cmd/ccallC:\Windows\TEMP\hudson642869198705461714.batD:\studio.exe-rD:\ROOT\TEST\2_Units_Module\SWK_RGL\SiLMSVS2010\Implementierung\ARAComponent\ARAComponent.rtp-htmlD:\ROOT\TEST\2_Units_Module\SWK_RGL\SiLMSVS2010\Reports\ARAComponent\ResultTestNode:ARAComponent.ARAComponent [113]TestCasePassed [0]TestCaseFailedD:/ROOT/TEST/2_Units_Module/SWK_RGL/SiLMSVS2010/Reports/ARAComponent/Result\index.htmlTheHTMLreportexportationsucceeded.D:\exit1BuildstepExecuteWindowsbatchcommandmarkedbuildasfailureRecordingtestresultsERROR:Failedtoarchivetestreportsjava.io.IOException:FailedtoreadD:\ROOT\TEST\2_Units_Module\SWK_RGL\SiLMSVS2010\Implementierung\ARAComponent\VS_SiL\ARAComponent.xrdIsthisreallyaJUnitreportfile?Yourconfigurationmustbematchingtoomanyfiles athudson.tasks.junit.TestResult.parse(TestResult.java:281) athudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:229) athudson.tasks.junit.TestResult.parse(TestResult.java:164) athudson.tasks.junit.TestResult.parse(TestResult.java:147) athudson.tasks.junit.TestResult.init(TestResult.java:123) athudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:117) athudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:90) athudson.FilePath.act(FilePath.java:914) athudson.FilePath.act(FilePath.java:887) athudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87) athudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:121) athudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:133) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) athudson.model.Build$BuildExecution.post2(Build.java:183) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) athudson.model.Run.execute(Run.java:1703) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:231)Causedby:org.dom4j.DocumentException:Erroronline68ofdocumentfile:///D:/ROOT/TEST/2_Units_Module/SWK_RGL/SiLMSVS2010/Implementierung/ARAComponent/VS_SiL/ARAComponent.xrd:TheprefixXRODforelementXROD:NODEisnotbound.Nestedexception:TheprefixXRODforelementXROD:NODEisnotbound. atorg.dom4j.io.SAXReader.read(SAXReader.java:482) atorg.dom4j.io.SAXReader.read(SAXReader.java:264) athudson.tasks.junit.SuiteResult.parse(SuiteResult.java:123) athudson.tasks.junit.TestResult.parse(TestResult.java:273) ...20moreCausedby:org.xml.sax.SAXParseException;systemId:file:///D:/ROOT/TEST/2_Units_Module/SWK_RGL/SiLMSVS2010/Implementierung/ARAComponent/VS_SiL/ARAComponent.xrd;lineNumber:68;columnNumber:85;TheprefixXRODforelementXROD:NODEisnotbound. atcom.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(UnknownSource) atcom.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(UnknownSource)
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
SCM/JIRA link daemon commented on JENKINS-20772 Apply error screens dont work Code changed in jenkins User: Jesse Glick Path: war/src/main/webapp/scripts/hudson-behavior.js http://jenkins-ci.org/commit/jenkins/9620057a58dc07b52752683a433e200f36d4317d Log: When a server error is caught by applyErrorMessage (“ERROR” link), do not render the whole oops.jelly page. Just pick out the div id="error-description" from JENKINS-20772. Compare: https://github.com/jenkinsci/jenkins/compare/7ddc6be48716...9620057a58dc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs] (JENKINS-4709) Add exclusion regions in TFS polling and checkout
Aaron Alexander commented on JENKINS-4709 Add exclusion regions in TFS polling and checkout There is a new pull request (https://github.com/jenkinsci/tfs-plugin/pull/28) that implements this with workspace cloaking. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [security] (JENKINS-25144) Basic Authentication in combination with Session is broken
Christof Schoell
created JENKINS-25144
Basic Authentication in combination with Session is broken
Issue Type:
Bug
Assignee:
Unassigned
Components:
security
Created:
14/Oct/14 1:42 PM
Description:
BasicAuthentication in combination with a sessionId is broken - after the first login following page refreshs fail with bad credentials.
Here my analysis (I commented this on the corresponding commit on github as well):
The BasicHeaderProcessor expects a not null Authentication Object
From BasicHeaderProcessor:
Authentication auth = a.authenticate(req, rsp, username, password);
if (auth!=null) {
LOGGER.log(FINE, "Request authenticated as {0} by {1}", new Object[]{auth,a});
success(req, rsp, chain, auth);
return;
}
>From BasicHeaderRealPasswordAuthenticator:
if (!authenticationIsRequired(username))
return null;
It seems that you need to return the existing authentication Object from BasicHeaderRealPasswordAuthenticator and not null if the current authentication is already valid...?
Anyway since we are running jenkins through a proxy with basicAuth the current version is completely broken for us...
Corresponding Github commit: https://github.com/jenkinsci/jenkins/commit/b2a98f6bc6924d1fd25f7da583888c2f4f36d83c
Environment:
Jenkins Version 1.584
Project:
Jenkins
Labels:
Authentication
BasicAuth
Priority:
Critical
Reporter:
Christof Schoell
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-25145) Version Jenkins Configuration In Perforce
Karl Wirth created JENKINS-25145 Version Jenkins Configuration In Perforce Issue Type: New Feature Assignee: Unassigned Components: p4 Created: 14/Oct/14 1:43 PM Description: Provide a plugin that versions the Jenkins configuration in Perforce. It could be similar to: https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin Project: Jenkins Priority: Minor Reporter: Karl Wirth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-19345) NoClassDefFoundError on project build
Rafa Torregrosa commented on JENKINS-19345 NoClassDefFoundError on project build I solve this problem downgrading the git-client and git plugins to 1.9.0 and 1.5.0 respectively, as Berg Systeme suggested in his blog: http://blog.berg-systeme.de/2014/05/15/downgrade-jenkins-git-plugin/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-25066) Build on the same node option triggers runs on node with same label and not on identical node
Tobias Del Fabro commented on JENKINS-25066 Build on the same node option triggers runs on node with same label and not on identical node The configured labels are: node: debian-build - label: debian-build debian-build1 node: debian-build2 - label: debian-build In fact I forgot to mention that in that configuration the "debian-build" node is running on the jenkins-master machine (not master-node, but ssh configured node). In the meantime I re-configured the system and have now 2 real slaves + 1 master. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-2452) Cannot install slave agent as Windows service
Chris Welch resolved JENKINS-2452 as Fixed Cannot install slave agent as Windows service Haven't had this issue in a very long time. Slave setup has been working fine for at least the past 4 years. Change By: Chris Welch (14/Oct/14 2:36 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
James Clark
commented on JENKINS-24965
Personal builds can encounter deadlock when fetching source
Hi Heather, no worries - late replying myself .
I've seen it happen to a handful of different people, including myself. My workspace is public (as we encourage all of our team to do) so visibility shouldn't be an issue. We only have a couple of components that rarely change so I imagine it's unlikely any of the hanging builds had something different, component-wise.
The load directory for the build definition is set to 'src' so that it checks out to {JOB_WORKSPACE}/src.
There are no special actions checked nor any excludes set for the load actions or accept options. I guess these are default values but I can send you exactly what option has what value if you need (assuming some might not be blank by default).
There haven't been many personal builds lately so I unfortunately don't have the output log to hand. Next time I see a hanging build, I will update this ticket.
Not quite sure what you mean by the build result having an activity for fetching files but the build doesn't get to the point of actually building anything. It tries to checkout the src code and never comes back from there.
Trying to abort the build via Jenkins has no effect. The only way to stop it is to kill the master Jenkins process.
Hope that helps, let me know if you need anything else!
Thanks,
James
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [security] (JENKINS-25144) Basic Authentication in combination with Session is broken
Christof Schoell updated JENKINS-25144 Basic Authentication in combination with Session is broken Change By: Christof Schoell (14/Oct/14 2:47 PM) Priority: Critical Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25146) When the anonymous user has no access rights, userContent is inaccessible
Roland Clobus created JENKINS-25146 When the anonymous user has no access rights, userContent is inaccessible Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Oct/14 3:14 PM Description: Hello, I've tried the following: I have a Jenkins installation on Debian stable with the most recent Jenkins release (via the official Jenkins repository) I have enabled security The anonymous user does not have any rights (not even 'Read'), because I don't want to show which nodes are active or which users are configured. Nobody is logged in I browse to http://localhost:8080/userContent/ Achieved result: I see a login prompt. Expected result: I've seen ticket https://issues.jenkins-ci.org/browse/JENKINS-23259, which handles exactly the opposite situation. According to the Wiki page at https://wiki.jenkins-ci.org/display/JENKINS/User+Content the userContent folder should be accessible. quoteNote that these files are not subject to any access controls./quote Versions affected: 1.565.3, 1.580, 1.584 Is the Wiki page incomplete and should it mention that when the anonymous has no rights at all, userContent is protected, or should the userContent folder always be unprotected? Project: Jenkins Priority: Minor Reporter: Roland Clobus This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-25141) Can't inject value to build parameter
Oleg Nenashev resolved JENKINS-25141 as Duplicate Cant inject value to build parameter Change By: Oleg Nenashev (14/Oct/14 3:07 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] [security] (JENKINS-25144) Basic Authentication in combination with Session is broken
Christof Schoell commented on JENKINS-25144 Basic Authentication in combination with Session is broken Added a pull request with a fix for this bug on github: https://github.com/jenkinsci/jenkins/pull/1427 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [youtrack] (JENKINS-25057) Backlinks option is commenting on wrong projects.
Erik Zielke resolved JENKINS-25057 as Fixed Backlinks option is commenting on wrong projects. Change By: Erik Zielke (14/Oct/14 4:17 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] [youtrack] (JENKINS-25057) Backlinks option is commenting on wrong projects.
Erik Zielke commented on JENKINS-25057 Backlinks option is commenting on wrong projects. Okay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [youtrack] (JENKINS-24333) No action for executing command from build step
Erik Zielke commented on JENKINS-24333 No action for executing command from build step Ok, will look into it when I get time. Yes. A possibilty is that I could create a changelog string in the plugin and inject it into the environment, although I believe it is a bit out of scope for the plugin. For now the text in the "Update YouTrack issue with link to build" is hardcoded, but having the possibilty to specify it is something I have considered implementing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-25147) Cannot access pom.xml directory after Jenkins update
Jennifer Hofmeister created JENKINS-25147 Cannot access pom.xml directory after Jenkins update Issue Type: Bug Assignee: stephenconnolly Components: credentials, maven-plugin Created: 14/Oct/14 4:27 PM Description: After updating Jenkins from 1.551 to 1.565.2, some of our Maven-type jobs fail with the following message: "INFO Scanning for projects... ERROR The build could not read 1 project - Help 1 org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: FATAL Non-readable POM D:\Jenkins\Jobs\JobName\workspace\JobName-test: D:\Jenkins\Jobs\JobName\workspace\JobName-test (Access is denied)" D:\...\JobName-test contains the pom.xml. It happens when Maven is called through "Invoke top-level Maven targets". Maven Version: (Default) Goals: verify -X -f "D:\Jenkins\Jobs\JobName\workspace\JobName-test" -Dparam1=abc -Dparam2=def -Dparam3=10 The Jenkins user account on Windows has all access rights on the Jenkins directories and files. The odd thing about this is that we have another set of Maven-type jobs that run just fine, with the same kind of build step. The only difference is that those are generated from a template job while the failing ones are not. All of them worked fine before the update. Unfortunately, reconstruction of this error is somewhat complicated since we have an issue with Jenkins giving no SVN credentials that sometimes aborts the build at an earlier point. It also occurred after the Jenkins update. I will open another issue for that, but I suspect the two might be related. It's a Environment: Windows 7 Jenkins 1.565.2 Maven Project Plugin 2.6 Subversion Plugin 2.4.3 Project: Jenkins Labels: maven3 credentials Priority: Major Reporter: Jennifer Hofmeister This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nested-view] (JENKINS-25148) Can't search nested views
milki mlk created JENKINS-25148 Cant search nested views Issue Type: Bug Assignee: Unassigned Components: nested-view Created: 14/Oct/14 4:32 PM Description: Views created in nested views aren't searchable in the main jenkins search box. Is this a design or limitation of the plugin? Cloudbees Folders seem to have the same issue. Project: Jenkins Labels: user-experience Priority: Minor Reporter: milki mlk This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-25149) svn: E200015: No credential to try - persistent
Jennifer Hofmeister created JENKINS-25149 svn: E200015: No credential to try - persistent Issue Type: Bug Assignee: stephenconnolly Components: credentials, subversion-plugin Created: 14/Oct/14 4:36 PM Description: After updating Jenkins from 1.551 to 1.565.2, our jobs fail, more often than not, with the SVN exception "E200015: No credential to try. Authentication failed" I know this has occurred before, but in our case, it is neither externals-only nor are there any parameters involved. Also, it is not restricted the first one. It doesn't happen every time, but about every second time. According to the SVN server's connection logs, Jenkins actually tries to connect to the SVN server without giving any credentials in those cases. Environment: Windows 7 Jenkins 1.565.2 Subversion Plugin 2.4.3 Project: Jenkins Labels: credentials Subversion Priority: Major Reporter: Jennifer Hofmeister This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-25149) svn: E200015: No credential to try - persistent
Jennifer Hofmeister updated JENKINS-25149 svn: E200015: No credential to try - persistent Change By: Jennifer Hofmeister (14/Oct/14 4:37 PM) Description: AfterupdatingJenkinsfrom1.551to1.565.2,ourjobsfail,moreoftenthannot,withtheSVNexceptionE200015:Nocredentialtotry.AuthenticationfailedIknowthishasoccurredbefore,butinourcase,itisneitherexternals-onlynorarethereanyparametersinvolved.Also,itisnotrestrictedthefirstone.Itdoesnthappeneverytime,butabouteverysecondtime.AccordingtotheSVNserversconnectionlogs,JenkinsactuallytriestoconnecttotheSVNserverwithoutgivinganycredentialsinthosecases. Mightberelatedtohttps://issues.jenkins-ci.org/browse/JENKINS-25147becausetthetwostartedoccurringatthesametime. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-25147) Cannot access pom.xml directory after Jenkins update
stephenconnolly updated JENKINS-25147 Cannot access pom.xml directory after Jenkins update This is absolutely nothing to do with the credentials plugin. Removing the credentials plugin label and component Change By: stephenconnolly (14/Oct/14 4:38 PM) Labels: credentials maven3 Assignee: stephenconnolly Component/s: credentials This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-25147) Cannot access pom.xml directory after Jenkins update
Jennifer Hofmeister updated JENKINS-25147 Cannot access pom.xml directory after Jenkins update Change By: Jennifer Hofmeister (14/Oct/14 4:39 PM) Component/s: credentials This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-25147) Cannot access pom.xml directory after Jenkins update
Jennifer Hofmeister updated JENKINS-25147 Cannot access pom.xml directory after Jenkins update Change By: Jennifer Hofmeister (14/Oct/14 4:39 PM) Description: AfterupdatingJenkinsfrom1.551to1.565.2,someofourMaven-typejobsfailwiththefollowingmessage:[INFO]Scanningforprojects...[ERROR]Thebuildcouldnotread1project-[Help1]org.apache.maven.project.ProjectBuildingException:SomeproblemswereencounteredwhileprocessingthePOMs:[FATAL]Non-readablePOMD:\Jenkins\Jobs\JobName\workspace\JobName-test:D:\Jenkins\Jobs\JobName\workspace\JobName-test(Accessisdenied)D:\...\JobName-testcontainsthepom.xml.IthappenswhenMaveniscalledthroughInvoketop-levelMaventargets.MavenVersion:(Default)Goals:verify-X-fD:\Jenkins\Jobs\JobName\workspace\JobName-test-Dparam1=abc-Dparam2=def-Dparam3=10TheJenkinsuseraccountonWindowshasallaccessrightsontheJenkinsdirectoriesandfiles.TheoddthingaboutthisisthatwehaveanothersetofMaven-typejobsthatrunjustfine,withthesamekindofbuildstep.Theonlydifferenceisthatthosearegeneratedfromatemplatejobwhilethefailingonesarenot.Allofthemworkedfinebeforetheupdate.Unfortunately,reconstructionofthiserrorissomewhatcomplicatedsincewehaveanissuewithJenkinsgivingnoSVNcredentialsthatsometimesabortsthebuildatanearlierpoint. ItalsooccurredaftertheJenkinsupdate (https://issues . jenkins-ci.org/browse/JENKINS-25149) I willopenanotherissueforthat,butI suspect thetwo they mightberelated becausetheJenkinsupdateseemstohavetriggeredthemboth . Itsa Labels: credentials maven3 Assignee: stephenconnolly Component/s: credentials This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-25066) Build on the same node option triggers runs on node with same label and not on identical node
Daniel Beck updated JENKINS-25066 Build on the same node option triggers runs on node with same label and not on identical node Config issue I think. I don't know whether there are legitimate use cases for giving one node's self label (i.e. node name) as regular label to another node, but it's really just asking for trouble, as this issue shows. Don't do that, and you should be fine. In the meantine reducing priority as the workaround is easy and obvious: Do not assign labels with the same name as a node to other nodes. Change By: Daniel Beck (14/Oct/14 4:51 PM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-25123) Configuration Slicing plugin 1.39 does not support build timeout plugin 1.12+
Daniel Beck updated JENKINS-25123 Configuration Slicing plugin 1.39 does not support build timeout plugin 1.12+ Change By: Daniel Beck (14/Oct/14 4:56 PM) Summary: ConfigurationSlicingplugin1.39doesnotsupportbuildtimeoutplugin1. 14 12+ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
Daniel Beck commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported the whole story Jetty replaced Winstone as embedded container in 1.535. (CLI and some messages were kept, so it still appears to be winstone, but it's not). So while they're supposed to behave similar, it should be no surprise that details are handled differently. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jiratestresultreporter] (JENKINS-25140) JiraTestResultReporter.JiraReporter aborted due to exception error.
Daniel Beck commented on JENKINS-25140 JiraTestResultReporter.JiraReporter aborted due to exception error. Plugin just needs a new release, has been fixed for months. https://github.com/jenkinsci/JiraTestResultReporter-plugin/commit/cece0846a08203e3fdb8212c574ba11160e3a4a3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jiratestresultreporter] (JENKINS-25140) JiraTestResultReporter.JiraReporter aborted due to exception error.
Daniel Beck commented on JENKINS-25140 JiraTestResultReporter.JiraReporter aborted due to exception error. Workaround: Build and install a snapshot of the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-results-analyzer] (JENKINS-25150) No longer generating XCTest reports with XCode 6
Danny Pier created JENKINS-25150 No longer generating XCTest reports with XCode 6 Issue Type: Bug Assignee: Varun Menon Components: test-results-analyzer, testexecuter, xcode Created: 14/Oct/14 5:17 PM Description: JUnit test reports are no longer generated for XCTest results with no clear indication of where the failure lies. Unit tests are run with the custom build argument of "test" and the results are printed out correctly in the console logs, but not parsed, as far as I can tell, and placed in the test-reports directory. Environment: Jenkins 1.5.6 running 1.4.2 version of xcodeplugin Project: Jenkins Priority: Major Reporter: Danny Pier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25142) The view style loss when there are many view tabs
Daniel Beck commented on JENKINS-25142 The view style loss when there are many view tabs Does it look correct with fewer views on newer Jenkins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25142) The view style loss when there are many view tabs
Daniel Beck updated JENKINS-25142 The view style loss when there are many view tabs Change By: Daniel Beck (14/Oct/14 5:33 PM) Labels: user-experience Component/s: core Component/s: view-job-filters This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25142) The view style loss when there are many view tabs
Daniel Beck updated JENKINS-25142 The view style loss when there are many view tabs How is this possibly a Major issue? (It's not.) Change By: Daniel Beck (14/Oct/14 5:36 PM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25142) The view style loss when there are many view tabs
Daniel Beck commented on JENKINS-25142 The view style loss when there are many view tabs What web browser are you using? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25142) The view style loss when there are many view tabs
Tom FENNELLY commented on JENKINS-25142 The view style loss when there are many view tabs Yes, as Daniel says please provide some screenshots with just a few extra tabs. Also can you test this on the very latest Jenkins and verify that it is the same please. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory] (JENKINS-25151) access denied errors encountered downloading repo artifacts in multi-configuration jobs
R. Tyler Croy moved JENKINS-25151 access denied errors encountered downloading repo artifacts in multi-configuration jobs Change By: R. Tyler Croy (14/Oct/14 5:45 PM) Project: Infrastructure Jenkins Key: INFRA JENKINS - 182 25151 Workflow: jira JNJira Component/s: artifactory Component/s: artifactory This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25146) When the anonymous user has no access rights, userContent is inaccessible
Daniel Beck commented on JENKINS-25146 When the anonymous user has no access rights, userContent is inaccessible This looks like a legitimate issue. Reproduced on 1.584 using project-based matrix permissions and Jenkins user database. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory] (JENKINS-25151) access denied errors encountered downloading repo artifacts in multi-configuration jobs
Daniel Beck commented on JENKINS-25151 access denied errors encountered downloading repo artifacts in multi-configuration jobs Are you using Artifactory Plugin for Jenkins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-25149) svn: E200015: No credential to try - persistent
Daniel Beck commented on JENKINS-25149 svn: E200015: No credential to try - persistent Report needs logging output. Create a log recorder in /log, add a bunch of SVN related loggers and set them to '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] [maven-plugin] (JENKINS-25147) Cannot access pom.xml directory after Jenkins update
Daniel Beck commented on JENKINS-25147 Cannot access pom.xml directory after Jenkins update Do these other jobs run on the same slave? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
