[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Daniel Beck commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin This may look like progress, but it's not IMO. Just see INFRA-234, severe issue (for both core devs and users) open for almost a week that should have a really simple fix. FWIW the last two scheduled weekly releases of Jenkins didn't happen either. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Cletus DSouza commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin Thanks! I see there is an INFRA issue opened now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Cletus DSouza commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin @Daniel - do you know if someone is looking into the release issue for jenkins-ci? I just tried to release a new version of the integrity-plugin and I'm still out of luck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Daniel Beck commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin Can't do more than ping the infra admins on IRC, which I did. Repeatedly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Grigoriy Milman resolved JENKINS-26770 as Fixed Apply doesnt work in version 1.29 of the plugin I have tested it. It works! Thanks for fast responses! Change By: Grigoriy Milman (11/Feb/15 7:02 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Cletus DSouza commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin Can you grab the latest hpi from JENKINS-26906 and test against that please? I added the ability to override the username/password at the job at the request of another user. Please make sure there is nothing in the latest fixes that comes as a surprise to you This latest snapshot will become the new release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Cletus DSouza updated JENKINS-26770 Apply doesnt work in version 1.29 of the plugin This version will become the next integrity-plugin.hpi 1.31. Please use this to test as I cannot release to jenkins-ci at the moment. Change By: Cletus DSouza (11/Feb/15 2:53 PM) Attachment: integrity-plugin.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Grigoriy Milman commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin Just tested. Hpi for JENKINS-26906 works fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Grigoriy Milman commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin By the way, on our production Jenkins server we will use the official plugin version This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Cletus DSouza commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin Just found an issue with the new credential management. If you change a particular hostname/port/user global config page then that changes the ID and can potentially cause a NPE if you don't go back and change it under each job. I will implement a unique ID that will guard against such NPE from a rename/change. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Daniel Beck commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin FYI see https://wiki.jenkins-ci.org/display/JENKINS/contributing#contributing-CommitMessages on how to write commit messages to get the bot to close the related issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Cletus DSouza edited a comment on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin @Daniel - seems like I can't do a release any more. Has something changed in terms of releasing to jenkins-ci? ERROR Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project integrity-plugin: Failed to deploy artifacts: Could not transfer artifact org.jenkins-ci.plugins:integrity-plugin:hpi:1.31 from/to maven.jenkins-ci.org (http://maven.jenkins-ci.org:8081/content/repositories/releases/): Failed to transfer file: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/integrity-plugin/1.31/integrity-plugin-1.31.hpi. Return code is: 401, ReasonPhrase: Unauthorized. Update - Seems like there is indeed something wrong on the repo side. Two other users have reported the same issue on the jenkins dev group. Will postpone the release until this is resolved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Cletus DSouza
updated JENKINS-26770
Apply doesnt work in version 1.29 of the plugin
Change By:
Cletus DSouza
(10/Feb/15 10:45 PM)
Summary:
Applydoesntworkin
version1.29oftheplugin
doesnotwork!
Description:
Updatedthisdefecttotracktheissueassociatedwiththeerrorwindowthatpops-upwhenclickingApplytosaveajob.Thisproblemaffectsv1.29andv1.30oftheintegrity-plugin--Originalpost...
Ihavetried1.29versionofthePlugintoday,justafter.Itdoesnotworkatall.AttempttobuildoldbuildjobsfailsbecauseoftheNullPointerExceptionduringbeginningofthebuild.ConfigurationofthenewjobsimpossibletosavebecauseoftheanotherNullPointerExceptionwhichhappenedduringattempttosave!Bytheway,why _ConfigurationName_isrequiredatall?maybetheinsteadthe_Projectname_(buildjobname)couldbeusedhere?Itisunique!h2.OldbuildjobsNullPointerExceptionhappendduringthebuild:{quote}[EnvInject]-Loadingnodeenvironmentvariables.[EnvInject]-Preparinganenvironmentforthebuild.[EnvInject]-KeepingJenkinssystemvariables.[EnvInject]-KeepingJenkinsbuildvariables.[EnvInject]-Injectingasenvironmentvariablesthepropertiescontent...[EnvInject]-Variablesinjectedsuccessfully.[EnvInject]-Injectingcontributions.BuildingFATAL:nulljava.lang.NullPointerException athudson.scm.IntegritySCM.buildEnvVars(IntegritySCM.java:463) athudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:910) athudson.model.AbstractBuild$AbstractBuildExecution.decideWorkspace(AbstractBuild.java:477) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:517) athudson.model.Run.execute(Run.java:1759) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:89) athudson.model.Executor.run(Executor.java:240){quote}h2.NullPointerExceptionduringsavingofthenewjobconfiguration{quote}Stacktracejavax.servlet.ServletException:java.lang.NullPointerException atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:649) atorg.kohsuke.stapler.Stapler.service(Stapler.java:238) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) athudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
SCM/JIRA link daemon commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin Code changed in jenkins User: cdsouza Path: src/main/java/hudson/scm/IntegrityCheckpointAction.java src/main/java/hudson/scm/IntegritySCM.java src/main/resources/hudson/scm/IntegrityCheckpointAction/config.jelly src/main/resources/hudson/scm/IntegrityCheckpointAction/help-checkpointLabel.html src/main/resources/hudson/scm/IntegrityCheckpointAction/help-tagName.html src/main/resources/hudson/scm/IntegritySCM/config.jelly src/main/resources/hudson/scm/IntegritySCM/help-checkpointLabel.html src/main/resources/hudson/scm/IntegritySCM/help-tagName.html http://jenkins-ci.org/commit/integrity-plugin/8c07aebda771658edcf2417f28cf39f243a24149 Log: Resolved JENKINS-26770 'Apply' doesn't work in version 1.29 of the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Cletus DSouza commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin @Daniel - seems like I can't do a release any more. Has something changed in terms of releasing to jenkins-ci? ERROR Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project integrity-plugin: Failed to deploy artifacts: Could not transfer artifact org.jenkins-ci.plugins:integrity-plugin:hpi:1.31 from/to maven.jenkins-ci.org (http://maven.jenkins-ci.org:8081/content/repositories/releases/): Failed to transfer file: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/integrity-plugin/1.31/integrity-plugin-1.31.hpi. Return code is: 401, ReasonPhrase: Unauthorized. I've done 29 releases thus far. Most recently on the 5th of Feb, so not really a noob when it comes to that The one thing I noticed in the error is that the repository has a :8081 where as I have the following in my .m2/settings.xml: idmaven.jenkins-ci.org/id Thoughts? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
