[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Dave Nichols edited a comment on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost Also having this issue with Gitlab, multibranch pipelines, and Jenkins 2.150.2.Jenkins is running as a container with nginx. Also not 100% on this but I don't think all of the branches disappeared, only a subset disappeared and I can't find a reason why only those. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196298.154504211.8024.1571149081579%40Atlassian.JIRA.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Dave Nichols commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost Also having this issue with Gitlab, multibranch pipelines, and Jenkins 2.150.2. Jenkins is running as a container with nginx. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196298.154504211.8011.1571148960459%40Atlassian.JIRA.
[JIRA] (JENKINS-56286) Multibranch Pipeline + P4Plugin + Helix Library + Polling = Infinite Build Loop
Title: Message Title Dave Nichols commented on JENKINS-56286 Re: Multibranch Pipeline + P4Plugin + Helix Library + Polling = Infinite Build Loop Hi Karl, our jenkins files are in the pipeline job in jenkins as text for most of our jobs. Our pipeline code is in a different depot in Perforce from the code it builds. Does this make sense? Thanks, Dave Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56286) Multibranch Pipeline + P4Plugin + Helix Library + Polling = Infinite Build Loop
Title: Message Title Dave Nichols commented on JENKINS-56286 Re: Multibranch Pipeline + P4Plugin + Helix Library + Polling = Infinite Build Loop Hi Karl, I am having this issue too. 1. We are using a persistent master container with a fixed storage that is mounted as a volume into the docker container. We did recently upgrade our container (to 2.150.2) to a new version and the perforce plugin at the same time (to 1.9.6) but the build history is still the same as before the upgrade. 2. We are using build discarder with all of our jobs. I am not sure how Mykola has jenkins configured though. Thanks, Dave Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56037) SCM Polling with p4-plugin triggers builds several times
Title: Message Title Dave Nichols edited a comment on JENKINS-56037 Re: SCM Polling with p4-plugin triggers builds several times Same issue here as well.Jenkins 2.150.2 (Official Docker Image)P4 Plugin: 1.9.6 Seeing SCM polling trigger jobs with no changes in perforce. Is there any kind of work-around to this issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56037) SCM Polling with p4-plugin triggers builds several times
Title: Message Title Dave Nichols commented on JENKINS-56037 Re: SCM Polling with p4-plugin triggers builds several times Same issue here as well. Jenkins 2.150.2 (Official Docker Image) P4 Plugin: 1.9.6 Seeing SCM polling trigger jobs with no changes in perforce. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52171) Gitlab plugin uncompatible with Jira plugin in pipeline
Title: Message Title Dave Nichols commented on JENKINS-52171 Re: Gitlab plugin uncompatible with Jira plugin in pipeline Getting the same error, but with a different plugin from the Jira one. java.lang.LinkageError: ClassCastException: attempting to castjar:file:/var/jenkins_home/plugins/gitlab-plugin/WEB-INF/lib/jboss-jaxrs-api_2.0_spec-1.0.0.Final.jar!/javax/ws/rs/ext/RuntimeDelegate.classtojar:file:/var/jenkins_home/plugins/coverity/WEB-INF/lib/jersey-core-1.13.jar!/javax/ws/rs/ext/RuntimeDelegate.class at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:116) at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:91) at javax.ws.rs.core.UriBuilder.newInstance(UriBuilder.java:69) at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:80) at jenkins.plugins.coverity.ws.ViewsService.getViewContents(ViewsService.java:83) at jenkins.plugins.coverity.CIMInstance.getIssuesVorView(CIMInstance.java:303) at jenkins.plugins.coverity.ws.ViewIssuesReader.getIssuesFromConnectView(ViewIssuesReader.java:47) at jenkins.plugins.coverity.CoverityViewResultsPublisher.perform(CoverityViewResultsPublisher.java:77) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE Not sure if it is related Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
