[JIRA] (JENKINS-58754) JIRA-JENKINS Integration | JsonException
Title: Message Title Selva G commented on JENKINS-58754 Re: JIRA-JENKINS Integration | JsonException Hello, I am facing the same problem with the version of 2.176.2. Any update pls ? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201057.1564657212000.396.1566878940187%40Atlassian.JIRA.
[JIRA] (JENKINS-59093) MultiBranch SVN raises: java.lang.ClassCastException: [[J cannot be cast to org.mapdb.BTreeMap$BNode
Title: Message Title Ryan Pisano created an issue Jenkins / JENKINS-59093 MultiBranch SVN raises: java.lang.ClassCastException: [[J cannot be cast to org.mapdb.BTreeMap$BNode Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin (not Pipeline), subversion-plugin Created: 2019-08-27 03:51 Environment: Latest docker image (2.191), SVN 1.8 Priority: Blocker Reporter: Ryan Pisano All of my SVN-based multi-branch pipelines are returning a java error, while my git are working successfully. If there's any other info that would be helpful please let me know! The error is as follows: ERROR: [Mon Aug 26 22:42:22 EST 2019] Could not fetch branches from source 5955653d-34d8-4612-a323-b463505b57d8 java.lang.ClassCastException: [[J cannot be cast to org.mapdb.BTreeMap$BNode at org.mapdb.BTreeMap.put2(BTreeMap.java:663) at org.mapdb.BTreeMap.put(BTreeMap.java:643) at org.mapdb.DB.catPut(DB.java:105) at org.mapdb.DB.createHashMap(DB.java:443) at org.mapdb.DB$HTreeMapMaker.make(DB.java:216) at org.mapdb.DB.getHashMap(DB.java:356) at org.mapdb.DB.getHashMap(DB.java:329) at jenkins.scm.impl.subversion.SVNRepositoryView.(SVNRepositoryView.java:115) at jenkins.scm.impl.subversion.SubversionSCMSource.openSession(SubversionSCMSource.java:338) at jenkins.scm.impl.subversion.SubversionSCMSource.retrieve(SubversionSCMSource.java:241) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:635) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at
[JIRA] (JENKINS-58231) Job build failed when one of domain in Active Directory unreachable
Title: Message Title Dennis Tran commented on JENKINS-58231 Re: Job build failed when one of domain in Active Directory unreachable I just facing this issues again. 14:15:16 FATAL: org.acegisecurity.AuthenticationServiceException: Failed to bind to LDAP server with the bind name/password; nested exception is javax.naming.CommunicationException: adv.aavn.local:3268 [Root exception is java.net.SocketTimeoutException: connect timed out]14:15:16java.net.SocketTimeoutException: connect timed out*14:15:16* at java.net.PlainSocketImpl.socketConnect(Native Method)14:15:16 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)14:15:16 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)14:15:16 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)14:15:16 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)14:15:16 at java.net.Socket.connect(Socket.java:589)14:15:16 at sun.reflect.GeneratedMethodAccessor20610.invoke(Unknown Source)14:15:16 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)14:15:16 at java.lang.reflect.Method.invoke(Method.java:498)14:15:16 at com.sun.jndi.ldap.Connection.createSocket(Connection.java:362)14:15:16 at com.sun.jndi.ldap.Connection.(Connection.java:215)14:15:16 Caused: javax.naming.CommunicationException: adv.aavn.local:3268 [Root exception is java.net.SocketTimeoutException: connect timed out]14:15:16 at com.sun.jndi.ldap.Connection.(Connection.java:228)14:15:16 at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137)14:15:16 at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1615)14:15:16 at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749)14:15:16 at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:319)14:15:16 at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192)14:15:16 at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:151)14:15:16 at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:668)14:15:16 at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:599)14:15:16 at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:357)14:15:16 Caused: org.acegisecurity.AuthenticationServiceException: Failed to bind to LDAP server with the bind name/password; nested exception is javax.naming.CommunicationException: adv.aavn.local:3268 [Root exception is java.net.SocketTimeoutException: connect timed out]14:15:16 at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:360)14:15:16 at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:340)14:15:16 at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767)14:15:16 at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568)14:15:16 at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350)14:15:16 at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313)14:15:16 at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228)14:15:16 at com.google.common.cache.LocalCache.get(LocalCache.java:3965)14:15:16 at
[JIRA] (JENKINS-51178) NullPointer while resolving already deployed apps
Title: Message Title Taha Latief edited a comment on JENKINS-51178 Re: NullPointer while resolving already deployed apps I am facing a similar issue even though i am using websphere-deployer-plugin version 1.6.1 plugin. Can you help by pointing out what i might be doing wrong ? [~hidminds] 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190486.152569328.389.1566872040134%40Atlassian.JIRA.
[JIRA] (JENKINS-51178) NullPointer while resolving already deployed apps
Title: Message Title Taha Latief commented on JENKINS-51178 Re: NullPointer while resolving already deployed apps I am facing a similar issue even though i am using websphere-deployer-plugin version 1.6.1 plugin. Can you help ? Daniel Fischer 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190486.152569328.387.1566871680096%40Atlassian.JIRA.
[JIRA] (JENKINS-57966) Multibranch Pipeline Indexing fails with ClassCastException in svn
Title: Message Title Ryan Pisano commented on JENKINS-57966 Re: Multibranch Pipeline Indexing fails with ClassCastException in svn Did you ever find a fix for this? Most (all but one) of my multibranch pipelines are failing with this error now, but I can't pinpoint what is different. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199949.1560271375000.385.1566871560146%40Atlassian.JIRA.
[JIRA] (JENKINS-43925) Personal credential management
Title: Message Title Danny Seymour commented on JENKINS-43925 Re: Personal credential management I'm running into a scenario that I believe fairly closely aligns with this bug. I need to be able to change the user account that a pipelines credentials are associated with. I do not want to change the value on the pipeline itself because I'm looking at needing to be able to update the credentials for possibly hundreds of pipelines at a time and don't want to have to manually do that (sadly, due to operational requirements, automating pipeline creation using something like Job DSL isn't really an option). I figure the only thing that's stopping me from getting to a point where I can fully codify credential management in Jenkins is this issue and https://issues.jenkins-ci.org/browse/JENKINS-59067. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181453.1493346656000.382.1566865620625%40Atlassian.JIRA.
[JIRA] (JENKINS-59092) Blue Ocean does not allow us to list Bitbucket repositories
Title: Message Title Marcello Ribeiro updated an issue Jenkins / JENKINS-59092 Blue Ocean does not allow us to list Bitbucket repositories Change By: Marcello Ribeiro Attachment: The last commit.png 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201512.1566860104000.370.1566864960174%40Atlassian.JIRA.
[JIRA] (JENKINS-59092) Blue Ocean does not allow us to list Bitbucket repositories
Title: Message Title Marcello Ribeiro updated an issue Jenkins / JENKINS-59092 Blue Ocean does not allow us to list Bitbucket repositories Change By: Marcello Ribeiro Attachment: Eternal Loading.png 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201512.1566860104000.367.1566864540067%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Jesse Glick commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Assuming workflow-job #137 passes, anyone affected should please try upgrading to the build which should be linked from the “incrementals” status. Purely speculative, but in the absence of any known steps to reproduce that is the best we can do. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.343.1566860520211%40Atlassian.JIRA.
[JIRA] (JENKINS-59092) Blue Ocean does not allow us to list Bitbucket repositories
Title: Message Title Marcello Ribeiro created an issue Jenkins / JENKINS-59092 Blue Ocean does not allow us to list Bitbucket repositories Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-08-26 22:55 Priority: Major Reporter: Marcello Ribeiro Blue Ocean does not allow us to list Bitbucket repositories: Caused by: io.jenkins.blueocean.commons.ServiceException: Unknown Status Code at io.jenkins.blueocean.blueocean_bitbucket_pipeline.HttpResponse.getContent(HttpResponse.java:71) at io.jenkins.blueocean.blueocean_bitbucket_pipeline.cloud.BitbucketCloudApi.getDefaultBranch(BitbucketCloudApi.java:249) at io.jenkins.blueocean.blueocean_bitbucket_pipeline.model.BbRepo.toScmRepository(BbRepo.java:63) at io.jenkins.blueocean.blueocean_bitbucket_pipeline.BitbucketRepositoryContainer$BitbucketRepositories.(BitbucketRepositoryContainer.java:82) at io.jenkins.blueocean.blueocean_bitbucket_pipeline.BitbucketRepositoryContainer.getRepositories(BitbucketRepositoryContainer.java:41) at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:72) ... 120 more Add Comment
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Jesse Glick commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever I do not get what you mean nothing problematic in the screenshot. Sorry, I meant nothing problematic other than the new build waiting, which is probably just due to the incorrect return value from isLogUpdated mentioned to begin with. Everything else looks normal enough. each build was kicking off downstream jobs A plausible lead, though apparently not the explanation for Roy Arnon. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.334.1566859870299%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Jesse Glick commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever I do not get what you mean nothing problematic in the screenshot. Sorry, I meant nothing problematic other than the new build waiting, which is probably just due to the incorrect return value from isLogUpdated mentioned to begin with. Everything else looks normal enough. each build was kicking off downstream jobs A plausible lead, though apparently not the explanation for Roy Arnon. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.339.1566859920033%40Atlassian.JIRA.
[JIRA] (JENKINS-58534) Impossible to access promotion's console output (navigation is broken from links and breadcrumbs)
Title: Message Title Tammy Osborn commented on JENKINS-58534 Re: Impossible to access promotion's console output (navigation is broken from links and breadcrumbs) I see the same thing. And like slav dok, once I downgraded to Promoted Builds version 3.2, navigation was 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200683.1563381278000.326.1566859620307%40Atlassian.JIRA.
[JIRA] (JENKINS-56036) Spot Instance Plugin Spawns Arbitrary Number of Instances
Title: Message Title Shubham Dhoka commented on JENKINS-56036 Re: Spot Instance Plugin Spawns Arbitrary Number of Instances I have seen this issue with on-demand instances as well. I'm using version 1.42 of the plugin 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197456.1549566996000.306.1566857760315%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: stuck-build-2.tar.gz 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.288.1566856206445%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever I went ahead and reproduced it again. This time I simulated a failure in the pipeline job - you can see build #1916 waiting for the failed build #1915. I have attached the builds folder again - stuck-build-2.tar.gz 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.289.1566856207285%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: stuck-build.tar.gz 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.283.1566856020304%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: failed.PNG 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.278.1566855900249%40Atlassian.JIRA.
[JIRA] (JENKINS-59091) Unable to get SAML 2.0 Plugin on Jenkins deployed on WebLogic
Title: Message Title Ivan Fernandez Calvo closed an issue as Not A Defect Jenkins / JENKINS-59091 Unable to get SAML 2.0 Plugin on Jenkins deployed on WebLogic Change By: Ivan Fernandez Calvo 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201511.1566847921000.273.1566855660271%40Atlassian.JIRA.
[JIRA] (JENKINS-58257) New secrets written to kubernetes store are not always loaded by Jenkins
Title: Message Title Kyle Cronin edited a comment on JENKINS-58257 Re: New secrets written to kubernetes store are not always loaded by Jenkins We have experienced this as well. Most likely the issue is the watch task closes due to some error like:```2019-08-25 06:20:05.874+ [id=43] INFO c.c.j.p.k.KubernetesCredentialProvider#onClose: onClose.io.fabric8.kubernetes.client.KubernetesClientException: too old resource version: 130846525 (135483452) at io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager$1.onMessage(WatchConnectionManager.java:254) at okhttp3.internal.ws.RealWebSocket.onReadMessage(RealWebSocket.java:323) at okhttp3.internal.ws.WebSocketReader.readMessageFrame(WebSocketReader.java:219) at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:105) at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:274) at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:214) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:206) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)``` The plugin does not attempt to recover from a closed watch connection. I've submitted a PR to restart the watcher if the onClose method is called with a client exception.https://github.com/jenkinsci/kubernetes-credentials-provider-plugin/pull/31 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200321.1561744491000.269.1566855600237%40Atlassian.JIRA.
[JIRA] (JENKINS-59091) Unable to get SAML 2.0 Plugin on Jenkins deployed on WebLogic
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-59091 Re: Unable to get SAML 2.0 Plugin on Jenkins deployed on WebLogic weblogic provide a OpenSAML library bundle that it is not compatible with the version used by the plugin, it is not a bug https://stackoverflow.com/questions/25061918/spring-saml-on-weblogic-12c 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201511.1566847921000.271.1566855600259%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Oleg Kalugin commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Hey, I can confirm experiencing the same problem of builds stuck in "already in progress" condition. I had to delete the previous build for it to move on every time. Unfortunately I didn't grab any logs or screenshots before downgrading because I had a bunch of work dependent on this, so my main concern was trying to get it fixed. The common traits with the builds that I noticed were: All of them were multibranch pipeline jobs Concurrent builds were disabled And this one seemed the most outstanding (pure speculation on my part) - each build was kicking off downstream jobs that are defined though properties.pipelineTriggers.upstream.upstreamProjects in those downstream projects 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.263.1566855300471%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever I do not get what you mean nothing problematic in the screenshot. This jenkins instance is still stuck forever on this build. I have tried restarting it and it reproduces again after completing one build. Is that not enough of a reproduction? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.261.1566855300411%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: Capture2.PNG 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.257.1566855180298%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Jesse Glick commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Unfortunately I see nothing problematic in the screenshot or either of the attachments, so unless you have a known way to reproduce the problem from scratch I doubt this is going anywhere. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.251.1566852660405%40Atlassian.JIRA.
[JIRA] (JENKINS-58010) nexus-jenkins-plugin.jpi.tmp does not match expected SHA-1
Title: Message Title Justin Young commented on JENKINS-58010 Re: nexus-jenkins-plugin.jpi.tmp does not match expected SHA-1 Hello, thanks for raising the issue. We (Sonatype) track issues via the following Jira: https://issues.sonatype.org/projects/NEXUS. Could you open this ticket there? Cheers. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200027.1560435517000.248.1566852360281%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon edited a comment on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Hi,I've uploaded a build that is stuck and an image of the state in jenkins. The build I uploaded is build #1913 - I aborted it (the process it was testing was just taking too much time, some misconfiguration probably), but jenkins still does not allow next builds to start - [^stuck-build.tar.gz]I'v also attached a thread dump - [^tdump]After a restart, these "stuck" builds immediately start. The jenkins logs do not seem to contain anything relevant. Regarding durability settings - this job is using the default (PERFORMANCE) but I've seen this issue on jobs that are set to DURABILITY as well. Let me know if you need anything else.!Capture.PNG|thumbnail! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.245.1566850980379%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon edited a comment on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Hi,I've uploaded a build that is stuck and an image of the state in jenkins. The build I uploaded is build #1913 - I aborted it (the process it was testing was just taking too much time, some misconfiguration probably), but jenkins still does not allow next builds to start - [^stuck-build.tar.gz]I'v also attached a thread dump - [^tdump]After a restart, these "stuck" builds immediately start. The jenkins logs do not seem to contain anything relevant.Let me know if you need anything else. [^stuck-build !Capture . tar.gz] PNG|thumbnail! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.238.1566850680807%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Hi, I've uploaded a build that is stuck and an image of the state in jenkins. The build I uploaded is build #1913 - I aborted it (the process it was testing was just taking too much time, some misconfiguration probably), but jenkins still does not allow next builds to start - stuck-build.tar.gz I'v also attached a thread dump - tdump After a restart, these "stuck" builds immediately start. The jenkins logs do not seem to contain anything relevant. Let me know if you need anything else. stuck-build.tar.gz 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.234.1566850680746%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: tdump 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.233.1566850680731%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: Capture.PNG 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.229.1566850440596%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: stuck-build.tar.gz 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.225.1566850380805%40Atlassian.JIRA.
[JIRA] (JENKINS-58768) Mailer doesn't authenticate properly with Gmail
Title: Message Title Daniel Beck updated JENKINS-58768 Jenkins / JENKINS-58768 Mailer doesn't authenticate properly with Gmail Change By: Daniel Beck 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201073.1564671799000.210.1566848703273%40Atlassian.JIRA.
[JIRA] (JENKINS-58768) Mailer doesn't authenticate properly with Gmail
Title: Message Title Daniel Beck started work on JENKINS-58768 Change By: Daniel Beck 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201073.1564671799000.202.1566848702922%40Atlassian.JIRA.
[JIRA] (JENKINS-58837) withDockerRegistry on multiple clusters
Title: Message Title Paul Clark commented on JENKINS-58837 Re: withDockerRegistry on multiple clusters Workaround: Command line docket logins, do the image mirror and then Docker logouts Post pipeline always to empty out the docker config.json. Not the best as any other pipelines running at the same time for cluster promotions on that node would have issues 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201152.1565148699000.217.1566848703479%40Atlassian.JIRA.
[JIRA] (JENKINS-58768) Mailer doesn't authenticate properly with Gmail
Title: Message Title Daniel Beck commented on JENKINS-58768 Re: Mailer doesn't authenticate properly with Gmail Only affects the "test email" feature, this code path isn't used for real emails. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201073.1564671799000.195.1566848640247%40Atlassian.JIRA.
[JIRA] (JENKINS-58768) Mailer doesn't authenticate properly with Gmail
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-58768 Mailer doesn't authenticate properly with Gmail Change By: Daniel Beck Labels: mailer plugin regression 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201073.1564671799000.188.1566848520328%40Atlassian.JIRA.
[JIRA] (JENKINS-46588) Pipeline Branch Specifier "blank for 'any'" fails
Title: Message Title Jorge Sivil commented on JENKINS-46588 Re: Pipeline Branch Specifier "blank for 'any'" fails I had the same problem, but for this you have to use another type of project "Multibranch Pipeline" instead of "Pipeline" 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184913.1504266201000.181.1566848100185%40Atlassian.JIRA.
[JIRA] (JENKINS-42509) authenticated team members should have read/build permissions when using Github Committer Authorization Strategy
Title: Message Title Sam Gleske closed an issue as Duplicate Closing again since this a duplicate. Please contribute in JENKINS-27844 which should track any rewriting of this feature. The GitHub authorization strategy needs to be redesigned completely. Jenkins / JENKINS-42509 authenticated team members should have read/build permissions when using Github Committer Authorization Strategy Change By: Sam Gleske Status: Reopened Closed Resolution: Duplicate 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179436.1488821196000.174.1566848041152%40Atlassian.JIRA.
[JIRA] (JENKINS-59091) Unable to get SAML 2.0 Plugin on Jenkins deployed on WebLogic
Title: Message Title SRINIVASAN RAMAMURTHY created an issue Jenkins / JENKINS-59091 Unable to get SAML 2.0 Plugin on Jenkins deployed on WebLogic Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: saml-plugin Created: 2019-08-26 19:32 Environment: QA Priority: Major Reporter: SRINIVASAN RAMAMURTHY Hi, I have installed Jenkins ver. 2.176.2 war as an application within my WebLogic Server (12.2.1.3). It's working as expected for all my other needs. I want to integrate with ADFS using SAML 2.0 and that's where I am running into issues. I have downloaded and installed the SAML Plugin (v 1.1.2). When I enable the SAML checkbox and enter the IDP Metadata Content or IDP MetaData URL and click on "Validate IDP MetaData" I get error message as shown below. Appreciate your help in this regards. Thanks java.lang.ClassCastException: org.opensaml.saml2.core.impl.ActionBuilder cannot be cast to org.opensaml.core.xml.XMLObjectBuilderjava.lang.ClassCastException: org.opensaml.saml2.core.impl.ActionBuilder cannot be cast to org.opensaml.core.xml.XMLObjectBuilder at org.opensaml.core.xml.config.XMLConfigurator.initializeObjectProviders(XMLConfigurator.java:238) at org.opensaml.core.xml.config.XMLConfigurator.load(XMLConfigurator.java:203) at org.opensaml.core.xml.config.XMLConfigurator.load(XMLConfigurator.java:188) at org.opensaml.core.xml.config.XMLConfigurator.load(XMLConfigurator.java:162) at org.opensaml.core.xml.config.AbstractXMLObjectProviderInitializer.init(AbstractXMLObjectProviderInitializer.java:52) at org.opensaml.core.config.InitializationService.initialize(InitializationService.java:56) at org.jenkinsci.plugins.saml.OpenSAMLWrapper.get(OpenSAMLWrapper.java:63) at
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title Matt Sicker resolved as Fixed This was implemented in JENKINS-58170, though it requires the use of credentials build parameters. Alternatively, you can use authorize-project to automate the user who is bound to the build to access their credentials. Jenkins / JENKINS-38963 User-scoped credentials cannot be looked up in pipeline Change By: Matt Sicker Status: Open Resolved 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175380.1476360951000.142.1566847921920%40Atlassian.JIRA.
[JIRA] (JENKINS-44773) User Scoped credentials are not used by the "git" pipeline step
Title: Message Title Matt Sicker resolved as Won't Fix There is now a new way to access user-scoped credentials detailed in JENKINS-58170 which uses credentials build parameters. These allow user-scoped credentials to be referenced in any context where you'd normally use the credentials id. Jenkins / JENKINS-44773 User Scoped credentials are not used by the "git" pipeline step Change By: Matt Sicker Status: Open Resolved Resolution: Won't Fix 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182828.1496921048000.130.1566847861057%40Atlassian.JIRA.
[JIRA] (JENKINS-44774) User Scoped credentials don't appear in credentials drop down lists
Title: Message Title Matt Sicker updated JENKINS-44774 Jenkins / JENKINS-44774 User Scoped credentials don't appear in credentials drop down lists Change By: Matt Sicker Status: In Review Fixed but Unreleased Resolution: Won't Fix 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182829.1496921337000.116.1566847743765%40Atlassian.JIRA.
[JIRA] (JENKINS-44774) User Scoped credentials don't appear in credentials drop down lists
Title: Message Title Matt Sicker updated JENKINS-44774 Jenkins / JENKINS-44774 User Scoped credentials don't appear in credentials drop down lists Change By: Matt Sicker 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182829.1496921337000.118.1566847743787%40Atlassian.JIRA.
[JIRA] (JENKINS-44774) User Scoped credentials don't appear in credentials drop down lists
Title: Message Title Matt Sicker resolved as Won't Fix This feature is implemented by JENKINS-58170 using a slightly different approach to that described in this ticket. The linked approach works using credentials build parameters which allows for using user-scoped credentials. Jenkins / JENKINS-44774 User Scoped credentials don't appear in credentials drop down lists Change By: Matt Sicker Status: Open Resolved Resolution: Won't Fix 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182829.1496921337000.92.1566847743484%40Atlassian.JIRA.
[JIRA] (JENKINS-44774) User Scoped credentials don't appear in credentials drop down lists
Title: Message Title Matt Sicker updated JENKINS-44774 Jenkins / JENKINS-44774 User Scoped credentials don't appear in credentials drop down lists Change By: Matt Sicker Resolution: Won't Fix Status: Resolved In 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182829.1496921337000.104.1566847743631%40Atlassian.JIRA.
[JIRA] (JENKINS-47864) Allow to select User Scope Credentials
Title: Message Title Matt Sicker resolved as Won't Fix You can now specify a credentials parameter to a build which can be used as the credentials id for using user-scoped credentials. See JENKINS-58170. Jenkins / JENKINS-47864 Allow to select User Scope Credentials Change By: Matt Sicker Status: Open Resolved Resolution: Won't Fix 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186376.1510067866000.79.1566847620409%40Atlassian.JIRA.
[JIRA] (JENKINS-47864) Allow to select User Scope Credentials
Title: Message Title Matt Sicker commented on JENKINS-47864 Re: Allow to select User Scope Credentials This should be addressed via JENKINS-58170. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186376.1510067866000.75.1566847560845%40Atlassian.JIRA.
[JIRA] (JENKINS-44774) User Scoped credentials don't appear in credentials drop down lists
Title: Message Title Matt Sicker commented on JENKINS-44774 Re: User Scoped credentials don't appear in credentials drop down lists This can be implemented via JENKINS-58170. It's already supported by build parameters, and we'll have full support for the same as an input step as well once that's released in JENKINS-47699. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182829.1496921337000.72.1566847560795%40Atlassian.JIRA.
[JIRA] (JENKINS-44773) User Scoped credentials are not used by the "git" pipeline step
Title: Message Title Matt Sicker commented on JENKINS-44773 Re: User Scoped credentials are not used by the "git" pipeline step This feature can be replaced by JENKINS-58170 which provides a more standardized approach to granting user-scoped credentials to builds. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182828.1496921048000.50.1566847440380%40Atlassian.JIRA.
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title Matt Sicker commented on JENKINS-38963 Re: User-scoped credentials cannot be looked up in pipeline This feature is improved in JENKINS-58170 and will also be supported by an upcoming release of pipeline-input-step to support user-scoped credentials prompted via an input step. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175380.1476360951000.21.1566847380725%40Atlassian.JIRA.
[JIRA] (JENKINS-58170) Allow credential parameters to shadow credential ids in lookup
Title: Message Title Matt Sicker updated JENKINS-58170 Credentials 2.3.0 is now released. Jenkins / JENKINS-58170 Allow credential parameters to shadow credential ids in lookup Change By: Matt Sicker Status: Fixed but Unreleased Resolved Released As: credentials-2.3.0 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200221.1561401761000.19.1566847200480%40Atlassian.JIRA.
[JIRA] (JENKINS-58170) Allow credential parameters to shadow credential ids in lookup
Title: Message Title Matt Sicker updated JENKINS-58170 Merged to master. Will be released in 2.3.0. Jenkins / JENKINS-58170 Allow credential parameters to shadow credential ids in lookup Change By: Matt Sicker Status: In Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200221.1561401761000.15.1566846720502%40Atlassian.JIRA.
[JIRA] (JENKINS-59078) jenkins Malformed POM Unknown attribute 'child.scm.url.inherit.append.path' for tag 'scm'
Title: Message Title Jason Pyeron commented on JENKINS-59078 Re: jenkins Malformed POM Unknown attribute 'child.scm.url.inherit.append.path' for tag 'scm' seems to be slightly relevant 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201460.1566802604000.7.1566845580071%40Atlassian.JIRA.
[JIRA] (JENKINS-59068) SSL connection reset during deploy
Title: Message Title Radek Antoniuk closed an issue as Not A Defect It turns out that Tomcat didn't have enough write permissions to the /webapps folder to overwrite the previous WAR file. Jenkins / JENKINS-59068 SSL connection reset during deploy Change By: Radek Antoniuk 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201450.1566656778000.6.1566845520378%40Atlassian.JIRA.
[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing
Title: Message Title Sandeep Yadav created an issue Jenkins / JENKINS-59090 Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing Issue Type: Bug Assignee: Maria Narcisa Galan Attachments: PeopleSoft_Test_Jenkins_Build_285.txt Components: hp-application-automation-tools-plugin Created: 2019-08-26 18:44 Labels: UFT MicroFocus ALM HPAutomationToolsPlugin hpuft Priority: Critical Reporter: Sandeep Yadav We are executing the UFT scripts from ALM using the Micro Focus Jenkins plugin and this plugin is marking the build as FAILURE even when the scripts are all passed in ALM. There is no pattern to this and we are consistently seeing this. Please see the attached log Add Comment
[JIRA] (JENKINS-58936) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jell
Title: Message Title balaji vajjala updated an issue Jenkins / JENKINS-58936 javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jelly:46:53: Change By: balaji vajjala Environment: Jenkins 2.189-1 jenkins 2.190-1 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201280.1565796626000.10165.1566844560062%40Atlassian.JIRA.
[JIRA] (JENKINS-58936) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jell
Title: Message Title balaji vajjala updated an issue Jenkins / JENKINS-58936 javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jelly:46:53: Change By: balaji vajjala Component/s: core Component/s: jenkinswalldisplay 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201280.1565796626000.10164.1566844500236%40Atlassian.JIRA.
[JIRA] (JENKINS-59068) SSL connection reset during deploy
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-59068
SSL connection reset during deploy
Change By:
Radek Antoniuk
Comment:
It gets even weirder, when I change the DSL to:{noformat} deploy adapters: [tomcat8(credentialsId: 'tomcat-dev', path: '/', url: "https://localhost:8080/manager/text" )], onFailure: false, war: 'target/ROOT.war' {noformat}it is trying to access wrong URL of the manager:{noformat}Caused by: org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: The Tomcat Manager responded "FAIL - Unknown command [/test/list] {noformat}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201450.1566656778000.10156.1566844200068%40Atlassian.JIRA.
[JIRA] (JENKINS-59068) SSL connection reset during deploy
Title: Message Title Radek Antoniuk commented on JENKINS-59068 Re: SSL connection reset during deploy It gets even weirder, when I change the DSL to: deploy adapters: [tomcat8(credentialsId: 'tomcat-dev', path: '/', url: "https://localhost:8080/manager/text" )], onFailure: false, war: 'target/ROOT.war' it is trying to access wrong URL of the manager: Caused by: org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: The Tomcat Manager responded "FAIL - Unknown command [/test/list] 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201450.1566656778000.10155.1566844020226%40Atlassian.JIRA.
[JIRA] (JENKINS-59078) jenkins Malformed POM Unknown attribute 'child.scm.url.inherit.append.path' for tag 'scm'
Title: Message Title Jason Pyeron commented on JENKINS-59078 Re: jenkins Malformed POM Unknown attribute 'child.scm.url.inherit.append.path' for tag 'scm' I gave a small effort to patch https://github.com/jenkinsci/maven-plugin , but I hit a brick wall on trying to update the maven-core to 3.6.x maven barf on 3.6.0 [INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (display-info) @ maven-plugin --- [INFO] Adding ignore: module-info [INFO] Ignoring requireUpperBoundDeps in com.google.guava:guava [INFO] Ignoring requireUpperBoundDeps in com.google.code.findbugs:jsr305 [WARNING] Rule 4: org.apache.maven.plugins.enforcer.RequireUpperBoundDeps failed with message: Failed while enforcing RequireUpperBoundDeps. The error(s) are [ Require upper bound dependencies error for org.codehaus.plexus:plexus-utils:3.1.0 paths to dependency are: +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven-interceptor:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven3-agent:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven35-agent:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven31-interceptor:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven32-interceptor:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven33-interceptor:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven35-interceptor:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven3-interceptor-commons:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven:maven-core:3.6.1 +-org.codehaus.plexus:plexus-utils:3.2.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven:maven-compat:3.6.1 +-org.codehaus.plexus:plexus-utils:3.2.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven:maven-repository-metadata:3.6.1 +-org.codehaus.plexus:plexus-utils:3.2.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven:maven-resolver-provider:3.6.1 +-org.codehaus.plexus:plexus-utils:3.2.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven:maven-embedder:3.6.1 +-org.codehaus.plexus:plexus-utils:3.2.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.eclipse.sisu:org.eclipse.sisu.plexus:0.3.3 +-org.codehaus.plexus:plexus-utils:3.0.17 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven.wagon:wagon-http:3.3.2 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven.wagon:wagon-file:3.3.2 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven.wagon:wagon-ssh:3.3.2
[JIRA] (JENKINS-55689) Not able to connect to jenkins master from windows slave
Title: Message Title Punith Shetty reopened an issue Jenkins / JENKINS-55689 Not able to connect to jenkins master from windows slave Change By: Punith Shetty Resolution: Not A Defect Status: Closed Reopened 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196875.1547848244000.10142.1566841380969%40Atlassian.JIRA.
[JIRA] (JENKINS-55689) Not able to connect to jenkins master from windows slave
Title: Message Title Punith Shetty commented on JENKINS-55689 Re: Not able to connect to jenkins master from windows slave Hi, Is there a resolution for this issue ? I am seeing the same error for my servers INFO: Setting up agent: windows_agent Aug 26, 2019 1:10:22 PM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode. Aug 26, 2019 1:10:22 PM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3.25 Aug 26, 2019 1:10:22 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using F:\win_jenkins\remoting as a remoting work directory Aug 26, 2019 1:10:22 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among https://myserver/ Aug 26, 2019 1:10:22 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping, Diagnostic-Ping, OperationsCenter2] Aug 26, 2019 1:10:23 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver isPortVisible WARNING: Connection refused: connect Aug 26, 2019 1:10:23 PM hudson.remoting.jnlp.Main$CuiListener error SEVERE: https://myserver/ provided port:46080 is not reachable java.io.IOException: https://myserver/ provided port:46080 is not reachable at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:286) at hudson.remoting.Engine.innerRun(Engine.java:523) at hudson.remoting.Engine.run(Engine.java:474) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196875.1547848244000.10139.1566841380926%40Atlassian.JIRA.
[JIRA] (JENKINS-46631) [JDK9] Illegal reflective access from slave.jar (Windows)
Title: Message Title Mark Waite commented on JENKINS-46631 Re: [JDK9] Illegal reflective access from slave.jar (Windows) Please don't use closed bug reports to ask additional questions P4. The users mailing list will generally provide better results than asking a question on a closed bug report. In this specific case, the message is a warning. There is no active project to remove those warnings. It may be a part of Hacktoberfest 2019 just as it was part of Hacktoberfest 2018. You're welcome to begin submitting pull requests to resolve those messages. This type of problem was mentioned in the "Running Jenkins with Java 9 & 10" blog post and in the Hacktoberfest 2018 announcement. Some of the places that may need to be addressed are listed in GitHub. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184965.1504533705000.10132.1566840720624%40Atlassian.JIRA.
[JIRA] (JENKINS-46631) [JDK9] Illegal reflective access from slave.jar (Windows)
Title: Message Title Mark Waite edited a comment on JENKINS-46631 Re: [JDK9] Illegal reflective access from slave.jar (Windows) Please don't use closed bug reports to ask additional questions [~remik]. The users mailing list will generally provide better results than asking a question on a closed bug report.In this specific case, the message is a warning. There is no active project to remove those warnings. It may be a part of Hacktoberfest 2019 just as it was part of Hacktoberfest 2018. You're welcome to begin submitting pull requests to resolve those messages. This type of problem was mentioned in the "[Running Jenkins with Java 9 & 10|https://jenkins.io/blog/2018/06/17/running-jenkins-with-java10-11/#known-issues]" blog post and in the [Hacktoberfest 2018 announcement|https://jenkins.io/blog/2018/10/01/hacktoberfest/]. Some of the places that may need to be addressed are [listed in GitHub|https://github.com/search?q=org%3Ajenkinsci+setAccessible%28true%29+path%3A%22src%2Fmain%22=Code]. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184965.1504533705000.10133.1566840720646%40Atlassian.JIRA.
[JIRA] (JENKINS-46724) [JDK9] Illegal reflective access from remoting
Title: Message Title Mark Waite commented on JENKINS-46724 Re: [JDK9] Illegal reflective access from remoting Please don't use closed bug reports to ask additional questions P4. The users mailing list will generally provide better results than asking a question on a closed bug report. In this specific case, the message is a warning. There is no active project to remove those warnings. It may be a part of Hacktoberfest 2019 just as it was part of Hacktoberfest 2018. You're welcome to begin submitting pull requests to resolve those messages. This type of problem was mentioned in the "Running Jenkins with Java 9 & 10" blog post and in the Hacktoberfest 2018 announcement. Some of the places that may need to be addressed are listed in GitHub. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185070.1504797804000.10125.1566840600647%40Atlassian.JIRA.
[JIRA] (JENKINS-57616) Security Requester Whitelist Plugin cannot be exported to JCasC
Title: Message Title rsandell updated JENKINS-57616 Jenkins / JENKINS-57616 Security Requester Whitelist Plugin cannot be exported to JCasC Change By: rsandell 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199544.1558540149000.10123.1566838800225%40Atlassian.JIRA.
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Anda Sorina Laakso commented on JENKINS-56750 Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. Hi Jim, Let me know if i understud correctly the case since i just received this ticket. You have 3 sets of tests, and in each set there is a test case which is run on 9 different machines. The problem is that the test summary shows only the test from the last set 27th times. Is that right? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198392.1553542192000.10121.1566838680407%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker commented on JENKINS-56217 Re: allow to hide version number New PR: https://github.com/jenkinsci/extended-security-settings-plugin/pull/9 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.10110.1566838380584%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker updated JENKINS-56217 Jenkins / JENKINS-56217 allow to hide version number Change By: Matt Sicker 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.10108.1566838380561%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker commented on JENKINS-56217 Re: allow to hide version number After discussion with some colleagues, we've decided that adding a servlet filter to ESS would work well enough to implement this feature as requested even though it can't remove the version number from other places. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.10098.1566838200166%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker started work on JENKINS-56217 Change By: Matt Sicker 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.10090.1566838140552%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-56217 allow to hide version number Change By: Matt Sicker Component/s: core 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.10092.1566838140579%40Atlassian.JIRA.
[JIRA] (JENKINS-59089) Control for logging level in the /var/log/jenkins/jenkins.log file
Title: Message Title MICHAEL LUPO created an issue Jenkins / JENKINS-59089 Control for logging level in the /var/log/jenkins/jenkins.log file Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger-plugin Created: 2019-08-26 16:36 Priority: Minor Reporter: MICHAEL LUPO Currently, I have a jenkins instance where the /var/log/jenkins/jenkins.log file is getting filled with WARNING: The Gerrit incoming events queue contains 67 items! Something might be stuck, or your system can't process the commands fast enough. Try to increase the number of receiving worker threads. Current thread-pool size: 3 I would like to be able to configure gerrit-trigger log levels via the plugin settings. Add Comment
[JIRA] (JENKINS-46724) [JDK9] Illegal reflective access from remoting
Title: Message Title P4 commented on JENKINS-46724 Re: [JDK9] Illegal reflective access from remoting Hi. I probably reported to the wrong issue (JENKINS-46631) but this is happening on our environment right now. Any plans for fixation? Jenkins master: Windows Server 2012 R2; JDK 1.8.0_172-b11; Jenkins v2.176.2. Jenkins slave: Ubuntu 19.04 LTS; openjdk-11-jdk 11.0.4+11-post-Ubuntu-1ubuntu219.04 Node log: ... [08/26/19 16:06:45] [SSH] Checking java version of java [08/26/19 16:06:45] [SSH] java -version returned 11.0.4. [08/26/19 16:06:45] [SSH] Starting sftp client. [08/26/19 16:06:45] [SSH] Copying latest remoting.jar... [08/26/19 16:06:45] [SSH] Copied 789,283 bytes. Expanded the channel window size to 4MB [08/26/19 16:06:45] [SSH] Starting agent process: cd "/home/jenkins/jenkins" && java -jar remoting.jar -workDir /home/jenkins/jenkins Aug 26, 2019 4:06:46 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /home/jenkins/jenkins/remoting as a remoting work directory Both error and output logs will be printed to /home/jenkins/jenkins/remoting <===[JENKINS REMOTING CAPACITY]===>channel started Remoting version: 3.29 This is a Unix agent WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by jenkins.slaves.StandardOutputSwapper$ChannelSwapper to constructor java.io.FileDescriptor(int) WARNING: Please consider reporting this to the maintainers of jenkins.slaves.StandardOutputSwapper$ChannelSwapper WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Evacuated stdout Aug 26, 2019 4:06:52 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ [StartupTrigger] - Scanning jobs for node node-linux Agent successfully connected and online Add Comment
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Jim Sears edited a comment on JENKINS-56750 Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. Hi [~gront], it has been over 2 months since the last comment on this issue.May I have an update? Did you get Bogdan's help as you mentioned? I see the issue is assigned to [~aslaakso] as well but I don't see any updates. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198392.1553542192000.10071.1566836880351%40Atlassian.JIRA.
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Jim Sears commented on JENKINS-56750 Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. Hi Daniel Gront, it has been over 2 months since the last comment on this issue. May I have an update? Did you get Bogdan's help as you mentioned? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198392.1553542192000.10064.1566836820280%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Hi, I can reproduce the error, I am not near a computer right now so I will have that for you by tomorrow. Yes, in this specific project - and probably all stuck builds - we have disabled concurrent builds. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.10062.1566835380166%40Atlassian.JIRA.
[JIRA] (JENKINS-58837) withDockerRegistry on multiple clusters
Title: Message Title Sergey Gladskih edited a comment on JENKINS-58837 Re: withDockerRegistry on multiple clusters Today I faced exactly the same bug. At least it's not the a problem of Windows agent that I use. Did you find some workaround (except traditional pull + push)? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201152.1565148699000.10058.1566835320143%40Atlassian.JIRA.
[JIRA] (JENKINS-58837) withDockerRegistry on multiple clusters
Title: Message Title Sergey Gladskih commented on JENKINS-58837 Re: withDockerRegistry on multiple clusters Today I faced exactly the same bug. At least it's not the problem of Windows agent that I use. Did you find some workaround (except traditional pull + push)? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201152.1565148699000.10055.1566835260188%40Atlassian.JIRA.
[JIRA] (JENKINS-58967) Credentials not available after upgrade to LTS 2.176.2
Title: Message Title Bram Mertens commented on JENKINS-58967 Re: Credentials not available after upgrade to LTS 2.176.2 A colleague found out that the problem is caused by the fact that as part of the upgrade the build authorization was configured to run as a specific user. The user that is configured does not have the Jobs/Configure permission. If we grant that permission the job is able to get the credentials as before. We will investigate the different options described in the Credentials API user guide to avoid granting that user Jobs/Configure permission. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201314.156596524.10052.1566835080070%40Atlassian.JIRA.
[JIRA] (JENKINS-55109) Unable to set credentials with CasC plugin
Title: Message Title Francisco Fernández updated JENKINS-55109 Jenkins / JENKINS-55109 Unable to set credentials with CasC plugin Change By: Francisco Fernández 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196170.1544461944000.10048.1566834780837%40Atlassian.JIRA.
[JIRA] (JENKINS-55109) Unable to set credentials with CasC plugin
Title: Message Title Francisco Fernández started work on JENKINS-55109 Change By: Francisco Fernández 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196170.1544461944000.10046.1566834780812%40Atlassian.JIRA.
[JIRA] (JENKINS-58257) New secrets written to kubernetes store are not always loaded by Jenkins
Title: Message Title Kyle Cronin commented on JENKINS-58257 Re: New secrets written to kubernetes store are not always loaded by Jenkins We have experienced this as well. Most likely the issue is the watch task closes due to some error like: ``` 2019-08-25 06:20:05.874+ [id=43] INFO c.c.j.p.k.KubernetesCredentialProvider#onClose: onClose. io.fabric8.kubernetes.client.KubernetesClientException: too old resource version: 130846525 (135483452) at io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager$1.onMessage(WatchConnectionManager.java:254) at okhttp3.internal.ws.RealWebSocket.onReadMessage(RealWebSocket.java:323) at okhttp3.internal.ws.WebSocketReader.readMessageFrame(WebSocketReader.java:219) at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:105) at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:274) at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:214) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:206) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) ``` The plugin does not attempt to recover from a closed watch connection. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200321.1561744491000.10041.1566833760720%40Atlassian.JIRA.
[JIRA] (JENKINS-59088) Github's pending does not wait until all concurrent builds are finished
Title: Message Title Gabriel Provencher created an issue Jenkins / JENKINS-59088 Github's pending does not wait until all concurrent builds are finished Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 2019-08-26 15:15 Priority: Major Reporter: Gabriel Provencher Hi! In my jenkinsfile, there are 2 builds that are launched concurrently. One for windows and another for linux. But when one of them is finished, Github shows that all checks are finished even if the other build is not finished. Could be useful that github waits until all builds are done before showing if it is a fail or a success. Thanx you Add Comment
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Jesse Glick commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Judging by the cause of blockage, I presume your project is set to disable concurrent builds. (The default for Pipeline is to permit them.) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.10031.1566832200132%40Atlassian.JIRA.
[JIRA] (JENKINS-59087) Credentials get stale when using Kubeconfig file rotating periodically
Title: Message Title John Smilanick created an issue Jenkins / JENKINS-59087 Credentials get stale when using Kubeconfig file rotating periodically Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-08-26 15:04 Labels: credentials config Priority: Minor Reporter: John Smilanick This is related to using kubernetes slaves via the Jenkins Cloud configuration. We use kubeconfig files to authenticate with the API server and we regenerate them daily using a cron job. We successfully update the credentials using groovy code, but the kubernetes-plugin doesn't detect the change and continues to use the old file until it eventually expires. It is behaving like it cached the credential somewhere. Our manual workaround is to go to Manage Jenkins -> Configure System and set the credential to 'none', save, return to Configure system and set it again. If we don't set it to none and just click save or use groovy to do a Jenkins save(), it doesn't reload the credential. This confirms that the credential is correct, but the kubernetes plugin needed some coercion to reload the credential. We would expect the credential change to be detected or the kubernetes plugin should read the file fresh each time it is used.
[JIRA] (JENKINS-46631) [JDK9] Illegal reflective access from slave.jar (Windows)
Title: Message Title P4 commented on JENKINS-46631 Re: [JDK9] Illegal reflective access from slave.jar (Windows) Hi. This issue still occurs in our environment. Any plans for fixation? Jenkins master: Windows Server 2012 R2; JDK 1.8.0_172-b11; Jenkins v2.176.2. Jenkins slave: Ubuntu 19.04 LTS; openjdk-11-jdk 11.0.4+11-post-Ubuntu-1ubuntu219.04 Node log: ... [08/26/19 16:06:45] [SSH] Checking java version of java [08/26/19 16:06:45] [SSH] java -version returned 11.0.4. [08/26/19 16:06:45] [SSH] Starting sftp client. [08/26/19 16:06:45] [SSH] Copying latest remoting.jar... [08/26/19 16:06:45] [SSH] Copied 789,283 bytes. Expanded the channel window size to 4MB [08/26/19 16:06:45] [SSH] Starting agent process: cd "/home/jenkins/jenkins" && java -jar remoting.jar -workDir /home/jenkins/jenkins Aug 26, 2019 4:06:46 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /home/jenkins/jenkins/remoting as a remoting work directory Both error and output logs will be printed to /home/jenkins/jenkins/remoting <===[JENKINS REMOTING CAPACITY]===>channel started Remoting version: 3.29 This is a Unix agent WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by jenkins.slaves.StandardOutputSwapper$ChannelSwapper to constructor java.io.FileDescriptor(int) WARNING: Please consider reporting this to the maintainers of jenkins.slaves.StandardOutputSwapper$ChannelSwapper WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Evacuated stdout Aug 26, 2019 4:06:52 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ [StartupTrigger] - Scanning jobs for node node-linux Agent successfully connected and online Add Comment
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: image.png 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.10024.1566830880237%40Atlassian.JIRA.
[JIRA] (JENKINS-58785) Environment variables for jnlp container are available to other containers
Title: Message Title Vincent Latombe updated JENKINS-58785 Jenkins / JENKINS-58785 Environment variables for jnlp container are available to other containers Change By: Vincent Latombe Status: Fixed but Unreleased Closed Released As: 1.18.2 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201095.156475539.9997.1566830761599%40Atlassian.JIRA.
[JIRA] (JENKINS-58766) kubernetes-plugin access denied after update to 1.18.0
Title: Message Title Vincent Latombe updated JENKINS-58766 Jenkins / JENKINS-58766 kubernetes-plugin access denied after update to 1.18.0 Change By: Vincent Latombe Status: Fixed but Unreleased Closed Released As: 1.18.2 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201071.1564670804000.10018.1566830761906%40Atlassian.JIRA.
[JIRA] (JENKINS-59000) KubernetesClientException onFailure(WatchConnectionManager.java:198) on k8s v1.15.3
Title: Message Title Vincent Latombe updated JENKINS-59000 Jenkins / JENKINS-59000 KubernetesClientException onFailure(WatchConnectionManager.java:198) on k8s v1.15.3 Change By: Vincent Latombe Status: Fixed but Unreleased Closed Released As: 1.18.2 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201351.1566264399000.10015.1566830761870%40Atlassian.JIRA.
[JIRA] (JENKINS-58767) Binary compatibility issue with 1.15 line
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-58767 Binary compatibility issue with 1.15 line Change By: Vincent Latombe Released As: 1.15.10 , 1.18.1 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201072.1564671718000.9986.1566829620408%40Atlassian.JIRA.
[JIRA] (JENKINS-58740) NullPointerException rendering kubernetes cloud configuration due to missing pod label field attribute
Title: Message Title Vincent Latombe updated JENKINS-58740 Jenkins / JENKINS-58740 NullPointerException rendering kubernetes cloud configuration due to missing pod label field attribute Change By: Vincent Latombe Status: Fixed but Unreleased 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201041.1564580209000.9990.1566829620466%40Atlassian.JIRA.
[JIRA] (JENKINS-58740) NullPointerException rendering kubernetes cloud configuration due to missing pod label field attribute
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-58740 NullPointerException rendering kubernetes cloud configuration due to missing pod label field attribute Change By: Vincent Latombe Released As: 1.18.1 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201041.1564580209000.9988.1566829620439%40Atlassian.JIRA.
[JIRA] (JENKINS-57616) Security Requester Whitelist Plugin cannot be exported to JCasC
Title: Message Title rsandell assigned an issue to rsandell Jenkins / JENKINS-57616 Security Requester Whitelist Plugin cannot be exported to JCasC Change By: rsandell Assignee: rsandell 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199544.1558540149000.9981.1566828900354%40Atlassian.JIRA.
[JIRA] (JENKINS-57616) Security Requester Whitelist Plugin cannot be exported to JCasC
Title: Message Title rsandell started work on JENKINS-57616 Change By: rsandell 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199544.1558540149000.9983.1566828900382%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Jesse Glick commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Yes, I suspect this is not so much an introduced bug as a change which made an existing bug more visible by treating termination conditions more consistently. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.9978.1566828060159%40Atlassian.JIRA.
[JIRA] (JENKINS-59086) PCT failing in BOM due to UC outage despite using -war
Title: Message Title
Jesse Glick created an issue
Jenkins / JENKINS-59086
PCT failing in BOM due to UC outage despite using -war
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
bom, plugin-compat-tester
Created:
2019-08-26 13:48
Priority:
Critical
Reporter:
Jesse Glick
Hook: org.jenkins.tools.test.hook.MultiParentCompileHook
Loaded multi-parent compile hook
Scanned contents of /home/jenkins/workspace/g.jenkins-ci.plugins-plugin-3.49/megawar.war: {"id":"default","core":{"name":"core","version":"2.176.2","url":"https://foobar"},"plugins":{...}}
Exception in thread "main" java.lang.RuntimeException: Invalid update center url : http://updates.jenkins-ci.org/update-center.json
at org.jenkins.tools.test.PluginCompatTester.extractUpdateCenterData(PluginCompatTester.java:583)
at org.jenkins.tools.test.PluginCompatTester.testPlugins(PluginCompatTester.java:183)
at org.jenkins.tools.test.PluginCompatTesterCli.main(PluginCompatTesterCli.java:164)
Caused by: java.net.ConnectException: Connection timed out (Connection timed out)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
at sun.net.www.http.HttpClient.(HttpClient.java:242)
at sun.net.www.http.HttpClient.New(HttpClient.java:339)
at
