[JIRA] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title rin_ne commented on JENKINS-38917 Re: Version 1.8 stopped working with remote agents Released 1.9. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title rin_ne resolved as Fixed Jenkins / JENKINS-38917 Version 1.8 stopped working with remote agents Change By: rin_ne Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title rin_ne commented on JENKINS-38917 Re: Version 1.8 stopped working with remote agents OK, I will release new version. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title rin_ne commented on JENKINS-38917 Re: Version 1.8 stopped working with remote agents As I described it, the only workaround for the issue is to build on the master which is not feasible in the production environments, therefore Blocker priority. I don't think so. Blocker priority should be used on Jenkins project if If core is affected by installed plugin with no configuration. This issue happens on the build that is started from a job which has this plugin related configurations. So this issue might be broker from the viewpoint of this plugin, but this is never blocker from the viewpoint of this issue tracker. Please confirm the meaning of priority in this issue tracker within bees. Unfortunately I still not reproduce this issue, but I found weakness code. So I uploaded a patch. Could you fetch the latest commit on 'JENKINS-38917' branch then build and test again? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title rin_ne commented on JENKINS-38917 Re: Version 1.8 stopped working with remote agents Could you reproduce this with export-params pkugin 1.5 once? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title rin_ne commented on JENKINS-38917 Re: Version 1.8 stopped working with remote agents Priority Blocker is really correct? Regarding help, Blocks development and/or testing work, production could not run. I cannot reproduce your facing issue with remote slave. I have not updated this area since 1.5. NotSerializableException is raised if given object does not have implementation of Serializable interface. This plugin passes String object that is serialized from EnvVars to BufferedWriter. Thus this exception would be raised by String object if this is export-params plugin issue. I don't think this is not export-params plugin issue for now. Please provide your job configuration regarding export-params plugin if you want further investigation. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [export-params-plugin] (JENKINS-34783) Parameters not written to slave after upgrade to latest LTS
Title: Message Title rin_ne commented on JENKINS-34783 Re: Parameters not written to slave after upgrade to latest LTS Note that this issue should be fixed by other plugins that contributes parameters. So this fix is temporary solution. I would not release new version including this commit. The issue that this plugin should fix is "2 parameters are not contributed to build". but no way to fix from plugin side as of now. This means other plugins are the same situation. Thus, current official solution is "define system properties" only. 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] [export-params-plugin] (JENKINS-34783) Parameters not written to slave after upgrade to latest LTS
Title: Message Title rin_ne updated an issue Jenkins / JENKINS-34783 Parameters not written to slave after upgrade to latest LTS Change By: rin_ne Attachment: export-params.hpi 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] [export-params-plugin] (JENKINS-34783) Parameters not written to slave after upgrade to latest LTS
Title: Message Title rin_ne commented on JENKINS-34783 Re: Parameters not written to slave after upgrade to latest LTS Unfortunately I don't have debug environment now, but read security advisory then fix this. https://github.com/jenkinsci/export-params-plugin/commit/5b2875f0e40e1b53469f99a056b8a216dd54ae05 Attached built hpi. Please test it? 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] [gerrit-trigger-plugin] (JENKINS-26010) Workflow plugin not working with with Gerrit event
Title: Message Title rin_ne commented on JENKINS-26010 Re: Workflow plugin not working with with Gerrit event Sorry, my mention regarding quiet period was not enough. GT has independent filed regarding quiet period as named Build Schedule Delay. GT compares both project and GT value then set bigger ones as argument of schedule() when scheduling build. Thus GT's quiet period is still enabled even if it cannot be taken from project. Regarding quiet period, the below links should be read. For project: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod.html For GT: https://github.com/jenkinsci/gerrit-trigger-plugin/blob/master/src/main/webapp/help-BuildScheduleDelay.html 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] [gerrit-trigger-plugin] (JENKINS-26010) Workflow plugin not working with with Gerrit event
Title: Message Title rin_ne commented on JENKINS-26010 Re: Workflow plugin not working with with Gerrit event Hi Jacob Keller, I'm also looking at this issue. Maybe .getTrigger() can be resolved within this method. .addTrigger() is not used in GerritTrigger class as of now. So we can proceed to next step. If AbstractProject in type parameter of Trigger is changed to ParameterizedJob, we would also need to change ones in argument type of methods. In this case, I found another issue. Triggered build is scheduled by EventListener.schedule(). This method takes project instance as argument then would call ParameterizedJobMixIn.schedule2() accordingly. It needs the value of quiet period field in project instance. But it has been placed into AbstractProject. Neither Job nor ParameterizedJob have such interface. In workflow plugin, it is placed into WorkflowJob. If triggered build for workflow needs to follow quiet period which project has, this plugin need to have dependency to workflow plugin. Personally I don't prefer adding it as dependency. If we can avoid getting quiet period in project then use GT's ones only, this issue can be solved. But I'm not sure this solution can be taken because it might be degrade. rsandell, WDYT? I think it is also one of solution not to support workflow... 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] [gerrit-trigger-plugin] (JENKINS-25615) extra '/' getting added in the generated url for finding files in a given commit
rin_ne edited a comment on JENKINS-25615 extra / getting added in the generated url for finding files in a given commit pl.touk.sonar.GerritPluginException: Error listing files To begin with, This is not an exception thrown by GT. Perhaps you are using sonar-gerrit-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] [gerrit-trigger-plugin] (JENKINS-25615) extra '/' getting added in the generated url for finding files in a given commit
rin_ne commented on JENKINS-25615 extra / getting added in the generated url for finding files in a given commit pl.touk.sonar.GerritPluginException: Error listing files To begin with, This is not an exception thrown by GT. Perhaps you are using sonar-gerrit-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] [gerrit-trigger-plugin] (JENKINS-26865) Matrix parent aborts when 'Exclude trivial rebase' set in gerrit-trigger plugin
rin_ne commented on JENKINS-26865 Matrix parent aborts when Exclude trivial rebase set in gerrit-trigger plugin Misunderstanding. All child builds are aborted because parent build is aborted at first. Do you mean that new build is not started even if previous builds are canceled by new patchset? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger-plugin] (JENKINS-23421) Parameter value should be always displayed as human-readable
rin_ne closed JENKINS-23421 as Fixed Parameter value should be always displayed as human-readable Change By: rin_ne (10/Feb/15 11:24 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-23189) REST related configuration is lost when copy server
rin_ne closed JENKINS-23189 as Fixed REST related configuration is lost when copy server Change By: rin_ne (10/Feb/15 11:24 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-22814) Some infomations are logged from constructor on startup
rin_ne closed JENKINS-22814 as Fixed Some infomations are logged from constructor on startup Change By: rin_ne (10/Feb/15 11:24 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-24099) Connection to Gerrit is always established on bootup
rin_ne closed JENKINS-24099 as Fixed Connection to Gerrit is always established on bootup Change By: rin_ne (10/Feb/15 11:23 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-24074) Cannot review for build completed to default Gerrit via REST API
rin_ne closed JENKINS-24074 as Fixed Cannot review for build completed to default Gerrit via REST API Change By: rin_ne (10/Feb/15 11:23 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-24575) The instance of extension class should not be kept
rin_ne closed JENKINS-24575 as Fixed The instance of extension class should not be kept Change By: rin_ne (10/Feb/15 11:22 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-24012) Messages in RabbitMQ's queue was consumed but unacknowledged
rin_ne closed JENKINS-24012 as Fixed Messages in RabbitMQs queue was consumed but unacknowledged Change By: rin_ne (10/Feb/15 11:23 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-22813) Warning when clean install and restart
rin_ne closed JENKINS-22813 as Fixed Warning when clean install and restart Change By: rin_ne (10/Feb/15 11:25 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-26865) Matrix parent aborts when 'Exclude trivial rebase' set in gerrit-trigger plugin
rin_ne commented on JENKINS-26865 Matrix parent aborts when Exclude trivial rebase set in gerrit-trigger plugin That's normal if 'Build Current Patchset Only' is enabled in gerrit server config. In this case, build would be canceled when new patchset is created in the same 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] [gerrit-trigger-plugin] (JENKINS-26865) Matrix parent aborts when 'Exclude trivial rebase' set in gerrit-trigger plugin
rin_ne commented on JENKINS-26865 Matrix parent aborts when Exclude trivial rebase set in gerrit-trigger plugin This feature depends on Gerrit version. AFAIK 2.10 or later is needed. If earlier, this feature would be always disable. See patchset attribute in patchset-created event. 2.9.4 (no kind attribute) https://gerrit-documentation.storage.googleapis.com/Documentation/2.9.4/json.html#patchSet 2.10 (kind attribute has TRIVIAL_REBASE value) https://gerrit-documentation.storage.googleapis.com/Documentation/2.10/json.html#patchSet This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger-plugin] (JENKINS-26865) Matrix parent aborts when 'Exclude trivial rebase' set in gerrit-trigger plugin
rin_ne edited a comment on JENKINS-26865 Matrix parent aborts when Exclude trivial rebase set in gerrit-trigger plugin This feature depends on Gerrit version. AFAIK 2.10 or later is needed. If earlier, this feature would be always ignored. See patchset attribute in patchset-created event. 2.9.4 (no kind attribute) https://gerrit-documentation.storage.googleapis.com/Documentation/2.9.4/json.html#patchSet 2.10 (kind attribute has TRIVIAL_REBASE value) https://gerrit-documentation.storage.googleapis.com/Documentation/2.10/json.html#patchSet This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger-plugin] (JENKINS-26010) Workflow plugin not working with with Gerrit event
rin_ne commented on JENKINS-26010 Workflow plugin not working with with Gerrit event ParameterizedJobMixIn.ParameterizedJob cannot be built since it is not BuildableItem. GT has trigger feature in order to schedule build for its job. So I think it is no reason why GT treats non-buildable job. Should we fix isApplicable() only? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25962) Using Jenkins Job Builder to create triggers based on comment regex fails to trigger
rin_ne edited a comment on JENKINS-25962 Using Jenkins Job Builder to create triggers based on comment regex fails to trigger What is Jenkins Job Builder? Should we take JJB related issues as Jenkins plugin developer? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25962) Using Jenkins Job Builder to create triggers based on comment regex fails to trigger
rin_ne updated JENKINS-25962 Using Jenkins Job Builder to create triggers based on comment regex fails to trigger What is Jenkins Job Builder? Should we take JJB related issues as Jenkins developer? Change By: rin_ne (09/Dec/14 7:15 AM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger-plugin] (JENKINS-25608) Intermittent gerrit trigger NPE on Jenkins restart
rin_ne commented on JENKINS-25608 Intermittent gerrit trigger NPE on Jenkins restart Maybe this was fixed in 2.12.0. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger-plugin] (JENKINS-20897) Wrong encoding of characters (e.g. æøå) in commit messages, committers name, etc
rin_ne commented on JENKINS-20897 Wrong encoding of characters (e.g. æøå) in commit messages, committers name, etc Maybe this patch will fix https://github.com/sonyxperiadev/gerrit-events/pull/28 Not sure release plan. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger-plugin] (JENKINS-25428) Pending Gerrit Job details overlay the whole jenkins screen
rin_ne resolved JENKINS-25428 as Duplicate Pending Gerrit Job details overlay the whole jenkins screen Change By: rin_ne (05/Nov/14 8:05 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-25428) Pending Gerrit Job details overlay the whole jenkins screen
rin_ne updated JENKINS-25428 Pending Gerrit Job details overlay the whole jenkins screen This is not critical issue. You need to apply proper priority when report issue. Change By: rin_ne (05/Nov/14 7:57 AM) Priority: Critical Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger-plugin] (JENKINS-25383) Gerrit manual triggers using gerrit-trigger plugin cause form too large error
rin_ne commented on JENKINS-25383 Gerrit manual triggers using gerrit-trigger plugin cause form too large error Maybe already fixed: JENKINS-21064 You can check it on the latest beta. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger-plugin] (JENKINS-25383) Gerrit manual triggers using gerrit-trigger plugin cause form too large error
rin_ne resolved JENKINS-25383 as Duplicate Gerrit manual triggers using gerrit-trigger plugin cause form too large error Change By: rin_ne (02/Nov/14 1:55 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
rin_ne updated JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Change By: rin_ne (07/Oct/14 7:20 AM) Component/s: maven-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] [gerrit-trigger] (JENKINS-23104) Gerrit trigger: support a 'Comment added' trigger with no verdict restriction
rin_ne resolved JENKINS-23104 as Fixed Gerrit trigger: support a Comment added trigger with no verdict restriction Change By: rin_ne (08/Oct/14 1:29 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-23104) Gerrit trigger: support a 'Comment added' trigger with no verdict restriction
rin_ne updated JENKINS-23104 Gerrit trigger: support a Comment added trigger with no verdict restriction Seems such feature was already merged. Change By: rin_ne (08/Oct/14 1:28 AM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/170 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
rin_ne commented on JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Not sure this is an issue. So you should provide log. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
rin_ne edited a comment on JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Not sure this is an issue. So you should provide console log using attached pom. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
rin_ne commented on JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Sorry, I'm not sure your claim... Seems not Git/GT plugin issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
rin_ne updated JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Please get log using attached pom.xml (goal: compile) Change By: rin_ne (06/Oct/14 4:52 AM) Attachment: pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-24924) Gerrit trigger is not wokring with Maven Projects
rin_ne resolved JENKINS-24924 as Not A Defect Gerrit trigger is not wokring with Maven Projects Change By: rin_ne (01/Oct/14 6:13 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-24924) Gerrit trigger is not wokring with Maven Projects
rin_ne commented on JENKINS-24924 Gerrit trigger is not wokring with Maven Projects I can configure MavenProject with Gerrit Trigger. Of course its job can be triggered by gerrit events. I'm setting Jenkins 1.581 and GT 2.11.1 (The same as you prepared) If you have correctly introduced GT to your Jenkins, you can see "Gerrit Trigger" option in Build Trigger section on Job configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22137) Broken feature: Check non-reviewed patchsets
rin_ne commented on JENKINS-22137 Broken feature: Check non-reviewed patchsets In addition, all processes are done by listener thread. It would be serious issue on system. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-11779) Gerrit-plugin modifies ant command line which is not compatible on windows
rin_ne commented on JENKINS-11779 Gerrit-plugin modifies ant command line which is not compatible on windows You can pass all parameters to ant via file (using '-propertyfile' option) if you use the below plugin. https://wiki.jenkins-ci.org/display/JENKINS/Export+Parameters+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] [gerrit-trigger] (JENKINS-15074) Wrong type of quoting of gerrit parameters to Jenkins
rin_ne commented on JENKINS-15074 Wrong type of quoting of gerrit parameters to Jenkins On Windows, you should treat all GT parameters via file by using the below plugin. https://wiki.jenkins-ci.org/display/JENKINS/Export+Parameters+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] [gerrit-trigger] (JENKINS-16211) Gerrit Trigger GERRIT_PATCHSET_UPLOADER not support space in user name
rin_ne commented on JENKINS-16211 Gerrit Trigger GERRIT_PATCHSET_UPLOADER not support space in user name On Windows, you sould treat all parameters via file by using the below plugin. https://wiki.jenkins-ci.org/display/JENKINS/Export+Parameters+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] [gerrit-trigger] (JENKINS-24924) Gerrit trigger is not wokring with Maven Projects
rin_ne commented on JENKINS-24924 Gerrit trigger is not wokring with Maven Projects See my comment again. I already confirmed GT configured job is correctly triggered by gerrit event. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-24924) Gerrit trigger is not wokring with Maven Projects
rin_ne resolved JENKINS-24924 as Not A Defect Gerrit trigger is not wokring with Maven Projects Change By: rin_ne (01/Oct/14 12:47 PM) Status: Reopened Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-24924) Gerrit trigger is not wokring with Maven Projects
rin_ne edited a comment on JENKINS-24924 Gerrit trigger is not wokring with Maven Projects See my comment again. I already confirmed GT configured job is correctly triggered by gerrit event. Please configure GT with the below parameters then test again. Project Path: ** Branch Path: ** This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24919) Gerrit Trigger Plugin - Build Current Patchset Only - leave workspace in a bad state if it interrupts a fetch
rin_ne commented on JENKINS-24919 Gerrit Trigger Plugin - Build Current Patchset Only - leave workspace in a bad state if it interrupts a fetch GT calls build.cancel(). Your seeing result is the same as cancelling on WebUI. So it is not an issue for GT. Workaround is: Wipe workspace before fetch anything from SCM (I know git client plugin already have such feature in advanced field) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24919) Gerrit Trigger Plugin - Build Current Patchset Only - leave workspace in a bad state if it interrupts a fetch
rin_ne edited a comment on JENKINS-24919 Gerrit Trigger Plugin - Build Current Patchset Only - leave workspace in a bad state if it interrupts a fetch GT calls build.cancel(). Your seeing result is the same as cancelling on WebUI. So it is not an issue for GT. Also core issue. Because this is normal. Workaround is: Wipe workspace before fetch anything from SCM (I know git client plugin already have such feature in advanced field) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24919) Gerrit Trigger Plugin - Build Current Patchset Only - leave workspace in a bad state if it interrupts a fetch
rin_ne resolved JENKINS-24919 as Wont Fix Gerrit Trigger Plugin - Build Current Patchset Only - leave workspace in a bad state if it interrupts a fetch Change By: rin_ne (30/Sep/14 7:40 AM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24746) Support a way to retrigger part of matrix job
rin_ne edited a comment on JENKINS-24746 Support a way to retrigger part of matrix job How to run a part of matrix job normally in Web UI? "retrigger" will perform new build with the previous parameters. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24746) Support a way to retrigger part of matrix job
rin_ne updated JENKINS-24746 Support a way to retrigger part of matrix job Change By: rin_ne (19/Sep/14 1:27 AM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24746) Support a way to retrigger part of matrix job
rin_ne edited a comment on JENKINS-24746 Support a way to retrigger part of matrix job How to run a part of matrix job normally in Web UI? "retrigger" will perform new build with the previous parameters. U This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24746) Support a way to retrigger part of matrix job
rin_ne commented on JENKINS-24746 Support a way to retrigger part of matrix job How to run a part of matrix job normally in Web UI? "retrigger" will perform new build with the previous parameters. That's all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21064) Form too large if there are many patchsets in the selection list (manual trigger)
rin_ne updated JENKINS-21064 Form too large if there are many patchsets in the selection list (manual trigger) Change By: rin_ne (16/Sep/14 9:44 AM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/182 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-21064) Form too large if there are many patchsets in the selection list (manual trigger)
rin_ne resolved JENKINS-21064 as Fixed Form too large if there are many patchsets in the selection list (manual trigger) Change By: rin_ne (17/Sep/14 1:00 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22756) Gerrit Trigger depends on Maven Integration plugin
rin_ne resolved JENKINS-22756 as Cannot Reproduce Gerrit Trigger depends on Maven Integration plugin Change By: rin_ne (17/Sep/14 1:14 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-18225) treat dependent patches as a set
rin_ne updated JENKINS-18225 treat dependent patches as a set Change By: rin_ne (12/Sep/14 6:59 AM) Issue Type: Improvement NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-18123) it.generateHelper() in /gerrit-trigger/. Reason: java.lang.NullPointerException
rin_ne resolved JENKINS-18123 as Fixed it.generateHelper() in /gerrit-trigger/. Reason: java.lang.NullPointerException Change By: rin_ne (12/Sep/14 7:13 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-18123) it.generateHelper() in /gerrit-trigger/. Reason: java.lang.NullPointerException
rin_ne commented on JENKINS-18123 it.generateHelper() in /gerrit-trigger/. Reason: java.lang.NullPointerException Seems that this issue was alredy fixed since 2.11.0. See commit:f1ca14d7acd86cd658b4bb6b4bcaa5597907ec8f This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-17557) NullPointerException when searching open Gerrit events
rin_ne resolved JENKINS-17557 as Fixed NullPointerException when searching open Gerrit events Change By: rin_ne (12/Sep/14 7:22 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-17557) NullPointerException when searching open Gerrit events
rin_ne commented on JENKINS-17557 NullPointerException when searching open Gerrit events Seems the fix for this issue was already released to 2.10.1. See commit: f0add2554bbbff8a9abac59a7684305b327f1c92 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-21064) Form too large if there are many patchsets in the selection list (manual trigger)
rin_ne commented on JENKINS-21064 Form too large if there are many patchsets in the selection list (manual trigger) I think this is not a bug because not sure that expected solution. Can you present it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21064) Form too large if there are many patchsets in the selection list (manual trigger)
rin_ne commented on JENKINS-21064 Form too large if there are many patchsets in the selection list (manual trigger) Pagenation using limit and resume_sortkey Disable manual trigger then install the below plugin to Gerrit https://github.com/rinrinne/gerrit-raise-patch Increase MaxPermSize for JVM Improve query string to narrow down the result This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work for Matrix jobs
rin_ne updated JENKINS-24295 Gerrit Cancel doesnt work for Matrix jobs Change By: rin_ne (11/Sep/14 8:43 AM) Assignee: rsandell rin_ne This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work for Matrix jobs
rin_ne started work on JENKINS-24295 Gerrit Cancel doesnt work for Matrix jobs Change By: rin_ne (11/Sep/14 8:43 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work for Matrix jobs
rin_ne stopped work on JENKINS-24295 Gerrit Cancel doesnt work for Matrix jobs Change By: rin_ne (11/Sep/14 9:20 AM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work for Matrix jobs
rin_ne commented on JENKINS-24295 Gerrit Cancel doesnt work for Matrix jobs I can reproduce then find root cause. New PR is created. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work for Matrix jobs
rin_ne updated JENKINS-24295 Gerrit Cancel doesnt work for Matrix jobs Change By: rin_ne (11/Sep/14 9:23 AM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/178 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work for Matrix jobs
rin_ne resolved JENKINS-24295 as Fixed Gerrit Cancel doesnt work for Matrix jobs Change By: rin_ne (11/Sep/14 9:26 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21407) additional trigger button at the top or floating trigger button
rin_ne updated JENKINS-21407 additional trigger button at the top or floating trigger button Change By: rin_ne (12/Sep/14 4:43 AM) Assignee: rsandell rin_ne This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-21407) additional trigger button at the top or floating trigger button
rin_ne stopped work on JENKINS-21407 additional trigger button at the top or floating trigger button Change By: rin_ne (12/Sep/14 4:46 AM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work for Matrix jobs
rin_ne assigned JENKINS-24295 to rsandell Gerrit Cancel doesnt work for Matrix jobs Change By: rin_ne (12/Sep/14 4:48 AM) Assignee: rin_ne rsandell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-21407) additional trigger button at the top or floating trigger button
rin_ne updated JENKINS-21407 additional trigger button at the top or floating trigger button Change By: rin_ne (12/Sep/14 4:53 AM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/180 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-21407) additional trigger button at the top or floating trigger button
rin_ne resolved JENKINS-21407 as Fixed additional trigger button at the top or floating trigger button Change By: rin_ne (12/Sep/14 4:54 AM) Status: Open Resolved Assignee: rin_ne rsandell 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] [gerrit-trigger] (JENKINS-21064) Form too large if there are many patchsets in the selection list (manual trigger)
rin_ne resolved JENKINS-21064 as Wont Fix Form too large if there are many patchsets in the selection list (manual trigger) Change By: rin_ne (12/Sep/14 5:29 AM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-21064) Form too large if there are many patchsets in the selection list (manual trigger)
rin_ne commented on JENKINS-21064 Form too large if there are many patchsets in the selection list (manual trigger) Solution: JENKINS-20327 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-19477) Gerrit trigger stores KeyFile password as clear text
rin_ne updated JENKINS-19477 Gerrit trigger stores KeyFile password as clear text Change By: rin_ne (12/Sep/14 5:46 AM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/157 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-19477) Gerrit trigger stores KeyFile password as clear text
rin_ne resolved JENKINS-19477 as Fixed Gerrit trigger stores KeyFile password as clear text Change By: rin_ne (12/Sep/14 5:47 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21513) trigger builds drafts if cahnge-set moved from non-draft to draft status and back again.
rin_ne resolved JENKINS-21513 as Fixed trigger builds drafts if cahnge-set moved from non-draft to draft status and back again. Seems this PR meets your requirement https://github.com/jenkinsci/gerrit-trigger-plugin/pull/153 Change By: rin_ne (10/Sep/14 5:59 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22503) There is no possibility manually re-trigger patchsets from several review simulteniosly, Please select something to build appears
rin_ne resolved JENKINS-22503 as Fixed There is no possibility manually re-trigger patchsets from several review simulteniosly, Please select something to build appears Recently I found issue for session management in manual trigger. It was already fixed on master branch. Please check again if possible. Change By: rin_ne (10/Sep/14 6:04 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-19013) Gerrit Trigger: NPE on manual trigger
rin_ne updated JENKINS-19013 Gerrit Trigger: NPE on manual trigger Change By: rin_ne (09/Sep/14 8:36 AM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/176 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-19013) Gerrit Trigger: NPE on manual trigger
rin_ne edited a comment on JENKINS-19013 Gerrit Trigger: NPE on manual trigger When you ran build, session for search query might have been already closed. I will create new PR to check session status. @eguess74, if you set "Gerrit Trigger" to choosing strategy in git plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-19013) Gerrit Trigger: NPE on manual trigger
rin_ne edited a comment on JENKINS-19013 Gerrit Trigger: NPE on manual trigger When you ran build, session for search query might have been already closed. I will create new PR to check session status. @eguess74, did you set "Gerrit Trigger" to choosing strategy in git plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-19013) Gerrit Trigger: NPE on manual trigger
rin_ne commented on JENKINS-19013 Gerrit Trigger: NPE on manual trigger Seems this plugin simply implements interface provided by git plugin. It does not have such feature. If you want, you should request to git plugin at first. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-19013) Gerrit Trigger: NPE on manual trigger
rin_ne resolved JENKINS-19013 as Fixed Gerrit Trigger: NPE on manual trigger Change By: rin_ne (10/Sep/14 1:23 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-23236) PatchSetCreatedEvent now has a kind field
rin_ne commented on JENKINS-23236 PatchSetCreatedEvent now has a kind field Someone did test with Gerrit 2.10-rc0? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-22756) Gerrit Trigger depends on Maven Integration plugin
rin_ne updated JENKINS-22756 Gerrit Trigger depends on Maven Integration plugin Change By: rin_ne (10/Sep/14 1:35 AM) Component/s: maven This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-24394) Gerrit trigger plugin doesnt update Gerrit with review comments using the latest Gerrit code base
rin_ne resolved JENKINS-24394 as Wont Fix Gerrit trigger plugin doesnt update Gerrit with review comments using the latest Gerrit code base It's known issue and solution is already given. https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger#GerritTrigger-NotetoGerrit2.6Users Change By: rin_ne (09/Sep/14 5:42 AM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-24575) The instance of extension class should not be kept
rin_ne updated JENKINS-24575 The instance of extension class should not be kept Change By: rin_ne (04/Sep/14 7:35 AM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/ 174 175 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
rin_ne resolved JENKINS-24445 as Fixed Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification Change By: rin_ne (04/Sep/14 7:35 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24575) The instance of extension class should not be kept
rin_ne resolved JENKINS-24575 as Fixed The instance of extension class should not be kept Change By: rin_ne (04/Sep/14 7:23 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24575) The instance of extension class should not be kept
rin_ne updated JENKINS-24575 The instance of extension class should not be kept Change By: rin_ne (04/Sep/14 7:23 AM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/174 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-24575) The instance of extension class should not be kept
rin_ne created JENKINS-24575 The instance of extension class should not be kept Issue Type: Bug Affects Versions: current Assignee: rsandell Components: gerrit-trigger Created: 04/Sep/14 2:54 AM Description: Some classes which is extended from Extension keeps one's instance into one's member. It might cause memory leak after restart. Environment: Jenkins 1.565.1 Gerrit Trigger 2.11.0-beta-4 Project: Jenkins Priority: Critical Reporter: rin_ne This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
rin_ne updated JENKINS-24445 Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification Change By: rin_ne (01/Sep/14 9:46 AM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/172 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
rin_ne commented on JENKINS-24445 Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification Sorry, I missed attachment and fully understand. BTW, it seems that this plugin has some useful logs around the related logic. So I think you had better provide logs if you have. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
rin_ne commented on JENKINS-24445 Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification I reproduced this on the latest plugin code but there is a bit difference with what you mentioned. This will let Test_2 finish successfully (as Test_2 always succeeds). The bug that happens now, is that the trigger plugin uploads a "Verified +1" message, DESPITE "Test_1 #2" not yet being finished. When LOCKFILE_Test_2-2 was removed, any message was not uploaded. Next, LOCKFILE_Test_1-1 was removed. Then message "Verified -1" was uploaded from "Test_1 #1". Also message "Verified +1" was uploaded when LOCKFILE_Test_2-1 was removed. Finally, LOCKFILE_Test_1_2 was removed. Then message "Verified -1" was uploaded with verdict value both "Test_1 #2" and "Test_2 #2". It means that uploading message for "Test_2 #2" was pended until "Test_1 #2" is completed. It means that: Running builds for event from Gerrit were deviated from verdict logic by manual triggered ones. But these were still enabled as individual triggered build. So I think that the issue you should address is #2. right? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
