[JIRA] (JENKINS-48694) Notifies successful build when still in progress
Title: Message Title Rasmus Pedersen commented on JENKINS-48694 Re: Notifies successful build when still in progress I tried version 2.2.14 and it doesn't cover all cases, but probably most. If there's no checkout scm step, like in stage 1 above, it is still reporting a successful build after completing stage 1 and then failing the build after stage 2. If checkout scm is added as the first step in stage 1 the status is now reported correctly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48694) Notifies successful build when still in progress
Title: Message Title Rasmus Pedersen updated an issue Jenkins / JENKINS-48694 Notifies successful build when still in progress Change By: Rasmus Pedersen Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Title: Message Title Rasmus Pedersen commented on JENKINS-27084 Re: SVN authentication fails using subversion plugin v.2.5 I've upgraded to 2.5.3 and the issue seems to be fixed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Rasmus Pedersen commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module I've also seen it on a freestyle job now running 1.609.3. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Rasmus Pedersen commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module I'm experiencing this on 1.609.3 on a Windows Server 2008 R2 running a Jenkins slave as a service. I've only seen it on matrix builds. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27925) Build step is not always saved
Rasmus Pedersen commented on JENKINS-27925 Build step is not always saved Sorry, wrong answer. It should have been: Q: And after submitting that, the job still contains two batch build steps? A: It contains a shell command build step at the top and a batch build step at the bottom. It is only the content of the shell command that doesn't get saved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27925) Build step is not always saved
Rasmus Pedersen commented on JENKINS-27925 Build step is not always saved Q: And after submitting that, the job still contains two batch build steps? A: Yes There's one warning in /log/all apr. 15, 2015 11:35:51 AM org.kohsuke.stapler.RequestImpl$TypePair convertJSON WARNING: 'stapler-class' is deprecated: hudson.tasks.Shell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27925) Build step is not always saved
Rasmus Pedersen commented on JENKINS-27925 Build step is not always saved Q: In the developer tools of your browser, what is the request sent on clicking 'Send' in step 7? A: The request-body: Content-Type: application/x-www-form-urlencoded Content-Length: 5363 name=rupt+test+tos&description=&_.daysToKeepStr=&_.numToKeepStr=&_.artifactDaysToKeepStr=&_.artifactNumToKeepStr=&stapler-class=hudson.tasks.LogRotator&%24class=hudson.tasks.LogRotator&stapler-class-bag=true&quiet_period=5&scmCheckoutRetryCount=0&_.customWorkspace=&_.displayNameOrNull=&scm=0&_.cvsRoot=&_.password=&_.branchName=&stapler-class=hudson.scm.CvsRepositoryLocation%24BranchRepositoryLocation&%24class=hudson.scm.CvsRepositoryLocation%24BranchRepositoryLocation&stapler-class=hudson.scm.CvsRepositoryLocation%24HeadRepositoryLocation&%24class=hudson.scm.CvsRepositoryLocation%24HeadRepositoryLocation&_.tagName=&stapler-class=hudson.scm.CvsRepositoryLocation%24TagRepositoryLocation&%24class=hudson.scm.CvsRepositoryLocation%24TagRepositoryLocation&_.remoteName=&_.localName=&stapler-class=hudson.scm.browsers.FishEyeCVS&%24class=hudson.scm.browsers.FishEyeCVS&stapler-class=hudson.scm.browsers.OpenGrok&%24class=hudson.scm.browsers.OpenGrok&stapler-class=hudson.scm.browsers.ViewCVS&%24class=hudson.scm.browsers.ViewCVS&_.pattern=&_.compressionLevel=-1&_.canUseUpdate=on&_.pruneEmptyDirectories=on&_.cvsRoot=&_.password=&_.branchName=&stapler-class=hudson.scm.CvsRepositoryLocation%24BranchRepositoryLocation&%24class=hudson.scm.CvsRepositoryLocation%24BranchRepositoryLocation&stapler-class=hudson.scm.CvsRepositoryLocation%24HeadRepositoryLocation&%24class=hudson.scm.CvsRepositoryLocation%24HeadRepositoryLocation&_.tagName=&stapler-class=hudson.scm.CvsRepositoryLocation%24TagRepositoryLocation&%24class=hudson.scm.CvsRepositoryLocation%24TagRepositoryLocation&_.remoteName=&_.localName=&_.projectsetFileName=&stapler-class=hudson.scm.browsers.FishEyeCVS&%24class=hudson.scm.browsers.FishEyeCVS&stapler-class=hudson.scm.browsers.OpenGrok&%24class=hudson.scm.browsers.OpenGrok&stapler-class=hudson.scm.browsers.ViewCVS&%24class=hudson.scm.browsers.ViewCVS&_.pattern=&_.compressionLevel=-1&_.canUseUpdate=on&_.username=&_.password=&_.pruneEmptyDirectories=on&stapler-class=hudson.scm.browsers.CvsFacadeRepositoryBrowser&%24class=hudson.scm.browsers.CvsFacadeRepositoryBrowser&stapler-class=hudson.scm.browsers.FishEyeCVS&%24class=hudson.scm.browsers.FishEyeCVS&stapler-class=hudson.scm.browsers.OpenGrok&%24class=hudson.scm.browsers.OpenGrok&stapler-class=hudson.scm.browsers.ViewCVS&%24class=hudson.scm.browsers.ViewCVS&_.remote=&_.local=.&depthOption=infinity&stapler-class=hudson.scm.subversion.UpdateUpdater&%24class=hudson.scm.subversion.UpdateUpdater&stapler-class=hudson.scm.subversion.CheckoutUpdater&%24class=hudson.scm.subversion.CheckoutUpdater&stapler-class=hudson.scm.subversion.UpdateWithCleanUpdater&%24class=hudson.scm.subversion.UpdateWithCleanUpdater&stapler-class=hudson.scm.subversion.UpdateWithRevertUpdater&%24class=hudson.scm.subversion.UpdateWithRevertUpdater&stapler-class=hudson.scm.browsers.Assembla&%24class=hudson.scm.browsers.Assembla&stapler-class=hudson.scm.browsers.CollabNetSVN&%24class=hudson.scm.browsers.CollabNetSVN&stapler-class=hudson.scm.browsers.FishEyeSVN&%24class=hudson.scm.browsers.FishEyeSVN&stapler-class=hudson.scm.browsers.SVNWeb&%24class=hudson.scm.browsers.SVNWeb&stapler-class=hudson.scm.browsers.Sventon&%24class=hudson.scm.browsers.Sventon&stapler-class=hudson.scm.browsers.Sventon2&%24class=hudson.scm.browsers.Sventon2&stapler-class=hudson.scm.browsers.ViewSVN&%24class=hudson.scm.browsers.ViewSVN&stapler-class=hudson.scm.browsers.WebSVN&%24class=hudson.scm.browsers.WebSVN&_.excludedRegions=&_.includedRegions=&_.excludedUsers=&_.excludedCommitMessages=&_.excludedRevprop=&_.upstreamProjects=&ReverseBuildTrigger.threshold=SUCCESS&_.spec=&scmpoll_spec=&command=hello+from+shell&stapler-class=hudson.tasks.Shell&kind=hudson.tasks.Shell&%24class=hudson.tasks.Shell&command=hello+from+batch+2&stapler-class=hudson.tasks.BatchFile&kind=hudson.tasks.BatchFile&%24class=hudson.tasks.BatchFile&core%3Aapply=&json=%7B%22name%22%3A+%22rupt+test+tos%22%2C+%22description%22%3A+%22%22%2C+%22logrotate%22%3A+false%2C+%22%22%3A+%220%22%2C+%22buildDiscarder%22%3A+%7B%22daysToKeepStr%22%3A+%22%22%2C+%22numToKeepStr%22%3A+%22%22%2C+%22artifactDaysToKeepStr%22%3A+%22%22%2C+%22artifactNumToKeepStr%22%3A+%22%22%2C+%22stapler-class%22%3A+%22hudson.tasks.LogRotator%22%2
[JIRA] [core] (JENKINS-27925) Build step is not always saved
Rasmus Pedersen
updated JENKINS-27925
Build step is not always saved
Change By:
Rasmus Pedersen
(14/Apr/15 9:15 PM)
Description:
When changing a build step from a {{Windows batch command}} to a {{Shell command}}
and at
the
same time puts two hyphens, {{--}}, in the shell command, the
content of the shell command is not always saved.*Steps to reproduce:*# Create two {{Windows batch command}} build steps.# Click {{Save}}# Click {{Configure}}# Delete one of the build steps# Create a {{Shell command}} build step and enter some text in it
containing two hyphens, e
.
g. {noformat}some text -- some thing{noformat}
# Move the just created build step to the top.# Click {{Save}}*What I expected to happen:*The content of the {{Shell command}} build step is saved.*What actually happens:*The content isn't saved.I've tried the above method in both Firefox (with addons disabled), IE and Chrome and I've only successfully reproduced it in Firefox (is it a bug in Firefox?).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27925) Build step is not always saved
Rasmus Pedersen commented on JENKINS-27925 Build step is not always saved Q: Does this work for newly created projects? A: Yes. Q: Are they freestyle projects? A: Yes Q: Are any errors shown in the JS console of your browser? A: No, but there are some warnings about getAttributeNode() and getPreventDefault(). Q: In the developer tools of your browser, what is the request sent on clicking 'Send' in step 7? A: I'll have a look at that tomorrow. Q: Is this reproducible 100% of the time, or only sometimes? A: It is reproducible 100% of the time. Q: Are the two original Windows batch commands empty, or do they contain text? A: It doesn't seem to matter whether they are empty or not. I don't know why I've been so focused on the hyphens, it doesn't seem to matter what text you enter in the Shell command text box. I'll update the description. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27925) Build step is not always saved
Rasmus Pedersen commented on JENKINS-27925 Build step is not always saved I didn't I clicked Configure (I've updated the description). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27925) Build step is not always saved
Rasmus Pedersen
updated JENKINS-27925
Build step is not always saved
Change By:
Rasmus Pedersen
(14/Apr/15 11:15 AM)
Description:
When changing a build step from a {{Windows batch command}} to a {{Shell command}} and at the same time puts two hyphens, {{--}}, in the shell command, the content of the shell command is not always saved.*Steps to reproduce:*# Create two {{Windows batch command}} build steps.# Click {{Save}}#
Click {{Configure}}#
Delete one of the build steps# Create a {{Shell command}} build step and enter some text in it containing two hyphens, e.g. {noformat}some text -- some thing{noformat}# Move the just created build step to the top.# Click {{Save}}*What I expected to happen:*The content of the {{Shell command}} build step is saved.*What actually happens:*The content isn't saved.I've tried the above method in both Firefox (with addons disabled), IE and Chrome and I've only successfully reproduced it in Firefox (is it a bug in Firefox?).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27925) Build step is not always saved
Rasmus Pedersen created JENKINS-27925 Build step is not always saved Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Apr/15 8:30 AM Description: When changing a build step from a Windows batch command to a Shell command and at the same time puts two hyphens, --, in the shell command, the content of the shell command is not always saved. Steps to reproduce: Create two Windows batch command build steps. Click Save Delete one of the build steps Create a Shell command build step and enter some text in it containing two hyphens, e.g. some text -- some thing Move the just created build step to the top. Click Save What I expected to happen: The content of the Shell command build step is saved. What actually happens: The content isn't saved. I've tried the above method in both Firefox (with addons disabled), IE and Chrome and I've only successfully reproduced it in Firefox (is it a bug in Firefox?). Environment: Jenkins 1.609 Firefox 37.0.1 (started with --safe-mode) Windows 7 Project: Jenkins Priority: Major Reporter: Rasmus Pedersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9911) JNLP slave JVM options are ignored
Rasmus Pedersen commented on JENKINS-9911 JNLP slave JVM options are ignored I tried it on 1.599 - doesn't work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Rasmus Pedersen commented on JENKINS-27084 SVN authentication fails using subversion plugin v.2.5 I don't know why the above workaround only works on some slaves but by adding -Dsvnkit.http.methods=Basic,NTLM,Negotiate,Digest to jenkins-slave.xml on the rest of the slaves seems to work. This is really annoying since we have a lot of slaves. It would be a little easier if I could set the property from the Jenkins master but JENKINS-9911 prevents me from doing so. I'm not exactly sure how this works but don't I risk Jenkins overwriting jenkins-slave.xml at some point if I add the property to jenkins-slave.xml manually? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Rasmus Pedersen reopened JENKINS-27084 SVN authentication fails using subversion plugin v.2.5 Change By: Rasmus Pedersen (18/Mar/15 4:16 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Rasmus Pedersen commented on JENKINS-27084 SVN authentication fails using subversion plugin v.2.5 I've reopened the issue because the workaround doesn't work in all cases. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Rasmus Pedersen edited a comment on JENKINS-27084 SVN authentication fails using subversion plugin v.2.5 Now I'm just wondering: Why is there a line saying lib.svnkit.http.methods Digest,Basic,NTLM,Negotiate when I go to JENKINS_HOST/systemInfo even though I've added the -Dsvnkit.http.methods=Basic,NTLM,Negotiate,Digest to jenkins.xml? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Rasmus Pedersen
commented on JENKINS-27084
SVN authentication fails using subversion plugin v.2.5
Now I'm just wondering:
Why is there a line saying lib.svnkit.http.methods Digest,Basic,NTLM,Negotiate when I go to JENKINS_HOST/systemInfo
even though I've added the -Dsvnkit.http.methods=Basic,NTLM,Negotiate,Digest }} to {{jenkins.xml?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Rasmus Pedersen commented on JENKINS-27084 SVN authentication fails using subversion plugin v.2.5 Adding -Dsvnkit.http.methods=Basic,NTLM,Negotiate,Digest to jenkins.xml fixes the 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/d/optout.
[JIRA] [cpptest-plugin] (JENKINS-26082) Cpptest Plugin fails to link to job source code
Rasmus Pedersen commented on JENKINS-26082 Cpptest Plugin fails to link to job source code Cool, this solved the problem. Thank you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Rasmus Pedersen created JENKINS-27084 SVN authentication fails using subversion plugin v.2.5 Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 23/Feb/15 2:28 PM Description: We're using username and password over HTTP as authentication to the svn server and the Jenkins service is running as the same user. Recently we upgraded the subversion plugin to v2.5 from v2.4.5 and this caused svn authentication to fail with the following error: svn: E200015: authentication cancelled Diving deeper into the cause of this revealed that Jenkins no longer tries to login to the svn server using HTTP clear text authorization (don't know the real name for this) but now tries to use NTLMSSP. Jenkins seems to use the correct username using NTLMSSP but the authentication fails. Environment: Windows Server 2008 R2, Jenkins 1.599 Project: Jenkins Priority: Minor Reporter: Rasmus Pedersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-24377) Create Tag (Tag this build) Not working
Rasmus Pedersen commented on JENKINS-24377 Create Tag (Tag this build) Not working Realized that the svn authentication depending on the cached of the svn password stored in the user profile. Does this mean that the username and password you choose for "Credentials for tagging" has no meaning? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cpptest-plugin] (JENKINS-26082) Cpptest Plugin fails to link to job source code
Rasmus Pedersen created JENKINS-26082 Cpptest Plugin fails to link to job source code Issue Type: Bug Assignee: Gregory Boissinot Components: cpptest-plugin Created: 16/Dec/14 1:37 PM Description: When following the link to the source code I get an error equal to this (taken from https://groups.google.com/forum/#!topic/jenkinsci-users/ml_3pMHdYAg): 01 Copying the source file '/ac_realinfo_srvd/ac_realinfo_srvd/ac_realinfo_data_proc.c' from the workspace to the build folder 'C:\.jenkins\jobs\wacap1.8_inspection\builds\2014-05-05_20-44-43\workspace-files\ef148ebb.tmp' on the Jenkins master failed. 02 Is the file '/ac_realinfo_srvd/ac_realinfo_srvd/ac_realinfo_data_proc.c' a valid filename? 03 If you are building on a slave: please check if the file is accessible under '$JENKINS_HOME/[job-name]//ac_realinfo_srvd/ac_realinfo_srvd/ac_realinfo_data_proc.c' 04 If you are building on the master: please check if the file is accessible under '$JENKINS_HOME/[job-name]/workspace//ac_realinfo_srvd/ac_realinfo_srvd/ac_realinfo_data_proc.c' 05 java.io.IOException: remote file operation failed: /ac_realinfo_srvd/ac_realinfo_srvd/ac_realinfo_data_proc.c at hudson.remoting.Channel@f9f7bc:compiler_1.75 06 at hudson.FilePath.act(FilePath.java:916) 07 at hudson.FilePath.act(FilePath.java:893) 08 at hudson.FilePath.copyTo(FilePath.java:1821) 09 at hudson.plugins.analysis.core.HealthAwareRecorder.copyFilesWithAnnotationsToBuildFolder(HealthAwareRecorder.java:398) 10 at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:165) 11 at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:333) 12 at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) 13 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745) 14 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:709) 15 at hudson.model.Build$BuildExecution.post2(Build.java:182) 16 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:658) 17 at hudson.model.Run.execute(Run.java:1734) 18 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 19 at hudson.model.ResourceController.execute(ResourceController.java:88) 20 at hudson.model.Executor.run(Executor.java:231) 21 Caused by: java.io.FileNotFoundException: /ac_realinfo_srvd/ac_realinfo_srvd/ac_realinfo_data_proc.c (没有那个文件或目录) 22 at java.io.FileInputStream.open(Native Method) 23 at java.io.FileInputStream.(FileInputStream.java:138) 24 at hudson.FilePath$37.invoke(FilePath.java:1826) 25 at hudson.FilePath$37.invoke(FilePath.java:1821) 26 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2474) 27 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 28 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 29 at hudson.remoting.Request$2.run(Request.java:328) 30 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 31 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 32 at java.util.concurrent.FutureTask.run(FutureTask.java:166) 33 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) 34 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) 35 at java.lang.Thread.run(Thread.java:722) What seems to be the problem is the two forward slashes in the file path. Project: Jenkins Priority: Minor Reporter: Rasmus Pedersen This message is automatically generated by JIRA.
[JIRA] [subversion-plugin] (JENKINS-24377) Create Tag (Tag this build) Not working
Rasmus Pedersen commented on JENKINS-24377 Create Tag (Tag this build) Not working After upgrading several other plugins I got the following exception when trying to tag: Tagging http://HOSTNAME/svn/PATH/TO/REPO/trunk (rev.123321) to http://HOSTNAME/svn/PATH/TO/REPO/tags/NAME_OF_TAG ERROR: Failed to tag org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/PATH/TO/REPO/trunk failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryRoot(DAVRepository.java:132) at org.tmatesoft.svn.core.internal.wc.SVNCopyDriver.copyReposToRepos(SVNCopyDriver.java:194) at org.tmatesoft.svn.core.internal.wc.SVNCopyDriver.setupCopy(SVNCopyDriver.java:627) at org.tmatesoft.svn.core.internal.wc16.SVNCopyClient16.doCopy(SVNCopyClient16.java:440) at org.tmatesoft.svn.core.internal.wc2.remote.SvnNgReposToReposCopy.run(SvnNgReposToReposCopy.java:65) at org.tmatesoft.svn.core.internal.wc2.remote.SvnNgReposToReposCopy.run(SvnNgReposToReposCopy.java:23) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc2.SvnRemoteCopy.run(SvnRemoteCopy.java:227) at org.tmatesoft.svn.core.wc.SVNCopyClient.doCopy(SVNCopyClient.java:480) at hudson.scm.SubversionTagAction$TagWorkerThread.perform(SubversionTagAction.java:307) at hudson.model.TaskThread.run(TaskThread.java:127) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 19 more Completed After changing the description of the credentials and running svn --no-auth-cache --config-dir invalid info http://HOSTNAME/svn/PATH/TO/REPO/trunk the exception disappeared and tagging fails silently 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/d/optout.
[JIRA] [subversion-plugin] (JENKINS-24377) Create Tag (Tag this build) Not working
Rasmus Pedersen commented on JENKINS-24377 Create Tag (Tag this build) Not working Still present on Jenkins 1.590 with Subversion plugin 2.4.5. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-24377) Create Tag (Tag this build) Not working
Rasmus Pedersen commented on JENKINS-24377 Create Tag (Tag this build) Not working I'm seeing the same bug using Jenkins 1.588 with the Subversion Plug-in 2.4.4 on one of our servers. We have another server running the same versions but here tagging works. I can't figure out what the difference is between the two though - suggestions on what to look for? It's hard to figure out what exactly is wrong since there's no error message. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
