[JIRA] (JENKINS-55500) Warnings per project portlet
Title: Message Title Robin Jansohn created an issue Jenkins / JENKINS-55500 Warnings per project portlet Issue Type: Task Assignee: Ulli Hafner Attachments: warnings_per_project_portlet.png Components: warnings-ng-plugin Created: 2019-01-10 07:54 Priority: Minor Reporter: Robin Jansohn Add a `Warnings per project` portlet. It should be possible to configure the display name of the portlet whether zero warnings projects should be hidden whether icons should be shown which report formats should be shown in the columns (CheckStyle, CPD, SpotBugs, ...) See attached image how the configuration looked like in the old warnings plugin. Add Comment
[JIRA] (JENKINS-55480) Add warnings-ng portlets for dashboard
Title: Message Title Robin Jansohn updated an issue Jenkins / JENKINS-55480 Add warnings-ng portlets for dashboard Change By: Robin Jansohn Epic Name: warnings-ng portlets Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-30515) scm (git) command does not fail correctly when it cannot look up credentials
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-30515 Jenkins / JENKINS-30515 scm (git) command does not fail correctly when it cannot look up credentials Change By: Jose Blas Camacho Taboada 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-30515) scm (git) command does not fail correctly when it cannot look up credentials
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-30515 Change By: Jose Blas Camacho Taboada 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-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Jens Beyer commented on JENKINS-55024 Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Devin Nusbaum Sorry I just realized that my issue with the build step logs (the first one I mentioned) was probably also caused by the full console issue with compressedBuildLog (JENKINS-55465, the second one I mentioned). Please disregard. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55499) Jenkins can`t display jobs view,my jenkins version 2.157
Title: Message Title Kevin Liu updated an issue Jenkins / JENKINS-55499 Jenkins can`t display jobs view,my jenkins version 2.157 Change By: Kevin Liu Summary: I Jenkins can`t enter display jobs view,my jenkins version 2.157 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55499) I can`t enter jobs view,my jenkins version 2.157
Title: Message Title
Kevin Liu updated an issue
Jenkins / JENKINS-55499
I can`t enter jobs view,my jenkins version 2.157
Change By:
Kevin Liu
My Jenkins is in docker container the version is 2.138, that use gitlab authentication,and updates to any version can`t use jobs views view for the user ,but the root user is normal . It`s will display not found 404, and this error in Jenkins log display is ``` {code:java} Jan 10, 2019 1:53:09 PM hudson.ExpressionFactory2$JexlExpression evaluateJan 10, 2019 1:53:09 PM hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: it.items in /. Reason: java.lang.reflect.InvocationTargetExceptionjava.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at
[JIRA] (JENKINS-55499) I can`t enter jobs view,my jenkins version 2.157
Title: Message Title Kevin Liu updated an issue Jenkins / JENKINS-55499 I can`t enter jobs view,my jenkins version 2.157 Change By: Kevin Liu My Jenkins is container the version is 2.138, that use gitlab authentication,and updates to any version can`t use jobs views for the user. It`s will display not found 404, and this error in Jenkins log display is " ``` Jan 10, 2019 1:53:09 PM hudson.ExpressionFactory2$JexlExpression evaluateJan 10, 2019 1:53:09 PM hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: it.items in /. Reason: java.lang.reflect.InvocationTargetExceptionjava.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] (JENKINS-55499) I can`t enter jobs view,my jenkins version 2.157
Title: Message Title Kevin Liu updated an issue Jenkins / JENKINS-55499 I can`t enter jobs view,my jenkins version 2.157 Change By: Kevin Liu My Jenkins is container the version is 2.138, that use gitlab authentication,and updates to any version can`t use jobs views for the user. It`s will display not found 404, and this error in Jenkins log display is``` Jan 10, 2019 1:53:09 PM hudson.ExpressionFactory2$JexlExpression evaluateJan 10, 2019 1:53:09 PM hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: it.items in /. Reason: java.lang.reflect.InvocationTargetExceptionjava.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] (JENKINS-55499) I can`t enter jobs views,my jenkins version 2.157
Title: Message Title Kevin Liu updated an issue Jenkins / JENKINS-55499 I can`t enter jobs views,my jenkins version 2.157 Change By: Kevin Liu Summary: I can`t enter job jobs views,my jenkins version 2.157 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55499) I can`t enter jobs view,my jenkins version 2.157
Title: Message Title Kevin Liu updated an issue Jenkins / JENKINS-55499 I can`t enter jobs view,my jenkins version 2.157 Change By: Kevin Liu Summary: I can`t enter jobs views view ,my jenkins version 2.157 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55499) I can`t enter job views,my jenkins version 2.157
Title: Message Title Kevin Liu updated an issue Jenkins / JENKINS-55499 I can`t enter job views,my jenkins version 2.157 Change By: Kevin Liu My Jenkins is container the version is 2.138, that use gitlab authentication,and updates to any version can`t use job jobs views for the user. It`s will display not found 404, and this error in Jenkins log display is"Jan 10, 2019 1:53:09 PM hudson.ExpressionFactory2$JexlExpression evaluateJan 10, 2019 1:53:09 PM hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: it.items in /. Reason: java.lang.reflect.InvocationTargetExceptionjava.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] (JENKINS-55499) I can`t enter job views,my jenkins version 2.157
Title: Message Title Kevin Liu assigned an issue to Daniel Beck Jenkins / JENKINS-55499 I can`t enter job views,my jenkins version 2.157 Change By: Kevin Liu Assignee: Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55499) I can`t enter job views,my jenkins version 2.157
Title: Message Title Kevin Liu created an issue Jenkins / JENKINS-55499 I can`t enter job views,my jenkins version 2.157 Issue Type: Bug Assignee: Unassigned Attachments: jenkins-view-error.log Components: core Created: 2019-01-10 06:03 Environment: linux, docker-1.13.1, jenkins-2.157, Labels: views jenkins Priority: Blocker Reporter: Kevin Liu My Jenkins is container the version is 2.138, that use gitlab authentication,and updates to any version can`t use job views for the user. It`s will display not found 404, and this error in Jenkins log display is "Jan 10, 2019 1:53:09 PM hudson.ExpressionFactory2$JexlExpression evaluateJan 10, 2019 1:53:09 PM hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: it.items in /. Reason: java.lang.reflect.InvocationTargetExceptionjava.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at
[JIRA] (JENKINS-55446) Unable to Execute Test in HP Performance Center 12.01
Title: Message Title Pradeepkumar Subramaniam started work on JENKINS-55446 Change By: Pradeepkumar Subramaniam 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-54982) Using Java8 Streams evaluates whole expression to Boolean
Title: Message Title
Thomas Fox commented on JENKINS-54982
Re: Using Java8 Streams evaluates whole _expression_ to Boolean
I have a similar problem when trying to use a Java8 parallelStream() in a Jenkins shared library. The stream processes only a single item in the list. The problem is also with stream() but not with the groovy each(which I cannot use because it does not execute in parallel). The shared library code is
def streamtest()
{
def myList = ["1","2","3","4"]
echo "each:"
myList.each{ entry -> echo "$entry" }
echo "parallelStream:"
myList.parallelStream().forEach{ entry -> echo "$entry" }
echo "stream:"
myList.stream().forEach{ entry -> echo "$entry" }
}
Sample output is
[Pipeline] stage
[Pipeline] { (streamtest)
[Pipeline] echo
each:
[Pipeline] echo
1
[Pipeline] echo
2
[Pipeline] echo
3
[Pipeline] echo
4
[Pipeline] echo
parallelStream:
[Pipeline] echo
3
[Pipeline] echo
stream:
[Pipeline] echo
1
[Pipeline] }
[Pipeline] // stage
As an aside, I have also tried to use GPars for parallelism but I could not get it to work with CPS. I also have tried an ThreadPoolExecutor which I also could not get to work (it did not seem to start any threads but I did not do a thorough investigation). My hopes are
If a java language feature does not work, it would be cool if it would fail fast instead of doing unexpected things
Is there any working method to use parallelism with threads (not with nodes) in a shared library?
Add Comment
[JIRA] (JENKINS-55498) CompositeIOException is thrown and Multibranch pipeline fails to load organization repos
Title: Message Title Preethi Mani updated an issue Jenkins / JENKINS-55498 CompositeIOException is thrown and Multibranch pipeline fails to load organization repos Change By: Preethi Mani Install a plugin "convert job to pipeline" with option "download and install later" that throws error "CompositeIOException" while downloading and after restart all the repos under our organization is gone... And also few of the already installed plugins like "github branch source" somehow moved to "available" tab of plugin manager indicating that it got uninstalled on its own... Also when tried to re install we get same "CompositeIOException" error stating the directory cannot be removed . One more point -This error "CompositeIOException" was also observed in job's *publish html report* step ( we don't archive for each build) since 2.157 release on January 6th. [htmlpublisher] Archiving HTML reports...[htmlpublisher] Archiving at PROJECT level /var/lib/jenkins/workspace/ ZapSecurityTest WORKSPACE_NAME /reports to /var/lib/jenkins/jobs/ ZapSecurityTest JOB_NAME /htmlreports/*FATAL: HTML Publisher failurejava.io.IOException: Unable to delete '/var/lib/jenkins/jobs/JOB_NAME/htmlreports/REPORT_NAME'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. at jenkins.util.io.PathRemover.forceRemoveFile(PathRemover.java:75) at hudson.Util.deleteFile(Util.java:255) at hudson.FilePath.deleteRecursive(FilePath.java:1305) at hudson.FilePath.access$1600(FilePath.java:213) at hudson.FilePath$DeleteRecursive.invoke(FilePath.java:1274) at hudson.FilePath$DeleteRecursive.invoke(FilePath.java:1270) at hudson.FilePath.act(FilePath.java:1078) at hudson.FilePath.act(FilePath.java:1061) at hudson.FilePath.deleteRecursive(FilePath.java:1268) at htmlpublisher.HtmlPublisher.publishReports(HtmlPublisher.java:285) at htmlpublisher.HtmlPublisher.perform(HtmlPublisher.java:193) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1835) 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: jenkins.util.io.CompositeIOException: Unable to remove directory
[JIRA] (JENKINS-55498) CompositeIOException is thrown and Multibranch pipeline fails to load organization repos
Title: Message Title Preethi Mani created an issue Jenkins / JENKINS-55498 CompositeIOException is thrown and Multibranch pipeline fails to load organization repos Issue Type: Bug Assignee: Matt Sicker Components: core Created: 2019-01-10 03:45 Environment: Jenkins 2.157 . OS - Linux (amd64) Labels: jenkins ioexception2 IOException CompositeIOException pathremover Priority: Major Reporter: Preethi Mani Install a plugin "convert job to pipeline" with option "download and install later" that throws error "CompositeIOException" while downloading and after restart all the repos under our organization is gone... And also few of the already installed plugins like "github branch source" somehow moved to "available" tab of plugin manager indicating that it got uninstalled on its own... Also when tried to re install we get same "CompositeIOException" error stating the directory cannot be removed . One more point - This error "CompositeIOException" was also observed in job's publish html report step ( we don't archive for each build) since 2.157 release on January 6th. [htmlpublisher] Archiving HTML reports... [htmlpublisher] Archiving at PROJECT level /var/lib/jenkins/workspace/ZapSecurityTest/reports to /var/lib/jenkins/jobs/ZapSecurityTest/htmlreports/* FATAL: HTML Publisher failure java.io.IOException: Unable to delete '/var/lib/jenkins/jobs/JOB_NAME/htmlreports/REPORT_NAME'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. at jenkins.util.io.PathRemover.forceRemoveFile(PathRemover.java:75) at hudson.Util.deleteFile(Util.java:255) at
[JIRA] (JENKINS-50573) Wrong username used for git clone with OpenSSH 7.7
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-50573
Wrong username used for git clone with OpenSSH 7.7
Change By:
Mark Waite
Windows VMs, Alpine Linux docker images, Debian Buster ("testing"), macOS 10.13.6, and OpenBSD 6.3 installations which use OpenSSH 7.7 (on Windows as part of Git on Windows 2.17 and Git on Windows 2.18) use the wrong username when cloning git repos with ssh (private key authentication). They're using {{jenkins}} when {{git}} is explicitly specified.{code:java}dir("dist-utils") {git credentialsId: 'ssh-id-rsa', url: 'ssh://g...@github.com/zeroc-ice/dist-utils.git'}{code}{code:java} > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url ssh://g...@github.com/zeroc-ice/dist-utils.git # timeout=10Fetching upstream changes from ssh://g...@github.com/zeroc-ice/dist-utils.git > git --version # timeout=10using GIT_SSH to set credentials Jenkins SSH RSA Key > git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from ssh://g...@github.com/zeroc-ice/dist-utils.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:862) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1129) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1160) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: jenk...@github.com: Permission denied (publickey).fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1996) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1715) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72) at
[JIRA] (JENKINS-50573) Wrong username used for git clone with OpenSSH 7.7
Title: Message Title Owen Mehegan commented on JENKINS-50573 Re: Wrong username used for git clone with OpenSSH 7.7 I just wanted to add that MacOS 10.13.6 is also affected by this. It includes OpenSSH 7.8. Updating git-client fixes the problem on those hosts. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55284) Command line git tag collision behavior changed in git 2.20
Title: Message Title Mark Waite commented on JENKINS-55284 Re: Command line git tag collision behavior changed in git 2.20 Henrik Lundahl and Stanislav Jursky could you test the build of the pull request I've submitted? I wrote a test that failed then made a code change to pass the test. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55497) BlueOcean Pipeline View sometimes shows No Changes
Title: Message Title Stuart Rowe updated an issue Jenkins / JENKINS-55497 BlueOcean Pipeline View sometimes shows No Changes Change By: Stuart Rowe The In these cases, the pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55497) BlueOcean Pipeline View sometimes shows No Changes
Title: Message Title Stuart Rowe created an issue Jenkins / JENKINS-55497 BlueOcean Pipeline View sometimes shows No Changes Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-01-09 23:38 Environment: Jenkins ver. 2.150.1 Blue Ocean 1.10.1 P4 Plugin 1.9.5 Priority: Major Reporter: Stuart Rowe The pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset. Add Comment
[JIRA] (JENKINS-55496) recordIssues step using groovy parser errors out
Title: Message Title Christopher Tindall commented on JENKINS-55496 Re: recordIssues step using groovy parser errors out Aha! Thank you! I guess sourceCodeEncoding is necessary 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-42422) Add support for directory caching in pod jobs
Title: Message Title R C commented on JENKINS-42422 Re: Add support for directory caching in pod jobs The only sane way to implement this is through StatefulSets, especially if you have more than one agent (who doesn't run Jenkins like that?). An example scenario: You're currently running three agents. A fourth one needs to be launched. As the last comment says, there's no easy way to create an unique volume name that can also be referenced by the new pod. StatefulSets do that: https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#writing-to-stable-storage Assuming a StatefulSet named agent-XYZ with a VolumeClaimTemplate named workspace, the plugin would need to scale the StatefulSet to 4. Then Kubernetes will take care of creating pod agent-XYZ-3 and PVC workspace-agent-XYZ-3. When, later, the cluster is idle, the plugin can scale the SS down to 1. Kubernetes will terminate pods 3, 2 and 1, in that order, leaving 0 still up. The volumes are KEPT, by design, which is probably what you want if they're a cache (I do, too). When, later the SS scales up, the volumes are already around. This is all nice and takes some complexity away from the plugin, but there's some extra work to be done. I haven't looked at the code, but I assume that the plugin treats each pod it creates in isolation, independent of each other (is that correct?). With StatefulSets, you probably want to fingerprint the pod definition so that identical ones are mapped to the same set (XYZ above would be such a hash). Then the plugin needs to track how many pods are needed for each fingerprint and scale the StatefulSets accordingly. The other problem is passing the unique JENKINS_SECRET to the pod. I don't think StatefulSets allow per-pod secrets/variables. So, either secrets need to be turned off (bad) or they need to be delivered out-of-band, e.g. in an init container. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the
[JIRA] (JENKINS-55496) recordIssues step using groovy parser errors out
Title: Message Title Ulli Hafner resolved as Not A Defect Jenkins / JENKINS-55496 recordIssues step using groovy parser errors out Change By: Ulli Hafner Status: Open Resolved 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-55496) recordIssues step using groovy parser errors out
Title: Message Title Ulli Hafner commented on JENKINS-55496 Re: recordIssues step using groovy parser errors out The syntax is (with one tool): recordIssues sourceCodeEncoding: 'UTF-8', tool: groovyScript(parserId: 'groovy-id-in-system-config', pattern:'**/*report.log', reportEncoding:'UTF-8') See documentation, still not yet in the master branch... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55063) Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Title: Message Title Christopher Tindall closed an issue as Duplicate Created new issue: JENKINS-55496 Jenkins / JENKINS-55063 Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage. Change By: Christopher Tindall Status: Reopened Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55496) recordIssues step using groovy parser errors out
Title: Message Title
Christopher Tindall updated an issue
Jenkins / JENKINS-55496
recordIssues step using groovy parser errors out
Change By:
Christopher Tindall
Using the below recordIssues step as suggested in JENKINS-55063 does not work:recordIssues tools: [[tool: groovyScript(parserId: 'luacheck', pattern: 'static_analysis_junit.xml', reportEncoding:'UTF-8')]] Error ( ellipsis added to denote removed text too long to be added in a comment ) : java.lang.UnsupportedOperationException: must specify $class with an implementation of class io.jenkins.plugins.analysis.core.model.Tool at org.jenkinsci.plugins.structs.describable.DescribableModel.resolveClass(DescribableModel.java:503) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:402) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerceList(DescribableModel.java:514) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:388) at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:361) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:284) Caused: java.lang.IllegalArgumentException: Could not instantiate {tools=[{tool=@groovyScript(parserId=luacheck,pattern=static_analysis_junit.xml,reportEncoding=UTF-8)}]} for IssuesRecorder(aggregatingResults?: boolean, blameDisabled?: boolean, enabledForFailure?: boolean, failedNewAll?: int, failedNewHigh?: int, failedNewLow?: int, failedNewNormal?: int, failedTotalAll?: int, failedTotalHigh?: int, failedTotalLow?: int, failedTotalNormal?: int, filters?: RegexpFilter\{ExcludeCategory(pattern: String) | ExcludeFile(pattern: String) | ExcludeModule(pattern: String) | ExcludePackage(pattern: String) | ExcludeType(pattern: String) | IncludeCategory(pattern: String) | IncludeFile(pattern: String) | IncludeModule(pattern: String) | IncludePackage(pattern: String) | IncludeType(pattern: String)}[], healthy?: int, id?: String, ignoreFailedBuilds?: boolean, ignoreQualityGate?: boolean, minimumSeverity?: String, name?: String, referenceJobName?: String, sourceCodeEncoding?: String, tool?: Tool{AcuCobol(id?: String, name?: String, pattern?: String, reportEncoding?: String) | Ajc(id?: String, name?: String, pattern?: String, reportEncoding?: String) | AndroidLint(id?: String, name?: String, pattern?: String, reportEncoding?: String) | AnsibleLint(id?: String, ... String, name?: String, pattern?: String, reportEncoding?: String) | SwiftLint(id?: String, name?: String, pattern?: String, reportEncoding?: String) | TagList(id?: String, name?: String, pattern?: String, reportEncoding?: String) | TaskingVx(id?: String, name?: String, pattern?: String ... ... ... ... ... ... ... ... ... JiraVersionCreatorBuilder(jiraVersion: String, jiraProjectKey: String) | Mailer(recipients: String, notifyEveryUnstableBuild: boolean, sendToIndividuals: boolean) | StashNotifier(stashServerBaseUrl: String, credentialsId: String,
[JIRA] (JENKINS-55496) recordIssues step using groovy parser errors out
Title: Message Title
Christopher Tindall updated an issue
Jenkins / JENKINS-55496
recordIssues step using groovy parser errors out
Change By:
Christopher Tindall
Using the below recordIssues step as suggested in JENKINS-55063 does not work:recordIssues tools: [[tool: groovyScript(parserId: 'luacheck', pattern: 'static_analysis_junit.xml', reportEncoding:'UTF-8')]] Error ellipsis added to denote removed text too long to be added in a comment : java.lang.UnsupportedOperationException: must specify $class with an implementation of class io.jenkins.plugins.analysis.core.model.Tool at org.jenkinsci.plugins.structs.describable.DescribableModel.resolveClass(DescribableModel.java:503) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:402) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerceList(DescribableModel.java:514) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:388) at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:361) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:284)Caused: java.lang.IllegalArgumentException: Could not instantiate \ {tools=[ {tool=@groovyScript(parserId=luacheck,pattern=static_analysis_junit.xml,reportEncoding=UTF-8)} ]} for IssuesRecorder(aggregatingResults?: boolean, blameDisabled?: boolean, enabledForFailure?: boolean, failedNewAll?: int, failedNewHigh?: int, failedNewLow?: int, failedNewNormal?: int, failedTotalAll?: int, failedTotalHigh?: int, failedTotalLow?: int, failedTotalNormal?: int, filters?: RegexpFilter\{ExcludeCategory(pattern: String) | ExcludeFile(pattern: String) | ExcludeModule(pattern: String) | ExcludePackage(pattern: String) | ExcludeType(pattern: String) | IncludeCategory(pattern: String) | IncludeFile(pattern: String) | IncludeModule(pattern: String) | IncludePackage(pattern: String) | IncludeType(pattern: String)}[], healthy?: int, id?: String, ignoreFailedBuilds?: boolean, ignoreQualityGate?: boolean, minimumSeverity?: String, name?: String, referenceJobName?: String, sourceCodeEncoding?: String, tool?: Tool {AcuCobol(id?: String, name?: String, pattern?: String, reportEncoding?: String) | Ajc(id?: String, name?: String, pattern?: String, reportEncoding?: String) | AndroidLint(id?: String, name?: String, pattern?: String, reportEncoding?: String) | AnsibleLint(id?: String, ... String, name?: String, pattern?: String, reportEncoding?: String) | SwiftLint(id?: String, name?: String, pattern?: String, reportEncoding?: String) | TagList(id?: String, name?: String, pattern?: String, reportEncoding?: String) | TaskingVx(id?: String, name?: String, pattern?: String ... ... ... ... ... ... ... ... ... JiraVersionCreatorBuilder(jiraVersion: String, jiraProjectKey: String) | Mailer(recipients: String, notifyEveryUnstableBuild: boolean, sendToIndividuals: boolean) | StashNotifier(stashServerBaseUrl: String, credentialsId: String,
[JIRA] (JENKINS-55496) recordIssues step using groovy parser errors out
Title: Message Title
Christopher Tindall created an issue
Jenkins / JENKINS-55496
recordIssues step using groovy parser errors out
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-01-09 22:42
Priority:
Major
Reporter:
Christopher Tindall
Using the below recordIssues step as suggested in JENKINS-55063 does not work: recordIssues tools: [[tool: groovyScript(parserId: 'luacheck', pattern: 'static_analysis_junit.xml', reportEncoding:'UTF-8')]] Error: java.lang.UnsupportedOperationException: must specify $class with an implementation of class io.jenkins.plugins.analysis.core.model.Tool at org.jenkinsci.plugins.structs.describable.DescribableModel.resolveClass(DescribableModel.java:503) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:402) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerceList(DescribableModel.java:514) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:388) at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:361) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:284) Caused: java.lang.IllegalArgumentException: Could not instantiate {tools=[ {tool=@groovyScript(parserId=luacheck,pattern=static_analysis_junit.xml,reportEncoding=UTF-8)} ]} for IssuesRecorder(aggregatingResults?: boolean, blameDisabled?: boolean, enabledForFailure?: boolean, failedNewAll?: int, failedNewHigh?: int, failedNewLow?: int, failedNewNormal?: int, failedTotalAll?: int, failedTotalHigh?: int, failedTotalLow?: int, failedTotalNormal?: int, filters?: RegexpFilter{ExcludeCategory(pattern: String) | ExcludeFile(pattern: String) | ExcludeModule(pattern: String) | ExcludePackage(pattern: String) | ExcludeType(pattern: String) | IncludeCategory(pattern: String) | IncludeFile(pattern: String) | IncludeModule(pattern: String) | IncludePackage(pattern: String) |
[JIRA] (JENKINS-55478) CompositeIOException when deleting workspace before check-out
Title: Message Title Matt Sicker commented on JENKINS-55478 Re: CompositeIOException when deleting workspace before check-out Do you have any logs from the agent? A CompositeIOException should print out all its IOExceptions during the stack trace, but it doesn't look like that works properly via remoting. Also, do you know whether or not the directory exists? Specific reproduction steps would help a lot. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55436) warnings-ng is not backwards compatible
Title: Message Title
Ulli Hafner commented on JENKINS-55436
Re: warnings-ng is not backwards compatible
I tried the following on my local machine:
node {
stage ('Checkout') {
git branch:'master', url: 'file:///Users/hafner/Development/git/analysis-model'
}
stage ('Build and Analysis') {
def mvnHome = tool 'mvn-default'
sh "${mvnHome}/bin/mvn --batch-mode -V -U -e clean verify revapi:check -Dsurefire.useFile=false -Dmaven.test.failure.ignore"
junit testResults: '**/target/surefire-reports/TEST-*.xml'
pmd canComputeNew: false, canRunOnFailed: true, defaultEncoding: '', healthy: '', pattern: "target/pmd.xml",unHealthy: '', unstableTotalAll: '0'
}
}
This works quite well with the PMD plugin 4.0.0 and warnings-ng plugin. There still seems to be something different in your configuration...
[PMD] Collecting PMD analysis files...
[PMD] Searching for all files in /Users/hafner/Development/jenkins/workspace/Old - Pipeline Model that match the pattern target/pmd.xml
[PMD] Parsing 1 file in /Users/hafner/Development/jenkins/workspace/Old - Pipeline Model
[PMD] Successfully parsed file /Users/hafner/Development/jenkins/workspace/Old - Pipeline Model/target/pmd.xml with 2 unique warnings and 0 duplicates.
Skipping warnings blame since pipelines do not have an SCM link.%n
[PMD] Ignore new warnings since this is the first valid build
[PMD] Plug-in Result: Unstable - 2 warnings exceed the threshold of 0 by 2
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55495) Improve layout of fixed issues table
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55495 Improve layout of fixed issues table Change By: Ulli Hafner !Bildschirmfoto 2019-01-09 um 23 See attachment . 01.02.png|width=787,height=122,thumbnail! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55495) Improve layout of fixed issues table
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55495 Improve layout of fixed issues table Change By: Ulli Hafner !Bildschirmfoto 2019-01-09 um 23.01.02.png |width=787,height=122,thumbnail ! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55495) Improve layout of fixed issues table
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-55495 Improve layout of fixed issues table Issue Type: New Feature Assignee: Ulli Hafner Attachments: Bildschirmfoto 2019-01-09 um 23.01.02.png Components: warnings-ng-plugin Created: 2019-01-09 22:01 Priority: Minor Reporter: Ulli Hafner Add Comment
[JIRA] (JENKINS-55494) Jenkin Jobs not running on slave
Title: Message Title Markee Clark created an issue Jenkins / JENKINS-55494 Jenkin Jobs not running on slave Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-01-09 21:41 Priority: Major Reporter: Markee Clark Error when running Jenkins. java.io.IOException: Remote call on (private) failed at hudson.remoting.Channel.call(Channel.java:963) at hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:263) at hudson.maven.ProcessCache.get(ProcessCache.java:236) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1810) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: java.lang.NoClassDefFoundError: Could not initialize class java.net.SocksSocketImpl at java.net.ServerSocket.setImpl(ServerSocket.java:288) at java.net.ServerSocket.(ServerSocket.java:87) at hudson.maven.AbstractMavenProcessFactory$SocketHandler$AcceptorImpl.(AbstractMavenProcessFactory.java:206) at hudson.maven.AbstractMavenProcessFactory$SocketHandler.call(AbstractMavenProcessFactory.java:193) at hudson.maven.AbstractMavenProcessFactory$SocketHandler.call(AbstractMavenProcessFactory.java:191) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Suppressed:
[JIRA] (JENKINS-55480) Add warnings-ng portlets for dashboard
Title: Message Title Ulli Hafner commented on JENKINS-55480 Re: Add warnings-ng portlets for dashboard Yes, these are still missing. I transformed this issue to an epic so we can add sub tasks. Can you please also add the required individual portlets as list of ordered sub issues? Since these charts need some time I can add them one after the other in a given priority. Having them as individual issues will also help to discuss new features or properties since the new charts will be rendered on the client side in JS. Maybe some old stuff should not be ported 1:1. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49717) no token field in Openshift OAuth token credential type
Title: Message Title Sean Lynch commented on JENKINS-49717 Re: no token field in Openshift OAuth token credential type As a workaround until this is fixed, I went in and manually edited credentials.xml. Here are the steps. First, go and create the Openshift OAuth token (hit OK even though it didn't give you any place to add the actual token). Next, open up credentials.xml and find the entry for the newly created token: ... The description field will be blank and you can add one here. Then add a tag for and put the token in there. Finally restart Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55479) Using workspace classes from multiple DSL scripts fails
Title: Message Title Daniel Spilker commented on JENKINS-55479 Re: Using workspace classes from multiple DSL scripts fails PR: https://github.com/jenkinsci/job-dsl-plugin/pull/1156 I think the problem is that Job DSL re-uses the GroovyShell object, but the Script Security plugin creates a new sandbox for each script. Currently the Script Security does not provide an API to run multiple scripts in the same sandbox. To fix this I had to disable the GroovyShell cache. Running many scripts in sandbox mode will be slower. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55480) Add warnings-ng portlets for dashboard
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55480 Add warnings-ng portlets for dashboard Change By: Ulli Hafner Issue Type: New Feature Epic Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55479) Using workspace classes from multiple DSL scripts fails
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-55479 Using workspace classes from multiple DSL scripts fails Change By: Daniel Spilker Component/s: script-security-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-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title Rajiv Jandial commented on JENKINS-15570 Re: Coverage report includes classes that have been excluded from Jacoco analysis I am still seeing this as an open issue. Even I exclude the package from the pom.xml as well as from the Jenkins "exclusions" fields, those packages are still being included in the JaCoCo report. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55493) [support-core] Upgrade parent pom and fix HTMLForm API usage
Title: Message Title Adrien Lecharpentier updated an issue Jenkins / JENKINS-55493 [support-core] Upgrade parent pom and fix HTMLForm API usage Change By: Adrien Lecharpentier Summary: [support-core] Upgrade parent pom and fix HTMLForm API usage Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55493) [support-core] Upgrade parent pom and fix HTMLForm API usage
Title: Message Title Adrien Lecharpentier started work on JENKINS-55493 Change By: Adrien Lecharpentier 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-55493) [support-core] Upgrade parent pom and fix HTMLForm API usage
Title: Message Title Adrien Lecharpentier updated JENKINS-55493 Jenkins / JENKINS-55493 [support-core] Upgrade parent pom and fix HTMLForm API usage Change By: Adrien Lecharpentier 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-55493) [support-core] Upgrade parent pom
Title: Message Title Adrien Lecharpentier created an issue Jenkins / JENKINS-55493 [support-core] Upgrade parent pom Issue Type: Improvement Assignee: Adrien Lecharpentier Components: support-core-plugin Created: 2019-01-09 20:28 Priority: Minor Reporter: Adrien Lecharpentier In order to validate the bahaviour of the plugin on Java 11, we need to upgrade the parent-pom used by the plugin. Initial tests shows that some dependencies changed, resulting in the usage of removed API in SupportActionTest [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:testCompile (default-testCompile) on project support-core: Compilation failure [ERROR] /home/adrien/workspaces/jenkinsci/support-core-plugin/src/test/java/com/cloudbees/jenkins/support/SupportActionTest.java:[105,50] cannot find symbol [ERROR] symbol: method getHtmlElementsByTagName(java.lang.String) [ERROR] location: variable form of type com.gargoylesoftware.htmlunit.html.HtmlForm
[JIRA] (JENKINS-55429) periodic trigger always results in 1 minute
Title: Message Title Daniel Spilker updated JENKINS-55429 Jenkins / JENKINS-55429 periodic trigger always results in 1 minute 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-55379) add support for warnings-ng-plugin to DSL Plugin
Title: Message Title Daniel Spilker commented on JENKINS-55379 Re: add support for warnings-ng-plugin to DSL Plugin Francisco Robles Martin The embedded API Viewer will display documentation if provided by the plugin (like the Warnings NG plugin). E.g. for a class foo.Bar, the plugin must provide a file foo/Bar/help.html. And for a property foo.Bar.test it must provide foo/Bar/help-test.html. The same help files are used by the Jenkins job configuration page. The public API viewer (https://jenkinsci.github.io/job-dsl-plugin/) can not display the Dynamic DSL. The embedded API viewer data is generated at runtime in Jenkins for the set of plugins in that Jenkins instance. The public API viewer is not the "main" API viewer, it's more a legacy API viewer for the limited built-in DSL. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55469) DSL Plugin - Missing support for Git Parameter fields
Title: Message Title Daniel Spilker closed an issue as Duplicate Jenkins / JENKINS-55469 DSL Plugin - Missing support for Git Parameter fields Change By: Daniel Spilker 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-49438) I can't use selectedValue and useRepository for git parameter job-dsl-plugin
Title: Message Title
Daniel Spilker edited a comment on JENKINS-49438
Re: I can't use selectedValue and useRepository for git parameter job-dsl-plugin
The [ Automatically Generated Dynamic DSL|https://github.com/jenkinsci/job-dsl-plugin/wiki/ Automatically Dynamic - Generated- DSL] supports all available options.{code}job { parameters {gitParameterDefinition { name(String value) type(String value) defaultValue(String value) description(String value) branch(String value) branchFilter(String value) tagFilter(String value) sortMode(String value) selectedValue(String value) useRepository(String value) quickFilterEnabled(Boolean value)} }}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55486) If lock() creates a new resource, there should be a choice to make it temporary
Title: Message Title D Pasto commented on JENKINS-55486 Re: If lock() creates a new resource, there should be a choice to make it temporary I can see several ways of addressing this issue - this ticket is a small improvement that will get us a nice improvement, while JENKINS-53332 addresses the scenario, and JENKINS-44141 is a larger goal but is short on detail Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-19046) ClassCastException: cannot assign instance of hudson.remoting.ProxyOutputStream$Chunk to field java.lang.Throwable.suppressedExceptions of type java.util.List in instance of hud
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce There is no more interest or information recently in this issue than there has been for a long time. I will go ahead and close it as Cannot Reproduce. Jenkins / JENKINS-19046 ClassCastException: cannot assign instance of hudson.remoting.ProxyOutputStream$Chunk to field java.lang.Throwable.suppressedExceptions of type java.util.List in instance of hudson.remoting.Command$Source Change By: Jeff Thompson Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55257) Timestamper break builds on Windows agents
Title: Message Title Jeff Thompson commented on JENKINS-55257 Re: Timestamper break builds on Windows agents I tried reproducing this on 2.150.1 with Windows Server 2016. Everything worked fine. As Jesse said originally it's most likely a configuration issue. Or possibly some interaction with another another plugin. There is no indication this is a Remoting problem. And probably not a Timestamper problem. As reported there is insufficient information to reproduce or analyze. If anyone can provide further details, isolate the problem more, or troubleshoot their configuration that we be useful. Otherwise it's probably best to mark this as Cannot Reproduce. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55436) warnings-ng is not backwards compatible
Title: Message Title Matthias Fuchs commented on JENKINS-55436 Re: warnings-ng is not backwards compatible Maybe the reason that checkstyle is working but not the others is the different names. In the checkstyle plugin the exposed symbol in the pipeline is check*s*tyle while warning-ng exposes check*S*tyle. Thus there is no clash. At the same time the exposed symbol for android lint is androidLint in both the android-lint plugin and the new plugin, respectively for pmd. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55466) PCT: maven-hpi-plugin fails to copy plugin's plugins dependencies to run the tests
Title: Message Title Adrien Lecharpentier updated JENKINS-55466 After discussing and reviewing the code, PCT expected to be able to resolve the dependency of the plugin we try to validate. So if we are working on a SNAPSHOT, which has a dependency to a module which is cannot be resolved outside of the local environment, the module needs to be installed in the localRepository. Jenkins / JENKINS-55466 PCT: maven-hpi-plugin fails to copy plugin's plugins dependencies to run the tests Change By: Adrien Lecharpentier Status: Open Fixed but Unreleased Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55453) Github PR creating job but not building
Title: Message Title Tyler Pickett commented on JENKINS-55453 Re: Github PR creating job but not building After looking at this again I'm seeing matching IDs, I could have sworn they didn't match before though. I'll keep trying to gather more info. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55492) Plugin is not reusing stopped AWS EC2 instances
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-55492 Re: Plugin is not reusing stopped AWS EC2 instances Are the nodes in stop state created before the update ? From 1.39 to 1.41 has been changed the tag labeling, in your case if the nodes was created before the upgrade the label associated is not recognize by the new version. What is reported in the log in term of the number of stopped instances ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55471) Git fetch timeout
Title: Message Title Mark Waite updated JENKINS-55471 The message in the fetch-timeout.txt file indicates that the failure is truly a timeout due to the clone time. Changes from git client plugin 2.7.4 to 2.7.5 have no relationship to any area of the code that would involve timeout. For hints on managing large git repositories, refer to my 2017 "Git in the Large" slides and to my 2016 "Large git repositories" slides, both from Jenkins World lightning talks. Jenkins / JENKINS-55471 Git fetch timeout Change By: Mark Waite Status: Open Fixed but Unreleased 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-55466) PCT: maven-hpi-plugin fails to copy plugin's plugins dependencies to run the tests
Title: Message Title Adrien Lecharpentier commented on JENKINS-55466 Re: PCT: maven-hpi-plugin fails to copy plugin's plugins dependencies to run the tests It seems that the problem is only with multi-module and with how the dependencies, when pointed to a module, are resolved. I re-run the test on structs for example. It's not working correctly and after running mvn install PCT is not failing (well, tests are failing but that's on the plugin, not on PCT). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-50729) exception when cleaning workspace
Title: Message Title
Mark Waite edited a comment on JENKINS-50729
Re: exception when cleaning workspace
[~msanders] and [~michal_gliniecki] please open a new bug report. The stack trace in your bug reports do not include the exotically named file that is mentioned as the critical attribute of this bug report. There was a [Jenkins core change|https://github.com/jenkinsci/jenkins/commits/65ecd43ecea3c3798b517959ce3e84201442492d/core/src/main/java/jenkins/util/io/PathRemover.java] by [~jvz] in Jenkins 2.157 that seems like it might be involved in this case but is not involved in the original bug report to which you attached your stack trace.When you open that new bug, please make the component {{core}} and the assignee [~jvz].
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-55284) Command line git tag collision behavior changed in git 2.20
Title: Message Title Mark Waite edited a comment on JENKINS-55284 Re: Command line git tag collision behavior changed in git 2.20 Shame on me! I fixed the unit test which discovered the problem but failed to test the problem in a real world use case. I've created a [real world use case| http https :// example github .com /MarkEWaite/jenkins-bugs/blob/JENKINS-55284/Jenkinsfile ] and confirmed that it fails in that use case.Sorry about the incomplete fix in git client plugin 2.7.5.Please be sure to review the git tag man page which explains why moving tags is strongly discouraged. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55284) Command line git tag collision behavior changed in git 2.20
Title: Message Title Mark Waite reopened an issue Shame on me! I fixed the unit test which discovered the problem but failed to test the problem in a real world use case. I've created a real world use case and confirmed that it fails in that use case. Sorry about the incomplete fix in git client plugin 2.7.5. Please be sure to review the git tag man page which explains why moving tags is strongly discouraged. Jenkins / JENKINS-55284 Command line git tag collision behavior changed in git 2.20 Change By: Mark Waite Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55492) Plugin is not reusing stopped AWS EC2 instances
Title: Message Title David Goate created an issue Jenkins / JENKINS-55492 Plugin is not reusing stopped AWS EC2 instances Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-01-09 17:01 Environment: Plugin version 1.42 Priority: Major Reporter: David Goate Using 1.39 of the plugin, the behaviour I observed was that when the instance cap was set to 2 and 2 slaves were already provisioned (e.g. in the stopped EC2 state rather than terminated), when a slave is required for a pending queued build, the plugin used to simply start one of the 2 stopped instances as required. Now, on 1.42, the plugin appears to leave the previous 2 EC2 instances in the stopped state on AWS and provision a brand new slave, leading to it exceeding the instance cap of 2 and there now being 3 EC2 instances (albeit 2 stopped and only 1 running). For now, my workaround was to go back to 1.39. Add Comment
[JIRA] (JENKINS-18796) Promoted Parameter String not valorised in publish-over-ssh Script (Exec command)
Title: Message Title Alex Earl commented on JENKINS-18796 Re: Promoted Parameter String not valorised in publish-over-ssh Script (Exec command) I don't currently have a way to replicate promotion issues, so the more detail on the configuration, the better Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55491) AWS Private key stored as plain text - when using Config as Code plugin
Title: Message Title Tim Brown created an issue Jenkins / JENKINS-55491 AWS Private key stored as plain text - when using Config as Code plugin Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-01-09 16:36 Priority: Minor Reporter: Tim Brown I have been playing about with creating a Jenkins instance from scratch. One of my key criteria is that I should be able to simply redeploy a new Docker container in an environment and quickly get a new setup which closely matches the previous setup (in terms of configuration). To do this I looked at the Config as Code plugin, which works well for my purposes. After configuring the EC2 plugin I found that the private key is stored by the ConfigAsCode plugin in plain text - which is bad as I want my config in source control. Can you allow the private key to be stored using the Credentials plugin instead (or as well as)? Add Comment
[JIRA] (JENKINS-55489) Update Jenkins upstream version from snapshot
Title: Message Title David Olorundare updated an issue Jenkins / JENKINS-55489 Update Jenkins upstream version from snapshot Change By: David Olorundare See details in attached links.Currently the project uses a snapshot version of Jenkins to consume the API changes, as the changes the snapshot contains have yet to be merged into the Jenkins main repository master branch.Thus, the Jenkins version used in the project will need to be updated once the upstream changes have been merged into the upstream Jenkins main repository and released publicly for use. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55465) Empty console when properties compressBuildLog() is enabled
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-55465 Empty console when properties compressBuildLog() is enabled Change By: Jesse Glick Status: Open Resolved 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-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title Victor Verbitsky commented on JENKINS-55139 Re: ansicolor 0.6.0 shows terminal escape sequences in console log I tried this snapshot and it's makes no difference... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54088) Log audit events for user creation
Title: Message Title Matt Sicker updated JENKINS-54088 Merged to master, new ticket made for cleaning up the snapshot stuff. Jenkins / JENKINS-54088 Log audit events for user creation Change By: Matt Sicker Status: In Review 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-18796) Promoted Parameter String not valorised in publish-over-ssh Script (Exec command)
Title: Message Title Dan Davids commented on JENKINS-18796 Re: Promoted Parameter String not valorised in publish-over-ssh Script (Exec command) Affected by the same issue. Any updates 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-55448) File cleaning failure, old build and plugin update
Title: Message Title Uwe Schindler edited a comment on JENKINS-55448 Re: File cleaning failure, old build and plugin update Maybe that's the reason for the whole thing: If anywhere in the path up to the root folder there is a symlink, the delete directory stull stuff breaks. In our case the home directory of jenkins was a symlink. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55448) File cleaning failure, old build and plugin update
Title: Message Title Uwe Schindler commented on JENKINS-55448 Re: File cleaning failure, old build and plugin update Maybe that's the reason for the whole thing: If anywhere in the path up to the root folder there is a symlink, the delete directory stull breaks. In our case the home directory of jenkins was a symlink. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55303) script-security - Using JDK internal classes
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-55303
script-security - Using JDK internal classes
Change By:
Devin Nusbaum
When trying to validate {{script-security}} plugin with PCT for Java 11, I got test failures with the following output When trying to validate { {script-security}} plugin with PCT for Java 11, I got test failures with the following output{ noformat}java.lang.reflect.InaccessibleObjectException: Unable to make field private static final java.lang.module.Configuration java.lang.module.Configuration.EMPTY_CONFIGURATION accessible: module java.base does not "opens java.lang.module" to unnamed module @5ebd56e9 at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340) at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280) at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:176) at java.base/java.lang.reflect.Field.setAccessible(Field.java:170) at org.netbeans.insane.impl.InsaneEngine.processClass(InsaneEngine.java:238) at org.netbeans.insane.impl.InsaneEngine.process(InsaneEngine.java:199) at org.netbeans.insane.impl.InsaneEngine.traverse(InsaneEngine.java:97) at org.netbeans.insane.impl.LiveEngine.traceImpl(LiveEngine.java:188) at org.netbeans.insane.impl.LiveEngine.trace(LiveEngine.java:166) at org.jvnet.hudson.test.MemoryAssert.fromRoots(MemoryAssert.java:292) at org.jvnet.hudson.test.MemoryAssert.assertGC(MemoryAssert.java:178) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovyMemoryLeakTest.loaderReleased(GroovyMemoryLeakTest.java:62) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)at org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:548)at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)at java.base/java.lang.Thread.run(Thread.java:834){noformat}
[JIRA] (JENKINS-55448) File cleaning failure, old build and plugin update
Title: Message Title Uwe Schindler commented on JENKINS-55448 Re: File cleaning failure, old build and plugin update We have seen the same issue when the jenkins home folder is a symlink. The issue went away, when we changed this to be an absolute path. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55490) syntax in a largish pom.xml, ArrayIndexOutOfBoundsException
Title: Message Title Kathryn Nixon created an issue Jenkins / JENKINS-55490 syntax in a largish pom.xml, ArrayIndexOutOfBoundsException Issue Type: Bug Assignee: Unassigned Attachments: plexus-pom.xml Components: maven-plugin Created: 2019-01-09 16:05 Environment: Jenkins version 2.138.3 https://plugins.jenkins.io/maven-plugin v3.1.2 Priority: Minor Reporter: Kathryn Nixon maven project job errors while parsing a largish pom that contains re-creatable in a similar way to the dependency bug (fixed in v3.1.0) described here : https://github.com/codehaus-plexus/plexus-utils/issues/22 To recreate the problem, set up a maven project job with the attached plexus-pom.xml, and run 'mvn clean verify' ERROR: Processing failed due to a bug in the code. Please report this to the issue tracker (https://jenkins.io/redirect/report-an-issue). java.lang.ArrayIndexOutOfBoundsException: 15418 at org.codehaus.plexus.util.xml.pull.MXParser.parsePI(MXParser.java:2502) at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1283) at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1131) at org.codehaus.plexus.util.xml.pull.MXParser.nextTag(MXParser.java:1116)
[JIRA] (JENKINS-55489) Update Jenkins upstream version from snapshot
Title: Message Title David Olorundare updated an issue Jenkins / JENKINS-55489 Update Jenkins upstream version from snapshot Change By: David Olorundare See details in attached links.Currently the project uses a snapshot version of Jenkins to consume the API changes, as the changes the snapshot contains have yet to be merged into the Jenkins main repository branch.Thus, the Jenkins version used in the project will need to be updated once the upstream changes have been merged into the Jenkins main repository and released publicly for use . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55489) Update Jenkins upstream version from snapshot
Title: Message Title David Olorundare updated an issue Jenkins / JENKINS-55489 Update Jenkins upstream version from snapshot Change By: David Olorundare See details in attached link links . Currently the project uses a snapshot version of Jenkins to consume the API changes, as the changes the snapshot contains have yet to be merged into the Jenkins main repo repository branch.Thus, the Jenkins version used in the project will need to be updated once the upstream changes have been merged into the Jenkins main repo repository and released publicly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55303) script-security - Using JDK internal classes
Title: Message Title Adrien Lecharpentier commented on JENKINS-55303 Re: script-security - Using JDK internal classes Vivek Pandey I changed the component here as well. Sorry for the wrong assignment. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55303) script-security - Using JDK internal classes
Title: Message Title Adrien Lecharpentier updated an issue Jenkins / JENKINS-55303 script-security - Using JDK internal classes Change By: Adrien Lecharpentier Component/s: jenkins-test-harness Component/s: script-security-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-54088) Log audit events for user creation
Title: Message Title David Olorundare commented on JENKINS-54088 Re: Log audit events for user creation follow-up ticket would be good. I just created one. JENKINS-55489 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55489) Update Jenkins upstream version from snapshot
Title: Message Title David Olorundare created an issue Jenkins / JENKINS-55489 Update Jenkins upstream version from snapshot Issue Type: Task Assignee: Unassigned Components: audit-log-plugin Created: 2019-01-09 15:59 Labels: audit-logging Priority: Minor Reporter: David Olorundare See details in attached link. Currently the project uses a snapshot version of Jenkins to consume the API changes, as the changes the snapshot contains have yet to be merged into the Jenkins main repo branch. Thus, the Jenkins version used in the project will need to be updated once the upstream changes have been merged into the Jenkins main repo and released publicly. Add Comment
[JIRA] (JENKINS-55465) Empty console when properties compressBuildLog() is enabled
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-55465 Empty console when properties compressBuildLog() is enabled Change By: Devin Nusbaum Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55303) script-security - Using JDK internal classes
Title: Message Title Vivek Pandey commented on JENKINS-55303 Re: script-security - Using JDK internal classes Isa Vilacides was opened as minor so didn't get our attention. From the stack trace it looks like issue somewhere in jenkins-test-harness. We are going to investigate as whats goin in there. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54088) Log audit events for user creation
Title: Message Title Matt Sicker commented on JENKINS-54088 Re: Log audit events for user creation Changes merged to master, but we're still using a snapshot version of Jenkins to consume the API changes. Do you think we should create a follow up ticket to update the jenkins version here when the upstream PR is merged and released? Or should we just leave this ticket open in review? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55303) script-security - Using JDK internal classes
Title: Message Title Devin Nusbaum commented on JENKINS-55303 Re: script-security - Using JDK internal classes Yeah, the problem is that MemoryAssert in jenkins-test-harness uses the Netbeans Insane Library to do live heap analysis, making it possible to do things like write a test to check for memory leaks (which is what script-security is doing). It looks like there are a few other uses of MemoryAssert, notably including workflow-job. There are new releases of org-netbeans-insane available, but I would be very surprised if they were able to be updated to be compliant with the Java 9+ module system. It seems like what that library is doing fundamentally requires access to JDK-internal classes and data structures. If we think the test in script-security would be valuable for detecting memory leaks in the future, then maybe we could just add an assumption so it only runs on JDK 8? Otherwise, I think we'd just have to remove the tests and eventually MemoryAssert itself. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54965) Create unit tests for code implementations
Title: Message Title Matt Sicker updated JENKINS-54965 Merged to master. Jenkins / JENKINS-54965 Create unit tests for code implementations Change By: Matt Sicker Status: In Review 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-55303) script-security - Using JDK internal classes
Title: Message Title Adrien Lecharpentier commented on JENKINS-55303 Re: script-security - Using JDK internal classes you are totally right Andrew Bayer and it seems I need a slap on the back of my head.. I just faced this only on script-security because I guess it's the only plugin I tested to use this 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55488) How to fetch the changelog specific to a repo when we have multiple SCM chcekout in Jenkinsfile
Title: Message Title
Raj G created an issue
Jenkins / JENKINS-55488
How to fetch the changelog specific to a repo when we have multiple SCM chcekout in Jenkinsfile
Issue Type:
Task
Assignee:
Unassigned
Components:
pipeline
Created:
2019-01-09 15:41
Priority:
Major
Reporter:
Raj G
Hi, In my Jenkinsfile, I've below configuration to checkout two SCM repos. stage('Multiple SCM checkuot'){ checkout([$class: 'GitSCM', branches: [[name: '${SERVICE_REPO_BRANCH1}']], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[credentialsId: 'GitHubCredentials', url: '${SERVICE_REPO_URL1}']]]) checkout([$class: 'GitSCM', branches: [[name: '${SERVICE_REPO_BRANCH2}']], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[credentialsId: 'GitHubCredentials', url: '${SERVICE_REPO_URL2}']]]) } Now I am fetching the changeLog using below code snippet. currentBuild.changeSets The above method is giving me the change sets from both the repos but I want to fetch the changesets specific to one repo. Please suggest on this.
Add Comment
[JIRA] (JENKINS-55284) Command line git tag collision behavior changed in git 2.20
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-55284
Command line git tag collision behavior changed in git 2.20
Change By:
Mark Waite
The unit tests on the git client plugin master branch (git client plugin 3.0.0 targeted release) and the stable-2.7 branch are showing a repeatable failure in the CliGitAPIImplTest.test_fetch_with_updated_tag when run with command line git 2.20.1.Git for Windows now delivers command line git 2.20.1 as does Debian Unstable ("sid"). Other vendors are likely to include git 2.20.1 as well.[Git 2.20.0 release notes|https://github.com/git/git/blob/b21ebb671bb7dea8d342225f0d66c41f4e54d5ca/Documentation/RelNotes/2.20.0.txt#L11] explain the change as:{quote}"git push" into refs/tags/* hierarchy is rejected without getting forced, but "git fetch" (misguidedly) used the "fast forwarding" rule used for the refs/heads/* hierarchy; this has been corrected, which means some fetches of tags that did not fail with older version of Git will fail without "--force" with this version.{quote}The git client plugin seems to have been relying on the misguided fast forward rule.The [man page|https://git-scm.com/docs/git-tag#_on_re_tagging] for git 2.20 recommends *strongly* against moving (re-tagging) a tag on a shared repository. It says:{quote}However, Git does *not* (and it should not) change tags behind users back. So if somebody already got the old tag, doing a git pull on your tree shouldn’t just make them overwrite the old one.If somebody got a release tag from you, you cannot just change the tag for them by updating your own one. This is a big security issue, in that people MUST be able to trust their tag-names. If you really want to do the insane thing, you need to just fess up to it, and tell people that you messed up. {quote}The test_fetch_with_updated_tag results report:{noformat}hudson.plugins.git.GitException: Command "git fetch -t /tmp/jkh1542368834541434789" returned status code 1:stdout: stderr: * branchHEAD -> FETCH_HEAD ! [rejected]t -> t (would clobber existing tag){noformat}That test is trying to fetch a tag from the remote when the remote has updated the tag to point to a different SHA1.This affects git client plugin 2.7.4 and git client plugin 3.0.0. Not yet clear which Jenkins use cases are harmed, only that there is a behavior change in command line git that the git client plugin automated tests have detected.
[JIRA] (JENKINS-55303) script-security - Using JDK internal classes
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-55303
script-security - Using JDK internal classes
Change By:
Devin Nusbaum
When trying to validate {{script-security}} plugin with PCT for Java 11, I got test failures with the following output When trying to validate { {script-security}} plugin with PCT for Java 11, I got test failures with the following output{ noformat}java.lang.reflect.InaccessibleObjectException: Unable to make field private static final java.lang.module.Configuration java.lang.module.Configuration.EMPTY_CONFIGURATION accessible: module java.base does not "opens java.lang.module" to unnamed module @ 5ebd56e9java.lang.reflect.InaccessibleObjectException: Unable to make field private static final java.lang.module.Configuration java.lang.module.Configuration.EMPTY_CONFIGURATION accessible: module java.base does not "opens java.lang.module" to unnamed module @ 5ebd56e9at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340)at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280)at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:176)at java.base/java.lang.reflect.Field.setAccessible(Field.java:170)at org.netbeans.insane.impl.InsaneEngine.processClass(InsaneEngine.java:238)at org.netbeans.insane.impl.InsaneEngine.process(InsaneEngine.java:199)at org.netbeans.insane.impl.InsaneEngine.traverse(InsaneEngine.java:97)at org.netbeans.insane.impl.LiveEngine.traceImpl(LiveEngine.java:188)at org.netbeans.insane.impl.LiveEngine.trace(LiveEngine.java:166)at org.jvnet.hudson.test.MemoryAssert.fromRoots(MemoryAssert.java:292)at org.jvnet.hudson.test.MemoryAssert.assertGC(MemoryAssert.java:178)at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovyMemoryLeakTest.loaderReleased(GroovyMemoryLeakTest.java:62)at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.base/java.lang.reflect.Method.invoke(Method.java:566)at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:548) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) at
[JIRA] (JENKINS-55483) ec2-plugin Wrong order of workers termination
Title: Message Title Jiri Polansky updated an issue Jenkins / JENKINS-55483 ec2-plugin Wrong order of workers termination Change By: Jiri Polansky Attachment: AwsCloudTrail.log Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55303) script-security - Using JDK internal classes
Title: Message Title Andrew Bayer commented on JENKINS-55303 Re: script-security - Using JDK internal classes From at org.jvnet.hudson.test.MemoryAssert.fromRoots(MemoryAssert.java:292) at org.jvnet.hudson.test.MemoryAssert.assertGC(MemoryAssert.java:178) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovyMemoryLeakTest.loaderReleased(GroovyMemoryLeakTest.java:62) in that output, it looks to be something in jenkins-test-harness? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55485) Declarative pipeline, lock() in stage options is executed before when clause
Title: Message Title
D Pasto updated an issue
Jenkins / JENKINS-55485
Declarative pipeline, lock() in stage options is executed before when clause
Change By:
D Pasto
In a a declarative pipeline i have a stage grouping several other stages and need to hold a lock for the duration of the group. I see I can add lock() to the options of the group and it works fine in that scenario. However the group also has a When clause so I can turn that group off with a job parameter. The problem is that when the "when" evaluates false so the stage will be skipped, it wait for the lock anyway. If the stage will be skipped for any reason, we should not block on the lock. The "when" defines a "beforeAgent" attribute for a similar need, so that might be an approach, but I'm not seeing a scenario where you would want to do it in the current order. My pipeline looks like: --- — pipeline {agent none stages { stage ('Build') { { } stage('Deploy-and-Test') { // Group Stage Deploy and test the Build - lock the deployment VM so we don't step on other runs when { _expression_ { "${params.Deploy}" == "true" } beforeAgent true } options { lock(quantity: 1, resource: "${params.DeployAgent}", variable: 'myDeployAgent') } agent none stages \{ ...} }}} When I run it withthe param to disable the stage I see: --- — [Pipeline] stage[Pipeline] { (Deploy-and-Test)[Pipeline] lockTrying to acquire lock on [DeploymentVM_Win]Lock acquired on [DeploymentVM_Win][Pipeline] {Stage "Deploy-and-Test" skipped due to when conditional --- — Since the stage is being skipped there is no point in holding the lock, but it the lock is already allocated, this will block anyway. The lock() should be processed _after_ the decision whether to execute the stage.
Add Comment
[JIRA] (JENKINS-55453) Github PR creating job but not building
Title: Message Title Tyler Pickett commented on JENKINS-55453 Re: Github PR creating job but not building Some additional info on this, we noticed some warnings in the administrative UI and inspected some additional logs and we're getting the following for several of our repos: Jan 09, 2019 3:15:26 PM WARNING org.jenkinsci.plugins.github.webhook.WebhookManager$2 applyNullSafeFailed to add GitHub webhook for GitHubRepositoryName[host=github.com,username=Instructure,repository=] java.io.FileNotFoundException: https://api.github.com/repos/instructure//hooks/ at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) After seeing that I looked at what what GitHub thought those hook-id values should be and they don't match what is in the logs. I wonder if that's the root of our problem. Which config files have that data, I'd like to try to make them match what GitHub has in their 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-55485) Declarative pipeline, lock() in stage options is executed before when clause
Title: Message Title D Pasto updated an issue Jenkins / JENKINS-55485 Declarative pipeline, lock() in stage options is executed before when clause Change By: D Pasto Summary: Declarative pipeline, lock() in stage aoptions options is executed before when clause Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55483) ec2-plugin Wrong order of workers termination
Title: Message Title Jiri Polansky edited a comment on JENKINS-55483 Re: ec2-plugin Wrong order of workers termination Spot instance was terminated by ec2 plugin ( Client.UserInitiatedShutdown Event name : User initiated CancelSpotInstanceRequests ). Node was available for some moment during instance spot termination and node removal from Jenkins. Therefore a new job was assigned. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55465) Empty console when properties compressBuildLog() is enabled
Title: Message Title Devin Nusbaum commented on JENKINS-55465 Re: Empty console when properties compressBuildLog() is enabled Are there any related error messages in your Jenkins logs? It looks like the compressBuildLog property comes from Compress Build Log Plugin, but based on the description on that page I think the decompression side of things is handled somewhere in a core API. It is certainly possible that this functionality is broken in workflow-job 2.26+, although I am not sure why or what would be required to get it working again. Note also that in workflow-job 2.26+, log data is no longer duplicated in individual step logs, so your logs should automatically take 50% less space, so turning off compression might be a good short term solution. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55483) ec2-plugin Wrong order of workers termination
Title: Message Title Jiri Polansky commented on JENKINS-55483 Re: ec2-plugin Wrong order of workers termination Spot instance was terminated by ec2 plugin (Client.UserInitiatedShutdown: User initiated). Node was available for some moment during instance spot termination and node removal from Jenkins. Therefore a new job was assign. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55483) ec2-plugin Wrong order of workers termination
Title: Message Title Jiri Polansky edited a comment on JENKINS-55483 Re: ec2-plugin Wrong order of workers termination Spot instance was terminated by ec2 plugin (Client.UserInitiatedShutdown: User initiated). Node was available for some moment during instance spot termination and node removal from Jenkins. Therefore a new job was assign assigned . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.
