[JIRA] [maven-plugin] (JENKINS-20594) Expose parsed maven project version
Title: Message Title
Scott MacDonald edited a comment on JENKINS-20594
Re: Expose parsed maven project version
{POM_VERSION_MAJOR}.${POM_VERSION_MINOR}.${revision} is super helpful in CD, especially when using SEMVER which embeds compatibility into the version identifier based on the scope of compatibility of the work. This allows the pom to contain the software SEMVER version and be a source controlled asset completely specified by the developer making the change (whose knows whether the change is compatible or not) , while allowing CD to simply add on a unique increment# to the existing checked in major.minor to indicate a compatible increment of the developer specified major.minor compatible SEMVER version checked into the pom.xml.mvn version:set -DnewVersion=${POM_VERSION_MAJOR}.${POM_VERSION_MINOR}.${BUILD_NUMBER} with the pom be something like 1.0.${revision} where the major.minor is controlled via checkin by the developer making the compatible or incompatible change,and increment is pulled from CD (like git commit or jenkins build#)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-20594) Expose parsed maven project version
Title: Message Title
Scott MacDonald commented on JENKINS-20594
Re: Expose parsed maven project version
{POM_VERSION_MAJOR}.${POM_VERSION_MINOR}.${revision} is super helpful in CD, especially when using SEMVER which embeds compatibility into the version identifier based on the scope of compatibility of the work. This allows the pom to contain the software SEMVER version and be a source controlled asset completely specified by the developer making the change (whose knows whether the change is compatible or not) , while allowing CD to simply add on a unique increment# to the existing checked in major.minor indicate a compatible increment the developer specified major.minor compatible SEMVER version checked into the pom.xml. mvn version:set -DnewVersion=${POM_VERSION_MAJOR}
.$ {POM_VERSION_MINOR}
.$ {BUILD_NUMBER}
with the pom be something like 1.0.$ {revision}
where the major.minor is controlled via checkin by the developer making the compatible or incompatible change,and increment is pulled from CD (like git commit or jenkins build#)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-24869) POM_VERSION is not resetted
Title: Message Title Scott MacDonald commented on JENKINS-24869 Re: POM_VERSION is not resetted Also seeing this issue trying to drive versioning for CD via jenkins in Jenkins 1.609.3 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-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-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 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 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 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 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 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 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 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 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 commented on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in Still an issue in 1.5444 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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 have "Unix user/group database" authentication with Service "sshd". The "test" button reports success, and changing the service to ssh or sshd makes no difference. We use "Project-based Matrix Authorization Strategy" and do not provide "anonymous" users any access, provide "authenticated" users read acess, and typically a few select users get "admin". At the moment, we have resorted to giving everyone full admin, as that appears to o be the the only way to allow folks to use the system (a very temporary workaround) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-19870) Status of the existing pipeline job is not updated after a failure or aborted build. Downstream job trigger is not enabled after the build succeeds
Scott MacDonald commented on JENKINS-19870 Status of the existing pipeline job is not updated after a failure or aborted build. Downstream job trigger is not enabled after the build succeeds Same issue on Jenkins 1.543 Pipeline 1.4.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/groups/opt_out.
[JIRA] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald updated JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in Change By: Scott MacDonald (12/Dec/13 6:27 PM) Component/s: core Component/s: other This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [other] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald commented on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in Similiar stack trace reported with JENKINS-15499 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [other] (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 Similiar stack trace reported with JENKINS-15499 though in our case, users get the stack trace at login preventing them from logging in. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [other] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald updated JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in Change By: Scott MacDonald (12/Dec/13 6:09 PM) Component/s: other Component/s: jenkins-tracker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [jenkins-tracker] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald created JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in Issue Type: Bug Assignee: Unassigned Components: jenkins-tracker Created: 12/Dec/13 5:26 PM Description: After specifying credentials on the login page, all non-admin users are presented with an Error page containing the following stack trace. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-0.0.0.0-8080-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.543.jar!/hudson/model/View/index.jelly:42:43: org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-0.0.0.0-8080-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.543.jar!/lib/hudson/projectView.jelly:66:22: java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.secur
[JIRA] [pam-auth] (JENKINS-18736) PAM authertication over NIS server does not work
Scott MacDonald commented on JENKINS-18736 PAM authertication over NIS server does not work I do not want to run as root if I don't have to. We had been running our jenkins server as "jenkins" user for 6+ months with "Unix user/group database" PAM based authentication. This broke on us following a reboot after installing a plugin. I just don;t see how running as root can be considered requirement, when it clearly wasn't the case for us over the last 6 months. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [pam-auth] (JENKINS-18736) PAM authertication over NIS server does not work
Scott MacDonald commented on JENKINS-18736 PAM authertication over NIS server does not work Still scowering the net for a solutiojn..not much out there.Found this old, failry definiative blog post from 2009.. Jon Schewe wrote: > Yes, this is the case if you have shadow passwords, which most people > do. You can either run hudson as root or give access to /etc/shadow to a > group, perhaps called 'shadow', and then add the hudson user to that > group. Then it'll work. > > Kohsuke Kawaguchi wrote: >> I've heard from some users that PAM auth can only authenticate the user >> that Hudson is running as, unless Hudson is run as root. >> ## So if I change jenkins to run as root, authentication does indeed work (although I see other breakages launching slaves due which I would now have to sort out) Considering that I have been running for 6 months as jenkins without any problems, I having a hard time buying that running as root is a hard requirement PAM auth. At least it has not been true for us for about 6 months. There's got to be something else going on. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [pam-auth] (JENKINS-18736) PAM authertication over NIS server does not work
Scott MacDonald edited a comment on JENKINS-18736 PAM authertication over NIS server does not work I am seeing them same problem after everything was working properly for months. We starting seeing this issue yesterday immediately following a reboot to install EnvInject PLugin(which is now uninstalled, without fixing the error) We originally had "Unix user/group database" configured with "Service sshd" and "jenkins" user was NOT part of linux group "shadow". We have tried changing "service" to "ssh"(now back to "sshd") and have added jenkins user to linux group "shadow" Nothing has had any affect. The linux credentials are indeed valid, and we can ssh directly to the box without any problem. OS is Ubuntu 12.04.2 LTS We really need authentication working, so any help is GREATLY appreciated. Nov 27, 2013 5:32:27 PM hudson.security.AuthenticationProcessingFilter2 onUnsuccessfulAuthentication INFO: Login attempt failed org.acegisecurity.BadCredentialsException: pam_authenticate failed : Authentication failure; nested exception is org.jvnet.libpam.PAMException: pam_authenticate failed : Authentication failure at hudson.security.PAMSecurityRealm.authenticate(PAMSecurityRealm.java:78) at hudson.security.AbstractPasswordBasedSecurityRealm$Authenticator.retrieveUser(AbstractPasswordBasedSecurityRealm.java:135) at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122) at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200) at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47) at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.j
[JIRA] [pam-auth] (JENKINS-18736) PAM authertication over NIS server does not work
Scott MacDonald commented on JENKINS-18736 PAM authertication over NIS server does not work I am seeing them same problem after everything was working properly for months. We starting seeing this issue yesterday immediately following a reboot to install EnvInject PLugin(which is now uninstalled, without fixing the error) We originally had "Unix user/group database" configured with "Service sshd" and "jenkins" user was NOT part of linux group "shadow". We have tried changing "service" to "ssh"(no back to "sshd") and have added jenkins user to linux group "shadow" Nothing has had any affect. The linux credentials are indeed valid, and we can ssh directly to the box without any problem. OS is Ubuntu 12.04.2 LTS We really need authentication working, so any help is GREATLY appreciated. Nov 27, 2013 5:32:27 PM hudson.security.AuthenticationProcessingFilter2 onUnsuccessfulAuthentication INFO: Login attempt failed org.acegisecurity.BadCredentialsException: pam_authenticate failed : Authentication failure; nested exception is org.jvnet.libpam.PAMException: pam_authenticate failed : Authentication failure at hudson.security.PAMSecurityRealm.authenticate(PAMSecurityRealm.java:78) at hudson.security.AbstractPasswordBasedSecurityRealm$Authenticator.retrieveUser(AbstractPasswordBasedSecurityRealm.java:135) at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122) at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200) at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47) at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.h
[JIRA] [deploy] (JENKINS-18991) Unable to access debian package 1.525 using apt-get or browse http://pkg.jenkins-ci.org/debian fails
Scott MacDonald commented on JENKINS-18991 Unable to access debian package 1.525 using apt-get or browse http://pkg.jenkins-ci.org/debian fails Doesn;t appear anyone can install jenkins via apt-get or dbpk at all, any version. apt-get install jenkins=1.525 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libjna-java libcommons-jxpath-java libmaven-dependency-tree-java libjaxp1.3-java junit4 gcj-4.6-jre-lib libmaven-plugin-testing-java libplexus-archiver-java librhino-java libplexus-containers-java python-twisted-mail libwagon-java libmodello-java gcj-4.6-base libxerces2-java libavalon-framework-java libgcj-bc libplexus-classworlds-java libmaven2-core-java libhttpclient-java libjffi-jni libcommons-beanutils-java libxalan2-java libcommons-jexl-java libjnr-posix-java python-twisted-lore junit libplexus-cipher-java libconstantine-java python-twisted-news bsh-gcj libplexus-build-api-java libplexus-i18n-java libplexus-interactivity-api-java libjenkins-remoting-java python-twisted-conch python-twisted-words libcommons-cli-java java-wrappers libmaven-common-artifact-filters-java libcommons-logging-java jenkins-cli python-twisted libxbean-java libcommons-net2-java libmaven-enforcer-plugin-java libsaxon-java libgcj12 libitext1-java libplexus-ant-factory-java ant libplexus-container-default-java libjsch-java bsh libeasymock-java libxml-commons-resolver1.1-java ant-optional fop python-txzookeeper libbsf-java libapache-pom-java libplexus-io-java libplexus-bsh-factory-java libclassworlds-java libxml-commons-external-java libplexus-interpolation-java libgoogle-collections-java libargs4j-java libanimal-sniffer-java libhttpcore-java libservlet2.5-java libcommons-httpclient-java libcommons-vfs-java libjsr305-java libslf4j-java libasm3-java libjsoup-java libregexp-java libfop-java python-zookeeper libcommons-configuration-java rhino python-twisted-runner libjffi-java libxmlgraphics-commons-java python-support python-pydot libcommons-codec-java jenkins-common libcommons-lang-java libhamcrest-java libnetbeans-cvsclient-java libcommons-parent-java libcommons-collections3-java libgcj-common libplexus-utils-java libplexus-sec-dispatcher-java libjaffl-java libmaven-scm-java libdoxia-java libcommons-digester-java libbatik-java libbackport-util-concurrent-java libjetty-java liblog4j1.2-java libjline-java libcommons-io-java python-txaws python-dateutil libzookeeper-mt2 libmaven-invoker-java python-pyasn1 libganymed-ssh2-java python-pyparsing Use 'apt-get autoremove' to remove them. The following extra packages will be installed: daemon The following NEW packages will be installed: daemon jenkins 0 upgraded, 2 newly installed, 0 to remove and 55 not upgraded. Need to get 55.8 MB/55.9 MB of archives. After this operation, 61.7 MB of additional disk space will be used. Do you want to continue [Y/n]? Y Err http://pkg.jenkins-ci.org/debian/ binary/ jenkins 1.525 404 Not Found Failed to fetch http://pkg.jenkins-ci.org/debian/binary/jenkins_1.525_all.deb 404 Not Found E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? 20:39:29 (100) r...@lvs-re-inf1-jenkinsmaster3001.qa:~ apt-get install jenkins=1.524 Reading package lists... Done Building dependency tree Reading state information... Done E: Version '1.524' for 'jenkins' was not found Any one trying t install jenkisn via pat-get is essentially blocked...Sadly, that include me Also tried the debian native packages, via dbpk, but those are failing in other ways. dpkg --install jenkins_1.524_all.deb (Reading database ... 62588 files and directories currently installed.) Unpacking jenkins (from jenkins_1.524_all.deb) ... dpkg: error processing jenkins_1.524_all.deb (--install): trying to overwrite '/usr/share/jenkins/jenkins.war', which is also in package jenkins-common 1.424.6+dfsg-1ubuntu0.1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: jenkins_1.524_all.deb This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://w
