[JIRA] (JENKINS-56260) Active Choices Reactive Parameter is showing sometimes empty list
Title: Message Title Bruno P. Kinoshita commented on JENKINS-56260 Re: Active Choices Reactive Parameter is showing sometimes empty list Oh, sorry Madhavi Katreddy. So I think we can ignore the screenshot. Could you provide some more info like Jenkins and active-choice-plugins versions (as well as any plugin relevant if used in this job). We would also need some way to replicate the issue. You mentioned a database, but it would probably take me a little while to work on this issue if I needed to set up a DB server/container/etc to replicate it. Does the issue happen if you execute a normal list that is retrieved via a Groovy script, but that is not going to the database? If the answer is no, then we will probably need to consider the possibility of a bug in the Groovy script that is calling the DB... Hope that makes sense. Ioannis and I triaged some issues a couple of weeks ago, and I am currently working through the current backlog. If it is easy to replicate and understand what's going on, I can try to include this issue in the next release. Otherwise we will have a look and try to include in the next one Cheers Bruno 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-56260) Active Choices Reactive Parameter is showing sometimes empty list
Title: Message Title Bruno P. Kinoshita edited a comment on JENKINS-56260 Re: Active Choices Reactive Parameter is showing sometimes empty list Oh, sorry [~madhavi_katreddy]. So I think we can ignore the screenshot.Could you provide some more info like Jenkins and active-choice-plugins versions (as well as any plugin relevant if used in this job). We would also need some way to replicate the issue.You mentioned a database, but it would probably take me a little while to work on this issue if I needed to set up a DB server/container/etc to replicate it. Does the issue happen if you execute a normal list that is retrieved via a Groovy script, but that is not going to the database? If the answer is no, then we will probably need to consider the possibility of a bug in the Groovy script that is calling the DB...Hope that makes sense. Ioannis [~ioannis] and I triaged some issues a couple of weeks ago, and I am currently working through the current backlog. If it is easy to replicate and understand what's going on, I can try to include this issue in the next release.Otherwise we will have a look and try to include in the next one (y)CheersBruno 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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title Lakshya Kapoor commented on JENKINS-56402 Re: Declarative Pipeline shows SUCCESS even though job FAILED Thanks, Andrew Bayer! I'll test 1.3.7-beta-1 on Monday and report back. 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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title Lakshya Kapoor edited a comment on JENKINS-56402 Re: Declarative Pipeline shows SUCCESS even though job FAILED Thanks, [~abayer] and [~dnusbaum] ! I'll test 1.3.7-beta-1 on Monday and report back. 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-56491) overeager provisioning of k8s nodes
Title: Message Title Denny Ho created an issue Jenkins / JENKINS-56491 overeager provisioning of k8s nodes Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-03-09 00:26 Environment: Behavior seen with kubernetes plugin 1.14.8 tested on Jenkins vers 2.150.2 and 2.150.3 the service is running on an ubuntu 16.04 machine Priority: Minor Reporter: Denny Ho Recently upgraded from kubernetes plugin 1.14.3 -> 1.14.8, so not sure which version the change was introduced. Seeing an overeagerness with node provisioning with k8s nodes. Happens most often when there are already existing k8s nodes jobs running to repro Create 3-4 jobs running with a k8s node label. I just used sleep 600 in my build start one of the jobs while that build is running, start the other jobs observe that more nodes will spin up than necessary and so some will sit idle before being terminated observe in /var/logs/jenkins/jenkins.log messages like this, negative workload: // INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 executors. Remaining excess workload: -0.183
[JIRA] (JENKINS-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title Andrew Bayer commented on JENKINS-56402 Re: Declarative Pipeline shows SUCCESS even though job FAILED I've just merged a potential fix (https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/319) and am cutting 1.3.7-beta-1 now - see https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/ for how you can install the beta. It should be in the update center within an hour or so. We'd appreciate your feedback as to how this change works for you - if it turns out not to solve enough of the use cases, we'll switch to reverting the problematic change completely, but we'd really like to be able to keep it in if we can. Thanks, and we appreciate your patience and are very sorry for the inconvenience this change has caused. 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-56490) JEP-200 Secuity java.lang.SecurityException: Rejected: net.minidev.json.JSONArray
Title: Message Title Krzysztof Mulica closed an issue as Won't Fix Jenkins / JENKINS-56490 JEP-200 Secuity java.lang.SecurityException: Rejected: net.minidev.json.JSONArray Change By: Krzysztof Mulica Status: Open Closed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56490) JEP-200 Secuity java.lang.SecurityException: Rejected: net.minidev.json.JSONArray
Title: Message Title Krzysztof Mulica commented on JENKINS-56490 Re: JEP-200 Secuity java.lang.SecurityException: Rejected: net.minidev.json.JSONArray Sorry please close, just saw this https://github.com/jenkinsci/git-changelog-plugin/commit/57c7c06db0c06c2cce1c0c66040fb4bfbf6adcf4 , I didnt notice this jenkins master was a version behind on 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56490) JEP-200 Secuity java.lang.SecurityException: Rejected: net.minidev.json.JSONArray
Title: Message Title Krzysztof Mulica created an issue Jenkins / JENKINS-56490 JEP-200 Secuity java.lang.SecurityException: Rejected: net.minidev.json.JSONArray Issue Type: Bug Assignee: Tomas Bjerre Components: git-changelog-plugin Created: 2019-03-08 22:10 Labels: JEP-200 Priority: Major Reporter: Krzysztof Mulica java.lang.SecurityException: Rejected: net.minidev.json.JSONArray; see https://jenkins.io/redirect/class-filter/ at hudson.remoting.ClassFilter.check(ClassFilter.java:77) at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:135) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1613) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1518) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1774) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371) at java.util.ArrayList.readObject(ArrayList.java:791) at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1017) at
[JIRA] (JENKINS-56393) RFLINT parser does not parse the Category correctly
Title: Message Title Bassam Khouri commented on JENKINS-56393 Re: RFLINT parser does not parse the Category correctly A PR has been posted: https://github.com/jenkinsci/analysis-model/pull/117 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-56489) Getting error when using HP Quality center plugin in a post build action step
Title: Message Title priya prasad updated an issue Jenkins / JENKINS-56489 Getting error when using HP Quality center plugin in a post build action step Change By: priya prasad Authentication and connection to HP ALM is successful.When adding the post build action HP Quality Center integration, the domain gets autopopulated but the Project dropdown is empty and on change gives the following error:-org.glassfish.jersey.message.internal.MessageBodyProviderNotFoundException: MessageBodyReader not found for media type=text/html; charset=ISO-8859-1, type=interface java.util.List, genericType=java.util.List. at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$TerminalReaderInterceptor.aroundReadFrom(ReaderInterceptorExecutor.java:230) at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor.proceed(ReaderInterceptorExecutor.java:154) at org.glassfish.jersey.message.internal.MessageBodyFactory.readFrom(MessageBodyFactory.java:1124) at org.glassfish.jersey.message.internal.InboundMessageContext.readEntity(InboundMessageContext.java:851) at org.glassfish.jersey.message.internal.InboundMessageContext.readEntity(InboundMessageContext.java:810) at org.glassfish.jersey.client.ClientResponse.readEntity(ClientResponse.java:368) at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:846) at org.glassfish.jersey.client.JerseyInvocation.access$600(JerseyInvocation.java:91) at org.glassfish.jersey.client.JerseyInvocation$3.call(JerseyInvocation.java:705) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:228) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:424) at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:701) at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:417) at org.glassfish.jersey.client.JerseyInvocation$Builder.get(JerseyInvocation.java:313) at org.jenkinsci.plugins.qc.client.QualityCenter.projects(QualityCenter.java:43) at org.jenkinsci.plugins.qc.QualityCenterIntegrationRecorder$QualityCenterIntegrationDescriptor.doFillProjectItems(QualityCenterIntegrationRecorder.java:490) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at
[JIRA] (JENKINS-53757) Exec Failure: Expected HTTP 101 response but was '403 Forbidden'
Title: Message Title Brett Cashman commented on JENKINS-53757 Re: Exec Failure: Expected HTTP 101 response but was '403 Forbidden' Nick Bromfield, Angel Bermudez, could you guys describe what you actually did in detail? I mean, I could Google around for it, and spend time trying to parse threads on Stack Overflow and Github, but if either or both of you could document what you did concisely, it'd be a big help. Thanks! 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-56383) BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins
Title: Message Title Gavin Mogan commented on JENKINS-56383 Re: BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins yea, 1.13.1 had a fix for downstream, while 1.13.2 rolled it back because it broke rendering parallel jobs I would say watch JENKINS-38339, I'm pretty sure both cases will be fixed in 1.14 when we do the next release (we are still working on a proper fix for this one, the parallel job ones) 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-56489) Getting error when using HP Quality center plugin in a post build action step
Title: Message Title priya prasad updated an issue Jenkins / JENKINS-56489 Getting error when using HP Quality center plugin in a post build action step Change By: priya prasad Authentication and connection to HP ALM is successful.When adding the post build action HP Quality Center integration, the domain gets autopopulated but the Project dropdown is empty and on change gives the following error:- org.glassfish.jersey.message.internal.MessageBodyProviderNotFoundException: MessageBodyReader not found for media type=text/html; charset=ISO-8859-1, type=interface java.util.List, genericType=java.util.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56489) Getting error when using HP Quality center plugin in a post build action step
Title: Message Title priya prasad updated an issue Jenkins / JENKINS-56489 Getting error when using HP Quality center plugin in a post build action step Change By: priya prasad org.glassfish.jersey.message.internal.MessageBodyProviderNotFoundException: MessageBodyReader not found for media type=text/html; charset=ISO-8859-1, type=interface java.util.List, genericType=java.util.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56489) Getting error when using HP Quality center plugin in a post build action step
Title: Message Title priya prasad created an issue Jenkins / JENKINS-56489 Getting error when using HP Quality center plugin in a post build action step Issue Type: Bug Assignee: Michael Fazio Components: hp-quality-center-plugin Created: 2019-03-08 20:33 Priority: Blocker Reporter: priya prasad 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-56383) BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins
Title: Message Title Guilherme Blanco commented on JENKINS-56383 Re: BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins Gavin Mogan Actually no... The issue started once I upgraded from 1.13.1 to 1.13.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title
Álvaro Iradier commented on JENKINS-51057
Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM
After many tests and cleanup scripts, we still we able to find some EventDispatcher$Retry elements in the heap but no subscribers in the GuavaPubSubBus or EventDispatchers in the HttpSessions. Some additional verifications in the plugin made me notice that as AsyncEventDispatcher was being used, it is possible that the EventDispatchers were still being referenced by some asyncContexts or threads that were not completed or released. Finally I also added a dispatcher.stop() call in my cleanup script, and it looks like there are no traces of leaked EventDispatcher$Retry clases in the heap anymore, but we still keep observing our instance and analyzing heap dumps, it is very soon to confirm. Just in case it can help, this is the cleanup script we are running daily:
import org.jenkinsci.plugins.pubsub.PubsubBus;
import org.jenkinsci.plugins.ssegateway.sse.*;
def dryRun = false
this.bus = PubsubBus.getBus();
// change visibility of retryQueue so that we can use reflection instead...
def retryQueueField = org.jenkinsci.plugins.ssegateway.sse.EventDispatcher.getDeclaredField('retryQueue')
retryQueueField.setAccessible(true)
def dispatcherCount = 0
def dispatchersList = []
//Build a list of EventDispatchers in all existing HTTP sessions
println "DISPATCHERS IN HTTP SESSIONS"
println ""
def sessions = Jenkins.instance.servletContext.this$0._sessionHandler._sessionCache._sessions
sessions.each{id, session->
def eventDispatchers = EventDispatcherFactory.getDispatchers(session)
if (eventDispatchers) {
eventDispatchers.each { dispatcherId, dispatcher ->
dispatchersList.add(dispatcherId)
def retryQueue = retryQueueField.get(dispatcher) // Need to use reflection since retryQueue is private in super class...
if (retryQueue.peek() != null) {
def oldestAge = (System.currentTimeMillis() - retryQueue.peek().timestamp)/1000
println "Dispatcher: " + dispatcher.getClass().getName() + " - " + dispatcher.id + " with " + retryQueue.size() + " events, oldest is " + oldestAge + " seconds."
} else {
println "Dispatcher: " + dispatcher.getClass().getName() + " - " + dispatcher.id + " with no retryEvents"
}
}
}
}
println "There are " + dispatchersList.size() + " dispatchers in HTTP sessions"
println ""
//Find all subscribers in bus
println "DISPATCHERS IN PUBSUBBUS"
println ""
this.bus.subscribers.each{ channelSubscriber, guavaSubscriber ->
if (channelSubscriber.getClass().getName().equals('org.jenkinsci.plugins.ssegateway.sse.EventDispatcher$SSEChannelSubscriber')) {
dispatcherCount++
def dispatcher = channelSubscriber.this$0
def retryQueue = retryQueueField.get(dispatcher) // Need to use reflection since retryQueue is private in super class...
if (retryQueue.peek() != null) {
def oldestAge = (System.currentTimeMillis() - retryQueue.peek().timestamp)/1000
println "Dispatcher: " + dispatcher.id + " with " + retryQueue.size() + " events, oldest is " + oldestAge + " seconds."
if (oldestAge > 300) {
println " Clearing retryQueue with " + retryQueue.size() + " events"
if (!dryRun) {
retryQueue.clear()
} else {
println " Ignoring, dryrun"
}
}
} else {
println "Dispatcher: " + dispatcher.id + " with no retryEvents"
}
[JIRA] (JENKINS-56488) Docker Pipeline plugin doesn't support quotes around Dockerfile path
Title: Message Title Aleksei Zhogov assigned an issue to Andrew Bayer Jenkins / JENKINS-56488 Docker Pipeline plugin doesn't support quotes around Dockerfile path Change By: Aleksei Zhogov Assignee: Andrew Bayer 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-56488) Docker Pipeline plugin doesn't support quotes around Dockerfile path
Title: Message Title Aleksei Zhogov commented on JENKINS-56488 Re: Docker Pipeline plugin doesn't support quotes around Dockerfile path PR to fix it: https://github.com/jenkinsci/docker-workflow-plugin/pull/164 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-56488) Docker Pipeline plugin doesn't support quotes around Dockerfile path
Title: Message Title
Aleksei Zhogov created an issue
Jenkins / JENKINS-56488
Docker Pipeline plugin doesn't support quotes around Dockerfile path
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-workflow-plugin
Created:
2019-03-08 18:55
Environment:
Jenkins 2.167 Both Docker Pipeline 1.17 and latest master (490870e)
Priority:
Minor
Reporter:
Aleksei Zhogov
Pipeline:
node {
sh 'echo "FROM alpine" > Dockerfile'
sh 'ls'
sh 'cat Dockerfile'
docker.build("test-image", "--file './Dockerfile' .")
}
Error I get from Docker Pipeline 1.17
[Pipeline] Start of Pipeline (hide)
[Pipeline] node
Running on Jenkins in /var/jenkins_home/workspace/test-pipeline
[Pipeline] {
[Pipeline] sh
+ echo FROM alpine
[Pipeline] sh
+ ls
Dockerfile
[Pipeline] sh
+ cat Dockerfile
FROM alpine
[Pipeline] sh
+ docker build -t test-image --file ./Dockerfile .
Sending build context to Docker daemon 2.048kB
Step 1/1 : FROM alpine
---> caf27325b298
Successfully built caf27325b298
Successfully tagged test-image:latest
[Pipeline] dockerFingerprintFrom
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
java.nio.file.NoSuchFileException: /var/jenkins_home/workspace/test-pipeline/'./Dockerfile'
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
at
[JIRA] (JENKINS-56469) Blueocean pipeline graph incomplete
Title: Message Title Patrick Hofmann commented on JENKINS-56469 Re: Blueocean pipeline graph incomplete Indeed fixed in 1.13.2, thanks! 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-56202) Blueocean unable to display inline pipeline script stage details
Title: Message Title Gavin Mogan commented on JENKINS-56202 Re: Blueocean unable to display inline pipeline script stage details Do you have a sample jenkinsfile that shows this problem? (just use echo or something inside the stages) 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-56221) github-sqs-plugin fails with blueocean > 1.10.1
Title: Message Title Gavin Mogan commented on JENKINS-56221 Re: github-sqs-plugin fails with blueocean > 1.10.1 My only guess is that the minimum git plugin got upgraded: https://wiki.jenkins.io/display/JENKINS/Blue+Ocean+Plugin#BlueOceanPlugin-1.11.0(Feb13,2019) None of the other changes I can see could even remotely affect this. Without more data/logs this is going to be pretty hard to debug. 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-56329) Blueocean hanging while loading
Title: Message Title Gavin Mogan commented on JENKINS-56329 Re: Blueocean hanging while loading are you running jenkins behind a proxy / webserver of some sort? I don't think the PUT error screenshot is a jenkins error, I think its apache/nginx method limiting. 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-56392) blue-ocean links from classic do not use https
Title: Message Title Gavin Mogan commented on JENKINS-56392 Re: blue-ocean links from classic do not use https HEY Björn Pedersen, are you running jenkins behind a proxy (apache/nginx or anything)? It seems to work right on ci.blueocean.io curl -v https://ci.blueocean.io/blue/organizations/jenkins/blueocean/detail/master/1811/pipeline 2>&1 | grep -i Location: < location: https://ci.blueocean.io/blue/organizations/jenkins/blueocean/detail/master/1811/pipeline/ You may need to set the right proxy headers, or fix the proxy_pass if you used https://wiki.jenkins.io/display/JENKINS/Blue+Ocean+Plugin#BlueOceanPlugin-Runningbehindaproxy?Readthis which says proxy_pass http, but you'd want proxy_pass https 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-56392) blue-ocean links from classic do not use https
Title: Message Title
Gavin Mogan updated an issue
Jenkins / JENKINS-56392
blue-ocean links from classic do not use https
Change By:
Gavin Mogan
trying to open a job located in a folder from the classic view (open- blue ocean link) raisesa 404 error. The URL in the link has correct escaping of slashes Inspecting the http-requests seems to indicate that jenkins sends an intermediate page via Location: that is not using https.Initals request (https)GET /jenkins/blue/organizations/jenkins/debocker%2FBuildEntangleContainersV2 HTTP/1.1Host: User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8Accept-Language: en-US,en;q=0.5Accept-Encoding: gzip, deflate, brReferer: https:///jenkins/job/debocker/job/BuildEntangleContainersV2/Connection: keep-aliveCookie: screenResolution=1920x1200; jenkins-timestamper-offset=-360; jenkins-timestamper=none; jenkins-timestamper-local=true; Upgrade-Insecure-Requests: 1 Response:HTTP/1.1 302 FoundDate: Mon, 04 Mar 2019 15:43:13 GMTServer: Jetty(9.4.z-SNAPSHOT)X-Content-Type-Options: nosniffX-Blueocean-Refresher: .Location: {color:# FF ff }http:// {color} forge.frm2.tum.de /jenkins/blue/organizations/jenkins/debocker/BuildEntangleContainersV2/Keep-Alive: timeout=5, max=86Connection: Keep-AliveTransfer-Encoding: chunked Note the http in there. Possibly also related to JENKINS-46347
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-56406) Expose artifacts and test display URLs in environment variables
Title: Message Title Gavin Mogan assigned an issue to Gavin Mogan Jenkins / JENKINS-56406 Expose artifacts and test display URLs in environment variables Change By: Gavin Mogan Assignee: Ivan Meredith Gavin Mogan 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-56406) Expose artifacts and test display URLs in environment variables
Title: Message Title Gavin Mogan assigned an issue to Unassigned Jenkins / JENKINS-56406 Expose artifacts and test display URLs in environment variables Change By: Gavin Mogan Assignee: Gavin Mogan 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-56469) Blueocean pipeline graph incomplete
Title: Message Title Gavin Mogan resolved as Fixed I'm pretty sure we fixed this in 1.13.2 which we rolled back a regression, 1.14 should have both fixed properly. If this is not fixed in 1.13.2, can you re-open but include a jenkinsfile that highlights the issue? Jenkins / JENKINS-56469 Blueocean pipeline graph incomplete Change By: Gavin Mogan 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56445) Pipeline stages not showing up correctly
Title: Message Title Gavin Mogan closed an issue as Duplicate Duplicate of JENKINS-56383 Fixed regression in 1.13.2 Jenkins / JENKINS-56445 Pipeline stages not showing up correctly Change By: Gavin Mogan Status: Open 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56382) Only one stage visible in BlueOcean
Title: Message Title Gavin Mogan commented on JENKINS-56382 Re: Only one stage visible in BlueOcean This is likely caused by a regression. We rolled back the change due to JENKINS-56383 into 1.13.2, we should have a proper fix for 1.14 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-56382) Only one stage visible in BlueOcean
Title: Message Title Gavin Mogan closed an issue as Duplicate Jenkins / JENKINS-56382 Only one stage visible in BlueOcean Change By: Gavin Mogan Status: Open Closed Resolution: Duplicate Released As: 1.13.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45719) Description for a pipeline run is not compatible and cannot be disabled
Title: Message Title Gavin Mogan assigned an issue to Unassigned Jenkins / JENKINS-45719 Description for a pipeline run is not compatible and cannot be disabled Change By: Gavin Mogan Assignee: James Dumay 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-47496) No automatic builds for tags
Title: Message Title
Mark F commented on JENKINS-47496
Re: No automatic builds for tags
Here is the workaround to add tag discovery for multibranch pipelines in JobDSL:
multibranchPipelineJob('my_repo') {
branchSources { branchSource { source { git {
remote(git_url)
credentialsId('my_credential_id')
traits {
gitBranchDiscovery()
gitTagDiscovery() // be careful you don't create a build storm!
headWildcardFilter {
includes('my_branch1 my_branches* my_tags* )
excludes('')
}
}
} } } }
...
}
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-56487) Post-Build Step In Pipeline Config, Not In Jenkinsfile
Title: Message Title
Brian Attwell created an issue
Jenkins / JENKINS-56487
Post-Build Step In Pipeline Config, Not In Jenkinsfile
Issue Type:
New Feature
Assignee:
Unassigned
Components:
pipeline
Created:
2019-03-08 17:31
Priority:
Minor
Reporter:
Brian Attwell
*Problem* Jenkins pipelines are a great way of allowing engineering teams to self service their CI needs. For example, every team can write their own `Jenkinsfile-release` in their own repos. Suppose we want to send a slack message to the `#release` channel every single time any team's `Jenkinsfile-release` succeeds. Today, we need to copy and paste the following snippet into every single repo's `Jenkinsfile-release`: ``` {{ slackSend channel: '#release', color: 'good', message: "The ${params.repo} repo released."}} ``` *Solution* Create a post-build-like phase that can be configured from inside the Jenkins UI. Then engineers can add post-build steps that globally apply to all Jenkinsfile's for a given pipeline.
Add Comment
[JIRA] (JENKINS-40198) allow scanning and retrieval of a pipeline job inside the pipeline
Title: Message Title Raj Sahae commented on JENKINS-40198 Re: allow scanning and retrieval of a pipeline job inside the pipeline I have the exact same use case and desire as Christopher Shannon on this. 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-56383) BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins
Title: Message Title Gavin Mogan commented on JENKINS-56383 Re: BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins Guilherme Blanco I think thats a different bug. I'm thinking you mean https://issues.jenkins-ci.org/browse/JENKINS-38339 which we had to roll back for .2 to fix 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-56383) BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins
Title: Message Title Guilherme Blanco updated an issue Jenkins / JENKINS-56383 BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins Change By: Guilherme Blanco Attachment: Screen Shot 2019-03-08 at 11.58.58 AM.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56383) BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins
Title: Message Title Guilherme Blanco commented on JENKINS-56383 Re: BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins And here is the example of duplicated step while also not showing the downstream job. 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, 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 Mykola Ulianytskyi commented on JENKINS-56286 Re: Multibranch Pipeline + P4Plugin + Helix Library + Polling = Infinite Build Loop Hi Karl, Is the library being under a branch a normal situation The library and all Jenkins Pipelines belong to the same stream. The library contains common functions used by pipelines. It is a normal practice and it works perfectly if used Legacy SCM > Perforce Software > Manual Workspace. 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-56486) Improve UX to prevent admins from approving blacklisted methods without understanding the impact
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-56486 Improve UX to prevent admins from approving blacklisted methods without understanding the impact Change By: Devin Nusbaum Summary: Make some Improve UX to prevent admins from approving blacklisted methods in without understanding the Script Security blacklist unapprovable impact 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-56486) Improve UX to prevent admins from approving blacklisted methods without understanding the impact
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-56486 Improve UX to prevent admins from approving blacklisted methods without understanding the impact Change By: Devin Nusbaum Summary: Make some Improve UX to prevent admins from approving blacklisted methods in without understanding the Script Security blacklist unapprovable impact 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-56486) Make some methods in the Script Security blacklist unapprovable
Title: Message Title Devin Nusbaum assigned an issue to Unassigned Jenkins / JENKINS-56486 Make some methods in the Script Security blacklist unapprovable Change By: Devin Nusbaum Assignee: Andrew Bayer 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-56486) Make some methods in the Script Security blacklist unapprovable
Title: Message Title Devin Nusbaum created an issue Jenkins / JENKINS-56486 Make some methods in the Script Security blacklist unapprovable Issue Type: Improvement Assignee: Andrew Bayer Components: script-security-plugin Created: 2019-03-08 16:49 Labels: pipeline Priority: Minor Reporter: Devin Nusbaum The script-security plugin already has a blacklist of dangerous method signatures that admins should probably not approve. Methods in this blacklist provide an extra warning when they are being approved, but perhaps that warning is not severe enough, as I have heard multiple reports of users accidentally causing a denial of service attack on their Jenkins instance with a Pipeline that runs System.exit. Some ideas: Make methods which are very unlikely to have legitimate use cases even in an environment where only admins are writing sandboxed scripts unable to be approved, such as System.exit (could be opt-in or opt-out with a system property?). For RejectedAccessExceptions where isDangerous returns true, provide per-signature documentation on the issues, and require the user to re-type the method signature or wait 10 seconds before they can approve the signature in the hope that providing the user with a better understanding of the problems will keep them from approving these methods. Create an admin monitor that warns when blacklisted methods are in the approved list, and gives admins a one-click way to unapprove them. In this case, some kind of additional warning is also likely needed to prevent admins from breaking running jobs
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Dmytro Kryvenko commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I understand your be frustrated but comments like this are not very helpful. Well sometimes truth is not helpful at all. What's your point? Maybe you have a solution or even a PR? Enlighten us. I couldn't disagree more. You didn't seem to read my suggestion careful enough. Declarative approach, indeed, is the future. Particular Jenkinsfile declarative implementation sucks, though. Because you kind of use declarative style but you still have to imperatively define steps. What a bummer! If you read careful enough what I said, you'll see what I opted in for is rather to have a small meta data file in the repository that explains facts about the app inside, so that the library can deal with it and render a pipeline for it. This render body is much easier to work with when it's scripted style, and the fact that it's scripted doesn't matter because users don't directly deal with it. 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 Karl Wirth commented on JENKINS-56286 Re: Multibranch Pipeline + P4Plugin + Helix Library + Polling = Infinite Build Loop Hi Mykola Ulianytskyi - Again thank you for all your work on this. Is the library being under a branch a normal situation for you or did you just do it force the bug? The problem is that if the library is under the branch it becomes included in two separate SyncIDs. The way we had assumed libraries would be used is that the library is external to the branch in some global location. For example: //build-dependencies/jenkins-main/library/vars/foo1.groovy //playground/jenkins-main/Jenkinsfile //playground/jenkins-main/src/f1.c //playground/jenkins-main/src/f1.h 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-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Henry Borchers commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Well then you may be trying to apply a wrong tool for the job. Try some commercial offers maybe. I understand your be frustrated but comments like this are not very helpful. I guess my point is - declarative style just sucks. From my experience it works only for small and simple projects despite how hard it's being advertised an opposite. I couldn't disagree more. It's super easy to read and understand. It has a clean syntax. It's well thought out. It's expandable with scripts if need be. It's so easy to to look through the blue ocean to see why something has failed. It's freaking brilliant!!! The declarative pipeline is the main reason that I use Jenkins and why I advocate for it wherever I go. Did I mention it's brilliant? The biggest issue is that it is so easy to use, that I just want to use it more and more until I get smacked in the face with "Method code too large!. It's a little bit like the use of electricity over the last century. Most electronic devices have become more efficient throughout the decades and use less electricity as their designs have improved. However, we keep finding new uses for electricity at a faster rate than we can make them more efficient. We end up needing more and more power plants as a result, not fewer. I feel the same way with Jenkins and especially the declarative pipeline. I've been getting the lines in my steps into fewer and fewer lines. I make shared-libraries for my common code and "helper script functions" outside of the pipeline block. However, I keep finding more and more ways to find problems in my code early with careful placement of "sequential and parallel stages" and "when and post" blocks. I end up with lots of stages with one or two lines in the steps block. Then all of a sudden, I run into "Method code too large!"... And then I become a sad developer... Add Comment
[JIRA] (JENKINS-56383) BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins
Title: Message Title Guilherme Blanco commented on JENKINS-56383 Re: BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins This fix introduced a regression for us. We have several layers of downstream jobs, and now the access links to them while being build are not showing, no reports are happening and also duplicated steps are appearing during build. 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-56383) BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins
Title: Message Title Guilherme Blanco updated an issue Jenkins / JENKINS-56383 BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins Change By: Guilherme Blanco Attachment: Screen Shot 2019-03-08 at 11.27.49 AM.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56485) RFE: Add Support for VPN Proxy for Starting Agents
Title: Message Title Randall Becker updated an issue Jenkins / JENKINS-56485 RFE: Add Support for VPN Proxy for Starting Agents Change By: Randall Becker Our network configuration requires that our Master, in one DMZ, start an agent in another DMZ that are separated by firewalls, proxies, and a VPN bridge with separate credentials from the agent machine.This is a request to add the following to SSH Slaves: # Host IP/name of the VPN proxy. # A field to specify the command to launch a VPN proxy. Sample: `openconnect --protocol=gp --server-key=... --user=something --key-password=something` # A credential specification to be used for the VPN proxy. # Launching the VPN proxy command. # Continue with SSH startup of the agent JVM but from an SSH session initiated on the VPN proxy instead of initiated from the master. There are actually three distinct sets of credentials involved here: * Controller to VPN proxy SSH keys * VPN proxy to VPN server keys (whichever they use, probably user/password) * Controller to Agent SSH keys once the VPN connection is established. The original thought was to use or even take over the now defunked openconnect plugin, but that seems to have disappeared. There are many different possible VPN solutions, with openconnect being one of them. This enhancement would remove the need to establish a static VPN connection available to all users and Jenkins instances on the Controller. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56086) Tabs missing in configuration page after adding plot to freestyle job
Title: Message Title
Stefan Drissen edited a comment on JENKINS-56086
Re: Tabs missing in configuration page after adding plot to freestyle job
I have the same issue. The plot plug-in is causing a _javascript_ error in hudson.behavior.js:{code:java}hudson-behavior.js:424 Uncaught TypeError: Cannot read property 'firstChild' of undefined at registerValidator (hudson-behavior.js:424) at Array.forEach () at behavior.js:111 at Array.forEach () at behavior.js:107 at Array.forEach () at Object.applySubtree (behavior.js:93) at select.js:269{code} Seems to be the same issue as JENKINS-53182
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-56088) FinishLogin throws: Illegal character in query at index 89
Title: Message Title Davíð Jóhannsson resolved as Fixed Jenkins / JENKINS-56088 FinishLogin throws: Illegal character in query at index 89 Change By: Davíð Jóhannsson 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56088) FinishLogin throws: Illegal character in query at index 89
Title: Message Title Davíð Jóhannsson commented on JENKINS-56088 Re: FinishLogin throws: Illegal character in query at index 89 I had to re-apply the client secret in plain text into .jenkins/config.xml:org.jenkinsci.plugins.GithubSecurityRealm 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-56485) RFE: Add Support for VPN Proxy for Starting Agents
Title: Message Title Randall Becker created an issue Jenkins / JENKINS-56485 RFE: Add Support for VPN Proxy for Starting Agents Issue Type: New Feature Assignee: Ivan Fernandez Calvo Components: ssh-slaves-plugin Created: 2019-03-08 16:06 Environment: Any Labels: slave configuration security Priority: Major Reporter: Randall Becker Our network configuration requires that our Master, in one DMZ, start an agent in another DMZ that are separated by firewalls, proxies, and a VPN bridge with separate credentials from the agent machine. This is a request to add the following to SSH Slaves: Host IP/name of the VPN proxy. A field to specify the command to launch a VPN proxy. Sample: `openconnect --protocol=gp --server-key=... --user=something --key-password=something` A credential specification to be used for the VPN proxy. Launching the VPN proxy command. Continue with SSH startup of the agent JVM but from an SSH session initiated on the VPN proxy instead of initiated from the master. The original thought was to use or even take over the now defunked openconnect plugin, but that seems to have disappeared. There are many different possible VPN solutions,
[JIRA] (JENKINS-56484) timestamper 1.9 breaks warnings-ng's ability to find source files
Title: Message Title
Steve Mokris updated an issue
Jenkins / JENKINS-56484
timestamper 1.9 breaks warnings-ng's ability to find source files
Change By:
Steve Mokris
In timestamper 1.9, the [log format was changed|https://plugins.jenkins.io/timestamper#Timestamper-1.9(2019-02-07)]. When I enable timestamper on a pipeline job, then scan it with warnings-ng, it detects errors but incorrectly parses the filename — it considers the timestamp to be part of the filename.To reproduce the issue, install both plugins and run this pipeline job:{code:java}node {timestamps {sh """echo '#error This is an error.' > test.cclang test.c || true"""recordIssues tools: [clang(id: 'clang', name: 'clang')]}}{code}and the console log says:{code:java}00:00:01.047 test.c:1:2: error: This is an error.…00:00:06.276 [clang] [ERROR] Can't resolve absolute paths for some files:00:00:06.276 [clang] [ERROR] - [2019-03-08T15:46:53.268Z] test.c00:00:06.276 [clang] [ERROR] Can't create fingerprints for some files:00:00:06.276 [clang] [ERROR] - '[2019-03-08T15:46:53.268Z] test.c', IO exception has been thrown: java.nio.file.NoSuchFileException: [2019-03-08T15:46:53.268Z] test.c{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
[JIRA] (JENKINS-56484) timestamper 1.9 breaks warnings-ng's ability to find source files
Title: Message Title
Steve Mokris created an issue
Jenkins / JENKINS-56484
timestamper 1.9 breaks warnings-ng's ability to find source files
Issue Type:
Bug
Assignee:
Steven G Brown
Components:
timestamper-plugin, warnings-ng-plugin
Created:
2019-03-08 16:04
Environment:
Jenkins 2.166 timestamper-plugin 1.9 warnings-ng-plugin 3.0.3
Priority:
Major
Reporter:
Steve Mokris
In timestamper 1.9, the log format was changed. When I enable timestamper on a pipeline job, then scan it with warnings-ng, it detects errors but incorrectly parses the filename — it considers the timestamp part of the filename. To reproduce the issue, install both plugins and run this pipeline job:
node {
timestamps {
sh """
echo '#error This is an error.' > test.c
clang test.c || true
"""
recordIssues tools: [clang(id: 'clang', name: 'clang')]
}
}
and the console log says:
00:00:01.047 test.c:1:2: error: This is an error.
…
00:00:06.276 [clang] [ERROR] Can't resolve absolute paths for some files:
00:00:06.276 [clang] [ERROR] - [2019-03-08T15:46:53.268Z] test.c
00:00:06.276 [clang] [ERROR] Can't create fingerprints for some files:
00:00:06.276 [clang] [ERROR] - '[2019-03-08T15:46:53.268Z] test.c', IO exception has been thrown:
[JIRA] (JENKINS-56418) RFLint Parser does not show the Robotframwork logo
Title: Message Title Ulli Hafner updated JENKINS-56418 Jenkins / JENKINS-56418 RFLint Parser does not show the Robotframwork logo Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56086) Tabs missing in configuration page after adding plot to freestyle job
Title: Message Title Stefan Drissen commented on JENKINS-56086 Re: Tabs missing in configuration page after adding plot to freestyle job I have the same issue. The plot plug-in is causing a _javascript_ error in hudson.behavior.js: hudson-behavior.js:424 Uncaught TypeError: Cannot read property 'firstChild' of undefined at registerValidator (hudson-behavior.js:424) at Array.forEach () at behavior.js:111 at Array.forEach () at behavior.js:107 at Array.forEach () at Object.applySubtree (behavior.js:93) at select.js:269 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-56479) Exception is thrown when trying to parse unhandled events
Title: Message Title lucamilanesio closed an issue as Fixed Jenkins / JENKINS-56479 Exception is thrown when trying to parse unhandled events Change By: lucamilanesio Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56479) Exception is thrown when trying to parse unhandled events
Title: Message Title lucamilanesio started work on JENKINS-56479 Change By: lucamilanesio Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56479) Exception is thrown when trying to parse unhandled events
Title: Message Title lucamilanesio updated JENKINS-56479 Jenkins / JENKINS-56479 Exception is thrown when trying to parse unhandled events Change By: lucamilanesio Status: In Review Resolved Resolution: Fixed Released As: gerrit-code-review-0.3.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56479) Exception is thrown when trying to parse unhandled events
Title: Message Title lucamilanesio updated JENKINS-56479 Jenkins / JENKINS-56479 Exception is thrown when trying to parse unhandled events Change By: lucamilanesio Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56442) Use agent slave pod label value instead of key
Title: Message Title
Todd Lyons commented on JENKINS-56442
Re: Use agent slave pod label value instead of key
I had considered this as another possible option: ```
$ git diff src/main/java/org/csanchez/jenkins/plugins/kubernetes/PodTemplate.java
diff --git a/src/main/java/org/csanchez/jenkins/plugins/kubernetes/PodTemplate.java b/src/main/java/org/csanchez/jenkins/plugins/kubernetes/PodTemplate.java
index 4cdecb0..74881fe 100644
--- a/src/main/java/org/csanchez/jenkins/plugins/kubernetes/PodTemplate.java
+++ b/src/main/java/org/csanchez/jenkins/plugins/kubernetes/PodTemplate.java
@@ -360,6 +360,7 @@ public class PodTemplate extends AbstractDescribableImpl implements
if (!labelSet.isEmpty()) {
for (LabelAtom label : labelSet) {
// builder.put(label == null ? DEFAULT_ID : "jenkins/" + label.getName(), "true");
+ builder.put(label == null ? DEFAULT_ID : "jenkins_build", label.getName());
}
}
return builder.build();
``` But I felt it was kind of stupid to even consider maintaining my own mods to a jenkins plugin, and instead make the log shipper do the transformation work. I struggle with the `if (!labelSet.isEmpty())` logic, and the getLabelsMap() in general. I think if we can specify our own label, probably in the config where we define the Kube “cloud”, it would possibly get around all of this. I never explored if there is in fact a way to do that from the config UI (or even if I was properly reading that function).
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
[JIRA] (JENKINS-56483) Limit local storage utilization
Title: Message Title Pablo Gomez created an issue Jenkins / JENKINS-56483 Limit local storage utilization Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-03-08 14:58 Environment: Jenkins 2.105 Labels: plugin Priority: Minor Reporter: Pablo Gomez Hi, I am using kubernetes plugin to provision dynamically Jenkins slaves in our Openshift cluster. We configured our pods to use a persistent storage to store Jenkins tools and caches (i.e. maven local repository). Workspaces are stored in EmptyDir volume. We also configured the plugin to destroy pods after 30 minutes idle. We are having problems because there are jobs the generate big binaries, so when a pod runs several jobs it may take a lot of ephemeral storage in the Openshift node and our Openshift administrators are complaining. Is it possible to limit the local storage that a pod can take ? I suggest as an improvement that, after each build, the plugin checks storage consumption of the pod. If it is higher than certain threshold, then the slave will be deleted.
[JIRA] (JENKINS-56442) Use agent slave pod label value instead of key
Title: Message Title Todd Lyons commented on JENKINS-56442 Re: Use agent slave pod label value instead of key I too had to work through this in Dec 2018 and worked with Eric in the slack channel discussing it. I couldn't get it to work with logstash and filebeats, in any combination. Instead in the Kube stack that runs our Jenkins builders, I had to install and configure fluentd and use inline ruby scripting to morph the fields. I had to capture everything after the `jenkins/(.+)`, create a new key "jenkins_build=$1". What I had to do to accomplish it is documented here: https://gist.github.com/mrballcb/c1a8ff4132224e654e85aad80f3a0fec 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-56482) custom name variable seems to not working
Title: Message Title
Omega BAVEDILA-KATUMUA created an issue
Jenkins / JENKINS-56482
custom name variable seems to not working
Issue Type:
Bug
Assignee:
Azure DevOps
Components:
azure-credentials-plugin
Created:
2019-03-08 14:31
Environment:
Azure Credentials 1.6.0 Jenkins ver. 2.150.3 Centos 7.4
Labels:
plugin azure-jenkins
Priority:
Minor
Reporter:
Omega BAVEDILA-KATUMUA
Hello, Before, I used Environment variables in Jenkins configuration to set Azure credentials and my terraform init worked. I installed the Azure credentials in order to use several tenant credentials. but my terraform init complain this:
Error configuring the backend "azurerm": resource_group_name and credentials must be provided when access_key is absent
when I set back Environment variables in Jenkins, everything works. this is my pipeline script: --- def checkout() { stage('Clone repository') { git branch: 'dev', credentialsId: 'gitalb-token-ci', url: 'https://url.git' sh "ls -lat" } } def terraformFmt() { stage('Terraform fmt') { sh 'terraform fmt' } } def terraformInit() { stage('Terraform Init') { sh "az login --service-principal -u $CLIENT_ID -p $CLIENT_SECRET -t $TENANT_ID" sh "az account set -s $SUBS_ID" sh "terraform init" } } def terraformPlan() {
[JIRA] (JENKINS-56480) Threads in TIMED_WAITING causing build agents to hold on to completed tasks
Title: Message Title Bill McMath updated an issue Jenkins / JENKINS-56480 Threads in TIMED_WAITING causing build agents to hold on to completed tasks Change By: Bill McMath Summary: Threads in TIMED_WAITING causing build agents to hold on to completed taks tasks 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-56481) Detached plugins override embedded ones
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-56481 Detached plugins override embedded ones Issue Type: Bug Assignee: Raul Arabaolaza Components: plugin-compat-tester Created: 2019-03-08 14:22 Priority: Minor Reporter: Raul Arabaolaza After https://github.com/jenkinsci/plugin-compat-tester/commit/76930e518a7a369ae0709e1e9be94dc5c7c83b15 PCt inspects detached plugins also, but if a plugin is present as an embedded one and as detached the detached one wrongly overrides the embedded one Add Comment
[JIRA] (JENKINS-56481) Detached plugins override embedded ones
Title: Message Title Raul Arabaolaza started work on JENKINS-56481 Change By: Raul Arabaolaza Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53757) Exec Failure: Expected HTTP 101 response but was '403 Forbidden'
Title: Message Title Angel Bermudez commented on JENKINS-53757 Re: Exec Failure: Expected HTTP 101 response but was '403 Forbidden' For got to mention I'm on kubernetes-plugin 1.13.5, Jenkins Master 2.138.2. I mimicked the idea Nick Bromfield had for the "clusterrolebinding setup for the jenkins user" and it all worked! 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-53796) Update from winston 2.x to 3.x
Title: Message Title Mrinal Dutta assigned an issue to Unassigned Jenkins / JENKINS-53796 Update from winston 2.x to 3.x Change By: Mrinal Dutta Assignee: Mrinal Dutta 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-53796) Update from winston 2.x to 3.x
Title: Message Title Mrinal Dutta stopped work on JENKINS-53796 Change By: Mrinal Dutta Status: In Progress Open 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-53796) Update from winston 2.x to 3.x
Title: Message Title Mrinal Dutta assigned an issue to Mrinal Dutta Jenkins / JENKINS-53796 Update from winston 2.x to 3.x Change By: Mrinal Dutta Assignee: Mrinal Dutta 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-53532) KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed
Title: Message Title Jean Mertz commented on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed It looks like this change does indeed work. However, it also looks like there's something incorrectly wired in the UI, because as soon as I change any values via the UI, the timeout settings are reset back to 0: 0 0 I can only get it to work again by changing the values from the config.xml file itself, and then reloading the config from disk. 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-53796) Update from winston 2.x to 3.x
Title: Message Title Mrinal Dutta started work on JENKINS-53796 Change By: Mrinal Dutta Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56260) Active Choices Reactive Parameter is showing sometimes empty list
Title: Message Title Madhavi Katreddy commented on JENKINS-56260 Re: Active Choices Reactive Parameter is showing sometimes empty list That screen shot doesn't seem to be relevant to this issue. The working version of config.xml doesn't have the projectName element. The jenkins jobs parameters are provided in the groovy file. So the fetching of values from DB for the active choices are in the groovy file. So, whenever there are changes to this parameter groovy file, this issue is happening( which is active choices list is empty). If I click on apply -> save without changes , its working fine. 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-53788) Javadoc fails on ci.jenkins.io with JDK 11
Title: Message Title Oleg Nenashev commented on JENKINS-53788 Re: Javadoc fails on ci.jenkins.io with JDK 11 https://github.com/jenkinsci/plugin-pom/pull/173 is a workaround proposed by Baptiste Mathus 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-53788) Javadoc fails on ci.jenkins.io with JDK 11
Title: Message Title Oleg Nenashev started work on JENKINS-53788 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53757) Exec Failure: Expected HTTP 101 response but was '403 Forbidden'
Title: Message Title Nick Bromfield commented on JENKINS-53757 Re: Exec Failure: Expected HTTP 101 response but was '403 Forbidden' I managed to fix my issue. Turns out the plugin was configured to look at a proxy rather than the api server. Once the url was changed to look at the api-server and a clusterrolebinding setup for the jenkins user, it all worked. 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-53788) Javadoc fails on ci.jenkins.io with JDK 11
Title: Message Title Oleg Nenashev updated JENKINS-53788 Jenkins / JENKINS-53788 Javadoc fails on ci.jenkins.io with JDK 11 Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53788) Javadoc fails on ci.jenkins.io with JDK 11
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-53788 Javadoc fails on ci.jenkins.io with JDK 11 Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53788) Javadoc fails on ci.jenkins.io with JDK 11
Title: Message Title Oleg Nenashev assigned an issue to Baptiste Mathus Jenkins / JENKINS-53788 Javadoc fails on ci.jenkins.io with JDK 11 Change By: Oleg Nenashev Assignee: Oleg Nenashev Baptiste Mathus 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-56480) Threads in TIMED_WAITING causing build agents to hold on to completed taks
Title: Message Title Bill McMath created an issue Jenkins / JENKINS-56480 Threads in TIMED_WAITING causing build agents to hold on to completed taks Issue Type: Bug Assignee: Unassigned Attachments: Screenshot-stuck-executors.png, threadDump.txt Components: bitbucket-branch-source-plugin Created: 2019-03-08 12:37 Environment: openjdk version "1.8.0_191" OpenJDK Runtime Environment (build 1.8.0_191-b12) OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode) OS: Amazon Linux 2018.03 Jenkins: 2.138 Bitbucket branch source: 2.2.12, 2.4.0, 2.4.2 Priority: Minor Reporter: Bill McMath A few times a day the executors in our build agents are filling up and not "releasing" completed tasks. The job will finish and be marked as success or failure, but the executors are still listed as active in the node, causing other jobs to queue up waiting for a free slot. After tracing through this for a while I think the problem is being caused by the Bitbucket Branch Source plugin, this thought is also being backed up by the fact the none of the jobs that have their code in Github are displaying this behaviour. From looking at a thread dump when this happens I can see we will have 10 threads stuck in TIMED_WAITING "com.cloudbees.jenkins.plugins.bitbucket.hooks.PullRequestHookProcessor$1 Thu Mar 07 15:45:43 UTC 2019 / jenkins.util.Timer 1" Id=20 Group=main TIMED_WAITING" (I have attached a partial thread dump from when this happened yesterday (taken when we rolled back to plugin version 2.2.12)). I'm not sure what is causing this behaviour or how to resolve it, so any help
[JIRA] (JENKINS-56387) Upgrading to 2.150.3 results in No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild()
Title: Message Title lee benhart commented on JENKINS-56387 Re: Upgrading to 2.150.3 results in No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild() Thank you, that does make sense. the job I run to upgrade jenkins is in a pipeline, with postbuild tasks. Once Jenkins comes back from restart and resumes the job, it then fails on the post build. The second run works flawlessly. I will evaluate what I am doing in the post build task, possibly eliminate it so others do not see 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-55642) Create experimental "vanilla" Docker packages for the Vanilla version of JFR
Title: Message Title Francisco Fernández started work on JENKINS-55642 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55642) Create experimental "vanilla" Docker packages for the Vanilla version of JFR
Title: Message Title Francisco Fernández assigned an issue to Francisco Fernández Jenkins / JENKINS-55642 Create experimental "vanilla" Docker packages for the Vanilla version of JFR Change By: Francisco Fernández Assignee: Francisco Fernández 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-56390) Duplicate ChangeLog on Jenkins builds for concurrent builds
Title: Message Title hariprasad Narnavara, updated an issue Jenkins / JENKINS-56390 Duplicate ChangeLog on Jenkins builds for concurrent builds Change By: hariprasad Narnavara, Component/s: workflow-scm-step-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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55663) Extend the Jenkinsfile Runner user documentation
Title: Message Title Francisco Fernández updated JENKINS-55663 Jenkins / JENKINS-55663 Extend the Jenkinsfile Runner user documentation 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56440) Jenkinsfile Runner tests fail on Windows
Title: Message Title Evaristo Gutierrez updated an issue Jenkins / JENKINS-56440 Jenkinsfile Runner tests fail on Windows Change By: Evaristo Gutierrez Labels: triaged 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-56479) Exception is thrown when trying to parse unhandled events
Title: Message Title
F Ponciroli created an issue
Jenkins / JENKINS-56479
Exception is thrown when trying to parse unhandled events
Issue Type:
Bug
Assignee:
lucamilanesio
Components:
gerrit-code-review-plugin
Created:
2019-03-08 10:40
Priority:
Minor
Reporter:
F Ponciroli
Trying to parse unhandled events in the plugin will throw an exception, while it should just skip them. See for example: INFO: Received body: {"project":"test-repo","ref":"refs/meta/config","targetNode":"gerrit-2:9418","type":"ref-replication-scheduled","eventCreatedOn":1552040918}INFO: Received body: {"project":"test-repo","ref":"refs/meta/config","targetNode":"gerrit-2:9418","type":"ref-replication-scheduled","eventCreatedOn":1552040918}Mar 08, 2019 10:28:56 AM org.eclipse.jetty.server.handler.ContextHandler$Context logWARNING: Error while serving http://9588e6bcfeae:8080/gerrit-webhook/java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.IndexDispatcher.dispatch(IndexDispatcher.java:27) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at
[JIRA] (JENKINS-56478) Invalid branch name when running a build on a regular branch
Title: Message Title F Ponciroli created an issue Jenkins / JENKINS-56478 Invalid branch name when running a build on a regular branch Issue Type: Bug Assignee: lucamilanesio Components: gerrit-code-review-plugin Created: 2019-03-08 10:38 Priority: Minor Reporter: F Ponciroli When running a build on a normal branch and not a change the logs show a misleading warning saying that the branch name is not valid, while it should say the branch name is not a change. Add Comment This message was sent
[JIRA] (JENKINS-54942) Source details inference fails on Java 11
Title: Message Title Daniel Spilker updated JENKINS-54942 Jenkins / JENKINS-54942 Source details inference fails on Java 11 Change By: Daniel Spilker Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54942) Source details inference fails on Java 11
Title: Message Title Daniel Spilker updated JENKINS-54942 Jenkins / JENKINS-54942 Source details inference fails on Java 11 Change By: Daniel Spilker Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56477) Selecting only compatible plugins when clicking "All" does not work
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-56477 Selecting only compatible plugins when clicking "All" does not work Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-03-08 10:02 Labels: newbie-friendly Priority: Minor Reporter: Daniel Beck See https://github.com/jenkinsci/jenkins/pull/3715#issuecomment-470873111 https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/PluginManager/table.jelly#L108...L120 Add Comment
[JIRA] (JENKINS-56462) pipelineJob does not support trim option for stringParam
Title: Message Title
Jean-Philippe HAUTIN updated an issue
Jenkins / JENKINS-56462
pipelineJob does not support trim option for stringParam
Change By:
Jean-Philippe HAUTIN
*context*I am trying to define a string parameter with a trim option set to true in a pipelineJob (inspired from syntax of implementation done in JENKINS-47115). {code:java}pipelineJob { ... parameters {stringParam('OWNER', 'team1', 'Team', true) } ...}{code} When I run the job, I got a job failure : {noformat} Processing DSL script jenkins-jobs/main_jobdsl.groovy(main_jobdsl.groovy, line 88) No signature of method: javaposse.jobdsl.dsl.helpers.BuildParametersContext.stringParam() is applicable for argument types: (java.lang.String, java.lang.String, java.lang.String, java.lang.Boolean) values: [OWNER, team1, Team, ...]Possible solutions: stringParam(java.lang.String, java.lang.String, java.lang.String), stringParam(java.lang.String, java.lang.String), stringParam(java.lang.String), runParam(java.lang.String, java.lang.String, java.lang.String), runParam(java.lang.String, java.lang.String, java.lang.String, java.lang.String).{noformat} looking at the code of the BuildParametersContext, I see the trim option is not managed in the method stringParam. created PR : https://github.com/jenkinsci/job-dsl-plugin/pull/1169
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56227) deployment successful but `java.lang.LinkageError` causes the build to fail
Title: Message Title Oleg Nenashev commented on JENKINS-56227 Re: deployment successful but `java.lang.LinkageError` causes the build to fail Kirat SinghIf you see any issues with upgrading Jenkins to Java 11 according to the https://jenkins.io/doc/administration/requirements/upgrade-java-guidelines guidelines, please submit a ticket about it with reproduction steps. We will appreciate any feedback about such upgrade issues CC Adrien Lecharpentier 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-56476) multi-branch pipeline creates new job for tag but job is not executed
Title: Message Title Erwin Dondorp created an issue Jenkins / JENKINS-56476 multi-branch pipeline creates new job for tag but job is not executed Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-03-08 09:42 Environment: Jenkins ver. 2.167, Git plugin 3.9.3, Pipeline Multibranch 2.20 (and several others) (everything up-to-date at this time) Labels: pipeline Priority: Major Reporter: Erwin Dondorp Multibranch pipeline works as expected for branches. Jobs are automatically created for new branches, build on any updates and deleted when the branch is removed. For TAGS, the situation is different. Jobs are automatically created for new tags (ok). But there is never a build triggered automatically. the job is deleted when te tag is deleted though. A simple manual build works properly; but automation is preferred of course.
[JIRA] (JENKINS-56387) Upgrading to 2.150.3 results in No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild()
Title: Message Title Thomas Keller commented on JENKINS-56387 Re: Upgrading to 2.150.3 results in No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild() The pipeline model definition plugin changed this method in v1.3.5, so when you update to this (or a later) version of the plugin while having a pipeline build in-flight, this single build will fail once it is resumed when Jenkins was restarted after the update was installed. Subsequent builds will then run on the new plugin code only and succeed. I understand as well that this is suboptimal (and I wonder if the whole "serialize builds" thing doesn't add more complexity and corner cases to Jenkins than it does good things), but at least the issue is not permanent. 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.
