[JIRA] (JENKINS-15018) Support more files and directories
Andreas Zoufal created JENKINS-15018 Support more files and directories Issue Type: Improvement Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 02/Sep/12 9:13 AM Description: I tried the current version, the idea is really good! But I see that there are alot of files not synced (such without hudson*), and important directories too (userContent). Maybe it would be possible to enhance the configuration? To have some kind of filters etc? I'm sorry I cannot provide code because I'm not an Java programmer. Project: Jenkins Priority: Major Reporter: Andreas Zoufal 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
[JIRA] (JENKINS-15018) Support more files and directories
Frédéric Camblor resolved JENKINS-15018 as Duplicate Support more files and directories Issue is duplicated with JENKINS-8225 which will be made available in upcoming v0.0.6. The user-defined synchronization file patterns should fix your problem. Change By: Frédéric Camblor (02/Sep/12 9:37 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
[JIRA] (JENKINS-14792) Can't authenticate with HTTPS client cert + username/password
Frédéric Camblor commented on JENKINS-14792 Cant authenticate with HTTPS client cert + username/password Plugin is not using the .svn/ configuration directory. More infos provided here 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
[JIRA] (JENKINS-14841) Show Configuration history in job and global config and restore from history
Frédéric Camblor commented on JENKINS-14841 Show Configuration history in job and global config and restore from history I tried to implement this feature some month ago, but unfortunately, I'm stuck, for the moment, on a technical limitation of the maven scm api I'm using to provide an abstraction over every scm (this allows to replace subversion by git for instance). Unfortunately, maven scm api doesn't provide a generic log() method allowing to browse commits done on a file. Once this will be made available, maybe should I speak to Job Config History maintainers to see if we could find synergies on our respective work. 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
[JIRA] (JENKINS-14871) Save Jenkins system config error
Frédéric Camblor updated JENKINS-14871 Save Jenkins system config error Not related to scm-sync-configuration plugin (no package found in stacktrace) Please, find a better component if you want your issue to be taken into consideration. Change By: Frédéric Camblor (02/Sep/12 9:49 AM) Assignee: FrédéricCamblor CletusDSouza Component/s: integrity-plugin Component/s: scm-sync-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
[JIRA] (JENKINS-14893) scm sync configuration causes memory leak
Frédéric Camblor updated JENKINS-14893 scm sync configuration causes memory leak Change By: Frédéric Camblor (02/Sep/12 9:51 AM) Assignee: FrédéricCamblor BertrandPaquet 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
[JIRA] (JENKINS-14948) Cannot commit the configuration change
Frédéric Camblor resolved JENKINS-14948 as Wont Fix Cannot commit the configuration change As pointed in JENKINS-8871 (and in the wiki), svn+ssh protocol is not yet supported in the plugin. Change By: Frédéric Camblor (02/Sep/12 9:53 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
[JIRA] (JENKINS-9720) Support multiple SCM types within the one job
Frédéric Camblor updated JENKINS-9720 Support multiple SCM types within the one job Change By: Frédéric Camblor (02/Sep/12 10:04 AM) Assignee: FrédéricCamblor Component/s: core Component/s: scm-sync-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
[JIRA] (JENKINS-10274) Can this plugin support CLOC for even more languages and better Windows support
Andreas Zoufal commented on JENKINS-10274 Can this plugin support CLOC for even more languages and better Windows support Yes indeed, it works very well! Thx 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
[JIRA] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
Gabor Garami commented on JENKINS-14825 winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 Same on openSUSE 11.4 x86_64, Jenkins installed from pkg.jenkins-ci.org/opensuse and started with its own init script. Java(TM) SE Runtime Environment (build 1.6.0_31-b05) 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
[JIRA] (JENKINS-15017) NPE exception during normal build
Ulli Hafner resolved JENKINS-15017 as Duplicate NPE exception during normal build Change By: Ulli Hafner (02/Sep/12 4:12 PM) 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
[JIRA] (JENKINS-15019) Improvements when used with non-java code using gcovr
tsondergaard created JENKINS-15019 Improvements when used with non-java code using gcovr Issue Type: New Feature Assignee: stephenconnolly Components: cobertura Created: 02/Sep/12 7:04 PM Description: With gcovr the cobertura plugin can be used for coverage reports for C and C++ programs. The following changes would be very useful in this context: Being able to remove the "Classes" statistics from tables and graphs as the data is identical to the "Files" statistics. Being able to relabel "Packages" as "Directories" in graphs and tables Being able to use / as separator instead of . in package-names (directory-names) With these changes the "java-ness" would be removed from the interface. This changes could be enabled based on a marker in the cobertura xml. Already gcovr puts "gcovr 2.5-prerelease (r2774)" as the version attribute on the root coverage element, so it is easy to detect. Project: Jenkins Priority: Minor Reporter: tsondergaard 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
[JIRA] (JENKINS-14138) New git branch has empty changelist
tsondergaard commented on JENKINS-14138 New git branch has empty changelist @nhnb: The change to use the merge target as baseline for computing the changelog has been accepted (commit 5ae255594bd7e118bee6c58eae504d1c49e9f97b). As far as I'm concerned this bug can be resolved now, but I don't think the OP is satisfied. 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
[JIRA] (JENKINS-15020) Fails to build a successful build
Iain Banks created JENKINS-15020 Fails to build a successful build Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 02/Sep/12 9:38 PM Description: When I try to build a build and get it to fetch from github I get this error Started by user Iain Building in workspace /var/lib/jenkins/workspace/BitzCommands Checkout:BitzCommands / /var/lib/jenkins/workspace/BitzCommands - hudson.remoting.LocalChannel@55f9bcfa Using strategy: Default Cloning the remote Git repository Cloning repository origin Error trying to determine the git version: Error performing command: --version Assuming 1.6 ERROR: Error cloning remote repo 'origin' : Could not clone g...@github.com:PvM_Iain/BitzCommands.git hudson.plugins.git.GitException: Could not clone g...@github.com:PvM_Iain/BitzCommands.git at hudson.plugins.git.GitAPI.clone(GitAPI.java:268) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1122) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1064) at hudson.FilePath.act(FilePath.java:842) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1064) at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1502) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: hudson.plugins.git.GitException: Error performing command: clone -o origin g...@github.com:PvM_Iain/BitzCommands.git /var/lib/jenkins/workspace/BitzCommands at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:862) at hudson.plugins.git.GitAPI.access$000(GitAPI.java:40) at hudson.plugins.git.GitAPI$1.invoke(GitAPI.java:264) at hudson.plugins.git.GitAPI$1.invoke(GitAPI.java:244) at hudson.FilePath.act(FilePath.java:842) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.git.GitAPI.clone(GitAPI.java:244) ... 13 more Caused by: java.lang.NullPointerException at hudson.Launcher.printCommandLine(Launcher.java:592) at hudson.Launcher.maskedPrintCommandLine(Launcher.java:614) at hudson.Launcher$LocalLauncher.launch(Launcher.java:700) at hudson.Launcher$ProcStarter.start(Launcher.java:338) at hudson.Launcher$ProcStarter.join(Launcher.java:345) at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:843) ... 19 more Trying next repository ERROR: Could not clone repository FATAL: Could not clone hudson.plugins.git.GitException: Could not clone at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1134) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1064) at hudson.FilePath.act(FilePath.java:842) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1064) at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1502) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) I'm new to Jenkins and don't know to set it up properly. Due Date: 05/Sep/12 12:00 AM Environment: Linux Operating System Project: Jenkins Labels: plugin
[JIRA] (JENKINS-15020) Fails to build a successful build
Iain Banks stopped work on JENKINS-15020 Fails to build a successful build Change By: Iain Banks (02/Sep/12 11:14 PM) 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
[JIRA] (JENKINS-15020) Fails to build a successful build
Iain Banks started work on JENKINS-15020 Fails to build a successful build Change By: Iain Banks (02/Sep/12 11:14 PM) 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
[JIRA] (JENKINS-15020) Fails to build a successful build
Iain Banks updated JENKINS-15020 Fails to build a successful build Change By: Iain Banks (02/Sep/12 11:32 PM) Environment: LinuxOperatingSystem gitpluginGitHubPlugingithub-api Component/s: github 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
[JIRA] (JENKINS-14943) Need documentation explaining how to handle self-signed certificate in case of Jenkins running on HTTPS
Bruno P. Kinoshita closed JENKINS-14943 as Fixed Need documentation explaining how to handle self-signed certificate in case of Jenkins running on HTTPS Change By: Bruno P. Kinoshita (03/Sep/12 1:51 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
[JIRA] (JENKINS-15010) You should be able to select for which environment and build you want to selct testcases
Bruno P. Kinoshita commented on JENKINS-15010 You should be able to select for which environment and build you want to selct testcases This is tricky. Because you have a list of testopia installations. If the user changes the testopia installation, then we have to clean the input/select fields. This will require some time and some _javascript_ + jelly. 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
[JIRA] (JENKINS-14944) plugin-info on wiki page sometimes gives no info for this plugin
Bruno P. Kinoshita closed JENKINS-14944 as Fixed plugin-info on wiki page sometimes gives no info for this plugin Intermittent problem, seems fixed. Change By: Bruno P. Kinoshita (03/Sep/12 1:58 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
[JIRA] (JENKINS-14420) All SSH hosts are changed to be copies of the first SSH host entry after upgrade to 2.0
Rafael Dalma updated JENKINS-14420 All SSH hosts are changed to be copies of the first SSH host entry after upgrade to 2.0 config.xml file displaying correct siteName siteNameX.X.X.108:22/siteName Change By: Rafael Dalma (03/Sep/12 1:58 AM) Attachment: screenshot-1.jpg 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
[JIRA] (JENKINS-14420) All SSH hosts are changed to be copies of the first SSH host entry after upgrade to 2.0
Rafael Dalma updated JENKINS-14420 All SSH hosts are changed to be copies of the first SSH host entry after upgrade to 2.0 UI displaying incorrect siteName X.X.X.98:22 which is the first selection from the dropdown menu. Change By: Rafael Dalma (03/Sep/12 2:00 AM) Attachment: 2012-09-03_114904.png 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
[JIRA] (JENKINS-15004) Collecting findbugs analysis files
King Hpd commented on JENKINS-15004 Collecting findbugs analysis files Can u give me some idea about how to increase the memory in slave? 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
[JIRA] (JENKINS-14945) No maintainers indicated in plugin-info in wiki page
Bruno P. Kinoshita commented on JENKINS-14945 No maintainers indicated in plugin-info in wiki page Hmmm, tried executing the commands in IRC, but there is still no maintainer associated with testopia-plugin. Let me see what can we do about 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
[JIRA] (JENKINS-14973) Export of more environment variables from Testcase
Bruno P. Kinoshita commented on JENKINS-14973 Export of more environment variables from Testcase The following env vars have been added: TESTOPIA_TESTCASE_RUN_ID TESTOPIA_TESTCASE_BUILD_ID TESTOPIA_TESTCASE_ARGUMENTS TESTOPIA_TESTCASE_REQUIREMENT TESTOPIA_TESTCASE_SORT_KEY TESTOPIA_TESTCASE_SUMMARY TESTOPIA_TESTCASE_AUTHOR_ID TESTOPIA_TESTCASE_CATEGORY_ID TESTOPIA_TESTCASE_DEFAULT_TESTER_ID TESTOPIA_TESTCASE_PRIORITY_ID TESTOPIA_TESTCASE_STATUS_ID TESTOPIA_TESTCASE_AUTOMATED TESTOPIA_TESTCASE_CREATION_DATE TESTOPIA_TESTCASE_ESTIMATED_TIME TESTOPIA_TESTCASE_ENV_ID 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
[JIRA] (JENKINS-14974) Export more environment variables from Testcase run
Bruno P. Kinoshita commented on JENKINS-14974 Export more environment variables from Testcase run I'll recheck tomorrow morning, but apparently, the plug-in uses Test Runs only, no test case runs. Is that what you meant in this issue? I'm still quite confused with Testopia and its terms but nevertheless, I've added the following env vars to TestRuns (may be useful in the future I guess): TESTOPIA_TESTRUN_ID TESTOPIA_TESTRUN_BUILD TESTOPIA_TESTRUN_ENVIRONMENT TESTOPIA_TESTRUN_MANAGER TESTOPIA_TESTRUN_NOTES TESTOPIA_TESTRUN_PRODUCT_VERSION TESTOPIA_TESTRUN_SUMMARY TESTOPIA_TESTRUN_CASES TESTOPIA_TESTRUN_PLAN_ID TESTOPIA_TESTRUN_PLAN_TEXT_VERSION TESTOPIA_TESTRUN_STATUS TESTOPIA_TESTRUN_TARGET_COMPLETION TESTOPIA_TESTRUN_PLAN_TARGET_PASS 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
[JIRA] (JENKINS-14973) Export of more environment variables from Testcase
Bruno P. Kinoshita resolved JENKINS-14973 as Fixed Export of more environment variables from Testcase Change By: Bruno P. Kinoshita (03/Sep/12 3:52 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
[JIRA] (JENKINS-14973) Export of more environment variables from Testcase
Bruno P. Kinoshita edited a comment on JENKINS-14973 Export of more environment variables from Testcase The following env vars were added: TESTOPIA_TESTCASE_RUN_ID TESTOPIA_TESTCASE_BUILD_ID TESTOPIA_TESTCASE_ARGUMENTS TESTOPIA_TESTCASE_REQUIREMENT TESTOPIA_TESTCASE_SORT_KEY TESTOPIA_TESTCASE_SUMMARY TESTOPIA_TESTCASE_AUTHOR_ID TESTOPIA_TESTCASE_CATEGORY_ID TESTOPIA_TESTCASE_DEFAULT_TESTER_ID TESTOPIA_TESTCASE_PRIORITY_ID TESTOPIA_TESTCASE_STATUS_ID TESTOPIA_TESTCASE_AUTOMATED TESTOPIA_TESTCASE_CREATION_DATE TESTOPIA_TESTCASE_ESTIMATED_TIME TESTOPIA_TESTCASE_ENV_ID 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
