[JIRA] [subversion-plugin] (JENKINS-24802) notifyCommit don't trigger a build if two svn repositories have same url start
Title: Message Title adoudev viaccess-orca commented on JENKINS-24802 Re: notifyCommit don't trigger a build if two svn repositories have same url start Hello, We have the same issue and the PR 99 on github seems to fix it so why not release it? Thanks, 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-26259) hudson.util.IOException2: Could not copy slave.jar into '/home/jenkins-build' on slave
adoudev viaccess-orca commented on JENKINS-26259 hudson.util.IOException2: Could not copy slave.jar into '/home/jenkins-build' on slave read-only file system error can also causing this copy failure error. 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] [sonar] (JENKINS-26330) Renaming global install sonar do not rename install name in job configuration
adoudev viaccess-orca updated JENKINS-26330 Renaming global install sonar do not rename install name in job configuration Change By: adoudev viaccess-orca (08/Jan/15 8:32 AM) Environment: Jenkins 1. 554 565 . 2 3 sonar plugin 2.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sonar] (JENKINS-26330) Renaming global install sonar do not rename install name in job configuration
adoudev viaccess-orca created JENKINS-26330 Renaming global install sonar do not rename install name in job configuration Issue Type: Bug Assignee: Sonar Team Components: sonar Created: 08/Jan/15 8:15 AM Description: Step to reproduce: Configure two installations named test1 and test2 (enought to reproduce) Manage Jenkins >> Configure System >> Sonar installations >> Add Sonar Create a job using post-build action Sonar, select test2 installation. Rename test2 global installation: Manage Jenkins >> Configure System >> Sonar installations Reopen the job that you created the sonar installation is now test1. When running the job it's failed saying that test2 installation doesn't exist. SONAR ANALYSIS FAILED FATAL: Sonar installation defined on this job (test2) do not match anything. Available installations count: 2. Environment: Jenkins 1.554.2 sonar plugin 2.1 Project: Jenkins Priority: Critical Reporter: adoudev viaccess-orca 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] [git] (JENKINS-25345) Git publisher; Tag message needs quote to create a tag
adoudev viaccess-orca commented on JENKINS-25345 Git publisher; Tag message needs quote to create a tag Hi Mark, Indeed, we cannot reproduce this bug today. We do not understand... random occurrence or PEBCAK 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] [git] (JENKINS-25345) Git publisher; Tag message needs quote to create a tag
adoudev viaccess-orca closed JENKINS-25345 as Cannot Reproduce Git publisher; Tag message needs quote to create a tag Change By: adoudev viaccess-orca (29/Oct/14 1:38 PM) Status: Open Closed Resolution: Cannot Reproduce 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] [git] (JENKINS-25345) Git publisher; Tag message needs quote to create a tag
adoudev viaccess-orca updated JENKINS-25345 Git publisher; Tag message needs quote to create a tag Change By: adoudev viaccess-orca (28/Oct/14 5:06 PM) Summary: Git publisher; Tag message needs double quote to create a tag Description: need to add double quote in tag message or create tag failed.tag message = tag message>git tag -a -f -m tag message tag # timeout=10tag message = "tag message">git tag -a -f -m "tag message" tag # timeout=10 Please note that quote are necessary to create the tag but also note that they are present in the tag. Same issue with simple quote. 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] [git] (JENKINS-25345) Git publisher; Tag message needs double quote to create a tag
adoudev viaccess-orca created JENKINS-25345 Git publisher; Tag message needs double quote to create a tag Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 28/Oct/14 4:34 PM Description: need to add double quote in tag message or create tag failed. tag message = tag message >git tag -a -f -m tag message tag # timeout=10 tag message = "tag message" >git tag -a -f -m "tag message" tag # timeout=10 Environment: Jenkins ver. 1.565.3 Git plugin 2.2.6 Project: Jenkins Priority: Minor Reporter: adoudev viaccess-orca 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-23425) View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp
adoudev viaccess-orca commented on JENKINS-23425 View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp I'm not able to reproduce it on a vanilla installation... I understand that it will be hard to debug if I can't reproduce 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/d/optout.
[JIRA] [core] (JENKINS-23425) View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp
adoudev viaccess-orca edited a comment on JENKINS-23425 View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp We just tried to : copy the job remove artifact publish launch the job view job page => not more war file in tomcat temp enable archiving artifact but NOT the war file launch the job view job page => war file in tomcat temp! 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-23425) View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp
adoudev viaccess-orca commented on JENKINS-23425 View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp We just tried to : copy the job remove artifact publish launch the job => not more war file in tomcat temp enable archiving artifact but NOT the war file launch the job => war file in tomcat temp! 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-23425) View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp
adoudev viaccess-orca updated JENKINS-23425 View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp Change By: adoudev viaccess-orca (13/Jun/14 12:50 PM) Summary: View or using REST api (json,xml) on a job building war publishing artifact do not delete war temp file in tomcat7 temp 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-23425) View or using REST api (json,xml) on a job building war do not delete temp file in tomcat7 temp
adoudev viaccess-orca created JENKINS-23425 View or using REST api (json,xml) on a job building war do not delete temp file in tomcat7 temp Issue Type: Bug Assignee: Christian Pelster Components: core, walldisplay Created: 13/Jun/14 12:45 PM Description: We faced to a problem with our Jenkins 1.537 into tomcat7; the tomcat7-tmp is full of war file. The problem have been put under the light when we started using wall display plug-in. We found out that it wasn't walldisplay that was causing this; but calls to the REST json api every 20 seconds. Calls are make on /job//api/json as you can see line 390 of this file : https://github.com/jenkinsci/walldisplay-plugin/blob/master/src/main/webapp/walldisplay.js The job also publish jar file but only war file is fulling the tomcat temp. We also see that not only REST api produce this temp war file! View the project page do this too. What we do not understand is why it's not happening to all job that publish war artifact... the job using: remove old build security based on project launch on a windows slave using Subversion publish Checkstyle analysis publish PMD analysis save artifacts (jar and war using *) If it's not a bug from Jenkins it may be a tomcat7 configuration error? Environment: Jenkins 1.537, tomcat7, Ubuntu 12.04.3 LTS Project: Jenkins Priority: Critical Reporter: adoudev viaccess-orca 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-16018) Not all builds show in the build history dashboard on job
adoudev viaccess-orca commented on JENKINS-16018 Not all builds show in the build history dashboard on job This is not related... We still have 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] [core] (JENKINS-16018) Not all builds show in the build history dashboard on job
adoudev viaccess-orca commented on JENKINS-16018 Not all builds show in the build history dashboard on job Hi all, Just to inform you that we did have this issue with some of our jobs with Jenkins ver. 1.517 and Jenkins ver. 1.537. We did some maintenance tasks: We increased the size of the temporary space of the master. We synchronized some of our slave's clock using ntp. Since those maintenance tasks, a month ago, we no more see this issue. I do not know if this is related. Hope this 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.
