[JIRA] [svn-revert-plugin] (JENKINS-15082) svn-revert-plugin: revert for failed builds, too
Title: Message Title Christian Bremer assigned an issue to Unassigned Jenkins / JENKINS-15082 svn-revert-plugin: revert for failed builds, too Change By: Christian Bremer Assignee: Christian Bremer Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-28597) GIT Parameter Plugin not using stored credentials
Title: Message Title adrian vindel commented on JENKINS-28597 Re: GIT Parameter Plugin not using stored credentials Hi Bruno I think that you are not using configured user credentials, right?I mean you just configure ssh keys (user running CI server, tomcat user--> git server) between servers. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-29773) stable sort order of AuthorizationMatrixProperty.java
Title: Message Title Bernhard Merkle created an issue Jenkins / JENKINS-29773 stable sort order of AuthorizationMatrixProperty.java Issue Type: Bug Assignee: Mirko Friedenhagen Components: jobconfighistory-plugin Created: 04/Aug/15 7:50 AM Priority: Major Reporter: Bernhard Merkle the jobconfighistory-plugin often reports diffs regarding the permission table but actually I have not changed anything in the permission table. If I compare the output I can see that all entries are there, but the order changed. So I actually get a diff where there is no one. I think there are two reasons for this: 1. class AuthorizationMatrixProperty has two members which are of type HashHap and HashSet. They have no stable sort order, so when saving the order varies, which results in the diffs. Proposal: can we use the sorted variants of these two types (SortedMap, SortedSet) ? private final Map> grantedPermissions = new HashMap>(); private Set sids = new HashSet(); 2. reason number two is that the configuration is saved at all, means I did not make a change, but a change it triggered. So I would propose to avoid saving changes when where are none, even if the user clicks on "Apply" or "Save" and in essence there are no changes. (e.g. deleted and added user again) Maybe this has to do with the stable sort order and is just a consequence of that. I do not know how a change is internally detected.
[JIRA] [teamconcert-plugin] (JENKINS-29763) Load Workflow Groovy Script from SCM (RTC) is failing with team-concert
Title: Message Title Krishna Kishore commented on JENKINS-29763 Re: Load Workflow Groovy Script from SCM (RTC) is failing with team-concert Issued tracked at link 364666 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-29763) Load Workflow Groovy Script from SCM (RTC) is failing with team-concert
Title: Message Title Krishna Kishore edited a comment on JENKINS-29763 Re: Load Workflow Groovy Script from SCM (RTC) is failing with team-concert Issued tracked at [ link RTC work item 364666|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/364666] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [_test] (JENKINS-29768) Fail to install stable version of jenkins on Linux
Title: Message Title Daniel Beck commented on JENKINS-29768 Re: Fail to install stable version of jenkins on Linux 1.623 is the current weekly release. Did you previously install that yum repo and it confused yum, maybe caching which version is the current one? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-29768) Fail to install stable version of jenkins on Linux
Title: Message Title Daniel Beck assigned an issue to Unassigned Jenkins / JENKINS-29768 Fail to install stable version of jenkins on Linux Change By: Daniel Beck Component/s: packaging Component/s: _test Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-node-stalker-plugin] (JENKINS-29774) [NODE STALKER] The job $jobname has no traceable runs!
Title: Message Title Steffen Breitbach created an issue Jenkins / JENKINS-29774 [NODE STALKER] The job $jobname has no traceable runs! Issue Type: Bug Assignee: Unassigned Components: job-node-stalker-plugin Created: 04/Aug/15 9:17 AM Environment: Jenkins 1.609.1 LTS Node Stalker Plugin 1.0.3 Priority: Minor Reporter: Steffen Breitbach Node Stalker does not seem to be able to determine the last slave a job ran on: [NODE STALKER] The job $jobname has no traceable runs! There is no evidence of the error in Jenkins' log file. Add Comment
[JIRA] [docker-build-step-plugin] (JENKINS-29775) client is too old, minimum supported API version is 1.12
Title: Message Title Milan Simonovic created an issue Jenkins / JENKINS-29775 client is too old, minimum supported API version is 1.12 Issue Type: Bug Assignee: vjuranek Components: docker-build-step-plugin Created: 04/Aug/15 9:49 AM Environment: Jenkins: 1.609.2 docker-build-step: 1.28 docker-commons: 1.2 docker remote server: 1.7.1 OS: Ubuntu 14.04 JDK: 1.8.0-45 Labels: plugin exception Priority: Blocker Reporter: Milan Simonovic Trying to build an image, I'm getting this exception: com.github.dockerjava.api.BadRequestException: client is too old, minimum supported API version is 1.12, please upgrade your client to a newer version Docker v1.7 is not supported?
[JIRA] [core] (JENKINS-29769) $WORKSPACE is not solved in slave nodes
Title: Message Title Daniel Beck resolved as Not A Defect WORKSPACE is not defined before a workspace is selected. You try to access it from the custom workspace option, which clearly needs to happen before workspace selection. Jenkins / JENKINS-29769 $WORKSPACE is not solved in slave nodes Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-29763) Load Workflow Groovy Script from SCM (RTC) is failing with team-concert
Title: Message Title Krishna Kishore commented on JENKINS-29763 Re: Load Workflow Groovy Script from SCM (RTC) is failing with team-concert I am not able to reproduce the issue, the RTC Scm checkout operation is completed and if the specified groovy files is not present Jenkins throws a file not found error but only after the scm checkout as shown below: Started by user anonymous RTC : checkout... RTC Checkout : Source control setup RTC Checkout : Accepting changes into workspace "SimpleStream Workflow Build" ... RTC Checkout : Fetching files to fetch destination "E:\JenkinsBuilds\workspace@script" ... RTC Checkout : Fetching Completed ERROR: failed to start build java.io.FileNotFoundException: E:\JenkinsBuilds\workspace@script\Simple\myflow1.groovy (The system cannot find the file specified) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(Unknown Source) at hudson.FilePath.read(FilePath.java:1750) at hudson.FilePath.readToString(FilePath.java:1851) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:114) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:58) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:183) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) If the file is present then the build completes with out errors. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap-plugin] (JENKINS-29770) Global security using ldap does not work
Title: Message Title Daniel Beck resolved as Not A Defect There is more to LDAP configuration that just the server. So far you haven't shown that there is a bug in Jenkins. I suggest you start with 'anyone can do anything' as auth realm, this way you can experiment with options until it works. Jenkins / JENKINS-29770 Global security using ldap does not work Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4580) "Latest Test Result" link is missing from project when build is executing
Title: Message Title Daniel Beck commented on JENKINS-4580 Re: "Latest Test Result" link is missing from project when build is executing Andi B Let me guess, the jobs that don't show test results never had a successful build with test results, while those that do, had? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-29763) Load Workflow Groovy Script from SCM (RTC) is failing with team-concert
Title: Message Title Krishna Kishore commented on JENKINS-29763 Re: Load Workflow Groovy Script from SCM (RTC) is failing with team-concert The problem reported here could be due to permissions issue, the error "FATAL: RTC : checkout failure: Failed to create /mnt/workspace/XXX-Docker-Workflow@script/.jazz5". Check the permissions for the path "/mnt/workspace/XXX-Docker-Workflow@script" and make sure that the path is reachable and write permission is present. Another issues could be with nested sandboxes, RTC Scm does not allow nesting of .jazz5 folders so make sure their is no .jazz5 folder in the "/mnt/workspace/XXX-Docker-Workflow@script" hierarchy Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap-plugin] (JENKINS-29772) Can't retrieve ldap info using domain search with spaces
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-29772 Can't retrieve ldap info using domain search with spaces Looks like this has a trivial workaround, so reducing priority. Change By: Daniel Beck Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled
Title: Message Title Krishna Kishore assigned an issue to Anil Bhatia Jenkins / JENKINS-29130 RTC Polling broken when Proxy enabled Change By: Krishna Kishore Assignee: Anil Bhatia Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4580) "Latest Test Result" link is missing from project when build is executing
Title: Message Title Andi B commented on JENKINS-4580 Re: "Latest Test Result" link is missing from project when build is executing Daniel Beck Yes, all builds failed because of failing tests. The "test result" link is correctly shown in a specific build. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4580) "Latest Test Result" link is missing from project when build is executing
Title: Message Title Andi B edited a comment on JENKINS-4580 Re: "Latest Test Result" link is missing from project when build is executing @ [~danielbeck] Yes, all builds failed because of failing tests. The "test result" link is correctly shown in a specific build. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-29743) admin-list and white-list not working
Title: Message Title Kanstantsin Shautsou assigned an issue to Honza Brázdil Jenkins / JENKINS-29743 admin-list and white-list not working Change By: Kanstantsin Shautsou Assignee: Kanstantsin Shautsou Honza Brázdil Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-29743) admin-list and white-list not working
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-29743 admin-list and white-list not working Change By: Kanstantsin Shautsou Component/s: ghprb-plugin Component/s: github-pullrequest-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20445) Git plugin timeout is too small
Title: Message Title Tim Knight commented on JENKINS-20445 Re: Git plugin timeout is too small If you add additional behaviours before the operation you can up the timeout for clone and checkout - which has translated to a higher timeout value in my console + Advanced Checkout behaviours + Advanced Clone behaviours Putting any value in timeout overrides the default. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19145) Builds fail because of "slave went offline during the build"
Title: Message Title Piotr Nadczuk commented on JENKINS-19145 Re: Builds fail because of "slave went offline during the build" Jenkins 1.622 12:04:02 Slave went offline during the build 12:04:02 ERROR: Connection was broken: java.io.IOException: Unexpected termination of the channel 12:04:02 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) 12:04:02 Caused by: java.io.EOFException 12:04:02 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325) 12:04:02 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) 12:04:02 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) 12:04:02 at java.io.ObjectInputStream.(ObjectInputStream.java:299) 12:04:02 at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:40) 12:04:02 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) 12:04:02 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-29776) Job DSL support for Promoted Builds Plugin
Title: Message Title Dennis Schulte created an issue Jenkins / JENKINS-29776 Job DSL support for Promoted Builds Plugin Issue Type: New Feature Assignee: Unassigned Components: promoted-builds-plugin Created: 04/Aug/15 11:09 AM Priority: Minor Reporter: Dennis Schulte There is actually a discussion on Google Groups if it makes sense to add support for the Job DSL plugin directly into the Promoted Builds Plugin: https://groups.google.com/d/msgid/jenkinsci-dev/e6946a1a-a207-4bc4-8fc2-b42021b996f3%40googlegroups.com?utm_medium=email&utm_source=footer I created already a Job DSL Extension in a separate Repository (https://github.com/codecentric/job-dsl-promotions-plugin). The question is now if I should invest the time to create a PR for the Promoted Builds Plugin. The main point is here, that the extension is mainly written in Groovy. Is it ok for you to see Groovy in your code base? Regards Dennis Add Comment
[JIRA] [git-plugin] (JENKINS-25289) git notify commit bug when use credentials
Title: Message Title Mark Waite resolved as Cannot Reproduce Pablo Alcaraz unfortunately, your stack does not duplicate the issue. The original issue reported a stack trace which did not transfer any significant data from the git server to the slave agents. Your new stack trace reports the message: ERROR: Timeout after 10 minutes ERROR: Error cloning remote repo 'origin' The transfer rate from your repository appears to be about 10 MB/s. A 6 GB repository (without a reference copy on the slave) will need 614 seconds to copy at 10 MB/s. That is slightly over 10 minutes. The default timeout for the git plugin clone is 10 minutes. If you need to clone a 6 GB repository to multiple machines in parallel without having a reference copy on the slave, you'll need to add the "Advanced clone options" and possibly "Advanced checkout option" to set the timeout to something greater than the default. If you're often cloning that large repository, you should probably use a separate technique to maintain a copy of a bare repository on each of the slaves and then include the path to that bare repository in the Jenkins job definition. Alternately, if the 6 GB repository is much smaller than 6 GB at checkout, you can reduce the amount of data transferred by adding the advanced option for "shallow checkout". Jenkins / JENKINS-25289 git notify commit bug when use credentials Change By: Mark Waite Status: Reopened Resolved Resolution: Cannot Reproduce Add Comment
[JIRA] [git-plugin] (JENKINS-29755) not able to install git plugin on Ubuntu with error 'java.io.IOException: Failed to dynamically deploy this plugin
Title: Message Title Mark Waite commented on JENKINS-29755 Re: not able to install git plugin on Ubuntu with error 'java.io.IOException: Failed to dynamically deploy this plugin The permission denied exception probably indicates that the file system permissions at that location in the file system tree on your Ubuntu slave (or on the master) do not allow the user running the slave to write to that location. I don't think this is a Jenkins bug or a git plugin bug. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkinslint-plugin] (JENKINS-29777) Unable to configure Dimensions in Jenkins
Title: Message Title Sambath Kumar created an issue Jenkins / JENKINS-29777 Unable to configure Dimensions in Jenkins Issue Type: Bug Assignee: Victor Martinez Components: jenkinslint-plugin Created: 04/Aug/15 12:42 PM Environment: OS: Windows 7- 64 bit, Jenkins version: 1.617, Dimension plugin version: permalink to the latest Labels: jenkins Priority: Critical Reporter: Sambath Kumar Throwing Java exception Add Comment
[JIRA] [jenkinslint-plugin] (JENKINS-29777) Unable to configure Dimensions in Jenkins
Title: Message Title Sambath Kumar updated an issue Jenkins / JENKINS-29777 Unable to configure Dimensions in Jenkins Change By: Sambath Kumar Throwing Java exception :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 tracejavax.servlet.ServletException: java.lang.NoClassDefFoundError: com/serena/dmclient/api/DimensionsRuntimeException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedSe
[JIRA] [git-plugin] (JENKINS-24809) Github-Jenkins Trigger issue with slave
Title: Message Title Kenneth Baltrinic commented on JENKINS-24809 Re: Github-Jenkins Trigger issue with slave Mark Waite I would like to re-open this issue. We are encountering the exact same behavior, though our setup is a bit different. We are not using git hooks in our case, simple SCM Polling. As with the originally reported situation, this is happening with a Linux master an multiple (8) windows slaves. All slaves are presenting with the same issue. Setting "Force polling workspace" also works as a workaround in our case. We are seeing this with Jenkins 1.609.1, Git 2.4, Git client 1.16.1 Below is our stack trace, though it does not seem to differ materially from the one in the original report: Started on Aug 4, 2015 12:37:01 PM Polling SCM changes on hq-jenwin-007 Using strategy: Default [poll] Last Built Revision: Revision c61ffa28bf6375f1907d49cc7c5ad282c32c5f1c (refs/remotes/origin/prod) using GIT_SSH to set credentials Credential ID: ** > C:\Program Files (x86)\Git\cmd\git.exe --version # timeout=10 > C:\Program Files (x86)\Git\cmd\git.exe ls-remote -h ssh://git@stash:7999/**/**.git # timeout=10 FATAL: hudson.plugins.git.GitException: Error performing command: C:\Program Files (x86)\Git\cmd\git.exe ls-remote -h ssh://git@stash:7999/**/**.git hudson.util.IOException2: hudson.plugins.git.GitException: Error performing command: C:\Program Files (x86)\Git\cmd\git.exe ls-remote -h ssh://git@stash:7999/**/**.git at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:529) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380) at hudson.scm.SCM.poll(SCM.java:397) at org.jenkinsci.plugins.multiplescms.MultiSCM.compareRemoteRevisionWith(MultiSCM.java:100) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1467) at hudson.model.AbstractProject._poll(AbstractProject.java:1438) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:510) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:539) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: hudson.plugins.git.GitException: Error performing command: C:\Program Files (x86)\Git\cmd\git.exe ls-remote -h ssh://git@stash:7999/**/**.git at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1598) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1277) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1268) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:2327) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:583) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:527) ... 15 more Caused by: java.io.IOException: Cannot run program "C:\Program Files (x86)\Git\cmd\git.exe": error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher
[JIRA] [core] (JENKINS-12875) "No valid crumb was included in the request" errors all around
Title: Message Title Paolo Giarrusso commented on JENKINS-12875 Re: "No valid crumb was included in the request" errors all around I ran into this yesterday. What's the status? Somebody proposed an X-Jenkins-Crumb header (in JENKINS-7518 ), which doesn't seem a legal _javascript_ identifier (though it might be "the start of a legal _javascript_ statement"). Would X-Jenkins-Crumb-0NoJS help, since `0NoJs` is an illegal token? Also, SECURITY-47 isn't visible in the bug tracker, apparently on purpose — I've only found the fix (https://github.com/jenkinsci/jenkins/commit/0de3e9b14ed75f70279435e78eb9f6a3a1a179df) and maybe the advisory (https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-02-16). For my part, I tried to document this on https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+behind+an+NGinX+reverse+proxy; I only mentioned the most secure workaround, not the -Dhudson.security.csrf.requestfield= setting. Improvements are welcome. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12875) "No valid crumb was included in the request" errors all around
Title: Message Title
Paolo Giarrusso edited a comment on JENKINS-12875
Re: "No valid crumb was included in the request" errors all around
I ran into this yesterday. What's the status? Somebody proposed an {{ X-Jenkins-Crumb }} header (in JENKINS-7518), which doesn't seem a legal _javascript_ identifier (though it might be "the start of a legal _javascript_ statement").Would {{ X-Jenkins-Crumb-0NoJS }} help, since ` {{ 0NoJs ` }} is an illegal JS token?Also, SECURITY-47 isn't visible in the bug tracker, apparently on purpose — I've only found the fix (https://github.com/jenkinsci/jenkins/commit/0de3e9b14ed75f70279435e78eb9f6a3a1a179df) and maybe the advisory (https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-02-16).For my part, I tried to document this on https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+behind+an+NGinX+reverse+proxy; I only mentioned the most secure workaround, not the {{-Dhudson.security.csrf.requestfield=}} setting. Improvements are welcome.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-24809) Github-Jenkins Trigger issue with slave
Title: Message Title Kenneth Baltrinic commented on JENKINS-24809 Re: Github-Jenkins Trigger issue with slave I should have added that we recently upgraded from an old version of jenkins where we were not seeing this behavior: Our old system was Jenkins 1.552, Git plugin 1.4 and Git Client plugin 1.6. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23654) UpdateCenter stuck at preparation phase when jenkins server is behind GFW
Title: Message Title NetAppBlueDevil commented on JENKINS-23654 Re: UpdateCenter stuck at preparation phase when jenkins server is behind GFW If the need in the end is that it is possible to reach the update site, then why bother checking www.google.com, why not check that you can reach the update site? It is possible to rsync the update site and update the update site URL in Jenkins, so it appears to be a valid use case to have an internal update site anyway. In that case this internet issue is artificial and should be able to be avoided if desired as a configuration option within the update management IMO. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29778) Jenkins behavior with rsync update site
Title: Message Title NetAppBlueDevil created an issue Jenkins / JENKINS-29778 Jenkins behavior with rsync update site Issue Type: Improvement Assignee: Unassigned Components: core Created: 04/Aug/15 1:43 PM Priority: Major Reporter: NetAppBlueDevil I have an isolated environment, but am able to rsync data into my environment. So, I have rsynced updates from http://updates.jenkins-ci.org/ as described on the index page taht appears on the URL and have configures the Update Site value on the Plugin manager->Advanced tab to point to the update-center.json file in that rsync copy. The problem is that all the URLs in the JSON file are for the real internet, not the host sering my rsync copy. It would be a clearer workflow if Jenkins would support replacing the bae portion of the URL in the .json file with the one configured in the update site so that I don't have to add special logic in my rsync process to create a custom copy of the update-center.json file with the URLs translated. Add Comment
[JIRA] [buildgraph-view-plugin] (JENKINS-29779) Build dependency graph
Title: Message Title Radek Chromy created an issue Jenkins / JENKINS-29779 Build dependency graph Issue Type: Bug Assignee: Unassigned Components: buildgraph-view-plugin Created: 04/Aug/15 1:47 PM Environment: buildgraph-1.1.1 jenkins 1.509.4 Labels: plugin gui Priority: Minor Reporter: Radek Chromy When triggered build has removed history build, Build Graph plugin shows empty page. job1 #10 -> job2 #20 when job1 #20 is removed, build graph on job1 #10 is empty In _javascript_ console is error: prototype.js:5798 Uncaught TypeError: element.dispatchEvent is not a function breadcrumbs.js:159 Uncaught TypeError: e.hasClassName is not a function
[JIRA] [artifactory-plugin] (JENKINS-29746) Revision checkout trough jenkis is failed
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-29746 Revision checkout trough jenkis is failed Seems to be an issue in the Artifactory plugin Change By: Oleg Nenashev Component/s: artifactory-plugin Component/s: _test Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-29746) Revision checkout trough jenkis is failed
Title: Message Title Oleg Nenashev commented on JENKINS-29746 Re: Revision checkout trough jenkis is failed Reassigned ti the plugin owners Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-29746) Revision checkout trough jenkis is failed
Title: Message Title Oleg Nenashev assigned an issue to yossis Jenkins / JENKINS-29746 Revision checkout trough jenkis is failed Change By: Oleg Nenashev Assignee: Oleg Nenashev yossis Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-29746) Revision checkout trough jenkis is failed. IllegalStateException in Artifactory's buildEnvVars
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-29746 Revision checkout trough jenkis is failed. IllegalStateException in Artifactory's buildEnvVars Change By: Oleg Nenashev Summary: Revision checkout trough jenkis is failed . IllegalStateException in Artifactory's buildEnvVars Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled
Title: Message Title Matthew Cipollone updated an issue Jenkins / JENKINS-29130 RTC Polling broken when Proxy enabled Change By: Matthew Cipollone Hi,We have an issue with RTC polling when we have the proxy set in Jenkins. We need to set http and https proxy settings on the master for many other apps. So we do this in the Jenkins.xml file on the master. But this seems to break polling on RTC jobs. Jobs can still pull files out of source control but polling does not work. What is the difference between these 2 operations? Gives the below stack trace in the polling log:The following settings are set in the jenkins.xml:-Dhttp.proxyHost=proxy001 -Dhttps.proxyHost=proxy001 -Dhttp.proxyPort=80 -Dhttps.proxyPort=80 -Dhttp.nonProxyHosts=*. ourcompanycomain ourcompanydomain .comOur thoughts are that the IBM RTC Jenkins plug-in may not be respecting the nonProxyHost java settings. Since our RTC instance is internal to the network, it should not feed the traffic destined for RTC through the proxy.Any ideas, this one is killing us ! :) Any help would be greatly appreciated!!FATAL: RTC : checking for changes failure: CRJAZ0099E An HTTP error occurred when this URL was being accessed: https://rtcserver.company.com:9443/ccm2/versionCompatibility?clientVersion=5.0. Error details: Remote host closed connection during handshake.com.ibm.team.repository.common.transport.TeamServiceException: CRJAZ0099E An HTTP error occurred when this URL was being accessed: https://rtcserver.company.com:9443/ccm2/versionCompatibility? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [artifactory-plugin] (JENKINS-29746) Revision checkout trough jenkis is failed. IllegalStateException in Artifactory's buildEnvVars
Title: Message Title Marcin Cimaszewski commented on JENKINS-29746 Re: Revision checkout trough jenkis is failed. IllegalStateException in Artifactory's buildEnvVars I have installed 2.3.1 version of this plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled
Title: Message Title Matthew Cipollone updated an issue Jenkins / JENKINS-29130 RTC Polling broken when Proxy enabled Change By: Matthew Cipollone Hi,We have an issue with RTC polling when we have the proxy set in Jenkins. We need to set http and https proxy settings on the master for many other apps. So we do this in the Jenkins.xml file on the master. But this seems to break polling on RTC jobs. Jobs can still pull files out of source control but polling does not work. What is the difference between these 2 operations? Gives the below stack trace in the polling log: The following settings are set in the jenkins.xml:-Dhttp.proxyHost=proxy001 -Dhttps.proxyHost=proxy001 -Dhttp.proxyPort=80 -Dhttps.proxyPort=80 -Dhttp.nonProxyHosts=*.ourcompanycomain.comOur thoughts are that the IBM RTC Jenkins plug-in may not be respecting the nonProxyHost java settings. Since our RTC instance is internal to the network, it should not feed the traffic destined for RTC through the proxy. Any ideas, this one is killing us ! :) Any help would be greatly appreciated!!FATAL: RTC : checking for changes failure: CRJAZ0099E An HTTP error occurred when this URL was being accessed: https://rtcserver.company.com:9443/ccm2/versionCompatibility?clientVersion=5.0. Error details: Remote host closed connection during handshake.com.ibm.team.repository.common.transport.TeamServiceException: CRJAZ0099E An HTTP error occurred when this URL was being accessed: https://rtcserver.company.com:9443/ccm2/versionCompatibility? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-29621) EnvInject Plugin is only working to a limited extent in combination with the docker build environment
Title: Message Title Stefan Kahlhöfer commented on JENKINS-29621 Re: EnvInject Plugin is only working to a limited extent in combination with the docker build environment We are facing the same problem. As I can see the environment present and used during container start is the host environment present during Jenkins node start (may be days or weeks ago) including environment variables configured for this node (before node startup). There is no way to add additional environment variables (e.g. using EnvInject) as it seems to be only working for build steps and the Docker container start isn't such a dedicated step but "fancy work in the background". Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-29621) EnvInject Plugin is only working to a limited extent in combination with the docker build environment
Title: Message Title Stefan Kahlhöfer commented on JENKINS-29621 Re: EnvInject Plugin is only working to a limited extent in combination with the docker build environment Nicolas De Loof: In JENKINS-29677 you mentioned priority of concurrent Build Wrappers. If you find a solution, this may be the trick for this issue as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-file-provider-plugin] (JENKINS-26339) Workflow integration for Config File Provider
Title: Message Title Dominik Bartholdi resolved as Fixed released with 2.9.2 Jenkins / JENKINS-26339 Workflow integration for Config File Provider Change By: Dominik Bartholdi Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-25977) Make publishers of analysis-core a SimpleBuildStep
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-25977 Make publishers of analysis-core a SimpleBuildStep Change By: Jesse Glick Assignee: Antonio Muñiz Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-25977) Make publishers of analysis-core a SimpleBuildStep
Title: Message Title Jesse Glick assigned an issue to Antonio Muñiz Jenkins / JENKINS-25977 Make publishers of analysis-core a SimpleBuildStep Change By: Jesse Glick Assignee: Jesse Glick Antonio Muñiz Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-29780 unarchive should support "Flatten directories" Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 04/Aug/15 2:31 PM Priority: Minor Reporter: Dominik Bartholdi The 'unarchive' command should support the option "Flatten directories" in the same way as the CopyArtifact Step does Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-s
[JIRA] [delivery-pipeline-plugin] (JENKINS-28463) Child level Downstream job doesn't display manual trigger button
Title: Message Title Patrik Boström commented on JENKINS-28463 Re: Child level Downstream job doesn't display manual trigger button Which version of Delivery Pipeline Plugin are you using? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership-plugin] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configurat
Title: Message Title Helmut Schaa commented on JENKINS-21390 Re: [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration I've just ran into the same issue where the inheritance plugin in conjunction with the project based matrix authorization plugin causes a stack overflow due to an infinite recursion. The fix mentioned by Alex in the previous commit does however not fix the problem. Here's part of the strack trace. I've cut it since it's repeating anyway. java.lang.StackOverflowError at hudson.model.ParameterDefinition.(ParameterDefinition.java:111) at hudson.model.SimpleParameterDefinition.(SimpleParameterDefinition.java:19) at hudson.model.ChoiceParameterDefinition.(ChoiceParameterDefinition.java:44) at hudson.model.ChoiceParameterDefinition.copyWithDefaultValue(ChoiceParameterDefinition.java:53) at hudson.plugins.project_inheritance.projects.parameters.InheritanceParametersDefinitionProperty.copyAndSortParametersByName(InheritanceParametersDefinitionProperty.java:212) at hudson.plugins.project_inheritance.projects.parameters.InheritanceParametersDefinitionProperty.(InheritanceParametersDefinitionProperty.java:181) at hudson.plugins.project_inheritance.projects.parameters.InheritanceParametersDefinitionProperty.createMerged(InheritanceParametersDefinitionProperty.java:245) at hudson.plugins.project_inheritance.projects.inheritance.ParameterSelector.merge(ParameterSelector.java:71) at hudson.plugins.project_inheritance.projects.inheritance.ParameterSelector.merge(ParameterSelector.java:29) at hudson.plugins.project_inheritance.projects.inheritance.InheritanceSelector.applyAgainstList(InheritanceSelector.java:264) at hudson.plugins.project_inheritance.projects.inheritance.InheritanceGovernor.reduceByMergeWithDuplicates(InheritanceGovernor.java:324) at hudson.plugins.project_inheritance.projects.inheritance.InheritanceGovernor.reduceByMerge(InheritanceGovernor.java:343) at hudson.plugins.project_inheritance.projects.InheritanceProject$9.reduceFromFullInheritance(InheritanceProject.java:3062) at hudson.plugins.project_inheritance.projects.InheritanceProject$9.reduceFromFullInheritance(InheritanceProject.java:3038) at hudson.plugins.project_inheritance.projects.inheritance.InheritanceGovernor.retrieveFullyDerivedField(InheritanceGovernor.java:204) at hudson.plugins.project_inheritance.projects.InheritanceProject.getAllProperties(InheritanceProject.java:3068) at hudson.plugins.project_inheritance.projects.InheritanceProject.getProperty(InheritanceProject.java:3202) at hudson.plugins.project_inheritance.projects.InheritanceProject.getProperty(InheritanceProject.java:3194) at hudson.security.ProjectMatrixAuthorizationStrategy.getACL(ProjectMatrixAuthorizationStrategy.java:54) at hudson.model.Job.getACL(Job.java:1482) at hudson.model.AbstractItem.hasPermission(AbstractItem.java:505) at jenkins.model.Jenkins.getItem(Jenkins.java:2344) at hudson.plugins.project_inheritance.projects.InheritanceProject.getProjectByName(InheritanceProject.java:521) at hudson.plugins.project_inheritance.projects.references.AbstractProjectReference.reloadProjectObject(AbstractProjectReference.java:90) at hudson.plugins.project_inheritance.projects.references.AbstractProjectReference.(AbstractProjectReference.java:71) at hudson.plugins.project_inheritance.projects.references.SimpleProjectReference.(SimplePro
[JIRA] [workflow-plugin] (JENKINS-28759) Batch steps on slaves randomly hang when complete
Title: Message Title A C commented on JENKINS-28759 Re: Batch steps on slaves randomly hang when complete I abandoned Workflow plugin awhile back due to this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap-plugin] (JENKINS-14520) LDAP Plugin should support StartTLS extension
Title: Message Title Lukasz Zalewski commented on JENKINS-14520 Re: LDAP Plugin should support StartTLS extension I know it has been a while but I'm also interested in this feature Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-24809) Github-Jenkins Trigger issue with slave
Title: Message Title Mark Waite commented on JENKINS-24809 Re: Github-Jenkins Trigger issue with slave I think the problem you're seeing is due to JENKINS-28943 and is resolved in git client plugin 1.18.0. I'm surprised you didn't update to git client plugin 1.18.0 at the same time you updated to git plugin 2.4.0. If that does not fix it, then you can also work-around the problem by changing the path to the git executable on those computers from C:\Program Files (x86)\Git\cmd\git.exe to C:\Program Files (x86)\Git\bin\git.exe Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap-plugin] (JENKINS-14520) LDAP Plugin should support StartTLS extension
Title: Message Title Lukasz Zalewski commented on JENKINS-14520 Re: LDAP Plugin should support StartTLS extension In the mean time, are there any workarounds available? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-28463) Child level Downstream job doesn't display manual trigger button
Title: Message Title Kalyan Koduru commented on JENKINS-28463 Re: Child level Downstream job doesn't display manual trigger button I think it's not an issue, and can be closed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-28463) Child level Downstream job doesn't display manual trigger button
Title: Message Title Kalyan Koduru closed an issue as Not A Defect Jenkins / JENKINS-28463 Child level Downstream job doesn't display manual trigger button Change By: Kalyan Koduru Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29781) BuildTrigger does not reflect moving aroung declaring job between folders
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-29781 BuildTrigger does not reflect moving aroung declaring job between folders Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Aug/15 2:59 PM Priority: Minor Reporter: Oliver Gondža Items.computeRelativeNamesAfterRenaming does its job well when it comes to moving referred items. However, then it is the referring item (context) moves around it fails to update the references correctly. Add Comment
[JIRA] [core] (JENKINS-29781) BuildTrigger does not reflect moving aroung declaring job between folders
Title: Message Title
Oliver Gondža updated an issue
Jenkins / JENKINS-29781
BuildTrigger does not reflect moving aroung declaring job between folders
Change By:
Oliver Gondža
{{Items.computeRelativeNamesAfterRenaming}} does its job well when it comes to moving referred items. However, then it is the referring item (context) moves around it fails to update the references correctly. Steps to reproduce:- Create upstream and downstream job inside folder using - Move
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29781) BuildTrigger does not reflect moving aroung declaring job between folders
Title: Message Title
Oliver Gondža updated an issue
Jenkins / JENKINS-29781
BuildTrigger does not reflect moving aroung declaring job between folders
Change By:
Oliver Gondža
{{Items.computeRelativeNamesAfterRenaming}} does its job well when it comes to moving referred items. However, then it is the referring item (context) moves around it fails to update the references correctly.Steps to reproduce:- Create upstream and downstream job inside folder using {{BuildTrigger}} using relative reference. - Move upstream job out of the folder.The reference is not updated
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-29046) NPE when using withDockerRegistry
Title: Message Title Tracy Kennedy commented on JENKINS-29046 Re: NPE when using withDockerRegistry Jesse Glick I meant that even though this step is not meant for end users per the docs, the snippet generator lists it as an option for registering a Docker registry under the "Advanced/Deprecated" section. I assume `withDockerRegistry` falls under the latter category, but that distinction might not be obvious enough for a newbie who is experimenting and hasn't read the docs yet. Perhaps the Advanced/Deprecated sections should be broken out into separate listings, with `withDockerRegistry` clearly plopped into the deprecated section and the preferred `docker.withRegistry` under the Advanced section. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-29782) Information returned in REST API
Title: Message Title
Karl-Heinz Marbaise created an issue
Jenkins / JENKINS-29782
Information returned in REST API
Issue Type:
Bug
Assignee:
redsolo
Components:
tfs-plugin
Created:
04/Aug/15 3:05 PM
Environment:
Jenkins 1.611, TFS Plugin 3.1.1
Priority:
Minor
Reporter:
Karl-Heinz Marbaise
Currently i'm trying to extract different informations from Jenkins builds via the REST API which works well for SVN, Git etc. but started with TFS i'm faced with the following problem.
If i take a look at the return of the REST API (json) on a SVN/Git build i got the following informations (excerpt):
"changeSet" : {
"items" : [
{
"affectedPaths" : [
"pom.xml"
],
"commitId" : "aeda48c80cde155cee1dfe2f3d8fb275bf0e7aa0",
"timestamp" : 1437760959000,
"author" : {
"absoluteUrl" : "http://ci.soebes.de:8080/user/khmarbaise",
"fullName" : "khmarbaise"
},
"comment" : "Fixed #3 Update to new mojo-parent\n",
"date" : "2015-07-24T20:02:39+0200 +0200",
"id" : "aeda48c80cde155cee1dfe2f3d8fb275bf0e7aa0",
"msg" : "Fixed #3 Update to new mojo-parent",
"paths" : [
{
"editType"
[JIRA] [core] (JENKINS-29781) BuildTrigger does not reflect moving aroung declaring job between folders
Title: Message Title Oliver Gondža started work on JENKINS-29781 Change By: Oliver Gondža Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-21421) GIT_BRANCH_SHORT for branch name without release/, feature/, etc. Just the bit after the '/'
Title: Message Title
Thomas Reinhardt commented on JENKINS-21421
Re: GIT_BRANCH_SHORT for branch name without release/, feature/, etc. Just the bit after the '/'
This would be especially handy with the "Check out to specific local branch" option. At the moment we have set this fixed to "master" but that prevents the build of multiple branches. To be more specific, the build itself works fine but "M2 Release Plugin" can not push tags back to origin when no local branch is present (see this discussion on stackoverflow).
Specifing the local branch as $ {GIT_BRANCH}
kind of works but duplicates the leading "origin/" part. $ {GIT_BRANCH,fullName=false}
does not expand the variable at all.
I will try to implement that tomorrow.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-29783) Parameterized trigger does not reflect moving aroung declaring job between folders
Title: Message Title Oliver Gondža assigned an issue to Oliver Gondža Jenkins / JENKINS-29783 Parameterized trigger does not reflect moving aroung declaring job between folders Change By: Oliver Gondža Assignee: huybrechts Oliver Gondža Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29781) BuildTrigger does not reflect moving aroung declaring job between folders
Title: Message Title Oliver Gondža assigned an issue to Oliver Gondža Jenkins / JENKINS-29781 BuildTrigger does not reflect moving aroung declaring job between folders Change By: Oliver Gondža Assignee: Oliver Gondža Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-29783) Parameterized trigger does not reflect moving aroung declaring job between folders
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-29783 Parameterized trigger does not reflect moving aroung declaring job between folders Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 04/Aug/15 3:11 PM Priority: Minor Reporter: Oliver Gondža Steps to reproduce: Create upstream and downstream job inside folder using BuildTrigger using relative reference. Move upstream job out of the folder. The reference is not updated Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-29784) DSL Job View shows many copies of Generated Items
Title: Message Title Ian Tait created an issue Jenkins / JENKINS-29784 DSL Job View shows many copies of Generated Items Issue Type: Bug Assignee: Daniel Spilker Attachments: Screenshot.png Components: job-dsl-plugin Created: 04/Aug/15 3:26 PM Environment: Job DSL plugin version 1.35 Jenkins version 1.612 Labels: DSL View Priority: Minor Reporter: Ian Tait I am creating a DSL job that creates and administrates the building of 3 other jobs. I want to watch the progress of each job's build, and when one finishes successfully, create the next job and kick off a build, then watch it and so on. I have done this successfully by creating 3 separate DSL scripts in the DSL job, which are separated by a groovy script in between that watches
[JIRA] [git-plugin] (JENKINS-21421) GIT_BRANCH_SHORT for branch name without release/, feature/, etc. Just the bit after the '/'
Title: Message Title
Thomas Reinhardt edited a comment on JENKINS-21421
Re: GIT_BRANCH_SHORT for branch name without release/, feature/, etc. Just the bit after the '/'
This would be especially handy with the "Check out to specific local branch" option. At the moment we have set this fixed to "master" but that prevents the build of multiple branches. To be more specific, the build itself works fine but "M2 Release Plugin" can not push tags back to origin when no local branch is present (see [this discussion on stackoverflow|http://stackoverflow.com/questions/3858563/active-git-branch-is-no-branch-on-hudson-ci]).Specifing the local branch as $ $ {GIT_BRANCH} kind of works but duplicates the leading "origin/" part. $ $ {GIT_BRANCH,fullName=false} does not expand the variable at all.I will try to implement that tomorrow.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-21421) GIT_BRANCH_SHORT for branch name without release/, feature/, etc. Just the bit after the '/'
Title: Message Title
Thomas Reinhardt edited a comment on JENKINS-21421
Re: GIT_BRANCH_SHORT for branch name without release/, feature/, etc. Just the bit after the '/'
This would be especially handy with the "Check out to specific local branch" option. At the moment we have set this fixed to "master" but that prevents the build of multiple branches. To be more specific, the build itself works fine but "M2 Release Plugin" can not push tags back to origin when no local branch is present (see [this discussion on stackoverflow|http://stackoverflow.com/questions/3858563/active-git-branch-is-no-branch-on-hudson-ci]).Specifing the local branch as \ $ $ {GIT_BRANCH} kind of works but duplicates the leading "origin/" part. \ $ $ {GIT_BRANCH,fullName=false} does not expand the variable at all.I will try to implement that tomorrow.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-21421) GIT_BRANCH_SHORT for branch name without release/, feature/, etc. Just the bit after the '/'
Title: Message Title
Thomas Reinhardt edited a comment on JENKINS-21421
Re: GIT_BRANCH_SHORT for branch name without release/, feature/, etc. Just the bit after the '/'
This would be especially handy with the "Check out to specific local branch" option. At the moment we have set this fixed to "master" but that prevents the build of multiple branches. To be more specific, the build itself works fine but "M2 Release Plugin" can not push tags back to origin when no local branch is present (see [this discussion on stackoverflow|http://stackoverflow.com/questions/3858563/active-git-branch-is-no-branch-on-hudson-ci]).Specifing the local branch as \ {noformat} ${GIT_BRANCH} {noformat} kind of works but duplicates the leading "origin/" part. \ ${GIT_BRANCH,fullName=false} does not expand the variable at all.I will try to implement that tomorrow.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-29785) Ability to build job that has a file parameter without sending the file
Title: Message Title Andrew Shay created an issue Jenkins / JENKINS-29785 Ability to build job that has a file parameter without sending the file Issue Type: Improvement Assignee: Unassigned Components: cli Created: 04/Aug/15 3:30 PM Priority: Minor Reporter: Andrew Shay I am currently running the cli jar on a Windows machine and I would like to be able to build a job that has a file parameter, but not have to add that parameter with the cli jar. Hopefully the change in functionality would build the job the same as if I executed the job through the web page and just didn't upload a file Add Comment
[JIRA] [git-plugin] (JENKINS-21421) GIT_BRANCH_SHORT for branch name without release/, feature/, etc. Just the bit after the '/'
Title: Message Title
Thomas Reinhardt edited a comment on JENKINS-21421
Re: GIT_BRANCH_SHORT for branch name without release/, feature/, etc. Just the bit after the '/'
This would be especially handy with the "Check out to specific local branch" option. At the moment we have set this fixed to "master" but that prevents the build of multiple branches. To be more specific, the build itself works fine but "M2 Release Plugin" can not push tags back to origin when no local branch is present (see [this discussion on stackoverflow|http://stackoverflow.com/questions/3858563/active-git-branch-is-no-branch-on-hudson-ci]).Specifing the local branch as {noformat} ${GIT_BRANCH} {noformat} kind of works but duplicates the leading "origin/" part. ${GIT_BRANCH,fullName=false} does not expand the variable at all.I will try to implement that tomorrow.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-21421) GIT_BRANCH_SHORT for branch name without release/, feature/, etc. Just the bit after the '/'
Title: Message Title
Thomas Reinhardt edited a comment on JENKINS-21421
Re: GIT_BRANCH_SHORT for branch name without release/, feature/, etc. Just the bit after the '/'
This would be especially handy with the "Check out to specific local branch" option. At the moment we have set this fixed to "master" but that prevents the build of multiple branches. To be more specific, the build itself works fine but "M2 Release Plugin" can not push tags back to origin when no local branch is present (see [this discussion on stackoverflow|http://stackoverflow.com/questions/3858563/active-git-branch-is-no-branch-on-hudson-ci]).Specifing the local branch as $ \ {GIT_BRANCH \ }kind of works but duplicates the leading "origin/" part. ${GIT_BRANCH,fullName=false} does not expand the variable at all.I will try to implement that tomorrow.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27248) List Subversion Tags parameter not available in workflow
Title: Message Title Jochen Ulrich commented on JENKINS-27248 Re: List Subversion Tags parameter not available in workflow I'm experiencing a similar issue but with an inheritance project: I cannot use the specified parameter name "SVN_BRANCH" to trigger the project from another project. It falls back to the default value. The "Build with Parameters" pages shows the correct name for the parameter but the "Parameter" page displays "Tag" and "Repository URL". Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-21421) GIT_BRANCH_SHORT for branch name without release/, feature/, etc. Just the bit after the '/'
Title: Message Title
Thomas Reinhardt edited a comment on JENKINS-21421
Re: GIT_BRANCH_SHORT for branch name without release/, feature/, etc. Just the bit after the '/'
This would be especially handy with the "Check out to specific local branch" option. At the moment we have set this fixed to "master" but that prevents the build of multiple branches. To be more specific, the build itself works fine but "M2 Release Plugin" can not push tags back to origin when no local branch is present (see [this discussion on stackoverflow|http://stackoverflow.com/questions/3858563/active-git-branch-is-no-branch-on-hudson-ci]).Specifing the local branch as $\{GIT_BRANCH\}kind of works but duplicates the leading "origin/" part. $ \ {GIT_BRANCH,fullName=false \ } does not expand the variable at all.I will try to implement that tomorrow.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [mock-slave-plugin] (JENKINS-25090) Mock slaves should use a consistent remoteFS after restart
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-25090 Mock slaves should use a consistent remoteFS after restart Change By: Jesse Glick Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28840) Deadlock between Queue.maintain and Executor.interrupt
Title: Message Title Jesse Glick commented on JENKINS-28840 Re: Deadlock between Queue.maintain and Executor.interrupt Another case in mock-slave-plugin in 1.609.1: thread dump. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled
Title: Message Title Matthew Cipollone updated an issue Jenkins / JENKINS-29130 RTC Polling broken when Proxy enabled Change By: Matthew Cipollone Hi,We have an issue with RTC polling when we have the proxy set in Jenkins. We need to set http and https proxy settings on the master for many other apps. So we do this in the Jenkins.xml file on the master. But this seems to break polling on RTC jobs. Jobs can still pull files out of source control but polling does not work. What is the difference between these 2 operations? Gives the below stack trace in the polling log: The following settings are set in the jenkins.xml:-Dhttp.proxyHost=proxy001 -Dhttps.proxyHost=proxy001 -Dhttp.proxyPort=80 -Dhttps.proxyPort=80 -Dhttp.nonProxyHosts=*.ourcompanydomain.comOur thoughts are that the IBM RTC Jenkins plug-in may not be respecting the nonProxyHost nonProxyHosts java settings. Since our RTC instance is internal to the network, it should not feed the traffic destined for RTC through the proxy.Any ideas, this one is killing us ! :) Any help would be greatly appreciated!! Gives the below stack trace in the polling log: FATAL: RTC : checking for changes failure: CRJAZ0099E An HTTP error occurred when this URL was being accessed: https://rtcserver.company.com:9443/ccm2/versionCompatibility?clientVersion=5.0. Error details: Remote host closed connection during handshake.com.ibm.team.repository.common.transport.TeamServiceException: CRJAZ0099E An HTTP error occurred when this URL was being accessed: https://rtcserver.company.com:9443/ccm2/versionCompatibility? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [teamconcert-plugin] (JENKINS-24760) Failure building the project
Title: Message Title David Jozis commented on JENKINS-24760 Re: Failure building the project I had a similar problem, and this is the only hit I found on Google for this, and I wanted to add what helped me, which is that it should be "file:///C:" not just "file:/C:". Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-29786) Incremental build - only build changed modules; wrong modules calculation
Title: Message Title Jakub Bochenski created an issue Jenkins / JENKINS-29786 Incremental build - only build changed modules; wrong modules calculation Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 04/Aug/15 5:18 PM Priority: Critical Reporter: Jakub Bochenski Given two SVN repos that are configured in the job: Repository URL: svn+ssh://s...@svn.acme.com/repos/foo Repository URL: svn+ssh://s...@svn.acme.com/repos/bar and an aggregator pom in foo, building modules from different repos: foo-submodule ../bar If there is a commit affecting bar only the root aggregator module will be built and not the bar module. Workaround (sort of): add the bar module (-pl bar) to Goals and options box, to have it always built.
[JIRA] [maven-plugin] (JENKINS-29786) Incremental build - only build changed modules; wrong modules calculation
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-29786 Incremental build - only build changed modules; wrong modules calculation Change By: Jakub Bochenski Environment: Jenkins 1.540maven-plugin 2.8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-29786) Incremental build - only build changed modules; wrong modules calculation
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-29786
Incremental build - only build changed modules; wrong modules calculation
Change By:
Jakub Bochenski
Given two SVN repos that are configured in the job: * Repository URL: svn+ssh://s...@svn.acme.com/repos/foo* Repository URL: svn+ssh://s...@svn.acme.com/repos/barand an aggregator pom in foo, building modules from different repos:{code:xml}foo-submodule../bar{code}If there is a commit affecting bar only the root aggregator module will be built and not the bar module.Workaround (sort of): add the bar module ({{-pl ../ bar}}) to {{Goals and options}} box, to have it always built.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM
Title: Message Title Sagi Sinai-Glazer updated an issue Jenkins / JENKINS-27514 Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM Change By: Sagi Sinai-Glazer Attachment: support_2015-08-04_14.10.32.zip Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM
Title: Message Title Sagi Sinai-Glazer commented on JENKINS-27514 Re: Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM Same here... see attached Support Bundle (support_2015-08-04_14.10.32.zip) for more details. Also seems to be related to JENKINS-23560 and JENKINS-26769. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-25070) Subversion fails to update externals once after external is changed.
Title: Message Title
Reece Johnston commented on JENKINS-25070
Re: Subversion fails to update externals once after external is changed.
We are presently seeing this as well, and have seen it with Jenkins {1.569, 1.580.1, 1.617}
, SVN {1.6, 1.7}
and for Subversion Plugin [2.4, 2.5.1]. Unfortunately, I need Subversion Plugin 2.4 or later due to the concurrent builds issue, so I cannot revert back to 2.3. Also, it seems to only occur on first checkout or when the external has been changed. The latter of which isn't a huge issue since the external in question is an ant build.xml, but first checkouts can occur quite frequently in our environment. For the relevant output (from Jenkins 1.580.1, SVN 1.6, and Subversion Plugin 2.5.1), see below:
Error Output
hudson.util.IOException2: revision check failed on svn+ssh://host/path_to_external/build.xml at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:196) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:137) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:488) at hudson.model.AbstractProject.checkout(AbstractProject.java:1253) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: authentication cancelled at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.io.svn.SVNSSHConnector.open(SVNSSHConnector.java:149) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:77) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1253) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:169) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:184) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:184) ... 12 more
[JIRA] [subversion-plugin] (JENKINS-25070) Subversion fails to update externals once after external is changed.
Title: Message Title
Reece Johnston edited a comment on JENKINS-25070
Re: Subversion fails to update externals once after external is changed.
We are presently seeing this as well, and have seen it with Jenkins { ( 1.569, 1.580.1, 1.617 } ) , SVN { ( 1.6, 1.7 } ) and for Subversion Plugin [ ( 2.4, 2.5.1 ] ) . Unfortunately, I need Subversion Plugin 2.4 or later due to the concurrent builds issue, so I cannot revert back to 2.3. Also, it seems to only occur on first checkout or when the external has been changed. The latter of which isn't a huge issue since the external in question is an ant build.xml, but first checkouts can occur quite frequently in our environment. For the relevant output (from Jenkins 1.580.1, SVN 1.6, and Subversion Plugin 2.5.1), see below:{panel:title=Error Output}hudson.util.IOException2: revision check failed on svn+ssh://host/path_to_external/build.xml at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:196) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:137) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:488) at hudson.model.AbstractProject.checkout(AbstractProject.java:1253) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: authentication cancelled at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.io.svn.SVNSSHConnector.open(SVNSSHConnector.java:149) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:77) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1253) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:169) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:184) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:184) ... 12 more{panel}
[JIRA] [subversion-plugin] (JENKINS-25070) Subversion fails to update externals once after external is changed.
Title: Message Title
Reece Johnston edited a comment on JENKINS-25070
Re: Subversion fails to update externals once after external is changed.
We are presently seeing this as well, and have seen it with Jenkins (1.569, 1.580.1, 1.617), SVN (1.6, 1.7) and for Subversion Plugin (2.4, 2. 4.4, 2. 5.1). Unfortunately, I need Subversion Plugin 2.4 or later due to the concurrent builds issue, so I cannot revert back to 2.3. Also, it seems to only occur on first checkout or when the external has been changed. The latter of which isn't a huge issue since the external in question is an ant build.xml, but first checkouts can occur quite frequently in our environment. For the relevant output (from Jenkins 1.580.1, SVN 1.6, and Subversion Plugin 2.5.1), see below:{panel:title=Error Output}hudson.util.IOException2: revision check failed on svn+ssh://host/path_to_external/build.xml at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:196) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:137) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:488) at hudson.model.AbstractProject.checkout(AbstractProject.java:1253) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: authentication cancelled at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.io.svn.SVNSSHConnector.open(SVNSSHConnector.java:149) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:77) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1253) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:169) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:184) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:184) ... 12 more{panel}
[JIRA] [subversion-plugin] (JENKINS-25070) Subversion fails to update externals once after external is changed.
Title: Message Title
Reece Johnston edited a comment on JENKINS-25070
Re: Subversion fails to update externals once after external is changed.
We are presently seeing this as well, and have seen it with Jenkins (1.569, 1.580.1, 1.617), SVN (1.6, 1.7) and for Subversion Plugin (2.4, 2.4.4, 2.5.1). Unfortunately, I need Subversion Plugin 2.4 or later due to the concurrent builds issue, so I cannot revert back to 2.3. Also, it seems to only occur on first checkout or when the external has been changed. The latter of which isn't a huge issue since the external in question is an ant build.xml, but first checkouts can occur quite frequently in our environment. I should also add that I have specified additional credentials for all of the jobs with a realm of "svn+ssh://host/path/to/svn", noting that this is svn+ssh protocol. For the relevant output (from Jenkins 1.580.1, SVN 1.6, and Subversion Plugin 2.5.1), see below:{panel:title=Error Output}hudson.util.IOException2: revision check failed on svn+ssh://host/path_to_external/build.xml at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:196) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:137) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:488) at hudson.model.AbstractProject.checkout(AbstractProject.java:1253) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: authentication cancelled at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.io.svn.SVNSSHConnector.open(SVNSSHConnector.java:149) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:77) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1253) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:169) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:184) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:184) ... 12 more{panel}
[JIRA] [subversion-plugin] (JENKINS-25070) Subversion fails to update externals once after external is changed.
Title: Message Title
Reece Johnston edited a comment on JENKINS-25070
Re: Subversion fails to update externals once after external is changed.
We are presently seeing this as well, and have seen it with Jenkins (1.569, 1.580.1, 1.617), SVN (1.6, 1.7) and for Subversion Plugin (2.4, 2.4.4, 2.5.1). Unfortunately, I need Subversion Plugin 2.4 or later due to the concurrent builds issue, so I cannot revert back to 2.3. Also, it seems to only occur on first checkout or when the external has been changed. The latter of which isn't a huge issue since the external in question is an ant build.xml, but first checkouts can occur quite frequently in our environment. I should also add that I have specified additional credentials for all of the jobs with a realm of "svn+ssh://host/path/to/svn", noting that this is svn+ssh protocol. For the relevant output (from Jenkins 1.580.1, SVN 1.6, and Subversion Plugin 2.5.1), see below:{panel:title=Error Output}hudson.util.IOException2: revision check failed on svn+ssh://host/ path_to_external path / to/external/ build.xml at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:196) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:137) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:488) at hudson.model.AbstractProject.checkout(AbstractProject.java:1253) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: authentication cancelled at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.io.svn.SVNSSHConnector.open(SVNSSHConnector.java:149) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:77) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1253) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:169) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:184) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:184) ... 12 more{panel}
[JIRA] [github-plugin] (JENKINS-29787) github-plugin com.cloudbees.jenkins.GitHubRepositoryNameContributor$FromSCM.parseAssociatedNames java.lang.NullPointerException
Title: Message Title Alan Scherger created an issue Jenkins / JENKINS-29787 github-plugin com.cloudbees.jenkins.GitHubRepositoryNameContributor$FromSCM.parseAssociatedNames java.lang.NullPointerException Issue Type: Bug Assignee: Kanstantsin Shautsou Components: github-plugin Created: 04/Aug/15 5:59 PM Environment: Jenkins 1.623 github-plugin: 1.12.0 Priority: Minor Reporter: Alan Scherger When saving the configuration of a project (configSubmit) I get the following stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(Servle
[JIRA] [github-plugin] (JENKINS-29787) NPE on stop
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-29787 NPE on stop Change By: Kanstantsin Shautsou Summary: NPE on stop () Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-29787) NPE on stop()
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-29787 NPE on stop() Change By: Kanstantsin Shautsou Summary: github-plugin com.cloudbees.jenkins.GitHubRepositoryNameContributor$FromSCM.parseAssociatedNames java.lang.NullPointerException NPE on stop() Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29765) Build Retry (both Naginator and Rebuild) pick wrong Git SHA under certain circumstances
Title: Message Title Eric Griswold updated an issue Jenkins / JENKINS-29765 Build Retry (both Naginator and Rebuild) pick wrong Git SHA under certain circumstances Change By: Eric Griswold This is easily reproduced on a standalone Cent 6 or Cent 7 machine.Create a job:* Uses Git* A trivial build step that fails, "false" or "exit 1" in the shell build-step for example* Uses one of the above retry mechanisms (Naginator or Rebuilder)* In the case of Naginator, stub it with a regex to keep it from automatically retrying* In the case of Rebuilder, enable the rebuild without parameters* Commit and run a build. It should fail. Note Git SHA (This is build #1)* Make a second build and run it. It should also fail. Note the Git SHA (This is build #2)* Now go back to build #1 and retrigger it. (build #3) My expectation is that the Expectation:The retriggered build (build #3) should have the same Git SHA as build #1. When I try it, the Observed problem:The Git SHA is the HEAD of the branch at the time of the retrigger. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29765) Build Retry (both Naginator and Rebuild) pick wrong Git SHA under certain circumstances
Title: Message Title Eric Griswold updated an issue Jenkins / JENKINS-29765 Build Retry (both Naginator and Rebuild) pick wrong Git SHA under certain circumstances Change By: Eric Griswold This is easily reproduced on a standalone Cent 6 or Cent 7 machine.Create a job:* Uses Git* A trivial build step that fails, "false" or "exit 1" in the shell build-step for example* Uses one of the above retry mechanisms (Naginator or Rebuilder)* In the case of Naginator, stub it with a regex to keep it from automatically retrying* In the case of Rebuilder, enable the rebuild without parameters* Commit Make a commit and run a build. It should fail. Note Git SHA (This is build #1)* Make a second commit, then build and run it. It should also fail. Note the Git SHA (This is build #2)* Now go back to build #1 and retrigger it. (build #3)Expectation:The retriggered build (build #3) should have the same Git SHA as build #1.Observed problem:The Git SHA is the HEAD of the branch at the time of the retrigger. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9283) Add timezone to cron expression
Title: Message Title Clint Brown commented on JENKINS-9283 Re: Add timezone to cron _expression_ I didn't bring it up initially cause I didn't realize it was an issue until I actually tried it Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29765) Build Retry (both Naginator and Rebuild) pick wrong Git SHA under certain circumstances
Title: Message Title Eric Griswold updated an issue Jenkins / JENKINS-29765 Build Retry (both Naginator and Rebuild) pick wrong Git SHA under certain circumstances Change By: Eric Griswold This is easily reproduced on a standalone Cent 6 or Cent 7 machine.Create a job:* Uses Git* A trivial build step that fails, "false" or "exit 1" in the shell build-step for example* Uses one of the above retry mechanisms (Naginator or Rebuilder)* In the case of Naginator, stub it with a regex to keep it from automatically retrying* In the case of Rebuilder, enable the rebuild without parameters* Make a commit and run a build. It should fail. Note Git SHA (This is build #1)* Make a second commit, then build it. It should also fail. Note the Git SHA (This is build #2)* Now go back to build #1 and retrigger it. (build #3)Expectation:The retriggered build (build #3) should have use the same Git SHA as build #1.Observed problem:The Git SHA is the HEAD of the branch at the time of the retrigger. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-29717) Exception during push
Title: Message Title William Gautier started work on JENKINS-29717 Change By: William Gautier Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-29717) Exception during push
Title: Message Title William Gautier commented on JENKINS-29717 Re: Exception during push Somebody else also reported this problem. I believe this is the cf-java-client receiving an unexpected json from the push call, probably receiving an error from the target. Unfortunately that deserialization error from the cf-java-client is masking the actual error from the target. I'm going to look into this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [join-plugin] (JENKINS-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin
Title: Message Title Patrik Boström updated an issue Jenkins / JENKINS-29652 Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin Change By: Patrik Boström Component/s: delivery-pipeline-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [join-plugin] (JENKINS-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin
Title: Message Title Patrik Boström resolved as Duplicate This is an issue for Join plugin. Jenkins / JENKINS-29652 Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin Change By: Patrik Boström Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29771) Rendering: Footer elements not re-positionable
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-29771 Rendering: Footer elements not re-positionable Change By: Manuel Jesús Recena Soto Assignee: Manuel Jesús Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
