[JIRA] (JENKINS-52670) WorkflowGraph.FlowNodeContainer is causing memory performance issues
Title: Message Title Yaniv Levi updated JENKINS-52670 Released as part of version 5.5.2 Download link Jenkins / JENKINS-52670 WorkflowGraph.FlowNodeContainer is causing memory performance issues Change By: Yaniv Levi Status: Fixed but Unreleased Resolved Resolution: Fixed Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52670) WorkflowGraph.FlowNodeContainer is causing memory performance issues
Title: Message Title Yaniv Levi assigned an issue to Yaniv Levi Jenkins / JENKINS-52670 WorkflowGraph.FlowNodeContainer is causing memory performance issues Change By: Yaniv Levi Assignee: Ayellet Lazar Yaniv Levi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54184) manager.removeSummaries() throws UnsupportedOperationException
Title: Message Title ikedam updated an issue Jenkins / JENKINS-54184 manager.removeSummaries() throws UnsupportedOperationException Change By: ikedam Released As: groovy-postbuild-2.4.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54184) manager.removeSummaries() throws UnsupportedOperationException
Title: Message Title ikedam closed an issue as Fixed Jenkins / JENKINS-54184 manager.removeSummaries() throws UnsupportedOperationException Change By: ikedam Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54184) manager.removeSummaries() throws UnsupportedOperationException
Title: Message Title ikedam updated JENKINS-54184 Released 2.4.3 with this fix. It will be available in the update center in a day. Jenkins / JENKINS-54184 manager.removeSummaries() throws UnsupportedOperationException Change By: ikedam Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54184) manager.removeSummaries() throws UnsupportedOperationException
Title: Message Title ikedam updated JENKINS-54184 Jenkins / JENKINS-54184 manager.removeSummaries() throws UnsupportedOperationException Change By: ikedam Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54401) NPE when parsing scm git revision date on PR branches
Title: Message Title Joseph Petersen commented on JENKINS-54401 Re: NPE when parsing scm git revision date on PR branches Released as 2.2.15 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54401) NPE when parsing scm git revision date on PR branches
Title: Message Title Joseph Petersen updated JENKINS-54401 Jenkins / JENKINS-54401 NPE when parsing scm git revision date on PR branches Change By: Joseph Petersen Status: In Review Resolved Resolution: Fixed Released As: 2.2.15 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54578) Cannot delete last category
Title: Message Title Diego Agulló assigned an issue to Diego Agulló Jenkins / JENKINS-54578 Cannot delete last category Change By: Diego Agulló Assignee: Diego Agulló Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54578) Cannot delete last category
Title: Message Title Diego Agulló started work on JENKINS-54578 Change By: Diego Agulló Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-49707) Auto retry for elastic agents after channel closure
Title: Message Title
Amir Barkal edited a comment on JENKINS-49707
Re: Auto retry for elastic agents after channel closure
The problem is Jenkins not aborting / cancelling / stopping / whatever the build when the agent is terminated in the middle of a build.There's an infinite loop that's easy to reproduce:1. Start Jenkins slave with remoting jnlp and give it a label jar :{code}java -jar agent.jar -jnlpUrl "http://jenkins:8080/computer/agent1/slave-agent.jnlp" -secret 123{code}2. Run the following pipeline:{code}node('agent1') {sh('sleep 1') }{code}3. Kill the agent (Ctrl+C)4. Jenkins output in job console log:{code}Started by user adminReplayed #23Running as adminRunning in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on agent1-805fa9fd in /workspace/Pipeline-1[Pipeline] {[Pipeline] sh[Pipeline-1] Running shell script+ sleep 1Cannot contact agent-805fa9fd: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from 2163fbb04240.jenkins/172.20.0.3:43902 failed. The channel is closing down or has closed down{code} [^threadDump.txt] System info:Jenkins ver. 2.138Durable Task: 1.25What I would like is a way to configure a maximum timeout for the Jenkins master to wait for the agent to respond, and then just abort the build. It's absolutely unacceptable that builds will hang due to dead agents.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-49707) Auto retry for elastic agents after channel closure
Title: Message Title
Amir Barkal edited a comment on JENKINS-49707
Re: Auto retry for elastic agents after channel closure
The problem is Jenkins not aborting / cancelling / stopping / whatever the build when the agent is terminated in the middle of a build.There's an infinite loop that's easy to reproduce:1. Start Jenkins slave with remoting jnlp and give it a label:{code}java -jar agent.jar -jnlpUrl "http://jenkins:8080/computer/agent1/slave-agent.jnlp" -secret 123{code}2. Run the following pipeline:{code}node('agent1') {sh('sleep 1') }{code}3. Kill the agent (Ctrl+C)4. Jenkins output in job console log:{code}Started by user adminReplayed #23Running as adminRunning in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on agent1-805fa9fd in /workspace/Pipeline-1[Pipeline] {[Pipeline] sh[Pipeline-1] Running shell script+ sleep 1Cannot contact agent-805fa9fd: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from 2163fbb04240.jenkins/172.20.0.3:43902 failed. The channel is closing down or has closed down{code} [^threadDump.txt] System info:Jenkins ver. 2.138Durable Task: 1.25 What I would like is a way to configure a maximum timeout for the Jenkins master to wait for the agent to respond, and then just abort the build. It's absolutely unacceptable that builds will hang due to dead agents.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-49707) Auto retry for elastic agents after channel closure
Title: Message Title
Amir Barkal edited a comment on JENKINS-49707
Re: Auto retry for elastic agents after channel closure
The problem is Jenkins not aborting / cancelling / stopping / whatever the build when the agent is terminated in the middle of a build.There's an infinite loop that's easy to reproduce:1. Start Jenkins slave with remoting jnlp and give it a label:{code}java -jar agent.jar -jnlpUrl "http://jenkins:8080/computer/ jnlp1 agent1 /slave-agent.jnlp" -secret 123{code}2. Run the following pipeline:{code}node('agent1') {sh('sleep 1') }{code}3. Kill the agent (Ctrl+C)4. Jenkins output in job console log:{code}Started by user adminReplayed #23Running as adminRunning in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on agent1-805fa9fd in /workspace/Pipeline-1[Pipeline] {[Pipeline] sh[Pipeline-1] Running shell script+ sleep 1Cannot contact agent-805fa9fd: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from 2163fbb04240.jenkins/172.20.0.3:43902 failed. The channel is closing down or has closed down{code} [^threadDump.txt] System info:Jenkins ver. 2.138Durable Task: 1.25
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-49707) Auto retry for elastic agents after channel closure
Title: Message Title
Amir Barkal commented on JENKINS-49707
Re: Auto retry for elastic agents after channel closure
The problem is Jenkins not aborting / cancelling / stopping / whatever the build when the agent is terminated in the middle of a build. There's an infinite loop that's easy to reproduce: 1. Start Jenkins slave with remoting jnlp and give it a label:
java -jar agent.jar -jnlpUrl "http://jenkins:8080/computer/jnlp1/slave-agent.jnlp" -secret 123
2. Run the following pipeline:
node('agent1') {
sh('sleep 1')
}
3. Kill the agent (Ctrl+C) 4. Jenkins output in job console log:
Started by user admin
Replayed #23
Running as admin
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Running on agent1-805fa9fd in /workspace/Pipeline-1
[Pipeline] {
[Pipeline] sh
[Pipeline-1] Running shell script
+ sleep 1
Cannot contact agent-805fa9fd: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from 2163fbb04240.jenkins/172.20.0.3:43902 failed. The channel is closing down or has closed down
threadDump.txt System info: Jenkins ver. 2.138 Durable Task: 1.25
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-49707) Auto retry for elastic agents after channel closure
Title: Message Title Amir Barkal updated an issue Jenkins / JENKINS-49707 Auto retry for elastic agents after channel closure Change By: Amir Barkal Attachment: threadDump.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54630) Scan Organization Folder fails when a repository is deleted but configured to redirect
Title: Message Title Ahmed Elghazal commented on JENKINS-54630 Re: Scan Organization Folder fails when a repository is deleted but configured to redirect I updated the priority from blocker to minor since I contacted Bitbucket and they've deleted the repo was causing me the issue. I'm unblocked now though other users might be suffering... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54630) Scan Organization Folder fails when a repository is deleted but configured to redirect
Title: Message Title Ahmed Elghazal updated an issue Jenkins / JENKINS-54630 Scan Organization Folder fails when a repository is deleted but configured to redirect Change By: Ahmed Elghazal Priority: Blocker Minor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-41516) Groovy script console actions should be logged
Title: Message Title Paul Deauna updated JENKINS-41516 Jenkins / JENKINS-41516 Groovy script console actions should be logged Change By: Paul Deauna Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-41516) Groovy script console actions should be logged
Title: Message Title Paul Deauna started work on JENKINS-41516 Change By: Paul Deauna Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54630) Scan Organization Folder fails when a repository is deleted but configured to redirect
Title: Message Title
Diego Agulló updated an issue
Jenkins / JENKINS-54630
Scan Organization Folder fails when a repository is deleted but configured to redirect
Change By:
Diego Agulló
I have a reporsitory in my Bitbucket account that was deleted but it's configured to redirect to an other URL, hence not 100% deleted and can still be accessed through [https://bitbucket.org/geniousphp/soam]When I run my scan, it fails because of that and throw the error{code:java}ERROR: [Wed Nov 14 14:59:11 UTC 2018] Could not fetch sources from navigator com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator@2e752b5f java.io.FileNotFoundException: URL:https://api.bitbucket.org/2.0/repositories/geniousphp/soamat com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequestAsInputStream(BitbucketCloudApiClient.java:765) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:785) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRepository(BitbucketCloudApiClient.java:330) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.getRepositoryType(BitbucketSCMSource.java:504) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:548) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:374) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:328) at jenkins.branch.MultiBranchProjectFactory$BySCMSourceCriteria.recognizes(MultiBranchProjectFactory.java:263) at jenkins.branch.OrganizationFolder$SCMSourceObserverImpl$1.recognizes(OrganizationFolder.java:1346) at jenkins.branch.OrganizationFolder$SCMSourceObserverImpl$1.complete(OrganizationFolder.java:1361) at jenkins.scm.api.trait.SCMNavigatorRequest.process(SCMNavigatorRequest.java:256) at jenkins.scm.api.trait.SCMNavigatorRequest.process(SCMNavigatorRequest.java:206) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator.visitSources(BitbucketSCMNavigator.java:487) at jenkins.branch.OrganizationFolder.computeChildren(OrganizationFolder.java:458) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165) at jenkins.branch.OrganizationFolder$OrganizationScan.run(OrganizationFolder.java:910) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429){code} I think that this issue can be similar to Jenkins JENKINS -47900The thing is that I can't workaround this and hence it's definitely a blocker. I would love to delete completely that repo but it's not possible from Bitbucket UI, not API. The only way to remove it is by contacting Bitbucket ([https://confluence.atlassian.com/bitbucket/how-do-i-remove-a-redirect-url-i-supplied-when-i-deleted-my-repo-282173855.html)|https://confluence.atlassian.com/bitbucket/how-do-i-remove-a-redirect-url-i-supplied-when-i-deleted-my-repo-282173855.html]
[JIRA] (JENKINS-54683) Pods entering error state
Title: Message Title Rakesh Kande created an issue Jenkins / JENKINS-54683 Pods entering error state Issue Type: Bug Assignee: Carlos Sanchez Attachments: image-2018-11-17-13-52-36-103.png Components: kubernetes-plugin Created: 2018-11-17 19:52 Environment: production Priority: Blocker Reporter: Rakesh Kande Hi Carlos recently we upgraded the plugin to 1.13.5 and we have been observing the pods entering into error state and the builds that are running are getting killed. INFO: Protocol JNLP4-connect encountered an unexpected exception E undefined java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: jnlp-xf91v at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474) Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: jnlp-xf91v at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816)
[JIRA] (JENKINS-52282) JNLPLauncher: Update Java Web Start built-in Documentation and Wiki to reflect unavailability in Java 10+
Title: Message Title Mark Waite commented on JENKINS-52282 Re: JNLPLauncher: Update Java Web Start built-in Documentation and Wiki to reflect unavailability in Java 10+ Pull request PR-3766 submitted Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52282) JNLPLauncher: Update Java Web Start built-in Documentation and Wiki to reflect unavailability in Java 10+
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-52282 JNLPLauncher: Update Java Web Start built-in Documentation and Wiki to reflect unavailability in Java 10+ Change By: Mark Waite Comment: Refer to the [hide-java-web-start-on-jdk-11 branch|https://github.com/MarkEWaite/jenkins/commits/hide-java-web-start-on-jdk-11] for my work in progress. I believe the most recent commit is closest to a final implementation and the preceding commit should be discarded. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52282) JNLPLauncher: Update Java Web Start built-in Documentation and Wiki to reflect unavailability in Java 10+
Title: Message Title Mark Waite updated JENKINS-52282 Jenkins / JENKINS-52282 JNLPLauncher: Update Java Web Start built-in Documentation and Wiki to reflect unavailability in Java 10+ Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52013) Switch the Java 11 branch to common UC by default
Title: Message Title Oleg Nenashev updated JENKINS-52013 Jenkins / JENKINS-52013 Switch the Java 11 branch to common UC by default Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52013) Switch the Java 11 branch to common UC by default
Title: Message Title Oleg Nenashev commented on JENKINS-52013 Re: Switch the Java 11 branch to common UC by default https://github.com/jenkinsci/jenkins/pull/3765 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-51871) Java 11 Docker Image: Invalid Manifest format when loading Git Client Plugin 2.7.2, JDK 11ea+18 is required
Title: Message Title Oleg Nenashev updated JENKINS-51871 Jenkins / JENKINS-51871 Java 11 Docker Image: Invalid Manifest format when loading Git Client Plugin 2.7.2, JDK 11ea+18 is required Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52013) Switch the Java 11 branch to common UC by default
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-52013 Switch the Java 11 branch to common UC by default Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52013) Switch the Java 11 branch to common UC by default
Title: Message Title Oleg Nenashev started work on JENKINS-52013 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52408) Multiple jobs on same pipeline: java.io.NotSerializableException: org.jenkinsci.plugins.workflow.job.WorkflowJob
Title: Message Title Romain N commented on JENKINS-52408 Re: Multiple jobs on same pipeline: java.io.NotSerializableException: org.jenkinsci.plugins.workflow.job.WorkflowJob After many investigations, I used Jenkins.getInstance().getJobs() in a groovy file and this call is not Serializable. Added a @CPS annotation resolve this problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52408) Multiple jobs on same pipeline: java.io.NotSerializableException: org.jenkinsci.plugins.workflow.job.WorkflowJob
Title: Message Title Romain N closed an issue as Not A Defect Jenkins / JENKINS-52408 Multiple jobs on same pipeline: java.io.NotSerializableException: org.jenkinsci.plugins.workflow.job.WorkflowJob Change By: Romain N Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54255) xUnit sets build status incorrectly
Title: Message Title Nikolas Falco commented on JENKINS-54255 Re: xUnit sets build status incorrectly With my local test it works. With Failed Threashold setup to total 5 and new to 2 run 1 test count 5 all pass -> BUILD OK run 2 test count 8, 3 fails (3 new fails) -> BUILD FAILED (new threshold) run 2 test count 9, 4 fails (1 new fails) -> BUILD OK run 2 test count 11, 6 fails (2 new fails) -> BUILD FAILED (total threshold) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
