[JIRA] [google-play-android-publisher-plugin] (JENKINS-29887) Required Token Macro plugin was not installed by the Google Play APK upload plugin
Title: Message Title rogerhu commented on JENKINS-29887 Re: Required Token Macro plugin was not installed by the Google Play APK upload plugin Thanks for fixing so fast! Noticed that the credentials store is not able to auth with the newer versions. I downgraded back to 1.3.1 and this error msg went away: Upload failed: The Google Service Account credential 'api-project-xxx' could not be found. If you renamed the credential since configuring this job, you must re-configure this job, choosing the new credential name - No changes have been applied to the Google Play account Build step 'Upload Android APK to Google Play' marked build as failure Finished: FAILURE 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] [google-play-android-publisher-plugin] (JENKINS-29887) Required Token Macro plugin was not installed by the Google Play APK upload plugin
Title: Message Title rogerhu commented on JENKINS-29887 Re: Required Token Macro plugin was not installed by the Google Play APK upload plugin Downgrading to 1.3 worked fine...possible to issue a new release soon? 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] [google-play-android-publisher-plugin] (JENKINS-29887) Required Token Macro plugin was not installed by the Google Play APK upload plugin
Title: Message Title rogerhu commented on JENKINS-29887 Re: Required Token Macro plugin was not installed by the Google Play APK upload plugin Does 1.4 still have this issue? We see the problem too. 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] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
rogerhu commented on JENKINS-22820 Changes are not commited when using a recent git client I just rechecked with this latest plugin and it works fine on Ubuntu 14.04 and Git 1.9.1. Furthermore, Git 2.1.0 also works fine. I would go to System Log - add a Log recorder for "hudson.plugins.scm_sync_configuration". It should be more obvious what the issue is on your system. Yes, Java 6. Also you can skip setting the parent version (leave it) since there are dependencies going from Hudson to Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
rogerhu commented on JENKINS-22820 Changes are not commited when using a recent git client The commit message dialog not being displayed is a different issue and a regression from a previous change. What other symptoms are you seeing? You can debug this too by using IntelliJ Community Edition and importing the project too...click right-click on the hpi:run and you can startup your own instance of Jenkins (bit.ly/1t9vKDd) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
rogerhu commented on JENKINS-22820 Changes are not commited when using a recent git client I had to bump all org.apache.maven.scm related packages to 1.9.1. https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/21 The fix works for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [violations] (JENKINS-14291) Unavailable violations per file view for jslint
rogerhu commented on JENKINS-14291 Unavailable violations per file view for jslint The problem has to do with Java reflection when using Jelly templates: This PR fixes the issue and should be merged: https://github.com/jenkinsci/violations-plugin/pull/13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
rogerhu commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Added PR https://github.com/jenkinsci/git-client-plugin/pull/100 to try to create this temporary workspace directory. Can we just use the same dir used to create the temporary workspace dir? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
rogerhu commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) The problem is upon configuring a job using an HTTP-based URL with Git credentials, the plug-in attempts to do form validation and verify whether the HTTP authentication succeeded. Because of the recent updates to store this info as a temporary store so that subsequent Git commands will succeed with these credentials, the validation can fail in the absence of a workspace directory. In other words, the warning message "Failed to connect to repository : Command "git config --local credential.helper store" appears and can be ignored, but it's a false alarm. The job will fetch correctly if ran. For instance, if Jenkins was started from the / dir, then git will attempt to access .git/config from the root directory, resulting in permissions denied. Should the creation of the local credential simply just not be done in the absence of a workspace directory? See: https://github.com/jenkinsci/git-client-plugin/pull/97 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
