[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
vjuranek commented on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 It seems that JoJ 1 runs without any problems, so this memory leak maybe appears only on some specific configurations (or somehow fixed in 1.539?). Did you only upgrade Jenkins core or did you also upgrade any plugins (so we can exclude memory leak in the plugins)? By system with 50 jobs you mean 50 jobs present or 50 jobs run in parallel most of the time? Thanks Btw: there's no Jenkins support team, it's community project based on volunteers, if you want a support team, you should check Cloudbees or some other provider which offers support for Jenkins. 1 https://ci.jenkins-ci.org/ 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-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg commented on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Thank You for your help First with all the respect to JoJ they doesn't have the system load that we are facing here and has you can see it's snapshots version. Anyway, I didn't try the release version 1.539... BTW: In order to solve memory leaks you must use load software such as Load Runner. I tried the new LTS versions after update plugins and without update plugins, still the same issue same bug and as I wrote this bug doesn't happens on previous version at all. Of course it community, open source and all of that... but don't forget there is also Enterprise edition that including "Jenkins support team" and I just wonder why they not solving this super critical issue but I guess this all another story... 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-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg updated JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Change By: Ronen Peleg (16/Dec/13 9:14 AM) Environment: LinuxServerwith24CPUsand64GBRAMJenkinsversionLTS1.509.4/1.532.1onJettyMemoryallocatedforJenkins/Jettyprocess:42GB Load Environment :Jenkinsworkingwith600jobswithhighactivities +40slavemachines(LinuxandWindows) 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] [additional-identities] (JENKINS-21017) Jenkins CLI update-job misses custom workspace deletion
Roy Zeng created JENKINS-21017 Jenkins CLI update-job misses custom workspace deletion Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: additional-identities Created: 16/Dec/13 9:19 AM Description: The custom workspace of a Jenkins job cannot be removed by the CLI using update-job. Steps to reproduce: 1. Have a job with a custom workspace. 2. Remove the custom workspace using the Jenkins java CLI (having a second job without the custom workspace and doing cli -get-job second job | cli update-job job is how we encountered this problem). 3. Note that the config.xml of the job no longer references a custom workspace. 4. Open the job in the Web GUI. Note that the custom workspace is there, and a save of the job without doing any updates will put the custom workspace configuration back into the config.xml file for the job. Bottom line - to remove the custom workspace, one either needs to do it via the web GUI, or do a restart of the Jenkins instance after doing it via the CLI. Side note: the and some other characters are save differently when updating a job via the CLI vs. the Web GUI. Example: double quotes " will be changed to '' in config.xml through CLI method. Environment: Red Hat Enterprise Linux Server release 6.4 (Santiago) Virtual Machine Project: Jenkins Priority: Minor Reporter: Roy Zeng 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] [delivery-pipeline] (JENKINS-20822) Pipeline start cause
Patrik Boström assigned JENKINS-20822 to Patrik Boström Pipeline start cause Change By: Patrik Boström (16/Dec/13 9:32 AM) Assignee: PatrikBoström 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] [delivery-pipeline] (JENKINS-20822) Pipeline start cause
Patrik Boström resolved JENKINS-20822 as Fixed Pipeline start cause Thanks to a contribution from Gustav Rånby, this issue is now fixed. Pipeline header will now include a start cause and contributors are removed from the header. Use show changes to see both changes and who contributed to the pipeline instance. Change By: Patrik Boström (16/Dec/13 9:34 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/groups/opt_out.
[JIRA] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
Jens Rydholm commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Moving the master to Linux is not an option for us, since our master is the company's main Exchange server. What we're doing instead is allowing lots of things to be done in Jenkins without being logged in, but that is far from optimal. Still, it prevents the annoyance of having to log in every time you want to do something, so that is the workaround we ended up choosing. 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-21015) NullPointerException in Jenkins Git Plugin
Stuart Boston commented on JENKINS-21015 NullPointerException in Jenkins Git Plugin Not only new jobs, this happens for ALL my Maven GitHub jobs that worked fine before the update. I assume this is related to JENKINS-20318 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-20630) Jenkins fails to start
K P commented on JENKINS-20630 Jenkins fails to start The issue by Linards L seems to be completely unrelated to the issue reported here. It would be better to create a different issue report for that, because "poluting" this issue with an unrelated issue is going to confuse people and makes it a mess to still see clearly through the issue comments, which isn't helping the original issue getting solved at 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/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Linards L commented on JENKINS-20630 Jenkins fails to start Sorry for mess. Created new issue: https://issues.jenkins-ci.org/browse/JENKINS-21018 Thanks again. 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-21018) After upgrading from v1.529 to any version later that v1.542 and then updating any plugin, jenkins becomes unsusable.
Linards L created JENKINS-21018 After upgrading from v1.529 to any version later that v1.542 and then updating any plugin, jenkins becomes unsusable. Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Dec/13 11:02 AM Description: Originally reported in https://issues.jenkins-ci.org/browse/JENKINS-20630, then moved here. Linards L added a comment - 03/Dec/13 11:33 AM - edited Still not fully functional. Reverted to v1.529. After first upgrade from v1.529 - it booted. After I updated more than 10 plugins and restarted ( second time, no jobs were finished / launched ) jenkins with v1.542, it again died with Jetty issues / spam in logs. My updated plugins: Artifactory Plugin This plugin allows deploying Maven 2, Maven 3, Ivy and Gradle artifacts and build info to the Artifactory artifacts manager. 2.2.1 (2.1.7) Credentials Plugin This plugin allows you to store credentials in Jenkins. 1.9.3 1.6 CVS Plugin This bundled plugin integrates Jenkins with CVS version control system. 2.11 2.9 Disk Usage Plugin This plugin records disk usage. 0.23 0.20 HTML Publisher Plugin 1.3 1.2 JIRA Plugin This plugin integrates Atlassian JIRA to Jenkins. Brīdinājums: Šis spraudnis ir paredzēts Jenkins 1.533 un jaunākai versijai. Tas var gan strādāt, gan nestrādāt ar Jūsu Jenkins instalāciju. 1.39 (1.36) JobConfigHistory Plugin Saves copies of all job and system configurations. 2.5 2.4 Maven Project Plugin Jenkins plugin for building Maven 2/3 jobs via a special project type. Brīdinājums: Šis spraudnis ir paredzēts Jenkins 1.532 un jaunākai versijai. Tas var gan strādāt, gan nestrādāt ar Jūsu Jenkins instalāciju. 2.0 1.529 Monitoring external jobs Adds the ability to monitor the result of externally executed jobs. 1.2 1.1 Nested View Plugin View type to allow grouping job views into multiple levels instead of one big list of tabs. 1.14 1.10 Parameterized Trigger Plugin This plugin lets you trigger new builds when your build has completed, with various ways of specifying parameters for the new build. 2.21 2.20 SSH Credentials Plugin This plugin allows you to store SSH credentials in Jenkins. Brīdinājums: Jaunā versija nav savietojama ar esošo uzstādīto spraudņa versiju. Jobs, kuri izmanto šo spraudni, var būt par iemeslu šo Jobu pārkonfigurācijai. 1.6 0.3 SSH Slaves plugin This plugin allows you to manage slaves running on *nix machines over SSH. Brīdinājums: Jaunā versija nav savietojama ar esošo uzstādīto spraudņa versiju. Jobs, kuri izmanto šo spraudni, var būt par iemeslu šo Jobu pārkonfigurācijai. 1.5 0.25 Subversion Plugin This plugin adds the Subversion support (via SVNKit) to Jenkins. 1.54 1.51 Warnings Plugin This plugin generates the trend report for compiler warnings in the console log or in log files. 4.38 4.35 cforce added a comment - 12/Dec/13 12:41 PM @Linards L Please post ur error logs. Did you test with Jenkins 1.543? Linards L added a comment - 13/Dec/13 12:31 PM - edited @cforce, I will do it now, but it will not be valid test anymore because once I reverted to v1.529, I updated plugins. So it might work now, but it does not cover the issue I had earlier - crash after second reboot ( after plugins update ). Test scenarion: 1. Up and running jenkins v1.529 with master and three slaves; All slaves offline; 2. Plugins - all updated ( from my last attempt ( see date of my previous comment here )); 3. Creating a slave ; installing as windows service ; starting it - up and running; 3.1 Updating java to 1.7u45 ; 3.2 Cannot launch slave-agent.jnlp because previously FAILED installation left old jars in slave directory. I had to delete them to make slave-agent.jlpn connectable, so I could install it as service. 4. Performing automatic upgrade with one job running and one in queue ; waiting till it finishes; Resulting in error from console before returning Finished: SUCCESS in console: ln builds\lastStableBuild c:\jenkins_master\jobs\trunk-build\lastStable failed java.nio.file.DirectoryNotEmptyException: c:\jenkins_master\jobs\trunk-ExportDlls\lastStable at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at
[JIRA] [maven] (JENKINS-20209) Maven plugin sends email notification to null address
Bruno Medeiros commented on JENKINS-20209 Maven plugin sends email notification to null address Where is it fixed? I'm on Jenkins 1.544, Maven Integration plugin 2.0 and still experiencing the issue. My downgrade option is to 1.533, not 1.534. 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] [delivery-pipeline] (JENKINS-21008) Severe performance degradation when loading view
Patrik Boström assigned JENKINS-21008 to Patrik Boström Severe performance degradation when loading view Change By: Patrik Boström (16/Dec/13 12:50 PM) Assignee: PatrikBoström 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] [gerrit-trigger] (JENKINS-11409) Gerrit-trigger should support waiting for downstream jobs of triggered builds
yannack commented on JENKINS-11409 Gerrit-trigger should support waiting for downstream jobs of triggered builds The problem with the parametrized-plugin-blocking-buildstep solution is also that you cannot copy artifacts, as artifact copying is only possible in the post build. This means that all the features around artifacts are lost (md5s, etc). The solution mentioned by Kohsuke, item #2 specifically, with UpstreamCause, would unfortunately not work for me, as the Upstream cause of the build does not pass through buildFlow. I believe one of the challenges here is what to do if the job / promotion you are waiting for never triggers ? For example, if you have some build which fails, it may not trigger downstream, and the "end" job might not happen. This means there will probably have to be a way to manually terminate the gerrit operation in case what is expected doesn't happen. Otherwise, you may end up with a lot of "open" gerrit events, waiting for jobs which may well never be triggered. One option I have been thinking of would be to have in the post-build phase, an action: 'fail/approve the triggering Gerrit event with ID: ', and allow a parameter. You would have to pass the Gerrit-event ID via build parameters for instance, but parameters are very well supported. This is sufficiently flexible for most use-cases I believe. optionally, we could even imagine: the fail/approve is directly related to the outcome of the build phase (have an option for "stable build only"). Failure = fail gerrit, Success = OK Gerrit, Unstable = OK Gerrit the fail/approve is manually set (to use is more complex constructs, such as promotions, etc). 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] (JENKINS-21019) Git Plugin not working with SCMServer
Lars Christensen created JENKINS-21019 Git Plugin not working with SCMServer Issue Type: Bug Assignee: Nicolas De Loof Attachments: jenkins.err.log, jenkins.out.log, jenkins.wrapper.log, no_cred_nullpointerexception.txt Components: git Created: 16/Dec/13 1:13 PM Description: We're trying to upgrade from Jenkins 1.533, Git Plugin 1.5.0, and Git Client Plugin 1.3.0 to the latest without luck. Jenkins simply will not clone Git repositories. Cloning via https://mydomain.com/repo.git using command line Git works perfectly on the machine that has Jenkins installed (msysgit and gitcredentialwinstore). This used to work on the old Jenkins/Git plugin too. The new Jenkins/Git Plugin had the following issues: 1. Failed to clone because of invalid certificate (despite command line git working). Seems like the plugin accesses https:// directly despite being told to use the command line Git. We now have a valid cert on the server however. 2. If using user/password credentials, Jenkins reports "status = 401" on the job configuration. Have tried with both DOMAIN\user and user (without domain specification). 3. When I select "NONE" as credentials (which works with the command line git, because of gitcredentialwinstore), I get a NullPointerException. (And a big fat error page in the middle of the configuration screen). I also get this exception with a simple https://github.com/someproject/ Environment: OS: Windows Server 2008 R2 Git Protocol: https Git server: SCManager (or even github). Jenkins 1.544 Git Client plugin 1.5.0 Git Plugin 2.0 Project: Jenkins Priority: Major Reporter: Lars Christensen 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] (JENKINS-21019) Git Plugin NullPoinerExcept with https protocol
Lars Christensen updated JENKINS-21019 Git Plugin NullPoinerExcept with https protocol Change By: Lars Christensen (16/Dec/13 1:14 PM) Summary: GitPlugin notworking NullPoinerExcept with SCMServer httpsprotocol 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] [subversion] (JENKINS-10678) Increased functionality of Subversion Plugins Dropdown Build Parameter
André Schramm assigned JENKINS-10678 to André Schramm Increased functionality of Subversion Plugins Dropdown Build Parameter Change By: André Schramm (16/Dec/13 1:13 PM) Assignee: RomainSeguy AndréSchramm 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] [maven] (JENKINS-20209) Maven plugin sends email notification to null address
Marcelo Rebasti commented on JENKINS-20209 Maven plugin sends email notification to null address Bruno, the fix will be present in the upcoming maven integration plugin 2.1. The only version with the bug is 2.0, so you can downgrade to 1.533 too. 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-21020) Builds disappear from the job after its renaming
Nickolay Rumyantsev created JENKINS-21020 Builds disappear from the job after its renaming Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Dec/13 1:40 PM Description: When a job is renamed, all its builds disappear from the build history (but remain it the filse system). Jenkins restart or reload fixes this completely. To reproduce: Choose a job with builds. Rename it. Run System.gc() several times in the Script Console. Now job shows no builds. Environment: 2 envs: - 1.512 RHEL 5.9 - 1.543 win7 Project: Jenkins Priority: Major Reporter: Nickolay Rumyantsev 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] [disk-usage] (JENKINS-20876) disk usage hangs http request to view job
Tim Drury commented on JENKINS-20876 disk usage hangs http request to view job Thanks, Lucie. I'm pretty confident this issue is caused by this one: https://issues.jenkins-ci.org/browse/JENKINS-19544 - if you can't reproduce this on 1.542, then feel free to close it (or mark as caused by 19544). 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] [mailer] (JENKINS-20954) Cannot save email recipients
dtriphaus edited a comment on JENKINS-20954 Cannot save email recipients Same problem here with 1.543 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] [mailer] (JENKINS-20954) Cannot save email recipients
dtriphaus commented on JENKINS-20954 Cannot save email recipients Same Problem here with 1.543 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] [ec2] (JENKINS-19943) EC2 plugin cannot connect to slaves outside us-east-1 on new AWS accounts (using EC2-VPC)
Michael Tutty commented on JENKINS-19943 EC2 plugin cannot connect to slaves outside us-east-1 on new AWS accounts (using EC2-VPC) This is a blocker for me, using a non-EC2 Jenkins server. +1 for the fix. 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] [cppcheck] (JENKINS-18029) In CppCheck plugin selected line with static analysis violation is hidden because breadcrumb covers it
Yoichi Nakayama commented on JENKINS-18029 In CppCheck plugin selected line with static analysis violation is hidden because breadcrumb covers it analysis-core uses 10 line offset for the link as: https://github.com/jenkinsci/analysis-core-plugin/blob/c27e8fe79ca4fecc4e485e3fda23982e37b59f4e/src/main/java/hudson/plugins/analysis/util/model/AbstractAnnotation.java#L424 Showing some lines before the target line is useful to read the context, too. 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] [cppcheck] (JENKINS-18029) In CppCheck plugin selected line with static analysis violation is hidden because breadcrumb covers it
Yoichi Nakayama edited a comment on JENKINS-18029 In CppCheck plugin selected line with static analysis violation is hidden because breadcrumb covers it For reference, analysis-core uses 10 line offset for the link as: https://github.com/jenkinsci/analysis-core-plugin/blob/c27e8fe79ca4fecc4e485e3fda23982e37b59f4e/src/main/java/hudson/plugins/analysis/util/model/AbstractAnnotation.java#L424 Showing some lines before the target line is useful to read the context, too. 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] [delivery-pipeline] (JENKINS-21008) Severe performance degradation when loading view
Patrik Boström commented on JENKINS-21008 Severe performance degradation when loading view PipelineFactory fixes: https://github.com/Diabol/delivery-pipeline-plugin/commit/6c31f5d5e34bddd0a804a228ffec2a8e8fe9662f Refresh request will just be one per client. JQuery fixes: https://github.com/Diabol/delivery-pipeline-plugin/commit/c7a2ef7ee6ed02f921fbc7519edc4c1dce8d7e89 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] [delivery-pipeline] (JENKINS-21008) Severe performance degradation when loading view
Patrik Boström resolved JENKINS-21008 as Fixed Severe performance degradation when loading view Change By: Patrik Boström (16/Dec/13 2:32 PM) 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/groups/opt_out.
[JIRA] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Mark Ottaviani commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. Email from bap: Hi Mark, I no longer use Jenkins and don't have time to maintain the publish over plugins. Feel free to merge, test and release as you see fit. Regards, Bap. 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Mark Ottaviani commented on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Email from bap: Hi Mark, I no longer use Jenkins and don't have time to maintain the publish over plugins. Feel free to merge, test and release as you see fit. Regards, Bap. 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-20989) PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered
ikedam commented on JENKINS-20989 PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered It seems that you need an access not to the latest build, but to the build that triggered the downstream build. If so, I know it can be resolved by adding RunParameter support to parameterized build plugin, but you may also consider using UpstreamCause to access to the upstream build. For example, Copy Artifact plugin provides an option to retrieve artifacts from the upstream build that triggered that downstream build. 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] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
SCM/JIRA link daemon commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. Code changed in jenkins User: Thomas Van Doren Path: src/main/java/jenkins/plugins/publish_over_ssh/BapSshHostConfiguration.java src/main/java/jenkins/plugins/publish_over_ssh/BapSshPublisherPlugin.java http://jenkins-ci.org/commit/publish-over-ssh-plugin/549ebd579841e5a7989aa1df30339d5367fdae3f Log: JENKINS-17058 Add Alexander Fisher's patches from comments. https://issues.jenkins-ci.org/browse/JENKINS-17058?focusedCommentId=177125page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-177125 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] [subversion] (JENKINS-20690) Subversion changes using Assembla
Cameron Horn commented on JENKINS-20690 Subversion changes using Assembla The repository browser is set to "(Auto)". 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] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
SCM/JIRA link daemon commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. Code changed in jenkins User: Alex Earl Path: pom.xml src/main/java/jenkins/plugins/publish_over_ssh/BapSshHostConfiguration.java src/main/java/jenkins/plugins/publish_over_ssh/BapSshPublisherPlugin.java http://jenkins-ci.org/commit/publish-over-ssh-plugin/dbc15b7ae03b4b140e074295a6c243a4781842ec Log: Merge pull request #4 from key-consulting/master JENKINS-17058 add readResolve on BapSshHostConfiguration, fix dep Compare: https://github.com/jenkinsci/publish-over-ssh-plugin/compare/c591bae51812...dbc15b7ae03b 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-21022) Jenkins 1.544 hangs on startup *after* upgrade
Kevin R.
created JENKINS-21022
Jenkins 1.544 hangs on startup *after* upgrade
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
16/Dec/13 3:42 PM
Description:
I get this in my logs:
]# tail -f /var/log/jenkins/jenkins.log
Running from: /usr/lib/jenkins/jenkins.war
Dec 16, 2013 3:39:13 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: jetty-8.y.z-SNAPSHOT
Dec 16, 2013 3:39:13 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Extract jar:file:/usr/lib/jenkins/jenkins.war!/ to /tmp/jetty-0.0.0.0-8080-jenkins.war-any/webapp
Dec 16, 2013 3:39:18 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: NO JSP Support for , did not find org.apache.jasper.servlet.JspServlet
Jenkins home directory: /var/lib/jenkins found at: System.getProperty("JENKINS_HOME")
Dec 16, 2013 3:39:19 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
And it just hangs.
This has happened to me going from 1.541 to 1.542 from 1.542 to 1.544
The quickfire solution for me was to literally nuke the entire installation directory and perform a clean install.
Environment:
CentOS 6.4
Version 1.544
Project:
Jenkins
Priority:
Major
Reporter:
Kevin R.
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-20387) Timeout (10min) on git clone command
Joseph S commented on JENKINS-20387 Timeout (10min) on git clone command How do I set the "org.jenkinsci.plugins.gitclient.Git.timeout" configuration on a Jenkins running on Windows 2012 as a Service? Thnx, (If this is not the rigth place to ask this question, kindly let me know where should I go, thnx). 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-21022) Jenkins 1.544 hangs on startup *after* upgrade
Kevin R. updated JENKINS-21022 Jenkins 1.544 hangs on startup *after* upgrade Change By: Kevin R. (16/Dec/13 3:54 PM) Description: Igetthisinmylogs: ]#tail-f/var/log/jenkins/jenkins Dec16,20133:53:30PMorg . log springframework.web.context.support.StaticWebApplicationContextprepareRefresh Runningfrom INFO : /usr/lib/jenkins/jenkins Refreshingorg . war springframework.web.context.support.StaticWebApplicationContext@453c8bb1:displayname[RootWebApplicationContext];startupdate[MonDec1615:53:30UTC2013];rootofcontexthierarchy Dec16,20133: 39 53 : 13 30 PMorg. eclipse springframework . jetty web . util context . log support . JavaUtilLoginfo StaticWebApplicationContextobtainFreshBeanFactory INFO: jetty-8 Beanfactoryforapplicationcontext[org . y springframework . z-SNAPSHOT web.context.support.StaticWebApplicationContext@453c8bb1]:org.springframework.beans.factory.support.DefaultListableBeanFactory@84a0b66 Dec16,20133: 39 53 : 13 30 PMorg. eclipse springframework . jetty beans . util factory . log support . JavaUtilLoginfo DefaultListableBeanFactorypreInstantiateSingletons INFO: Extractjar Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@84a0b66 : file definingbeans[authenticationManager];rootoffactoryhierarchyDec16,20133 : /usr/lib/jenkins/jenkins 53:31PMorg . war!/to/tmp/jetty-0 springframework . 0 web . 0 context . 0-8080-jenkins support . war--any-/webapp StaticWebApplicationContextprepareRefresh INFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@2471fd20:displayname[RootWebApplicationContext];startupdate[Mon Dec16 15:53:31UTC2013];rootofcontexthierarchyDec16 ,20133: 39 53 : 18 31 PMorg. eclipse springframework . jetty web . util context . log support . JavaUtilLoginfo StaticWebApplicationContextobtainFreshBeanFactory INFO: NOJSPSupport Beanfactory for ,didnotfind applicationcontext[ org. apache springframework . jasper web . servlet context . JspServletJenkinshomedirectory support.StaticWebApplicationContext@2471fd20] : /var/lib/jenkinsfoundat:System org . getProperty(JENKINS_HOME) springframework.beans.factory.support.DefaultListableBeanFactory@36927633 Dec16,20133: 39 53 : 19 31 PM jenkins org . InitReactorRunner$1onAttained springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletons INFO: Startedinitialization Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@36927633:definingbeans[filter,legacy];rootoffactoryhierarchy Anditjusthangs.Thishashappenedtomegoingfrom1.541to1.542from1.542to1.544Thequickfiresolutionformewastoliterallynuketheentireinstallationdirectoryandperformacleaninstall. --Edit:copy-pastedthewrongtextblock-- 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-4354) Make Hudson user names case insensitive
stephenconnolly commented on JENKINS-4354 Make Hudson user names case insensitive This needs to be configurable. Making usernames case insensitive will raise a similar bug for Security Realms which are case sensitive. e.g. Unix login names are case sensitive (convention is to only use all lowercase, but they are actually case sensitive) e.g. Email addresses are permitted to be case sensitive (nobody really treats them as case sensitive but according to the RFC everything before the @ must be treated as case preserving as it may be case sensitive and only the receiving mailbox will have the correct knowledge) Worse still is that Jenkins sees Users who's ID differs only in case as being the same User object under some code paths and different User objects under other code paths. 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-21004) Label usage doesn't account for labels used as part of a logical grouping
Brian Smith updated JENKINS-21004 Label usage doesnt account for labels used as part of a logical grouping Change By: Brian Smith (16/Dec/13 4:07 PM) Description: Ifyoubringuponeofyournodes(byclickingonthenodenameinthestatusorbrowsingtoitviaManageNodes ) yougetalistoflabelsonthatpage.Ifyouclickonalabelitletsyouknowwhatprojectsareusingthatlabel.However,anyjobsthatusethelabelaspartofalogical_expression_(i.e.Label1(Label2||Label3)dontappearonthelist.ThismeansthatasfarasIcantellthereisnowaytotrackdownallofthejobsthatarecurrentlyusingaparticularlabelunlesstheyareusingitindividually.Thismakesitreallyhardtomanagelabelusageandtomaintainlabelsifyouneedtoupdatesome...youhavetowaitforthejobtofailbecauseitcannolongerfindthecorrectlabelasameanstotrackthemdown.Myapologiesinadvanceifthishasalreadybeenaddressedsomewhere.Ilookedaroundforquiteawhileanddidntfindanything. 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-20387) Timeout (10min) on git clone command
Mark Waite commented on JENKINS-20387 Timeout (10min) on git clone command I'd ask the question on the Jenkins users mailing list. I don't know how to pass Java properties to the java virtual machine running as a service on Windows. There are more people using the service on the Jenkins users mailing list than there are people monitoring this bug. 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] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Preston Gilchrist commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. What do we need to do to get on the maintainers list? 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] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Alexander Fischer commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. Hello, I hve fixed the problem earlier this year. See my Jira-comments on April of 2013. You can look into my sources on Github. https://github.com/afischer211/publish-over-plugin https://github.com/afischer211/publish-over-ssh-plugin I don't know, how to propagate my patches to the official version of the plugins (pull-request?). So I use my own patched version since April without any problems until now with Jenkins 1.544. 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Alexander Fischer commented on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Hello, how can we take over the maintainance for the plugins? I use my own patched version (see on Github) for a long-time without any problems. https://github.com/afischer211/publish-over-plugin https://github.com/afischer211/publish-over-ssh-plugin Is Github the correct place for Jenkins-plugins? 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] (JENKINS-20607) GIT Plugin 2.0: Polling ignores commit from certain users not working
venu 1456 commented on JENKINS-20607 GIT Plugin 2.0: Polling ignores commit from certain users not working @Owen, I tried "Force Polling using workspace" option which didnt work in my case. I see that your pull request is not yet merged,once done i'll try it again. 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] [project-inheritance] (JENKINS-21021) StackOverflowError whole switching versions
Khurram Malik commented on JENKINS-21021 StackOverflowError whole switching versions if i remove "Matrix Authorization Strategy Plugin" it works fine. I think Martin Schroder has fixed this for me in past for a similar case during Beta release project-inheritance-1.4.6-SNAPSHOT.hpi. Any info when it can be 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.
[JIRA] [project-inheritance] (JENKINS-21021) StackOverflowError while switching versions
Khurram Malik updated JENKINS-21021 StackOverflowError while switching versions Change By: Khurram Malik (16/Dec/13 5:29 PM) Summary: StackOverflowError whole while switchingversions 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-21023) WorkspaceCleanupThread does not handle folders
Jesse Glick created JENKINS-21023 WorkspaceCleanupThread does not handle folders Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Dec/13 5:37 PM Description: Only considers direct subdirectories of jobs, and later calls getItem which can only work for top-level jobs. Also process(Jenkins) is only looking for $JENKINS_HOME/jobs//workspace/ for builds run on master, which is deprecated—new installations use $JENKINS_HOME/workspace/*/. Ideally would handle any workspace location pattern, since this is configurable. Project: Jenkins Labels: folders Priority: Major Reporter: Jesse Glick 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] [maven] (JENKINS-20209) Maven plugin sends email notification to null address
nomar morado commented on JENKINS-20209 Maven plugin sends email notification to null address when is the schedule for 2.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-20630) Jenkins fails to start
Daniel Beck resolved JENKINS-20630 as Fixed Jenkins fails to start Marking as resolved again, as the user who reopened it appears to be affected by a different issue. Change By: Daniel Beck (16/Dec/13 6:19 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21024) Miscellaneous exceptions in config.xml can prevent entire job from loading
Jesse Glick created JENKINS-21024 Miscellaneous exceptions in config.xml can prevent entire job from loading Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Dec/13 6:31 PM Description: Jenkins has code to ensure that certain kinds of errors in configuration XML, such as missing classes saved by formerly installed plugins, are safely sent to OldDataMonitor and do not break loading of the rest of the item. But this does not seem to work for miscellaneous exceptions rethrown by XStream, such as a syntactically malformed trigger specification. Project: Jenkins Labels: robustness xstream Priority: Major Reporter: Jesse Glick 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-21024) Miscellaneous exceptions in config.xml can prevent entire job from loading
Jesse Glick started work on JENKINS-21024 Miscellaneous exceptions in config.xml can prevent entire job from loading Change By: Jesse Glick (16/Dec/13 6:37 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 -- 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-21024) Miscellaneous exceptions in config.xml can prevent entire job from loading
Jesse Glick assigned JENKINS-21024 to Jesse Glick Miscellaneous exceptions in config.xml can prevent entire job from loading Change By: Jesse Glick (16/Dec/13 6:37 PM) Assignee: JesseGlick 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] [campfire] (JENKINS-21025) Campfire Plugin duplicates configuration in each job when job-specific settings are not specified
Daniel Atallah created JENKINS-21025 Campfire Plugin duplicates configuration in each job when job-specific settings are not specified Issue Type: Bug Assignee: jenslukowski Components: campfire Created: 16/Dec/13 6:47 PM Description: Instead of referencing the campfire settings in the global configuration, the global values are duplicated in the configuration for each job. The job configuration dialog does show empty fields and a comment about only needing to enter a value to override the global configuration, but it still stores the global value within the job-specific config.xml The effect of this is that making a change to the global configuration doesn't affect any of the jobs - you need to go through and "clear out" the settings for the global settings to be re-copied to the jobs. Environment: Jenkins 1.544 running in Tomcat 7 Version 2.6 of the Campfire Plugin. Project: Jenkins Priority: Major Reporter: Daniel Atallah 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] [findbugs] (JENKINS-20874) Slow FindBugsPlugin.start is wasted
Jesse Glick commented on JENKINS-20874 Slow FindBugsPlugin.start is wasted it's less than a second we will gain Maybe so but that winds up being a significant portion of startup time, especially if you are running interactive or Selenium tests, etc. Would it help if we make some performance tests with Jenkins? This would be wonderful! run in CI to prevent that the performance degenerates if a new feature is added I doubt that is practical—there would be too many false positives, since performance timings are always mere estimates (unless you can run in some very tightly controlled virtual machine). Anyway in some cases a slightly slower startup is a worthwhile price to pay for some crucial fix or major feature; it requires human judgment to decide whether a performance regression is a mistake, and if so, who should fix 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/groups/opt_out.
[JIRA] [core] (JENKINS-19142) Don't add jobs to a view
Daniel Beck commented on JENKINS-19142 Dont add jobs to a view When a user invoke "New Job" from a view, I think the expected behavior is that new item is included in the view. Unless it's the default view. How else are you creating jobs, if not in a view? There's no way (except by entering the URL or using weird view types) to create a job and not have it listed in any way. Since Folders plugin always uses a list view as default view, using a different view type as default won't work. I've reworked to add option to disable job selector: Not sure this is approach is better than the earlier one. I have a default view with manually selected contents. Any newly created jobs are added to that view automatically (unless users select a different view first). To disable automatically adding jobs, I need to use a workaround to get the manually selected content. How about the following: Let's assume that the problem is mostly with the default view in the current ViewGroup, because users who just want to create a new job usually select the ItemGroupTopLevelItem the job should be in (i.e. Jenkins homepage, or a folder), and then create it there. Further, note that URLs /.../ and /.../view/DefaultViewName/ both exist and show the same view (you navigate to the latter after saving a default view's configuration). Unfortunately, when clicking the 'DefaultViewName' tab, you're directed to /.../ instead of /.../view/DefaultViewName/. How about 1) the 'New Job' link simply links to (effectively) $currentUrl/newJob, and 2) the tab title for 'DefaultViewName' links to /.../view/DefaultViewName/? Then you won't automatically add jobs to the default view if you just selected its parent, but will be able to add jobs to it when navigating there deliberately. Unfortunately, this will behave weirdly when you only have one view. In that case, a redirect to /.../view/DefaultViewName/ might work: If there are other views, don't add the job anywhere, otherwise add to the default view. Maybe the solution is to get rid of the default view entirely and use a dashboard-like or nested-view-like view instead, whose 'Add' link doesn't have add jobs anywhere by default. Won't work for Folders plugin unfortunately, as the default view is always a list view. To explain my particulat need for this: Also adding one of my use cases: I have a Jenkins instance with ~6500 jobs which build and bundle components for a rather large software distribution. Nobody cares about these jobs as long as they're successful, and showing list views with 150-4500 jobs each (distinguished by type, and no further division is useful) wouldn't be productive. So the only views I have only show unstable, failing, or disabled jobs, using View Job Filters. When someone adds a new job, it makes no sense to add it to one of these computed views. 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] [hp-application-automation-tools-plugin] (JENKINS-21026) LR Scenario runs but LR Analysis fails
Mark McLauchlin created JENKINS-21026 LR Scenario runs but LR Analysis fails Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 16/Dec/13 7:50 PM Description: I can get the plugin to work and run a LoadRunner scenario but I get an error after the scenario completes and the analysis kicks off. I tried a master/slave configuration and I also tried running the command on the slave using the command line and the command that Jenkins shows (HpToolsLauncher.exe -paramfile blahblah.txt) but get the same error. I can open the results file that is generated manually. Right now I am just using a dummy project for the build that I can run a load test on. There is no SCM or other dependencies on the project. The build should do nothing other than start LoadRunner. Here is the error. Error Message no results file found for Standard Output 16/12/2013 13:38:28 Running: \\10.10.10.141\c$\lrdemo\webgoat.lrs Cleaning up the environment... Preparing scenario \\10.10.10.141\c$\lrdemo\webgoat.lrs for execution. Load Generator localhost connected Starting scenario... Analyzing results... Error: Error during Analysis run. See output console for details Analysis Results: Loader Manager initialization failed. at Analysis.ApiSL.ApiSlRuntimeErrors.Throw(Int32 aErrorCode, ApiException aException) at Analysis.ApiSL.ApiSlRuntimeErrors.UnsafeCode(UnsafeCodeHandlerBool aHandler, Int32 aLraErrorCode) at Analysis.Api.Session.CreateWithTemplateFile(String aSessionName, String aResultFileName, String aTemplateFileName) at Analysis.Api.Session.Create(String aSessionName, String aResultFileName) at LRAnalysisLauncher.Program.Main(String[] args) Error(s) summary: 0 ignored , 0 errors Test result: Error 16/12/2013 13:39:59 Test complete: \\10.10.10.141\c$\lrdemo\webgoat.lrs --- Cleaning up the environment... Standard Error Error: Error during Analysis run. See output console for details Environment: Win Server 2008 64-bit (Master) where Jenkins runs / Win 7 32-bit (slave) where LoadRunner runs LoadRunner 11.52 Project: Jenkins Priority: Major Reporter: Mark McLauchlin 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] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Mark Ottaviani commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. @Preston, I suggest e-mailing on this thread in the jenkins-dev mailing list: https://groups.google.com/forum/#!topic/jenkinsci-dev/7vEwarVHbgc Slide merged the change today and is supposed to be pushing out a release, but he's still looking for a new official maintainer. 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] [mailer] (JENKINS-20954) Cannot save email recipients
Jesse Glick resolved JENKINS-20954 as Fixed Cannot save email recipients Fixed in sources in https://github.com/jenkinsci/mailer-plugin/commit/2dd9a1ec694e44e2ba47feae6b718d5c5040cda4 (though this was reported to me in 1.5, not 1.6). Change By: Jesse Glick (16/Dec/13 8:16 PM) 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21015) NullPointerException in Jenkins Git Plugin
Ignacio Albors commented on JENKINS-21015 NullPointerException in Jenkins Git Plugin Workaround: create an empty .netrc on your $HOME touch $HOME/.netrc 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-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow
Daniel Beck updated JENKINS-9120 RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow Change By: Daniel Beck (16/Dec/13 8:41 PM) Labels: lts-candidate 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] [active-directory] (JENKINS-21027) LDAP/AD: Both username and username@email-addr permitted as login; can be confusing
Eric Griswold created JENKINS-21027 LDAP/AD: Both username and username@email-addr permitted as login; can be confusing Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: active-directory, ldap Created: 16/Dec/13 9:12 PM Description: Jenkins 1.509.4 LDAP 1.6 Active Directory 1.33 (Using role-based authentication but it also seems to be the same using matrix authentication) If I authenticate to Jenkins using my username and AD password, I receive the permissions that I'm expecting. However, Jenkins will allow me to also log in with my email address and same AD password. When I do this, I seem to be authenticated but the permissions are different (and often far more limited) than logging in with just the username. Is there a way to reject a user if they try to log in with their email address? In other words, this works: user: eric.griswold password: AD password But this is rejected as "unknown user" or "bad password" user: eric.grisw...@jivesoftware.com password: AD password Environment: Jenkins server running on CentOS 6 Project: Jenkins Priority: Minor Reporter: Eric Griswold 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] [mercurial] (JENKINS-14862) Setting a tag in branch configuration breaks the check out
Jesse Glick resolved JENKINS-14862 as Duplicate Setting a tag in branch configuration breaks the check out Change By: Jesse Glick (16/Dec/13 9:15 PM) Status: InProgress 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/groups/opt_out.
[JIRA] [core] (JENKINS-21024) Miscellaneous exceptions in config.xml can prevent entire job from loading
SCM/JIRA link daemon resolved JENKINS-21024 as Fixed Miscellaneous exceptions in config.xml can prevent entire job from loading Change By: SCM/JIRA link daemon (16/Dec/13 9:24 PM) Status: InProgress 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/groups/opt_out.
[JIRA] [core] (JENKINS-21024) Miscellaneous exceptions in config.xml can prevent entire job from loading
SCM/JIRA link daemon commented on JENKINS-21024 Miscellaneous exceptions in config.xml can prevent entire job from loading Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/util/CopyOnWriteList.java core/src/main/java/hudson/util/RobustCollectionConverter.java core/src/main/java/hudson/util/RobustReflectionConverter.java core/src/main/java/hudson/util/xstream/ImmutableListConverter.java test/src/test/groovy/hudson/model/RunMapTest.groovy test/src/test/java/hudson/util/RobustReflectionConverterTest.java test/src/test/resources/hudson/util/RobustReflectionConverterTest/randomExceptionsReported.zip http://jenkins-ci.org/commit/jenkins/c3508113f0e1659f0e6c1064f31cb2ac1caa2ef3 Log: FIXED JENKINS-21024 Catch a full range of XStreamException’s during deserialization, including rethrown exceptions from readResolve. 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] [accelerated-build-now] (JENKINS-21028) I can get on to ci.bukkit.org
Edward Hoblyn created JENKINS-21028 I can get on to ci.bukkit.org Issue Type: Patch Affects Versions: current Assignee: Unassigned Components: accelerated-build-now Created: 16/Dec/13 9:55 PM Project: Jenkins Priority: Major Reporter: Edward Hoblyn 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] [mercurial] (JENKINS-5396) Support tags instead of branches
Jesse Glick started work on JENKINS-5396 Support tags instead of branches Change By: Jesse Glick (16/Dec/13 10:30 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 -- 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] [analysis-core] (JENKINS-10596) Improve handling of source code files with duplicate relative path names
Colin Bennett commented on JENKINS-10596 Improve handling of source code files with duplicate relative path names What is the "scan workspace option"? I see there is a "Scan workspace files" section with an "Add" button that allows one to "Workspace files to scan for compiler warnings using a predefined parser", but that's not what I want, I am already scanning and correctly capturing the warnings on the console output I don't have a log file to scan. I did try to enable the "Resolve relative paths" checkbox under "Advanced..." but that didn't fix the issue. I am using a custom parser for the Freescale (formerly Metrowerks) ColdFire compiler, with the "-msgstyle gcc" option. Here's the regex: ^\s*(?:\[exec\])\s*(.*):(\d+):\s*(warning|error): (\S.*)$ and here's the mapping script: import hudson.plugins.warnings.parser.Warning String fileName = matcher.group(1) String lineNumber = matcher.group(2) String category = matcher.group(3) String message = matcher.group(4) return new Warning(fileName, Integer.parseInt(lineNumber), "Dynamic Parser", category, message); and here's an example message: [exec] ..\..\..\..\common\comps\mx\mqx\mxDefs.h:247: warning: florbity frobbity grokkity goo I see no problem with the parsing; it works fine and correctly identifies the file path and line number etc. 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-21024) Miscellaneous exceptions in config.xml can prevent entire job from loading
dogfood commented on JENKINS-21024 Miscellaneous exceptions in config.xml can prevent entire job from loading Integrated in jenkins_main_trunk #3120 FIXED JENKINS-21024 Catch a full range of XStreamException’s during deserialization, including rethrown exceptions from readResolve. (Revision c3508113f0e1659f0e6c1064f31cb2ac1caa2ef3) Result = SUCCESS Jesse Glick : c3508113f0e1659f0e6c1064f31cb2ac1caa2ef3 Files : test/src/test/groovy/hudson/model/RunMapTest.groovy test/src/test/resources/hudson/util/RobustReflectionConverterTest/randomExceptionsReported.zip core/src/main/java/hudson/util/xstream/ImmutableListConverter.java test/src/test/java/hudson/util/RobustReflectionConverterTest.java core/src/main/java/hudson/util/RobustCollectionConverter.java core/src/main/java/hudson/util/CopyOnWriteList.java changelog.html core/src/main/java/hudson/util/RobustReflectionConverter.java 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] (JENKINS-21019) Git Plugin NullPoinerExcept with https protocol
Hans-Christoph Steiner commented on JENKINS-21019 Git Plugin NullPoinerExcept with https protocol I'm also seeing this exact same issue on our Jenkins. Its bad, a total showstopper for us since all of our core repos are accessed via HTTPS. We're running Jenkins 1.532.1 with all the plugins fully updated (that's what triggered this problem, updating all the plugins). Jenkins git client is 1.5. Our jenkins is running on Debian/wheezy/amd64. Downgrading Jenkins git client to 1.4.6 fixed the issue 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/groups/opt_out.
[JIRA] [support-core] (JENKINS-21029) Flush logs to disk only periodically
Jesse Glick created JENKINS-21029 Flush logs to disk only periodically Issue Type: Bug Assignee: Unassigned Components: support-core Created: 16/Dec/13 10:48 PM Description: See: https://github.com/jenkinsci/support-core-plugin/commit/2deeb5d1db04c80c75aba62b6dc63ba9c3149d4c#commitcomment-4861058 Project: Jenkins Labels: performance Priority: Major Reporter: Jesse Glick 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] [analysis-core] (JENKINS-10596) Improve handling of source code files with duplicate relative path names
Ulli Hafner commented on JENKINS-10596 Improve handling of source code files with duplicate relative path names Yes I thought the 'Resolve relative paths' option will help. Can you please activate the logging for hudson.plugins.analysis.core.ParserResult (level FINE). There should be some messages why the resolve relative path failed. 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] [mercurial] (JENKINS-5396) Support tags instead of branches
SCM/JIRA link daemon commented on JENKINS-5396 Support tags instead of branches Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/mercurial/MercurialSCM.java src/main/resources/hudson/plugins/mercurial/MercurialSCM/config.jelly src/main/resources/hudson/plugins/mercurial/MercurialSCM/help-branch.html src/main/resources/hudson/plugins/mercurial/MercurialSCM/help-revision.html src/main/resources/hudson/plugins/mercurial/MercurialSCM/help-revisionType.html src/test/java/hudson/plugins/mercurial/SCMTestBase.java http://jenkins-ci.org/commit/mercurial-plugin/a1d636a76bbcd99a7ee11e6460da3c2240030d42 Log: FIXED JENKINS-5396 Added supported option to update to a tag rather than a branch. 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] [mercurial] (JENKINS-5396) Support tags instead of branches
SCM/JIRA link daemon resolved JENKINS-5396 as Fixed Support tags instead of branches Change By: SCM/JIRA link daemon (16/Dec/13 11:03 PM) Status: InProgress 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Mark Waite commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Git client plugin 1.5.0 has released. I plan to confirm this bug is fixed in that version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20640) Jenkins become very slow and had 'proxy error'
Sam Xiao commented on JENKINS-20640 Jenkins become very slow and had proxy error I don't think these are monitor plugin specific bugs, I've seen the proxy errors almost every endpoints. I think there's an upstream bug somewhere caused this, and only when Jenkins is under heavy load. 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] [openid] (JENKINS-8925) Cannot use CLI when using OpenID
Rafael Fonseca commented on JENKINS-8925 Cannot use CLI when using OpenID Can you clarify how you are logging in using the CLI? I can't get it to work. It does pick the right username based on my SSH key, though. java -jar jenkins-cli.jar -s http://jenkins_url:8080/ login hudson.security.UserMayOrMayNotExistException: Unable to query user information: my_username at hudson.security.UserDetailsServiceProxy.loadUserByUsername(UserDetailsServiceProxy.java:43) at hudson.security.SecurityRealm.loadUserByUsername(SecurityRealm.java:305) at hudson.cli.ClientAuthenticationCache.set(ClientAuthenticationCache.java:90) at hudson.cli.LoginCommand.run(LoginCommand.java:37) at hudson.cli.CLICommand.main(CLICommand.java:232) at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63) at hudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) 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] (JENKINS-20258) Git plugin with checkout to subdir and prune stale branches fails all builds
Mark Waite reopened JENKINS-20258 Git plugin with checkout to subdir and prune stale branches fails all builds Git client plugin 1.5.0 was intended to fix this (based on the submission ba2ab8934), but it still fails. Steps I used to duplicate the problem with Git client plugin 1.5.0: Create a new job (I named mine git-jgit-specific-subdir-prune) Configure git repo URL https://github.com/MarkEWaite/check_git.git Add behavior to checkout to a local subdirectory Add behavior to prune stale remote tracking branches Save the job and run it Change By: Mark Waite (17/Dec/13 2:25 AM) Resolution: Fixed Status: Resolved 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/groups/opt_out.
[JIRA] [git] (JENKINS-20258) Git plugin with checkout to subdir and prune stale branches fails all builds
Mark Waite edited a comment on JENKINS-20258 Git plugin with checkout to subdir and prune stale branches fails all builds Git client plugin 1.5.0 was intended to fix this (based on the submission ba2ab8934), but it still fails. Steps I used to duplicate the problem with Git client plugin 1.5.0: Create a new job (I named mine git-jgit-specific-subdir-prune) Configure git repo URL https://github.com/MarkEWaite/check_git.git Use jgit as the implementation rather than the default Add behavior to checkout to a local subdirectory Add behavior to prune stale remote tracking branches Save the job and run 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/groups/opt_out.
[JIRA] [git] (JENKINS-20258) Git plugin with checkout to subdir and prune stale branches fails all builds
Mark Waite edited a comment on JENKINS-20258 Git plugin with checkout to subdir and prune stale branches fails all builds Git client plugin 1.5.0 was intended to fix this (based on the submission ba2ab8934), but it still fails. Steps I used to duplicate the problem with Git client plugin 1.5.0: Create a new job (I named mine git-jgit-specific-subdir-prune) Configure git repo URL https://github.com/MarkEWaite/check_git.git Use jgit as the implementation rather than the default Add behavior to checkout to a local subdirectory Add behavior to prune stale remote tracking branches Save the job and run it Stack trace looks like: Building on master in workspace /var/lib/jenkins/jobs/git-jgit-specific-subdir-prune-simple/workspace Pruning obsolete local branches FATAL: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null hudson.plugins.git.GitException: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null at org.jenkinsci.plugins.gitclient.JGitAPIImpl.prune(JGitAPIImpl.java:913) at hudson.plugins.git.extensions.impl.PruneStaleBranch.beforeCheckout(PruneStaleBranch.java:31) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:858) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557) at hudson.model.Run.execute(Run.java:1665) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Caused by: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null at org.eclipse.jgit.transport.URIish.init(URIish.java:205) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.listRemoteBranches(JGitAPIImpl.java:923) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.prune(JGitAPIImpl.java:901) ... 10 more 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] (JENKINS-20258) Git plugin with checkout to subdir and prune stale branches fails all builds
Mark Waite edited a comment on JENKINS-20258 Git plugin with checkout to subdir and prune stale branches fails all builds Git client plugin 1.5.0 was intended to fix this (based on the submission ba2ab8934), but it still fails. Steps I used to duplicate the problem with Git client plugin 1.5.0: Create a new job (I named mine git-jgit-specific-subdir-prune) Configure git repo URL https://github.com/MarkEWaite/check_git.git Use jgit as the implementation rather than the default Add behavior to checkout to a local subdirectory Add behavior to prune stale remote tracking branches Save the job and run it Stack trace looks like: Building on master in workspace /var/lib/jenkins/jobs/git-jgit-specific-subdir-prune-simple/workspace Pruning obsolete local branches FATAL: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null hudson.plugins.git.GitException: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null at org.jenkinsci.plugins.gitclient.JGitAPIImpl.prune(JGitAPIImpl.java:913) at hudson.plugins.git.extensions.impl.PruneStaleBranch.beforeCheckout(PruneStaleBranch.java:31) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:858) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557) at hudson.model.Run.execute(Run.java:1665) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Caused by: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null at org.eclipse.jgit.transport.URIish.init(URIish.java:205) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.listRemoteBranches(JGitAPIImpl.java:923) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.prune(JGitAPIImpl.java:901) ... 10 more 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] (JENKINS-20258) Git plugin with checkout to subdir and prune stale branches fails all builds
Mark Waite edited a comment on JENKINS-20258 Git plugin with checkout to subdir and prune stale branches fails all builds Git client plugin 1.5.0 was intended to fix this (based on the submission ba2ab8934), but it still fails. Steps I used to duplicate the problem with Git client plugin 1.5.0: Create a new job (I named mine git-jgit-specific-subdir-prune) Configure git repo URL https://github.com/MarkEWaite/check_git.git Use jgit as the implementation rather than the default Add behavior to checkout to a local subdirectory Add behavior to prune stale remote tracking branches Save the job and run it Stack trace looks like: Building on master in workspace /var/lib/jenkins/jobs/git-jgit-specific-subdir-prune-simple/workspace Pruning obsolete local branches FATAL: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null hudson.plugins.git.GitException: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null at org.jenkinsci.plugins.gitclient.JGitAPIImpl.prune(JGitAPIImpl.java:913) at hudson.plugins.git.extensions.impl.PruneStaleBranch.beforeCheckout(PruneStaleBranch.java:31) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:858) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557) at hudson.model.Run.execute(Run.java:1665) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Caused by: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null at org.eclipse.jgit.transport.URIish.init(URIish.java:205) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.listRemoteBranches(JGitAPIImpl.java:923) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.prune(JGitAPIImpl.java:901) ... 10 more }} 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] (JENKINS-20258) Git plugin with checkout to subdir and prune stale branches fails all builds
Mark Waite
edited a comment on JENKINS-20258
Git plugin with checkout to subdir and prune stale branches fails all builds
Git client plugin 1.5.0 was intended to fix this (based on the submission ba2ab8934), but it still fails.
Steps I used to duplicate the problem with Git client plugin 1.5.0:
Create a new job (I named mine git-jgit-specific-subdir-prune)
Configure git repo URL https://github.com/MarkEWaite/check_git.git
Use jgit as the implementation rather than the default
Add behavior to checkout to a local subdirectory
Add behavior to prune stale remote tracking branches
Save the job and run it
Stack trace looks like:
{{
Building on master in workspace /var/lib/jenkins/jobs/git-jgit-specific-subdir-prune-simple/workspace
Pruning obsolete local branches
FATAL: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null
hudson.plugins.git.GitException: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null
at org.jenkinsci.plugins.gitclient.JGitAPIImpl.prune(JGitAPIImpl.java:913)
at hudson.plugins.git.extensions.impl.PruneStaleBranch.beforeCheckout(PruneStaleBranch.java:31)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:858)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1411)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557)
at hudson.model.Run.execute(Run.java:1665)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:246)
Caused by: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null
at org.eclipse.jgit.transport.URIish.init(URIish.java:205)
at org.jenkinsci.plugins.gitclient.JGitAPIImpl.listRemoteBranches(JGitAPIImpl.java:923)
at org.jenkinsci.plugins.gitclient.JGitAPIImpl.prune(JGitAPIImpl.java:901)
... 10 more
}}
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] (JENKINS-20258) Git plugin with checkout to subdir and prune stale branches fails all builds
Mark Waite edited a comment on JENKINS-20258 Git plugin with checkout to subdir and prune stale branches fails all builds Git client plugin 1.5.0 was intended to fix this (based on the submission ba2ab8934), but it still fails. Steps I used to duplicate the problem with Git client plugin 1.5.0: Create a new job (I named mine git-jgit-specific-subdir-prune) Configure git repo URL https://github.com/MarkEWaite/check_git.git Use jgit as the implementation rather than the default Add behavior to checkout to a local subdirectory Add behavior to prune stale remote tracking branches Save the job and run it Stack trace looks like: Building on master in workspace /var/lib/jenkins/jobs/git-jgit-specific-subdir-prune-simple/workspace Pruning obsolete local branches FATAL: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null hudson.plugins.git.GitException: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null at org.jenkinsci.plugins.gitclient.JGitAPIImpl.prune(JGitAPIImpl.java:913) at hudson.plugins.git.extensions.impl.PruneStaleBranch.beforeCheckout(PruneStaleBranch.java:31) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:858) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557) at hudson.model.Run.execute(Run.java:1665) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Caused by: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null at org.eclipse.jgit.transport.URIish.init(URIish.java:205) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.listRemoteBranches(JGitAPIImpl.java:923) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.prune(JGitAPIImpl.java:901) ... 10 more 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] (JENKINS-20258) Git plugin with checkout to subdir and prune stale branches fails all builds
Mark Waite
updated JENKINS-20258
Git plugin with checkout to subdir and prune stale branches fails all builds
Change By:
Mark Waite
(17/Dec/13 2:35 AM)
Description:
Iconfiguredajobwiththegit2.0plugintocheckouttoaspecificsubdirectoryandtoprunestalebranches.Thatpairofconfigurationsettingscausetheinitialgitoperationstofailwithbothgitcommandlineandjgitimplementations.Thestacktraceforthecommandlineimplementationis:
{noformat}
StartedbyuseranonymousBuildingremotelyonalan-pcinworkspaceC:\J\workspace\git-multi-subdir-prunePruningobsoletelocalbranchesFATAL:Commandconfig--getremote.origin.urlreturnedstatuscode1:stdout:stderr:hudson.plugins.git.GitException:Commandconfig--getremote.origin.urlreturnedstatuscode1:stdout:stderr: atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:940) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:921) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:865) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:875) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteUrl(CliGitAPIImpl.java:603) athudson.plugins.git.GitAPI.getRemoteUrl(GitAPI.java:61) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.prune(CliGitAPIImpl.java:393) atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(UnknownSource) atjava.lang.reflect.Method.invoke(UnknownSource) athudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor.runWorker(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) athudson.remoting.Engine$1$1.run(Engine.java:63) atjava.lang.Thread.run(UnknownSource)
{noformat}
Thestacktraceforthejgitimplementationis:
{noformat}
StartedbyanSCMchangeStartedbyuseranonymousBuildingremotelyonwaite2011inworkspaceD:\J\workspace\git-multi-jgit-subdir-prunePruningobsoletelocalbranchesFATAL:java.net.URISyntaxException:CannotparseGitURI-ish:Theuriwasemptyornullhudson.plugins.git.GitException:java.net.URISyntaxException:CannotparseGitURI-ish:Theuriwasemptyornull atorg.jenkinsci.plugins.gitclient.JGitAPIImpl.prune(JGitAPIImpl.java:869) atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(UnknownSource) atjava.lang.reflect.Method.invoke(UnknownSource) athudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor.runWorker(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) athudson.remoting.Engine$1$1.run(Engine.java:63) atjava.lang.Thread.run(UnknownSource)Causedby:java.net.URISyntaxException:CannotparseGitURI-ish:Theuriwasemptyornull atorg.eclipse.jgit.transport.URIish.init(URIish.java:205) atorg.jenkinsci.plugins.gitclient.JGitAPIImpl.listRemoteBranches(JGitAPIImpl.java:879) atorg.jenkinsci.plugins.gitclient.JGitAPIImpl.prune(JGitAPIImpl.java:857) ...16more
{noformat}
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Mark Waite
updated JENKINS-20356
Git CLI cannot clone on Windows using GIT_SSH to set credentials
Change By:
Mark Waite
(17/Dec/13 2:38 AM)
Description:
AgitjobconfiguredtousethecommandlineimplementationwithGitplugin2.0andgitclientplugin1.4.6failstocloneonWindows,butsuccessfullyclonesonLinux.Theproblemseemstobethatitistryingtoconfigureanenvironment(settingSSH_PASS=echo)forthelaunchedcommand,eventhoughWindowsdoesnotusethesametechniquetopassenvironmentvariablestoaprocess.Ithinktherewasadifferentbehaviorinpriorversionsofgit-client.Icreatedthejobby:
0-
#
Configureaglobalsshcredential
1-
#
Createanewjob,restrictittoonlyrunonWindows
2-
#
UseagitsshprotocolURL(likessh://wheezy64b/var/cache/git/mwaite/bin.git)
3-
#
Selectthecorrectsshcredentialfromthedropdownlist
4-
#
Addabuildstep(IusedXShellechohelloworld)
5-
#
Savethejob
6-
#
RunthejobStacktraceonWindows:
{noformat}
StartedbyuseranonymousBuildingremotelyonalan-pcinworkspaceC:\J\workspace\git-cli-sshCloningtheremoteGitrepositoryCloningrepositoryssh://wheezy64b/var/cache/git/mwaite/bin.gitgit--versiongitversion1.8.3.msysgit.0usingGIT_SSHtosetcredentialsJenkinsERROR:Errorcloningremoterepooriginhudson.plugins.git.GitException:Couldnotclonessh://wheezy64b/var/cache/git/mwaite/bin.git atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:310) atorg.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:151) atorg.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:144) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor.runWorker(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) athudson.remoting.Engine$1$1.run(Engine.java:63) atjava.lang.Thread.run(UnknownSource)Causedby:hudson.plugins.git.GitException:Commandclone--progress-ooriginssh://wheezy64b/var/cache/git/mwaite/bin.gitC:\J\workspace\git-cli-sshreturnedstatuscode128:stdout:CloningintoC:\J\workspace\git-cli-ssh...stderr:error:cannotspawnC:\Users\Alan\AppData\Local\Temp\ssh3783977685963347919.exe:Nosuchfileordirectoryfatal:unabletofork atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:981) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:920) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:64) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:308) ...11moreERROR:nullFinished:FAILURE
{noformat}
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] (JENKINS-21030) Git CLI cannot clone on Windows if Git is in non-default location
Mark Waite created JENKINS-21030 Git CLI cannot clone on Windows if Git is in non-default location Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git, git-client Created: 17/Dec/13 2:58 AM Description: The GIT_SSH fix for JENKINS-20356 only works if the Git program is installed in the default location on Windows. I had installed to a different location and had updated the PATH variable to find that non-default location. All the typical plugin operations worked, except this recently added code for JENKINS-20356 was not able to find ssh.exe. The message is misleading, since the issue is not that the plugin only supports official git client. The plugin could not find the ssh.exe program on the simple paths it checked. Unfortunately, it did not search the PATH, it only searched in the ProgramFiles directory, and I had installed to a different drive in order to save space on a small disc that was hosting ProgramFiles. Stack trace looks like this: Started by user anonymous Building remotely on alan-pc in workspace C:\J\workspace\JENKINS-20356 Cloning the remote Git repository Cloning repository ssh://wheezy64b/var/cache/git/mwaite/bin.git Fetching upstream changes from ssh://wheezy64b/var/cache/git/mwaite/bin.git using GIT_SSH to set credentials Jenkins FATAL: git plugin only support official git client http://git-scm.com/download/win java.lang.RuntimeException: git plugin only support official git client http://git-scm.com/download/win at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.createWindowsGitSSH(CliGitAPIImpl.java:1053) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:963) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:68) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:217) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:349) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) 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:63) at java.lang.Thread.run(Unknown Source) Environment: Windows Git client plugin 1.5.0 Git plugin 2.0 Project: Jenkins Priority: Minor Reporter: Mark Waite 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] [subversion] (JENKINS-20690) Subversion changes using Assembla
Yoichi Nakayama commented on JENKINS-20690 Subversion changes using Assembla When "(Auto)" is selected, it searches for a job which uses same SCM class and SCMDescriptor#isBrowserReuseable() returns true. If the one is found, select same browser. For SubversionSCM case, it searches a job which uses same repository URL (obtained by SvnHelper#getUrlWithoutRevision). Do you have any other project which uses same repository URL and "Repository browser" = "Assembla"? 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-19142) Don't add jobs to a view
Yoichi Nakayama commented on JENKINS-19142 Dont add jobs to a view Daniel, I understand that there is no need to add job into View automatically, for your use case. How about introducing a global config disable/enable the behavior? 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-19142) Don't add jobs to a view
Yoichi Nakayama edited a comment on JENKINS-19142 Dont add jobs to a view Daniel, I understand that there is no need to add job into View automatically, for your use case. How about introducing a global config to disable/enable the behavior? 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] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Mark Waite closed JENKINS-20356 as Fixed Git CLI cannot clone on Windows using GIT_SSH to set credentials Confirmed closed in git client plugin 1.5.0. Change By: Mark Waite (17/Dec/13 4:26 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Mark Waite updated JENKINS-20569 Polling with excluded regions dont prevent job triggered Change By: Mark Waite (17/Dec/13 4:30 AM) Priority: Blocker Minor 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] [postbuildscript] (JENKINS-21031) Add checkbox for every build status
Jacky Zhang created JENKINS-21031 Add checkbox for every build status Issue Type: Improvement Assignee: Gregory Boissinot Components: postbuildscript Created: 17/Dec/13 5:48 AM Description: Currently we want to run some scripts when build is successful or unstable. But scripts can only be triggered when build is successful. And I saw there was a request to run scripts when job is failed. But Can we add checkbox for every build status? So we don't need to deal with such request. Project: Jenkins Priority: Major Reporter: Jacky Zhang 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-9913) Not obvious why some post-build tasks enforce serial behavior even when builds are concurrent
Not Again commented on JENKINS-9913 Not obvious why some post-build tasks enforce serial behavior even when builds are concurrent Got bitten by the same thing. Now planning to move the post build stuff into an additional last step of the build job. Only problem is that I need to get data from the slave to master before that. And that is also a Post build action (I use Copy-To-Slave plugin). Any way I can do it as a part of build job 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21032) git executable should be determined by node, not by the host
Orgad Shaneh created JENKINS-21032 git executable should be determined by node, not by the host Issue Type: Bug Assignee: Nicolas De Loof Components: git-client Created: 17/Dec/13 6:47 AM Description: A Windows host with a Linux node tries to execute "git.exe", which fails. To workaround it, I added a softlink. Project: Jenkins Priority: Major Reporter: Orgad Shaneh 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] [mailer] (JENKINS-20954) Cannot save email recipients
epikur2412 commented on JENKINS-20954 Cannot save email recipients I installed Version 1.7 , added an email recipient, but all email recipients were deleted. (Maven2/3-Job, Jenkins 1544, Linux) 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] [mailer] (JENKINS-20954) Cannot save email recipients
Dejan Stojadinovic commented on JENKINS-20954 Cannot save email recipients Thanks for resolving this so quickly Jesse Glick 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] [build-failure-analyzer] (JENKINS-17658) Provide a token so that build failure causes can be included in build failure emails
Adam Guja
commented on JENKINS-17658
Provide a token so that build failure causes can be included in build failure emails
jelly script for obtaining information from Build Failure Analyzer plugin and using it in Email ext plugin
Many thanks to Robert Sandell (one of the developers of BFA) for assisting me in creating this snippet!
html_causes.jelly
j:jelly xmlns:j="jelly:core" xmlns:st="jelly:stapler" xmlns:d="jelly:define"
BODY
j:set var="failureCauses" value="${it.getAction('com.sonyericsson.jenkins.plugins.bfa.model.FailureCauseBuildAction').getFoundFailureCauses()}"/
j:if test="${failureCauses.size() gt 0}"
j:forEach var="cause" items="${failureCauses}"
${cause.name}
br/
${cause.description}
br/
/j:forEach
/j:if
/BODY
/j: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
--
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-20989) PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered
Geoff Cummings
commented on JENKINS-20989
PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered
Some of the downstream builds might be configured for All, lastCompleted, lastSuccessful and others for lastStable. Multiple downstream builds might have different requirements. It would be better to have this config in one place, the downstream jobs, and not have to work around this change and require additional logic in the upstream build to determine what RunParameter to pass to the downstream job.
It worked as expected when the Run#getLastStableBuild used to be like:
public RunT getLastStableBuild() {
RunT r = getLastBuild();
while (r != null
(r.isBuilding() || r.getResult().isWorseThan(Result.SUCCESS)))
r = r.getPreviousBuild();
return r;
}
It no longer works after it was changed to use the Permalink
public RunT getLastStableBuild() {
return (RunT)Permalink.LAST_STABLE_BUILD.resolve(this);
}
The State.POST_PRODUCTION seems to be for this very scenario, where the build result is now final and it is now ok to trigger other builds as described in JENKINS-980
private static enum State {
/**
* Build is completed now, and the status is determined,
* but log files are still being updated.
*
* The significance of this state is that Jenkins
* will now see this build as completed. Things like
* "triggering other builds" requires this as pre-condition.
* See JENKINS-980.
*/
POST_PRODUCTION,
In the Run#execute method, I think we should update the PeepholePermalinks as soon as we change state and before we trigger fireCompleted on the listeners
Currently the Permalinks are updated in a fireCompleted event on a listener, the same as triggering downstream jobs. But they seem to be updated after the other builds are triggered.
// advance the state.
// the significance of doing this is that Jenkins
// will now see this build as completed.
// things like triggering other builds requires this as pre-condition.
// see issue #980.
//
state = State.POST_PRODUCTION;
if (listener != null) {
try {
job.cleanUp(listener);
} catch (Exception e) {
handleFatalBuildProblem(listener,e);
// too late to update the result now
}
RunListener.fireCompleted(this,listener);
listener.finished(result);
listener.closeQuietly();
}
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.
