[JIRA] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
Christian Galsterer reopened JENKINS-17742 Pick Up Committer from Upstream Job Change By: Christian Galsterer (24/Dec/13 8:16 AM) Resolution: WontFix Status: Resolved Reopened Assignee: AlexEarl ChristianGalsterer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
Christian Galsterer commented on JENKINS-17742 Pick Up Committer from Upstream Job I implemented a change which is available in pull request https://github.com/jenkinsci/email-ext-plugin/pull/83. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-21140) TF tool respects TFSPROXY environment variable but SDK does not.
Calvin Mann created JENKINS-21140 TF tool respects TFSPROXY environment variable but SDK does not. Issue Type: Bug Affects Versions: current Assignee: redsolo Components: tfs Created: 24/Dec/13 9:21 AM Description: When using the plugin behind a proxy, and specifying the proxy with the TFSPROXY environment variable, the plugin is able to start the process (using the tf script), then fails when it attempts to use the TFS SDK (Unable to connect). Environment: Windows Project: Jenkins Priority: Major Reporter: Calvin Mann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-21141) Error in jelly template file for UnclaimedIdentityException error message
Stanislav Panyushkin
created JENKINS-21141
Error in jelly template file for UnclaimedIdentityException error message
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
screenshot.jpg
Components:
security
Created:
24/Dec/13 9:38 AM
Description:
In file jenkins\core\src\main\resources\hudson\security\FederatedLoginService\UnclaimedIdentityException\error.jelly:
must be
l:layout title="${%loginError(it.identity.pronoun)}"
instead of
l:layout title="${%loginError(it.identifier.pronoun)}"
and
l:main-panel
h1${%loginError(it.identity.pronoun)}/h1
p${%blurb(it.identity.pronoun, it.identity.identifier)}/p
/l:main-panel
instead of
l:main-panel
h1${%loginError(it.identifier.pronoun)}/h1
p${%blurb(it.identifier.pronoun, it.identifier.identifier)}/p
/l:main-panel
Project:
Jenkins
Labels:
exception
security
gui
Priority:
Minor
Reporter:
Stanislav Panyushkin
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18676) Allow CommandInterpreters to set build status based on script result
benoit guerin commented on JENKINS-18676 Allow CommandInterpreters to set build status based on script result Maybe a solution : https://github.com/jenkinsci/jenkins/pull/1079 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cucumber-perf] (JENKINS-19888) NPE when running plugin
Jim Gallagher commented on JENKINS-19888 NPE when running plugin Hi Teilo I don't know your JSON file, as you never supplied it. The one from Mathias did seem to contain malformed objects. If you'd care to supply the JSON output file and your input feature file, I'll re-open the issue and re-examine it. I did ask you to do this back in October. Jim This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg commented on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Thanks Oleg. I can't dump it because it's to big (40GB) and for some reason the "jmap" unable to connect to the Jenkins process. Anyway I downgraded the version to 1.537... Oleg, If you have a system with 600 jobs with high activities + 40 slave machines online and you don't have this issue it's very strange because I test these versions on several different machines and each time the problem reproduced (after 12-24 hours). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Oleg Nenashev commented on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Probably, we have different job contents/plugins (e.g. we don't use Maven plugin; xUnit components are not popular due to integration with external systems). Could you provide a list of your plugins? Since we know about stable/unstable versions, we can try to find an interoperability issue if it exists. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21143) Timezone override by user
Vitold S created JENKINS-21143 Timezone override by user Issue Type: Improvement Assignee: Unassigned Components: core Created: 24/Dec/13 1:21 PM Description: Sometimes the assumption that the current time zone of the interface can lead to serious errors. Good to be able to use for the user override the default time zone. Environment: Ubuntu/12 Project: Jenkins Priority: Major Reporter: Vitold S This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-14378) Email-ext plugin failed to install
Alex Earl commented on JENKINS-14378 Email-ext plugin failed to install Did you try restarting 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/groups/opt_out.
[JIRA] [maven] (JENKINS-21144) Is there any way to disable/prevent use of the built-in maven job types?
Nathan Neulinger created JENKINS-21144 Is there any way to disable/prevent use of the built-in maven job types? Issue Type: New Feature Assignee: Unassigned Components: maven Created: 24/Dec/13 1:50 PM Description: We have a problem where some developers try to use the maven job type instead of just invocing maven on command line. Unfortunately, this results in over 600 job records being defined for every invocation of this particular job, which basically brings Jenkins server to a crawl with multi-minute hangs/etc. Since developers won't properly communicate - is there any way to effectively just disable this job type? Project: Jenkins Priority: Major Reporter: Nathan Neulinger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg commented on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Oleg, I sent you email with our Jenkins Plugins list. Thank You This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-20556) Build with lots of parameterized tests makes Jenkins hang
Julien Nicoulaud commented on JENKINS-20556 Build with lots of parameterized tests makes Jenkins hang Unfortunately, I can not provide the file as it contains sensitive data. However, in the meanwhile I realized it works fine with lots of parameterized tests, the slowdown happens when a parameterized tests with lots of combinations is skipped. So I guess the steps to reproduce are: Create a test class with a single test method Make it parameterized with 10 combinations Make it throw a SkipException This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-21094) NullPointerException at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:178)
Stefan Zwanenburg commented on JENKINS-21094 NullPointerException at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:178) I can confirm. I get the same exception on Jenkins v1.534, with xUnit v1.65 AND v1.67. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20879) SSH Credentials do not work to connect to private GitHub repository
Richard van der Hoff commented on JENKINS-20879 SSH Credentials do not work to connect to private GitHub repository My impression is that the git plugin doesn't work with ssh keys which have a non-empty passphrase. Can you confirm if it works ok on a key with an empty passphrase? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21145) Several concurrent builds waits for each other
Vitaliy Baskoff updated JENKINS-21145 Several concurrent builds waits for each other Change By: Vitaliy Baskoff (24/Dec/13 4:35 PM) Environment: Gentoo Jenkins1.532.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/groups/opt_out.
[JIRA] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald commented on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in I upgraded another Jenkins server to 1.544. It now gets the same : org.apache.commons.jelly.JellyTagException. This other server is using Active Directory authentication with Project-based Matrix Authorization Strategy. This issue is not reportedly occuring with LDAP authentication with Project-based Matrix Authorization Strategy, Active Directory authentication with Project-based Matrix Authorization Strategy, and Unix user/group database athentciation with Project-based Matrix Authorization Strategy. Seems pretty clear the root cause is not related to an authentication strategy, and probably via use of "Project-based Matrix Authorization Strategy." IN both my server experiencing this bug, giving Admin credentials to people (either individually or through authenticated group, or via anonymous user) all allows them to login without error. This problem defintatley happened for us, immediatley after upgrading to 1.544. (along with a slew of plugins) We upgraded from 1.517 to 1.5444. Incidentally, rolling back just jenkins.war to 1.517 did not cause the problem to go away (although the presentiation of the stack trace screen was slightly different) which seems to indicate one of the plugin upgraded is the culprit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald edited a comment on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in I upgraded another Jenkins server to 1.544. It now gets the same : org.apache.commons.jelly.JellyTagException. This other server is using Active Directory authentication with Project-based Matrix Authorization Strategy. This issue is now reportedly occuring with LDAP authentication with Project-based Matrix Authorization Strategy, Active Directory authentication with Project-based Matrix Authorization Strategy, and Unix user/group database athentciation with Project-based Matrix Authorization Strategy. Seems pretty clear the root cause is not related to an authentication strategy, and probably via use of "Project-based Matrix Authorization Strategy." IN both my server experiencing this bug, giving Admin credentials to people (either individually or through authenticated group, or via anonymous user) all allows them to login without error. This problem defintatley happened for us, immediatley after upgrading to 1.544. (along with a slew of plugins) We upgraded from 1.517 to 1.5444. Incidentally, rolling back just jenkins.war to 1.517 did not cause the problem to go away (although the presentiation of the stack trace screen was slightly different) which seems to indicate one of the plugin upgraded is the culprit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald edited a comment on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in I upgraded another Jenkins server to 1.544. It now gets the same : org.apache.commons.jelly.JellyTagException. This other server is using Active Directory authentication with Project-based Matrix Authorization Strategy. This issue is now reportedly occuring with LDAP authentication with Project-based Matrix Authorization Strategy, Active Directory authentication with Project-based Matrix Authorization Strategy, and Unix user/group database athentciation with Project-based Matrix Authorization Strategy. Seems pretty clear the root cause is not related to an authentication strategy, and probably via use of "Project-based Matrix Authorization Strategy." In both my servers experiencing this bug, giving Admin credentials to people (either individually or through authenticated group, or via anonymous user) all allows them to login without error. This problem defintitley happened for us, immediately after upgrading to 1.544. (along with a slew of plugins) We upgraded from 1.517 to 1.5444. Incidentally, rolling back just jenkins.war to 1.517 did not cause the problem to go away (although the presentation of the stack trace screen was slightly different) which seems to indicate one of the plugin upgraded is the culprit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald edited a comment on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in I tried roling back PAM Authentcation plugin from 1.1 to 1.0. It did not resolve the issue. I noticed that there is a plugin called "Matrix Authorization Strategy Plugin" currently installed at 1.1. At least on my server, This plugin can not be downgraded nor uninstalled. According to plugin page it says this plugin "Split from Jenkins core" in Oct, and a recent upgrade 1.1., released in Nov 11th, 2013, contains improvements for "Using an extension point in Jenkins 1.535." and "Better diagnosis for a form-related error" 1.353 went out Oct 14th. THis look to be promising as the timing of either the timing ""Split from Jenkins core" in Oct, or the "Matrix Authorization Strategy Plugin" would fit the timing of when we saw this issue. Inceidently, we did try moving from "project based matrix" to "Matrix-based" and the issue was not resolved. (I am unsure if oth "project-based matrix", and "matrix" are both manifested in "Matrix Authorization Strategy Plugin" At this point, seems they probably are. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald commented on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in I tried roling back PAM Authentcation plugin from 1.1 to 1.0. It did nto resolve the issue. I noticed that ther eis a plugin called "Matrix Authorization Strategy Plugin" currently installed at 1.1. At least on my server, This plugin can not be downgraded nor uninstalled. According to plugin page it says this plugin "Split from Jenkins core" in Oct, and a recent upgrade 1.1., released in Nov 11th, 2013, contains improvements for "Using an extension point in Jenkins 1.535." and "Better diagnosis for a form-related error" 1.353 went out Oct 14th. THis look to be promising as the timing of either the timing ""Split from Jenkins core" in Oct, or the "Matrix Authorization Strategy Plugin" would fit the timing of when we saw this issue. Inceidently, we did try moving from "project based matrix" to "Matrix-based" and the issue was not resolved. (I am unsure if oth "project-based matrix", and "matrix" are both manifested in "Matrix Authorization Strategy Plugin" At this point, seems they probably are. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald edited a comment on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in I tried roling back PAM Authentcation plugin from 1.1 to 1.0. It did not resolve the issue. I noticed that ther eis a plugin called "Matrix Authorization Strategy Plugin" currently installed at 1.1. At least on my server, This plugin can not be downgraded nor uninstalled. According to plugin page it says this plugin "Split from Jenkins core" in Oct, and a recent upgrade 1.1., released in Nov 11th, 2013, contains improvements for "Using an extension point in Jenkins 1.535." and "Better diagnosis for a form-related error" 1.353 went out Oct 14th. THis look to be promising as the timing of either the timing ""Split from Jenkins core" in Oct, or the "Matrix Authorization Strategy Plugin" would fit the timing of when we saw this issue. Inceidently, we did try moving from "project based matrix" to "Matrix-based" and the issue was not resolved. (I am unsure if oth "project-based matrix", and "matrix" are both manifested in "Matrix Authorization Strategy Plugin" At this point, seems they probably are. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald commented on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in Given the timing of our upgrades and the recent changes in the 1.1 Matrix Authorization Strategy Plugin, I loved to downgrade to 1.0 and see what happens. I tried copying the matrix-auth.hpi to jenkins plugin dir and restarting jenkins, but the plugin remained at 1.1. I never manually downgraded a plugin before, but copying the hip seems to be the totality of instructions I can find. Anyone know why the plugin is not downgrading when simply copying the older .hpi file to the plugins directory? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald edited a comment on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in I tried roling back PAM Authentcation plugin from 1.1 to 1.0. It did not resolve the issue. I noticed that there is a plugin called "Matrix Authorization Strategy Plugin" currently installed at 1.1. At least on my server, This plugin can not be downgraded nor uninstalled. According to plugin page it says this plugin "Split from Jenkins core" in Oct, and a recent upgrade 1.1., released in Nov 11th, 2013, contains improvements for "Using an extension point in Jenkins 1.535." and "Better diagnosis for a form-related error" 1.535 went out Oct 14th. This look to be promising as the timing of either the timing ""Split from Jenkins core" in Oct, or the "Matrix Authorization Strategy Plugin" would fit the timing of when we saw this issue. Incidentally, we did try moving from "project based matrix" to "Matrix-based" and the issue was not resolved. (I am unsure if oth "project-based matrix", and "matrix" are both manifested in "Matrix Authorization Strategy Plugin" At this point, seems they probably are. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald edited a comment on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in Given the timing of our upgrades and the recent changes in the 1.1 Matrix Authorization Strategy Plugin, I'd love to downgrade to 1.0 and see what happens. I tried copying the matrix-auth.hpi to jenkins plugin dir and restarting jenkins, but the plugin remained at 1.1. I never manually downgraded a plugin before, but copying the .hpi seems to be the totality of instructions I can find. Anyone know why the plugin is not downgrading when simply copying the older .hpi file to the plugins directory and restarting 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/groups/opt_out.
[JIRA] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald edited a comment on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in I tried roling back PAM Authentcation plugin from 1.1 to 1.0. It did not resolve the issue. I noticed that there is a plugin called "Matrix Authorization Strategy Plugin" currently installed at 1.1. At least on my server, This plugin can not be downgraded nor uninstalled. According to plugin page it says this plugin "Split from Jenkins core" in Oct, and a recent upgrade 1.1., released in Nov 11th, 2013, contains improvements for "Using an extension point in Jenkins 1.535." and "Better diagnosis for a form-related error" 1.535 went out Oct 14th. This look to be promising as the timing of either the "Split from Jenkins core" in Oct, or the "Matrix Authorization Strategy Plugin" would fit the timing of when we upgraded an saw this issue. Incidentally, we did try moving from "project based matrix" to "Matrix-based" and the issue was not resolved. I am unsure if "project-based matrix", and "matrix" are both manifested in "Matrix Authorization Strategy Plugin". At this point, seems they probably are. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18179) Allow Build Hiding in Build History
martin naughton commented on JENKINS-18179 Allow Build Hiding in Build History based on regex or build stability or limit build history number? Your requirement can interpreted different ways. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18179) Allow Build Hiding in Build History
martin naughton edited a comment on JENKINS-18179 Allow Build Hiding in Build History based on regex or build stability or limit build history number? Your requirement can interpreted different ways. Code to be changed in the build history widget This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18179) Allow Build Hiding in Build History
martin naughton edited a comment on JENKINS-18179 Allow Build Hiding in Build History based on regex or build stability or limit build history number? Your requirement can interpreted different ways. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18179) Allow Build Hiding in Build History
martin naughton assigned JENKINS-18179 to martin naughton Allow Build Hiding in Build History Change By: martin naughton (24/Dec/13 11:54 PM) Assignee: martinnaughton This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18179) Allow Build Hiding in Build History
martin naughton commented on JENKINS-18179 Allow Build Hiding in Build History Code to be changed in the build history widget. Idea would be to pass the build history limit number to the widget. Limit could be stored in the project 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21124) Use proxy to access git repository
ping he updated JENKINS-21124 Use proxy to access git repository Change By: ping he (25/Dec/13 12:23 AM) Priority: Blocker Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17589) show project type somewhere
martin naughton
commented on JENKINS-17589
show project type somewhere
Actually the information is not saved any where. Checked all the files in jenkins build information. Nothing shows up with a find command.
find . -exec grep -Hn free-style {} \;
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17589) show project type somewhere
martin naughton assigned JENKINS-17589 to martin naughton show project type somewhere Change By: martin naughton (25/Dec/13 12:34 AM) Assignee: martinnaughton This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17589) show project type somewhere
martin naughton commented on JENKINS-17589 show project type somewhere information could be stored in the config.xml file for the project. It could then appear in project configuration and project status page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14967) When creating a New Job and using the Copy existing Job the Display Name under Advanced Project Options is not populated.
martin naughton commented on JENKINS-14967 When creating a New Job and using the Copy existing Job the Display Name under Advanced Project Options is not populated. any update? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20662) When triggering a new build from current build page, 'Next Build' isn't shown after reloading page
Daniel Beck commented on JENKINS-20662 When triggering a new build from current build page, Next Build isnt shown after reloading page Reproduced every time on newly created Jenkins instances with empty Jenkins home. Just now verified in 1.544. Auto enable is disabled (which is the default anyway I believe). It takes until the build is finished, or the /job/foo page is reloaded until the build shows up as 'Next Build' on the previously completed build's page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20662) When triggering a new build from current build page, 'Next Build' isn't shown after reloading page
Daniel Beck edited a comment on JENKINS-20662 When triggering a new build from current build page, Next Build isnt shown after reloading page Reproduced every time on newly created Jenkins instances with empty Jenkins home. Just now verified in 1.544. Auto enable is disabled (which is the default anyway I believe). It takes until the build is finished, or the /job/foo page is reloaded, for the build to show up as 'Next Build' on the previously completed build's page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20662) When triggering a new build from current build page, 'Next Build' isn't shown after reloading page
Daniel Beck commented on JENKINS-20662 When triggering a new build from current build page, Next Build isnt shown after reloading page Weirdly enough, an existing instance (RHEL Linux, OpenJDK 1.6, Jenkins installed as service) is not affected by this. So far, all systems I reproduced this with seem to have been OS X 10.8.6 with Oracle Java 1.7, Jenkins launched from the command line using java -jar jenkins.war. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20666) master node config not changed from Utilize this slave as much as possible to leave this setting to tied job only
hiteswar kumar commented on JENKINS-20666 master node config not changed from Utilize this slave as much as possible to leave this setting to tied job only Hi Martin. thanks for your comment. i am using LTS version 1.480.3 and config.xm file even having EXCLUSIVE MODE modeEXCLUSIVE/mode then also UI page showing "utilize this slave as much as possible" but as per you. UI should show "leave for tied jobs" for EXCLUSIVE mode. please share your comments. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-21147) Elimiate race condition so plugin can support more than 1 cloud configuration
Igor Okulist created JENKINS-21147 Elimiate race condition so plugin can support more than 1 cloud configuration Issue Type: Bug Affects Versions: current Assignee: Francis Upton Components: ec2 Created: 25/Dec/13 6:17 AM Description: If more than 1 ec2/eucalyptus clouds configured then jenkins start picking configuration options from a random one. Solution seems to cherry pick a commit from prior pull request. A new pull request is here: https://github.com/jenkinsci/ec2-plugin/pull/74 Due Date: 27/Dec/13 12:00 AM Project: Jenkins Priority: Major Reporter: Igor Okulist This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-21147) Elimiate race condition so plugin can support more than 1 cloud configuration
Igor Okulist updated JENKINS-21147 Elimiate race condition so plugin can support more than 1 cloud configuration Change By: Igor Okulist (25/Dec/13 6:17 AM) Priority: Major 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/groups/opt_out.
[JIRA] [core] (JENKINS-20662) When triggering a new build from current build page, 'Next Build' isn't shown after reloading page
martin naughton commented on JENKINS-20662 When triggering a new build from current build page, Next Build isnt shown after reloading page any update? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20666) master node config not changed from Utilize this slave as much as possible to leave this setting to tied job only
martin naughton commented on JENKINS-20666 master node config not changed from Utilize this slave as much as possible to leave this setting to tied job only Duplicate bug report. Already ran the test and it worked for me. Have you check the config file has been changed? https://issues.jenkins-ci.org/browse/JENKINS-15875 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20666) master node config not changed from Utilize this slave as much as possible to leave this setting to tied job only
martin naughton edited a comment on JENKINS-20666 master node config not changed from Utilize this slave as much as possible to leave this setting to tied job only Duplicate bug report. Already ran the test and it worked for me. Have you check the config file has been changed when you save the change. Check the other issue comments. https://issues.jenkins-ci.org/browse/JENKINS-15875 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21145) Several concurrent builds waits for each other
Vitaliy Baskoff updated JENKINS-21145 Several concurrent builds waits for each other Change By: Vitaliy Baskoff (25/Dec/13 7:44 AM) Description: Hi,Wehaveanupstreamproject(withconfigurationmatrix)which tigers trigers downstreamone.DownstreamprojecthasThrottleConcurrentBuilds tick option enabledwithThrottlethisprojectalone,MaximumTotalConcurrentBuilds=2,MaximumConcurrentBuildsPer Nod Node =2BothupstreamanddownstreamprojectshavexUnitrelatedstepsinPost-buildActionsIssuethereiswhenwehavetriggered10concurrentbuilds(#100-#109)ofthedownstreamprojectandthethirdone(#102)requiresmoretimetofinish-allfurtherbuilds(#103-#109)willbelockeduntilthisthirdbuildfinish.Otherexample,whentwobuildstherewereexecutingsimultaneously,oneofthemfailedandtooklongtimetofinish.Itlookslikesuccessfulonewaswaitingforunsuccessfulone.Justcompareendoflogsforthesepairsoftests : . https Payattentionontimestamps : // gapbetweenStoppingrecordingandSendinge-mails: jenkins/view/QA/job/_SIP/job/pjsip_c/2900/console https:// jenkins/view/QA/job/_SIP/job/pjsip_c/2901/console11:07:30[xUnit][INFO]-Startingtorecord.11:07:30[xUnit][INFO]-ProcessingJUnit11:07:30[xUnit][INFO]-[JUnit]-3testreportfile(s)werefoundwiththepatternresults-pjsip/*.xmlrelativeto/tmp/workspace/_SIP/pjsip_cforthetestingframeworkJUnit.11:07:35[xUnit][INFO]-CheckFailedTeststhreshold.11:07:35[xUnit][INFO]-Thetotalnumberoftestsforthiscategoryexceedsthespecifiedfailurethresholdvalue.11:07:35[xUnit][INFO]-SettingthebuildstatustoFAILURE11:07:35[xUnit][INFO]-Stoppingrecording.11:07:35BuildstepPublishxUnittestresultreportchangedbuildresulttoFAILURE11:07:35Sendinge-mailsto:11:08:05Notifyingupstreamprojectsofjobcompletion11:08:05Joinnotifiercannotfindupstreamproject:_SIP/pjsip_cron/VM=etsys,Version=39011:08:05Finished:FAILUREVS10:56:40[xUnit][INFO]-SettingthebuildstatustoSUCCESS10:56:40[xUnit][INFO]-Stoppingrecording.11:07:34Sendinge-mailsto:11:08:04Notifyingupstreamprojectsofjobcompletion11:08:04Joinnotifiercannotfindupstreamproject:_SIP/pjsip_cron/VM=etsys_ora,Version=38011:08:04Finished:SUCCESSAnd: https:// jenkins/view/QA/job/_SIP/job/pjsip_c/2904/console https:// jenkins/view/QA/job/_SIP/job/pjsip_c/2905/console10:34:52[xUnit][INFO]-Startingtorecord.10:34:52[xUnit][INFO]-ProcessingJUnit10:34:53[xUnit][INFO]-[JUnit]-3testreportfile(s)werefoundwiththepatternresults-pjsip/*.xmlrelativeto/tmp/workspace/_SIP/pjsip_cforthetestingframeworkJUnit.10:34:57[xUnit][INFO]-CheckFailedTeststhreshold.10:34:57[xUnit][INFO]-Thetotalnumberoftestsforthiscategoryexceedsthespecifiedfailurethresholdvalue.10:34:57[xUnit][INFO]-SettingthebuildstatustoFAILURE10:34:57[xUnit][INFO]-Stoppingrecording.10:34:57BuildstepPublishxUnittestresultreportchangedbuildresulttoFAILURE10:34:57Sendinge-mailsto:10:35:36Notifyingupstreamprojectsofjobcompletion10:35:36Joinnotifiercannotfindupstreamproject:_SIP/pjsip_cron/VM=etsys_ora,Version=39010:35:36Finished:FAILUREVS10:21:28[xUnit][INFO]-SettingthebuildstatustoSUCCESS10:21:28[xUnit][INFO]-Stoppingrecording.10:34:57Sendinge-mailsto:10:35:31Notifyingupstreamprojectsofjobcompletion10:35:31Joinnotifiercannotfindupstreamproject:_SIP/pjsip_cron/VM=etsys,Version=37110:35:31Finished:SUCCESSCouldyou promptus pleaseadvise how toovercome wecanworkaround thisissue ? . Anyhelpisappreciated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
