[JIRA] (JENKINS-54261) Submit ( go ) on Email Template Testing produces blank screen
Title: Message Title Steve Graham updated an issue Jenkins / JENKINS-54261 Submit ( go ) on Email Template Testing produces blank screen Change By: Steve Graham Component/s: core Component/s: emailext-template-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-54261) Submit ( go ) on Email Template Testing produces blank screen
Title: Message Title Steve Graham updated an issue Jenkins / JENKINS-54261 Submit ( go ) on Email Template Testing produces blank screen Change By: Steve Graham Jenkins 2.148 Email Template Testing broken - results from submit immediately replaced with blank screen Rollback to Jenkins 2.147 fixes issue. Nothing to do with the emailext-template-plugin - no new version, works on jenkins 2.147 Possibly due to change for :-> Make form submit buttons on the Jenkins classic UI compatible with potentially upcoming Firefox bug fix. (issue 53462, [Firefox bug 1370630|https://bugzilla.mozilla.org/show_bug.cgi?id=1370630]) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54261) Submit ( go ) on Email Template Testing produces blank screen
Title: Message Title Steve Graham updated an issue Jenkins / JENKINS-54261 Submit ( go ) on Email Template Testing produces blank screen Change By: Steve Graham Summary: GO Submit ( go ) on Email Template Testing produces blank screen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54261) GO on Email Template Testing produces blank screen
Title: Message Title Steve Graham updated an issue Jenkins / JENKINS-54261 GO on Email Template Testing produces blank screen Change By: Steve Graham Jenkins 2.148 Email Template Testing broken - results from submit immediately replaced with blank screen Rollback to Jenkins 2.147 fixes issue.Possibly due to change for :-> Make form submit buttons on the Jenkins classic UI compatible with potentially upcoming Firefox bug fix. (issue 53462, [Firefox bug 1370630|https://bugzilla.mozilla.org/show_bug.cgi?id=1370630]) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54261) GO on Email Template Testing produces blank screen
Title: Message Title Steve Graham updated an issue Jenkins / JENKINS-54261 GO on Email Template Testing produces blank screen Change By: Steve Graham Jenkins 2.148 Email Template Testing broken - results immediately replaced with blank screen Rollback to Jenkins 2.147 fixes issue.Possibly due to change for :-> Make form submit buttons on the Jenkins classic UI compatible with potentially upcoming Firefox bug fix. (issue 53462, [Firefox bug 1370630|https://bugzilla.mozilla.org/show_bug.cgi?id=1370630]) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54261) GO on Email Template Testing produces blank screen
Title: Message Title Steve Graham created an issue Jenkins / JENKINS-54261 GO on Email Template Testing produces blank screen Issue Type: Bug Assignee: Alex Earl Components: emailext-template-plugin Created: 2018-10-26 05:30 Environment: jenkins 2.148 Browser - chrome and IE Priority: Minor Reporter: Steve Graham Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email
[JIRA] (JENKINS-54144) Job fails as JiraSCMListsener/JiraSite potentially creating Executor with 0 threads
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-54144 Job fails as JiraSCMListsener/JiraSite potentially creating Executor with 0 threads Change By: Olivier Lamy Component/s: blueocean-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-54144) Job fails as JiraSCMListsener/JiraSite potentially creating Executor with 0 threads
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-54144 Job fails as JiraSCMListsener/JiraSite potentially creating Executor with 0 threads Change By: Olivier Lamy Component/s: jira-plugin Component/s: blueocean-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-54144) Job fails as JiraSCMListsener/JiraSite potentially creating Executor with 0 threads
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-54144 Job fails as JiraSCMListsener/JiraSite potentially creating Executor with 0 threads Change By: Olivier Lamy Labels: jira-plugin-3.0.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Olivier Lamy Labels: jira-plugin-3.0.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Olivier Lamy Assignee: Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54144) Job fails as JiraSCMListsener/JiraSite potentially creating Executor with 0 threads
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-54144 Job fails as JiraSCMListsener/JiraSite potentially creating Executor with 0 threads Change By: Olivier Lamy Assignee: Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-48296) Multibranch pipeline - ignore commits from certain user
Title: Message Title dan tran commented on JENKINS-48296 Re: Multibranch pipeline - ignore commits from certain user We are using BB to ignore the commit user, but is get reset every multi branch job rescanned ouch Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54260) Fails when notifying for merged PR build
Title: Message Title Sean MacKay created an issue Jenkins / JENKINS-54260 Fails when notifying for merged PR build Issue Type: Bug Assignee: Antonio Mansilla Components: bitbucket-build-status-notifier-plugin Created: 2018-10-25 23:11 Priority: Minor Reporter: Sean MacKay Flagged as minor because one workaround is just not to merge your PRs before building (losing the functionality of testing the merge result also builds). There may also be a way to tell the jenkinsfile to only notify if it's not a merged PR build. The Bitbucket Build Status Notifier Plugin fails when building a PR with the "Merging the pull request with the current target branch revision" PR policy, with the following error: [Bitbucket] Notifying pull request build result [Bitbucket] Build result notified Also: java.lang.Exception: None or multiple repos java.lang.Exception: None or multiple repos at org.jenkinsci.plugins.bitbucket.scm.GitScmAdapter.getCommitRepoMap(GitScmAdapter.java:53) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper.createBuildStatusResources(BitbucketBuildStatusHelper.java:87) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper.createBuildStatusResources(BitbucketBuildStatusHelper.java:140) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper.notifyBuildStatus(BitbucketBuildStatusHelper.java:231) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifierStep$Execution.run(BitbucketBuildStatusNotifierStep.java:206) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifierStep$Execution.run(BitbucketBuildStatusNotifierStep.java:152) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at
[JIRA] (JENKINS-48446) TestInProgress stopped working with Jenkins core 2.85
Title: Message Title Jeff Thompson updated an issue Jenkins / JENKINS-48446 TestInProgress stopped working with Jenkins core 2.85 Change By: Jeff Thompson Labels: remoting Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-48446) TestInProgress stopped working with Jenkins core 2.85
Title: Message Title Jeff Thompson commented on JENKINS-48446 Re: TestInProgress stopped working with Jenkins core 2.85 There isn't sufficient information to progress with this as a remoting issue. It doesn't look there is much interest in the testinprogress-plugin either so it's unlikely that we'll get more information from that side. I'll remove Remoting from this ticket. I someone wants to bring testinprogress-plugin up to date and still encounters issues relating to Remoting, we can address those. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54252) unstash very slow blocked on SecureRandom
Title: Message Title Jeff Thompson commented on JENKINS-54252 Re: unstash very slow blocked on SecureRandom See the documentation for Pipeline:stash: https://jenkins.io/doc/pipeline/steps/workflow-basic-steps/#stash-stash-some-files-to-be-used-later-in-the-build "Note that the stash and unstash steps are designed for use with small files. For large data transfers, use the External Workspace Manager plugin, or use an external repository manager such as Nexus or Artifactory. This is because stashed files are archived in a compressed TAR, and with large files this demands considerable on-master resources, particularly CPU time. There's not a hard stash size limit, but between 5-100 MB you should probably consider alternatives." Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54252) unstash very slow blocked on SecureRandom
Title: Message Title Jeff Thompson closed an issue as Not A Defect Jenkins / JENKINS-54252 unstash very slow blocked on SecureRandom Change By: Jeff Thompson Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54202) Too much output from SH executor causes the agent to freeze
Title: Message Title Jeff Thompson commented on JENKINS-54202 Re: Too much output from SH executor causes the agent to freeze Could you provide any further logging output? Particularly agent logs. My attempts at reproduction haven't succeeded yet. I haven't tried it with your configuration as I don't have Ubuntu systems immediately available. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53162) Blueocean support for visualizing stages in parallel block in scripted pipeline
Title: Message Title leromarinvit commented on JENKINS-53162 Re: Blueocean support for visualizing stages in parallel block in scripted pipeline I dug into this a little and found that BlueOcean explicitly disables rendering sequential stages in parallel branches unless the build is a declarative pipeline run. So a quick and dirty workaround is to fake a declarative pipeline in a scripted one. Then arrange your stages similarly to what declarative would do (namely create a wrapper stage with the same name as each parallel branch), and it will be rendered nicely. Needless to say, this is an ugly hack and might break in unforeseen ways. Though it seems to work in my tests, and the only side effect I saw was that a "Restart from Stage" option appeared in the build's menu, with an empty dropdown list. This seems benign enough, but I don't know what else it could cause, so be warned. So how do you fake a declarative run? BlueOcean checks for an action of type ExecutionModelAction, so that's what we have to add: import org.jenkinsci.plugins.pipeline.modeldefinition.actions.ExecutionModelAction import org.jenkinsci.plugins.pipeline.modeldefinition.ast.ModelASTStages if (!currentBuild.rawBuild.getAction(ExecutionModelAction)) currentBuild.rawBuild.addAction(new ExecutionModelAction(new ModelASTStages(null))) This won't work in a sandboxed script, but it does in a global shared library. So it's probably not worth the effort (and potential risk) to make jobs with hand-written parallel-sequential stages render properly, but it might just be a workaround if you generate jobs with such a structure from library functions. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You
[JIRA] (JENKINS-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title
Hal Deadman edited a comment on JENKINS-54131
Re: "Failed to parse changelog" in JIRA plugin 3.0.3
We are getting similar error when we run the following from a pipeline:jiraComment body: env.runningComment, issueKey: env.jiraIssueId { color code : #9a java } [Pipeline] jiraComment{color}Error jiraCommentError when executing success post condition:java.lang.IllegalArgumentException at java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1314) at java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1237) at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151) at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:457) at hudson.plugins.jira.JiraSite.getSession(JiraSite.java:426) at hudson.plugins.jira.pipeline.CommentStep$CommentStepExecution.run(CommentStep.java:80) at hudson.plugins.jira.pipeline.CommentStep$CommentStepExecution.run(CommentStep.java:64) 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) {code} We downgraded to 3.0.2 and the error didn't happen.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Hal Deadman commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 We are getting similar error when we run the following from a pipeline: jiraComment body: env.runningComment, issueKey: env.jiraIssueId [Pipeline] jiraCommentError when executing success post condition: java.lang.IllegalArgumentException at java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1314) at java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1237) at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151) at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:457) at hudson.plugins.jira.JiraSite.getSession(JiraSite.java:426) at hudson.plugins.jira.pipeline.CommentStep$CommentStepExecution.run(CommentStep.java:80) at hudson.plugins.jira.pipeline.CommentStep$CommentStepExecution.run(CommentStep.java:64) 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) We downgraded to 3.0.2 and the error didn't happen. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54255) xUnit sets build status incorrectly
Title: Message Title Nikolas Falco commented on JENKINS-54255 Re: xUnit sets build status incorrectly Update xunit plugin to latest version Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Hal Deadman updated an issue Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Hal Deadman Attachment: Attachment.url Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Hal Deadman updated an issue Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Hal Deadman Attachment: Attachment.url Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54259) "Missing End Delimiter" when creating the first admin account
Title: Message Title mark grandi created an issue Jenkins / JENKINS-54259 "Missing End Delimiter" when creating the first admin account Issue Type: Bug Assignee: Oleg Nenashev Attachments: support_2018-10-25_21.03.29.zip Components: _unsorted Created: 2018-10-25 21:13 Priority: Minor Reporter: mark grandi I downloaded the jenkins docker image from https://hub.docker.com/r/jenkins/jenkins/ to test something locally without using my company's instance, and when setting it up with the first admin account, it barfed with a stack trace: (snipped version): java.lang.IllegalArgumentException: Invalid indexed property '["password1",' on bean class 'class hudson.security.HudsonPrivateSecurityRealm$SignupInfo' Missing End Delimiter at org.apache.commons.beanutils.PropertyUtilsBean.getIndexedProperty(PropertyUtilsBean.java:397) at org.apache.commons.beanutils.PropertyUtilsBean.getNestedProperty(PropertyUtilsBean.java:768) at org.apache.commons.beanutils.BeanUtilsBean.getNestedProperty(BeanUtilsBean.java:715) at org.apache.commons.beanutils.BeanUtilsBean.getProperty(BeanUtilsBean.java:741) at org.apache.commons.beanutils.BeanUtils.getProperty(BeanUtils.java:382) at org.kohsuke.stapler.RequestImpl.fill(RequestImpl.java:580) at org.kohsuke.stapler.RequestImpl.bindParameters(RequestImpl.java:391) at org.kohsuke.stapler.RequestImpl.bindParameters(RequestImpl.java:383) at hudson.security.HudsonPrivateSecurityRealm$SignupInfo.(HudsonPrivateSecurityRealm.java:566) at
[JIRA] (JENKINS-54258) Build stops Jenkins server and build.xml is missing
Title: Message Title fnu shabana created an issue Jenkins / JENKINS-54258 Build stops Jenkins server and build.xml is missing Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2018-10-25 20:50 Environment: Jenkins 1.597, Java 1.7, Windows Server 2012 R2 Standard, Maven build Priority: Major Reporter: fnu shabana I have Jenkins installed on Production and Non Prod servers and this has been running since Jan 2017 with out any issues. The last successful build was performed on September 03, 2018. I tried to build my projects last week and started to see an issue on all my project builds both in Production and Non-Prod environments. The build version is visible and then it suddenly stops to show the build progress and also shuts down the Jenkins server. The build log shows build is successful and build.xml is missing from the recent builds. Once I start the Jenkins server(as it was stopped) and check the console for build history, the recent build history is not displayed. I do not see any error particular to this problem in the logs. This happens for all my projects on both the Servers and there has been no changes done by us on these servers. Please look into it.
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Ray Kivisto commented on JENKINS-52946 Re: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 Holger Sunke I have been trying to reproduce this error with envinject plugin 2.1.6 and Jenkins LTS 2.138.2, and have been unable to, but I do see reports of this warning from others. Can you please provide the steps to reproduce this bug? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Tommy McNeely commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline WORKAROUND For users using python virtualenv, try using virtualenv --relocatable venv ... BEFORE calling "pip" That changes the shebang line to: #!/usr/bin/env python27 ... or whatever version of python you are using, but significantly shorter. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-39403) Path separators in nested variables are not being escaped correctly when parsing the property file
Title: Message Title Alex Taylor commented on JENKINS-39403 Re: Path separators in nested variables are not being escaped correctly when parsing the property file I tried a fix in https://github.com/jenkinsci/envinject-plugin/pull/133 so please try it out to see if you see any obvious errors Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54257) Infinite loop when an exception occurs on slave
Title: Message Title Arnaud TAMAILLON updated JENKINS-54257 Jenkins / JENKINS-54257 Infinite loop when an exception occurs on slave Change By: Arnaud TAMAILLON 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-54257) Infinite loop when an exception occurs on slave
Title: Message Title Arnaud TAMAILLON started work on JENKINS-54257 Change By: Arnaud TAMAILLON 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-54257) Infinite loop when an exception occurs on slave
Title: Message Title Arnaud TAMAILLON created an issue Jenkins / JENKINS-54257 Infinite loop when an exception occurs on slave Issue Type: Bug Assignee: Arnaud TAMAILLON Components: xunit-plugin Created: 2018-10-25 18:51 Priority: Minor Reporter: Arnaud TAMAILLON Occurs when an exception is raised on a slave, which has a cause which is not a TransformerException Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54222) p4-plugin keeps opening connection during the build. Causing long delays
Title: Message Title Erez Arbell commented on JENKINS-54222 Re: p4-plugin keeps opening connection during the build. Causing long delays Thank you Paul. What about the original issue. Did you try to reproduce it using the steps I provided? Do you see the issue and the large time difference in the remaining of the build run, after the p4 stage has finished? If it is not a bug, can you suggest how to overcome the issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54256) Pipeline stages can be nested indefinitely
Title: Message Title Ray Kivisto created an issue Jenkins / JENKINS-54256 Pipeline stages can be nested indefinitely Issue Type: Bug Assignee: Andrew Bayer Attachments: Jenkinsfile, log Components: pipeline-model-definition-plugin Created: 2018-10-25 18:25 Environment: Jenkins LTS 2.138.2 Recommended plugins, specifically: https://plugins.jenkins.io/workflow-aggregator 2.6 https://plugins.jenkins.io/pipeline-model-definition 1.3.2 Running on Mac OS Mojave java version "1.8.0_151" Java(TM) SE Runtime Environment (build 1.8.0_151-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode) Priority: Trivial Reporter: Ray Kivisto This is an uncommon situation, and not blocking anything, but it seems that there is no limit on the number of times you can nest stages in a Pipeline, even though as per the following, the limit should be two levels of stage nesting when in a sequential stage: https://jenkins.io/doc/book/pipeline/syntax/#sequential-stages "The stages within stages in a stage cannot contain further parallel or stages themselves, but they do allow use of all other functionality of a stage, including agent, tools, `when, etc." Attached is a testcase: Jenkinsfile When this is run, it passes without any warnings or errors, even though this should be technically unsupported. Here is the log: log I'm unsure if we should warn users in this situation, or update the sequential stage documentation at https://jenkins.io/doc/book/pipeline/syntax/#sequential-stages
[JIRA] (JENKINS-54255) xUnit sets build status incorrectly
Title: Message Title John Schmitz created an issue Jenkins / JENKINS-54255 xUnit sets build status incorrectly Issue Type: Bug Assignee: Nikolas Falco Components: xunit-plugin Created: 2018-10-25 18:13 Environment: Jenkins 2.89.3, xUnit 1.102 Priority: Major Reporter: John Schmitz We are counting on the xUnit "Publish xUnit test report" post-build step to properly set the build status. The Failed Tests section has 4 inputs that let you set thresholds to set the build to either UNSTABLE or FAILED based on whether the Total number of Failed tests, or total number of New failures, exceeds the specified thresholds. There is something broken in the test of the number of failures against the specified threshold. A recent build has the number of actual failures < the specified threshold for Total, and the number of New failures (1) < the specified threshold for New (5). It set the build to failed anyway. It appears that whenever the number of New failed tests is positive, that is reported as a build failure even when that number is less than the specified threshold. 00:17:17 [xUnit] [INFO] - Starting to record.00:17:17 [xUnit] [INFO] - Processing CppUnit-1.12.1 (default)00:17:18 [xUnit] [INFO] - [CppUnit-1.12.1 (default)] - 1 test report file(s) were found with the pattern '*/testResult.xml' relative to '/home/bnet/jenkins/workspace/Linux-integration-test' for the testing framework 'CppUnit-1.12.1 (default)'.*00:17:18 [xUnit] [INFO] - Check 'Failed Tests' threshold.00:17:18 [xUnit] [INFO] - Check 'Skipped Tests' threshold.00:17:18 [xUnit] [INFO] - Setting the build status to FAILURE*00:17:18* [xUnit] [INFO] - Stopping recording.
[JIRA] (JENKINS-48775) Proxy authentication error 407 even if 'check proxy' works
Title: Message Title Israel Romero Fijo edited a comment on JENKINS-48775 Re: Proxy authentication error 407 even if 'check proxy' works I respond to myself here to help anyone with same issue.The problem wasn't Jenkins. Problem comes from Java JDK8 and above. Since this version, Oracle has disabled basic auth tunnelling for Basic authentication. If you want to use Basic mode again (security will be compromised), execute Jenkins adding this parameter to your JAVA_OPTS variable: "-Djdk.http.auth.tunneling.disabledSchemes="default value is "-Djdk.http.auth.tunneling.disabledSchemes=Basic", so Basic Schema is DISABLED by default and will return HTTP 407 error even if your credentials were OK. Check proxy Proxy checking must use other method to validate Internet connection... I hope this can help you, guys. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Aleksey Smyrnov commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Looks like working branch rebasing causes this issue Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title
Kamil Demecki commented on JENKINS-28335
Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Ruslan Zenin Above there are examples working for me with ssh key. I didn't check how to use credentials with password if you are asking about this case specific.
sshagent(['credentiald-id-using-ssh-key'])
{
sh('git command or program calling git inside')
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-47551) aws-sqs-plugin: process read message attributes and pass all of them as job parameters
Title: Message Title Ann Beeskau commented on JENKINS-47551 Re: aws-sqs-plugin: process read message attributes and pass all of them as job parameters We have a fix for this issue in an open PR - https://github.com/jenkinsci/aws-sqs-plugin/pull/22/files#diff-ec22c76f5276229f7a70b9ac98649190 Please consider merging it. cc: Mike Kozell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54210) Jenkins integration with load runner
Title: Message Title mohan jayaram commented on JENKINS-54210 Re: Jenkins integration with load runner I had installed the same java version.now i am getting below error ."Build results to unstable" 11:50:49 11:50:49 Test PASSED*11:50:49* SLA rule Transaction Response Time (Percentile) failed: GoalValue = 0 ActualValue = 0.091*11:50:49* Test result: Failed*11:50:49* 25/10/2018 11:50:49 Test complete: \\Ccew-cdrom1\transfer\MOhan\Jenkins\Scenario1.lrs*11:50:49* ---11:50:49 Cleaning up the environment...11:50:49 11:50:49 Run status: Job unstable (Passed with failed tests), total tests: 1, succeeded: 0, failures: 1, errors: 0*11:50:49* Failed : \\Ccew-cdrom1\transfer\MOhan\Jenkins\Scenario1.lrs*11:50:49* 11:50:49 Build step 'Execute Micro Focus tests from file system' changed build result to UNSTABLE*11:50:50* Recording test results*11:50:50* Report archiving mode is set to: PUBLISH_HTML_REPORT*11:50:50* Zipping report folder: C:\Jenkins\workspace\TC_wx_login\6788ce*11:50:51* Parsing test run dataset for perfomrance report*11:50:51* Finished: UNSTABLE Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54210) Jenkins integration with load runner
Title: Message Title mohan jayaram assigned an issue to Rolando-Mihai Vlad Jenkins / JENKINS-54210 Jenkins integration with load runner Change By: mohan jayaram Assignee: mohan jayaram Rolando-Mihai Vlad Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-16502) Permission to see an executor/slave
Title: Message Title Tiago Lopes commented on JENKINS-16502 Re: Permission to see an executor/slave There are build queue and executors filters in Views, which omit jobs from unselected folders/jobs in the view. But the filters are not recursive, making them recursive would be a start, so that you can create a View with a selected folder and view only the corresponding jobs inside the folder. which I assume is typical organization in 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-16502) Permission to see an executor/slave
Title: Message Title Jesse Glick commented on JENKINS-16502 Re: Permission to see an executor/slave Would also be useful to override SlaveComputer.hasPermission from those plugins which dynamically attach and then detach an agent in the course of a build—for example, dockerNode from docker-plugin, podTemplate from kubernetes—to delegate the permission check to READ on the corresponding Job. Thus, in a multitenant installation with segregated view permissions, these one-off agents would be displayed in the Build Executor Status widget only to users who would actually be able to see the build itself. Otherwise you see a bunch of containers running but cannot view the associated builds, which is pretty useless. CC Daniel Beck Wadeck Follonier Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Jesse Scott commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Aleksey Smyrnov We had a similar issue and we were able to workaround the specific issue by deleting the contents of: /var/lib/jenkins/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache On our Jenkins server. We have not yet identified the underlying cause however. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54210) Jenkins integration with load runner
Title: Message Title mohan jayaram updated an issue Jenkins / JENKINS-54210 Jenkins integration with load runner Change By: mohan jayaram Component/s: hp-application-automation-tools-plugin Component/s: microdocs-integration-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-54210) Jenkins integration with load runner
Title: Message Title Steven Hermans assigned an issue to mohan jayaram Jenkins / JENKINS-54210 Jenkins integration with load runner Change By: Steven Hermans Assignee: Steven Hermans mohan jayaram Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54210) Jenkins integration with load runner
Title: Message Title Steven Hermans commented on JENKINS-54210 Re: Jenkins integration with load runner Hi, I think you've selected the wrong component in this Jira issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title James Howe commented on JENKINS-48463 Re: Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 Just to add, as far as I can tell you only need 1.1 if you've got control characters in names (i.e. of tags and attributes). Surely if people are putting them in their configuration it's in text content, where 1.0 works just fine. Not only does .NET not support xml 1.1 but neither does Firefox, nor any of my editors. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title James Howe edited a comment on JENKINS-48463 Re: Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 Just to add, as far as I can tell you only need 1.1 if you've got control characters in names (i.e. of tags and attributes).Surely if people are putting them in their configuration it's in text content, where 1.0 works just fine with standard escapes .Not only does .NET not support xml 1.1 but neither does Firefox, nor any of my editors. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Tibor Digana edited a comment on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix [~nfalco]Hi Nicolas,Not sure what you mean by??At this point why do not add an attribute to mark the differences between flaky failures and failure also in the XMLWith the XML you have to parse whole file and make logic on top to calculate real failures.??As always because this is XML and the stacktrace is not big like kilobytes.Not sure why you validate XML but anyway. Parsing the XML and displaying the statistics is what has to be done by the plugins. In this case we have to find a way how you detect version of the XSD. We have not had any version in the XSD which would be easier to have it in past. What alternatives are you facing in order to detect which XSD is actual?We can fix this as following.I will deploy the old XSD to the old schema location URL="" and I will deploy a new schema location for the current status 2.22.1 with another name of XSD file and new schema location which would have a version 2.22.1. Do you agree or you see another solution?If the change present in 3.0 version, we would have to wait quite long time and there would be a risk that the rerun feature as well as flaky failures are heavily used. One way or another these Jenkins plugins do not care about Maven plugin versions because they only read the XML report as the outcome of the Maven plugins and Jenkins plugins do not use to check the version of surefire in POM. Not that easy for them. The fact that nobody claimed that the stacktrace contained *std-out* in one string of XML Value means that these features are not much used or the users do not print logs in tested logic on the console, but the frequency of use of these features is more probable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Tibor Digana edited a comment on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix [~nfalco]Hi Nicolas,Not sure what you mean by??At this point why do not add an attribute to mark the differences between flaky failures and failure also in the XMLWith the XML you have to parse whole file and make logic on top to calculate real failures.??As always because this is XML and the stacktrace is not big like kilobytes.Not sure why you validate XML but anyway. Parsing the XML and displaying the statistics is what has to be done by the plugins. In this case we have to find a way how you detect version of the XSD. We have not had any version in the XSD which would be easier to have it in past. What alternatives are you facing in order to detect which XSD is actual?We can fix this as following.I will deploy the old XSD to the old schema location URL=""> _ [ https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd _ |https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd] and I will deploy a new schema location for the current status 2.22.1 with another name of XSD file and new schema location which would have a version 2.22.1. Do you agree or you see another solution?If the change present in 3.0 version, we would have to wait quite long time and there would be a risk that the rerun feature as well as flaky failures are heavily used. One way or another these Jenkins plugins do not care about Maven plugin versions because they only read the XML report as the outcome of the Maven plugins and Jenkins plugins do not use to check the version of surefire in POM. Not that easy for them. The fact that nobody claimed that the stacktrace contained *std-out* in one string of XML Value means that these features are not much used or the users do not print logs in tested logic on the console, but the frequency of use of these features is more probable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) --
[JIRA] (JENKINS-54254) Can't use credentials provided by "Folder Credentials" provider
Title: Message Title Georgijs Radovs updated an issue Jenkins / JENKINS-54254 Can't use credentials provided by "Folder Credentials" provider Change By: Georgijs Radovs Hello, Jenkins team.The issue: * It seems,"Base URL" parameter in "Download Content Packages from CRX" build step can't access credentials provided by "Folder Credentials" provider, when downloading packages.How to reproduce: # Create a freestyle Jenkins project, add "Download Content Packages from CRX" build-step # Input "Base URL", "Package ID" variables # Create a set of "Jenkins Credentials" provided credentials to be used by "CRX Content Deployer" plugin # Re-create the same set of credentials in project's "Folder Credentials" provider # Go to the Jenkins project configuration, select credentials set: ** Select global credentials, press "Test Connection" - should be "Success" access to Base URL ** Select credentials from "Folder Credentials" provider - should be "Access Denied" to Base URL Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Tibor Digana edited a comment on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix [~nfalco]Hi Nicolas,Not sure what you mean by??At this point why do not add an attribute to mark the differences between flaky failures and failure also in the XML (not only in console) With the XML you have to parse whole file and make logic on top to calculate real failures.??As always because this is XML and the stacktrace is not big like kilobytes.Not sure why you validate XML but anyway. Parsing the XML and displaying the statistics is what has to be done by the plugins. In this case we have to find a way how you detect version of the XSD. We have not had any version in the XSD which would be easier to have it in past. What alternatives are you facing in order to detect which XSD is actual?We can fix this as following.I will deploy the old XSD to the old schema location URL=""> _https _ https ://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report. xsd_ xsd _ and I will deploy a new schema location for the current status 2.22.1 with another name of XSD file and new schema location which would have a version 2.22.1. Do you agree or you see another solution?If the change present in 3.0 version, we would have to wait quite long time and there would be a risk that the rerun feature as well as flaky failures are heavily used. One way or another these Jenkins plugins do not care about Maven plugin versions because they only read the XML report as the outcome of the Maven plugins and Jenkins plugins do not use to check the version of surefire in POM. Not that easy for them. The fact that nobody claimed that the stacktrace contained *std-out* in one string of XML Value means that these features are not much used or the users do not print logs in tested logic on the console, but the frequency of use of these features is more probable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed
[JIRA] (JENKINS-54254) Can't use credentials provided by "Folder Credentials" provider
Title: Message Title Georgijs Radovs updated an issue Jenkins / JENKINS-54254 Can't use credentials provided by "Folder Credentials" provider Change By: Georgijs Radovs Summary: Can't use credentials from provided by "Folder Credentials" provider Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54254) Can't use credentials from "Folder Credentials" provider
Title: Message Title Georgijs Radovs created an issue Jenkins / JENKINS-54254 Can't use credentials from "Folder Credentials" provider Issue Type: Bug Assignee: Unassigned Components: crx-content-package-deployer-plugin Created: 2018-10-25 15:52 Environment: Jenkins application version - 2.138.1 CRX Content Deployer plugin version - 1.8.1 Java version - 1.8.0_131 Labels: crx Priority: Major Reporter: Georgijs Radovs Hello, Jenkins team. The issue: It seems,"Base URL" parameter in "Download Content Packages from CRX" build step can't access credentials provided by "Folder Credentials" provider, when downloading packages. How to reproduce: Create a freestyle Jenkins project, add "Download Content Packages from CRX" build-step Input "Base URL", "Package ID" variables Create a set of "Jenkins Credentials" provided credentials to be used by "CRX Content Deployer" plugin Re-create the same set of credentials in project's "Folder Credentials" provider Go to the Jenkins project configuration, select credentials set:
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Tibor Digana commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix Nikolas Falco Hi Nicolas, Not sure what you mean by ??At this point why do not add an attribute to mark the differences between flaky failures and failure also in the XML (not only in console) ?? With the XML you have to parse whole file and make logic on top to calculate real failures. As always because this is XML and the stacktrace is not big like kilobytes. Not sure why you validate XML but anyway. Parsing the XML and displaying the statistics is what has to be done by the plugins. In this case we have to find a way how you detect version of the XSD. We have not had any version in the XSD which would be easier to have it in past. What alternatives are you facing in order to detect which XSD is actual? We can fix this as following. I will deploy the old XSD to the old schema location URL="" href="https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd_" class="external-link" rel="nofollow" style="color: #3b73af; text-decoration: none">https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd_ and I will deploy a new schema location for the current status 2.22.1 with another name of XSD file and new schema location which would have a version 2.22.1. Do you agree or you see another solution? If the change present in 3.0 version, we would have to wait quite long time and there would be a risk that the rerun feature as well as flaky failures are heavily used. One way or another these Jenkins plugins do not care about Maven plugin versions because they only read the XML report as the outcome of the Maven plugins and Jenkins plugins do not use to check the version of surefire in POM. Not that easy for them. The fact that nobody claimed that the stacktrace contained std-out in one string of XML Value means that these features are not much used or the users do not print logs in tested logic on the console, but the frequency of use of these features is more probable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54253) fix SSC (Fortify) integration
Title: Message Title Yuri Guller started work on JENKINS-54253 Change By: Yuri Guller 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-54253) fix SSC (Fortify) integration
Title: Message Title Yuri Guller created an issue Jenkins / JENKINS-54253 fix SSC (Fortify) integration Issue Type: Bug Assignee: Yuri Guller Components: hp-application-automation-tools-plugin Created: 2018-10-25 15:46 Priority: Critical Reporter: Yuri Guller after the refactoring of the OctaneSDK to multi-shared space work flavor, SSC integration failed to retrieve/get some of the required configuration Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53674) fix SRF/SRL/PC test types detection
Title: Message Title Yuri Guller closed an issue as Fixed Jenkins / JENKINS-53674 fix SRF/SRL/PC test types detection Change By: Yuri Guller Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53674) fix SRF/SRL/PC test types detection
Title: Message Title Yuri Guller resolved as Fixed Jenkins / JENKINS-53674 fix SRF/SRL/PC test types detection Change By: Yuri Guller Status: In Progress 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-52487) p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
Title: Message Title
Daniel Hsueh commented on JENKINS-52487
Re: p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
my tests on the workspace name suggest env is available 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-52487) p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
Title: Message Title
Paul Allen assigned an issue to Kevin Williamson
Jenkins / JENKINS-52487
p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
Change By:
Paul Allen
Assignee:
Kevin Williamson
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-52487) p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
Title: Message Title
Paul Allen commented on JENKINS-52487
Re: p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
Unfortunately I have no control over env as it is set by Jenkins. Scope is important as certain variable are not defined until the Job starts to run. For example inside a Library or Jenkinsfile many variables are not yet defined e.g. which slave (NODE_NAME) is going to be used. I'll close the issue and add a note to the docs regarding the use of single/double quotes. Please let me know if you have any other concerns.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-54210) Jenkins integration with load runner
Title: Message Title mohan jayaram commented on JENKINS-54210 Re: Jenkins integration with load runner Hi , I have Java 10.0.1 on both the machines. should i need to install java 8 on both?Thanks for your help! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16502) Permission to see an executor/slave
Title: Message Title Daniel Ng commented on JENKINS-16502 Re: Permission to see an executor/slave I believe this would be useful as well. Especially in my case where I am deploying Selenium Grid Nodes through Jenkins Agents. If I wanted to dedicate a particular node to only automated testing and not have it bogged down by other build tasks, it would be ideal to hide them from view and make them "unavailable" to people. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54078) [JEP-210] Exception: Object was recently deallocated when using Git + timeout(activity: true)
Title: Message Title Patrick Ruckstuhl commented on JENKINS-54078 Re: [JEP-210] Exception: Object was recently deallocated when using Git + timeout(activity: true) Thanks for this, unfortunately I'm right now not in a position to try this experimental build out. Now with the down/upgrades (workflow-job 2.25 and workflow-durable-task-step 2.25) that you did it looks like things are running stable again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54252) unstash very slow blocked on SecureRandom
Title: Message Title
Patrick Ruckstuhl updated an issue
Jenkins / JENKINS-54252
unstash very slow blocked on SecureRandom
Change By:
Patrick Ruckstuhl
unstash in pipeline jobs takes quite a long time and I see a decent number of BLOCKED threads with the following stack{code}RemoteInputStream greedy pump thread: hudson.remoting.RemoteInputStream$Greedyat hudson.remoting.RemoteInputStream.(RemoteInputStream.java:106)at hudson.remoting.RemoteInputStream.(RemoteInputStream.java:89)at hudson.FilePath.untar(FilePath.java:569)at org.jenkinsci.plugins.workflow.flow.StashManager.unstash(StashManager.java:165)at org.jenkinsci.plugins.workflow.support.steps.stash.UnstashStep$Execution.run(UnstashStep.java:76)at org.jenkinsci.plugins.workflow.support.steps.stash.UnstashStep$Execution.run(UnstashStep.java:63)at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)at hudson.security.ACL.impersonate(ACL.java:290)at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.java:745)java.security.SecureRandom.nextBytes(SecureRandom.java:468)sun.security.ssl.CipherBox.createExplicitNonce(CipherBox.java:1015)sun.security.ssl.EngineOutputRecord.write(EngineOutputRecord.java:287)sun.security.ssl.EngineOutputRecord.write(EngineOutputRecord.java:225)sun.security.ssl.EngineWriter.writeRecord(EngineWriter.java:186)sun.security.ssl.SSLEngineImpl.writeRecord(SSLEngineImpl.java:1300)sun.security.ssl.SSLEngineImpl.writeAppRecord(SSLEngineImpl.java:1271)sun.security.ssl.SSLEngineImpl.wrap(SSLEngineImpl.java:1186)javax.net.ssl.SSLEngine.wrap(SSLEngine.java:469)org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:491)org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248)org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200)org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doSend(ProtocolStack.java:692)org.jenkinsci.remoting.protocol.ApplicationLayer.write(ApplicationLayer.java:157)org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.write(ChannelApplicationLayer.java:299)hudson.remoting.AbstractByteBufferCommandTransport.write(AbstractByteBufferCommandTransport.java:304)hudson.remoting.Channel.send(Channel.java:721)hudson.remoting.ProxyOutputStream.write(ProxyOutputStream.java:144)hudson.remoting.RemoteInputStream$1.run(RemoteInputStream.java:148){code}Interestingly there is enough entropy available (as we have haveged installed){code}cat /proc/sys/kernel/random/entropy_avail3878{code}The key
[JIRA] (JENKINS-54078) [JEP-210] Exception: Object was recently deallocated when using Git + timeout(activity: true)
Title: Message Title Jesse Glick commented on JENKINS-54078 Re: [JEP-210] Exception: Object was recently deallocated when using Git + timeout(activity: true) Patrick Ruckstuhl if you are still in a position to try experimental builds, I think this update should correct your issue. activity: true as originally implemented (and in my fix from 2018-10-16) sent a distinct Remoting packet for every line of output, which made for substantial overhead in busy builds. I have now rewritten this to only send a “reset the timer please” message from the agent to the master at intervals of half of the idle timeout. There are still some fixes I plan to make in this PR, but that build ought to address the performance problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-21336) ADMINISTER should not imply RUN_SCRIPTS
Title: Message Title Matt Sicker assigned an issue to Matt Sicker Jenkins / JENKINS-21336 ADMINISTER should not imply RUN_SCRIPTS Change By: Matt Sicker Assignee: Mikael Gaunin Matt Sicker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54252) unstash very slow blocked on SecureRandom
Title: Message Title Patrick Ruckstuhl created an issue Jenkins / JENKINS-54252 unstash very slow blocked on SecureRandom Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2018-10-25 14:49 Priority: Minor Reporter: Patrick Ruckstuhl unstash in pipeline jobs takes quite a long time and I see a decent number of BLOCKED threads with the following stack RemoteInputStream greedy pump thread: hudson.remoting.RemoteInputStream$Greedy at hudson.remoting.RemoteInputStream.(RemoteInputStream.java:106) at hudson.remoting.RemoteInputStream.(RemoteInputStream.java:89) at hudson.FilePath.untar(FilePath.java:569) at org.jenkinsci.plugins.workflow.flow.StashManager.unstash(StashManager.java:165) at org.jenkinsci.plugins.workflow.support.steps.stash.UnstashStep$Execution.run(UnstashStep.java:76) at org.jenkinsci.plugins.workflow.support.steps.stash.UnstashStep$Execution.run(UnstashStep.java:63) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) java.security.SecureRandom.nextBytes(SecureRandom.java:468) sun.security.ssl.CipherBox.createExplicitNonce(CipherBox.java:1015) sun.security.ssl.EngineOutputRecord.write(EngineOutputRecord.java:287)
[JIRA] (JENKINS-52487) p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
Title: Message Title
Daniel Hsueh commented on JENKINS-52487
Re: p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
my observations are (note gstring/string differences): workspace manualSpec name both "${env.JOB_NAME}" and '${JOB_NAME}' work *** but see below workspace manualSpec spec clientSpec view "${env.JOB_NAME}" results in java.lang.NullPointerException: Cannot get property 'JOB_NAME' on null object (likely env) '${JOB_NAME}' works with both *** above So my original problem (on me) was with the view mapping (which needs to be vanilla string). Not sure if you want to address the gstring view null env issue. Thank you for assisting me.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54251) RunResults throws NullPointerException
Title: Message Title Tamas Florin assigned an issue to Tamas Florin Jenkins / JENKINS-54251 RunResults throws NullPointerException Change By: Tamas Florin Assignee: Daniel Gront Tamas Florin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54251) RunResults throws NullPointerException
Title: Message Title Tamas Florin created an issue Jenkins / JENKINS-54251 RunResults throws NullPointerException Issue Type: Bug Assignee: Daniel Gront Components: hp-application-automation-tools-plugin Created: 2018-10-25 14:37 Priority: Major Reporter: Tamas Florin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title
Benjamin Coover commented on JENKINS-54131
Re: "Failed to parse changelog" in JIRA plugin 3.0.3
Seeing this as well, but in a different context. It only appears to be happening from automatically triggered builds, I have yet to see a build fail for this reason that I started manually. I did some digging using the stack trace and found the same thing that Matthew Kelly mentions in JENKINS-54144. The offending section appears to be here, in jira-plugin-jira-3.0.3/src/main/java/hudson/plugins/jira/JiraSite.java:457
if (executorService==null){
executorService = Executors.newFixedThreadPool(
threadExecutorNumber, //
new ThreadFactory()
{
final AtomicInteger threadNumber = new AtomicInteger( 0 );
@Override
public Thread newThread( Runnable r )
{
return new Thread( r, "jira-plugin-http-request-" + threadNumber.getAndIncrement() + "-thread" );
}
} );
}
According to the docs, IllegalArgumentException is thrown if "nThreads" ("threadExecutorNumber" here) is 0, so something appears to be setting this value to 0 on triggered builds, but not manual builds.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52605) Helix branches do not recurse when defining multibranch pipeline
Title: Message Title Kevin Williamson commented on JENKINS-52605 Re: Helix branches do not recurse when defining multibranch pipeline Bubble help is fixed in the latest release (1.9.2). Online doc is 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-52487) p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
Title: Message Title
Daniel Hsueh commented on JENKINS-52487
Re: p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
thanks for looking into this, and acknowledge the gstring/string difference may be the cause I'll confirm shortly (I have a nagging doubt/thought involving $BUILD_NUMBER but I cannot recall exactly what... I'll do some experimentation)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-52605) Helix branches do not recurse when defining multibranch pipeline
Title: Message Title Kevin Williamson assigned an issue to Kevin Williamson Jenkins / JENKINS-52605 Helix branches do not recurse when defining multibranch pipeline Change By: Kevin Williamson Assignee: Paul Allen Kevin Williamson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-48775) Proxy authentication error 407 even if 'check proxy' works
Title: Message Title Israel Romero Fijo edited a comment on JENKINS-48775 Re: Proxy authentication error 407 even if 'check proxy' works I respond to myself here to help anyone with same issue.The problem wasn't Jenkins. Problem comes from Java JDK8 and above. Since this version, Oracle has disabled basic auth tunnelling for Basic authentication. If you want to use Basic mode again (security will be compromised), execute Jenkins adding this parameter to your JAVA_OPTS variable: "-Djdk.http.auth.tunneling.disabledSchemes="default value is "-Djdk.http.auth.tunneling.disabledSchemes=Basic", so Basic Schema is DISABLED by default and will return HTTP 407 error even if your credentials were OK. Check proxy must use other method to validate Internet connection...I hope this can help you, guys. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-47553) Pipeline 'poll' option in checkout ignored if using libraries for sync
Title: Message Title Paul Allen commented on JENKINS-47553 Re: Pipeline 'poll' option in checkout ignored if using libraries for sync Hi Karl Wirth, please can you check this using different workspace names. Thanks, Paul Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-47553) Pipeline 'poll' option in checkout ignored if using libraries for sync
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-47553 Pipeline 'poll' option in checkout ignored if using libraries for sync Change By: Paul Allen Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53669) Expected 8 bytes application/vnd.docker.raw-stream header
Title: Message Title Jakub Bochenski commented on JENKINS-53669 Re: Expected 8 bytes application/vnd.docker.raw-stream header This happens to me too (Docker Plugin 1.1.5) , the difference being slaves just die within seconds of being created. Also reported as https://github.com/jenkinsci/docker-plugin/issues/628 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54078) [JEP-210] Exception: Object was recently deallocated when using Git + timeout(activity: true)
Title: Message Title Jesse Glick commented on JENKINS-54078 Re: [JEP-210] Exception: Object was recently deallocated when using Git + timeout(activity: true) Patrick Ruckstuhl I have a fix for your issue already, it is going through CI 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-46291) p4 plugin is polling stream containing shared library instead of stream specified in checkout step
Title: Message Title Paul Allen closed an issue as Fixed Closing old issues. The p4-plugin has Global Library support, please reopen if you are experiencing issues. Jenkins / JENKINS-46291 p4 plugin is polling stream containing shared library instead of stream specified in checkout step Change By: Paul Allen Status: Open Closed 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-52487) p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
Title: Message Title
Paul Allen commented on JENKINS-52487
Re: p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
Have you tried using single quotes for the workspace view as double quotes are expanded by Groovy and not the plugin. e.g.
p4view = '''\
//depot/foo/bar/... //jenkins-${JOB_NAME}/...
'''
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-52487) p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
Title: Message Title
Paul Allen updated an issue
Jenkins / JENKINS-52487
p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
Change By:
Paul Allen
Labels:
P4_VERIFY P4_SUPPORT environment-variables 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-54078) [JEP-210] Exception: Object was recently deallocated when using Git + timeout(activity: true)
Title: Message Title Patrick Ruckstuhl commented on JENKINS-54078 Re: [JEP-210] Exception: Object was recently deallocated when using Git + timeout(activity: true) Figured out that I had to downgrade workflow-job from 2.26 to 2.25 as well, now I think the issue doesn't happen anymore. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-52524) p4-plugin + global pipeline shared library - problems specifying latest default version
Title: Message Title Paul Allen closed an issue as Fixed Setting a revision of now should allow you to use the latest revision of the library. Jenkins / JENKINS-52524 p4-plugin + global pipeline shared library - problems specifying latest default version Change By: Paul Allen Status: Open Closed 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-54078) [JEP-210] Exception: Object was recently deallocated when using Git + timeout(activity: true)
Title: Message Title Patrick Ruckstuhl commented on JENKINS-54078 Re: [JEP-210] Exception: Object was recently deallocated when using Git + timeout(activity: true) After the troubles with huge number of "Computer.threadPoolForRemoting" threads I'm having as described on JENKINS-54073 I now rolled back to the latest released (2.11) in the hope of having this together with workflow-durable-task-step 2.25 it would go away but that's unfortunately not the case Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48775) Proxy authentication error 407 even if 'check proxy' works
Title: Message Title Israel Romero Fijo commented on JENKINS-48775 Re: Proxy authentication error 407 even if 'check proxy' works I respond to myself here to help anyone with same issue. The problem wasn't Jenkins. Problem comes from Java JDK8 and above. Since this version, Oracle has disabled basic auth tunnelling for Basic authentication. If you want to use Basic mode again (security will be compromised), execute Jenkins adding this parameter to your JAVA_OPTS variable: "-Djdk.http.auth.tunneling.disabledSchemes=" default value is "-Djdk.http.auth.tunneling.disabledSchemes=Basic", so Basic Schema is DISABLED by default and will return HTTP 407 error even if your credentials were OK. I hope this can help you, guys. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-37575) Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely
Title: Message Title Sam Van Oort commented on JENKINS-37575 Re: Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely Kurt Routley Yes, 1.23, sorry, typo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54247) Add to TROUBLESHOOTING how to backup/restore current keys
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54247 Re: Add to TROUBLESHOOTING how to backup/restore current keys If you configured the encryption settings, you only have to copy the key store and the config files (you should maintain the secrets also). The default key store is "JENKINS_HOME/saml-jenkins-keystore.jks" the configuration is in "JENKINS_HOME/saml-jenkins-keystore.xml" some data is encrypted, so it is not for manual manage, and it only is valid for a Jenkins with the same JANKINS_HOME/secrets. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Nick Jones commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Sam Van Oort, is the fix for this to apply a @DataBoundConstructor annotation on the constructor of GitSCMSourceDefaults? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Patrick Ruckstuhl commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Ok, could very well be as I had to install your patch as otherwise nothing was working. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53888) Batch step running on a node other than the master fails
Title: Message Title Jesse Glick commented on JENKINS-53888 Re: Batch step running on a node other than the master fails Anyone who is encountering the asynchronous notification was lost error: assuming you do not know how to reproduce the issue from scratch, please create a custom logger tracking org.jenkinsci.plugins.workflow.steps.durable_task and org.jenkinsci.plugins.durabletask at FINE and report details. Installing the support-core plugin is ideal as it allows these logs and other things to be recorded as a single ZIP file. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jesse Glick commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Patrick Ruckstuhl you seem to have a distinct issue from everyone else. I suspect there is something amiss in my fix of JENKINS-54078 specific to using activity: true. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-32681) Option to disable script security approval
Title: Message Title Jesse Glick commented on JENKINS-32681 Re: Option to disable script security approval Why does Groovy Postbuild need Overall/Administer permission if Script Security is used to approve or whitelist scripts and methods? Perhaps predates script security integration, and you are the first to try using it with authorize-project. Best to file a separate bug report in groovy-postbuild for it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48775) Proxy authentication error 407 even if 'check proxy' works
Title: Message Title Fukusuke Takahashi commented on JENKINS-48775 Re: Proxy authentication error 407 even if 'check proxy' works Same issue with 2.138.2 version Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-38906) Remove lock resource name from global configuration when lock is released
Title: Message Title Sam Van Oort commented on JENKINS-38906 Re: Remove lock resource name from global configuration when lock is released Vivek Pandey This one might be worth our team taking up, since locks are used rather heavily. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54250) Disable restarting stages in jenkinsfile optionally
Title: Message Title Jan Hoppe updated an issue Jenkins / JENKINS-54250 Disable restarting stages in jenkinsfile optionally Change By: Jan Hoppe Summary: Disable restarting stages in jenkinsfile optionally Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.
