[JIRA] [parameterized-trigger] (JENKINS-8952) Not Expanding Environment Variable
Nathan Nutter commented on JENKINS-8952 Not Expanding Environment Variable Thanks for the follow up and suggestion. 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-21110) Git Publisher failes because remote.origin.url is not set
Nathan Nutter created JENKINS-21110 Git Publisher failes because remote.origin.url is not set Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 20/Dec/13 4:25 PM Description: I saw a comment that may be the basis of the problem: git-plugin 2.0 don't use remote.foo.url anymore The error is very similar to JENKINS-20258 but this is occurring in the Git Publisher Post-build Actions: 07:23:10 Started by an SCM change 07:23:10 Building on master in workspace XXX 07:23:10 Fetching changes from the remote Git repository 07:23:10 Fetching upstream changes from ssh://XXX.git 07:23:20 Checking out Revision XXX (origin/perl-tests) 07:23:23 Cleaning workspace 07:23:23 Resetting working tree 07:23:24 Triggering XXX 07:59:13 XXX completed with result SUCCESS 07:59:13 Pushing HEAD to branch XXX at repo origin 07:59:14 ERROR: Failed to push branch XXX to origin 07:59:14 hudson.plugins.git.GitException: Command "git config --get remote.origin.url" returned status code 1: 07:59:14 stdout: 07:59:14 stderr: 07:59:14 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1099) 07:59:14 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1076) 07:59:14 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:917) 07:59:14 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:927) 07:59:14 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteUrl(CliGitAPIImpl.java:656) 07:59:14 at hudson.plugins.git.GitAPI.getRemoteUrl(GitAPI.java:61) 07:59:14 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.push(CliGitAPIImpl.java:1129) 07:59:14 at hudson.plugins.git.GitAPI.push(GitAPI.java:65) 07:59:14 at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:303) 07:59:14 at hudson.plugins.git.GitPublisher$1.endBuild(GitPublisher.java:138) 07:59:14 at hudson.matrix.MatrixBuild$MatrixBuildExecution.post2(MatrixBuild.java:403) 07:59:14 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) 07:59:14 at hudson.model.Run.execute(Run.java:1703) 07:59:14 at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) 07:59:14 at hudson.model.ResourceController.execute(ResourceController.java:88) 07:59:14 at hudson.model.Executor.run(Executor.java:231) 07:59:14 at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) 07:59:14 Notifying upstream projects of job completion 07:59:14 Finished: SUCCESS Environment: Jenkins ver. 1.544 Jenkins GIT plugin ver. 2.0 Jenkins GIT client plugin ver. 1.6.0 Project: Jenkins Priority: Major Reporter: Nathan Nutter 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-21110) Git Publisher fails because remote.origin.url is not set
Nathan Nutter updated JENKINS-21110 Git Publisher fails because remote.origin.url is not set Change By: Nathan Nutter (20/Dec/13 4:30 PM) Summary: GitPublisher failes fails becauseremote.origin.urlisnotset 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-20461) Git Plugin 2.0: fails to clone repo
Nathan Nutter commented on JENKINS-20461 Git Plugin 2.0: fails to clone repo This does seem to be a duplicate of JENKINS-20258. 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-9016) Git creates usernames based on 'name' not the email.
Nathan Nutter commented on JENKINS-9016 Git creates usernames based on name not the email. The only two "modes" at the moment (v2.0) seem to be either user.name or user.email not the username from user.email? The latter being the suggested default "mode" in v1.1.7: If no Jenkins user is found for a commit's user.name value, strip the username from "usern...@domain.com" from the user.email value and use that instead. We want users to be associated with just their username not their full email and not their user.name so that other things can automatically work, e.g. the Jabber Plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-9016) Git creates usernames based on 'name' not the email.
Nathan Nutter edited a comment on JENKINS-9016 Git creates usernames based on name not the email. The only two "modes" at the moment (v2.0) seem to be either user.name or user.email not the username from user.email? The latter being the suggested default "mode" in v1.1.7: If no Jenkins user is found for a commit's user.name value, strip the username from "usern...@domain.com" from the user.email value and use that instead. We want users to be associated with just their username not their full email and not their user.name so that other things can automatically work, e.g. the Jabber Plugin. Also, the users log in, via LDAP, with just their username. 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-9016) Git creates usernames based on 'name' not the email.
Nathan Nutter edited a comment on JENKINS-9016 Git creates usernames based on name not the email. The only two "modes" at the moment (v2.0) seem to be either user.name or user.email not the username from user.email? The latter being the suggested default "mode" in v1.1.7: If no Jenkins user is found for a commit's user.name value, strip the username from "usern...@domain.com" from the user.email value and use that instead. We want users to be associated with just their username not their full email and not their user.name so that other things can automatically work, e.g. the Jabber Plugin. Also, the users loging, via LDAP, with just their username. 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-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Nathan Nutter commented on JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH I noticed the same problem. I'll be updating my scripts for now. It would be nice to know whether this will be a Won't Fix issue, i.e. a "feature" of 2.0, or whether it might be reverted back to the old 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] [junit] (JENKINS-18148) JUnit Test Result Report Silently Ignores Files With Old Timestamps?
Nathan Nutter created JENKINS-18148 JUnit Test Result Report Silently Ignores Files With Old Timestamps? Issue Type: Bug Assignee: Unassigned Components: junit Created: 30/May/13 3:23 PM Description: We recently had an issue where the clock on our Jenkins server was ahead by about 15 minutes which caused the test result files (that are generated on other machines and shared over NFS) to appear 15 minutes old to Jenkins. In one case where the test suite takes less than that 15 minutes it correctly guessed that something was wrong and displayed a message like: 10:20:01 Test reports were found but none of them are new. Did tests run? 10:20:01 For example, /gscmnt/gc13001/info/model_data/apipe-ci/workspace/0-Genome-Perl-Tests-Quick/PERL_VERSION=5.10/PERL_VERSION/5.10/test_results/Model/Tools/Validation/Sciclone.t.junit.xml is 15 min old However, for another test suite that takes about 40 minutes it appears to have just silently ignored old files which caused it to report all tests as passing despite one of the tests failing. From the console log: ... 18:40:08 * ./Model/Command/Services/WebApp/Core.t STDERR * 18:40:08 Waiting for dispatch ... 18:40:08 Starting on blade10-2-11.gsc.wustl.edu 18:40:08 Job 5231505 is submitted to queue short. 18:40:08 * ... 19:07:37 testsuite failures="1" 19:07:37 errors="0" 19:07:37 time="0.0159821510314941" 19:07:37 tests="3" 19:07:37 name="Model_Command_Services_WebApp_Core_t" But then the test report make no mention of this test. It also appears to be missing about 6k tests from the normal 16k tests run. Allowing a test failure to be reported as success seems absolutely undermining. Is it possible I could have configured Jenkins to prevent this problem? Or is this possible a critical bug (that has a low? chance of occurring)? Environment: Jenkins ver. 1.511 Linux vm86.gsc.wustl.edu 2.6.32-36-server #79-Ubuntu SMP Tue Nov 8 22:44:38 UTC 2011 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 10.04.4 LTS Release:10.04 Codename: lucid Project: Jenkins Priority: Major Reporter: Nathan Nutter 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.
