[JIRA] (JENKINS-49547) Description block should support html format
Title: Message Title Lajish Lakshmanan created an issue Jenkins / JENKINS-49547 Description block should support html format Issue Type: Improvement Assignee: Dominik Bartholdi Components: nodelabelparameter-plugin Created: 2018-02-14 10:21 Environment: Any Priority: Minor Reporter: Lajish Lakshmanan Hi there, This is a small enhancement for the mentioned plugin. The description block for Label should support html content. Regards, Lajish Lakshmanan Add Comment
[JIRA] (JENKINS-49485) jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
Title: Message Title
Sam Gleske commented on JENKINS-49485
Re: jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
How are you running your master? Is it possible there's a network issue blocking GitHub from your master? e.g. hosts file, misconfigured proxy, firewall, etc. I've tested this plugin successfully running Jenkins in a docker container, my laptop, and a VM. I'm not able to reproduce your issue.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48974) Pipeline Intermittent "Error grabbing Grapes" Issues
Title: Message Title Sam Gleske commented on JENKINS-48974 Re: Pipeline Intermittent "Error grabbing Grapes" Issues This is reliably reproducible if one runs a multibranch pipeline with multiple branches building concurrently attempting to Grab via a globally configured pipeline library. Here's an example: https://github.com/samrocketman/jenkins-bootstrap-jervis/issues/19 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48361) ‘Jenkinsfile’ not found when PR triggers a build with Bitbucket
Title: Message Title László Terjéki edited a comment on JENKINS-48361 Re: ‘Jenkinsfile’ not found when PR triggers a build with Bitbucket I faced with the same issue like in [# comment-321827 ] by [~timdowney]: Lightweight checkout not working for PRs. As I found the issue came in with version 2.2.6 when the bitbucket REST is used to get the content of Jenkinsfile instead of cloning it. The configuration for the BitBucket source to use HEAD instead of merge and also a BitBucket server is used.Is there anything can be done to avoid this kind of issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48361) ‘Jenkinsfile’ not found when PR triggers a build with Bitbucket
Title: Message Title László Terjéki commented on JENKINS-48361 Re: ‘Jenkinsfile’ not found when PR triggers a build with Bitbucket I faced with the same issue like in comment-321827 by Tim Downey: Lightweight checkout not working for PRs. As I found the issue came in with version 2.2.6 when the bitbucket REST is used to get the content of Jenkinsfile instead of cloning it. The configuration for the BitBucket source to use HEAD instead of merge and also a BitBucket server is used. Is there anything can be done to avoid this kind of issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48563) Agent Labels missing in GUI
Title: Message Title Carlos Lopez commented on JENKINS-48563 Re: Agent Labels missing in GUI Daniel Beck I opened this issue on behalf of Jason Newblanc. Jason Newblanc - Can you please provide the requested input when the issue is exposed? The output from Required Data: CJP/CJT Hang Issue On Linux might be really useful in this context. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44430) p4 authenticity of 'perforce:1666' can't be established
Title: Message Title Paul Allen assigned an issue to Paul Allen Jenkins / JENKINS-44430 p4 authenticity of 'perforce:1666' can't be established Change By: Paul Allen Labels: P4_VERIFY Assignee: Paul Allen Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47366) Checkout in second stage sets SUCCESS on Github commit
Title: Message Title Alexander Vorobiev updated an issue Jenkins / JENKINS-47366 Checkout in second stage sets SUCCESS on Github commit Change By: Alexander Vorobiev Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40991) No signature of method: groovy.util.Node.div()... error in configure block
Title: Message Title
Sam Gleske commented on JENKINS-40991
Re: No signature of method: groovy.util.Node.div()... error in configure block
I solved this odd message by quoting the selector. Example:
maven{
mavenInstallation 'maven339'
goals '-B -q dependency:resolve-plugins'
configure {
it / 'injectBuildVariables' << false
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title
Stefan Drissen updated an issue
Jenkins / JENKINS-49546
java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Change By:
Stefan Drissen
Since upgrading from the pre-Java SDK TFS-plugin (3.2) to the latest plugin (5.126.0) I am needing to tickle my agents every now and then. They will work fine for a few days and then suddenly one will start throwing the above error. Once in this state, that agent never recovers and the Jenkins agent task needs to be restarted. That agent will then behave for some time.The agents are started via the Windows Task Scheduler.Complete log:{code:java}Started by upstream project "/build work" build number 325originally caused by:Started by an SCM change[EnvInject] - Loading node environment variables.Building remotely on (coded_ui_oe) in workspace c:\jenkins\workspace\\work\coded.ui_run.all.tests.ieFATAL: java.io.IOException: Remote call on JNLP4-connect connection from 10.2.33.142/10.2.33.142:4028 failedAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.2.33.142/10.2.33.142:4028at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1696)at hudson.remoting.UserResponse.retrieve(UserRequest.java:313)at hudson.remoting.Channel.call(Channel.java:909)at hudson.plugins.tfs.model.Server.execute(Server.java:233)at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:280)at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:276)at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:292)at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:394)at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:343)at hudson.scm.SCM.checkout(SCM.java:504)at hudson.model.AbstractProject.checkout(AbstractProject.java:1203)at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:136)at hudson.model.Run.execute(Run.java:1727)at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429)java.lang.NoClassDefFoundError: Could not initialize class com.microsoft.tfs.core.config.persistence.DefaultPersistenceStoreProviderat hudson.plugins.tfs.model.Server.(Server.java:119)at hudson.plugins.tfs.commands.AbstractCallableCommand.createServer(AbstractCallableCommand.java:45)at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:56)at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:34)at hudson.remoting.UserRequest.perform(UserRequest.java:210)at
[JIRA] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title
Stefan Drissen updated an issue
Jenkins / JENKINS-49546
java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Change By:
Stefan Drissen
Since upgrading from the pre-Java SDK TFS-plugin (3.2) to the latest plugin (5.126.0) I am needing to tickle my agents every now and then. They will work fine for a few days and then suddenly one will start throwing the above error. Once in this state, that agent never recovers and the Jenkins agent task needs to be restarted. That agent will then behave for some time.The agents are started via the Windows Task Scheduler.Complete log:{code:java}Started by upstream project "/build work" build number 325originally caused by:Started by an SCM change[EnvInject] - Loading node environment variables.Building remotely on (coded_ui_oe) in workspace c:\jenkins\workspace\\work\coded.ui_run.all.tests.ieFATAL: java.io.IOException: Remote call on JNLP4-connect connection from 10.2.33.142/10.2.33.142:4028 failedAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.2.33.142/10.2.33.142:4028at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1696)at hudson.remoting.UserResponse.retrieve(UserRequest.java:313)at hudson.remoting.Channel.call(Channel.java:909)at hudson.plugins.tfs.model.Server.execute(Server.java:233)at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:280)at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:276)at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:292)at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:394)at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:343)at hudson.scm.SCM.checkout(SCM.java:504)at hudson.model.AbstractProject.checkout(AbstractProject.java:1203)at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:136)at hudson.model.Run.execute(Run.java:1727)at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429)java.lang.NoClassDefFoundError: Could not initialize class com.microsoft.tfs.core.config.persistence.DefaultPersistenceStoreProviderat hudson.plugins.tfs.model.Server.(Server.java:119)at hudson.plugins.tfs.commands.AbstractCallableCommand.createServer(AbstractCallableCommand.java:45)at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:56)at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:34)at hudson.remoting.UserRequest.perform(UserRequest.java:210)at
[JIRA] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Stefan Drissen created an issue Jenkins / JENKINS-49546 java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 2018-02-14 08:54 Environment: Windows 2012R2 x64 Java 1.8.0_161 x64 Jenkins 2.105 TFS-plugni 5.126.0 Labels: slave plugin windows Priority: Critical Reporter: Stefan Drissen Since upgrading from the pre-Java SDK TFS-plugin (3.2) to the latest plugin (5.126.0) I am needing to tickle my agents every now and then. They will work fine for a few days and then suddenly one will start throwing the above error. Once in this state, that agent never recovers and the Jenkins agent task needs to be restarted. That agent will then behave for some time. The agents are started via the Windows Task Scheduler. Complete log: Started by upstream project "/build work" build number 325 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on (coded_ui_oe) in workspace c:\jenkins\workspace\\work\coded.ui_run.all.tests.ie FATAL: java.io.IOException: Remote call on JNLP4-connect connection from 10.2.33.142/10.2.33.142:4028 failed Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.2.33.142/10.2.33.142:4028 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1696)
[JIRA] (JENKINS-46193) New test failures are reported as both new test failures and existing test failures.
Title: Message Title v o commented on JENKINS-46193 Re: New test failures are reported as both new test failures and existing test failures. Our team is also experiencing this problem in some of our pipelines. Both "New failing" and "Fixed" lists are wrong. Some tests show up in these lists even if we simply re-run a build. Hopefully this will be fixed soon because this feature is very useful (one of the main reasons our team is using Blue Ocean). I am using Blue Ocean 1.4.0. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49274) Reverse proxy auth is not authenticating users
Title: Message Title roadrunner2 commented on JENKINS-49274 Re: Reverse proxy auth is not authenticating users For Apache I think the more proper setting is: RequestHeader unset Authorization (verified this fixes the issues for me too) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49543) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl
Title: Message Title Oleg Nenashev commented on JENKINS-49543 Re: Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl All classes from modules should be serializable, will try to reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49543) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-49543 Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
