[JIRA] (JENKINS-59854) gitlab group project can't open in blue ocean
Title: Message Title dd xq created an issue Jenkins / JENKINS-59854 gitlab group project can't open in blue ocean Issue Type: Bug Assignee: Parichay Barpanda Attachments: image-2019-10-19-10-09-10-424.png, image-2019-10-19-10-10-05-143.png, image-2019-10-19-10-10-29-355.png, image-2019-10-19-10-12-54-635.png, image-2019-10-19-10-13-25-252.png, image-2019-10-19-10-13-41-478.png, image-2019-10-19-10-14-04-241.png Components: blueocean-plugin, gitlab-branch-source-plugin Created: 2019-10-19 02:14 Environment: centos7 docker Priority: Minor Reporter: dd xq recurrence steps: 1.create a new gitlab group item 2. open one of the projects 3. open in ocean blue Add Comment
[JIRA] (JENKINS-59844) Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command
Title: Message Title Dishit Devasia commented on JENKINS-59844 Re: Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command Hi - I will like to work on this. However, I am unable to reporduce the issue. Can you please provide the steps to reproduce? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202579.1571403818000.10840.1571447100136%40Atlassian.JIRA.
[JIRA] (JENKINS-59829) GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository
Title: Message Title Kyle Jackson updated JENKINS-59829 Jenkins / JENKINS-59829 GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository Change By: Kyle Jackson Status: Open Fixed but Unreleased Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202564.1571336378000.10838.1571443500495%40Atlassian.JIRA.
[JIRA] (JENKINS-59829) GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository
Title: Message Title Kyle Jackson commented on JENKINS-59829 Re: GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository From: Google I've discovered that a recent Jenkins update to their LTS version deprecated an API that breaks the google-source-plugin [1]. The API that they deprecated breaks the plugin here [2] which can't call getInstance() anymore. A workaround for the moment is to switch to GIT or some other compatible SCM for the time being until a fix can be rolled out that is compatible with the LTS release of Jenkins. Another workaround would be to rollback Jenkins to jenkins:2.182, the last known release where the API was functioning as expected. Let me know if there is anything else I can help you with. [1] https://github.com/jenkinsci/google-source-plugin/pull/9 [github.com] [2] https://github.com/jenkinsci/google-source-plugin/pull/9/files#diff-ae66052e7782a54371071f2fbacbd1faR146 [github.com] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202564.1571336378000.10836.1571443440163%40Atlassian.JIRA.
[JIRA] (JENKINS-59851) Stash Pull Request Builder plugin keep on posting the Build Started comment without build result
Title: Message Title Nareen M updated an issue Jenkins / JENKINS-59851 Stash Pull Request Builder plugin keep on posting the Build Started comment without build result Change By: Nareen M Stash Pull Request Builder plugin keeps on posting the Build Started comment, but I don't see any builds running on the Jenkins. I think it's happening when there are multiple PRs open and seems like it's including multiple PRs into one build, instead of running one job build per PR. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202587.1571422014000.10834.1571433900157%40Atlassian.JIRA.
[JIRA] (JENKINS-43038) Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins
Title: Message Title Andrey Babushkin commented on JENKINS-43038 Re: Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins We're experiencing the same issue when our java agent get killed my OOM or machine on which agent is running is rebooted. Is there any way to reduce amount of time Jenkins will wait till the build will be mark as failed? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180142.1490197006000.10792.1571432400995%40Atlassian.JIRA.
[JIRA] (JENKINS-43775) java.util.ConcurrentModificationException when calling junit() step in parallel pipeline branch
Title: Message Title Daniel Geißler commented on JENKINS-43775 Re: java.util.ConcurrentModificationException when calling junit() step in parallel pipeline branch Same here today in a parallel block test execution (declarative pipeline): Jenkins: 2.176.3 JUnit Plugin : 1.27 java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909) at java.util.ArrayList$Itr.next(ArrayList.java:859) at hudson.tasks.junit.TestResult.getResultByNodes(TestResult.java:656) at hudson.tasks.junit.TestResult.getResultByNode(TestResult.java:647) at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:57) at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:23) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Strange thing is that we've never had this in structural pipelines so far, although they run in parallel too. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Cenk Tosun commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) Hi suryatej yaramada you could exclude the shared library and check if this is really the reason for the rebuilds. I would also advise you to add the remote name to the branch specifier instead of using only the branch name. If the cause is really the shared library, you could test the following: adjust the Global Pipeline Library definition and choose legancy scm instead of mordern scm. There you have the option where you can add the additional behavior, 'Polling ignore commits of certain path'. When selected enter "ignoreRepo" under Included Region and save. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192737.1533040103000.10767.1571431920274%40Atlassian.JIRA.
[JIRA] (JENKINS-59853) When using gradle to name an android app the App Center plugin is unable to locate the file
Title: Message Title Navin Joseph updated an issue Jenkins / JENKINS-59853 When using gradle to name an android app the App Center plugin is unable to locate the file Change By: Navin Joseph Summary: When using the gradle to name an android app the App Center plugin is unable to locate the file Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202589.1571431054000.10762.1571431320222%40Atlassian.JIRA.
[JIRA] (JENKINS-59853) When using gradle to name an android app the App Center plugin is unable to locate the file
Title: Message Title Navin Joseph updated an issue Jenkins / JENKINS-59853 When using gradle to name an android app the App Center plugin is unable to locate the file Change By: Navin Joseph Environment: Jenkins ver. 2.200 App Center plugin ver 0.6.2 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202589.1571431054000.10764.1571431320250%40Atlassian.JIRA.
[JIRA] (JENKINS-59853) When using the gradle to name an android app the App Center plugin is unable to locate the file
Title: Message Title Navin Joseph updated an issue Jenkins / JENKINS-59853 When using the gradle to name an android app the App Center plugin is unable to locate the file Change By: Navin Joseph We use the gradle to name the release versions of our apk via Jenkins and subsequently upload for distribution.The [Android signing plugin|[https://github.com/jenkinsci/android-signing-plugin]] is able finding files despite having special characters " \ *" in the file name .eg: app_name_v*_release.apkUnfortunately the App center plugin is not able to identify the file. Any recommendations ? [SignApksBuilder] signed APK app/build/outputs/apk/app_name_Release/app_v0.20.0_20191018_1512_app_name_Release-signed.apk[SignApksBuilder] signed APK app/build/outputs/apk/app_name_Release/app_v0.20.0_20191018_1512_app_name_Release-signed.apk[SignApksBuilder] archiving signed APK app/build/outputs/apk/app_name_Release/app_v0.20.0_20191018_1512_app_name_Release-signed.apk[SignApksBuilder] finished signing APKsio.jenkins.plugins.appcenter.AppCenterException: File not found: app/build/outputs/apk/app_name_Release/app_v*_app_name_Release.apk at io.jenkins.plugins.appcenter.task.internal.CheckFileExistsTask.execute(CheckFileExistsTask.java:44) at io.jenkins.plugins.appcenter.task.UploadTask.call(UploadTask.java:42) at io.jenkins.plugins.appcenter.task.UploadTask.call(UploadTask.java:17) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)io.jenkins.plugins.appcenter.AppCenterException: Upload to AppCenter failed. at io.jenkins.plugins.appcenter.task.UploadTask.call(UploadTask.java:56) at io.jenkins.plugins.appcenter.task.UploadTask.call(UploadTask.java:17) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to Robot at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1159) at
[JIRA] (JENKINS-59851) Stash Pull Request Builder plugin keep on posting the Build Started comment without build result
Title: Message Title Nareen M updated an issue Jenkins / JENKINS-59851 Stash Pull Request Builder plugin keep on posting the Build Started comment without build result Change By: Nareen M Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202587.1571422014000.10758.1571431140181%40Atlassian.JIRA.
[JIRA] (JENKINS-59853) When using the gradle to name an android app the App Center plugin is unable to locate the file
Title: Message Title Navin Joseph created an issue Jenkins / JENKINS-59853 When using the gradle to name an android app the App Center plugin is unable to locate the file Issue Type: Improvement Assignee: Mez Pahlan Components: appcenter-plugin Created: 2019-10-18 20:37 Environment: Jenkins ver. 2.200 Priority: Minor Reporter: Navin Joseph We use the gradle to name the release versions of our apk via Jenkins and subsequently upload for distribution. The [Android signing plugin|https://github.com/jenkinsci/android-signing-plugin] is able finding files despite having "" in the file name .eg: app_name_v_release.apk Unfortunately the App center plugin is not able to identify the file. Any recommendations ? [SignApksBuilder] signed APK app/build/outputs/apk/app_name_Release/app_v0.20.0_20191018_1512_app_name_Release-signed.apk[SignApksBuilder] signed APK app/build/outputs/apk/app_name_Release/app_v0.20.0_20191018_1512_app_name_Release-signed.apk[SignApksBuilder] archiving signed APK app/build/outputs/apk/app_name_Release/app_v0.20.0_20191018_1512_app_name_Release-signed.apk[SignApksBuilder] finished signing APKsio.jenkins.plugins.appcenter.AppCenterException: File not found: app/build/outputs/apk/app_name_Release/app_v*_app_name_Release.apk at io.jenkins.plugins.appcenter.task.internal.CheckFileExistsTask.execute(CheckFileExistsTask.java:44) at io.jenkins.plugins.appcenter.task.UploadTask.call(UploadTask.java:42) at io.jenkins.plugins.appcenter.task.UploadTask.call(UploadTask.java:17) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at
[JIRA] (JENKINS-59851) Stash Pull Request Builder plugin keep on posting the Build Started comment without build result
Title: Message Title Nareen M updated an issue Jenkins / JENKINS-59851 Stash Pull Request Builder plugin keep on posting the Build Started comment without build result Change By: Nareen M Stash Pull Request Builder plugin keeps on posting the Build Started comment, but I don't see any builds running on the Jenkins. I think it's happening when there are multiple PRs open and seems like it's including multiple PRs into one build , instead of running one job per PR . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202587.1571422014000.10754.1571431080497%40Atlassian.JIRA.
[JIRA] (JENKINS-59851) Stash Pull Request Builder plugin keep on posting the Build Started comment without build result
Title: Message Title Nareen M updated an issue Jenkins / JENKINS-59851 Stash Pull Request Builder plugin keep on posting the Build Started comment without build result Change By: Nareen M Stash Pull Request Builder plugin keeps on posting the Build Started comment, but I don't see any builds running on the Jenkins. I think it's happening when there are multiple PRs open and seems like it's including multiple PRs into one build. !Screen Shot 2019-10-18 at 10.47.08 AM.png|width=2158,height=1309! !Screen Shot 2019-10-18 at 1.27.28 PM.png! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202587.1571422014000.10752.1571431020159%40Atlassian.JIRA.
[JIRA] (JENKINS-59851) Stash Pull Request Builder plugin keep on posting the Build Started comment without build result
Title: Message Title Nareen M updated an issue Jenkins / JENKINS-59851 Stash Pull Request Builder plugin keep on posting the Build Started comment without build result Change By: Nareen M Attachment: Screen Shot 2019-10-18 at 1.27.28 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202587.1571422014000.10748.1571430960241%40Atlassian.JIRA.
[JIRA] (JENKINS-59851) Stash Pull Request Builder plugin keep on posting the Build Started comment without build result
Title: Message Title Nareen M updated an issue Jenkins / JENKINS-59851 Stash Pull Request Builder plugin keep on posting the Build Started comment without build result Change By: Nareen M Stash Pull Request Builder plugin keeps on posting the Build Started comment, but I don't see any builds running on the Jenkins. I think it's happening when there are multiple PRs open or when new PR merged and the old seems like it's including multiple PRs still open into one build . !Screen Shot 2019-10-18 at 10.47.08 AM.png|width=2158,height=1309! !Screen Shot 2019-10-18 at 1.27.28 PM.png! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-58381) Trend graph not appearing
Title: Message Title Steve Springett commented on JENKINS-58381 Re: Trend graph not appearing No updates from me. I no longer use this plugin so it doesn't affect me. The project is open source, so if someone has the capacity and wants to submit a fix, I will gladly accept it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200503.1562595115000.10738.1571430480377%40Atlassian.JIRA.
[JIRA] (JENKINS-59852) Strange logging {"enableFile":false,"tagFile":"","emitOnCheckout":false,"enableProperty":false,"tagProperties":""}
Title: Message Title
seafight seafight updated an issue
Jenkins / JENKINS-59852
Strange logging {"enableFile":false,"tagFile":"","emitOnCheckout":false,"enableProperty":false,"tagProperties":""}
Change By:
seafight seafight
Attachment:
CefSharp.BrowserSubprocess.exe
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202588.1571422142000.10732.1571429100308%40Atlassian.JIRA.
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title Daniel Beck updated JENKINS-59849 Jenkins / JENKINS-59849 Spaces don't work in resource root paths Change By: Daniel Beck Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202585.1571419376000.10729.1571427840428%40Atlassian.JIRA.
[JIRA] (JENKINS-59754) Jenkins Micro Focus Application Automation Tools Plugin losing connection with Octane after running pipelines
Title: Message Title Joshua Yates commented on JENKINS-59754 Re: Jenkins Micro Focus Application Automation Tools Plugin losing connection with Octane after running pipelines Hello Radi, What happens is if they go more than a few hours without running a build It will not run a build from Octane. At the time that this is happening if you check Octane it does not show the Jenkins CI server as connected during that period, even though we can ping the jenkins server from Octane at the time that Octane is saying that it cannot get to jenkins. The log files that we sent had a period in there where it could not connect but that is the weird thing, the plugin seems to think that it is creating a new session but we do not think that this is actually happening. And as soon as Jenkins is restarted the issue goes away Thanks Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202477.1570821116000.10726.1571426760185%40Atlassian.JIRA.
[JIRA] (JENKINS-42720) ConcurrentModificationException when serializing LockableResourcesManager
Title: Message Title Stefan Thurnherr closed an issue as Fixed Jenkins / JENKINS-42720 ConcurrentModificationException when serializing LockableResourcesManager Change By: Stefan Thurnherr Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179679.1489419394000.10721.1571425860645%40Atlassian.JIRA.
[JIRA] (JENKINS-42720) ConcurrentModificationException when serializing LockableResourcesManager
Title: Message Title Stefan Thurnherr commented on JENKINS-42720 Re: ConcurrentModificationException when serializing LockableResourcesManager Yes thanks, I confirm that this is solved, I haven't seen this issue in the last months. So closing this issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179679.1489419394000.10719.1571425860597%40Atlassian.JIRA.
[JIRA] (JENKINS-10163) Update Hadoop plugin to latest stable version
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-10163 Update Hadoop plugin to latest stable version Change By: Josh Soref Summary: Uopdate Update Hadoop plugin to latest stable version Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140351.130941862.10711.1571424900388%40Atlassian.JIRA.
[JIRA] (JENKINS-10162) Update Hadoop plugin to latest stable version
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-10162 Update Hadoop plugin to latest stable version Change By: Josh Soref Summary: Uopdate Update Hadoop plugin to latest stable version Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140350.1309418588000.10714.1571424900430%40Atlassian.JIRA.
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title Josh Soref commented on JENKINS-59849 Re: Spaces don't work in resource root paths Daniel Beck found the problem: https://github.com/jenkinsci/jenkins/blob/11c1146d0dc30e948ade8d1636ae01345c294291/core/src/main/java/jenkins/security/ResourceDomainRootAction.java#L166-L176 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202585.1571419376000.10708.1571423880168%40Atlassian.JIRA.
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-59849
Spaces don't work in resource root paths
Change By:
Josh Soref
We have an archived folder called {{HeadlessChrome 77.0.3865 (Linux 0.0.0)}} with a file {{index.html}} the contents of that folder fail when served via resource root. If I make a copy of the folder {{HeadlessChrome-77.0.3865-(Linux-0.0.0)}}, that {{index.html}} file will be served successfully.Pipeline for testing:{code:java}node('master') { sh '''mkdir -p " a/ foo bar has lots of spaces to make people unhappy " touch " a/ foo bar has lots of spaces to make people unhappy /index.html" ''' archiveArtifacts ' foo bar a /'}{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Tony Poerio commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException Hi Devin Nusbaum – when will this fix be released? My team needs it. (Or at least we think we do.) And I saw that this message is from about 9 months back, at time of writing. As of right now, the current release is only `2.200`, (released 10-14-2019). However, the post immediately above is referencing version `2.29`. Is it possible that this update is already present in `2.200`? If not, when will it become available in a stable release? Many thanks for the help. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184823.1503944107000.10678.1571423460719%40Atlassian.JIRA.
[JIRA] (JENKINS-58381) Trend graph not appearing
Title: Message Title Michael Tupitsyn commented on JENKINS-58381 Re: Trend graph not appearing Hi, is there any update on this issue? We had to upgrade from 4.0.2 to 5.0.2 due to https://github.com/jeremylong/DependencyCheck/issues/1988, and now all report trends are gone. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200503.1562595115000.10667.1571422204040%40Atlassian.JIRA.
[JIRA] (JENKINS-59852) Strange logging {"enableFile":false,"tagFile":"","emitOnCheckout":false,"enableProperty":false,"tagProperties":""}
Title: Message Title
Josh Soref created an issue
Jenkins / JENKINS-59852
Strange logging {"enableFile":false,"tagFile":"","emitOnCheckout":false,"enableProperty":false,"tagProperties":""}
Issue Type:
Bug
Assignee:
Datadog HQ
Components:
datadog-plugin
Created:
2019-10-18 18:09
Priority:
Minor
Reporter:
Josh Soref
Periodically, this appears in my console where i'm running jenkins:
{"enableFile":false,"tagFile":"","emitOnCheckout":false,"enableProperty":false,"tagProperties":""}
datadog 0.7.1 At the very least, if datadog thinks it's important, it'd be nice if it had some indication it was from datadog.
Add Comment
[JIRA] (JENKINS-59851) Stash Pull Request Builder plugin keep on posting the Build Started comment without build result
Title: Message Title Nareen M created an issue Jenkins / JENKINS-59851 Stash Pull Request Builder plugin keep on posting the Build Started comment without build result Issue Type: Bug Assignee: Jakub Bochenski Attachments: Screen Shot 2019-10-18 at 10.47.08 AM.png Components: stash-pullrequest-builder-plugin Created: 2019-10-18 18:06 Environment: Jenkins: 2.190.1 Stash Pullrequest Builder Plugin: 1.13 Priority: Minor Reporter: Nareen M Stash Pull Request Builder plugin keeps on posting the Build Started comment, but I don't see any builds running on the Jenkins. I think it's happening when there are multiple PRs open or when new PR merged and the old PRs still open. Add Comment
[JIRA] (JENKINS-59850) Use of toString() on hudson.util.Secret from hudson.util.jelly.MorphTagLibrary$1.run(MorphTagLibrary.java:91)
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59850 Use of toString() on hudson.util.Secret from hudson.util.jelly.MorphTagLibrary$1.run(MorphTagLibrary.java:91) Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-10-18 18:01 Priority: Minor Reporter: Josh Soref Use of toString() on hudson.util.Secret from hudson.util.jelly.MorphTagLibrary$1.run(MorphTagLibrary.java:91). Prefer getPlainText() or getEncryptedValue() depending your needs. see https://jenkins.io/redirect/hudson.util.Secret/ https://github.com/jenkinsci/jenkins/blob/22aa2e6e766074d11249893e3f35e0b99e20d3d0/core/src/main/java/hudson/util/jelly/MorphTagLibrary.java#L91 Add Comment
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-59849
Spaces don't work in resource root paths
Change By:
Josh Soref
We have an archived folder called {{HeadlessChrome 77.0.3865 (Linux 0.0.0)}} with a file {{index.html}} the contents of that folder fail when served via resource root. If I make a copy of the folder {{HeadlessChrome-77.0.3865-(Linux-0.0.0)}}, that {{index.html}} file will be served successfully.Pipeline for testing:{code :java }node('master') { sh '''mkdir -p "foo bar" touch "foo bar/index.html" ''' archiveArtifacts 'foo bar/'}{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-59849
Spaces don't work in resource root paths
Change By:
Josh Soref
We have an archived folder called {{HeadlessChrome 77.0.3865 (Linux 0.0.0)}} with a file {{index.html}} the contents of that folder fail when served via resource root. If I make a copy of the folder {{HeadlessChrome-77.0.3865-(Linux-0.0.0)}}, that {{index.html}} file will be served successfully. Pipeline for testing:{code}node('master') { sh '''mkdir "foo bar" touch "foo bar/index.html" ''' archiveArtifacts 'foo bar/'}{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title Daniel Beck started work on JENKINS-59849 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202585.1571419376000.10651.1571420160690%40Atlassian.JIRA.
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-59849 Spaces don't work in resource root paths Change By: Daniel Beck Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202585.1571419376000.10648.1571420042499%40Atlassian.JIRA.
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-59849 Spaces don't work in resource root paths Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202585.1571419376000.10645.1571420042434%40Atlassian.JIRA.
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-59849 Spaces don't work in resource root paths Change By: Josh Soref Summary: Parentheses Spaces don't work in resource root paths Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202585.1571419376000.10642.1571419500069%40Atlassian.JIRA.
[JIRA] (JENKINS-59849) Parentheses don't work in resource root paths
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59849 Parentheses don't work in resource root paths Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-10-18 17:22 Priority: Minor Reporter: Josh Soref We have an archived folder called HeadlessChrome 77.0.3865 (Linux 0.0.0) with a file index.html the contents of that folder fail when served via resource root. If I make a copy of the folder HeadlessChrome-77.0.3865-(Linux-0.0.0), that index.html file will be served successfully. Add Comment
[JIRA] (JENKINS-59631) Adding different colors to history table and data filter
Title: Message Title Daniel Beck commented on JENKINS-59631 Re: Adding different colors to history table and data filter Kalana Wijethunga Thanks for your interest. This is a job's build history, e.g. on the left of https://ci.jenkins.io/job/Core/job/jenkins/job/master/ When you load the page, the background of the filter field near the top is white, and the topmost build has a grey background. Enter the number "7" into the filter field and press Enter: It will now have a grey background, and the topmost build has a white background. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202313.1570043107000.10635.1571418240161%40Atlassian.JIRA.
[JIRA] (JENKINS-59631) Adding different colors to history table and data filter
Title: Message Title Kalana Wijethunga commented on JENKINS-59631 Re: Adding different colors to history table and data filter I was able to reproduce this. I have attached the image herewith for your verification. I will start working on this. I would be thankful if you could provide me with some guidance on where should i look for this HTML/CSS files Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202313.1570043107000.10639.1571418300157%40Atlassian.JIRA.
[JIRA] (JENKINS-59631) Adding different colors to history table and data filter
Title: Message Title Kalana Wijethunga updated an issue Jenkins / JENKINS-59631 Adding different colors to history table and data filter Change By: Kalana Wijethunga Attachment: jenkinsIssue.JPG Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202313.1570043107000.10630.1571418180341%40Atlassian.JIRA.
[JIRA] (JENKINS-59631) Adding different colors to history table and data filter
Title: Message Title Kalana Wijethunga commented on JENKINS-59631 Re: Adding different colors to history table and data filter Hi all, I would like to work on fixing this. I am a newbie to this project so i hope you all will help me until i get a hang of the system. Can you kindly provide me with a screenshot of the page where this issue occurs so that i can recreate and start working on this? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202313.1570043107000.10620.1571417940406%40Atlassian.JIRA.
[JIRA] (JENKINS-59661) EC2 fails to provision due incorrect instance cap
Title: Message Title
Handi Gao commented on JENKINS-59661
Re: EC2 fails to provision due incorrect instance cap
ryan M Yeah, the probelm they are having is that the EC2 instance gets restarted in AWS but it will take some time for it to show as "Pending" and the plugin only checks the state of the instance once... if the state is neither running or pending, Jenkins stops provisioning the node... the pr adds the idea of retrying when waking up stopped instances so it should be able to solve the issue we are having right now
Oct 16, 2019 5:06:19 PM WARNING hudson.plugins.ec2.EC2Cloud$1 call
SlaveTemplate{ami='ami-02eac2c0129f6376b', labels='default master_ec2'}. Node stopped is neither pending, neither running, its {2}. Terminate provisioning
For the environment variables, I'm not sure if the init script can add them for you... you could check it out, may save you some effort
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202351.1570203874000.10593.1571414280315%40Atlassian.JIRA.
[JIRA] (JENKINS-59661) EC2 fails to provision due incorrect instance cap
Title: Message Title
Handi Gao edited a comment on JENKINS-59661
Re: EC2 fails to provision due incorrect instance cap
[~ryan_m] Yeah, the probelm they are having is that the EC2 instance gets restarted in AWS but it will take some time for it to show as "Pending" and the plugin only checks the state of the instance once... if the state is neither running or pending, Jenkins the plugin stops provisioning the node... the pr adds the idea of retrying when waking up stopped instances so it should be able to solve the issue we are having right now{code:java}Oct 16, 2019 5:06:19 PM WARNING hudson.plugins.ec2.EC2Cloud$1 callSlaveTemplate{ami='ami-02eac2c0129f6376b', labels='default master_ec2'}. Node stopped is neither pending, neither running, its {2}. Terminate provisioning{code}For the environment variables, I'm not sure if the init script can add them for you... you could check it out, may save you some effort :P
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202351.1570203874000.10597.1571414280425%40Atlassian.JIRA.
[JIRA] (JENKINS-59831) update JsonPath from 0.5.5 to 2.4.0
Title: Message Title Kemal Soysal assigned an issue to Tony Noble Jenkins / JENKINS-59831 update JsonPath from 0.5.5 to 2.4.0 Change By: Kemal Soysal Assignee: Gregory Boissinot Tony Noble Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202566.1571343899000.10587.1571413740358%40Atlassian.JIRA.
[JIRA] (JENKINS-59847) Hashicorp Vault plugin - CASC - approle path not configurable
Title: Message Title Emmanuel Cornette created an issue Jenkins / JENKINS-59847 Hashicorp Vault plugin - CASC - approle path not configurable Issue Type: Improvement Assignee: Peter Tierno Components: hashicorp-vault-plugin Created: 2019-10-18 15:44 Priority: Minor Reporter: Emmanuel Cornette As implemented in JENKINS-54635, it should be possible to configure an alternate approle path in CASC location : line 24 of https://github.com/jenkinsci/hashicorp-vault-plugin/blob/hashicorp-vault-plugin-3.0.0/src/main/java/com/datapipe/jenkins/vault/jcasc/secrets/VaultAppRoleAuthenticator.java ".loginByAppRole(approle, approleSecret)" to be replaced by .loginByAppRole(, approle, approleSecret) Add Comment
[JIRA] (JENKINS-59661) EC2 fails to provision due incorrect instance cap
Title: Message Title ryan M commented on JENKINS-59661 Re: EC2 fails to provision due incorrect instance cap If jenkins has stopped the instance and tries to connect to it I get the instance cap error but the EC2 instance will be running in the EC2 console. I think terminating the instances instead of stopping will work for us. However, we have environment variables set for each node that need to be manually added when a new node is brought up. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202351.1570203874000.10575.1571413320363%40Atlassian.JIRA.
[JIRA] (JENKINS-59831) update JsonPath from 0.5.5 to 2.4.0
Title: Message Title Kemal Soysal stopped work on JENKINS-59831 Change By: Kemal Soysal Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202566.1571343899000.10570.1571412780433%40Atlassian.JIRA.
[JIRA] (JENKINS-59831) update JsonPath from 0.5.5 to 2.4.0
Title: Message Title Kemal Soysal assigned an issue to Gregory Boissinot Jenkins / JENKINS-59831 update JsonPath from 0.5.5 to 2.4.0 Change By: Kemal Soysal Assignee: Kemal Soysal Gregory Boissinot Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202566.1571343899000.10573.1571412780538%40Atlassian.JIRA.
[JIRA] (JENKINS-59846) Hyperlink URLs in JUnit Test Report
Title: Message Title Kim Randell created an issue Jenkins / JENKINS-59846 Hyperlink URLs in JUnit Test Report Issue Type: Improvement Assignee: Unassigned Attachments: url.xml Components: junit-plugin Created: 2019-10-18 15:27 Environment: Windows Server 2012 Jenkins 2.176.4 JUnit 1.28 Priority: Minor Reporter: Kim Randell Adding a URL to JUnit output will automatically hyperlink in the page for the individual test (see https://issues.jenkins-ci.org/browse/JENKINS-3225 ). However, it does not get linked for the Test Report page when expanding the failure. Steps to reproduce: Create a Freestyle job with url.xml in the workspace In the build steps, touch url.xml In Post-Build Actions, add Publish JUnit test result report with Test Result XMLs as *.xml Run job Go to Test Results Expand All Failed Tests URL is not hyperlinked. Click test name link to go to test page. URL is hyperlinked.
[JIRA] (JENKINS-59825) Can't update git client plugin
Title: Message Title Robert Hill resolved as Fixed Solution is posted to "Description" section Jenkins / JENKINS-59825 Can't update git client plugin Change By: Robert Hill Status: Open Resolved Assignee: Robert Hill Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-59825) Can't update git client plugin
Title: Message Title Robert Hill updated an issue Jenkins / JENKINS-59825 Can't update git client plugin Change By: Robert Hill I'm new to Jenkins. I installed the various git plugins and had it working for a pipeline project. Recently, Jenkins notified me of a security vulnerability for the git client. I choose to downgrade from 3.0 to the previous version. After doing that, my pipeline lost it's reference to the git login. Any new pipelines doesn't list git as a choice. When I go into the manage plugins, it doesn't list the git-client with an available update. How do I get it back to using the 3.x version? I found the solution. I went to [https://updates.jenkins-ci.org/download/plugins/] and downloaded .hpi files for git plugin 3.12.1 & git-client 2.8.6. I used the "Advanced" tab within the "Managed Plugins" page and used the update plugins section to install these versions. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you
[JIRA] (JENKINS-59831) update JsonPath from 0.5.5 to 2.4.0
Title: Message Title Kemal Soysal started work on JENKINS-59831 Change By: Kemal Soysal Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202566.1571343899000.10563.1571411880289%40Atlassian.JIRA.
[JIRA] (JENKINS-59810) Kubernetes Plugin fails with PVC error from 1.19.2 onwards
Title: Message Title Ronald Schuurman commented on JENKINS-59810 Re: Kubernetes Plugin fails with PVC error from 1.19.2 onwards We are running in Kubernetes 1.9.2 and get exactly the same issue. Also after upgrading to Kubernetes Plugin from 1.20.0 to 1.20.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202541.157126394.10561.1571411880240%40Atlassian.JIRA.
[JIRA] (JENKINS-59831) update JsonPath from 0.5.5 to 2.4.0
Title: Message Title Kemal Soysal assigned an issue to Kemal Soysal Jenkins / JENKINS-59831 update JsonPath from 0.5.5 to 2.4.0 Change By: Kemal Soysal Assignee: Gregory Boissinot Kemal Soysal Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202566.1571343899000.10559.1571411820236%40Atlassian.JIRA.
[JIRA] (JENKINS-59661) EC2 fails to provision due incorrect instance cap
Title: Message Title Handi Gao commented on JENKINS-59661 Re: EC2 fails to provision due incorrect instance cap ryan M We are having this issue as well and noticed the same as Denis Bel. The current workaround we have is that instead of stopping the instances after idle timeout, we terminate the instances, i.e. uncheck the option "Stop/Disconnect on Idle Timeout". I think the root cause is somehow releated to JENKINS-57795 which has an open pr addressing it https://github.com/jenkinsci/ec2-plugin/pull/399 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202351.1570203874000.10555.1571410982729%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Andrey Babushkin commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head We've faced this issue today. Our 300+ parallel pipeline builds have failed simultaneously due to the error in ticket's description. But I've found the following in Jenkins server's logs in the same time: [207043.805s][warning][os,thread] Attempt to protect stack guard pages failed (0x7f6d188c9000-0x7f6d188cd000). [207043.805s][warning][os,thread] Attempt to deallocate stack guard pages failed. OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x7f6d187c8000, 16384, 0) failed; error='Not enough space' (errno=12) [207043.810s][warning][os,thread] Failed to start thread - pthread_create failed (EAGAIN) for attributes: stacksize: 1024k, guardsize: 0k, detached. [207043.811s][warning][os,thread] Failed to start thread - pthread_create failed (EAGAIN) for attributes: stacksize: 1024k, guardsize: 0k, detached. # # There is insufficient memory for the Java Runtime Environment to continue. # Native memory allocation (mmap) failed to map 16384 bytes for committing reserved memory. # An error report file with more information is saved as: # /tmp/hs_err_pid6.log So I guess something is wrong with our settings (out of memory on server with 180GB of RAM? Our Jenkins instance's load isn't that much, we've run the same load on VM with 60GB of RAM, but with 20 GB of swap) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-3225) Hyperlink URLs in JUnit output
Title: Message Title Kim Randell commented on JENKINS-3225 Re: Hyperlink URLs in JUnit output Just noticed that it does work correctly when viewing the individual test, but not when expanding All Failed Tests from the main Test Report. I'll report that as a new issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.133298.123618976.10527.1571410200212%40Atlassian.JIRA.
[JIRA] (JENKINS-3225) Hyperlink URLs in JUnit output
Title: Message Title Jesse Glick commented on JENKINS-3225 Re: Hyperlink URLs in JUnit output I doubt the plugin split would have mattered, but it could have regressed since then for other reasons. Best to file a separate bug with complete steps to reproduce from scratch, linked to this one. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.133298.123618976.10525.1571409720120%40Atlassian.JIRA.
[JIRA] (JENKINS-57712) Allow entering search path for git blame
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-57712 Allow entering search path for git blame Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/219 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199653.1559042804000.10519.1571409540977%40Atlassian.JIRA.
[JIRA] (JENKINS-57712) Allow entering search path for git blame
Title: Message Title Ulli Hafner started work on JENKINS-57712 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199653.1559042804000.10515.1571409540814%40Atlassian.JIRA.
[JIRA] (JENKINS-59661) EC2 fails to provision due incorrect instance cap
Title: Message Title Denis Bel commented on JENKINS-59661 Re: EC2 fails to provision due incorrect instance cap ryan M we are experiencing the same issue, but in our case agents marked as Offline in Jenkins actually are still running in AWS. After stop those EC2 instances manually via AWS console, we can see increased capacity again, you could check this out too. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202351.1570203874000.10522.1571409541016%40Atlassian.JIRA.
[JIRA] (JENKINS-57260) git blame fails for out-of-tree builds
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-57260 git blame fails for out-of-tree builds Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/219 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199025.1556641885000.10509.1571409480369%40Atlassian.JIRA.
[JIRA] (JENKINS-57260) git blame fails for out-of-tree builds
Title: Message Title Ulli Hafner started work on JENKINS-57260 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199025.1556641885000.10505.1571409240574%40Atlassian.JIRA.
[JIRA] (JENKINS-3225) Hyperlink URLs in JUnit output
Title: Message Title Kim Randell commented on JENKINS-3225 Re: Hyperlink URLs in JUnit output Jesse Glick Was this lost in the conversion to a plugin? It doesn't seem to work any more. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.133298.123618976.10500.1571407980207%40Atlassian.JIRA.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title
Pablo Rodriguez edited a comment on JENKINS-55308
Re: intermittent "terminated" messages using sh in Pipelines
The issue could be reproduced by running this simple Pipeline:{code:java}Pipeline scriptpipeline { agent { label ' rhel6 nodelinux ' } stages { stage('build') {steps { echo "Hello World!" sh "echo Hello from the shell"{code}Console output:{code:java}[Pipeline] Start of Pipeline[Pipeline] node[Pipeline] {[Pipeline] stage[Pipeline] { (build)[Pipeline] echoHello World![Pipeline] sh+ echo Hello from the shellHello from the shell[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinesh: line 1: 18285 Terminated sleep 3Finished: SUCCESS{code}Environment: * CloudBees Jenkins Platform - Master [2.176.2.3|https://release-notes.cloudbees.com/release/1/2.176.2.3] * workflow-job:2.32 'Pipeline: Job'It started happening after workflow-job was updated from 2.25 to 2.32
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196395.1545434467000.10458.1571407680958%40Atlassian.JIRA.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title
Pablo Rodriguez commented on JENKINS-55308
Re: intermittent "terminated" messages using sh in Pipelines
The issue could be reproduced by running this simple Pipeline:
Pipeline script
pipeline {
agent { label 'rhel6' }
stages {
stage('build') {
steps {
echo "Hello World!"
sh "echo Hello from the shell"
}
}
}
}
Console output:
[Pipeline] Start of Pipeline
[Pipeline] node
[Pipeline] {
[Pipeline] stage
[Pipeline] { (build)
[Pipeline] echo
Hello World!
[Pipeline] sh
+ echo Hello from the shell
Hello from the shell
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
sh: line 1: 18285 Terminated sleep 3
Finished: SUCCESS
Environment:
CloudBees Jenkins Platform - Master 2.176.2.3
workflow-job:2.32 'Pipeline: Job'
It started happening after workflow-job was updated from 2.25 to 2.32
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title Denis Bel edited a comment on JENKINS-59724 Re: no known implementation of class java.lang.String is named Target [~aleksisimell]So finally I found a way to reproduce: * open a build which contains InfluxDB step with `target` instead of `selectedTarget` * press `Pipeline Steps` link: * !image-2019-10-18-16-47-00-919.png|width=311,height=694!Warning will appear in log immediately BlueOcean view also triggers it Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202441.1570700819000.10415.1571407260399%40Atlassian.JIRA.
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title Denis Bel commented on JENKINS-59724 Re: no known implementation of class java.lang.String is named Target Aleksi Simell So finally I found a way to reproduce: open a build which contains InfluxDB step with `target` instead of `selectedTarget` press `Pipeline Steps` link: Warning will appear in log immediately Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202441.1570700819000.10412.1571406540171%40Atlassian.JIRA.
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title Denis Bel updated an issue Jenkins / JENKINS-59724 no known implementation of class java.lang.String is named Target Change By: Denis Bel Attachment: image-2019-10-18-16-47-00-919.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202441.1570700819000.10409.1571406480184%40Atlassian.JIRA.
[JIRA] (JENKINS-59845) Whitelisting of Gerrit-users/groups whose changes are built
Title: Message Title Thomas Draebing created an issue Jenkins / JENKINS-59845 Whitelisting of Gerrit-users/groups whose changes are built Issue Type: New Feature Assignee: lucamilanesio Components: gerrit-code-review-plugin Created: 2019-10-18 13:34 Priority: Minor Reporter: Thomas Draebing Building every change that is pushed to Gerrit is potentially dangerous on publicly accessible Gerrit servers, since users may add malicious code that might be executed during the build job. As an example, the Kubernetes project solves this issue by requiring a label in each pull request that will be validated. This label can only be set by trusted contributors of the project. A similar setup would also be useful to have for changes in Gerrit. A way to do this would be to decide on the change's author and/or his/her group in Gerrit whether to trigger a build. A build of a change of a non-whitelisted user could be then triggered by a label set in Gerrit by a project maintainer. This functionality should be part of this plugin and would be useful for a lot of projects. Add Comment
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title Denis Bel commented on JENKINS-59724 Re: no known implementation of class java.lang.String is named Target Aleksi Simell Seems this issue might be related to workflow plugin I found this in jobs/adhoc-db-create-dump/builds/24/workflow/66.xml '1.1' encoding='UTF-8'?> "workflow-support@3.3"> "cps.n.StepAtomNode" plugin="workflow-cps@2.68"> 65 66 org.jenkinsci.plugins.workflow.steps.CoreStep "workflow-cps@2.68"> delegate $class</string> InfluxDbPublisher customData versionendpoint scmrevision 5c5626 customDataMap customPrefix target Preprod InfluxDB Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google
[JIRA] (JENKINS-59844) Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-59844 Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command Change By: Daniel Beck Labels: robustness Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202579.1571403818000.10399.1571405220168%40Atlassian.JIRA.
[JIRA] (JENKINS-59843) Remote access API job builds list limit shouldn't be hardcoded
Title: Message Title Daniel Beck closed an issue as Won't Fix that's what allBuilds is for, documented in the section titled "Retrieving all builds". Pagination (well, slicing) exists as documented in the section titled "Controlling the amount of data you fetch" Jenkins / JENKINS-59843 Remote access API job builds list limit shouldn't be hardcoded Change By: Daniel Beck Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-59665) Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-59665 Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager Change By: Daniel Beck Attachment: Screenshot 2019-10-18 at 15.20.09.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202357.1570213644000.10393.1571404921580%40Atlassian.JIRA.
[JIRA] (JENKINS-59665) Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager
Title: Message Title Daniel Beck commented on JENKINS-59665 Re: Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager At least on Jenkins 2.190.1, the "Enabled" column does not behave. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202357.1570213644000.10390.1571404860839%40Atlassian.JIRA.
[JIRA] (JENKINS-57260) git blame fails for out-of-tree builds
Title: Message Title
m l commented on JENKINS-57260
Re: git blame fails for out-of-tree builds
Using dir('src') does not really help My pipeline checks out the source code in a separate folder by settings the option
skipDefaultCheckout()
I checkout the source into ${ws}/Platform via
stage('Checkout') {
steps {
script {
def gitVarsPlatform = checkout([$class: 'GitSCM',
branches: [[name: "${env.BRANCH_NAME}"]],
extensions: [[$class: 'CleanCheckout', $class: 'RelativeTargetDirectory', relativeTargetDir: 'Platform']],
userRemoteConfigs: [[url: 'https://X.git', name: 'Platform', credentialsId: '' ]]
])
lastChanges since: 'LAST_SUCCESSFUL_BUILD', format:'SIDE',matching: 'LINE'
}
}
}
When I start analyzing the warnings following way:
post {
always {
dir('Platform') {
recordIssues enabledForFailure: true, tool: msBuild()
}
}
}
Warnings are counted correctly but git blame fails with
[Pipeline] dir
14:08:31 Running in C:\jenkins\w\latform_feature_jenkins_master_2\Platform
[Pipeline] {
[Pipeline] recordIssues
14:08:31 [MSBuild] Sleeping for 5 seconds due to JENKINS-32191...
14:08:36 [MSBuild] Parsing console log (workspace: 'C:\jenkins\w\latform_feature_jenkins_master_2\Platform')
14:08:45 using credential
14:08:45 using credential
14:08:50 > git rev-parse "HEAD^{commit}" # timeout=10
14:08:52 [MSBuild] [-ERROR-] Errors while extracting author and commit information from Git:
14:08:52 [MSBuild] [-ERROR-] - error running git blame on 'UnitTests/X/ServicePlugIn.UnitTest/TestCases/WhenSetXXXInvoked.cs' with revision 'AnyObjectId[be2c88e23e194da25873f9440a8f35d62ced0835]'
14:08:52 [MSBuild] [-ERROR-] org.eclipse.jgit.errors.MissingObjectException: Missing unknown be2c88e23e194da25873f9440a8f35d62ced0835
14:08:52 [MSBuild] [-ERROR-] at org.eclipse.jgit.internal.storage.file.WindowCursor.open(WindowCursor.java:158)
14:08:52 [MSBuild] [-ERROR-] at org.eclipse.jgit.lib.ObjectReader.open(ObjectReader.java:227)
14:08:52 [MSBuild] [-ERROR-] at org.eclipse.jgit.blame.BlameGenerator.push(BlameGenerator.java:317)
14:08:52 [MSBuild] [-ERROR-] at org.eclipse.jgit.api.BlameCommand.call(BlameCommand.java:214)
14:08:52 [MSBuild] [-ERROR-] [wrapped] org.eclipse.jgit.api.errors.JGitInternalException: Missing unknown
[JIRA] (JENKINS-57435) Cannot configure SSH credentials via Job DSL
Title: Message Title
Renzo Crisóstomo edited a comment on JENKINS-57435
Re: Cannot configure SSH credentials via Job DSL
If you're wondering how to do this with configure blocks, it's something like this:{code:java} folder('example') {properties {folderCredentialsProperty {domainCredentials {domainCredentials {domain { name("") description("")}}}}}configure {def configNode = it / 'properties' / 'com.cloudbees.hudson.plugins.folder.properties.FolderCredentialsProvider_-FolderCredentialsProperty' / 'domainCredentialsMap' / 'entry' / 'java.util.concurrent.CopyOnWriteArrayList'configNode << 'com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey' {id("test_ssh_credentials")description("")username("test_ssh_credentials")privateKeySource(class:"com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey\$DirectEntryPrivateKeySource") {privateKey("""YOUR_PRIVATE_KEY_HERE""")}} }} {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199248.1557757091000.10380.1571404262227%40Atlassian.JIRA.
[JIRA] (JENKINS-57435) Cannot configure SSH credentials via Job DSL
Title: Message Title
Renzo Crisóstomo commented on JENKINS-57435
Re: Cannot configure SSH credentials via Job DSL
If you're wondering how to do this with configure blocks, it's something like this:
configNode << 'com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey' {
id("test_ssh_credentials")
description("")
username("test_ssh_credentials")
privateKeySource(class:"com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey\$DirectEntryPrivateKeySource") {
privateKey("""YOUR_PRIVATE_KEY_HERE""")
}
}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199248.1557757091000.10375.1571404140194%40Atlassian.JIRA.
[JIRA] (JENKINS-59844) Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command
Title: Message Title
Esther Álvarez Feijoo created an issue
Jenkins / JENKINS-59844
Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
2019-10-18 13:03
Environment:
Oracle JRE 8 and 11 Jenkins 2.190.1
Priority:
Minor
Reporter:
Esther Álvarez Feijoo
If you try to launch a blank command (' ') using Launch.ProcStarter#cmdAsSingleString, an ArrayIndexOutOfBoundException is thrown. Example of command invocation:
launcher.launch()
.cmdAsSingleString(" ")
.envs(computer.getEnvironment())
.readStdout()
.pwd(rootPath)
.start();
Exception thrown:
java.lang.ArrayIndexOutOfBoundsException: 0
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1014)
at hudson.Proc$LocalProc.(Proc.java:249)
at hudson.Proc$LocalProc.(Proc.java:218)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:930)
at hudson.Launcher$ProcStarter.start(Launcher.java:450)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1299)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1260)
at hudson.remoting.UserRequest.perform(UserRequest.java:205)
at hudson.remoting.UserRequest.perform(UserRequest.java:52)
at hudson.remoting.Request$2.run(Request.java:356)
at
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title
Denis Bel edited a comment on JENKINS-59724
Re: no known implementation of class java.lang.String is named Target
[~aleksisimell] Sure, thanks for the notice, I have a backup for both files. Unfortunately I am still getting those errors.WARNING o.j.p.s.d.DescribableModel#uninstantiate2: Cannot create control version of class org.jenkinsci.plugins.workflow.steps.CoreStep using {delegate=$InfluxDbPublisher During digging into logs and using saved scmrevision in custom data, I found affected builds and some weird things.. Two examples:1. Warning appeared today: {code:java}2019-10-18 09:51:53.876+ [id=199445]WARNINGhudson.util.Secret#toString: Use of toString() on hudson.util.Secret from java.lang.String.valueOf(String.java:2994). Prefer getPlainText() or getEncryptedValue() depending your needs. see https://jenkins.io/redirect/hudson.util.Secret/2019-10-18 09:51:53.877+ [id=199445] WARNINGhudson.util.Secret#toString: Use of toString() on hudson.util.Secret from java.lang.String.valueOf(String.java:2994). Prefer getPlainText() or getEncryptedValue() depending your needs. see https://jenkins.io/redirect/hudson.util.Secret/2019-10-18 09:51:53.877+ [id=199445] WARNINGhudson.util.Secret#toString: Use of toString() on hudson.util.Secret from java.lang.String.valueOf(String.java:2994). Prefer getPlainText() or getEncryptedValue() depending your needs. see https://jenkins.io/redirect/hudson.util.Secret/2019-10-18 09:51:53.877+ [id=199445] WARNINGo.j.p.s.d.DescribableModel#uninstantiate2: Cannot create control version of classorg.jenkinsci.plugins.workflow.steps.CoreStep using {delegate=$InfluxDbPublisher(customData={version=null, endpoint=null, scmrevision=5c5626}{code}but job with this scmrevision was actually executed in May{code:java}***/adhoc-db-create-dump/builds/24/log:[2019-05-31T12:35:38.878Z] [InfluxDB Plugin] customData: [version:null, endpoint:null, scmrevision:5c5626]{code} 2. At the same time today (according timestamps) appeared another warning:{code:java}2019-10-18 09:51:53.830+ [id=199445] WARNINGo.j.p.s.d.DescribableModel#uninstantiate2: Cannot create control version of classorg.jenkinsci.plugins.workflow.steps.CoreStep using {delegate=$InfluxDbPublisher(customData={version=null, endpoint=null, scmrevision=aa7495}{code}Job was executed in July{code:java}***/adhoc-db-download/builds/69/log:[2019-07-25T14:27:05.908Z] [InfluxDB Plugin] customData: [version:null, endpoint:null, scmrevision:aa7495]***/adhoc-db-download/builds/68/log:[2019-07-25T11:22:18.183Z] [InfluxDB Plugin] customData: [version:null, endpoint:null, scmrevision:aa7495]{code} That job has no executions since August Any Ideas what is happening?
Add Comment
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title
Denis Bel commented on JENKINS-59724
Re: no known implementation of class java.lang.String is named Target
Aleksi Simell Sure, thanks for the notice, I have a backup for both files. Unfortunately I am still getting those errors. WARNING o.j.p.s.d.DescribableModel#uninstantiate2: Cannot create control version of class org.jenkinsci.plugins.workflow.steps.CoreStep using {delegate=$InfluxDbPublisher During digging into logs and using saved scmrevision in custom data, I found affected builds and some weird things.. Two examples: 1. Warning appeared today:
2019-10-18 09:51:53.876+ [id=199445]WARNINGhudson.util.Secret#toString: Use of toString() on hudson.util.Secret from java.lang.String.valueOf(String.java:2994). Prefer getPlainText() or getEncryptedValue() depending your needs. see https://jenkins.io/redirect/hudson.util.Secret/
2019-10-18 09:51:53.877+ [id=199445] WARNINGhudson.util.Secret#toString: Use of toString() on hudson.util.Secret from java.lang.String.valueOf(String.java:2994). Prefer getPlainText() or getEncryptedValue() depending your needs. see https://jenkins.io/redirect/hudson.util.Secret/
2019-10-18 09:51:53.877+ [id=199445] WARNINGhudson.util.Secret#toString: Use of toString() on hudson.util.Secret from java.lang.String.valueOf(String.java:2994). Prefer getPlainText() or getEncryptedValue() depending your needs. see https://jenkins.io/redirect/hudson.util.Secret/
2019-10-18 09:51:53.877+ [id=199445] WARNING
o.j.p.s.d.DescribableModel#uninstantiate2: Cannot create control version of class
org.jenkinsci.plugins.workflow.steps.CoreStep using {delegate=$InfluxDbPublisher(customData={version=null, endpoint=null, scmrevision=5c5626}
but job with this scmrevision was actually executed in May
***/adhoc-db-create-dump/builds/24/log:[2019-05-31T12:35:38.878Z] [InfluxDB Plugin] customData: [version:null, endpoint:null, scmrevision:5c5626]
2. At the same time today (according timestamps) appeared another warning:
2019-10-18 09:51:53.830+ [id=199445] WARNING
o.j.p.s.d.DescribableModel#uninstantiate2: Cannot create control version of class
org.jenkinsci.plugins.workflow.steps.CoreStep using {delegate=$InfluxDbPublisher(customData={version=null, endpoint=null, scmrevision=aa7495}
Job was executed in July
***/adhoc-db-download/builds/69/log:[2019-07-25T14:27:05.908Z] [InfluxDB Plugin] customData: [version:null, endpoint:null, scmrevision:aa7495]
***/adhoc-db-download/builds/68/log:[2019-07-25T11:22:18.183Z] [InfluxDB Plugin] customData: [version:null, endpoint:null,
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title Denis Bel updated an issue Jenkins / JENKINS-59724 no known implementation of class java.lang.String is named Target Change By: Denis Bel Attachment: image-2019-10-18-15-16-12-400.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202441.1570700819000.10361.1571401140302%40Atlassian.JIRA.
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title Denis Bel updated an issue Jenkins / JENKINS-59724 no known implementation of class java.lang.String is named Target Change By: Denis Bel Attachment: image-2019-10-18-15-16-12-400.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202441.1570700819000.10358.1571401020286%40Atlassian.JIRA.
[JIRA] (JENKINS-12548) Read-only configuration summary page support
Title: Message Title Jesse Glick commented on JENKINS-12548 Re: Read-only configuration summary page support From the discussion of JCasC I am guessing this is being interpreted in the context of global settings. There is a somewhat analogous RFE for project settings: JENKINS-50173. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.142914.1327605395000.10354.1571400600229%40Atlassian.JIRA.
[JIRA] (JENKINS-43820) Stage name must be a string literal
Title: Message Title
Chris Hemp commented on JENKINS-43820
Re: Stage name must be a string literal
Karolina Arancibia Valuskova is that with scripted pipeline or declarative syntax? I tried above inside declarative syntax (`pipeline {...}`) and above did not work.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181338.1493122184000.10325.1571399520620%40Atlassian.JIRA.
[JIRA] (JENKINS-59843) Remote access API job builds list limit shouldn't be hardcoded
Title: Message Title
Oded Arbel created an issue
Jenkins / JENKINS-59843
Remote access API job builds list limit shouldn't be hardcoded
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
2019-10-18 11:35
Environment:
Operating System: Fedora 30 64bit JDK: openjdk 8 Jenkins verrsion: 2.200, from official docker hub container image
Labels:
REST remote-api
Priority:
Minor
Reporter:
Oded Arbel
When using the Remote Access API to get the list of builds in a job, for example - like this: curl https://${AUTH}@jenkins/job/myjob/api/json -G --data-urlencode 'tree=builds[number]' only the last 100 jobs are returned. This seem to be hard coded in the Job model (saw it here: https://github.com/jenkinsci/jenkins/blob/11c1146d0dc30e948ade8d1636ae01345c294291/core/src/main/java/hudson/model/Job.java#L737 ) There should be a way to override this and get at the older builds - by paging, setting the limit, etc. The only workaround seem to be to check if a build exists by guessing its number (shouldn't be hard as they're sequential) and query each and every build URL directly. If a job has a few thousand builds, this gets really old really fast.
[JIRA] (JENKINS-59841) Scriptler 3.1 destroys groovy scripts containing German special characters (Umlauts)
Title: Message Title Robert Nitschke commented on JENKINS-59841 Re: Scriptler 3.1 destroys groovy scripts containing German special characters (Umlauts) Dominik Bartholdi Please find two files attached. One is the original one saved with Scriptler 2.9. Second is after editing and saving it using Scriptler 3.1. You can see encoding of this file was changed to UTF-8 and two characters 'ß' were replaced by '?'. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202576.1571392265000.10322.1571397900209%40Atlassian.JIRA.
[JIRA] (JENKINS-59841) Scriptler 3.1 destroys groovy scripts containing German special characters (Umlauts)
Title: Message Title Robert Nitschke updated an issue Jenkins / JENKINS-59841 Scriptler 3.1 destroys groovy scripts containing German special characters (Umlauts) Change By: Robert Nitschke Attachment: Debug_Scriptler2.9.groovy Attachment: Debug_Scriptler3.1.groovy Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202576.1571392265000.10318.1571397660220%40Atlassian.JIRA.
[JIRA] (JENKINS-59841) Scriptler 3.1 destroys groovy scripts containing German special characters (Umlauts)
Title: Message Title Dominik Bartholdi commented on JENKINS-59841 Re: Scriptler 3.1 destroys groovy scripts containing German special characters (Umlauts) Robert Nitschke could you please check wether the files are also saved with the wrong encoding on the disc? at /scriptler/scripts?*.groovy and could you attach a simple example file? thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202576.1571392265000.10316.1571396400427%40Atlassian.JIRA.
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Jakub Bochenski commented on JENKINS-59833 Re: Stash Pull Request Builder Multiple PR in single build I don't expect I'll find time to investigate this any time soon. If you can investigate the issue and file a PR I'll be happy to review it (that's what "experimental support" is about) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202568.1571346229000.10313.1571395980159%40Atlassian.JIRA.
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Jakub Bochenski assigned an issue to Unassigned Jenkins / JENKINS-59833 Stash Pull Request Builder Multiple PR in single build Change By: Jakub Bochenski Assignee: Jakub Bochenski Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202568.1571346229000.10311.1571395800155%40Atlassian.JIRA.
[JIRA] (JENKINS-45685) Declarative Pipeline Example
Title: Message Title
vassil marjunits edited a comment on JENKINS-45685
Re: Declarative Pipeline Example
After version 2.3.0 and higher, 3.0.0 was latest, when this comment was made{code:java}// define vault configurationdef configuration = [engineVersion: 1, skipSslVerification: true, timeout: 60, vaultUrl: "http://my-vault.com:8200", vaultCredentialId: "my-vault-cred-id"]// define vault secret path and env vardef secret = [ [path: 'dev/kv1', secretValues: [[envVar: 'PASSWORD', vaultKey: 'password'],[envVar: 'USER', vaultKey: 'user' pipeline {agent anyoptions {buildDiscarder(logRotator(numToKeepStr: '20'))disableConcurrentBuilds()}stages{ stage('Vault') {steps {script {withVault([configuration: configuration, vaultSecrets: secret]) { sh 'echo $PASSWORD' sh 'echo $USER'}}} }}post {always {cleanWs()}}}{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183881.1500551847000.10306.1571393820420%40Atlassian.JIRA.
[JIRA] (JENKINS-45685) Declarative Pipeline Example
Title: Message Title
vassil marjunits edited a comment on JENKINS-45685
Re: Declarative Pipeline Example
After version 2.3.0 and higher,3.0.0 was latest, when this comment was made{code:java}// define vault configurationdef configuration = [engineVersion: 1,skipSslVerification: true,timeout: 60,vaultUrl: ' " http:// 172 my-vault . 21.0.2 com :8200 ' " ,vaultCredentialId: "my-vault-cred-id"]// define vault secret path and env vardef secret = [ [path: 'dev/kv1', secretValues: [[envVar: 'PASSWORD', vaultKey: 'password'],[envVar: 'USER', vaultKey: 'user'pipeline {agent anyoptions {buildDiscarder(logRotator(numToKeepStr: '20'))disableConcurrentBuilds()}stages{ stage('Vault') {steps {script {withVault([configuration: configuration, vaultSecrets: secret]) { sh 'echo $PASSWORD' sh 'echo $USER'}}} }}post {always {cleanWs()}}}{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183881.1500551847000.10300.1571393760243%40Atlassian.JIRA.
[JIRA] (JENKINS-45685) Declarative Pipeline Example
Title: Message Title
vassil marjunits commented on JENKINS-45685
Re: Declarative Pipeline Example
After version 2.3.0 and higher, 3.0.0 was latest, when this comment was made
// define vault configuration
def configuration = [engineVersion: 1, skipSslVerification: true, timeout: 60, vaultUrl: 'http://172.21.0.2:8200', vaultCredentialId: "my-vault-cred-id"]
// define vault secret path and env var
def secret = [
[path: 'dev/kv1', secretValues: [
[envVar: 'PASSWORD', vaultKey: 'password'],
[envVar: 'USER', vaultKey: 'user']]]
]pipeline {
agent any
options {
buildDiscarder(logRotator(numToKeepStr: '20'))
disableConcurrentBuilds()
}
stages{
stage('Vault') {
steps {
script {
withVault([configuration: configuration, vaultSecrets: secret]) {
sh 'echo $PASSWORD'
sh 'echo $USER'
}
}
}
}
}
post {
always {
cleanWs()
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-59834) Retry Mechanism for collate and analyze when it fails
Title: Message Title Maria Narcisa Galan assigned an issue to Daniel Danan Jenkins / JENKINS-59834 Retry Mechanism for collate and analyze when it fails Change By: Maria Narcisa Galan Assignee: Maria Narcisa Galan Daniel Danan Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202569.157136096.10283.1571392740305%40Atlassian.JIRA.
[JIRA] (JENKINS-31120) blank page show up after click run button with parameterized builds
Title: Message Title Sini George updated an issue Jenkins / JENKINS-31120 blank page show up after click run button with parameterized builds Change By: Sini George Comment: !After clicking on run button of the job, the pop-up window shows blank page when the first job of the pipeline is parameterized..PNG|thumbnail! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165772.1445566982000.10278.1571392680377%40Atlassian.JIRA.
[JIRA] (JENKINS-59842) The run button is not clickable when the first job of the pipeline is parameterized.
Title: Message Title Sini George created an issue Jenkins / JENKINS-59842 The run button is not clickable when the first job of the pipeline is parameterized. Issue Type: Bug Assignee: Unassigned Attachments: Screenshot from 2019-10-18 15-15-48.png Components: build-pipeline-plugin Created: 2019-10-18 09:57 Priority: Major Reporter: Sini George The run button is not clickable when the first job of the pipeline is parameterized. A similar bug has already been opened and fixed a few years ago here, but I still have the same problem with the current version. jenkins version-2.190.1 latest plugin version 1.5.8 Add Comment
[JIRA] (JENKINS-59841) Scriptler 3.1 destroys groovy scripts containing German special characters (Umlauts)
Title: Message Title
Robert Nitschke created an issue
Jenkins / JENKINS-59841
Scriptler 3.1 destroys groovy scripts containing German special characters (Umlauts)
Issue Type:
Bug
Assignee:
Dominik Bartholdi
Components:
scriptler-plugin
Created:
2019-10-18 09:51
Environment:
Windows Server 2008 64bit Jenkins 2.190.1 Scriptler 3.1 java version "1.8.0_221"
Priority:
Major
Reporter:
Robert Nitschke
I have some groovy scripts replacing German characters like 'ß' by '.' e.g.: directory.getName().replace('ß','.') Now since Scriptler plugin version 3.1 when editing those scripts I see '?' instead of 'ß' and after saving the scripts they are no more working because characters are replaced by invalid characters. I guess that files are encoded in ISO 8859-1 but now are intepreted as UTF-8. Finally going back to Scriptler plugin version 2.9 solved the problem.
Add Comment
