[JIRA] [cvs] (JENKINS-17656) CVS symbolic name parameter
Barthélémy von Haller commented on JENKINS-17656 CVS symbolic name parameter I am new to Jenkins, thus I can't really help. However, I have tried with different CVS projects and always got that. I thought it could be due to spaces in the tag names, but as far as I can see it is not the case. 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] [safe-restart] (JENKINS-12574) Provide a better image
SCM/JIRA link daemon resolved JENKINS-12574 as Fixed Provide a better image Change By: SCM/JIRA link daemon (19/Apr/13 6:33 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] [safe-restart] (JENKINS-12574) Provide a better image
SCM/JIRA link daemon commented on JENKINS-12574 Provide a better image Code changed in jenkins User: Seiji Sogabe Path: pom.xml src/main/webapp/images/24x24/quick_restart.png src/main/webapp/images/48x48/quick_restart.png http://jenkins-ci.org/commit/saferestart-plugin/51be0ccf717ec0f0b91830c811a0a7c9b3f2bab6 Log: FIXED JENKINS-12574 Provide a better image 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] [matrix] (JENKINS-3234) checkboxes for combination-filter
Jos Decoster commented on JENKINS-3234 checkboxes for combination-filter As an alternative, would it be possible to make the make the filter entry a multi-line entry which keeps the newlines info? That would make editing filters a lot easier. 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] [matrix] (JENKINS-3234) checkboxes for combination-filter
Jos Decoster edited a comment on JENKINS-3234 checkboxes for combination-filter As an alternative, would it be possible to make the filter entry a multi-line entry which keeps the newlines info? That would make editing filters a lot easier. 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-15070) Login via Active Directory with a valid user without read rights gives an Error 404
Miquel Martin commented on JENKINS-15070 Login via Active Directory with a valid user without read rights gives an Error 404 I would have expected a 403 forbidden: "The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead." 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-17208) Link to affected source from a warning does not function
David Jorm commented on JENKINS-17208 Link to affected source from a warning does not function Which plug-in versions are you using? findbugs 2.0.1 with TODO mvn plugin on Jenkins ver. 1.480.2-SNAPSHOT Is this the only source that does not show up? All source links from the jenkin findbugs results fail to show up in the same way. Is the source file generated? No. Is there a corresponding log message in the console log of your job? No, the job executes with no log messages of note, everything is clean. What is the source path of the warning in the file that is generated from findbugs? I am sorry I am having trouble understanding exactly what you mean here. What do you mean by the file that is generated from findbugs? Is that the same as findbugs-warnings.xml ? Upon further analysis I can see that the source package does not have findbugs-maven-plugin configured in its POM. Is that a possible cause of this problem? 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] [mstest] (JENKINS-8805) Problem with MSTest post build action with following message: FATAL: No MSTest TRX test report files were found. Configuration error?
Vishal Gupta commented on JENKINS-8805 Problem with MSTest post build action with following message: FATAL: No MSTest TRX test report files were found. Configuration error? What have have you provided in publish Mstest result report ?? In your case it should be relative to your workspace. Example : publish Mstest result report : trunk\build\TestOutput\results.trx 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-14057) With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails
schtefan updated JENKINS-14057 With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails Attached complete stack trace of error message Change By: schtefan (19/Apr/13 8:25 AM) Attachment: Stacktrace1.txt 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] [cvs] (JENKINS-17656) CVS symbolic name parameter
Nicolas Martin
edited a comment on JENKINS-17656
CVS symbolic name parameter
it's difficult to guess what is wrong, as in the CVS plugin, the same error message is thrown by 4 different exceptions ...
CvsTagsParamDefinition.java :
catch(IOException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (CommandAbortedException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (CommandException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
};
} catch (AuthenticationException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
}
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] [cvs] (JENKINS-17656) CVS symbolic name parameter
Nicolas Martin
commented on JENKINS-17656
CVS symbolic name parameter
it's difficult to guess what is wrong, as in the CVS plugin, the same error message is thrown by 4 different exceptions ...
CvsTagsParamDefinition.java :
catch(IOException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (CommandAbortedException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
}
} catch (CommandException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (AuthenticationException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
}
}
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-17178) Upstream job name/link not listed when job at the bottom of hierarchy
stenudd commented on JENKINS-17178 Upstream job name/link not listed when job at the bottom of hierarchy Please fix this issue as soon as possible. This issue is causing probelms in various 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] [update-center] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Potroshitel Jack created JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 Issue Type: Bug Assignee: Unassigned Components: update-center Created: 19/Apr/13 8:50 AM Description: I encountered an issue that seems that should be fixed since i saw it appear in JIRA a couple of times before. When installing a fresh Jenkins LTS 1.480.3 release on Windows Server 2008 R2 x64 I can't find any plugins in "Available" and "Updates" tabs. I receive the following error: Apr 19, 2013 1:34:59 AM hudson.model.UpdateSite doPostBack SEVERE: div class=errorimg src='' height=16 width=1Digest mismatch: 1Woxyt3oLgioZax7SGlbwYITc98= vs +JLZbigPye2eA9Fsv6sa3DW3q2s= in update center default/div I have tried the latest Jenkins version and I don't receive this issue. The thing is - i want to go with the LTS version since i'm installing it on a PROD environment. Environment: Windows Server 2008 R2 x64 with latest updates (or without them) Fix Versions: current Project: Jenkins Labels: plugin Priority: Blocker Reporter: Potroshitel Jack 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.
Maxime Ménard commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. I have the same issue if I upgrade Jenkins from 1.502 to the latest version. Debian 2.6.39-3 x86_64 java 1.6.0_26 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-16257) Active Directory Plugin - Credential exception tying to authenticate
Bjoern Becker commented on JENKINS-16257 Active Directory Plugin - Credential exception tying to authenticate Yes, maybe. How escape this in the plugin? I'll test everything. What can I do now? 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-17116) gracefull job termination
torbent commented on JENKINS-17116 gracefull job termination I am struggling with this as well! There is documentation which states that Jenkins uses SIGTERM to kill processes, but I too am having a hard time trapping it. One of the problems I have is that even if my script might trap the TERM, Jenkins appears to not wait for termination of the process(es) it has started. It's a bit difficult, then, to know whether the traps work or not when I cannot see the output. You should be aware that the bash build scripts are usually invoked with -e, which may "break" your error handling. Jenkins will list all of the processes you have started, including the sleep, and send a TERM to all of them. Your sleep then fails (before you can kill it), causing the rest of the script to fail. It looks like you may have worked around that to get the "Ending" text out, but it caught me and may confuse others trying to reproduce the problem The "list all of the processes" part involves an environment variable called BUILD_ID. See https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller By using a set +e (and maybe BUILD_ID=ignore so many experiments lately) I have managed to make my script ignore TERM, which can consistently lead to an orphaned bash. Jenkins is certain the build is aborted, but the script keeps running. I can kill the script (behind Jenkins) with -9, however. 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-17648) SSH Slaves Plugin 0.24: Exception while connection slaves
Johannes Luther commented on JENKINS-17648 SSH Slaves Plugin 0.24: Exception while connection slaves Great! Thanks! 0.25 works as expected - no problems with slaves anymore. 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] (JENKINS-17678) Connect to slave via SSH with key in a file fails whereas it works if pasted
Barthélémy von Haller created JENKINS-17678 Connect to slave via SSH with key in a file fails whereas it works if pasted Issue Type: Bug Assignee: stephenconnolly Components: ssh, ssh-agent, ssh-credentials, ssh-slaves Created: 19/Apr/13 9:35 AM Description: I have a master running with user XXX on a machine M1. I want to run a slave on machine M2 with user YYY. I have a private-public key in place between the two machines so that I can do XXX@M1$ ssh YYY@M2 and I am connected. In Jenkins, I created credentials for username M2 and selected the option From the Jenkins master ~/.ssh. But when I try to connect it fails : 04/18/13 14:58:11 SSH Opening SSH connection to M2:22. ERROR: Failed to authenticate as YYY with credential=c2cdc4dd-cb39-4f15-8329-033933ad5621 java.io.IOException: Publickey authentication failed. 04/18/13 14:58:11 SSH Authentication failed. hudson.AbortException: Authentication failed. Surprisingly, if I use the option Enter directly and copy paste the private key from ~/.ssh/id_dsa , then it works. What am I doing wrong ? is it that it takes ~/.ssh/id_rsa instead of id_dsa ? Environment: linux Project: Jenkins Labels: ssh Priority: Major Reporter: Barthélémy von Haller 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-14057) With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails
James Howe commented on JENKINS-14057 With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails The error is because your AD does not allow anonymous bind How does that account for the observation that the calls fail and succeed in alternation? 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-timeout] (JENKINS-17667) Unable to kill a job which is running
Aswini Rajasekaran commented on JENKINS-17667 Unable to kill a job which is running Any updates on this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-timeout] (JENKINS-17667) Unable to kill a job which is running
Aswini Rajasekaran updated JENKINS-17667 Unable to kill a job which is running Change By: Aswini Rajasekaran (19/Apr/13 10:12 AM) Priority: Trivial Major 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] (JENKINS-17678) Connect to slave via SSH with key in a file fails whereas it works if pasted
stephenconnolly commented on JENKINS-17678 Connect to slave via SSH with key in a file fails whereas it works if pasted The order of preference is: id_rsa, id_dsa, identity https://github.com/jenkinsci/ssh-credentials-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/BasicSSHUserPrivateKey.java#L348 So it will take ~/.ssh/id_rsa if that is present and only fall back to ~/.ssh/id_dsa if the id_rsa is missing. Where you have multiple keys and you need to specify explicitly one key, the recommendation is to either specify the path to the file or use copy paste 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] (JENKINS-17678) Connect to slave via SSH with key in a file fails whereas it works if pasted
stephenconnolly resolved JENKINS-17678 as Not A Defect Connect to slave via SSH with key in a file fails whereas it works if pasted Change By: stephenconnolly (19/Apr/13 10:23 AM) Status: Open Resolved Resolution: NotADefect 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] (JENKINS-17678) Connect to slave via SSH with key in a file fails whereas it works if pasted
stephenconnolly commented on JENKINS-17678 Connect to slave via SSH with key in a file fails whereas it works if pasted If you want to add a feature request to select an explicit one of those keys, then please open a separate ticket for the feature request. For now I don't see this as an issue as there are two valid work-arounds 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-17676) ADSI mode auth no longer working after update to AD plugin v 1.31
Kurt Loupal updated JENKINS-17676 ADSI mode auth no longer working after update to AD plugin v 1.31 Change By: Kurt Loupal (19/Apr/13 10:30 AM) Environment: Jenkins1.511 UE (UI accessedviaHTTPS ) ,JRE1.7.0_0764bitrunningonWin7ProSP164bit.Multipleslaves,allrunningWindows7orServer2008. 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] [grails] (JENKINS-7750) Grails Plugin - You can't use build.job.name=${env['JOB_NAME']} in the 'properties' box.
Alex Anderson
commented on JENKINS-7750
Grails Plugin - You cant use build.job.name=${env[JOB_NAME]} in the properties box.
Think this is fixed by https://github.com/jenkinsci/grails-plugin/pull/6
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-17585) tag this build improvement
herve_colliaux commented on JENKINS-17585 tag this build improvement Hello, Is there an easy way, i.e. by patching some files, to modify the default naming rule in the plugin ? Thanks for any 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/groups/opt_out.
[JIRA] [cvs] (JENKINS-17656) CVS symbolic name parameter
Nicolas Martin
edited a comment on JENKINS-17656
CVS symbolic name parameter
it's difficult to guess what is wrong, as in the CVS plugin, the same error message is thrown by 4 different exceptions ...
CvsTagsParamDefinition.java :
catch(IOException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (CommandAbortedException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (CommandException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
};
} catch (AuthenticationException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
}{/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] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Axel Bodemer commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. We have the same Issue. Red Hat Enterprise Linux Server release 5.9 (Tikanga) Java(TM) SE Runtime Environment (build 1.6.0_33-b03) tomcat5.x86_64 5.5.23-0jpp.38.el5_9 Jenkins 1.501 Publish Over SSH 1.10 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] [cvs] (JENKINS-17656) CVS symbolic name parameter
Nicolas Martin
edited a comment on JENKINS-17656
CVS symbolic name parameter
it's difficult to guess what is wrong, as in the CVS plugin, the same error message is thrown by 4 different exceptions ...
CvsTagsParamDefinition.java :
{nopanel} catch(IOException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (CommandAbortedException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (CommandException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
};
} catch (AuthenticationException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
}{/nopanel}
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] [cvs] (JENKINS-17656) CVS symbolic name parameter
Nicolas Martin
edited a comment on JENKINS-17656
CVS symbolic name parameter
it's difficult to guess what is wrong, as in the CVS plugin, the same error message is thrown by 4 different exceptions ...
CvsTagsParamDefinition.java
(...)
catch(IOException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (CommandAbortedException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (CommandException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
};
} catch (AuthenticationException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
}
(...)
{/code}
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] [cvs] (JENKINS-17656) CVS symbolic name parameter
Nicolas Martin
edited a comment on JENKINS-17656
CVS symbolic name parameter
it's difficult to guess what is wrong, as in the CVS plugin, the same error message is thrown by 4 different exceptions ...
CvsTagsParamDefinition.java
(...)
catch(IOException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (CommandAbortedException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (CommandException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (AuthenticationException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
}
(...)
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] [cvs] (JENKINS-17656) CVS symbolic name parameter
Nicolas Martin
edited a comment on JENKINS-17656
CVS symbolic name parameter
it's difficult to guess what is wrong, as in the CVS plugin, the same error message is thrown by 4 different exceptions ...
CvsTagsParamDefinition.java :
{nopanel} catch(IOException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (CommandAbortedException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (CommandException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
};
} catch (AuthenticationException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
}
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] [cvs] (JENKINS-17656) CVS symbolic name parameter
Nicolas Martin
edited a comment on JENKINS-17656
CVS symbolic name parameter
it's difficult to guess what is wrong, as in the CVS plugin, the exact same error message is thrown by 4 different exceptions ...
CvsTagsParamDefinition.java
(...)
catch(IOException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (CommandAbortedException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (CommandException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
} catch (AuthenticationException ex) {
model.add(new ListBoxModel.Option("Could not load symbolic names - " + ex.getLocalizedMessage()));
return model;
}
(...)
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-17208) Link to affected source from a warning does not function
Ulli Hafner commented on JENKINS-17208 Link to affected source from a warning does not function Upon further analysis I can see that the source package does not have findbugs-maven-plugin configured in its POM. Is that a possible cause of this problem? Which source package? Do you have multiple maven modules? I am sorry I am having trouble understanding exactly what you mean here. What do you mean by the file that is generated from findbugs? Is that the same as findbugs-warnings.xml ? No, it is the output of the maven-findbug-plugin: it is located in your target folder, findbugsResult.xml or something like 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 -- 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] (JENKINS-17678) Connect to slave via SSH with key in a file fails whereas it works if pasted
Barthélémy von Haller commented on JENKINS-17678 Connect to slave via SSH with key in a file fails whereas it works if pasted I think it is good as it is. Maybe the only thing is to document this in the official documentation where it was not mentioned. Thank you very much for you 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17546) New Trigger: broken build - compiling build (unstable/stable)
SCM/JIRA link daemon commented on JENKINS-17546 New Trigger: broken build - compiling build (unstable/stable) Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/trigger/BuildingTrigger.java src/main/resources/hudson/plugins/emailext/plugins/trigger/Messages.properties src/test/java/hudson/plugins/emailext/plugins/trigger/BuildingTriggerTest.java src/test/java/hudson/plugins/emailext/plugins/trigger/FirstFailureTriggerTest.java src/test/java/hudson/plugins/emailext/plugins/trigger/NthFailureTriggerTestBase.java src/test/java/hudson/plugins/emailext/plugins/trigger/SecondFailureTriggerTest.java src/test/java/hudson/plugins/emailext/plugins/trigger/TriggerTestBase.java http://jenkins-ci.org/commit/email-ext-plugin/3ea1848751f762f26674c7a8d92023bbe59d4117 Log: Fixed JENKINS-17546 Added new trigger BuildingTrigger that is triggered on the transition from Failure to Unstable. 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] [email-ext] (JENKINS-17546) New Trigger: broken build - compiling build (unstable/stable)
Alex Earl resolved JENKINS-17546 as Fixed New Trigger: broken build - compiling build (unstable/stable) Added new Building trigger for the transition from Failure to Unstable. Change By: Alex Earl (19/Apr/13 11:39 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] [git] (JENKINS-17679) Git plugins crashes with exception for jobs using git merging features
Johannes Wienke created JENKINS-17679 Git plugins crashes with exception for jobs using git merging features Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 19/Apr/13 11:40 AM Description: Several of out build jobs using git are broken since some of the last version of the git plugin. They are crashing already in the main job triggering the individual builds with the following exception: Commencing build of Revision 5dc28f3d5e0787318df51a9cc58fdf712273ec7b (origin/bug-1175) hudson.util.IOException2: remote file operation failed: /home/jenkins/workspace/rsb-cpp-trunk-merge-simulator at hudson.remoting.Channel@44a89714:ubuntu_quantal_64bit at hudson.FilePath.act(FilePath.java:900) at hudson.FilePath.act(FilePath.java:877) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1121) at hudson.model.AbstractProject.checkout(AbstractProject.java:1367) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:674) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:579) at hudson.model.Run.execute(Run.java:1575) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@18379284 at hudson.remoting.UserRequest.serialize(UserRequest.java:166) at hudson.remoting.UserRequest.init(UserRequest.java:62) at hudson.remoting.Channel.call(Channel.java:671) at hudson.FilePath.act(FilePath.java:893) ... 10 more Caused by: java.io.NotSerializableException: hudson.matrix.MatrixBuild at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) at hudson.remoting.UserRequest._serialize(UserRequest.java:155) at hudson.remoting.UserRequest.serialize(UserRequest.java:164) ... 13 more Finished: FAILURE All of the crashing jobs are matrix jobs using git and merging from a separate branch. Other jobs with git without merging are not affected by this. We are currently using version 1.3.0 of the git plugin and this version is affected by this bug. Environment: Jenkins running on a debian master and multiple ubuntu linux slaves in different versions and with different JVM versions. Slaves are connected through ssh. Project: Jenkins Labels: git exception Priority: Blocker Reporter: Johannes Wienke 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
[JIRA] [core] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Jan Hoppe commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException I blogged a little bit about detecting that problem: http://devophuman.blogspot.com/2013/04/jenkins-is-going-wild.html 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-17553) Archived artifacts of Maven Modules are no longer cleaned up
Henrik Horneber commented on JENKINS-17553 Archived artifacts of Maven Modules are no longer cleaned up Same issue here, running 1.506. The script does not make any difference. Due to the number and size of our builds, this really is a problem for us. 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] [copyartifact] (JENKINS-17680) Upgrade to new Copy Artifacts version erases all job names to copy from
Johannes Wienke created JENKINS-17680 Upgrade to new Copy Artifacts version erases all job names to copy from Issue Type: Bug Assignee: Unassigned Components: copyartifact Created: 19/Apr/13 12:04 PM Description: After an update to the new copy artifacts version 1.26 existing configurations are broken because all job names to copy artifacts from are empty. The configuration files still contain the correct names, e.g.: hudson.plugins.copyartifact.CopyArtifact plugin="copyartifact@1.25" projectNamersc-trunk/label=$label/projectName filter*/.tar.gz/filter targetupstream/target selector class="hudson.plugins.copyartifact.StatusBuildSelector"/ flattentrue/flatten /hudson.plugins.copyartifact.CopyArtifact As you can see, most of our jobs use variables in the projectName tag. Maybe this is the reason for the problem. I actually cannot find a job without this, so I cannot verify this idea. With 1.25 everything is ok. Project: Jenkins Labels: copyartifact upgrade Priority: Critical Reporter: Johannes Wienke 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] [plugin] (JENKINS-16669) GitHub SQS Plugin works only once after project config
SCM/JIRA link daemon commented on JENKINS-16669 GitHub SQS Plugin works only once after project config Code changed in jenkins User: André Turgeon Path: src/main/java/com/base2services/jenkins/SqsBuildTrigger.java http://jenkins-ci.org/commit/github-sqs-plugin/db1c0595c218a39e439d881a891b9d6ad721ad34 Log: Fix for JENKINS-16669 and JENKINS-16617. 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-16617) Github SQS plugin not starting jobs on Jenkins 1.500
SCM/JIRA link daemon commented on JENKINS-16617 Github SQS plugin not starting jobs on Jenkins 1.500 Code changed in jenkins User: André Turgeon Path: src/main/java/com/base2services/jenkins/SqsBuildTrigger.java http://jenkins-ci.org/commit/github-sqs-plugin/db1c0595c218a39e439d881a891b9d6ad721ad34 Log: Fix for JENKINS-16669 and JENKINS-16617. 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] [gradle] (JENKINS-7702) Could not load Logmanager org.apache.juli.ClassLoaderLogManager
SCM/JIRA link daemon commented on JENKINS-7702 Could not load Logmanager org.apache.juli.ClassLoaderLogManager Code changed in jenkins User: Kiyotaka Oku Path: src/main/java/com/g2one/hudson/grails/GrailsBuilder.java http://jenkins-ci.org/commit/grails-plugin/3393e20cedea00162367804a8d3d2f579b602362 Log: Merge pull request #5 from jglick/JENKINS-7702 FIXED JENKINS-7702 Tomcat sometimes defines a $JAVA_OPTS inappropriate for subprocesses. Compare: https://github.com/jenkinsci/grails-plugin/compare/46a785348002...3393e20cedea 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] [gradle] (JENKINS-7702) Could not load Logmanager org.apache.juli.ClassLoaderLogManager
SCM/JIRA link daemon commented on JENKINS-7702 Could not load Logmanager org.apache.juli.ClassLoaderLogManager Code changed in jenkins User: Jesse Glick Path: src/main/java/com/g2one/hudson/grails/GrailsBuilder.java http://jenkins-ci.org/commit/grails-plugin/47586fa88e3c0886ceaae78d8703e15b8f5fd2f0 Log: FIXED JENKINS-7702 Tomcat sometimes defines a $JAVA_OPTS inappropriate for subprocesses. 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-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Fabian Tietz created JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 19/Apr/13 12:24 PM Description: The lastStable and LastSuccessful links are created as invalid symlinks with no destination under Windows. These Files cause the backup to fail, since they are not valid and cause all sorts of zip archivers to fail. Due Date: 19/Apr/13 12:00 AM Environment: Windows Server 2008, NTFS, Jenkins runs as Windows Service Project: Jenkins Priority: Major Reporter: Fabian Tietz 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] [update-center] (JENKINS-17029) update-center.json seems to be broken
andrew cooke
commented on JENKINS-17029
update-center.json seems to be broken
A diff against the current trunk to remove the checks is:
diff --git a/core/src/main/java/jenkins/util/JSONSignatureValidator.java b/core/src/main/java/jenkins/util/JSONSignatureValidator.java
index 684f8eb..641d25e 100644
a/core/src/main/java/jenkins/util/JSONSignatureValidator.java
+++ b/core/src/main/java/jenkins/util/JSONSignatureValidator.java
@@ -130,12 +130,12 @@ public class JSONSignatureValidator {
LOGGER.severe(msg);
LOGGER.severe(o.toString(2));
}
return FormValidation.error(msg);
+ // return FormValidation.error(msg);
}
String providedSignature = signature.getString("correct_signature");
if (!sig.verify(Base64.decode(providedSignature.toCharArray( {
-return FormValidation.error("Signature in the update center doesn't match with the certificate in "+name);
+// return FormValidation.error("Signature in the update center doesn't match with the certificate in "+name);
}
if (warning!=null) return warning;
diff --git a/pom.xml b/pom.xml
index 1d098c9..bf961d4 100644
a/pom.xml
+++ b/pom.xml
@@ -33,7 +33,7 @@ THE SOFTWARE.
groupIdorg.jenkins-ci.main/groupId
artifactIdpom/artifactId
version1.513-SNAPSHOT/version
+ version1.513-SNAPSHOT-NOCHECK/version
packagingpom/packaging
nameJenkins main module/name
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [update-center] (JENKINS-17029) update-center.json seems to be broken
andrew cooke commented on JENKINS-17029 update-center.json seems to be broken The repo at https://github.com/andrewcooke/jenkins contains the fix above. It's just a snapshot of the current tree today (like, an hour ago) plus the hack above. It's very easy to build - just follow the instructions in BUILDING.TXT (you need maven to be installed first). PS Also, it works - plugins now available. 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] [update-center] (JENKINS-17029) update-center.json seems to be broken
andrew cooke
edited a comment on JENKINS-17029
update-center.json seems to be broken
A diff against the current trunk to remove the checks is:
monospaced
diff --git a/core/src/main/java/jenkins/util/JSONSignatureValidator.java b/core/src/main/java/jenkins/util/JSONSignatureValidator.java
index 684f8eb..641d25e 100644
a/core/src/main/java/jenkins/util/JSONSignatureValidator.java
+++ b/core/src/main/java/jenkins/util/JSONSignatureValidator.java
@@ -130,12 +130,12 @@ public class JSONSignatureValidator {
LOGGER.severe(msg);
LOGGER.severe(o.toString(2));
}
return FormValidation.error(msg);
+ // return FormValidation.error(msg);
}
String providedSignature = signature.getString("correct_signature");
if (!sig.verify(Base64.decode(providedSignature.toCharArray( {
-return FormValidation.error("Signature in the update center doesn't match with the certificate in "+name);
+// return FormValidation.error("Signature in the update center doesn't match with the certificate in "+name);
}
if (warning!=null) return warning;
diff --git a/pom.xml b/pom.xml
index 1d098c9..bf961d4 100644
a/pom.xml
+++ b/pom.xml
@@ -33,7 +33,7 @@ THE SOFTWARE.
groupIdorg.jenkins-ci.main/groupId
artifactIdpom/artifactId
version1.513-SNAPSHOT/version
+ version1.513-SNAPSHOT-NOCHECK/version
packagingpom/packaging
nameJenkins main module/name
monospaced
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] [environment-script] (JENKINS-14951) In a Matrix job, Environment Script variables are not expanded in a Parameterized Build Trigger
Aaron Stone commented on JENKINS-14951 In a Matrix job, Environment Script variables are not expanded in a Parameterized Build Trigger If this was fixed, I'm trying to find which release did it. JENKINS-15507 looks somewhat related, maybe. 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] [update-center] (JENKINS-17029) update-center.json seems to be broken
andrew cooke
edited a comment on JENKINS-17029
update-center.json seems to be broken
A diff against the current trunk to remove the checks is:
monospaced
diff --git a/core/src/main/java/jenkins/util/JSONSignatureValidator.java b/core/src/main/java/jenkins/util/JSONSignatureValidator.java
index 684f8eb..641d25e 100644
a/core/src/main/java/jenkins/util/JSONSignatureValidator.java
+++ b/core/src/main/java/jenkins/util/JSONSignatureValidator.java
@@ -130,12 +130,12 @@ public class JSONSignatureValidator {
LOGGER.severe(msg);
LOGGER.severe(o.toString(2));
}
return FormValidation.error(msg);
+ // return FormValidation.error(msg);
}
String providedSignature = signature.getString("correct_signature");
if (!sig.verify(Base64.decode(providedSignature.toCharArray( {
-return FormValidation.error("Signature in the update center doesn't match with the certificate in "+name);
+// return FormValidation.error("Signature in the update center doesn't match with the certificate in "+name);
}
if (warning!=null) return warning;
diff --git a/pom.xml b/pom.xml
index 1d098c9..bf961d4 100644
a/pom.xml
+++ b/pom.xml
@@ -33,7 +33,7 @@ THE SOFTWARE.
groupIdorg.jenkins-ci.main/groupId
artifactIdpom/artifactId
version1.513-SNAPSHOT/version
+ version1.513-SNAPSHOT-NOCHECK/version
packagingpom/packaging
nameJenkins main module/name
monospaced
Jeez. Even your markup is broken?!
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] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Justin Slattery commented on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process Another confirmation here. We upgraded to 1.511 and immediately encountered the issue. I lost more time than I care to admit troubleshooting. Downgrading to 1.505 fixed it right away. 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-17116) gracefull job termination
Martin dAnjou commented on JENKINS-17116 gracefull job termination When the shell script starts with the shabang: #!/bin/bash set -o echo $- I get: allexport off braceexpand on emacs off errexit off errtrace off functrace off hashall on histexpand off history off ignoreeof off interactive-comments on keyword off monitor off noclobber off noexec off noglob off nolog off notify off nounset off onecmd off physical off pipefail off posix off privileged off verbose off vi off xtrace off hB When the shell script does not start with the shabang: set -o echo $- I get: + set -o allexport off braceexpand on emacs off errexit on errtrace off functrace off hashall on histexpand off history off ignoreeof off interactive-comments on keyword off monitor off noclobber off noexec off noglob off nolog off notify off nounset off onecmd off physical off pipefail off posix on privileged off verbose off vi off xtrace on + echo ehxB ehxB Conclusion: Jenkins forces -ex when there is no shabang (#!/bin/bash) line, so you can control at least that part. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [other] (JENKINS-17682) pom: Licensing terms are not specified
Mikolaj Izdebski created JENKINS-17682 pom: Licensing terms are not specified Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: other Created: 19/Apr/13 1:14 PM Description: Licensing terms of main POM (groupId: org.jenkins-ci, artifactId: jenkins) are not specified. Please add license text to the repository, or at least mention licensing terms in the POM itself (as a comment header or as license field). Project: Jenkins Priority: Major Reporter: Mikolaj Izdebski 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] [email-ext] (JENKINS-17659) Attach URLTrigger Log to email
Nathan Felton commented on JENKINS-17659 Attach URLTrigger Log to email I was unable to find the documentation you referred to, if you could provide a link, I would appreciate it. For some background, the file I wanted to attach was in "projectname/builds/lastSuccessfulBuild/". With the base directory being "projectname/workspace/", I could not figure out how to break out of the workspace directory to get into the builds directory to get the log file I wanted. For now I have simply created a simlink in the "projectname/workspace/" directory to the "projectname/builds/lastSuccessfulBuild/" directory. Is this the intended way for this to work, or is there another method that I am unaware of? 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-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
david catalan commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException Hello, we are experiencing the same issue on our 2 Jenkins instances. I have found a way to reproduce the issue: 1. Create a job which generates a big console output (minimum 25Mb) (ie. a shell action doing a cat of a big text file) 2. On your screen, keep an eye on the jenkins log (file tail) + the cpu utilization of the jenkins process (top command or visualVM) 3. On Jenkins interface, navigate to the full console output of this job (http://JENKINS_HOST/job/JENKINS_JOB/lastBuild/consoleFull) 4. Keep refreshing the console page without letting the page load completly = You should see the "java.util.zip.Deflater.deflate" stack trace in the the jenkins.log 5. Keep refreshing until the Jenkins process uses all the CPU(s)!! Tested on our 2 instances and, depending on the box current use + the size of the console, the CPU issue takes more or less time to occur. Finally, after applying the "-Dorg.kohsuke.stapler.compression.CompressionFilter.disabled=true" fix, the exception still occurs in the log BUT, no more CPU overload!! I see that a lot of users are experiencing this issue on multiple configuration (OS/Jenkins Version)!! Also a lot of users are spending time on it trying to debug and find out the reason/solution of this issue. Now, I would like to see some reaction from the Jenkins team. Are they taking care of this issue? We expect some solution from their side. Thanks in advance, David. 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] [email-ext] (JENKINS-17659) Attach URLTrigger Log to email
Alex Earl commented on JENKINS-17659 Attach URLTrigger Log to email Yes, the file needs to be under the workspace in order for the attachments feature to work. The documentation is the help button next to the item in the project configuration. It gives an explanation of how to use the feature. 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-17112) Publish over CIFS shares do not persist
Kevin Burge commented on JENKINS-17112 Publish over CIFS shares do not persist I reverted back to 1.503, so, I cannot provide precise details. CentOS 6.4 x86_64 java-1.6.0-openjdk-1.6.0.0-1.57.1.11.9.el6_4.x86_64 (I switched to using jdk1.7.0_17 from oracle, but can't remember if I did that before or after reverting to 1.503. I believe it was AFTER.) Publish over cifs 0.2 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] [tap] (JENKINS-17215) TAP plugin can prevent Jenkins startup
Alex Newnham updated JENKINS-17215 TAP plugin can prevent Jenkins startup New stack trace as requested. One way to trigger the problem is to kill the subprocess triggered by Jenkins that will ultimately produce the TAP. Change By: Alex Newnham (19/Apr/13 2:38 PM) Attachment: stack4.txt 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] [cvs] (JENKINS-17656) CVS symbolic name parameter
Michael Clarke commented on JENKINS-17656 CVS symbolic name parameter The issue is caused by something having happened on Line 315 of CvsTagsParamDefinition1. It's easy to fix and will be in the next release (I just have to remove the excessive spaces and incorrect characters. I'll add in something to differentiate each error message too. https://github.com/jenkinsci/cvs-plugin/blob/master/src/main/java/hudson/scm/CvsTagsParamDefinition.java#L135 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] [cvs] (JENKINS-17656) CVS symbolic name parameter
Barthélémy von Haller commented on JENKINS-17656 CVS symbolic name parameter Thank you very much, I am impressed by the support. 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-11964) [Regression] Cannot build a single module in a Maven multi-module job with Maven 3
Ruben Martin Pozo commented on JENKINS-11964 [Regression] Cannot build a single module in a Maven multi-module job with Maven 3 Hi everyone. I registered this issue in the "proposing" section on FreedomSponsors. This means that if you need this issue that bad, you can go to http://www.freedomsponsors.org/core/issue/245/regression-cannot-build-a-single-module-in-a-maven-multi-module-job-with-maven-3 and offer a few bucks for 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] [ec2] (JENKINS-17683) Incorrect hash calculated for custom SSH keys
Joseph Lawson created JENKINS-17683 Incorrect hash calculated for custom SSH keys Issue Type: Bug Assignee: Francis Upton Components: ec2 Created: 19/Apr/13 4:03 PM Description: EC2 keypair fingerprints are generated in two different ways. Currently the EC2 plugin only recognizes keypairs generated via AWS. No imported keypairs are allowed. If AWS generates the keypair, the following command can generate the fingerprint resulting from the private key being hashed: openssl rsa -in privatekey.pem -outform DER -pubout | openssl sha1 -c If you generate a public key from the private using ssh-keygen (ssh-keygen -y -f privatekey.pem) and then upload the public key, the fingerprint is calculated off the public key instead of the private key. You generate the same public key fingerprint that amazon gets via: openssl rsa -in privatekey.pem -outform DER -pubout | openssl md5 -c If I put in the ec2 plugin a private key that I generated and then uploaded the public key, the ec2 plugin cannot find the proper resulting fingerprint from the public key. Could the plugin be updated to either allow entering a public key and private key or have it generate a public key fingerprint as well as the private key fingerprint and check for either? Project: Jenkins Priority: Major Reporter: Joseph Lawson 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-17683) Incorrect hash calculated for custom SSH keys
Joseph Lawson commented on JENKINS-17683 Incorrect hash calculated for custom SSH keys To convert an OpenSSH compatible public to to the PKCS#1 PEM encoded: ssh-keygen -f key.pub -e -m pem 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] [cvs] (JENKINS-17656) CVS symbolic name parameter
Nicolas Martin commented on JENKINS-17656 CVS symbolic name parameter Great news ! I guess we'll be waiting for the next release then. thanks a lot. 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] [update-center] (JENKINS-17029) update-center.json seems to be broken
andrew cooke
edited a comment on JENKINS-17029
update-center.json seems to be broken
A diff against the current trunk to remove the checks is:
{{
diff --git a/core/src/main/java/jenkins/util/JSONSignatureValidator.java b/core/src/main/java/jenkins/util/JSONSignatureValidator.java
index 684f8eb..641d25e 100644
a/core/src/main/java/jenkins/util/JSONSignatureValidator.java
+++ b/core/src/main/java/jenkins/util/JSONSignatureValidator.java
@@ -130,12 +130,12 @@ public class JSONSignatureValidator {
LOGGER.severe(msg);
LOGGER.severe(o.toString(2));
}
return FormValidation.error(msg);
+ // return FormValidation.error(msg);
}
String providedSignature = signature.getString("correct_signature");
if (!sig.verify(Base64.decode(providedSignature.toCharArray( {
-return FormValidation.error("Signature in the update center doesn't match with the certificate in "+name);
+// return FormValidation.error("Signature in the update center doesn't match with the certificate in "+name);
}
if (warning!=null) return warning;
diff --git a/pom.xml b/pom.xml
index 1d098c9..bf961d4 100644
a/pom.xml
+++ b/pom.xml
@@ -33,7 +33,7 @@ THE SOFTWARE.
groupIdorg.jenkins-ci.main/groupId
artifactIdpom/artifactId
version1.513-SNAPSHOT/version
+ version1.513-SNAPSHOT-NOCHECK/version
packagingpom/packaging
nameJenkins main module/name
}}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [update-center] (JENKINS-17029) update-center.json seems to be broken
andrew cooke
edited a comment on JENKINS-17029
update-center.json seems to be broken
A diff against the current trunk to remove the checks is:
{{diff --git a/core/src/main/java/jenkins/util/JSONSignatureValidator.java b/core/src/main/java/jenkins/util/JSONSignatureValidator.java
index 684f8eb..641d25e 100644
a/core/src/main/java/jenkins/util/JSONSignatureValidator.java
+++ b/core/src/main/java/jenkins/util/JSONSignatureValidator.java
@@ -130,12 +130,12 @@ public class JSONSignatureValidator {
LOGGER.severe(msg);
LOGGER.severe(o.toString(2));
}
return FormValidation.error(msg);
+ // return FormValidation.error(msg);
}
String providedSignature = signature.getString("correct_signature");
if (!sig.verify(Base64.decode(providedSignature.toCharArray( {
-return FormValidation.error("Signature in the update center doesn't match with the certificate in "+name);
+// return FormValidation.error("Signature in the update center doesn't match with the certificate in "+name);
}
if (warning!=null) return warning;
diff --git a/pom.xml b/pom.xml
index 1d098c9..bf961d4 100644
a/pom.xml
+++ b/pom.xml
@@ -33,7 +33,7 @@ THE SOFTWARE.
groupIdorg.jenkins-ci.main/groupId
artifactIdpom/artifactId
version1.513-SNAPSHOT/version
+ version1.513-SNAPSHOT-NOCHECK/version
packagingpom/packaging
nameJenkins main module/name}}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [update-center] (JENKINS-17029) update-center.json seems to be broken
andrew cooke
edited a comment on JENKINS-17029
update-center.json seems to be broken
A diff against the current trunk to remove the checks is:
diff --git a/core/src/main/java/jenkins/util/JSONSignatureValidator.java b/core/src/main/java/jenkins/util/JSONSignatureValidator.java
index 684f8eb..641d25e 100644
--- a/core/src/main/java/jenkins/util/JSONSignatureValidator.java
+++ b/core/src/main/java/jenkins/util/JSONSignatureValidator.java
@@ -130,12 +130,12 @@ public class JSONSignatureValidator {
LOGGER.severe(msg);
LOGGER.severe(o.toString(2));
}
-return FormValidation.error(msg);
+ // return FormValidation.error(msg);
}
String providedSignature = signature.getString("correct_signature");
if (!sig.verify(Base64.decode(providedSignature.toCharArray( {
-return FormValidation.error("Signature in the update center doesn't match with the certificate in "+name);
+// return FormValidation.error("Signature in the update center doesn't match with the certificate in "+name);
}
if (warning!=null) return warning;
diff --git a/pom.xml b/pom.xml
index 1d098c9..bf961d4 100644
--- a/pom.xml
+++ b/pom.xml
@@ -33,7 +33,7 @@ THE SOFTWARE.
groupIdorg.jenkins-ci.main/groupId
artifactIdpom/artifactId
- version1.513-SNAPSHOT/version
+ version1.513-SNAPSHOT-NOCHECK/version
packagingpom/packaging
nameJenkins main module/name
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-16102) Cannot change my JIRA - Jenkins account password.
Jorge Hidalgo commented on JENKINS-16102 Cannot change my JIRA - Jenkins account password. same here This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Walter Kacynski commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException I have tried option -Dorg.kohsuke.stapler.compression.CompressionFilter.disabled=true however, the Content-Encoding header that is returned is always of type gzip. Does it matter where in the arguments section that this needs to be set? After looking a little more at the code it seems that the disable doesn't actually disable to compression just the error reporting? Why would this be? 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-17683) Incorrect hash calculated for custom SSH keys
Joseph Lawson updated JENKINS-17683 Incorrect hash calculated for custom SSH keys Change By: Joseph Lawson (19/Apr/13 6:20 PM) Description: EC2keypairfingerprintsaregeneratedintwodifferentways.CurrentlytheEC2pluginonlyrecognizeskeypairsgeneratedviaAWS.Noimportedkeypairsareallowed.If AWSgeneratesthekeypair,thefollowingcommandcangeneratethefingerprintresultingfromtheprivatekeybeinghashed:opensslrsa-inprivatekey.pem-outformDER-pubout|opensslsha1-cIf yougenerateapublickeyfromtheprivateusingssh-keygen(ssh-keygen-y-fprivatekey.pem)andthenuploadthepublickey,thefingerprintiscalculatedoffthepublickeyinsteadoftheprivatekey.Yougeneratethesamepublickeyfingerprintthatamazongetsvia:opensslrsa-inprivatekey.pem-outformDER-pubout|opensslmd5-cIfIputintheec2pluginaprivatekeythatIgeneratedandthenuploadedthepublickey,theec2plugincannotfindtheproperresultingfingerprintfromthepublickey.Couldthepluginbeupdatedtoeitherallowenteringapublickeyandprivatekeyorhaveitgenerateapublickeyfingerprintaswellastheprivatekeyfingerprintandcheckforeither? 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Rob Petti commented on JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? Can you try without the quotes? 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis commented on JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? Yes - I did and unfortunately the files I'm trying to exclude have spaces in the Perforce path. When I take away the quotes, I'm warned about the path not being a valid Perforce path and it looks like Polling stops altogether. I tested this with another project that was just excluding files in this path: "//asecondfilepath/config/buildinfo/..." I just took this path out of another build and left only: //afilepath/VersionInfo.cs in the exclude files section, but I'll have to wait for awhile for to see if the exclusions work and if it's quoted Perforce paths causing the problem. 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-17663) Fail by publishing report will fail whole build
Ulli Hafner commented on JENKINS-17663 Fail by publishing report will fail whole build Actually that behavior is by design: there should appear an "Error" link in the results of your build. Is this link not visible in your job? 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis edited a comment on JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? Yes - I just now did and unfortunately the files I'm trying to exclude have spaces in the Perforce path. When I take away the quotes, I'm warned about the path not being a valid Perforce path and it looks like Polling stops altogether. I tested this with another project that was only excluding files in this path: "//asecondfilepath/config/buildinfo/..." To possibly test if quoted Perforce paths are what's causing the problem, I also just now took the above path out of another build and left only: //afilepath/VersionInfo.cs in the exclude files section. I'll have to wait for awhile to see if the exclusions start allowing build through 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis edited a comment on JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? Yes - I just now did and unfortunately the files I'm trying to exclude have spaces in the Perforce path. When I take away the quotes, I'm warned about the path not being a valid Perforce path and it looks like Polling stops altogether. I tested this with another project that was only excluding files in this path: "//asecondfilepath/config/buildinfo/..." To possibly test if quoted Perforce paths are what's causing the problem, I also just now took the above path out of another build and left only: //afilepath/VersionInfo.cs in the exclude files section. I'll have to wait for awhile to see if the exclusions start allowing builds through 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] [email-ext] (JENKINS-17546) New Trigger: broken build - compiling build (unstable/stable)
calculu5 commented on JENKINS-17546 New Trigger: broken build - compiling build (unstable/stable) Thanks. Quick questions. What is the trigger for the transition from Failure - Successful (so I can configure the other part of my request)? Also, is there documentation on the script triggers (e.g. variables that can be used)? 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] [email-ext] (JENKINS-17546) New Trigger: broken build - compiling build (unstable/stable)
Alex Earl commented on JENKINS-17546 New Trigger: broken build - compiling build (unstable/stable) Should be the Fixed trigger. I haven't added docs to the wiki, but there is documentation inside the configuration pages for each trigger (see the help icon next to the trigger). 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-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
GlennZ reopened JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification I hope it's ok to reopen this, because I'm also seeing the same issue and have not seen it go away across jenkins upgrades. I'm currently running version 1.511-1.1 on a RHEL 5 system, using the officially supplied rpm. I also he emailext plugin, in case that has anything to do with this. There are not full user accounts that were explicitly registered with passwords. These are all auto-created users from the mercurial SCM change sets. My main concern with this bug is that submitters are no longer receiving email notifications when the build fails. Change By: GlennZ (19/Apr/13 8:18 PM) Resolution: CannotReproduce 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] [ec2] (JENKINS-17683) Incorrect hash calculated for custom SSH keys
Joseph Lawson commented on JENKINS-17683 Incorrect hash calculated for custom SSH keys Hello I have made some simple changes to the plugin to support looking for the SSH Keypair's private key fingerprint as well as it's public key fingerprint as well. Unit test is included as well. https://github.com/jenkinsci/ec2-plugin/pull/45 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-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Sergey Grigoriev commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification This issue happen again 1 week ago on the latest version of Jenkins. 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] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
Gregory Boissinot commented on JENKINS-17566 Severe polling error when using script trigger Please try version 0.23 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] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
Gregory Boissinot started work on JENKINS-17566 Severe polling error when using script trigger Change By: Gregory Boissinot (19/Apr/13 8:44 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] [mstest] (JENKINS-8805) Problem with MSTest post build action with following message: FATAL: No MSTest TRX test report files were found. Configuration error?
gopivinay gande updated JENKINS-8805 Problem with MSTest post build action with following message: FATAL: No MSTest TRX test report files were found. Configuration error? the plugin and here is configuration that i have used as shown Change By: gopivinay gande (19/Apr/13 9:11 PM) Attachment: screenshot-1.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [mstest] (JENKINS-8805) Problem with MSTest post build action with following message: FATAL: No MSTest TRX test report files were found. Configuration error?
gopivinay gande commented on JENKINS-8805 Problem with MSTest post build action with following message: FATAL: No MSTest TRX test report files were found. Configuration error? I have attached the files and screen shot showing you the way i followed you to achive ( display the trx results to dashboard) 1) added the plugin to publish 2) trx file was generated and path was given as shown in screen shot this is the error that i get 4 Time Elapsed 00:00:39.24 20:53:34 Processing tests results in file(s) results.trx 20:53:34 FATAL: No MSTest test report files were found. 20:53:34 FATAL: No MSTest TRX test report files were found. Configuration error? 20:53:34 Build step 'Publish MSTest test result report' marked build as failure 20:53:34 Finished: FAILURE Can you please give me pointer or any alternative to achive this . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mstest] (JENKINS-8805) Problem with MSTest post build action with following message: FATAL: No MSTest TRX test report files were found. Configuration error?
gopivinay gande updated JENKINS-8805 Problem with MSTest post build action with following message: FATAL: No MSTest TRX test report files were found. Configuration error? I have attached you the trx file and folder generated .Here iam running web performance test. Change By: gopivinay gande (19/Apr/13 9:12 PM) Attachment: Files.zip 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] [email-ext] (JENKINS-17546) New Trigger: broken build - compiling build (unstable/stable)
calculu5 commented on JENKINS-17546 New Trigger: broken build - compiling build (unstable/stable) The description for the Fixed trigger says: "An email will be sent when the build status changes from "Failure" or "Unstable" to "Successful"." This sounds like it would trigger on the "there are some tests failing" to "there are no tests failing" (not desired) in addition to the "Failure" to "Successful" transition (which is what I am looking for). 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] [email-ext] (JENKINS-17546) New Trigger: broken build - compiling build (unstable/stable)
Alex Earl commented on JENKINS-17546 New Trigger: broken build - compiling build (unstable/stable) You could filter in the pre-send script if you want. 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-17684) Dashboard web pages don't render correctly in Chrome because of bad cache
Ragi Burhum created JENKINS-17684 Dashboard web pages dont render correctly in Chrome because of bad cache Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 19/Apr/13 9:54 PM Description: After using Chrome for a day, the page renders incorrectly. Screenshot: http://imgur.com/9Y11bqz It doesn't matter if I hit refresh multiple times, it always renders the same way. If I open another browser, it works fine. If I debug under Chrome Dev Tools, I don't see any errors when fetching the resources... just a whole bunch of 304s. If I clear the cache manually using the Chrome Web settings, then everything works fine again. I went to #jenkins on freenode and apparently other people were having the same issue. Environment: Google Chrome 26.0.1410.65 (Official Build 193261) OS Mac OS X WebKit 537.31 (@147513) _javascript_ V8 3.16.14.11 Flash 11.7.700.169 User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31 Command Line /Applications/Google Chrome.app/Contents/MacOS/Google Chrome -psn_0_17293437 --flag-switches-begin --enable-expose-for-tabs --enable-experimental-extension-apis --sync-keystore-encryption --flag-switches-end Executable Path /Applications/Google Chrome.app/Contents/MacOS/Google Chrome Profile Path /Users/rburhum/Library/Application Support/Google/Chrome/Default Variations 853359fa-33ba05a4 5f9f065f-15eb91be b03ddc1f-2d9ef0cc f9b252d0-fd526c81 ca6785ad-766fa2d 3709139-766fa2d ff3fc1a6-766fa2d d86b76a4-d674141c 7f6da4bf-cda32b90 75f7fb7e-611a9f49 24dca50e-837c4893 ca65a9fe-91ac3782 82d91892-3d47f4f4 3028188e-d60b5a5f 5a3c10b5-e1cc0f14 244ca1ac-4ad60575 246fb659-75cb33fc f296190c-19dcaa1a 4442aae2-d7f6b13c 75f0f0a0-e1cc0f14 e2b18481-6bdfffe7 e7e71889-e1cc0f14 Project: Jenkins Priority: Major Reporter: Ragi Burhum This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [other] (JENKINS-13540) Redirects do not work properly on IE
evernat commented on JENKINS-13540 Redirects do not work properly on IE Reproduced with Jenkins 1.511 and IE8. And so the "Previous build" and "Next build" links in test reports may go to an error 404 page. 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-17684) Dashboard web pages don't render correctly in Chrome because of bad cache
Kohsuke Kawaguchi commented on JENKINS-17684 Dashboard web pages dont render correctly in Chrome because of bad cache If anyone else sees a similar issue, please attach your screenshots as well. http://imgur.com/9Y11bqz has no table borders, which indicates that style.css isn't kicking in. The chrome dev output indicates that Jenkins had sent 304 without content, which then makes me wonder what Chrome thinks it has in its cache. One would think somehow the cache gets poluted, and Chrome isn't even noticing that because the server keeps sending 304 to the client. 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-10016) hudson.Util.deleteFile fails on files with non-standard characters
Kohsuke Kawaguchi resolved JENKINS-10016 as Not A Defect hudson.Util.deleteFile fails on files with non-standard characters This is not a bug in Jenkins but a misconfigured LANG header. POSIX treats file names as a sequence of bytes, and Java treats them as a sequence of chars. Thus a certain encoding needs to be asumed, and in Java that is governed by the LANG header. What Jenkins is doing when it's in Util.deleteRecursive is that it's listing all the files in a directory (bytes-chars conv), then delete them one by one (chars-bytes conv.) If the LANG header is such that this file name converstion process isn't loseless (for example, the file is created from LANG=en_US.UTF-8 process but read as LANG=en_US.iso-8859-1), then you see the problem you are seeing. Check the system information of the slave process in question to make sure that it's having the right encoding set in the LANG environment variable. If not, check the way you are launching the process and check where in your slave the LANG header is supposed to be set. Note that abayer is wrong about the role of the file.encoding system property. This is about how Java process reads the contents of files, and it has nothing to do with the encoding of file names. Change By: Kohsuke Kawaguchi (19/Apr/13 10:45 PM) Status: Open Resolved Assignee: abayer KohsukeKawaguchi Resolution: NotADefect 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] [phing] (JENKINS-17668) Windows phing is broken, jenkins tries to execute phing.bat with php.exe
SCM/JIRA link daemon commented on JENKINS-17668 Windows phing is broken, jenkins tries to execute phing.bat with php.exe Code changed in jenkins User: ssogabe Path: src/main/java/hudson/plugins/phing/PhingBuilder.java http://jenkins-ci.org/commit/phing-plugin/ffb569ec63f8179f09ddae4b036c87200b9e3815 Log: FIXED JENKINS-17668 Windows phing is broken, jenkins tries to execute phing.bat with php.exe 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] [phing] (JENKINS-17668) Windows phing is broken, jenkins tries to execute phing.bat with php.exe
SCM/JIRA link daemon resolved JENKINS-17668 as Fixed Windows phing is broken, jenkins tries to execute phing.bat with php.exe Change By: SCM/JIRA link daemon (20/Apr/13 12:24 AM) 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] [ios-device-connector] (JENKINS-15578) hudson.security.AccessDeniedException2: anonymous is missing the Administer permission
Mark Steinberg commented on JENKINS-15578 hudson.security.AccessDeniedException2: anonymous is missing the Administer permission I had to disable iOS Device connector 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] [grails] (JENKINS-15628) grails can not build non-production war
Ramzi Maalej closed JENKINS-15628 as Not A Defect grails can not build non-production war Environnment can be set using the properties field: grails.env=test Change By: Ramzi Maalej (20/Apr/13 1:40 AM) Status: Open Closed Resolution: NotADefect 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] [grails] (JENKINS-13252) Grails build step not finding grails
Ramzi Maalej commented on JENKINS-13252 Grails build step not finding grails have you made Grails accessible via GRAILS_HOME and added $GRAILS_HOME/bin to path variable ? 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.
