[JIRA] [vsphere-cloud] (JENKINS-22025) VM cannot be started repeatedly with vSphere plugin
Jerry Maloney commented on JENKINS-22025 VM cannot be started repeatedly with vSphere plugin Eric Lordahl, that was, in fact, my problem. I didn't have VMware tools installed and so the VM did not have an IP assigned. Thanks for the help! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud] (JENKINS-22025) VM cannot be started repeatedly with vSphere plugin
Jerry Maloney commented on JENKINS-22025 VM cannot be started repeatedly with vSphere plugin I rebuilt the plugin using your latest change, but it did not fix my problem. The more I think about it, the more I think the fact that it works for one target VM but not another target VM suggests that the problem is not the plugin, but rather the configuration of my VMs. It is probably just coincidental that the error I am getting is similar to this one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud] (JENKINS-22025) VM cannot be started repeatedly with vSphere plugin
Jerry Maloney commented on JENKINS-22025 VM cannot be started repeatedly with vSphere plugin I'm seeing similar behavior. I'm just getting started with this plugin and I'm running very simple tests right now on two VMs. For both VMs, the Jenkins job A. creates a file at /tmp/AppIsInstalled B. reverts the VM C. powers on the VM D. verifies that /tmp/AppIsInstalled (thus verifying that the app is no longer installed in my toy scenario) This succeeds on one VM and fails on another. The failure is: SSH: Connecting from host [jenkins] SSH: Connecting with configuration [NPD-ars-app-01.builder] ... SSH: EXEC: STDOUT/STDERR from command [# the next line installs ARS echo "this file means ARS is installed and working" /tmp/ArsIsInstalled ] ... SSH: EXEC: completed after 202 ms SSH: Disconnecting configuration [NPD-ars-app-01.builder] ... SSH: Transferred 0 file(s) [vSphere] [vSphere] Performing vSphere build step: "Revert to Snapshot" [vSphere] Attempting to use server configuration: "NPD vSphere" [vSphere] Reverting to snapshot "base" for VM phlq1cfldars001... [vSphere] Complete. [vSphere] [vSphere] Performing vSphere build step: "Power-On/Resume VM" [vSphere] Attempting to use server configuration: "NPD vSphere" [vSphere] Waiting for IP (VM may be restarted during this time) [vSphere] Error: Could not get IP for "phlq1cfldars001" Build step 'vSphere Build Step' marked build as failure Notifying upstream projects of job completion Finished: FAILURE The succeeding output is: SSH: Connecting from host [jenkins] SSH: Connecting with configuration [NPD-cds-grid01.builder] ... SSH: EXEC: STDOUT/STDERR from command [# the next line installs CDS (this is much easier than you thought it was) echo "this file means CDS is installed and working" /tmp/CdsIsInstalled] ... SSH: EXEC: completed after 202 ms SSH: Disconnecting configuration [NPD-cds-grid01.builder] ... SSH: Transferred 0 file(s) [vSphere] [vSphere] Performing vSphere build step: "Revert to Snapshot" [vSphere] Attempting to use server configuration: "NPD vSphere" [vSphere] Reverting to snapshot "base" for VM phlpdccdsgrd001... [vSphere] Complete. [vSphere] [vSphere] Performing vSphere build step: "Power-On/Resume VM" [vSphere] Attempting to use server configuration: "NPD vSphere" [vSphere] Waiting for IP (VM may be restarted during this time) [vSphere] Successfully retrieved IP for "phlpdccdsgrd001" : 10.114.72.20 SSH: Connecting from host [jenkins] SSH: Connecting with configuration [NPD-cds-grid01.builder] ... SSH: EXEC: STDOUT/STDERR from command [# after revert, check to make sure CDS is not installed ls /tmp/CdsIsInstalled # we expect this to be missing if [ $? -eq 2 ]; then exit 0 else exit 1 fi ] ... ls: cannot access /tmp/CdsIsInstalled: No such file or directory SSH: EXEC: completed after 407 ms SSH: Disconnecting configuration [NPD-cds-grid01.builder] ... SSH: Transferred 0 file(s) Notifying upstream projects of job completion Finished: SUCCESS Now on the VM where it fails, everything works correctly, by which I mean the VM is reverted and restarted, and the /tmp file is deleted. I can verify this manually. The only part that fails is where Jenkins fails to return to the program flow. I don't know enough about vSphere to know if this is something about how the failing VM is configured. I'm talking with my data center folks to try to figure this out, but this ticket looks so similar to my behavior that I wonder if it is the same cause. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-15746) Cannot run SSH commands on SSH servers that use Windows shell
Jerry Maloney commented on JENKINS-15746 Cannot run SSH commands on SSH servers that use Windows shell The original pull request was somehow left out, even after being approved. Since the fix was 2 characters, I found it easier to delete the old fork and create a new one, then create a new pull request: https://github.com/jenkinsci/ssh-slaves-plugin/pull/12 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-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jerry Maloney commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification I believe there may be an issue in MercurialChangeLogParser method MercurialChangeSetList parse(AbstractBuild build, File changelogFile). If I pass in a changelog that looks like the following: changelog.xml ?xml version='1.0' encoding='UTF-8'? changesets changeset author='joe.schmo lt;joe.sc...@example.comgt;'/ !-- note that those escape characters are on purpose and not some relic of posting in Jira -- /changesets I get a changeset author with the ID and fullname "joe.schmo joe.sc...@example.com", which is the error reported in this ticket. I believe the Digester class from Apache Commons is taking the escaped XML characters in the changesets/changeset/@author attribute and rendering them as underscores. I pushed a unit test showing this to my fork of mercurial-plugin, but not requesting a pull because I don't have a fix yet. 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] [ssh-slaves] (JENKINS-15746) Cannot run SSH commands on SSH servers that use Windows shell
Jerry Maloney commented on JENKINS-15746 Cannot run SSH commands on SSH servers that use Windows shell Is this pull request scheduled for inclusion in a release of the plugin? Thanks, Jerry 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-17409) looselyMatches throws exception if second parameter (repository) is null
Jerry Maloney commented on JENKINS-17409 looselyMatches throws exception if second parameter (repository) is null Additional commit for the same pull request addresses Jesse's suggestions. 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] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
Jerry Maloney created JENKINS-17409 looselyMatches throws exception if second parameter (repository) is null Issue Type: Bug Affects Versions: current Assignee: Jerry Maloney Components: mercurial Created: 29/Mar/13 2:06 PM Description: Version 1.506 of Jenkins and version 1.44 of the Mercurial plugin. My users were having the issue that, when working against a repository that has an hg hook that triggers a Jenkins job, running hg push from a console would cause the process to hang permanently, until it was killed. I tracked down the issue to a NullPointerException that was not handled by handleNotifyCommit. This only occurs if there is at least one Jenkins project that (A) has Source Code Management enabled and (B) does not have a Repository URL entered. This is a situation that shouldn't happen there's no use case for it but in an environment where we let individual developers control their own Jenkins projects, mistakes happen. Everyone in the organization should not suffer because of another developer's mistake. Project: Jenkins Priority: Minor Reporter: Jerry Maloney 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] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
Jerry Maloney commented on JENKINS-17409 looselyMatches throws exception if second parameter (repository) is null Fixed with this commit. I sent a pull request. 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] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
Jerry Maloney started work on JENKINS-17409 looselyMatches throws exception if second parameter (repository) is null Change By: Jerry Maloney (29/Mar/13 2:42 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] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
Jerry Maloney commented on JENKINS-17409 looselyMatches throws exception if second parameter (repository) is null Not sure what the protocol is here should I Resolve Issue now, or when (if) the pull request is accepted? 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] (JENKINS-15704) Incomplete list of builds when I go to JobName/api/json
Jerry Maloney commented on JENKINS-15704 Incomplete list of builds when I go to JobName/api/json I have this issue as well. The json object returned only ever includes ten builds, even though there are really many more than that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15746) Cannot run SSH commands on SSH servers that use Windows shell
Jerry Maloney commented on JENKINS-15746 Cannot run SSH commands on SSH servers that use Windows shell I put in a pull request for the fix: https://github.com/jenkinsci/ssh-slaves-plugin/pull/7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15746) Cannot run SSH commands on SSH servers that use Windows shell
Jerry Maloney started work on JENKINS-15746 Cannot run SSH commands on SSH servers that use Windows shell Change By: Jerry Maloney (06/Nov/12 7:54 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
