[JIRA] [subversion] (JENKINS-6746) build revision is wrong/confusing when last changed is different
Roger C. Pao commented on JENKINS-6746 build revision is wrong/confusing when last changed is different I would have preferred SVN_REVISION match svn info Revision: while SVN_LAST_CHANGED_REV match svn info Last Changed Rev: to more closely match svn info output. 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-24082) Be able to force push for branch on git publisher
Mark Waite commented on JENKINS-24082 Be able to force push for branch on git publisher Force push from a Jenkins job seems like a very dangerous option. Can you describe further why you want a Jenkins job to be able to delete history from a repository? The Jenkins plugin can merge, and can push that merge result, so long as no intervening commit has been pushed to the destination branch in the central repository. If an intervening commit has been pushed to the destination branch, then the Jenkins job is not allowed to push the merge result because it would overwrite the intervening commit with that forced push. 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-24086) Add GIT_SPARSE or similar environment variable
Mark Waite resolved JENKINS-24086 as Won't Fix Add GIT_SPARSE or similar environment variable Change By: Mark Waite (02/Aug/14 12:42 AM) Status: Open Resolved Resolution: Won't Fix 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-24086) Add GIT_SPARSE or similar environment variable
Mark Waite commented on JENKINS-24086 Add GIT_SPARSE or similar environment variable Can't you just read the contents of .git/info/sparse-checkout? That is the file which git uses to record the definition of the sparse checkout, and it doesn't require that you determine how many environment variables were set. 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-20307) Job status page shows "Build has been executing for null on master"
Daniel Beck commented on JENKINS-20307 Job status page shows "Build has been executing for null on master" I'm almost sure I found the cause in Run.getExecutor(). Workaround should be -Dhudson.model.Hudson.flyweightSupport=false, because it affects only Flyweight tasks that run on One-off executors. 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] [jenkins-tracker] (JENKINS-24088) Stack trace java.lang.OutOfMemoryError: Java heap space
LNP created JENKINS-24088 Stack trace java.lang.OutOfMemoryError: Java heap space Issue Type: Bug Assignee: Unassigned Components: jenkins-tracker Created: 01/Aug/14 11:40 PM Description: I was building the java project and during the execution below is the message seen A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Unknown Source) at java.lang.AbstractStringBuilder.expandCapacity(Unknown Source) at java.lang.AbstractStringBuilder.ensureCapacityInternal(Unknown Source) at java.lang.AbstractStringBuilder.append(Unknown Source) at java.lang.StringBuilder.append(Unknown Source) at java.lang.StackTraceElement.toString(Unknown Source) at java.lang.String.valueOf(Unknown Source) at java.lang.StringBuilder.append(Unknown Source) at java.lang.Throwable.printStackTrace(Throwable.java:657) at java.lang.Throwable.printStackTrace(Throwable.java:720) at java.util.logging.SimpleFormatter.format(Unknown Source) at java.util.logging.StreamHandler.publish(Unknown Source) at java.util.logging.ConsoleHandler.publish(Unknown Source) at java.util.logging.Logger.log(Unknown Source) at java.util.logging.Logger.doLog(Unknown Source) at java.util.logging.Logger.log(Unknown Source) at org.eclipse.jetty.util.log.JavaUtilLog.warn(JavaUtilLog.java:70) at org.eclipse.jetty.server.handler.ContextHandler$Context.log(ContextHandler.java:2043) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:769) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) Let me know if more information required. Environment: Used Jenkins ver 1.572. Project: Jenkins Priority: Major Reporter: LNP 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-20307) Job status page shows "Build has been executing for null on master"
Daniel Beck reopened JENKINS-20307 Job status page shows "Build has been executing for null on master" Change By: Daniel Beck (01/Aug/14 11:39 PM) Resolution: Incomplete Status: Resolved Reopened Assignee: Daniel Beck 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] [artifactory] (JENKINS-18073) Allow variables in Artifactory deployment include/exclude patterns
Gregory Boissinot updated JENKINS-18073 Allow variables in Artifactory deployment include/exclude patterns Change By: Gregory Boissinot (01/Aug/14 11:13 PM) Component/s: artifactdeployer 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] [artifactdeployer] (JENKINS-18233) Artifacts archiver throws IOException2 ENOENT for files with special file names
Gregory Boissinot resolved JENKINS-18233 as Not A Defect Artifacts archiver throws IOException2 ENOENT for files with special file names It is not an ArifactDeployer plugin issue. It is a charset issue. Check your JAVA_OPTS environment variable. You can use set "JAVA_OPTS=%JAVA_OPTS% -Dfile.encoding=UTF8" Change By: Gregory Boissinot (01/Aug/14 11:09 PM) Status: Open Resolved Resolution: Not A Defect 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] [docker-build-step] (JENKINS-23704) Control over ports with docker build steps
SCM/JIRA link daemon commented on JENKINS-23704 Control over ports with docker build steps Code changed in jenkins User: Vojtech Juranek Path: src/main/java/org/jenkinsci/plugins/dockerbuildstep/cmd/StartCommand.java http://jenkins-ci.org/commit/docker-build-step-plugin/37aab429b6eeff9e29185a5c37885df18a00c9c0 Log: [FIXED JENKINS-23704] Allow specify port binding when starting the container Compare: https://github.com/jenkinsci/docker-build-step-plugin/compare/a8b40740b672...37aab429b6ee 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] [docker-build-step] (JENKINS-23704) Control over ports with docker build steps
SCM/JIRA link daemon resolved JENKINS-23704 as Fixed Control over ports with docker build steps Change By: SCM/JIRA link daemon (01/Aug/14 11:05 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 -- 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] [artifactdeployer] (JENKINS-18371) Custom URLs for artifact download link
Gregory Boissinot commented on JENKINS-18371 Custom URLs for artifact download link Does a new option 'Deploy artifacts to an HTTP server' suit you? Your remote HTTP server should support PUT protocols. 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-20307) Job status page shows "Build has been executing for null on master"
Michael Rose commented on JENKINS-20307 Job status page shows "Build has been executing for null on master" It is the parent. The configuration build seem to have the correct description. Sorry I accidentally clipped off the host last time. The on "HOSTNAME" portion of the string is correct. Started 46 sec ago Build has been executing for null on b261806 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] [artifactdeployer] (JENKINS-19664) Archived artifact of promoted build corrupted after download!
Gregory Boissinot commented on JENKINS-19664 Archived artifact of promoted build corrupted after download! What is the Content-type of the 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 -- 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-20307) Job status page shows "Build has been executing for null on master"
Daniel Beck commented on JENKINS-20307 Job status page shows "Build has been executing for null on master" Michael: Which of the Matrix builds shows this message? The parent? A regular configuration's build? Is there no node name specified (i.e. 'Build has been executing for null on' rather than 'Build has been executing for null on master' as described above)? 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Richard Mortimer commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Can you post the log please. If the correct build was installed the order of some messages should have changed. I would just like to confirm that before investigating further. Does the error always seem to happen for you? Knowing that will be a good data point! 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] [xunit] (JENKINS-14517) XUnit does not store threshold mode in config.xml
Ozan Turgut assigned JENKINS-14517 to Ozan Turgut XUnit does not store threshold mode in config.xml Change By: Ozan Turgut (01/Aug/14 10:36 PM) Assignee: Gregory Boissinot Ozan Turgut 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] [artifactdeployer] (JENKINS-23313) Overwrite Files or only cleanup files to be copied to remote directory
Gregory Boissinot
resolved JENKINS-23313 as Won't Fix
Overwrite Files or only cleanup files to be copied to remote directory
The plugin delegates internally to the very robust Atlassian copy-filesystem Ant task.
For your use case, I suggest use a separate directory between builds.
Maybe use the ${BUILD_ID} variable.
Change By:
Gregory Boissinot
(01/Aug/14 10:35 PM)
Status:
Open
Resolved
Resolution:
Won't Fix
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] [artifactdeployer] (JENKINS-20341) Artifcat deployer plugin is not working suddenly
Gregory Boissinot resolved JENKINS-20341 as Won't Fix Artifcat deployer plugin is not working suddenly I have difficulty managing the 'Delete' option because I don't have control on the external Jenkins infrastructure. I suggest not using this option and I would remove it in next versions. Change By: Gregory Boissinot (01/Aug/14 10:26 PM) Status: Open Resolved Resolution: Won't Fix 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-20307) Job status page shows "Build has been executing for null on master"
Michael Rose commented on JENKINS-20307 Job status page shows "Build has been executing for null on master" I am seeing this issue on version 1.559 for my multi-configuration (matrix) project. Started 6 min 42 sec ago Build has been executing for null on 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] [android-emulator] (JENKINS-23736) Emulator plugin can not run emulator if user is not logged on to desktop
Christopher Orr commented on JENKINS-23736 Emulator plugin can not run emulator if user is not logged on to desktop Searching for that error message seems to suggest that it's not possible without logging on to the desktop. For example: https://stackoverflow.com/questions/9157980/postbuild-uiautomation-script-not-running-in-jenkins https://stackoverflow.com/questions/13966595/build-unity-project-with-jenkins-failed We run OS X slaves and the emulator runs fine, but I think we run Jenkins in the way shown in those answers. 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] [perforce] (JENKINS-24087) Project constantly rebuilding when using multiple Perforce SCMs
Dane Wagner updated JENKINS-24087 Project constantly rebuilding when using multiple Perforce SCMs Change By: Dane Wagner (01/Aug/14 9:39 PM) Summary: Project constant constantly rebuilding when using multiple Perforce SCMs 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] [perforce] (JENKINS-24087) Project constantly rebuilding when using multiple Perforce SCMs
Rob Petti assigned JENKINS-24087 to Unassigned Project constantly rebuilding when using multiple Perforce SCMs Change By: Rob Petti (01/Aug/14 9:39 PM) Assignee: Rob Petti 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] [perforce] (JENKINS-24087) Project constant rebuilding when using multiple Perforce SCMs
Dane Wagner created JENKINS-24087 Project constant rebuilding when using multiple Perforce SCMs Issue Type: Bug Assignee: Rob Petti Components: perforce Created: 01/Aug/14 9:38 PM Description: We have multiple perforce servers set up and our projects pull code from both servers when building. I'm using the Multiple SCMs plugin to handle clientspecs to both of these servers. Everything seems to work except for the polling. It appears that only one SCMRevisionState is attached to a build or that only one is being retrieved when polling for changes. Here's the polling log showing the issue: Started on Aug 1, 2014 2:21:13 PM Polling SCM changes on dwagner-dev-t36 Looking for changes... Using node: dwagner-dev-t36 Using remote perforce client: [jenkins] $ p4 workspace -o [jenkins] $ p4 counter change [jenkins] $ p4 -s changes -s submitted ...@3477236,@10592344 Latest submitted change selected by workspace is 10592053 [jenkins] $ p4 describe -s 10592053 [jenkins] $ p4 -G where //... Looking for changes... Using node: dwagner-dev-t36 Using remote perforce client: [jenkins] $ p4 workspace -o [jenkins] $ p4 counter change [jenkins] $ p4 -s changes -s submitted ...@3477236,@3490195 No changes found. Done. Took 0.56 sec Changes found The problem is visible on this line: [jenkins] $ p4 -s changes -s submitted ...@3477236,@10592344 The starting changelist is the changelist from the second account. Digging through the code, it looks like the Multiple SCMs plugin uses scm.getKey() to differentiate SCMRevisionStates for each account. The Perforce plugin looks like it uses the parent hudson.scm.SCM.getKey(), which simply returns the class name. I don't have the facility to debug, but my guess is that implementing PerforceSCM.getKey() such that each account returned a different key based on P4PORT and the base clientspec would fix the problem. Environment: RHEL 6.5 Project: Jenkins Labels: plugin scm perforce multiple-scms Priority: Major Reporter: Dane Wagner 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-24086) Add GIT_SPARSE or similar environment variable
David Ruhmann created JENKINS-24086 Add GIT_SPARSE or similar environment variable Issue Type: Improvement Assignee: Nicolas De Loof Components: git Created: 01/Aug/14 9:37 PM Description: Add a GIT_SPARSE and GIT_SPARSE_N environment variables when sparse locations are entered. Environment: Git Plugin = 2.2.2 Jenkins = 1.574 Project: Jenkins Labels: git-plugin git Priority: Major Reporter: David Ruhmann 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] [artifactdeployer] (JENKINS-22180) Artifact Deployer does not handle OS type well
Frank Merrow commented on JENKINS-22180 Artifact Deployer does not handle OS type well Close it if you want, but you've missed the point. I don't want to run the job on Linux AND Windows . . . however, the job is setup so it can run on EITHER Linux or Windows. One option would be to "node lock" the job to a specific OS type using labels. But if the goal is to actually let the job build on either type . . . there is no way to know what type of OS you might actually build on for any given job run. Matrix Job would be ideal if I wanted to run both . . . I don't . . . I want to run "here" whatever here happens to be. The curse of running a combined Windows/Linux shop where both are equal. Frank 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] [artifactdeployer] (JENKINS-22180) Artifact Deployer does not handle OS type well
Gregory Boissinot resolved JENKINS-22180 as Fixed Artifact Deployer does not handle OS type well Use Matrix Job Type for this kind of issue. Change By: Gregory Boissinot (01/Aug/14 9:06 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 -- 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Bruno Perel edited a comment on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Thanks for the advice. I updated the plugin to version 2.12-SNAPSHOT but unfortunately got the exact same error log. 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Bruno Perel commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Hi, thanks for the advice. I updated the plugin to version 2.12-SNAPSHOT but got the exact same error log. 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] [jacoco] (JENKINS-24085) Coverage report differences between jacoco report and jenkins plugin
kingargyle created JENKINS-24085 Coverage report differences between jacoco report and jenkins plugin Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco Created: 01/Aug/14 8:15 PM Description: Recently upgraded to use android-maven-plugin 3.9.0-rc.3, and the jacoco plugin is no longer reporting the correct code coverage. If I run the maven jacoco report stage, the maven plugin will report the correct code coverage. The jacoco.exec file is created, and as far as I can tell is generating the right coverage as the site/jacoco report is correct. I've tried the lastest jenkins plugin as well a the latest jacoco maven plugin and it still reports differently. The only change I see is the android-maven-plugin and the code results to sure fire seem to be passed correctly. I can provide privately a same jacoco.exec for testing purposes if necessary. Project: Jenkins Priority: Major Reporter: kingargyle 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-22641) Jenkins no longer kills running processes after job fails
SCM/JIRA link daemon commented on JENKINS-22641 Jenkins no longer kills running processes after job fails Code changed in jenkins User: Kohsuke Kawaguchi Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/durable_task/ShellStepTest.java http://jenkins-ci.org/commit/workflow-plugin/e74fd8349c15568354fc3934010713503d22761f Log: added a test bug this is blocked by JENKINS-22641 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-18065) AbstractLazyLoadRunMap.iterator() calls .all()
SCM/JIRA link daemon commented on JENKINS-18065 AbstractLazyLoadRunMap.iterator() calls .all() Code changed in jenkins User: Jesse Glick Path: core/src/test/java/jenkins/model/lazy/AbstractLazyLoadRunMapTest.java core/src/test/java/jenkins/model/lazy/FakeMap.java http://jenkins-ci.org/commit/jenkins/8c70a2b76875d2ca6a114c45fd54c0b1e9ecb7d2 Log: JENKINS-18065 Uncommenting original test. The actual implementation does not behave as nicely as one would hope, for a few reasons: 1. isEmpty actually tries to load the newestBuild, rather than simply checking whether there is some idOnDisk. Arguably this is necessary, since there could be an unloadable build record, in which case it would be technically correct for the map to be considered empty. 2. Loading AbstractLazyLoadRunMap.newestBuild calls search(MAX_VALUE, DESC), which behaves oddly, by doing a binary search, and thus perhaps loading lg(|map|) entries. You would think that it would suffice to check for the last member of idOnDisk in index.byId. 3. The iterator eagerly loads the next value before hasNext has even been called. Looks bad in a test, though it probably has little practical impact since most callers would be calling hasNext soon afterward anyway. Might cause one extra build record to be loaded unnecessarily from a limited RunList. (cherry picked from commit 2f58ceb1a66c8ed621fa2562c5ed3445b29ea200) 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-22395) Run.delete (from LogRotator) failing with "...looks to have already been deleted"
SCM/JIRA link daemon commented on JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted" Code changed in jenkins User: Kohsuke Kawaguchi Path: test/src/test/java/jenkins/model/lazy/LazyBuildMixInTest.java http://jenkins-ci.org/commit/jenkins/2baa7caade6923b9a2023e64b60bb537fcc65077 Log: JENKINS-22395 I'm not sure if I understand how the original fix in PR #1190 (f1430a2) addresses the problem. My understanding is of the problem is as follows: someone deletes 'b2' but holds on to its reference (could be different threads) someone calls b2.getPreviousBuild() if b2.previousBuildR is null, then this triggers the loading of b1, and that process sets up a bi-di link via b1<>b2 via b1.nextBuildR <> b2.previousBuildR this makes b1.getNextBuild() incorrectly return b2 Presumably f1430a2 addresses this somehow, but I think I can induce this situation in other ways, which is what dropLinksAfterGC2() does. In this test, initial state: b1 <> b2 <> b3 we load everyone and connect them all up after deleting b2: b1 <> b3 ^^ b2 b1 and b3 points each other, and b2 still refers to each side after dropping b1: b2 --> b3 now, here, when I do b2.getPreviousBuild(), it loads b1a and it sets b1a.nextBuildR to b2. b1a <-> b2 --> b3 So I claim this is a proof that the fix is incomplete, even for the problem JENKINS-22395 has discovered. I don't think that the problem is for the dropLinks call to fail to patch up references. The problem is that b2.getPreviousBuild() forcing b1 to point to b2, because if b2 is deleted and assumed to be invalid, then no matter what bX this method will find you never want bX.nextBuildR to point to b2. (cherry picked from commit 53e95ee517259e1e10d7209bcbaa4314397c1f40) 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-22395) Run.delete (from LogRotator) failing with "...looks to have already been deleted"
SCM/JIRA link daemon commented on JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted" Code changed in jenkins User: Jesse Glick Path: test/src/test/java/jenkins/model/lazy/LazyBuildMixInTest.java http://jenkins-ci.org/commit/jenkins/579753403c63886cf0feff177602d79254829780 Log: JENKINS-22395 Taking advantage of BuildReference.clear (just introduced in b6226ad) to simplify test by not requiring a custom build reference holder just to simulate GC. Confirmed that dropLinksAfterGC and dropLinksAfterGC2 both fail in the expected way (b1a.nextBuild == b2) after commenting out the call to createReference().clear() in dropLinks. (Also that they fail as expected in assertNotSame if the reference is not cleared at all.) (cherry picked from commit b7ec8578f938864af9c8dbfb73a54d67f972d694) 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-22395) Run.delete (from LogRotator) failing with "...looks to have already been deleted"
SCM/JIRA link daemon commented on JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted" Code changed in jenkins User: Kohsuke Kawaguchi Path: test/src/test/java/jenkins/model/lazy/LazyBuildMixInTest.java http://jenkins-ci.org/commit/jenkins/3f0388379b06b31ebec1bf17cc976001fcd80b7b Log: JENKINS-22395 correcting the control test As I step-executed the code, I discovered b2.getPreviousBuild() was getting invoked between BRHF.drop(b1) and b2.dropLinks() call, in PeepholePermalink.RunListenerImpl.onDeleted() because Run.delete() calls RunListener.fireDeleted(this). Thus in effect the sequence of the call order was as follows: assertEquals(1, BRHF.drop(b1)); b2.getPreviousBuild(); // happens indirectly in PeepholePermalink b2.delete(); FreeStyleBuild b1a = b2.getPreviousBuild(); This defeats the purpose of the fix, because in this call sequence, by b2.dropLinks() as implemented before f1430a2 will correctly fix up b1a.nextBuildR to b3. For the test to work as intended, it is important that b2.previousBuildR.get()==null during dropLinks(). That is what causes b2.getPreviousBuild() in the next line to go load b1a, and sets up b1a.nextBuildR to b2, and trigger the assertion error. Added a code to remove all RunListeners. With this change, the test now fails without the fix in f1430a2. (cherry picked from commit 7b1b50c85a6a4bdb75f1ae5b40885afa45f96b82) 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-22395) Run.delete (from LogRotator) failing with "...looks to have already been deleted"
SCM/JIRA link daemon commented on JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted" Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/jenkins/model/lazy/LazyBuildMixIn.java http://jenkins-ci.org/commit/jenkins/ca156f730b9aedac9072f7243e3f1528330ca68b Log: JENKINS-22395 more diagnostics Just in case the previous fix didn't address the root cause of ZD-11985 (and given the time it takes for changes like this to land in LTS), I'm adding additional diagnostics that let us track how previous/next builds are getting discovered (cherry picked from commit aa8e0b4f0e312ba4ef9c647ccf2c093793a9bece) 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-18065) AbstractLazyLoadRunMap.iterator() calls .all()
SCM/JIRA link daemon commented on JENKINS-18065 AbstractLazyLoadRunMap.iterator() calls .all() Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/model/lazy/LazyLoadRunMapEntrySet.java http://jenkins-ci.org/commit/jenkins/f1b0779c6d356db8fb0de6c89bd5bc03483d6b34 Log: JENKINS-18065 54c0846 amendment: presumably RunMap.entrySet().iterator().next().setValue(…) should be illegal. (cherry picked from commit da57ad5c30b1c9ca8365f869638abd29c8fb5896) 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-18065) AbstractLazyLoadRunMap.iterator() calls .all()
SCM/JIRA link daemon commented on JENKINS-18065 AbstractLazyLoadRunMap.iterator() calls .all() Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/util/RunList.java core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java core/src/main/java/jenkins/model/lazy/LazyLoadRunMapEntrySet.java core/src/test/java/jenkins/model/lazy/AbstractLazyLoadRunMapTest.java http://jenkins-ci.org/commit/jenkins/632d7fe0d01d492e0803495691f4397980cf44e0 Log: [FIXED JENKINS-18065] made ALLRM.entrySet() smarter (cherry picked from commit 54c084613f83f9b7a02957eb98dbd8dc661d1c9c) Conflicts: changelog.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/d/optout.
[JIRA] [core] (JENKINS-20663) file name encoding broken in zip archives
SCM/JIRA link daemon commented on JENKINS-20663 file name encoding broken in zip archives Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/DirectoryBrowserSupport.java http://jenkins-ci.org/commit/jenkins/e6a46d880dc7eaf06a6df368b0a42156447c0a6d Log: [FIXED JENKINS-20663] For now, go back to using ZipOutputStream from Ant that supports setting the filename encoding (present in java.util.zip only in Java 7+). (cherry picked from commit 84c76253862a2f36f813a7aa45b77d99c1616be4) Conflicts: changelog.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/d/optout.
[JIRA] [core] (JENKINS-22395) Run.delete (from LogRotator) failing with "...looks to have already been deleted"
SCM/JIRA link daemon commented on JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted" Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/jenkins/model/lazy/BuildReference.java core/src/main/java/jenkins/model/lazy/LazyBuildMixIn.java http://jenkins-ci.org/commit/jenkins/4bfa16143705e219705ff667c6917a2d6a6a8939 Log: [FIXED JENKINS-22395] redoing the fix in f1430a2 Based on the last few commits, I proved that the original fix in f1430a2 doesn't really address the problem. That is, once b2 is deleted, and after sufficient garbage collection, we can make b2.previousBuild.get() be null, and then b2.getPreviousBuild().getNextBuild() ends up incorrectly returning b2. In this commit, I roll back that part of f1430a2, and then fix the problem differently. I started thinking that the main problem we are trying to fix here is that the deleted build object should be unreferenceable. That is, it should behave almost as if the object has already been GCed. The easiest way to do this is to clear a BuildReference object, since we always use the same BuildReference object for all inbound references. This change allows us to clear BuildReference. Code like b2.getPreviousBuild() will continue to try to update b1.nextBuildR to b2, but it will only end up wiping out the field, only to have b1.getNextBuild() recompute the correct value. This fix makes both test cases pass in LazyBuildMixInTest. (cherry picked from commit b6226ad2d1a332cb661ceb5c5f5b673771118e14) 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-18116) text() function does not work in xpath evaluation on XML API
SCM/JIRA link daemon commented on JENKINS-18116 text() function does not work in xpath evaluation on XML API Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/Api.java http://jenkins-ci.org/commit/jenkins/58e6c7ba4d7fafc9dcfd349476876e2876b86d5b Log: [JENKINS-17374 JENKINS-18116] Don't set gzip header for error (cherry picked from commit 0a241aafdbdf3ad15d34efa3077658c5770b9195) 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-23410) Kill win32 processes from win64 JVMs
SCM/JIRA link daemon commented on JENKINS-23410 Kill win32 processes from win64 JVMs Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/pom.xml http://jenkins-ci.org/commit/jenkins/6b9c4ee6e8905a6eb701a95fcca63559e6bf2fa1 Log: [FIXED JENKINS-23410] Integrated the fix made in winp 1.20. (cherry picked from commit fad3f7db48e4184221469fbbb0edc2163e26ac0f) 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-17374) Direct links to project page leads to 404 errors
SCM/JIRA link daemon commented on JENKINS-17374 Direct links to project page leads to 404 errors Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/Api.java http://jenkins-ci.org/commit/jenkins/58e6c7ba4d7fafc9dcfd349476876e2876b86d5b Log: [JENKINS-17374 JENKINS-18116] Don't set gzip header for error (cherry picked from commit 0a241aafdbdf3ad15d34efa3077658c5770b9195) 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] [ec2] (JENKINS-17086) Use IAM Role when creating instance
Fred Drake commented on JENKINS-17086 Use IAM Role when creating instance Hmm. I just noticed this has been marked as resolved, but the EC2 plugin I just installed into a test jenkins doesn't appear to include this. Does this remain unreleased? 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-24084) Slave file leak
mrobinet created JENKINS-24084 Slave file leak Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 01/Aug/14 6:57 PM Description: Random slave processes are having file locks to files in the workspace hanging around after builds complete. I used http://file-leak-detector.kohsuke.org/ to get a stack trace of the lock: #20 C:\jenkins\workspace\Browser Tests (Smoke)\BrowserType\Firefox\OS\windows\TestCategory\BrowserRegistration\Bin\Release\Test\System.Net.Http.Extensions.xml by thread:pool-1-thread-728 for channel on Wed Jul 30 13:23:30 CDT 2014 at java.io.FileOutputStream.(Unknown Source) at java.io.FileOutputStream.(Unknown Source) at hudson.FilePath$32.call(FilePath.java:1715) at hudson.FilePath$32.call(FilePath.java:1710) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) I can reproduce it within a few days usually, so let me know if more information is needed. Environment: Windows Server 2012 R2 Java 1.7.0_55-b13 Project: Jenkins Priority: Major Reporter: mrobinet 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] [warnings] (JENKINS-23827) Puppet-lint regex matching too much
Ulli Hafner commented on JENKINS-23827 Puppet-lint regex matching too much Thanks. Can you please update the existing test case so that the example will be correctly parsed 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/d/optout.
[JIRA] [ec2] (JENKINS-17086) Use IAM Role when creating instance
Fred Drake commented on JENKINS-17086 Use IAM Role when creating instance Being able to use instance roles would be a big plus for me as well. 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] [p4] (JENKINS-24070) Error: Wipe Out Workspace blocked by SCM
Grant Limberg commented on JENKINS-24070 Error: Wipe Out Workspace blocked by SCM Yes this is via the "Wipe Out Current Workspace" option. Most of our projects in Jenkins are just sync & incremental build, but there's always that occasion where CMake decides to mess something up and a clean build is required. Having to go edit the project settings, switch it to "Forced clean and sync", kick off a build, and switch it back to "Sync Only" is a lot of steps to take, especially when the competing plugin makes it so much easier. Just wipe out current workspace, and rebuild. A full p4 sync -f is done automatically. 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-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
David McWhorter
commented on JENKINS-20427
Build Parameter variable in branch name causes polling to detect false changes in GIT
same issue for me, ${BRANCH} in Branch Specifier is ignored
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-24080) set-build-result and set-build-parameter do insufficient checks
dogfood commented on JENKINS-24080 set-build-result and set-build-parameter do insufficient checks Integrated in jenkins_main_trunk #3573 [FIXED JENKINS-24080] Improved security of CommandDuringBuild and its current implementations. (Revision 137c90cc612ddb3a51d050be298dcd2e0ae86a4c) Result = SUCCESS Jesse Glick : 137c90cc612ddb3a51d050be298dcd2e0ae86a4c Files : core/src/main/java/hudson/cli/SetBuildParameterCommand.java core/src/main/java/hudson/cli/SetBuildResultCommand.java test/src/test/groovy/hudson/cli/SetBuildParameterCommandTest.groovy core/src/main/java/hudson/cli/CommandDuringBuild.java changelog.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/d/optout.
[JIRA] [crowd2] (JENKINS-22136) Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security
Kanstantsin Shautsou edited a comment on JENKINS-22136 Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security Page not found. Crowd doesn't do anything with authorization. It provides groups that belong to user for other jenkins routines. Crowd works perfect with role-based 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/d/optout.
[JIRA] [crowd2] (JENKINS-22136) Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security
Kanstantsin Shautsou commented on JENKINS-22136 Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security Page not found. Crowd doesn't do anything with authorization. Crowd works perfect with role-based 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/d/optout.
[JIRA] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Richard Mortimer commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Are you able to try following android emulator plugin build It will be interesting to see if it helps your situation. 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] [crowd2] (JENKINS-16703) Too many periodic requests to Crowd server
Kanstantsin Shautsou commented on JENKINS-16703 Too many periodic requests to Crowd server Is it still reproducible with 1.8 version? 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] [crowd2] (JENKINS-16978) NoHttpResponseException with working Crowd2-Plugin
Kanstantsin Shautsou resolved JENKINS-16978 as Cannot Reproduce NoHttpResponseException with working Crowd2-Plugin Check your network and crowd as java application latency for replies. Check new connection options available from 1.7 version. Change By: Kanstantsin Shautsou (01/Aug/14 4:22 PM) Status: Open Resolved Assignee: Thorsten Heit Kanstantsin Shautsou 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] [crowd] (JENKINS-18731) crowd authentication suddenly stopped working after chaning the domain of jenkins
Kanstantsin Shautsou resolved JENKINS-18731 as Cannot Reproduce crowd authentication suddenly stopped working after chaning the domain of jenkins Try latest 1.8 version and try reproduce. Change By: Kanstantsin Shautsou (01/Aug/14 4:19 PM) Status: Open Resolved 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] [jiratestresultreporter] (JENKINS-24083) Jira Plug-In Not Working
Jeremy Walker created JENKINS-24083 Jira Plug-In Not Working Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jiratestresultreporter Created: 01/Aug/14 4:18 PM Description: When I try to use the Jira reporter plug-in to connect our Jenkins instance with an (Atlassian-hosted) Jira instance, it fails to work. When I check the debug output, I have: 17:54:23 Build step 'Publish JUnit test result report' changed build result to UNSTABLE 17:54:25 [JiraTestResultReporter] [INFO] Examining test results... 17:54:25 [JiraTestResultReporter] [DEBUG] Build result is UNSTABLE 17:54:25 17:54:25 [JiraTestResultReporter] [DEBUG] [JiraTestResultReporter] [INFO] Workspace is /home/jenkins/webapps/syapse/src/syapse 17:54:25 17:54:29 [JiraTestResultReporter] [DEBUG] projectKey: AP 17:54:29 [JiraTestResultReporter] [DEBUG] errorDetails: expected false to equal true 17:54:29 [JiraTestResultReporter] [DEBUG] fullName: AccountCredentialsContentView FAKE! (do not panic).please ignore: Jeremy W. is testing the Jira-Jenkins plug-in 17:54:29 [JiraTestResultReporter] [DEBUG] simpleName: AccountCredentialsContentView FAKE! (do not panic) 17:54:29 [JiraTestResultReporter] [DEBUG] title: Case Result: please ignore: Jeremy W. is testing the Jira-Jenkins plug-in 17:54:29 [JiraTestResultReporter] [DEBUG] packageName: (root) 17:54:29 [JiraTestResultReporter] [DEBUG] name: please ignore: Jeremy W. is testing the Jira-Jenkins plug-in 17:54:29 [JiraTestResultReporter] [DEBUG] className: AccountCredentialsContentView FAKE! (do not panic) 17:54:29 [JiraTestResultReporter] [DEBUG] failedSince: 1470 17:54:29 [JiraTestResultReporter] [DEBUG] status: FAILED 17:54:29 [JiraTestResultReporter] [DEBUG] age: 1 17:54:29 [JiraTestResultReporter] [DEBUG] ErrorStackTrace: Error: expected false to equal true 17:54:29 at file:///home/jenkins/webapps/syapse/src/syapse/static/js/test/expectjQueryAssertions.js?v=undefined:96 17:54:29 at file:///home/jenkins/webapps/syapse/src/syapse/static/js/ext/expect.js:203 17:54:29 at file:///home/jenkins/webapps/syapse/src/syapse/static/js/ext/expect.js:73 17:54:29 at file:///home/jenkins/webapps/syapse/src/syapse/static/js/test/mocha/account/views/AccountCredentialsContentViewTests.js?v=undefined:20 17:54:29 at file:///home/jenkins/webapps/syapse/src/syapse/static/js/ext/mocha/mocha.js:4106 17:54:29 at file:///home/jenkins/webapps/syapse/src/syapse/static/js/ext/mocha/mocha.js:4475 17:54:29 at file:///home/jenkins/webapps/syapse/src/syapse/static/js/ext/mocha/mocha.js:4534 17:54:29 at next (file:///home/jenkins/webapps/syapse/src/syapse/static/js/ext/mocha/mocha.js:4401) 17:54:29 at file:///home/jenkins/webapps/syapse/src/syapse/static/js/ext/mocha/mocha.js:4410 17:54:29 at next (file:///home/jenkins/webapps/syapse/src/syapse/static/js/ext/mocha/mocha.js:4354) 17:54:29 at file:///home/jenkins/webapps/syapse/src/syapse/static/js/ext/mocha/mocha.js:4378 17:54:29 at timeslice (file:///home/jenkins/webapps/syapse/src/syapse/static/js/ext/mocha/mocha.js:5361) 17:54:29 [JiraTestResultReporter] [DEBUG] affectedFile: Error: expected false to equal true 17:54:29 at file:///static/js/test/expectjQueryAssertions.js?v=undefined:96 17:54:29 at file:///static/js/ext/expect.js:203 17:54:29 at file:///static/js/ext/expect.js:73 17:54:29 at file:///static/js/test/mocha/account/views/AccountCredentialsContentViewTests.js?v=undefined:20 17:54:29 at file:///static/js/ext/mocha/mocha.js:4106 17:54:29 at file:///static/js/ext/mocha/mocha.js:4475 17:54:29 at file:///static/js/ext/mocha/mocha.js:4534 17:54:29 at next (file:///static/js/ext/mocha/mocha.js:4401) 17:54:29 at file:///static/js/ext/mocha/mocha.js:4410 17:54:29 at next (file:///static/js/ext/mocha/mocha.js:4354) 17:54:29 at file:///static/js/ext/mocha/mocha.js:4378 17:54:29 at timeslice (file:///static/js/ext/mocha/mocha.js:5361) 17:54:29 [JiraTestResultReporter] [DEBUG] 17:54:29 [JiraTestResultReporter] [DEBUG] Cr
[JIRA] [crowd2] (JENKINS-22774) Crowd2 does not honor Crowd's Session Timeout
Kanstantsin Shautsou resolved JENKINS-22774 as Incomplete Crowd2 does not honor Crowd's Session Timeout Change By: Kanstantsin Shautsou (01/Aug/14 4:16 PM) Status: Open Resolved Assignee: Thorsten Heit Kanstantsin Shautsou Resolution: Incomplete 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] [crowd2] (JENKINS-21852) Allow configuration of HTTPS proxy for connection to Crowd
Kanstantsin Shautsou resolved JENKINS-21852 as Fixed Allow configuration of HTTPS proxy for connection to Crowd Change By: Kanstantsin Shautsou (01/Aug/14 4:17 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 -- 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] [ui-changes] (JENKINS-24079) Getting a Crash in IE10 when configuring Jenkins
George Li commented on JENKINS-24079 Getting a Crash in IE10 when configuring Jenkins I did not see any empty name attributes (viewed source in Chrome) . 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] [crowd2] (JENKINS-22775) Crowd2 seems to destroy user session when using SSO
Kanstantsin Shautsou commented on JENKINS-22775 Crowd2 seems to destroy user session when using SSO Does this comment solves issue? Why plugin and jenkins version is not specified? 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-22472) CommandDuringBuild not automatically authenticated
Jesse Glick commented on JENKINS-22472 CommandDuringBuild not automatically authenticated Right, there is a chance of an environment variable leaking to others in the build log or similar. An alternative would be a designated file in the slave root containing a secret which the CLI agent would have to be modified to look for and send back to the master; this would not be protected from other builds on the same slave, but then again neither is your workspace. The ideal is to send the secret over a file descriptor inherited only via things started by the Launcher (akin to how ssh-agent works), but this is not portable to Windows that I know 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/d/optout.
[JIRA] [core] (JENKINS-24050) All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting
Kevin Browder commented on JENKINS-24050 All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting I have filed a pull request: https://github.com/jenkinsci/remoting/pull/24 Some might consider avoiding the error and catching it a bit paranoid, but I'm not entirely sure about concurrency issues with NIO. Additionally I still don't have a good test for this, I guess you'd need to cancel the key before calling key.isReadable(), but there's probably a very narrow window there. 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-24050) All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting
Kevin Browder edited a comment on JENKINS-24050 All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting @James: So I think the closed channel exception is actually closer to the Jenkins-22932 bug (if so you should repopen, since I had reopened before realizing I had a different root cause I then closed). However one could argue that the "selector" loop should actually catch all NIO errors and try again instead of it's current behavior of killing the loop entirely so it might be the case that the fix ends up being the same. Additionally I've implemented a patch that implements the key.isValid() check above: https://github.com/kbrowder/remoting/commit/d52cef17a789bac0d1478c561c6696a82eb9ab6a Additionally I've got another change that captures CancelledKeyExceptions: https://github.com/kbrowder/remoting/commit/1dc29075e26c382b593d189a3a04cd1ab859f7c5 And have filed a pull request: https://github.com/jenkinsci/remoting/pull/24; I freely admit having both is a bit paranoid but it seems like it's reasonably OK? Actually I think with some minor modification you could extend this last approach to catch a number of potential pitfalls 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-24082) Be able to force push for branch on git publisher
Guilhem Lettron created JENKINS-24082 Be able to force push for branch on git publisher Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 01/Aug/14 4:10 PM Description: We can't force push when pushing to a remote branch. Project: Jenkins Priority: Major Reporter: Guilhem Lettron 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-24050) All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting
Kevin Browder edited a comment on JENKINS-24050 All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting @James: So I think the closed channel exception is actually closer to the Jenkins-22932 bug (if so you should repopen, since I had reopened before realizing I had a different root cause I then closed). However one could argue that the "selector" loop should actually catch all NIO errors and try again instead of it's current behavior of killing the loop entirely so it might be the case that the fix ends up being the same. Additionally I've implemented a patch that implements the key.isValid() check above: https://github.com/kbrowder/remoting/commit/d52cef17a789bac0d1478c561c6696a82eb9ab6a Additionally I've got another change that captures CancelledKeyExceptions: https://github.com/kbrowder/remoting/commit/1dc29075e26c382b593d189a3a04cd1ab859f7c5 Actually I think with some minor modification you could extend this last approach to catch a number of potential pitfalls 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Bruno Perel edited a comment on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I have this issue as well. My build log is the following : $ /var/lib/jenkins/tools/android-sdk/tools/android list target [android] Using Android SDK: /var/lib/jenkins/tools/android-sdk $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb start-server [android] Starting Android emulator [android] Erasing existing emulator data... $ /var/lib/jenkins/tools/android-sdk/tools/emulator64-arm -no-boot-anim -ports 5747,5748 -prop persist.sys.language=fr -prop persist.sys.country=FR -avd hudson_fr-FR_240_WVGA_android-17_armeabi-v7a -no-snapshot-load -no-snapshot-save -wipe-data -no-window -no-audio -gpu off * daemon not running. starting it now on port 5749 * * daemon started successfully * Failed to Initialize backend EGL display $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect emulator-5747 [android] Waiting for emulator to finish booting... $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s emulator-5747 shell getprop dev.bootcomplete error: device offline error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect emulator-5747 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s emulator-5747 shell getprop dev.bootcomplete error: device offline error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect emulator-5747 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s emulator-5747 shell getprop dev.bootcomplete error: device offline error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect emulator-5747 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect emulator-5747 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s emulator-5747 shell getprop dev.bootcomplete error: device offline error: device offline and then continues infinitely. I can reproduce it all the time. I run on Debian 3.14.4-1 (headless), Jenkins version 1.574 with Android Emulator plugin version 2.11.1. I configured the emulator to run android-17 with "Reset emulator state at start-up" checked. 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Bruno Perel commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I have this issue as well. My build log is the following : $ /var/lib/jenkins/tools/android-sdk/tools/android list target [android] Using Android SDK: /var/lib/jenkins/tools/android-sdk $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb start-server [android] Starting Android emulator [android] Erasing existing emulator data... $ /var/lib/jenkins/tools/android-sdk/tools/emulator64-arm -no-boot-anim -ports 5747,5748 -prop persist.sys.language=fr -prop persist.sys.country=FR -avd hudson_fr-FR_240_WVGA_android-17_armeabi-v7a -no-snapshot-load -no-snapshot-save -wipe-data -no-window -no-audio -gpu off * daemon not running. starting it now on port 5749 * * daemon started successfully * Failed to Initialize backend EGL display $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect emulator-5747 [android] Waiting for emulator to finish booting... $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s emulator-5747 shell getprop dev.bootcomplete error: device offline error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect emulator-5747 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s emulator-5747 shell getprop dev.bootcomplete error: device offline error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect emulator-5747 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s emulator-5747 shell getprop dev.bootcomplete error: device offline error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect emulator-5747 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect emulator-5747 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s emulator-5747 shell getprop dev.bootcomplete error: device offline error: device offline and then continues infinitely. I can reproduce it all the time. I run on Debian 3.14.4-1, Jenkins version 1.574 with Android Emulator plugin version 2.11.1. I configured the emulator to run android-17 with "Reset emulator state at start-up" checked. 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-23713) Remove AbstractProject-ness from BuildStep
Jesse Glick started work on JENKINS-23713 Remove AbstractProject-ness from BuildStep Change By: Jesse Glick (01/Aug/14 3:59 PM) Status: Open In Progress 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-23713) Remove AbstractProject-ness from BuildStep
Jesse Glick assigned JENKINS-23713 to Jesse Glick Remove AbstractProject-ness from BuildStep Change By: Jesse Glick (01/Aug/14 3:59 PM) Assignee: Kohsuke Kawaguchi Jesse Glick 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-24080) set-build-result and set-build-parameter do insufficient checks
SCM/JIRA link daemon resolved JENKINS-24080 as Fixed set-build-result and set-build-parameter do insufficient checks Change By: SCM/JIRA link daemon (01/Aug/14 3:51 PM) Status: In Progress 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/d/optout.
[JIRA] [core] (JENKINS-22472) CommandDuringBuild not automatically authenticated
Daniel Beck commented on JENKINS-22472 CommandDuringBuild not automatically authenticated Environment variables may be too public to act as authorization. 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] [ui-changes] (JENKINS-24079) Getting a Crash in IE10 when configuring Jenkins
Daniel Beck commented on JENKINS-24079 Getting a Crash in IE10 when configuring Jenkins Could you check to see whether there's a form element in the HTML with an empty string as name attribute value, i.e. name=""? If so, this would duplicate JENKINS-23724. See also https://github.com/jenkinsci/jenkins/pull/1346 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-24080) set-build-result and set-build-parameter do insufficient checks
SCM/JIRA link daemon commented on JENKINS-24080 set-build-result and set-build-parameter do insufficient checks Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/cli/CommandDuringBuild.java core/src/main/java/hudson/cli/SetBuildParameterCommand.java core/src/main/java/hudson/cli/SetBuildResultCommand.java test/src/test/groovy/hudson/cli/SetBuildParameterCommandTest.groovy http://jenkins-ci.org/commit/jenkins/137c90cc612ddb3a51d050be298dcd2e0ae86a4c Log: [FIXED JENKINS-24080] Improved security of CommandDuringBuild and its current implementations. Compare: https://github.com/jenkinsci/jenkins/compare/4f27f4cc2633...137c90cc612d 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-22514) Zip generated from "all files in zip" contains the wrong slashes
Daniel Beck commented on JENKINS-22514 Zip generated from "all files in zip" contains the wrong slashes Oleg, this is set to you, are you planning to work on 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/d/optout.
[JIRA] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Ryan Hummer commented on JENKINS-24055 Matrix Job Unable To Sync I will give that a go. 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] [crowd2] (JENKINS-23208) Backtrace when trying to use 'remember me' with latest crowd auth plugin
SCM/JIRA link daemon commented on JENKINS-23208 Backtrace when trying to use 'remember me' with latest crowd auth plugin Code changed in jenkins User: Kanstantsin Shautsou Path: src/main/java/de/theit/jenkins/crowd/CrowdAuthenticationToken.java src/main/java/de/theit/jenkins/crowd/CrowdRememberMeServices.java http://jenkins-ci.org/commit/crowd2-plugin/d86d674e2e25620472403b58f640ea5fdeb32a9d Log: [FIXED JENKINS-23208] Principal is UserDetails. 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] [crowd2] (JENKINS-23208) Backtrace when trying to use 'remember me' with latest crowd auth plugin
SCM/JIRA link daemon resolved JENKINS-23208 as Fixed Backtrace when trying to use 'remember me' with latest crowd auth plugin Change By: SCM/JIRA link daemon (01/Aug/14 3:44 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 -- 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] [crowd2] (JENKINS-23208) Backtrace when trying to use 'remember me' with latest crowd auth plugin
SCM/JIRA link daemon commented on JENKINS-23208 Backtrace when trying to use 'remember me' with latest crowd auth plugin Code changed in jenkins User: Kanstantsin Shautsou Path: src/main/java/de/theit/jenkins/crowd/CrowdAuthenticationToken.java src/main/java/de/theit/jenkins/crowd/CrowdMailAddressResolverImpl.java src/main/java/de/theit/jenkins/crowd/CrowdRememberMeServices.java http://jenkins-ci.org/commit/crowd2-plugin/08ff25af08f23752054b8d9d44a26538b2a6b340 Log: Merge pull request #8 from KostyaSha/JENKINS-23208 [FIXED JENKINS-23208] Principal is UserDetails. True setAuthenticated() in token. Compare: https://github.com/jenkinsci/crowd2-plugin/compare/472451687cd3...08ff25af08f2 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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen commented on JENKINS-24055 Matrix Job Unable To Sync Before you try rolling back the plugin; have you tried a clean Jenkins Job. I'm thinking that the previous builds might not have full TagAction info and could cause a Null Pointer. 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-23929) Cannot use 'WORKSPACE' variable when creating custom workspace to *modify* the auto-generated workspace
Phil Rutherford
commented on JENKINS-23929
Cannot use 'WORKSPACE' variable when creating custom workspace to *modify* the auto-generated workspace
Hi Daniel,
I'm afraid that doesn't work. The way the Jenkins core code works any custom workspace is treated as an absolute path so in the case of concurrent builds they would all end up overwriting each other. If you use EXECUTOR_NUMBER in the custom workspace then you run into the problem in my original description above.
I've fixed this myself and created a pull request: https://github.com/jenkinsci/jenkins/pull/1347
My fix means that you can now specify "${WORKSPACE}_${Branch}" as in my original description above. If there are any concurrent builds then they will be named "${WORKSPACE}_${Branch}@N" where '@' is the separator and N is the concurrent build index - not this is not the same as using the EXECUTOR_NUMBER, i.e. the second concurrent build (i.e. N=2) could be running on executor number 4 (if you have 4 or more executors). If the number of concurrent builds is restricted to say 2 then only 2 workspaces will be created, whereas if using EXECUTOR_NUMBER then up to the number of executors worth of workspaces could be created. As I said in the description our workspaces are very large and SSD space is limited so we need to restrict the number of these, particularly as we have multiple branches as well.
If this goes into the master build I'll resolve 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/d/optout.
[JIRA] [core] (JENKINS-24050) All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting
James Noonan commented on JENKINS-24050 All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting We updated to take in fix 22932 today. If the issue reoccurs for us, I'll raise a new defect. 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-24050) All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting
Jesse Glick commented on JENKINS-24050 All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting Assuming the purported fix in JENKINS-22932 did in fact correct at least some variants of the bug, it should be left closed; if this issue represents some other variants, then fine—a follow-up fix can close this one, and it can be backported separately if marked lts-candidate. 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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen commented on JENKINS-24055 Matrix Job Unable To Sync I setup a slave on Ubuntu and was not able to reproduce this issue. The string "3605760456" might refer to a serialisation issue, but I can't find anything odd in the code. Thanks for checking the logs; please can you check the Perforce Credential for the Server connection. Did you use an IP or FQDN? Can the slave resolve the Perforce Server? 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-22472) CommandDuringBuild not automatically authenticated
Jesse Glick commented on JENKINS-22472 CommandDuringBuild not automatically authenticated Another option would be to define a BuildWrapper which sets an environment variable during the build to a random UUID which CommandDuringBuild, and perhaps any CLICommand, would check for; if set, the transport authentication would be set automatically to that of the build, and a flag set so that commands could decide to skip permission checks for the running build. Such a build wrapper could also ensure that jenkins-cli.jar is available on the slave machine in $JENKINS_CLI_JAR, so that you would not be required to download it manually, which would make running CLI commands from inside a build a lot more convenient. Of course this could be done automatically on any slave without requiring a custom build wrapper, but that would affect performance of everybody. (Defining a Builder is also an option, though this gives less flexibility for people who want to embed CLI commands in the middle of shell scripts and the like.) 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-24080) set-build-result and set-build-parameter do insufficient checks
Jesse Glick assigned JENKINS-24080 to Jesse Glick set-build-result and set-build-parameter do insufficient checks Change By: Jesse Glick (01/Aug/14 3:03 PM) Assignee: Jesse Glick 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-24080) set-build-result and set-build-parameter do insufficient checks
Jesse Glick created JENKINS-24080 set-build-result and set-build-parameter do insufficient checks Issue Type: Bug Assignee: Unassigned Components: core Created: 01/Aug/14 2:40 PM Description: Formally filing some issues which were previously noted parenthetically in JENKINS-22472: SetBuildResultCommand checks Item.BUILD; I would have expected Run.UPDATE. And SetBuildParameterCommand does no check at all. getCurrentlyBuilding does not even check Run.isBuilding, so this could even be used to mangle a completed build's state, such as parameters via SetBuildParameterCommand. (SetBuildResultCommand would not work on a finished build because of checks inside Run.setResult.) Project: Jenkins Labels: security cli lts-candidate Priority: Major Reporter: Jesse Glick 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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Ryan Hummer commented on JENKINS-24055 Matrix Job Unable To Sync We use a DN, not fully qualified. I was able to issue the same sync command on that machine and it worked just fine. It uses the same string as the P4Port as how we have our credentials for that server configured. I'll try rolling back the plugin on the machine too to see if I'm insane or not thinking it was working. 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-22472) CommandDuringBuild not automatically authenticated
Jesse Glick commented on JENKINS-22472 CommandDuringBuild not automatically authenticated Oddly, SetBuildDisplayNameCommand is not a CommandDuringBuild. You would expect this to be a natural thing to do from inside a build. 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] [jacoco] (JENKINS-24081) [Jacoco] license missing from project
Aaron Searle created JENKINS-24081 [Jacoco] license missing from project Issue Type: Improvement Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 01/Aug/14 2:56 PM Description: It appears that there is no license associated with the project plugin/project http://github.com/jenkinsci/jacoco-plugin. Could an appropriate one be added? Project: Jenkins Priority: Major Reporter: Aaron Searle 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-22472) CommandDuringBuild not automatically authenticated
Jesse Glick
updated JENKINS-22472
CommandDuringBuild not automatically authenticated
Change By:
Jesse Glick
(01/Aug/14 2:49 PM)
Description:
Some {{CommandDuringBuild}} implementations, such as {{SetBuildResultCommand}}, check permissions.
(Oddly, {{Item.BUILD}} in this case; I would have expected {{Run.UPDATE}}. And {{SetBuildParameterCommand}} does no check at all.)
This is necessary to prevent a random user (with at least {{Item.READ}} permission) from running one of these commands on someone else's build from an external command shell. (
{{getCurrentlyBuilding}} does not even check {{Run
Cf
.
isBuilding}}, so this could even be used to mangle a _completed_ build's state, such as parameters via {{SetBuildParameterCommand}}
JENKINS-24080
.
{{SetBuildResultCommand}} would not work on a finished build because of checks inside {{Run.setResult}}.
)Yet Jenkins provides no assistance in authenticating such commands. So if you are running in a properly secured instance and want to run {{set-build-result}}, your job would have to provide an SSH private key or password for a user with permissions on the job. Managing such credentials safely could be tricky.It would be better if this were automatic, when the CLI command is indeed run from inside the build (say in a shell step). Perhaps {{$JENKINS_SERVER_COOKIE}} could be inspected on the CLI side and compared to {{Run.getCharacteristicEnvVars}}? Assuming there is a match, you could either* Set the transport authentication for the command to the authentication in effect in {{Run.getExecutor}}, if not just {{SYSTEM}}. ({{Executor}} would need to have a method reporting its current authentication. Running {{workUnit.context.item.authenticate()}} again and assuming that the result is the same is unsafe since a job configuration might have changed since it started running.)* Return null from {{getCurrentlyBuilding}} in case there is _not_ a match, and removing permission checks from command implementations. This is arguably better because it will make the job work correctly even if the authentication in effect during the build is for a user (for example {{anonymous}}) who would not otherwise generally have those permissions on the job; or when there is no authentication in effect during the build at all.
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-24080) set-build-result and set-build-parameter do insufficient checks
Jesse Glick started work on JENKINS-24080 set-build-result and set-build-parameter do insufficient checks Change By: Jesse Glick (01/Aug/14 2:50 PM) Status: Open In Progress 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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Ryan Hummer commented on JENKINS-24055 Matrix Job Unable To Sync I haven't been able to find anything in the log files. 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] [job-dsl-plugin] (JENKINS-23289) ClassCastException in JobDSL whith removed Folder
Romain Chalumeau closed JENKINS-23289 as Fixed ClassCastException in JobDSL whith removed Folder Tested and validated on version 1.24 Thx Change By: Romain Chalumeau (01/Aug/14 2:45 PM) Status: Resolved Closed Assignee: Daniel Spilker Romain Chalumeau 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] [ui-changes] (JENKINS-24079) Getting a Crash in IE10 when configuring Jenkins
George Li created JENKINS-24079 Getting a Crash in IE10 when configuring Jenkins Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkins_ie_crash.flv Components: ui-changes Created: 01/Aug/14 2:36 PM Description: While testing Jenkins 1.574 in a sandbox, I ran into an issue in IE 10 where configuration pages seem to be causing an unrecoverable crash. So far I've discovered this on both /configure and /job/JOBNAME/configure. There are no issues in Opera, Chrome, and Firefox. Please see attached video. Environment: Windows 7 x64, IE 10.0.9200.17028 Project: Jenkins Labels: user-experience Priority: Major Reporter: George Li 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] [maven] (JENKINS-24075) Build modules in parallel mode is not working at all. No error shown in logs.
Daniel Beck commented on JENKINS-24075 Build modules in parallel mode is not working at all. No error shown in logs. If this is supposed to be a request for assistance, Jira is the wrong choice. Ask on jenkinsci-users or the #jenkins IRC channel. 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] [active-directory] (JENKINS-22727) AD plugin times out for large user/group membership
Mark Syms commented on JENKINS-22727 AD plugin times out for large user/group membership Catching the LimitExceededException in chainGroupLookup and returning false seems to work but is a bit brute force. Something that did some deferred lookups on demand would probably be a better solution but I'm not sure how that would map into the architecture. 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] [email-ext] (JENKINS-16181) Jenkins does not try to resend a failed e-mail
Alex Earl commented on JENKINS-16181 Jenkins does not try to resend a failed e-mail There is no option to specify the number of retries. 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-21309) Git plugins changes URL for Bitbucket is incorrect
Mark Waite commented on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect The URL in the job definition does not match the URL that I see in the source code. That means I don't understand the source code well enough to map the string you're seeing as default to the string in the source code. It will require a debugger and some time investigating actual behavior, rather than just reading the source 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/d/optout.
[JIRA] [clearcase] (JENKINS-24078) Jira Link are not created for ClearCase UCM project
Xavier Xemaire created JENKINS-24078 Jira Link are not created for ClearCase UCM project Issue Type: Bug Assignee: Vincent Latombe Attachments: change-with-link-to-jira-in-git-project .jpg, change-without-jira-link-in-CC-project.jpg Components: clearcase, jira Created: 01/Aug/14 1:02 PM Description: Problem: The jira Plugin works correctly for job using git as SCM. The commit message is scanned and a link to the corresponding Jira issue is created with the method JiraChangeLogAnnotator. (see attachment change-with-link-to-jira-in-git-project.jpg) But we have also Jobs, that use ClearCase UCM as SCM. The activity is not scanned. So that there is no link to Jira. (see attachment change-without-jira-link-in-CC-project.jpg) Environment: Jenkins 1.554.2, Jira Plugin 1.39, ClearCase Plugin 1.5 Project: Jenkins Priority: Minor Reporter: Xavier Xemaire 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.
