[JIRA] (JENKINS-15891) Dependency arrows are missing
Ulli Hafner commented on JENKINS-15891 Dependency arrows are missing Ok, installing the UI plugin fixed 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
[JIRA] (JENKINS-15891) Dependency arrows are missing
Ulli Hafner closed JENKINS-15891 as Fixed Dependency arrows are missing Change By: Ulli Hafner (22/Nov/12 8:45 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collection compiler warnings with the eclipse compiler
Ulli Hafner commented on JENKINS-15895 Job stuck collection compiler warnings with the eclipse compiler Can you please attach a thread dump? Do the warnings contain relative paths? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15896) Spaces in the path when the configuration axis values have spaces
Murray Cumming
created JENKINS-15896
Spaces in the path when the configuration axis values have spaces
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
git
Created:
22/Nov/12 9:21 AM
Description:
When using a multi-configuration job, with a Configuration Matrix, if the axis values have spaces then those spaces appear in the directory used for the source code checkout. Although most builds should be able to cope with it, it's fairly unusual and an obstacle when the build cannot handle it yet.
For instance, I have this axis name:
configureoptions
and these axis values:
"--disable-calendar --disable-weather"
""
(Which I pass to our ./autogen.sh in the "Execute Shell" build step.)
Then the spaces in the path cause our build to fail:
make4: Leaving directory `/var/lib/jenkins/workspace/evolution-data-server/configureoptions/--disable-calendar --disable-weather/camel'
Making all in providers
make4: Entering directory `/var/lib/jenkins/workspace/evolution-data-server/configureoptions/--disable-calendar --disable-weather/camel/providers'
Making all in pop3
make5: Entering directory `/var/lib/jenkins/workspace/evolution-data-server/configureoptions/--disable-calendar --disable-weather/camel/providers/pop3'
CC libcamelpop3_la-camel-pop3-engine.lo
CC libcamelpop3_la-camel-pop3-folder.lo
CC libcamelpop3_la-camel-pop3-provider.lo
CC libcamelpop3_la-camel-pop3-settings.lo
CC libcamelpop3_la-camel-pop3-stream.lo
CC libcamelpop3_la-camel-pop3-store.lo
CCLD libcamelpop3.la
/bin/sed: unrecognized option '--disable-weather/camel/libcamel-1.2.la'
Usage: /bin/sed OPTION... {script-only-if-no-other-script} input-file...
Environment:
Ubuntu Linux 12.10 (Quantal)
Official Ubuntu Jenkins packages (Jenkins ver. 1.466.2)
Project:
Jenkins
Priority:
Major
Reporter:
Murray Cumming
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Nick Vancauwenberghe commented on JENKINS-13790 Subversion externals fail I hit... AssertionError: appears to be using unpatched svnkit at jar:file:/D:/Jenkins/plugins/subversion/WEB-INF/lib/svnkit-1.7.4-jenkins-3.jar!/org/tmatesoft/svn/core/wc/SVNEvent.class This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15897) !build command does not work for all builds
cforce created JENKINS-15897 !build command does not work for all builds Issue Type: Bug Assignee: kutzi Components: instant-messaging Created: 22/Nov/12 10:06 AM Description: the !build command only works for some builds, for others it says syntax is: 'build job [now|delays|m|h] parameterkey=value*' I use exactly the name from jenkins view, and there are no blanks or special chars. The name is correct and i have all necesarry right. Btw. Please extend decription which rights (in job and global) are needed to execute !build commands from im. Environment: openfire 3.7.1 jenkins 1.491 im plugin 1.23 Project: Jenkins Priority: Major Reporter: cforce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15898) Subversion back-end cannot handle renaming of jobs
Claes Wallin (韋嘉誠) created JENKINS-15898 Subversion back-end cannot handle renaming of jobs Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 22/Nov/12 10:14 AM Description: To reproduce: 1. Install and configure scm-sync-configuration to use Subversion. In my case, I was using a file:///... repo 2. Rename a job (configure job, change Project name). Expected result: Job is moved in Subversion repository. Actual result: 1. scm-sync-configuration.fail.log: "Error while checking in file to scm repository" 2. Nothing happens in Subversion repository. 3. Any changes after this are queued up but never checked in. Workaround: Use git rather than svn. When using git as a backend, the plugin behaves as expected. Or if you need svn, the workaround is to make sure to never rename jobs. Environment: CentOS 5.8 svn version 1.6.11 (r934486) Jenkins Subversion Plug-in 1.43 git version 1.7.11.3 Project: Jenkins Labels: subversion checkin Priority: Critical Reporter: Claes Wallin (韋嘉誠) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14550) Checksum mismatch while updating with Subversion Plugin 1.42
Bartosy Tworek commented on JENKINS-14550 Checksum mismatch while updating with Subversion Plugin 1.42 I've experienced same issue... lot of "Checksum mismatch while updating". Downgrading to subversion plugin ver 1.39 fixed that issue. Using Jenkins ver. 1.491 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15898) Subversion back-end cannot handle renaming of jobs
Claes Wallin (韋嘉誠) updated JENKINS-15898 Subversion back-end cannot handle renaming of jobs Change By: Claes Wallin (韋嘉誠) (22/Nov/12 10:16 AM) Description: Toreproduce:1.Installandconfigurescm-sync-configurationtouseSubversion.-Inmycase,Iwasusingafile:///...repo 2.Renameajob(configurejob,changeProjectname).Expectedresult:JobismovedinSubversionrepository.Actualresult:1.scm-sync-configuration.fail.log:Errorwhilecheckinginfiletoscmrepository2.NothinghappensinSubversionrepository.3.Anychangesafterthisarequeuedupbutnevercheckedin.Workaround:Usegitratherthansvn.Whenusinggitasabackend,thepluginbehavesasexpected.Orifyouneedsvn,theworkaroundistomakesuretoneverrenamejobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13632) AbstractMethodError with PTC Integrity Plugin
O H reopened JENKINS-13632 AbstractMethodError with PTC Integrity Plugin Unfortunately this is still an issue. If we upgrade the PTC Plugin we always get the error: FATAL: com.mks.connect.UserApplicationSessionImpl$SSLSocketFactory.createSocket(Ljava/lang/String;ILjava/net/InetAddress;ILorg/apache/commons/httpclient/params/HttpConnectionParams;)Ljava/net/Socket; java.lang.AbstractMethodError: com.mks.connect.UserApplicationSessionImpl$SSLSocketFactory.createSocket(Ljava/lang/String;ILjava/net/InetAddress;ILorg/apache/commons/httpclient/params/HttpConnectionParams;)Ljava/net/Socket; at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323) at com.mks.connect.UserApplicationSessionImpl.handleHTTPResponse(UserApplicationSessionImpl.java:304) at com.mks.connect.UserApplicationSessionImpl.getSession(UserApplicationSessionImpl.java:350) at com.mks.connect.UserApplicationSessionImpl.getSessionURI(UserApplicationSessionImpl.java:413) at com.mks.connect.HttpCmdRunnerImpl.getSessionURI(HttpCmdRunnerImpl.java:72) at com.mks.connect.HttpBlimpInputStream.getSessionURI(HttpBlimpInputStream.java:125) at com.mks.connect.HttpBlimpInputStream.blimpInitiate(HttpBlimpInputStream.java:152) at com.mks.connect.BlimpInputStream.getInputStream(BlimpInputStream.java:223) at com.mks.connect.BlimpInputStream.readNoEof(BlimpInputStream.java:693) at com.mks.connect.BlimpInputStream.handleNextBlimpCommand(BlimpInputStream.java:266) at com.mks.connect.BlimpInputStream.read(BlimpInputStream.java:190) This is absolutely reproducable! Due to this issue we weren't not able to upgrade our Jenkins a long time since the "patched" plugin version by me did not work with newer Jenkins installations. With the latest one (491) the "patched" version of the 4.12 works again. But if I replace the MKSApi.jar in the latest version of your plugin I get now: Preparing to execute si viewproject for #p=/Archiv/mks/develop/IFA/IFA.pj#s=5000_Construction/Product.pj#s=Java/Java.pj Checkout directory is C:\Jenkins\jobs\IFA_buildAndDist\workspace FATAL: null java.lang.IllegalArgumentException at java.util.concurrent.ThreadPoolExecutor.init(ThreadPoolExecutor.java:589) at java.util.concurrent.ThreadPoolExecutor.init(ThreadPoolExecutor.java:480) at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:59) at hudson.scm.IntegrityCheckoutTask.invoke(IntegrityCheckoutTask.java:322) at hudson.scm.IntegrityCheckoutTask.invoke(IntegrityCheckoutTask.java:25) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:825) So it is always a kind of gambling updating our Jenkins and PTC plugin. Any help would be highly appreciated... Change By: O H (22/Nov/12 10:19 AM) 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
[JIRA] (JENKINS-15898) Subversion back-end cannot handle renaming of jobs
Claes Wallin (韋嘉誠) updated JENKINS-15898 Subversion back-end cannot handle renaming of jobs Change By: Claes Wallin (韋嘉誠) (22/Nov/12 10:20 AM) Environment: CentOS5 SCMSyncConfigurationPlugin0 . 8svnversion1 0 .6. 11(r934486) 1 JenkinsSubversionPlug-in1.43 svnversion1.6.11(r934486) gitversion1.7.11.3 CentOS5.8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10222) Jenkins cleaning out workspace unnecessarily when polling SCM (SVN)
Andreas Schoen commented on JENKINS-10222 Jenkins cleaning out workspace unnecessarily when polling SCM (SVN) I had the same problem with a project with the Repository URL of the following pattern: svn://servername/applications/xxx//trunk/yyy The polling message was: Workspace doesn't contain svn://servername/applications/xxx//trunk/yyy. Need a new build. However, the polling did work successfully (no changes, at revision...) when I set the Repository URL to svn://servername/applications/xxx/trunk/yyy (without the second slash after xxx). It seems that the repository url in the working copy is normalized (e.g. removing double slashes, port number) by the svn client, but the check if the working copy matches the project does not perform this kind of normalization. Jenkins ver. 1.471 Subversion Plugin version 1.4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7114) aborting download of workspace files makes slave agent hang
Jes Struck commented on JENKINS-7114 aborting download of workspace files makes slave agent hang we have just upgraded from jenkins 1.490 - 1.491 and are still seing this issue we are on ubuntu 12.04 LTS on both master and slaves and using the ssh slave connector. is there any one that havesolved this. it stackes up in the log file quit fast. so the log file grows to 2-3 GB in a couple of hours This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Michael Clarke updated JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Reducing priority given there is a workaround (tick the 'Show all CVS Output' box) and that this does not seem to be impacting a lot of users Change By: Michael Clarke (22/Nov/12 12:49 PM) Priority: Blocker 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
[JIRA] (JENKINS-15872) Running 'rlog' after 'cvs up -r TAG' superfluous giving incorrect change log for the workspace
Michael Clarke updated JENKINS-15872 Running rlog after cvs up -r TAG superfluous giving incorrect change log for the workspace Reducing priority given this is only detecting additional changes and does not impact workspace contents or miss changes Change By: Michael Clarke (22/Nov/12 12:51 PM) Priority: Blocker Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15899) Use extended revision matching enhancement
Gilles Faucherand created JENKINS-15899 Use extended revision matching enhancement Issue Type: Task Assignee: Timothy Bingaman Components: ivy Created: 22/Nov/12 1:14 PM Description: Hello, I use the ivy plugin to build my projects following the dependency graph. We have for example several projects : A-1.0 exists but not in jenkins A-1.0.1a : A-1.0 branch to fix previous version already deployed B-1.0.1a : depends of A-1.0.1a B-1.1 : depends of A-1.0 I use the option "Use extended revision matching" to not build for example B-1.1 if A-1.0.1a is built, but B-1.1 is still built ! A-1.0 being not in jenkins, by default if you don't find the exact rev num then you use the default "module matching rule" ? Could you enhance "revision matching" to be strictly "rev num matching" else do nothing ? Or maybe, I'am not using your plugin correctly ? Let me know how I can help you to debug/log and/or fix myself the code if necessary. thanks for all. Gilles Due Date: 22/Nov/12 12:00 AM Environment: Linux Project: Jenkins Priority: Minor Reporter: Gilles Faucherand This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15899) Use extended revision matching enhancement
Gilles Faucherand updated JENKINS-15899 Use extended revision matching enhancement Change By: Gilles Faucherand (22/Nov/12 1:24 PM) Due Date: 22/Nov/12 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15900) A build failure in a parallel section does not mark it as failed
Damien Coraboeuf
created JENKINS-15900
A build failure in a parallel section does not mark it as failed
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
build-flow
Created:
22/Nov/12 1:53 PM
Description:
Using version 0.5, I still get this problem. Using the following flow:
guard {
build ("test-a")
parallel (
{ build("test-b") },
{ build("test-c") }
)
parallel (
{ build("test-d") },
{ build("test-e") }
)
} rescue {
build ("test-f")
}
Whenever "test-b" job fails (for example), "test-d" and "test-e" will be executed still. Is there something wrong with the syntax?
Project:
Jenkins
Priority:
Critical
Reporter:
Damien Coraboeuf
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14027) Build flow with parallel jobs requires read permissions for Anonymous, fails silently
SCM/JIRA link daemon commented on JENKINS-14027 Build flow with parallel jobs requires read permissions for Anonymous, fails silently Code changed in jenkins User: Nicolas De Loof Path: src/main/groovy/com/cloudbees/plugins/flow/FlowDSL.groovy http://jenkins-ci.org/commit/build-flow-plugin/ef1dab2cdc87fc021b97a8aae758a3c1ba9ee312 Log: FIXED JENKINS-14027 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14027) Build flow with parallel jobs requires read permissions for Anonymous, fails silently
SCM/JIRA link daemon resolved JENKINS-14027 as Fixed Build flow with parallel jobs requires read permissions for Anonymous, fails silently Change By: SCM/JIRA link daemon (22/Nov/12 2:10 PM) 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
[JIRA] (JENKINS-13790) Subversion externals fail
Jan Linnenkohl commented on JENKINS-13790 Subversion externals fail Hi Nick, the problem is, that the "patched" svnkit is already in use, but the "patches" for subversion 1.7 are still missing. May be you could write to the mailing list, because here seems none of the plugin developers to listen. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14550) Checksum mismatch while updating with Subversion Plugin 1.42
SCM/JIRA link daemon commented on JENKINS-14550 Checksum mismatch while updating with Subversion Plugin 1.42 Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/scm/subversion/UpdateUpdater.java http://jenkins-ci.org/commit/subversion-plugin/638f83527e8244aa086c5c2f571960c964f9acd5 Log: JENKINS-14550 SVNException E155017 may be wrapped into a E175002 so lookup the root cause This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15900) A build failure in a parallel section does not mark it as failed
Damien Coraboeuf
commented on JENKINS-15900
A build failure in a parallel section does not mark it as failed
I have found a workaround:
guard {
build ("test-a")
// Fast running jobs
def fast = parallel (
{ build("test-b") },
{ build("test-c") }
)
// Slow running jobs
def fastFailed = fast*.getResult()*.toString().any { result - !"SUCCESS".equals(result) }
if (!fastFailed) {
parallel (
{ build("test-d") },
{ build("test-e") }
)
}
} rescue {
build ("test-f")
}
It is not very nice but it does the trick...
Damien.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15901) Run shell script/batch job after prqa report generation
XYZ created JENKINS-15901 Run shell script/batch job after prqa report generation Issue Type: New Feature Assignee: Praqma Support Components: prqa Created: 22/Nov/12 3:36 PM Description: It would be useful to run a batch job behind the report generation. E.g. generated temporary files can be deleted or something else can be done there. I've installed the plugin post-build task. When I try to add this behind the prqa plugin it is always placed before! Regards, Frank Environment: Win 7 Project: Jenkins Priority: Major Reporter: XYZ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collection compiler warnings with the eclipse compiler
Stéphane Nicoll
updated JENKINS-15895
Job stuck collection compiler warnings with the eclipse compiler
Change By:
Stéphane Nicoll
(22/Nov/12 3:37 PM)
Description:
Ihaveamavenprojectstylewiththefollowingconfigurationforthemavencompilerplugin{code:java}pluginartifactIdmaven-compiler-plugin/artifactIdversion2.3.2/versionconfigurationsource1.6/sourcetarget1.6/targetcompilerIdjdt/compilerIdshowWarningstrue/showWarnings/configuration/plugin{code}Thejenkinsconfigscanforcompilerwarningsusingtwoparsers:EclipseJavacompilerandJavacompiler.Noneoftheadvancedoptionsareenabled(seescrenshot).Ihaveanotsobigprojectwitharound20compilerwarnings.IamrunningJenkins1.459withthewarningsplugin3.26andthisisworkingfine(thegraphisgenerated,newwarningsarefound,etc).IfIswitchtothenewconfiguration(andthatsbeenalongtimeIwanttoupgrade),thejobisstuckwhenparsingthewarnings.ThisisexactlysimilartoJENKINS-10097.Seetheconfigurationof1.459withthelatestwarningsplugins.
Alsoattachedathreadsdump.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collection compiler warnings with the eclipse compiler
Stéphane Nicoll updated JENKINS-15895 Job stuck collection compiler warnings with the eclipse compiler Change By: Stéphane Nicoll (22/Nov/12 3:38 PM) Attachment: config-491-warnings-4.18.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collection compiler warnings with the eclipse compiler
Stéphane Nicoll commented on JENKINS-15895 Job stuck collection compiler warnings with the eclipse compiler Hi, Sorry I was in the middle of updating this issue and the network went down. The only threadump I can attach is from my-jenkins:8080/threadDump and I haven't found any useful information there. Do you have a way to generate a reliable thread dump of the process? The warnings are all in java source files. I am attaching the config for the instance that is stuck 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
[JIRA] (JENKINS-15897) !build command does not work for all builds
kutzi commented on JENKINS-15897 !build command does not work for all builds Can you spot any pattern which jobs can be started and which not? Is there any relevant log info in Jenkins' log file? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15218) Dependency tree should be constrained to only contain relevant nodes in the path
wolfs commented on JENKINS-15218 Dependency tree should be constrained to only contain relevant nodes in the path The idea of the DependencyGraph View is to always show the weakly connected component containing the node. So this is desired behavior. What is the reason you do not want to have Test.Job.4 in the graph? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13632) AbstractMethodError with PTC Integrity Plugin
Cletus DSouza resolved JENKINS-13632 as Wont Fix AbstractMethodError with PTC Integrity Plugin As mentioned earlier, this is related to compatibility with the mksapi.jar and your Jenkins setup. There is little I can do about this issue other than you need to put focus on the Integrity development team to update their version of apache HTTP client in the mksapi.jar. With regards the latest issue you've encountered. It has nothing to do with this problem. You need to edit your job and set a value for the new 'Thread Pool' parameter that has been added. This will resolve your problem. Change By: Cletus DSouza (22/Nov/12 5:11 PM) Status: Reopened Resolved Fix Version/s: current Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15850) JavaScript view fails if one job has a '.' in the name
wolfs closed JENKINS-15850 as Fixed _javascript_ view fails if one job has a . in the name Change By: wolfs (22/Nov/12 5:55 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15661) Jenkins-RTC auto-pull SCM problem
Mark Lohmann
commented on JENKINS-15661
Jenkins-RTC auto-pull SCM problem
Same issue here.
Experienced with build 1.490:
RTC-Plugin v0.3 was not working. No changes reported in log file.
At the same time command
$ scm compare ws workspaceName stream streamName -u -P -r repositoryName -I s -C "|{name}|{email}|" -D "|-MM-dd-HH:mm:ss|"
was working correctly reporting the changes.
Workaround: Go back to long term supported release 1.480.1
and RTC-Plugin will probably do its job again, at least ist does 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
[JIRA] (JENKINS-15902) Add support for custom xcodebuild arguments
Francis Labrie created JENKINS-15902 Add support for custom xcodebuild arguments Issue Type: Improvement Assignee: Josh Kennedy Components: clang-scanbuild Created: 22/Nov/12 6:37 PM Description: It would like very useful to add a parameter field to this plugin to be able to set custom xcodebuild arguments. Just like the Xcode plugin. These arguments are typically build settings like FOO_BAR=YES. We need these to avoid some Xcode build phase when performing the C language analysis. Thank you very much. Project: Jenkins Priority: Major Reporter: Francis Labrie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15881) svn revision check failed when checking out older revision after HEAD build
kutzi resolved JENKINS-15881 as Duplicate svn revision check failed when checking out older revision after HEAD build Change By: kutzi (22/Nov/12 7:18 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15707) Cppcheck Trend graph is blank even though the plugin processes stats correctly
Gregory Boissinot resolved JENKINS-15707 as Fixed Cppcheck Trend graph is blank even though the plugin processes stats correctly I fixed it. Display 'all errors' is now checked by default. Change By: Gregory Boissinot (22/Nov/12 8:59 PM) 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
[JIRA] (JENKINS-14685) Subversion Plugin should be able to ignore property only commits (eps. Mergeinfos)
kutzi resolved JENKINS-14685 as Fixed Subversion Plugin should be able to ignore property only commits (eps. Mergeinfos) Will be in 1.44 Change By: kutzi (22/Nov/12 10:16 PM) 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
[JIRA] (JENKINS-15854) github-sqs-plugin amazon sns
Aaron Walker resolved JENKINS-15854 as Fixed github-sqs-plugin amazon sns Functionality added in version 1.3 of the SQS plugin. You need to manually configure the Github SNS service hook and need to make sure that you use the same SQS Queue name as you have configured in the Jenkins SQS Profile Change By: Aaron Walker (23/Nov/12 4:02 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
[JIRA] (JENKINS-15903) Broken URL for Monkey result icons
David Barri created JENKINS-15903 Broken URL for Monkey result icons Issue Type: Bug Assignee: Christopher Orr Components: android-emulator Created: 23/Nov/12 4:30 AM Description: Plugin is generating incorrect URL for Monkey icons (ie. icon displayed to indicate Monkey success or failure on build). The URL it generates is: http://xxx:yyy/static/8c6c454b/static/8c6c454b/plugin/android-emulator/icons/monkey-happy_48x48.png As you can see static/8c6c454b is repeated twice. Changing it to once works. Environment: Jenkins v1.490 android-emulator plugin v2.6 Linux 3.6.6-1-ARCH #1 SMP PREEMPT Mon Nov 5 11:57:22 CET 2012 x86_64 GNU/Linux Project: Jenkins Priority: Minor Reporter: David Barri This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15904) Perforce plugin issues wrong error message when it can't start cmd.exe to run p4.exe
Markus Strand created JENKINS-15904 Perforce plugin issues wrong error message when it cant start cmd.exe to run p4.exe Issue Type: Bug Assignee: Unassigned Components: perforce Created: 23/Nov/12 5:41 AM Description: When there is an error in the global configuration that injects broken environment variables (blank name for the variable) the Perforce-plugin fails with: Started by user testuser EnvInject - Loading node environment variables. Building remotely on testslave in workspace E:\build_e\workspace\Test_Component Using remote perforce client: testclient-12345678 Test_Component $ C:\apps\perforce\p4.exe workspace -o -S //test/test_stream testclient-12345678 Caught exception communicating with perforce. No output for: C:\apps\perforce\p4.exe workspace -o -S //test/test_stream testclient-12345678 com.tek42.perforce.PerforceException: No output for: C:\apps\perforce\p4.exe workspace -o -S //test/test_stream testclient-12345678 at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:384) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1528) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1489) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:795) at hudson.model.AbstractProject.checkout(AbstractProject.java:1195) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:579) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:468) at hudson.model.Run.run(Run.java:1408) at hudson.model.Build.run(Build.java:110) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) ERROR: Unable to communicate with perforce. No output for: C:\apps\perforce\p4.exe workspace -o -S //test/test_stream testclient-12345678 Finished: FAILURE The correct error would be something like, can't "run the command". Because the actual error is something like: Caused by: java.io.IOException: Cannot run program "cmd.exe" (in directory "E:\build_e\workspace\Test_Component"): CreateProcess error=87, The parameter is incorrect at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.init(Proc.java:244) Environment: Windows Project: Jenkins Priority: Major Reporter: Markus Strand This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15885) Not able to any configutation changes for existing jobs and new jobs
viral shah commented on JENKINS-15885 Not able to any configutation changes for existing jobs and new jobs Is there any updates on this Jira This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8792) --prefix ignored
Onno van der Straaten reopened JENKINS-8792 --prefix ignored On Windows Server 2008 this still does not work. I’m deploying latest release of Jenkins on Windows 2008 server. Now I want to run jenkins in web context /jenkins so I in my jenkins.xml I added a prefix. For example arguments-Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "BASE\jenkins.war" --httpPort=8282 --ajp13Port=8283 --prefix=/jenkins/arguments I also tried prefix=jenkins, so without the slash. Both produce same results. There is a 404 on all paths, the old one and the new one. I don't think it is possible to run under different web context. Change By: Onno van der Straaten (23/Nov/12 6:17 AM) Resolution: NotADefect 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
[JIRA] (JENKINS-8792) --prefix ignored
Onno van der Straaten updated JENKINS-8792 --prefix ignored Change By: Onno van der Straaten (23/Nov/12 6:31 AM) Assignee: OnnovanderStraaten 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
