[JIRA] (JENKINS-55905) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Jan Hoppe created an issue Jenkins / JENKINS-55905 Git Plugin 3.9.2 cannot clone remote repo Issue Type: Bug Assignee: Mark Waite Attachments: config.xml Components: git-plugin Created: 2019-02-01 06:58 Priority: Minor Reporter: Jan Hoppe Clone works with 3.9.1. I restored this version. Checking out Revision 3798afd32ccac880988e2c065f0445454e42dd95 (origin/master) Commit message: "#DC Added commits from SIG-Signa SIG-BIN-TestDaten to master" FATAL: not implemented yet Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from kie-jenkinsbld9.ceu.corp.heidelberg.com/10.51.200.115:57675 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserResponse.retrieve(UserRequest.java:389) at hudson.remoting.Channel.call(Channel.java:955) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283) at com.sun.proxy.$Proxy114.setupSubmoduleUrls(Unknown Source) at org.jenkinsci.plugins.gitclient.RemoteGitImpl.setupSubmoduleUrls(RemoteGitImpl.java:655) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:101) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1257) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1819) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at
[JIRA] (JENKINS-55900) Java memory mishandling identified
Title: Message Title Yevhen Bulatnikov updated an issue Jenkins / JENKINS-55900 Java memory mishandling identified Change By: Yevhen Bulatnikov Environment: docker container lts-alpine all 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-55900) Java memory mishandling identified
Title: Message Title Yevhen Bulatnikov updated an issue Jenkins / JENKINS-55900 Java memory mishandling identified Change By: Yevhen Bulatnikov Priority: Minor Major 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-55900) Java memory mishandling identified
Title: Message Title
Yevhen Bulatnikov updated an issue
Jenkins / JENKINS-55900
Java memory mishandling identified
Change By:
Yevhen Bulatnikov
I was running Jenkins in docker container lts-alpine on low memory instance on cloud. At the beginning it looked working well. But after some period of time container stopped. I started it again and it stopped after some time again even I was doing nothing there.I realized that OutOfMemory happens there. I decided to investigate locally using YourKit.It showed that hudson.model.TimeSeries.update() during short time (~ 15 minutes) allocates totally several gigabytes.Of course GC is handling that. But looking at the code I think memory allocation can be handled much better.{code:java}public void update(float newData) {float data = "" + newData*(1-decay);float[] r = new float[Math.min(history.length+1,historySize)];System.arraycopy(history,0,r,1,Math.min(history.length,r.length-1));r[0] = data;history = r;}{code}As for me this code looks like updating fixed sized queue. And each time new array created when only one element should be added. This is bad approach. I would suggest to use EvictingQueue from Google Guava or CircularFifoQueue from Apache Commons, or at least LinkedList with removing last element if size exceeds. Also I found very old bugs related to this. They were closed without any analysis: # JENKINS-12333 # JENKINS-8330
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53050) Empty "depth" parameter for shallow cloning is not handled correctly
Title: Message Title René Scheibe updated an issue Jenkins / JENKINS-53050 Empty "depth" parameter for shallow cloning is not handled correctly Change By: René Scheibe Comment: resolved with https://github.com/jenkinsci/git-plugin/pull/614 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-54646) External jars in shared libraries are always executed on master
Title: Message Title Kishore Kumar commented on JENKINS-54646 Re: External jars in shared libraries are always executed on master Tried this and this approve doesn't seem to work. Is there any specific setup that need to done prior to trying this approach. 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-55904) Kubernetes pod template with persistance volume
Title: Message Title
venkatesh kristipati updated an issue
Jenkins / JENKINS-55904
Kubernetes pod template with persistance volume
Change By:
venkatesh kristipati
Hi,we are using jenkins on k8s and running slave on pods using pod template.we want to use DSL language for jenkins and trying to do with volume option with agent on k8s. like below example {code:java}pipeline { agent {kubernetes {label 'jenkins-demo'containerTemplate {name 'dind-jdk8-maven3'image 'eu.gcr.io/jenkins-demo/dind-jdk8-maven3:v4'ttyEnabled truecommand 'cat'} }volumes { type persistentVolumeClaim mountPath '/home/jenkins/workspace' claimName 'jenkins-workspace-pv' readOnly false} } }{code}Is there any possibility to like this or we can just do it with another approach. If we want to write in another format please post an example for 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
[JIRA] (JENKINS-55904) Kubernetes pod template with persistance volume
Title: Message Title
venkatesh kristipati created an issue
Jenkins / JENKINS-55904
Kubernetes pod template with persistance volume
Issue Type:
Task
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2019-02-01 05:05
Environment:
K8s
Priority:
Critical
Reporter:
venkatesh kristipati
Hi, we are using jenkins on k8s and running slave on pods using pod template.we want to use DSL language for jenkins and trying to do with volume option with agent on k8s. like below example
pipeline {
agent {
kubernetes {
label 'jenkins-demo'
containerTemplate {
name 'dind-jdk8-maven3'
image 'eu.gcr.io/jenkins-demo/dind-jdk8-maven3:v4'
ttyEnabled true
command 'cat'
}
}
volumes {
type persistentVolumeClaim
mountPath '/home/jenkins/workspace'
claimName 'jenkins-workspace-pv'
readOnly false
}
}
-
---
}
Is there any possibility to like this or we can just do it with another approach.
[JIRA] (JENKINS-55904) Kubernetes pod template with persistance volume
Title: Message Title venkatesh kristipati started work on JENKINS-55904 Change By: venkatesh kristipati 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-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Nisarg Shah commented on JENKINS-55829 Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API I think error is due to the “Restricted(NoExternalUse.class)” as shown in the tests. And please can you help me that how can I compile and run the complete code on my local computer and can do all these tests on local? 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-49897) gerrit-plugin pr branch names are incorrectly name
Title: Message Title Jose Sa commented on JENKINS-49897 Re: gerrit-plugin pr branch names are incorrectly name I also consider that we should only consider the gerrit review id (6 digits number) as the branch name, and treat it the same way as the other actual branches. This way all individual patches, manual replays, etc... will be displayed in the history of that branch, retaining a build history while the review is open. As it is right now, once a new patchset is uploaded previous related builds are destroyed and only the latest patchset "job" is available, effectively loosing history and for me that is a serious bug. 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-55462) "shelve project" button missing for all non-admin users
Title: Message Title Roger Wang commented on JENKINS-55462 Re: "shelve project" button missing for all non-admin users Hello Pierre, the development team think that should be doable. So, just wondering when could we have a trial? Thank you very much! Roger 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-43563) Git plugin does not set user in pipeline
Title: Message Title Lei JIANG commented on JENKINS-43563 Re: Git plugin does not set user in pipeline It that possible to prioritise this issue please. 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-55903) High latency networks add extra time to a job completion
Title: Message Title Manuel Corona created an issue Jenkins / JENKINS-55903 High latency networks add extra time to a job completion Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin, remoting Created: 2019-01-31 23:55 Environment: Hybrid deployment (on-prem and AWS) Jenkins version: 2.150.2 Kubernetes plugin: 1.14.3 JNLP Protocol: Any (tested with 2 and 4) Jenkins Docker Image: 3.27-1 Labels: slave jenkins Priority: Minor Reporter: Manuel Corona When a Jenkins agent is added to a cluster and a job is assigned to it, this job will take some extra time to complete regardless of what the job does. Testing with an empty job on a network with high latency (75ms roundtrip) caused an additional *45 second*s for the empty job to succeed. looking a the console we noticed that the job is not doing any computation.
[JIRA] (JENKINS-55902) Jenkins job executing HP QC Test Set duplicates reporting for the same test in two different situations.
Title: Message Title Jim Sears created an issue Jenkins / JENKINS-55902 Jenkins job executing HP QC Test Set duplicates reporting for the same test in two different situations. Issue Type: Bug Assignee: Daniel Gront Attachments: Jenkins HP QC Plug-in Reporting Bug with logs.docx, JenkinsSystemDetails.txt Components: hp-application-automation-tools-plugin Created: 2019-01-31 23:46 Environment: Production. HP plugin is the latest 5.6.2. Jenkins details are in attached system log. Labels: Jenkins QC Reporting Console Priority: Minor Reporter: Jim Sears Attached word doc provides examples and details. The test reporting in the log lists the wrong test instance or wrong test name as duplicates. Two scenarios 1) Multiple test instances in QC Test Set are listed as only the last test instance in the console output. Given 9 instances of a test, the log only says the test instance [9] has passed. Test 1-8 is not mentioned for the pass/fail. The other tests are mentioned prior for "about to run on Hostname" and "x number of tests in test set". It is only in the status results where the issue appears. 2) 200 plus test in Test Set and in the Test execution status of the console towards the very end of the console output, the same test is listed 200 times. The other 199 tests in the test set are not listed. Only the one or two tests are mentioned. Again, the execution
[JIRA] (JENKINS-55900) Java memory mishandling identified
Title: Message Title
Yevhen Bulatnikov updated an issue
Jenkins / JENKINS-55900
Java memory mishandling identified
Change By:
Yevhen Bulatnikov
I was running Jenkins in docker container lts-alpine on low memory instance on cloud. At the beginning it looked working well. But after some period of time container stopped. I started it again and it stopped after some time again even I was doing nothing there.I realized that OutOfMemory happens there. I decided to investigate locally using YourKit.It showed that hudson.model.TimeSeries.update() during short time (~ 15 minutes) allocates totally several gigabytes.Of course GC is handling that. But looking at the code I think memory allocation can be handled much better.{code:java}public void update(float newData) {float data = "" + newData*(1-decay);float[] r = new float[Math.min(history.length+1,historySize)];System.arraycopy(history,0,r,1,Math.min(history.length,r.length-1));r[0] = data;history = r;}{code}As for me this code looks like updating fixed sized queue. I would suggest to use EvictingQueue from Google Guava or CircularFifoQueue from ApacheCommons Apache Commons , or at least LinkedList with removing last element if size exceeds. Also I found very old bugs related to this. They were closed without any analysis: # JENKINS-12333 # JENKINS-8330
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55901) Branch Rebasing Does not Update config.xml or Options
Title: Message Title Junze He created an issue Jenkins / JENKINS-55901 Branch Rebasing Does not Update config.xml or Options Issue Type: Bug Assignee: Denis Saponenko Components: pipeline, pipeline-multibranch-defaults-plugin Created: 2019-01-31 22:15 Priority: Minor Reporter: Junze He We removed the compressBuildLog() option from our pipelines after realizing https://issues.jenkins-ci.org/browse/JENKINS-54678 was causing us to not be able to read the logs in the UI after they are compressed. The pipelines created after branching off of master without that option run fine. However, the pipelines created from before the change on master and had to rebase still have the option in their config.xml on master and still compresses the logs. Their Jenkinsfile does not show the option still. We have managed to get around this by either deleting the option from the config.xml or by committing the option, running the pipeline, committing removing the option, and running again. Add Comment
[JIRA] (JENKINS-55900) Java memory mishandling identified
Title: Message Title
Yevhen Bulatnikov updated an issue
Jenkins / JENKINS-55900
Java memory mishandling identified
Change By:
Yevhen Bulatnikov
I was running Jenkins in docker container lts-alpine on low memory instance on cloud. At the beginning it looked working well. But after some period of time container stopped. I started it again and it stopped after some time again even I was doing nothing there. I realized that OutOfMemory happens there. I decided to investigate locally using YourKit. It showed that hudson.model.TimeSeries.update() during short time (~ 15 minutes) allocates totally several gigabytes. Of course GC is handling that. But looking at the code I think memory allocation can be handled much better. {code:java} public void update(float newData) { float data = "" + newData*(1-decay); float[] r = new float[Math.min(history.length+1,historySize)]; System.arraycopy(history,0,r,1,Math.min(history.length,r.length-1)); r[0] = data; history = r;} {code} As for me this code looks like updating fixed sized queue. I would suggest to use EvictingQueue from Google Guava or CircularFifoQueue from ApacheCommons, or at least LinkedList with removing last element if size exceeds. Also I found very old bugs related to this. They were closed without any analysis: # JENKINS-12333 # JENKINS-8330
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54249) GitHub Commit Status Setter - Cannot retrieve Git metadata
Title: Message Title Johan Andersson commented on JENKINS-54249 Re: GitHub Commit Status Setter - Cannot retrieve Git metadata Same here! Error both when starting end finishing a build. ERROR: [GitHub Commit Status Setter] Failed to update commit state on GitHub. Ignoring exception [Cannot retrieve Git metadata for the build] I was using GitHub plugin v1.29.3 both before and after my upgrade when this started. Some of the plugin upgrades I had pending that after installing forced me to do a rollback: Git 3.9.1 -> 4.0.0rc Git client 2.7.3 -> 3.0.0rc GitHub API 1.92 -> 1.95 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-55900) Java memory mishandling identified
Title: Message Title
Yevhen Bulatnikov created an issue
Jenkins / JENKINS-55900
Java memory mishandling identified
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2019-01-31 21:59
Environment:
docker container lts-alpine
Priority:
Minor
Reporter:
Yevhen Bulatnikov
I was running Jenkins in docker container lts-alpine on low memory instance on cloud. At the beginning it looked working well. But after some period of time container stopped. I started it again and it stopped after some time again even I was doing nothing there. I realized that OutOfMemory happens there. I decided to investigate locally using YourKit. It showed that hudson.model.TimeSeries.update() during short time (~ 15 minutes) allocates totally several gigabytes. Of course GC is handling that. But looking at the code I think memory allocation can be handled much better. public void update(float newData) { float data = "" + newData*(1-decay); float[] r = new float[Math.min(history.length+1,historySize)]; System.arraycopy(history,0,r,1,Math.min(history.length,r.length-1)); r[0] = data; history = r; } As for me this code looks like updating fixed sized queue. I would suggest to use EvictingQueue from Google Guava or CircularFifoQueue from ApacheCommons, or at least LinkedList with removing last element if size exceeds. Also I found very old bugs related to this. They were closed without any analysis:
JENKINS-12333
JENKINS-8330
[JIRA] (JENKINS-22566) XML API does not escape/filter invalid characters
Title: Message Title Basil Crow commented on JENKINS-22566 Re: XML API does not escape/filter invalid characters I have written a reproducible test case. 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-55898) Surface pod scheduling failures to the user instead of waiting forever
Title: Message Title Matt Luceen updated an issue Jenkins / JENKINS-55898 Surface pod scheduling failures to the user instead of waiting forever Change By: Matt Luceen Labels: plugin user-experience 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-22566) XML API does not escape/filter invalid characters
Title: Message Title Basil Crow commented on JENKINS-22566 Re: XML API does not escape/filter invalid characters When a build has a parameter whose value contains an invalid XML character, the XML API returns a 500 Internal Server error: org.dom4j.DocumentException: Error on line 1 of document : An invalid XML character (Unicode: 0x1b) was found in the element content of the document. Nested exception: An invalid XML character (Unicode: 0x1b) was found in the element content of the document. at org.dom4j.io.SAXReader.read(SAXReader.java:482) at org.dom4j.io.SAXReader.read(SAXReader.java:365) at hudson.model.Api.doXml(Api.java:117) 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) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:221) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) 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:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Devin Nusbaum updated JENKINS-46507 As of version 2.29 of the Pipeline Nodes and Process Plugin, the default timeout for remote calls is 20 seconds, and the value can be configured using the system property org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep.REMOTE_TIMEOUT. I am marking this ticket as closed since that is the main cause of the issue identified from discussion in the comments (thanks Andrew a!). If this issue is still occurring frequently for someone after increasing that value, please comment and we can investigate further. Jenkins / JENKINS-46507 Parallel Pipeline random java.lang.InterruptedException Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-durable-task-step 2.29 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55899) Jenkins CasC ec2 plugin configuration doesn't work
Title: Message Title Gilad Shefer closed an issue as Not A Defect Jenkins / JENKINS-55899 Jenkins CasC ec2 plugin configuration doesn't work Change By: Gilad Shefer Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55899) Jenkins CasC ec2 plugin configuration doesn't work
Title: Message Title Gilad Shefer commented on JENKINS-55899 Re: Jenkins CasC ec2 plugin configuration doesn't work My bad. the problem was that other things were not been configured correctly and I didn't wait for the message "this config can be applied". Closing... 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-36547) Queue.Task.getFullDisplayName is a poor choice of key for LoadBalancer.CONSISTENT_HASH
Title: Message Title Devin Nusbaum assigned an issue to Joerg Schwaerzler Jenkins / JENKINS-36547 Queue.Task.getFullDisplayName is a poor choice of key for LoadBalancer.CONSISTENT_HASH Change By: Devin Nusbaum Assignee: Joerg Schwaerzler 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-36547) Queue.Task.getFullDisplayName is a poor choice of key for LoadBalancer.CONSISTENT_HASH
Title: Message Title Devin Nusbaum resolved as Fixed The Pipeline side of this was just released in version 2.29 of the Pipeline Nodes and Processes Plugin. Jenkins / JENKINS-36547 Queue.Task.getFullDisplayName is a poor choice of key for LoadBalancer.CONSISTENT_HASH Change By: Devin Nusbaum Status: Open Resolved Resolution: Fixed Released As: jenkins 2.145, workflow-durable-task-step 2.29 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-54249) GitHub Commit Status Setter - Cannot retrieve Git metadata
Title: Message Title Adam Stracener commented on JENKINS-54249 Re: GitHub Commit Status Setter - Cannot retrieve Git metadata Same issue here 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-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title Devin Nusbaum commented on JENKINS-55139 Re: ansicolor 0.6.0 shows terminal escape sequences in console log I just released 0.6.2 with a change that should fix this issue for the cases I am aware of. If you are still seeing it after the upgrade, please copy-and-paste some of the broken output from Jenkins here (preferably replacing literal occurrences of the ASCII character 0x1b with the text 0x1b so we can see what is happening to the escape sequences). 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-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title Devin Nusbaum updated JENKINS-55139 Jenkins / JENKINS-55139 ansicolor 0.6.0 shows terminal escape sequences in console log Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: ansicolor 0.6.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-55805) Warnings Next Generation Plugin is slow at parsing the log output
Title: Message Title Ronald Brill commented on JENKINS-55805 Re: Warnings Next Generation Plugin is slow at parsing the log output Maybe using the regex with the first e.g. 400 chars of a line to make sure this is a candidate for a deeper analysis is an option to make the parser faster. 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-55805) Warnings Next Generation Plugin is slow at parsing the log output
Title: Message Title Ronald Brill commented on JENKINS-55805 Re: Warnings Next Generation Plugin is slow at parsing the log output Have removed the Java parser, not the JavaDoc parser is the blocker 20:39:49 [JavaDoc] Sleeping for 5 seconds due to JENKINS-32191... 20:39:54 [JavaDoc] Parsing console log (workspace: '/var/lib/jenkins/workspace/HtmlUnit') 20:50:24 [JavaDoc] Attaching ResultAction with ID 'javadoc-warnings' to run 'HtmlUnit #268'. 20:50:24 [JavaDoc] Using reference build 'HtmlUnit #267' to compute new, fixed, and outstanding issues 20:50:24 [JavaDoc] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0 20:50:24 [JavaDoc] No quality gates have been set - skipping 20:50:24 [JavaDoc] Health report is disabled - skipping 20:50:24 [JavaDoc] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34426) Changing project-based settings for AD-Groups shows error
Title: Message Title Ben Primrose commented on JENKINS-34426 Re: Changing project-based settings for AD-Groups shows error I'm getting this on v2.11 and v2.10 (tried downgrading). I'm using role-based security as well. 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-37341) Add support of z/OS USS to sh step
Title: Message Title Devin Nusbaum updated JENKINS-37341 This feature was just added in version 1.29 of the Durable Task plugin. Jenkins / JENKINS-37341 Add support of z/OS USS to sh step Change By: Devin Nusbaum Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37341) Add support of z/OS USS to sh step
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-37341 Add support of z/OS USS to sh step Change By: Devin Nusbaum Released As: durable-task 1.29 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Nisarg Shah edited a comment on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master [~batmat] [~jglick]Due to some issues I have deleted my previous repo and due to that my old PR got deleted.Here is my new PR : [ https://github.com/jenkinsci/jenkins/pull/3874 ] 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Nisarg Shah commented on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master Baptiste Mathus Jesse Glick Due to some issues I have deleted my previous repo and due to that my old PR got deleted. Here is my new PR : https://github.com/jenkinsci/jenkins/pull/3874 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-55899) Jenkins CasC ec2 plugin configuration doesn't work
Title: Message Title Gilad Shefer created an issue Jenkins / JENKINS-55899 Jenkins CasC ec2 plugin configuration doesn't work Issue Type: Bug Assignee: Ewelina Wilkosz Attachments: image-2019-01-31-13-04-55-622.png Components: configuration-as-code-plugin Created: 2019-01-31 18:05 Labels: plugin jenkins configuration-as-code Priority: Minor Reporter: Gilad Shefer I'm trying to configure EC2 plugin but for some reason it doesn't work and the I can't see the new cloud after I'm running CasC Jenkins version: 2.154 This is the content of the file that I'm running the CasC with: plugins: required: ec2: 1.40.1 sites: - id: "default" url: "https://updates.jenkins.io/update-center.json"jenkins: agentProtocols: - "JNLP4-connect" - "Ping" clouds: - amazonEC2: cloudName: "ec2" instanceCapStr: 20 region: "us-west-2" # this shouldn't be needed, since without explicit creds this should already be used # but let's be explicit to avoid issues. useInstanceProfileForCredentials: true # Reminder: the following key has multiple lines privateKey: "PRIVATE_KEY" templates: - description: "Auto configured EC2 Agent, yay again" zone: "us-west-2" ami: "ami-0c6bb742864ffa3f3" labelString: "test yey" type: "T2Xlarge" securityGroups:
[JIRA] (JENKINS-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Nisarg Shah commented on JENKINS-55829 Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API Oleg Nenashev PR : https://github.com/jenkinsci/jenkins/pull/3873 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-44924) pipeline groovy script - Sort a list with custom comparator or closure not sorting
Title: Message Title Daniel Issac commented on JENKINS-44924 Re: pipeline groovy script - Sort a list with custom comparator or closure not sorting Any updates on this.?I agree with Roman Sinyakov.This seems to be a serious issue which needs to be 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-55898) Surface pod scheduling failures to the user instead of waiting forever
Title: Message Title Nathan Lowe created an issue Jenkins / JENKINS-55898 Surface pod scheduling failures to the user instead of waiting forever Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-01-31 17:55 Environment: jenkins/jenkins:lts-alpine (2.150.1) Kubernetes Plugin 1.14.3 Priority: Major Reporter: Nathan Lowe Every now and then developers will either make environmental changes or changes to the pod spec that cause the pod to fail to schedule. I've seen this most frequently happen when: A developer removes a container image from an internal registry that is referenced in the pod spec without updating the pod spec in all branches (The container will get stuck in ErrImagePull) A developer adds a container to the pod spec without overriding the entrypoint. When the container exits, kubernetes kills and restarts the pod before jenkins sees the pod becoming ready It would be awesome if the kubernetes plugins could detect these failures and fail the build if this happens so the build doesn't run forever and we don't block other builds from scheduling. This is especially useful for users who don't have access to the kubernetes api to inspect *why* their builds aren't running.
[JIRA] (JENKINS-55870) MercurialSCM hard codes --clean in updates
Title: Message Title Sanjay Bhandari updated an issue Jenkins / JENKINS-55870 MercurialSCM hard codes --clean in updates Change By: Sanjay Bhandari Summary: mercurial-scm MercurialSCM hard codes --clean in updates Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55897) Build time estimation continues while waiting for executor in pipeline
Title: Message Title Dominik Zäuner created an issue Jenkins / JENKINS-55897 Build time estimation continues while waiting for executor in pipeline Issue Type: Bug Assignee: Unassigned Components: pipeline, pipeline-view-plugin Created: 2019-01-31 16:46 Environment: Jenkins 2.162 Priority: Minor Reporter: Dominik Zäuner When a pipeline build is started on master and halts while "waiting for next free executor" it correctly moves from the "Build Executor Status" widget to "Build Queue" saying "part of job". But in the Job view in the widget "Build History" and "Stage View" although, the estimation keeps running. Add Comment
[JIRA] (JENKINS-55896) Jenkins is not triggering build on any pullrequest created in bitbucket repo
Title: Message Title Hassaan Sohail created an issue Jenkins / JENKINS-55896 Jenkins is not triggering build on any pullrequest created in bitbucket repo Issue Type: Bug Assignee: Christian Del Monte Components: bitbucket-pullrequest-builder-plugin, bitbucket-push-and-pull-request-plugin, generic-webhook-trigger-plugin Created: 2019-01-31 16:32 Environment: Bitbucket Cloud and Jenkins Labels: jenkins Plugins pullrequestbuilder Priority: Blocker Reporter: Hassaan Sohail I am using Bitbucket cloud service for repositories and Jenkins for builds. I am able to run my pipeline and trigger automatically when a new push chnages to a specified branch and have multiple jobs. E.g I have dev, stage, production environments for android builds. Whenever some one push to those branches in Bitbucket cloud, so jenkins is able to trigger build automatically against its branches. But I have another job in jenkins which is created for developers to test their code before merging it into other branch. It is pr job which must execute when someone created any pull request then it should trigger build against it but it is not working. I have installed all the plugins mentioned above to fulfill my requirement but jenkins is not able to trigger build when someone created a pull request from any branch to any branch. Please suggest some configurations on jenkins side so that it will be able to trigger build when a new pr created or updated.
[JIRA] (JENKINS-55295) Add support of Timeout option to Jenkinsfile Runner
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55295 Add support of Timeout option to Jenkinsfile Runner Change By: Oleg Nenashev Currently Jenkinsfile Runner does not support passing timeout to CLI. In Docker it may be worked around by timing out the Docker container, but in such case there is no way to have a graceful shutdown. timeout() is not enough, because Jenkins may hang before Pipeline even starts. Acceptance criteria: * There is a soft and hard timeout options which may be set via CLI argument or passed via Environment variable (for Docker) * If the option is set, timeout is applied to the execution * Once the soft timeout happens, Jenkins instance termination is invoked (job termination and then instance shutdown) * Once the hard timeout happens, Jenkins instance is forcefully aborted 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-55888) class names are causing issues
Title: Message Title Ulli Hafner commented on JENKINS-55888 Re: class names are causing issues There is another Jira issue about that problem. If you have just one result then the additional ID Parameter is not used in publishIssues. 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-54452) Allow a user to install their own set of plugins
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54452 Allow a user to install their own set of plugins Change By: Oleg Nenashev Issue Type: Task New Feature 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-55323) Payload module classes loaded after Jenkins initialization
Title: Message Title Oleg Nenashev commented on JENKINS-55323 Re: Payload module classes loaded after Jenkins initialization Francisco Fernández: the issue may happen only in edge cases, and there are workarounds for it. So it is not a priority for now. 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-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Nisarg Shah commented on JENKINS-55829 Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API Oleg Nenashev Sorry for the inconvenience occurred in the pull request. There were some issues due to which it happened, so I just closed previous pull request and now I will do two individual PR. 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-37341) Add support of z/OS USS to sh step
Title: Message Title Devin Nusbaum updated JENKINS-37341 Jenkins / JENKINS-37341 Add support of z/OS USS to sh step Change By: Devin Nusbaum Status: In Progress 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-37341) Add support of z/OS USS to sh step
Title: Message Title Devin Nusbaum commented on JENKINS-37341 Re: Add support of z/OS USS to sh step PR 80 was merged, so z/OS support will be available in the next release. 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-37341) Add support of z/OS USS to sh step
Title: Message Title Devin Nusbaum updated JENKINS-37341 Jenkins / JENKINS-37341 Add support of z/OS USS to sh step Change By: Devin Nusbaum Status: In Review 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-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Alex Earl commented on JENKINS-55722 Re: jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection Does your server support sftp? 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-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Raphael Pionke updated JENKINS-55202 I tested the new release of the JAXB Plugin and it works with and without a container. I will release the plugin in the next few days. Thanks a lot for your effort! Jenkins / JENKINS-55202 Performance Signature Plugin: JAXB API is missing with Java 11 Change By: Raphael Pionke Status: Open Fixed but Unreleased Assignee: Raphael Pionke 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
[JIRA] (JENKINS-55681) Release the JAXB Plugin
Title: Message Title Raphael Pionke updated JENKINS-55681 I tested the new release of the JAXB Plugin and it works with and without a container. I will release the plugin in the next few days. Thanks a lot for your effort! Jenkins / JENKINS-55681 Release the JAXB Plugin Change By: Raphael Pionke Status: In Progress 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-55895) Mercurial cache on stash and unstash is missing
Title: Message Title Javier Raez created an issue Jenkins / JENKINS-55895 Mercurial cache on stash and unstash is missing Issue Type: Bug Assignee: Unassigned Components: mercurial-plugin Created: 2019-01-31 15:13 Priority: Major Reporter: Javier Raez When using Mercurial as SCM, with pipelines and the "stash" and "unstash" step, Mercurial is creating two different caches, one on the master and another one on the agent. The problem is that when we "stash", the pipeline only get the cache folder from the workspace. When we do an "unstash" the cache from workspace is recovered but there is some information in the master cache that is not recovered and this makes that the works fail. Add Comment
[JIRA] (JENKINS-55681) Release the JAXB Plugin
Title: Message Title Raphael Pionke updated JENKINS-55681 Jenkins / JENKINS-55681 Release the JAXB Plugin Change By: Raphael Pionke Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Nisarg Shah commented on JENKINS-55829 Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API Thank you. 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-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Nisarg Shah assigned an issue to Nisarg Shah Jenkins / JENKINS-55829 Expose AbstractCIBase#disabledAdministrativeMonitors as internal API Change By: Nisarg Shah Assignee: Nisarg Shah 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-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Baptiste Mathus stopped work on JENKINS-55202 Change By: Baptiste Mathus 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-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Baptiste Mathus updated JENKINS-55202 Jenkins / JENKINS-55202 Performance Signature Plugin: JAXB API is missing with Java 11 Change By: Baptiste Mathus Status: In Review 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-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-55202 Performance Signature Plugin: JAXB API is missing with Java 11 Change By: Baptiste Mathus Assignee: 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-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Baptiste Mathus stopped work on JENKINS-55202 Change By: Baptiste Mathus 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-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Baptiste Mathus updated JENKINS-55202 Jenkins / JENKINS-55202 Performance Signature Plugin: JAXB API is missing with Java 11 Change By: Baptiste Mathus Status: In Review 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-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Baptiste Mathus commented on JENKINS-55202 Re: Performance Signature Plugin: JAXB API is missing with Java 11 Raphael Pionke can you please retest with https://github.com/jenkinsci/performance-signature-dynatrace-plugin/pull/7 ? 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-55894) Starting and stopping existing instances
Title: Message Title Daniel Stoian created an issue Jenkins / JENKINS-55894 Starting and stopping existing instances Issue Type: New Feature Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-01-31 14:49 Priority: Major Reporter: Daniel Stoian Hello, We use Terraform and Chef to provision and configured all Jenkins slaves. Therefore the provision part of the plugin is not essential for us. We are more interested in starting and stopping existing instances based on the load of the cluster using our own instances. If possible, please add the functionally to scale the cluster using existing instances: add a field to configure a list of existing instances (or a tag) start instances from the predefined list (or from the list of instances having the same tag) don't do nothing else except of changing the instance state to start or stop Thank you. Add Comment
[JIRA] (JENKINS-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Baptiste Mathus updated JENKINS-55202 Jenkins / JENKINS-55202 Performance Signature Plugin: JAXB API is missing with Java 11 Change By: Baptiste Mathus 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-55826) Add '-f' to 'p4 client -d' with cleanup/p4cleanup
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-55826 Add '-f' to 'p4 client -d' with cleanup/p4cleanup Change By: Karl Wirth I am creating new workspace using template workspace. template Template workspace is locked. So created workspace is also locked. In this situation, How to delete workspace?I used " cleanup true " in pipeline. I think I have to change workspace's option every time or you can provide cleanup true with force option. 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-55826) Add '-f' to 'p4 client -d' with cleanup/p4cleanup
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-55826 Add '-f' to 'p4 client -d' with cleanup/p4cleanup Change By: Karl Wirth Labels: P4_VERIFY 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-55826) Add '-f' to 'p4 client -d' with cleanup/p4cleanup
Title: Message Title Karl Wirth assigned an issue to Unassigned Jenkins / JENKINS-55826 Add '-f' to 'p4 client -d' with cleanup/p4cleanup Change By: Karl Wirth Assignee: Karl Wirth 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-55826) how to delete workspace forcely?
Title: Message Title Karl Wirth commented on JENKINS-55826 Re: how to delete workspace forcely? Hi Hokwang Lee I apologise. My testing was incorrect. My system was failing to delete the client but the error was hidden under '+'. P4 Task: remove client: jenkins-dockervm-0001o1pa9npua-Pipeline_Locked_Template_Workspace-0 ... p4 client -d jenkins-dockervm-0001o1pa9npua-Pipeline_Locked_Template_Workspace-0 - p4 client -d jenkins-dockervm-0001o1pa9npua-Pipeline_Locked_Template_Workspace-0 Client 'jenkins-dockervm-0001o1pa9npua-Pipeline_Locked_Template_Workspace-0' is locked and can't be deleted. I will therefore pass this to developers as a request to add '-f' to 'client -d'. 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-55826) Add '-f' to 'p4 client -d' with cleanup/p4cleanup
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-55826 Add '-f' to 'p4 client -d' with cleanup/p4cleanup Change By: Karl Wirth Summary: how Add '-f' to delete workspace forcely? 'p4 client -d' with cleanup/p4cleanup 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-55840) Doxygen parser not fully compatible with warnings-ng-plugin
Title: Message Title Torben Stößel commented on JENKINS-55840 Re: Doxygen parser not fully compatible with warnings-ng-plugin This was executed on Ubuntu /srv/www/jenkins/workspace/code_master/pump/external/specific/arm/cmsis/arm_math.h:5110: warning: explicit link request to 'define' could not be resolved /srv/www/jenkins/workspace/code_master/pump/external/specific/arm/cmsis/arm_math.h:2257: warning: argument 'pSrc' of command @param is not found in the argument list of arm_bitreversal_q15(q15_t *pSrc16, uint32_t fftLen, uint16_t bitRevFactor, uint16_t *pBitRevTab) /srv/www/jenkins/workspace/code_master/pump/external/specific/arm/cmsis/arm_math.h:2265: warning: The following parameters of arm_bitreversal_q15(q15_t *pSrc16, uint32_t fftLen, uint16_t bitRevFactor, uint16_t *pBitRevTab) are not documented: parameter 'pSrc16' /srv/www/jenkins/workspace/code_master/pump/external/specific/arm/cmsis/arm_math.h:2212: warning: argument 'pBitRevTab' of command @param is not found in the argument list of arm_bitreversal_q31(q31_t *pSrc, uint32_t fftLen, uint16_t bitRevFactor, uint16_t *pBitRevTable) /srv/www/jenkins/workspace/code_master/pump/external/specific/arm/cmsis/arm_math.h:2220: warning: The following parameters of arm_bitreversal_q31(q31_t *pSrc, uint32_t fftLen, uint16_t bitRevFactor, uint16_t *pBitRevTable) are not documented: parameter 'pBitRevTable' /srv/www/jenkins/workspace/code_master/pump/external/specific/arm/cmsis_dsp/MatrixFunctions/arm_mat_inverse_f32.c:70: warning: argument 'src' of command @param is not found in the argument list of arm_mat_inverse_f32(const arm_matrix_instance_f32 *pSrc, arm_matrix_instance_f32 *pDst) /srv/www/jenkins/workspace/code_master/pump/external/specific/arm/cmsis_dsp/MatrixFunctions/arm_mat_inverse_f32.c:70: warning: argument 'dst' of command @param is not found in the argument list of arm_mat_inverse_f32(const arm_matrix_instance_f32 *pSrc, arm_matrix_instance_f32 *pDst) /srv/www/jenkins/workspace/code_master/pump/external/specific/arm/cmsis_dsp/StatisticsFunctions/arm_min_q7.c:48: warning: argument 'result' of command @param is not found in the argument list of arm_min_q7(q7_t *pSrc, uint32_t blockSize, q7_t *pResult, uint32_t *pIndex) /srv/www/jenkins/workspace/code_master/pump/external/specific/arm/cmsis_dsp/StatisticsFunctions/arm_min_q7.c:48: warning: argument 'index' of command @param is not found in the argument list of arm_min_q7(q7_t *pSrc, uint32_t blockSize, q7_t *pResult, uint32_t *pIndex) /srv/www/jenkins/workspace/code_master/pump/external/specific/arm/stm32f4xx/libinc/stm32f4xx_flash.h:354: warning: The following parameters of FLASH_ITConfig(uint32_t FLASH_IT, FunctionalState NewState) are not documented: parameter 'NewState' /srv/www/jenkins/workspace/code_master/pump/external/specific/arm/stm32f4xx/libsrc/stm32f4xx_gpio.c:518: warning: End of list marker found without any preceding list items /srv/www/jenkins/workspace/code_master/pump/external/specific/arm/stm32f4xx/libinc/stm32f4xx_i2c.h:599: warning: The following parameters of I2C_ReadRegister(I2C_TypeDef *I2Cx, uint8_t I2C_Register) are not documented: parameter 'I2Cx' /srv/www/jenkins/workspace/code_master/pump/external/specific/arm/stm32f4xx/libsrc/stm32f4xx_flash.c:966: warning: The following parameters of FLASH_ITConfig(uint32_t FLASH_IT, FunctionalState NewState) are not documented: parameter 'NewState' /srv/www/jenkins/workspace/code_master/pump/external/specific/arm/stm32f4xx/libsrc/stm32f4xx_gpio.c:518: warning: End of list marker found without any preceding list items
[JIRA] (JENKINS-55879) Declarative SCM checkout not running on certain branches
Title: Message Title Travis Ball commented on JENKINS-55879 Re: Declarative SCM checkout not running on certain branches After many hours of trial and error I think I may have found a "solution"... My target branches 'qa', 'uat' & 'master' did not have the Jenkinsfile in them (only the source branch in the PR did). I merged my branch in the 'qa' branch and now subsequent PRs to the 'qa' branch are now checking out fine. I think we can close this issue for now. Thanks for your help. 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-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54929 Some final output is missing in Jenkins Pipeline when using the Ansible Plugin Change By: Jesse Glick Component/s: pipeline Labels: ansible ansible-plugin jenkins pipeline pipeline-triaged playbook 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-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-55722 jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection Change By: Devin Nusbaum Component/s: publish-over-ssh-plugin Component/s: ssh-credentials-plugin Component/s: ssh-slaves-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-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Oleg Nenashev commented on JENKINS-55829 Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API Yes, thanks. If a task is not assigned, just feel free to take it. No need to ask 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-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Title: Message Title Jesse Glick commented on JENKINS-54929 Re: Some final output is missing in Jenkins Pipeline when using the Ansible Plugin Not familiar with this plugin so cannot give details, but in general if you have a Callable (or FileCallable) running on an agent that has been passed a serialized TaskListener, it will need to flush before returning. 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-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Devin Nusbaum assigned an issue to Unassigned Jenkins / JENKINS-55722 jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection Change By: Devin Nusbaum Assignee: Devin Nusbaum 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-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Devin Nusbaum commented on JENKINS-55722 Re: jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection Subhransubala Routray Repeatedly assigning me to this ticket is pointless, please stop doing it. I am not the person who would be able to help you even if you had provided enough information to do so (I think Alex Earl is the maintainer based on the plugin site). If you think this is a regression, you need to explain what, if anything, changed on your side (did you update your machines, update the plugin, update Jenkins, etc.) 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Yair Ogen commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Denis Zakharov I tried this. Doesn't work. I get the links only after the triggered builds finish. During the parallel run, I only see the build name and the number in the console but no link in blue ocean ui. 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-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Nisarg Shah commented on JENKINS-55829 Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API I would like to do this task. Can i assign it to me? 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-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Nisarg Shah edited a comment on JENKINS-55829 Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API I would like to do this task. Can i I assign it to me? 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-55888) class names are causing issues
Title: Message Title Jakub Pawlinski closed an issue as Not A Defect I should call publishIssues after all the builds are done, not one by one Jenkins / JENKINS-55888 class names are causing issues Change By: Jakub Pawlinski Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55888) class names are causing issues
Title: Message Title
Jakub Pawlinski updated an issue
Jenkins / JENKINS-55888
class names are causing issues
Change By:
Jakub Pawlinski
I have msbuild.groovy in my Using shared library, this class is responsible for acting on and declarative pipeline I build msbuild . projects (c#, c++, fortran) Got into some troubles when implementing this component due to it having msbuild class as well Each of those builds produces a log file, in pattern project . I overcome it using full name : + architecture + ".build.log" Trying to add warnings-ng at the end of all builds, so I made a method and call it then. {code:java}def publishWarnings( log, namePrefix = 'Build' ) { //has to define via full namespace due to existence of local msbuild class def warnings issues = scanForIssues tool: [$class: 'io.jenkins.plugins.analysis.warnings.MsBuild', pattern: "*.build. log " ] def results = scanForIssues tool: warnings def reference = env.JOB_NAME.replace(env.BRANCH_NAME, "develop") publishIssues issues id : [results] 'analyseWarnings' , name: 'All ', //the " ${namePrefix} Warnings " postfix will be addedissues: [issues] , //filters: [includePackage('io.jenkins.plugins.analysis.*')], referenceJobName: reference, unstableNewAll: 5}{code} unfortunately it seems still not enough as I get:{code:java} [C# ] Attaching ResultAction with ID ' msbuild ' to run 'EDM Platform/commonapplicationframework/feature%2FmoreWarnings #6'. ID msbuild is already used by another action: io.jenkins.plugins.analysis.core.model.ResultAction for C#{code}not sure how to handle this further. {code:java}java.lang.IllegalStateException: ID analyseWarnings is already used by another action: io.jenkins.plugins.analysis.core.model.ResultAction for All {code}
Add Comment
[JIRA] (JENKINS-55888) class names are causing issues
Title: Message Title
Jakub Pawlinski updated an issue
Jenkins / JENKINS-55888
class names are causing issues
Change By:
Jakub Pawlinski
Comment:
Or maybe it is that. Example at [https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#advanced-pipeline-configuration] is a bit misleading:{code:java}stage ('Analysis') {def mvnHome = tool 'mvn-default'sh "${mvnHome}/bin/mvn -batch-mode -V -U -e checkstyle:checkstyle pmd:pmd pmd:cpd findbugs:findbugs"def checkstyle = scanForIssues tool: checkStyle(pattern: '**/target/checkstyle-result.xml')publishIssues issues: [checkstyle] def pmd = scanForIssues tool: pmd(pattern: '**/target/pmd.xml')publishIssues issues: [pmd]def cpd = scanForIssues tool: cpd(pattern: '**/target/cpd.xml')publishIssues issues: [cpd]def spotbugs = scanForIssues tool: spotBugs(pattern: '**/target/findbugsXml.xml')publishIssues issues: [spotbugs]def maven = scanForIssues tool: mavenConsole()publishIssues issues: [maven]publishIssues id: 'analysis', name: 'All Issues', issues: [checkstyle, pmd, spotbugs], filters: [includePackage('io.jenkins.plugins.analysis.*')]}{code}why there is publishIssues after each scanForIssues ?and the last one which should publish few of them, throws:{code:java}java.lang.ClassCastException: io.jenkins.plugins.analysis.core.steps.PublishIssuesStep.issues expects class io.jenkins.plugins.analysis.core.steps.AnnotatedReport but received class java.util.ArrayList{code}when I give it an array of previously collected results in my case number of builds is dynamic, can be one project, can be plenty, most of them are msbuild based
Add Comment
[JIRA] (JENKINS-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Nisarg Shah updated an issue Jenkins / JENKINS-55829 Expose AbstractCIBase#disabledAdministrativeMonitors as internal API Change By: Nisarg Shah Comment: Okay so just instance of jenkins from Jenkins.get() needs to be stored by that method. Am I correct? 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-55890) RocketChat notification (using proxy) fails since version 1.3.1
Title: Message Title Falko Modler commented on JENKINS-55890 Re: RocketChat notification (using proxy) fails since version 1.3.1 PR sent: https://github.com/jenkinsci/rocketchatnotifier-plugin/pull/30 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-55893) Show build name instead of build number
Title: Message Title Oliver Schnabel created an issue Jenkins / JENKINS-55893 Show build name instead of build number Issue Type: New Feature Assignee: Gustaf Lundh Attachments: 2019-01-31_14h23_58.png Components: yet-another-build-visualizer-plugin Created: 2019-01-31 13:24 Labels: plugin jenkins pipeline Priority: Minor Reporter: Oliver Schnabel Plugin could show the build name (build.displayName) instead of the build number. Especially helpful if the job names are generic and do not contain any information about build details. Add Comment
[JIRA] (JENKINS-55681) Release the JAXB Plugin
Title: Message Title Baptiste Mathus commented on JENKINS-55681 Re: Release the JAXB Plugin Raphael Pionke this should be fixed https://github.com/jenkinsci/performance-signature-dynatrace-plugin/pull/7 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-55892) CollabNet-Plugin is not compatible with SECURITY-901 fix (Upgrading to 2.160)
Title: Message Title Holger Huebner created an issue Jenkins / JENKINS-55892 CollabNet-Plugin is not compatible with SECURITY-901 fix (Upgrading to 2.160) Issue Type: Bug Assignee: whsu Components: collabnet-plugin Created: 2019-01-31 12:55 Environment: Jenkins 2.160 collabnet-plugin 2.0.6 Labels: regression security-901 Priority: Major Reporter: Holger Huebner Since the update to version 2.160 Single sign on does not work anymore. After the Build & Test Integration call, the Jenkins home page still shows that the user is logged in. When trying to access another Jenkins page, the user must log in again. note: https://jenkins.io/doc/upgrade-guide/2.150/#upgrading-to-jenkins-lts-2-150-2 Add Comment
[JIRA] (JENKINS-55871) Update without losing plugins settings
Title: Message Title Patrik Boström assigned an issue to Unassigned Jenkins / JENKINS-55871 Update without losing plugins settings Change By: Patrik Boström Assignee: Patrik Boström 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-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title Baptiste Mathus commented on JENKINS-54864 Re: github multibranch builds fail to build with latest branch api update John Mellor we understand your frustration, but please be more careful with your phrasing, and be respectful of people time here. This is not a customer support channel. 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-55891) Jenkin is unable to login into testopia
Title: Message Title Sanjay Bhatta created an issue Jenkins / JENKINS-55891 Jenkin is unable to login into testopia Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: Jenkin-Logs.txt Components: testopia-plugin Created: 2019-01-31 12:44 Environment: Bugzilla Version - 4.4.10 Jenkin verison - 2.124 Testopia plugin - 1.3 Priority: Blocker Reporter: Sanjay Bhatta Jenkin is unable to login into testopia with correct credentials. Please find attached the error logs. Also can we have a proper document for integrating testopia plugin with Jenkins Add Comment
[JIRA] (JENKINS-20844) Bugzilla Plugin 1.5 not working with Bugzilla version 4.4.1
Title: Message Title Sanjay Bhatta commented on JENKINS-20844 Re: Bugzilla Plugin 1.5 not working with Bugzilla version 4.4.1 I am also trying to configure testopia with Jenkin. Bugzilla Version - 4.4.10 Jenkin - 2.124 Error - Connecting to Testopia to retrieve automated test cases java.lang.RuntimeException: Failed to login! at org.mozilla.testopia.service.xmlrpc.XmlRpcMiscService.login(XmlRpcMiscService.java:63) at org.mozilla.testopia.TestopiaAPI.login(TestopiaAPI.java:106) at jenkins.plugins.testopia.TestopiaBuilder.perform(TestopiaBuilder.java:214) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1794) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: org.apache.xmlrpc.client.XmlRpcClientException: Failed to parse server's response: The declaration for the entity "HTML.Version" must end with '>'. at org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTransport.java:188) at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:156) at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:143) at org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTransport.java:69) at org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:56) at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167) at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:137) at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:126) at org.mozilla.testopia.service.xmlrpc.XmlRpcMiscService.login(XmlRpcMiscService.java:61) ... 11 more Caused by: org.xml.sax.SAXParseExceptionpublicId: -//W3C//DTD HTML 4.01 Transitional//EN; systemId: http://www.w3.org/TR/html4/loose.dtd; lineNumber: 31; columnNumber: 3; The declaration for the entity "HTML.Version" must end with '>'. at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1239) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643) at org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTransport.java:186) ... 19 more ERROR: Failed to login! Add Comment
[JIRA] (JENKINS-55888) class names are causing issues
Title: Message Title
Jakub Pawlinski commented on JENKINS-55888
Re: class names are causing issues
Or maybe it is that. Example at https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#advanced-pipeline-configuration is a bit misleading:
stage ('Analysis') {
def mvnHome = tool 'mvn-default'
sh "${mvnHome}/bin/mvn -batch-mode -V -U -e checkstyle:checkstyle pmd:pmd pmd:cpd findbugs:findbugs"
def checkstyle = scanForIssues tool: checkStyle(pattern: '**/target/checkstyle-result.xml')
publishIssues issues: [checkstyle]
def pmd = scanForIssues tool: pmd(pattern: '**/target/pmd.xml')
publishIssues issues: [pmd]
def cpd = scanForIssues tool: cpd(pattern: '**/target/cpd.xml')
publishIssues issues: [cpd]
def spotbugs = scanForIssues tool: spotBugs(pattern: '**/target/findbugsXml.xml')
publishIssues issues: [spotbugs]
def maven = scanForIssues tool: mavenConsole()
publishIssues issues: [maven]
publishIssues id: 'analysis', name: 'All Issues',
issues: [checkstyle, pmd, spotbugs],
filters: [includePackage('io.jenkins.plugins.analysis.*')]
}
why there is publishIssues after each scanForIssues ? and the last one which should publish few of them, throws:
java.lang.ClassCastException: io.jenkins.plugins.analysis.core.steps.PublishIssuesStep.issues expects class io.jenkins.plugins.analysis.core.steps.AnnotatedReport but received class java.util.ArrayList
when I give it an array of previously collected results in my case number of builds is dynamic, can be one project, can be plenty, most of them are msbuild based
Add Comment
[JIRA] (JENKINS-48775) Proxy authentication error 407 even if 'check proxy' works
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-48775 Proxy authentication error 407 even if 'check proxy' works Change By: Oliver Gondža Labels: 2.150.1-rejected 2.150.2-rejected 2.150.3-rejected Proxy lts-candidate 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Oliver Gondža Labels: 2.150.3-rejected lts-candidate regression Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Baptiste Mathus started work on JENKINS-55202 Change By: Baptiste Mathus 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.
