[JIRA] (JENKINS-60581) Plugin Compat Tester should not print Maven download logs in process-test-classes steps
Title: Message Title Oleg Nenashev commented on JENKINS-60581 Re: Plugin Compat Tester should not print Maven download logs in process-test-classes steps Sure, feel free to take it Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203706.1577188091000.853.1577687460192%40Atlassian.JIRA.
[JIRA] (JENKINS-60604) Slave agent connection failed
Title: Message Title Vadivel Natarajan updated an issue Jenkins / JENKINS-60604 Slave agent connection failed Change By: Vadivel Natarajan Slave agent connection getting failed with the below error. Please check and provide the solution for this issue. java.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208) at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:800) at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:311) at hudson.remoting.Channel.close(Channel.java:1405) at hudson.remoting.Channel.close(Channel.java:1358) at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:737) at hudson.slaves.SlaveComputer.access$800(SlaveComputer.java:96) at hudson.slaves.SlaveComputer$3.run(SlaveComputer.java:655) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) 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:748)
[JIRA] (JENKINS-60604) Slave agent connection failed
Title: Message Title Vadivel Natarajan created an issue Jenkins / JENKINS-60604 Slave agent connection failed Issue Type: Bug Assignee: Rick Components: agent-loadbalance-plugin, core, slave-setup-plugin Created: 2019-12-30 05:26 Environment: Ubuntu linux machine, Jenkins version 2.90 am using. Labels: slave jenkins user-experience performance windows Priority: Major Reporter: Vadivel Natarajan Slave connection getting failed with the below error. Please check and provide the solution for this issue. java.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208) at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213) at
[JIRA] (JENKINS-60417) Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Title: Message Title shubham srivastava commented on JENKINS-60417 Re: Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version Ulli Hafner Any progress/update on this issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203478.1575970934000.847.1577673180719%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs after git rev-list command
Title: Message Title Mark Waite commented on JENKINS-60536 Re: Jenkins job hangs after git rev-list command Thanks. You are correct. I had not read enough of the details of the new Jira plugin from Atlassian. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203639.1576745651000.813.1577668200257%40Atlassian.JIRA.
[JIRA] (JENKINS-60603) Send emails when new administrative monitors appear
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-60603 Send emails when new administrative monitors appear Issue Type: New Feature Assignee: Adrien Lecharpentier Components: core, mailer-plugin, plugin-proposals Created: 2019-12-30 00:05 Priority: Minor Reporter: Daniel Beck It would be nice if Jenkins were able to inform admins via email about changes in administrative monitors (i.e. new admin monitors appear, or existing ones are gone – like a very basic monitoring system for active admin monitors). Unsure whether it makes sense to put this in core (and only be effective if Mailer Plugin is installed), or whether it should be in Mailer Plugin, or an altogether new plugin. It feels like a "core" feature (i.e. make it available to every install), but given how we split our components, the implementation there would be weird. Add Comment
[JIRA] (JENKINS-60536) Jenkins job hangs after git rev-list command
Title: Message Title benoit guerin commented on JENKINS-60536 Re: Jenkins job hangs after git rev-list command Hello Mark Waite Thanks for the news, and the pointers. This new plugin only handles build and deployment informations. My company uses the legacy Jira plugin to add comments on issues, and also the jira-steps plugin to enforce our workflow. I do not see how I will do this with this new plugin, until all these features are implemented on it. And I also think I am not alone with these usecases. This new Jira plugin is too young enough, and not complete enough to be considered as a drop in remplacement for the legacy Jira one. Plus the legacy is a hard dependency for blue ocean. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203639.1576745651000.790.1577656260310%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs after git rev-list command
Title: Message Title Mark Waite commented on JENKINS-60536 Re: Jenkins job hangs after git rev-list command A new Jira integration has been created by Atlassian. You might consider trying the new integration, available from https://plugins.jenkins.io/atlassian-jira-software-cloud . A blog post announcing the new plugin will likely be published early in 2020. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203639.1576745651000.781.1577654580214%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs after git rev-list command
Title: Message Title
Mike Poulson edited a comment on JENKINS-60536
Re: Jenkins job hangs after git rev-list command
We saw this issue manifest in jobs also hanging at "Started by user" with the only thing in the console log. We have repro on fully updated 2.210 system with Jira plugin running 3.0.11. By dumping the java threads (sudo jstack > jstack-out.txt) we discovered the following thread consuming a high amount of CPU. We were able to see the issue start on ~12/18/2019 after no changes to our master or the plugins. This was easily seen based on CPU history logs which show the system would consume a full CPU when it was hung.By removing the config file hudson.plugins.jira.JiraGlobalConfiguration.xml and restarting it resolved the issue.{code:java}// "Handling GET /job/App/job/master/3/ from 172.30.4.236 : qtp328638398-38531 WorkflowRun/index.jelly GitChangeSetList/digest.jelly" #38531 prio=5 os_prio=0 cpu=58.61ms elapsed=2320.00s tid=0x7f446840b800 nid=0x23a3 waiting on condition [0x7f440703d000]"Handling GET /job/App/job/master/3/ from 172.30.4.236 : qtp328638398-38531 WorkflowRun/index.jelly GitChangeSetList/digest.jelly" #38531 prio=5 os_prio=0 cpu=58.61ms elapsed=2320.00s tid=0x7f446840b800 nid=0x23a3 waiting on condition [0x7f440703d000] java.lang.Thread.State: WAITING (parking) at jdk.internal.misc.Unsafe.park(java.base@11.0.5/Native Method) - parking to wait for <0x0006bfcf6888> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) at java.util.concurrent.locks.LockSupport.park(java.base@11.0.5/LockSupport.java:194) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(java.base@11.0.5/AbstractQueuedSynchronizer.java:885) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(java.base@11.0.5/AbstractQueuedSynchronizer.java:917) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@11.0.5/AbstractQueuedSynchronizer.java:1240) at java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.5/ReentrantLock.java:267) at org.apache.http.nio.pool.AbstractNIOConnPool.lease(AbstractNIOConnPool.java:278) at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.requestConnection(PoolingNHttpClientConnectionManager.java:295) at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.requestConnection(AbstractClientExchangeHandler.java:377) at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.start(DefaultClientExchangeHandlerImpl.java:129) at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:141) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:75) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:108) at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.execute(SettableFuturePromiseHttpPromiseAsyncClient.java:36) at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.doExecute(ApacheAsyncHttpClient.java:417) at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.execute(ApacheAsyncHttpClient.java:364) at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.execute(DefaultRequest.java:297) at com.atlassian.jira.rest.client.internal.async.AtlassianHttpClientDecorator$AuthenticatedRequestBuilder.execute(AtlassianHttpClientDecorator.java:83) at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.get(DefaultRequest.java:253) at
[JIRA] (JENKINS-60536) Jenkins job hangs after git rev-list command
Title: Message Title Mike Poulson commented on JENKINS-60536 Re: Jenkins job hangs after git rev-list command We saw this issue manifest in jobs also hanging at "Started by user" with the only thing in the console log. By dumping the java threads (sudo jstack > jstack-out.txt) we discovered the following thread consuming a high amount of CPU. We were able to see the issue start on ~12/18/2019 after no changes to our master or the plugins. This was easily seen based on CPU history logs which show the system would consume a full CPU when it was hung. By removing the config file hudson.plugins.jira.JiraGlobalConfiguration.xml and restarting it resolved the issue. // "Handling GET /job/App/job/master/3/ from 172.30.4.236 : qtp328638398-38531 WorkflowRun/index.jelly GitChangeSetList/digest.jelly" #38531 prio=5 os_prio=0 cpu=58.61ms elapsed=2320.00s tid=0x7f446840b800 nid=0x23a3 waiting on condition [0x7f440703d000]"Handling GET /job/App/job/master/3/ from 172.30.4.236 : qtp328638398-38531 WorkflowRun/index.jelly GitChangeSetList/digest.jelly" #38531 prio=5 os_prio=0 cpu=58.61ms elapsed=2320.00s tid=0x7f446840b800 nid=0x23a3 waiting on condition [0x7f440703d000] java.lang.Thread.State: WAITING (parking) at jdk.internal.misc.Unsafe.park(java.base@11.0.5/Native Method) - parking to wait for <0x0006bfcf6888> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) at java.util.concurrent.locks.LockSupport.park(java.base@11.0.5/LockSupport.java:194) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(java.base@11.0.5/AbstractQueuedSynchronizer.java:885) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(java.base@11.0.5/AbstractQueuedSynchronizer.java:917) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@11.0.5/AbstractQueuedSynchronizer.java:1240) at java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.5/ReentrantLock.java:267) at org.apache.http.nio.pool.AbstractNIOConnPool.lease(AbstractNIOConnPool.java:278) at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.requestConnection(PoolingNHttpClientConnectionManager.java:295) at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.requestConnection(AbstractClientExchangeHandler.java:377) at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.start(DefaultClientExchangeHandlerImpl.java:129) at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:141) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:75) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:108) at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.execute(SettableFuturePromiseHttpPromiseAsyncClient.java:36) at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.doExecute(ApacheAsyncHttpClient.java:417) at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.execute(ApacheAsyncHttpClient.java:364) at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.execute(DefaultRequest.java:297) at com.atlassian.jira.rest.client.internal.async.AtlassianHttpClientDecorator$AuthenticatedRequestBuilder.execute(AtlassianHttpClientDecorator.java:83) at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.get(DefaultRequest.java:253) at
[JIRA] (JENKINS-60316) Git client plugin doesn't quote file locations in askpass wrappers
Title: Message Title René Scheibe updated an issue Jenkins / JENKINS-60316 Git client plugin doesn't quote file locations in askpass wrappers Change By: René Scheibe Comment: I will have a look at it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203313.1574939216000.767.1577638260202%40Atlassian.JIRA.
[JIRA] (JENKINS-60581) Plugin Compat Tester should not print Maven download logs in process-test-classes steps
Title: Message Title Gyanesha Prajjwal commented on JENKINS-60581 Re: Plugin Compat Tester should not print Maven download logs in process-test-classes steps I would like to contribute on this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203706.1577188091000.764.1577635020272%40Atlassian.JIRA.
[JIRA] (JENKINS-60305) Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required
Title: Message Title benoit guerin assigned an issue to benoit guerin Jenkins / JENKINS-60305 Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required Change By: benoit guerin Assignee: benoit guerin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203300.1574868719000.755.1577629981451%40Atlassian.JIRA.
[JIRA] (JENKINS-60305) Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required
Title: Message Title benoit guerin started work on JENKINS-60305 Change By: benoit guerin Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203300.1574868719000.748.1577629981362%40Atlassian.JIRA.
[JIRA] (JENKINS-60305) Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required
Title: Message Title benoit guerin updated JENKINS-60305 Jenkins / JENKINS-60305 Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required Change By: benoit guerin Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203300.1574868719000.757.1577629981473%40Atlassian.JIRA.
[JIRA] (JENKINS-60316) Git client plugin doesn't quote file locations in askpass wrappers
Title: Message Title René Scheibe assigned an issue to René Scheibe Jenkins / JENKINS-60316 Git client plugin doesn't quote file locations in askpass wrappers Change By: René Scheibe Assignee: René Scheibe Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203313.1574939216000.738.1577628604493%40Atlassian.JIRA.
[JIRA] (JENKINS-60316) Git client plugin doesn't quote file locations in askpass wrappers
Title: Message Title René Scheibe started work on JENKINS-60316 Change By: René Scheibe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203313.1574939216000.740.1577628604556%40Atlassian.JIRA.
[JIRA] (JENKINS-60316) Git client plugin doesn't quote file locations in askpass wrappers
Title: Message Title René Scheibe commented on JENKINS-60316 Re: Git client plugin doesn't quote file locations in askpass wrappers I will have a look at it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203313.1574939216000.734.1577628540128%40Atlassian.JIRA.
[JIRA] (JENKINS-40517) Allow changing delimiter in log output
Title: Message Title Pierre Beitz started work on JENKINS-40517 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177193.1481911536000.730.1577628240521%40Atlassian.JIRA.
[JIRA] (JENKINS-40517) Allow changing delimiter in log output
Title: Message Title Pierre Beitz updated JENKINS-40517 Jenkins / JENKINS-40517 Allow changing delimiter in log output Change By: Pierre Beitz Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177193.1481911536000.732.1577628240557%40Atlassian.JIRA.
[JIRA] (JENKINS-11048) Broken link in help text of Audit Trail plugin configuration
Title: Message Title Pierre Beitz updated JENKINS-11048 Jenkins / JENKINS-11048 Broken link in help text of Audit Trail plugin configuration Change By: Pierre Beitz Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.141258.1316451512000.720.1577627340386%40Atlassian.JIRA.
[JIRA] (JENKINS-60305) Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required
Title: Message Title benoit guerin commented on JENKINS-60305 Re: Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required Duplicates of JENKINS-56987 I think Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203300.1574868719000.713.1577624340291%40Atlassian.JIRA.
[JIRA] (JENKINS-60602) Bitbucket integration with Jenkins
Title: Message Title Alex Martynenko updated an issue Jenkins / JENKINS-60602 Bitbucket integration with Jenkins Change By: Alex Martynenko Please, advice how to make such integration. * I have merged PR's in Bitbucket. * I would like the information from these PR's (diff pull request number + title) to populate in the parametrised "Release Notes" field of Jenkins. * This should happen when you click the "Build with parameters" button in Jenkins. Example of view merged pull request in Bitbucket (that should come to Jenkins):#490: Implementation release notes feature #491: Fixing bug in release notes#492: Improvements in release notes functionality Example of Release Notes field in Jenkins (that we have in current configuration):Attachment: release-notes.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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
[JIRA] (JENKINS-60602) Bitbucket integration with Jenkins
Title: Message Title Alex Martynenko updated an issue Jenkins / JENKINS-60602 Bitbucket integration with Jenkins Change By: Alex Martynenko Please, advice how is better to make such integration. * I have merged PR's in Bitbucket. * I would like the information from these PR's (diff pull request number + title) to populate in the parametrised "Release Notes" field of Jenkins. * This should happen when you click the "Build with parameters" button in Jenkins. Example of view merged pull request in Bitbucket (that should come to Jenkins):#490: Implementation release notes feature #491: Fixing bug in release notes#492: Improvements in release notes functionalityExample of Release Notes field in Jenkins (that we have in current configuration):Attachment: release-notes.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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
[JIRA] (JENKINS-60602) Bitbucket integration with Jenkins
Title: Message Title Alex Martynenko created an issue Jenkins / JENKINS-60602 Bitbucket integration with Jenkins Issue Type: Task Assignee: Christian Del Monte Attachments: release-notes.png Components: bitbucket-push-and-pull-request-plugin, webhook-step-plugin Created: 2019-12-29 12:46 Labels: jenkins bitbucket Priority: Critical Reporter: Alex Martynenko Please, advice how to make such integration. I have merged PR's in Bitbucket. I would like the information from these PR's (diff pull request number + title) to populate in the parametrised "Release Notes" field of Jenkins. This should happen when you click the "Build with parameters" button in Jenkins. Example of view merged pull request in Bitbucket (that should come to Jenkins): #490: Implementation release notes feature Example of Release Notes field in Jenkins (that we have in current configuration): Attachment: release-notes.png
[JIRA] (JENKINS-60316) Git client plugin doesn't quote file locations in askpass wrappers
Title: Message Title René Scheibe updated an issue Jenkins / JENKINS-60316 Git client plugin doesn't quote file locations in askpass wrappers Change By: René Scheibe Environment: git-client-plugin 3.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203313.1574939216000.704.1577621460183%40Atlassian.JIRA.
[JIRA] (JENKINS-55655) BlueOcean Pipeline creation does not respect ssh ProxyCommand even though classic project creation does
Title: Message Title René Scheibe stopped work on JENKINS-55655 Change By: René Scheibe Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196833.1547738918000.701.1577619960266%40Atlassian.JIRA.
[JIRA] (JENKINS-56150) git plugin with repo that has empty .gitmodules file NPE during submodule update
Title: Message Title René Scheibe updated JENKINS-56150 Jenkins / JENKINS-56150 git plugin with repo that has empty .gitmodules file NPE during submodule update Change By: René Scheibe Status: Fixed but Unreleased Resolved Released As: git-4.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197596.1550187897000.698.1577618580270%40Atlassian.JIRA.
[JIRA] (JENKINS-56150) git plugin with repo that has empty .gitmodules file NPE during submodule update
Title: Message Title René Scheibe updated an issue Jenkins / JENKINS-56150 git plugin with repo that has empty .gitmodules file NPE during submodule update Change By: René Scheibe Component/s: git-plugin Component/s: git-client-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197596.1550187897000.686.1577618340275%40Atlassian.JIRA.
[JIRA] (JENKINS-56150) git plugin with repo that has empty .gitmodules file NPE during submodule update
Title: Message Title René Scheibe commented on JENKINS-56150 Re: git plugin with repo that has empty .gitmodules file NPE during submodule update I found the respective pull request and added a link to the ticket. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197596.1550187897000.688.1577618340306%40Atlassian.JIRA.
