[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Idan Bidani commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file Assigned to hp-application-automation-tools-plugin. Workaround: Since I didn't need the HP plugin anymore I simply uninstalled it but for those which may still use it It could be worth trying to revert to 5.0 version(last known working version I used) For hp-application-automation-tools-plugin maintainers, it's recommended you either to place the repository manipulating calls inside try with resources, or switch (where feasible) to use calls to the git client plugin rather than calling directly to JGit. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Idan Bidani updated an issue Jenkins / JENKINS-55836 Unable to delete workspace due to locked git .pack file Change By: Idan Bidani Component/s: hp-application-automation-tools-plugin Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Idan Bidani commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file Per Mark Waite guidance and suggestions - big thanks! I've used Kosuke's tool https://file-leak-detector.kohsuke.org/ which helped me identify the open file handlers of the Jenkins node. This the stack trace the tool provided, notice com.microfocus.application.automation.tools.octane.model.processors.scm.GitSCMProcessor I disabled this plugin and the issue is resolved now. #17 PATH_TOWORKSPACE\GitWinBug\.git\objects\pack\pack-1db6aa468a129acaa6b8055b79680fec66793541.pack by thread:pool-1-thread-7 for JNLP4-connect connection to JENKINS_URL/IP_ADDR:60048 id=1013 on Sat Mar 16 21:44:38 EDT 2019#17 PATH_TOWORKSPACE\GitWinBug\.git\objects\pack\pack-1db6aa468a129acaa6b8055b79680fec66793541.pack by thread:pool-1-thread-7 for JNLP4-connect connection to JENKINS_URL/IP_ADDR:60048 id=1013 on Sat Mar 16 21:44:38 EDT 2019 at java.io.RandomAccessFile.(Unknown Source) at org.eclipse.jgit.internal.storage.file.PackFile.doOpen(PackFile.java:643) at org.eclipse.jgit.internal.storage.file.PackFile.beginWindowCache(PackFile.java:625) at org.eclipse.jgit.internal.storage.file.WindowCache.load(WindowCache.java:295) at org.eclipse.jgit.internal.storage.file.WindowCache.getOrLoad(WindowCache.java:379) at org.eclipse.jgit.internal.storage.file.WindowCache.get(WindowCache.java:184) at org.eclipse.jgit.internal.storage.file.WindowCursor.pin(WindowCursor.java:360) at org.eclipse.jgit.internal.storage.file.WindowCursor.copy(WindowCursor.java:259) at org.eclipse.jgit.internal.storage.file.PackFile.readFully(PackFile.java:601) at org.eclipse.jgit.internal.storage.file.PackFile.load(PackFile.java:773) at org.eclipse.jgit.internal.storage.file.PackFile.get(PackFile.java:285) at org.eclipse.jgit.internal.storage.file.ObjectDirectory.openPackedObject(ObjectDirectory.java:486) at org.eclipse.jgit.internal.storage.file.ObjectDirectory.openPackedFromSelfOrAlternate(ObjectDirectory.java:444) at org.eclipse.jgit.internal.storage.file.ObjectDirectory.openObject(ObjectDirectory.java:435) at org.eclipse.jgit.internal.storage.file.WindowCursor.open(WindowCursor.java:165) at org.eclipse.jgit.lib.ObjectReader.open(ObjectReader.java:236) at org.eclipse.jgit.revwalk.RevWalk.parseAny(RevWalk.java:890) at org.eclipse.jgit.revwalk.RevWalk.parseCommit(RevWalk.java:800) at com.microfocus.application.automation.tools.octane.model.processors.scm.GitSCMProcessor$FileContentCallable.invoke(GitSCMProcessor.java:128) at com.microfocus.application.automation.tools.octane.model.processors.scm.GitSCMProcessor$FileContentCallable.invoke(GitSCMProcessor.java:105) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3087) at hudson.remoting.UserRequest.perform(UserRequest.java:207) at hudson.remoting.UserRequest.perform(UserRequest.java:53) at hudson.remoting.Request$2.run(Request.java:358) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:98) at java.lang.Thread.run(Unknown Source)
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Idan Bidani commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file I looked at https://github.com/jenkinsci/git-plugin/compare/git-3.0.5...git-3.1.0 which led me to https://github.com/jenkinsci/git-client-plugin/compare/git-client-2.1.0...git-client-2.3.0 Mark Waite do you think it could be related to think it could be caused by https://github.com/jenkinsci/git-client-plugin/compare/git-client-2.1.0...git-client-2.3.0#diff-4a13310f7c84a9d6e133def48c0aed5a thanks in advance! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Idan Bidani edited a comment on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file I can actually reproduce the bug on Git 3.8.0 and couldn't reproduce it on 3.0.5. I hope to bisect it to later versions to narrow the changes caused it. reproduced on git I've isolated the bug to a change that happened between the 3.0.5(no bug) and 3.1.0 releaseIt may be a case of a conflicting change with another plugin change. If anyone else can try testing 3. 6 0 . 4 5 fixes the issue it will be helpful Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Idan Bidani edited a comment on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file I can actually reproduce the bug on Git 3.8.0 and couldn't reproduce it on 3.0.5. I hope to bisect it to later versions to narrow the changes caused it .reproduced on git plugin 3.6.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Idan Bidani commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file I can actually reproduce the bug on Git 3.8.0 and couldn't reproduce it on 3.0.5. I hope to bisect it to later versions to narrow the changes caused it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-41109) Kubernetes plugin defaults to wrong container
Title: Message Title Idan Bidani commented on JENKINS-41109 Re: Kubernetes plugin defaults to wrong container Thanks guys, I think this issue will be back often for others, having a radio button or allow reordering the container template for selecting the default container to use could be helpful. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-49484) Passwords and api key are saved in clear text in config
Title: Message Title Idan Bidani created an issue Jenkins / JENKINS-49484 Passwords and api key are saved in clear text in config Issue Type: Bug Assignee: Dhara Ghodasara Components: qmetry-for-jira-test-management-plugin Created: 2018-02-09 23:57 Labels: security Priority: Minor Reporter: Idan Bidani Passwords and api key are saved in plain text Add Comment
[JIRA] (JENKINS-49461) Publish test results
Title: Message Title Idan Bidani updated an issue Jenkins / JENKINS-49461 Publish test results Change By: Idan Bidani Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49461) Publish test results
Title: Message Title
Idan Bidani created an issue
Jenkins / JENKINS-49461
Publish test results
Issue Type:
Bug
Assignee:
Dhara Ghodasara
Components:
qmetry-for-jira-test-management-plugin
Created:
2018-02-08 16:37
Environment:
Jenkins 2.89.3 running on Windows 2012
Labels:
plugin
Priority:
Major
Reporter:
Idan Bidani
I'm really glad to see that you're working on Jenkins plugin, it is essential part of our testing framework. It seems like the "File URL"(probably should be named Test Results Location, it's not a URL) field doesn't accept relative paths. When running a build on an jenkins linux agent hwile the master Jenkins runs on windows, the plugin can't find results file see stack trace below.
INFO: Retrying request to {s}->https://issues.somewhere.com:443
java.io.FileNotFoundException: \opt\jenkins\jenkins-stg-slave\workspace\POC\SCM-JIRATest\target\surefire-reports\TEST-somepackage.xml (The system cannot find the path specified)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
at org.apache.http.entity.mime.content.FileBody.writeTo(FileBody.java:116)
at org.apache.http.entity.mime.AbstractMultipartForm.doWriteTo(AbstractMultipartForm.java:134)
at org.apache.http.entity.mime.AbstractMultipartForm.writeTo(AbstractMultipartForm.java:157)
at
[JIRA] (JENKINS-31491) Powershell plugin does not seem to work with Jenkins env variables
Title: Message Title Idan Bidani edited a comment on JENKINS-31491 Re: Powershell plugin does not seem to work with Jenkins env variables Any idea if/how to use paramters parameters like String Parameter? EDIT: Sorry had a different issue Answer: same as above 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-31491) Powershell plugin does not seem to work with Jenkins env variables
Title: Message Title Idan Bidani commented on JENKINS-31491 Re: Powershell plugin does not seem to work with Jenkins env variables Any idea if/how to use paramters like String Parameter? 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] [build-pipeline-plugin] (JENKINS-19870) Status of the existing pipeline job is not updated after a failure or aborted build. Downstream job trigger is not enabled after the build succeeds
Title: Message Title Idan Bidani commented on JENKINS-19870 Re: Status of the existing pipeline job is not updated after a failure or aborted build. Downstream job trigger is not enabled after the build succeeds This issue has been fixed in pull 73 Manuel Jesús Recena Soto do you mind taking a look at this pull request? 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] [multiple-scms-plugin] (JENKINS-30243) NoClassDefFoundError during startup (Template Project plugin 1.5)
Title: Message Title Idan Bidani edited a comment on JENKINS-30243 Re: NoClassDefFoundError during startup (Template Project plugin 1.5) same issue here, I don't have "Multiple SCMs plugin" plugin installed .Installing it solves the issue.seems like issue introduced in b6fe18f480f1216777400e56b1fae851665903a9 commit.[~brantone] Is there any way to make "Multiple SCMs plugin" dependency no mandatory? 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] [multiple-scms-plugin] (JENKINS-30243) NoClassDefFoundError during startup (Template Project plugin 1.5)
Title: Message Title Idan Bidani commented on JENKINS-30243 Re: NoClassDefFoundError during startup (Template Project plugin 1.5) same issue here, I don't have "Multiple SCMs plugin" plugin installed 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] [build-pipeline-plugin] (JENKINS-30404) Run button not clickable with parameterized builds
Title: Message Title Idan Bidani commented on JENKINS-30404 Re: Run button not clickable with parameterized builds Did you mean Jenkins version 1.609.3? there was no release with version 1.606.3 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-26596) On restarting broken build in pipeline, dashboard should update accordingly
Idan Bidani commented on JENKINS-26596 On restarting broken build in pipeline, dashboard should update accordingly Can this issue be considered as higher priority? rerunning a new build is the very basic functionality of the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-26877) Manual trigger ignores properties file if the build node doesn't exists anymore
Idan Bidani commented on JENKINS-26877 Manual trigger ignores properties file if the build node doesnt exists anymore Ended up doing just "source file.properties" and passing the env vars to the downstream. 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] [parameterized-trigger-plugin] (JENKINS-26877) Manual trigger ignores properties file if the build node doesn't exists anymore
Idan Bidani commented on JENKINS-26877 Manual trigger ignores properties file if the build node doesnt exists anymore Thanks, I got the same 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] [build-pipeline-plugin] (JENKINS-27238) Inject parameters on manual build trigger
Idan Bidani commented on JENKINS-27238 Inject parameters on manual build trigger Sounds more like a feature/improvement request and not a critical priority. please adjust 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] [build-pipeline-plugin] (JENKINS-25391) Cannot delete project
Idan Bidani closed JENKINS-25391 as Fixed Cannot delete project Been fixed here https://github.com/jenkinsci/build-pipeline-plugin/commit/880ba84553e1e6a58c284a8c8a705495ed5911b0 Change By: Idan Bidani (18/Feb/15 12:09 AM) Status: Reopened Closed 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] [build-pipeline-plugin] (JENKINS-25391) Cannot delete project
Idan Bidani reopened JENKINS-25391 Cannot delete project should be closed as fixed Change By: Idan Bidani (18/Feb/15 12:08 AM) Resolution: CannotReproduce Status: Closed Reopened 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] [build-pipeline-plugin] (JENKINS-25391) Cannot delete project
Idan Bidani closed JENKINS-25391 as Cannot Reproduce Cannot delete project Change By: Idan Bidani (17/Feb/15 11:21 PM) Status: Open Closed Assignee: IdanBidani 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] [build-pipeline-plugin] (JENKINS-25391) Cannot delete project
Idan Bidani commented on JENKINS-25391 Cannot delete project I Agree Daniel, However this issue is not reproducible therefore will be 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] [build-pipeline-plugin] (JENKINS-25391) Cannot delete project
Idan Bidani commented on JENKINS-25391 Cannot delete project Thanks Daniel, Sorry, I can't reproduce this issue. Morne do you know what's the steps to reproduce this? otherwise I'll close this 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-23456) I'm getting 23456!!!
Idan Bidani commented on JENKINS-23456 Im getting 23456!!! Hilarious! Wait,is that resolvable? 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] [maven2] (JENKINS-755) Default JDK meaning in project options is confusing.
Idan Bidani commented on JENKINS-755 Default JDK meaning in project options is confusing. Do you think this bug can be more generic and relate to all Jenkins tools: JDK, ant, Maven, Grails etc. The "(Default)" option functionality is not clear enough. My suggested solutions are: 1. Renaming it to something like "Find in PATH" or point out it's function in the help of the tools can help a lot. 2. Remove it completely 3. Allow the user to choose what is the default action does: "Find tool in PATH", "Use the first entry", "Use tool_name" 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] [configurationslicing] (JENKINS-11774) Mass-configure triggers in Email-Ext-plugin
Idan Bidani commented on JENKINS-11774 Mass-configure triggers in Email-Ext-plugin I've applied the patch and compiled successfully on the branch "with_triggers" you may find only the compilation fix without the error under branch "master" https://github.com/iplaman/configurationslicing-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/groups/opt_out.
[JIRA] [viewVC] (JENKINS-18283) Wrong URL in diff
Idan Bidani commented on JENKINS-18283 Wrong URL in diff We have the same issue I've had to compile it and manually upload the plugin. any chance to approve this pull request https://github.com/jenkinsci/viewVC-plugin/pull/4 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] [viewVC] (JENKINS-18283) Wrong URL in diff
Idan Bidani edited a comment on JENKINS-18283 Wrong URL in diff We have the same issue I've had to compile it and manually upload the plugin. any chance to approve this pull request https://github.com/jenkinsci/viewVC-plugin/pull/1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20809) JVM Crash during startup
Idan Bidani commented on JENKINS-20809 JVM Crash during startup Issue is a 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/groups/opt_out.
[JIRA] [core] (JENKINS-20219) Plugin Manager » Installed should have a Filter box
Idan Bidani assigned JENKINS-20219 to Idan Bidani Plugin Manager » Installed should have a Filter box Change By: Idan Bidani (07/Dec/13 6:39 AM) Assignee: IdanBidani This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [other] (JENKINS-20622) In the prompts to enter the password it says something else
Idan Bidani assigned JENKINS-20622 to Idan Bidani In the prompts to enter the password it says something else Change By: Idan Bidani (18/Nov/13 5:55 AM) Assignee: IdanBidani This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [other] (JENKINS-20622) In the prompts to enter the password it says something else
Idan Bidani started work on JENKINS-20622 In the prompts to enter the password it says something else Change By: Idan Bidani (18/Nov/13 5:55 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/groups/opt_out.
[JIRA] [other] (JENKINS-20622) In the prompts to enter the password it says something else
Idan Bidani resolved JENKINS-20622 as Fixed In the prompts to enter the password it says something else 90934e8 FIXED JENKINS-20622 - bad community translation Change By: Idan Bidani (18/Nov/13 6:20 AM) Status: InProgress Resolved Fix Version/s: current 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/groups/opt_out.
