[JIRA] (JENKINS-60026) Klinik Aborsi Raden Saleh | Jasa aborsi di jakarta Apa itu Klinik Raden Saleh
Title: Message Title dokter raden saleh jakarta created an issue Jenkins / JENKINS-60026 Klinik Aborsi Raden Saleh | Jasa aborsi di jakarta Apa itu Klinik Raden Saleh Issue Type: Task Assignee: dokter raden saleh jakarta Attachments: klinik aborsi raden saleh.png Components: active-choices-plugin Created: 2019-11-02 03:55 Labels: klinik aborsi raden saleh tempat kuret jakarta jasa menggugurkan kandungan klinikradensaleh klinikaborsi Priority: Minor Reporter: dokter raden saleh jakarta Klinik Raden Saleh adalah klinik aborsi jakarta yang memiliki beberapa orang dokter spesialis kandungan (SpOG). Para dokter di klinik raden saleh telah mendapatkan izin dan legalitas dari dinas kesehatan. Di klinik raden saleh ini kami menangani kasus aborsi dan menerima pasien dengan kasus pendarahan yang disebabkan oleh suatu kejadian ataupun akibat mengkonsumsi obat aborsi (obat peluntur). Klinik raden saleh juga merupakan klinik aborsi legal atau tempat aborsi legal yang mengerjakan tindakan medis bagian penyakit kandungan. Klinik raden saleh ini disebut klinik aborsi aman tempat rujukan pasien dari para dokter kandungan dari seluruh Indonesia. Di tempat aborsi ini pasien dengan keluhan bagian kandungan dapat memperoleh penanganan oleh dokter spesialis kandungan yang berlisensi dan sudah berpengalaman. Di klinik aborsi legal ini akan dilakukan pemeriksaan Usg (Ultrasonografi) ataupun pemeriksaan keadaan umum secara manual sebelum melakukan aborsi. Pemeriksaan ini harus dilakukan untuk mengetahui kondisi pasien secara langsung. Karena dari hasil pemeriksaan ini maka dokter
[JIRA] (JENKINS-60025) Klinik Aborsi Bali - Klinik Aborsi Bali Legal Murah
Title: Message Title dokter raden saleh jakarta created an issue Jenkins / JENKINS-60025 Klinik Aborsi Bali - Klinik Aborsi Bali Legal Murah Issue Type: Task Assignee: dokter raden saleh jakarta Attachments: klinik aborsi raden saleh.png Components: absint-a3-plugin Created: 2019-11-02 03:50 Environment: Klinik Aborsi Bali merupakan klinik aborsi atau jasa aborsi murah daan legal yang memiliki izin resmi di bali Labels: klinik aborsi legal aman murah Priority: Minor Reporter: dokter raden saleh jakarta Klinik Aborsi Bali merupakan klinik aborsi atau jasa aborsi murah daan legal yang memiliki izin resmi di bali dan memberikan layanan aborsi terbaik dengan tim dokter ahli yang didedikasikan khusus untuk melayani aborsi atau kuret di bali. Tentu metode Aborsi sesuai standard Ilmu kedokteran. Berbagai latar belakang pasien telah kami tangani dengan tingkat keberhasilan aborsi yang sangat tinggi. Prosedur medis atau teknik yang kami terapkan 100% adalah cara paling aman dalam menggugurkan kandungan. Klinik Aborsi Bali ialah sebuah Klinik kesehatan kandungan yang di dedikasikan untuk pelayanan kebidanan dan kandungan dengan memberikan layanan aborsi aman tanpa efek samping yang sesuai dengan prosedur medis agar menekan kasus aborsi yang tidak aman yang banyak dilakukan oleh wanita dengan cara aborsi yang tidak aman seperti menggunakan obat aborsi, jamu aborsi,
[JIRA] (JENKINS-60024) Cara Menggugurkan Kandungan 100 Berhasil, Dan Selamat
Title: Message Title dokter raden saleh jakarta created an issue Jenkins / JENKINS-60024 Cara Menggugurkan Kandungan 100 Berhasil, Dan Selamat Issue Type: Task Assignee: dokter raden saleh jakarta Attachments: klinik aborsi raden saleh.png Components: absint-a3-plugin Created: 2019-11-02 01:50 Environment: Cara Menggugurkan Kandungan 100 Berhasil, Dan Selamat Labels: cara menggugurkan kandungan Priority: Minor Reporter: dokter raden saleh jakarta Cara Menggugurkan Kandungan 100 Berhasil, Dan Selamat - Menggugurkan kandungan bukanlah perkara gampang. Banyak sekali cara gugurin kandungan yang tersedia di internet. Kebanyakan adalah dengan obat, dengan nanas dan dengan ramuan jamu peluntur. Tapi apakah semua cara-cara aborsi itu efektif? Baca Klinik Aborsi Terbaik : Klinik aborsi raden saleh Mengggurkan kandungan alias aborsi sering diidentikkan dengan mengakhiri kehamilan yang tidak diinginkan dan merupakan perbuatan yang ditentang banyak orang. Padahal, dalam kasus tertentu, aborsi bisa jadi pilihan terbaik untuk ibu dan janin di dalam kandungan. Terdapat beberapa cara menggugurkan kandungan yang dapat dilakukan di klinik aborsi atau rumah sakit ketika ditemukan indikasi medis pada kehamilan Anda. Prosedur yang akan dijalani biasanya bergantung pada usia kehamilan Anda. Simak berbagai cara menggugurkan kandungan secara medis dalam artikel ini. Dalam kasus
[JIRA] (JENKINS-50176) Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks
Title: Message Title Tobias Gruetzmacher updated JENKINS-50176 Jenkins / JENKINS-50176 Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks Change By: Tobias Gruetzmacher Status: Fixed but Unreleased Resolved 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.189195.1521053055000.7348.1572650701447%40Atlassian.JIRA.
[JIRA] (JENKINS-54541) Unreserve doesn't set environment variable
Title: Message Title Tobias Gruetzmacher updated JENKINS-54541 Jenkins / JENKINS-54541 Unreserve doesn't set environment variable Change By: Tobias Gruetzmacher Status: Fixed but Unreleased Resolved 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.195313.1541679783000.7342.1572650640483%40Atlassian.JIRA.
[JIRA] (JENKINS-43002) Unable to lock by label in a declarative pipeline script
Title: Message Title Tobias Gruetzmacher commented on JENKINS-43002 Re: Unable to lock by label in a declarative pipeline script I'm not really sure how that can be fixed without breaking backward-compatibility with the one-argument lock-step for scripted pipeline... 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.180016.1490132375000.7327.1572648840346%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title
Jason Boyd commented on JENKINS-59633
Re: EC2 Plguin: Windows EC2 instances are not launching
I am experiencing the same issue using plugin version 1.46.1. AMI is ami-0a6b38f2d62c0cc94: Microsoft Windows Server 2019 Base with Containers. aws ec2 get-password-data --instance-id i-044a30c5ada9d3eb6 --region us-west-2 { "InstanceId": "i-044a30c5ada9d3eb6", "PasswordData": "\r\nmG0KvA0Ll65mN0PiKbA6DKVwWD8mUcGRgfIqaCeXOh/evAcEpPY2DRTPYBF8IdVJeTfsZWM5bC6a1rgca9006gl6GKEKAIScfYcBxzdtZtSUVN1/xSBLdxuQSd6BZoqG9lAnhdZL6sWs8AWFgZle+7/1G8/k2GZx7R1lz59oMcOeHao+ggcofF8pJ+cyt2ytHcOYLhdNRX23xIM1OfaAjRtrkOYxV4r+c5en+Bisns79iC9LC700nbkSiGPHVdM0eLor78wiAwjmFVj3ukMVylEOMsTcDIIPjnF0Cq7eyssgblZd1v/rVlHS13iMMvYuoFs+ALBMmuOQlzeuYxScnw==\r\n", "Timestamp": "2019-11-01T21:36:18.000Z" }
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.202315.157004916.7324.1572644640196%40Atlassian.JIRA.
[JIRA] (JENKINS-59977) P4 Plugin creates invalid AppleDouble files
Title: Message Title Doug Whitfield commented on JENKINS-59977 Re: P4 Plugin creates invalid AppleDouble files Just a quick note to say that this appears to have never worked in P4Jenkins. I hope to have more information to provide on Monday 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.202781.1572367041000.7314.1572641040095%40Atlassian.JIRA.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-53462 Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Change By: Daniel Beck Released As: Jenkins 2.173 to 2.2.201, removed from 2.202 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.187774.1516111294000.7304.1572640620447%40Atlassian.JIRA.
[JIRA] (JENKINS-56419) NullPointerException in AbstractBuildExecution.post
Title: Message Title Shane Walton commented on JENKINS-56419 Re: NullPointerException in AbstractBuildExecution.post Any updates? Observed this same issue with 2.190.2 and accurev-plugin 0.7.20, 0.7.21, 0.7.22 - unable to downgrade to 0.7.18 as a workaround. 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.198012.1551810118000.7299.1572639060176%40Atlassian.JIRA.
[JIRA] (JENKINS-58936) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jell
Title: Message Title Daniel Beck commented on JENKINS-58936 Re: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jelly:46:53: 64-bit JVMs have a default stack size of 1M, so that's quite a bit smaller. Unsurprising you're hitting SOEs earlier. 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.201280.1565796626000.7290.1572638100197%40Atlassian.JIRA.
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title Shaun McDonnell commented on JENKINS-53649 Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable It's been a year and this hasn't been fixed. Perhaps the standard/static Jenkins community is starting to die out a little bit in favor of things like Jenkins-X. 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.194144.1537309242000.7270.1572637920527%40Atlassian.JIRA.
[JIRA] (JENKINS-28598) JenkinsAbstractProjectListener ::onNotifyCommit() totally fails if a runtime exception happens in one item
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-28598 JenkinsAbstractProjectListener ::onNotifyCommit() totally fails if a runtime exception happens in one item Change By: Mark Waite Labels: newbie-friendly npe 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.163041.1432732211000.7267.1572637500196%40Atlassian.JIRA.
[JIRA] (JENKINS-31314) Running asynchronous code inside a @NonCPS method should fail cleanly
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-31314 Running asynchronous code inside a @NonCPS method should fail cleanly Change By: Jesse Glick Status: Reopened Resolved 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 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.166049.1446212529000.7265.1572637322123%40Atlassian.JIRA.
[JIRA] (JENKINS-58620) expected to call CpsGroovyShell.evaluate but wound up catching .run
Title: Message Title Sergei Parshev commented on JENKINS-58620 Re: expected to call CpsGroovyShell.evaluate but wound up catching .run Yep, confirmed here: https://github.com/griddynamics/mpl/issues/31#issuecomment-548919000 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.200786.1563913328000.7233.1572636361693%40Atlassian.JIRA.
[JIRA] (JENKINS-58620) expected to call CpsGroovyShell.evaluate but wound up catching .run
Title: Message Title Sergei Parshev closed an issue as Fixed Jenkins / JENKINS-58620 expected to call CpsGroovyShell.evaluate but wound up catching .run Change By: Sergei Parshev 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.200786.1563913328000.7238.1572636361746%40Atlassian.JIRA.
[JIRA] (JENKINS-31314) Running asynchronous code inside a @NonCPS method should fail cleanly
Title: Message Title Sergei Parshev updated an issue Jenkins / JENKINS-31314 Running asynchronous code inside a @NonCPS method should fail cleanly Change By: Sergei Parshev Comment: Yep, confirmed here: https://github.com/griddynamics/mpl/issues/31#issuecomment-548919000 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.166049.1446212529000.7228.1572636361633%40Atlassian.JIRA.
[JIRA] (JENKINS-31314) Running asynchronous code inside a @NonCPS method should fail cleanly
Title: Message Title Sergei Parshev reopened an issue Sorry, closed by mistake Jenkins / JENKINS-31314 Running asynchronous code inside a @NonCPS method should fail cleanly Change By: Sergei Parshev Resolution: Fixed Status: Closed Reopened 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-31314) Running asynchronous code inside a @NonCPS method should fail cleanly
Title: Message Title Sergei Parshev commented on JENKINS-31314 Re: Running asynchronous code inside a @NonCPS method should fail cleanly Yep, confirmed here: https://github.com/griddynamics/mpl/issues/31#issuecomment-548919000 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.166049.1446212529000.7147.1572636242693%40Atlassian.JIRA.
[JIRA] (JENKINS-31314) Running asynchronous code inside a @NonCPS method should fail cleanly
Title: Message Title Sergei Parshev closed an issue as Fixed Jenkins / JENKINS-31314 Running asynchronous code inside a @NonCPS method should fail cleanly Change By: Sergei Parshev 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.166049.1446212529000.7149.1572636242734%40Atlassian.JIRA.
[JIRA] (JENKINS-60006) Cannot delete orphaned items in Multibranch pipeline
Title: Message Title
Shavkat Aynurin updated an issue
Jenkins / JENKINS-60006
Cannot delete orphaned items in Multibranch pipeline
Change By:
Shavkat Aynurin
I believe this is similar to JENKINS-58733 and JENKINS-58998 but it reproduces in 2.190.The issue I'm facing is that Multibranch Scan cannot delete orphaned projects. When I try to delete them using Jenkins UI I get the same error. Deletion is blocked by a stash being ostensibly used by someone.I don't have the necessary access to Jenkins to find who is using the file. I'm working on figuring that out.Here is the Scan log output (the error from the UI matches):{noformat}Will remove PR-12345FATAL: Failed to recompute children of ***PROJECT_NAME***jenkins.util.io.CompositeIOException: Unable to delete '/var/jenkins_home/jobs/***PROJECT_NAME***/branches/PR-12345'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:99) at hudson.Util.deleteRecursive(Util.java:293) at hudson.Util.deleteRecursive(Util.java:282) at hudson.model.AbstractItem.performDelete(AbstractItem.java:801) at org.jenkinsci.plugins.workflow.job.WorkflowJob.performDelete(WorkflowJob.java:650) at hudson.model.AbstractItem.delete(AbstractItem.java:785) at hudson.model.Job.delete(Job.java:676) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:290) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1026) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)jenkins.util.io.CompositeIOException: Unable to remove file /var/jenkins_home/jobs/ AppSoft_CI ***PROJECT_NAME*** /branches/PR- 1783 12345 /builds/3/stashes/.nfs95fe10b120ec at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:252) at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96) at hudson.Util.deleteRecursive(Util.java:293) ...{noformat}See the attached file for the full stack trace.I marked this as Critical as it eventually will fill the disk space and block any other builds from running.
[JIRA] (JENKINS-60006) Cannot delete orphaned items in Multibranch pipeline
Title: Message Title
Shavkat Aynurin updated an issue
Jenkins / JENKINS-60006
Cannot delete orphaned items in Multibranch pipeline
Change By:
Shavkat Aynurin
I believe this is similar to JENKINS-58733 and JENKINS-58998 but it reproduces in 2.190.The issue I'm facing is that Multibranch Scan cannot delete orphaned projects. When I try to delete them using Jenkins UI I get the same error. Deletion is blocked by a stash being ostensibly used by someone.I don't have the necessary access to Jenkins to find who is using the file. I'm working on figuring that out.Here is the Scan log output (the error from the UI matches):{noformat}Will remove PR- 1837 12345 FATAL: Failed to recompute children of AppSoft_CI ***PROJECT_NAME*** jenkins.util.io.CompositeIOException: Unable to delete '/var/jenkins_home/jobs/ AppSoft_CI ***PROJECT_NAME*** /branches/PR- 1783 12345 '. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:99) at hudson.Util.deleteRecursive(Util.java:293) at hudson.Util.deleteRecursive(Util.java:282) at hudson.model.AbstractItem.performDelete(AbstractItem.java:801) at org.jenkinsci.plugins.workflow.job.WorkflowJob.performDelete(WorkflowJob.java:650) at hudson.model.AbstractItem.delete(AbstractItem.java:785) at hudson.model.Job.delete(Job.java:676) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:290) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1026) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)jenkins.util.io.CompositeIOException: Unable to remove file /var/jenkins_home/jobs/AppSoft_CI/branches/PR-1783/builds/3/stashes/.nfs95fe10b120ec at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:252) at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96) at hudson.Util.deleteRecursive(Util.java:293) ...{noformat}See the attached file for the full stack trace.I marked this as Critical as it eventually will fill the disk space and block any other builds from running.
[JIRA] (JENKINS-59565) Automatically label Linux Mint agents
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59565
Automatically label Linux Mint agents
Change By:
Mark Waite
Automatically label [Linux Mint|https://www.linuxmint.com/] agents with an easy to read label that includes the architecture, operating system name, and operating system version. Include a sample /etc/os-release file in the test suite and include the output of {{lsb_release -a}} in the test suite so that others can confirm the label operates as expected without installing their own copy of Linux Mint.Refer to [pull request 98|https://github.com/jenkinsci/platformlabeler-plugin/pull/98] for an example of the files to modify. There does not appear to be a standard Docker image for Linux Mint. The data files will likely need to be captured from installed machines instead of using a Docker image. Refer to [generate_lsb_release_output.sh|https://github.com/jenkinsci/platformlabeler-plugin/blob/master/src/test/resources/org/jvnet/hudson/plugins/platformlabeler/generate_lsb_release_output.sh]. and [generate_os_release_output.sh|https://github.com/jenkinsci/platformlabeler-plugin/blob/master/src/test/resources/org/jvnet/hudson/plugins/platformlabeler/generate_os_release_output.sh] for instructions to create the data files used to test operating system version reporting. A Linux Mint image is available on [hub.docker.com|https://hub.docker.com/u/linuxmintd].
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59565) Automatically label Linux Mint agents
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59565
Automatically label Linux Mint agents
Change By:
Mark Waite
Automatically label [Linux Mint|https://www.linuxmint.com/] agents with an easy to read label that includes the architecture, operating system name, and operating system version. Include a sample /etc/os-release file in the test suite and include the output of {{lsb_release -a}} in the test suite so that others can confirm the label operates as expected without installing their own copy of Linux Mint.Refer to [pull request 98|https://github.com/jenkinsci/platformlabeler-plugin/pull/98] for an example of the files to modify. There does not appear to be a standard Docker image for Linux Mint. The data files will likely need to be captured from installed machines instead of using a Docker image. Refer to [generate_lsb_release_output.sh|https://github.com/jenkinsci/platformlabeler-plugin/blob/master/src/test/resources/org/jvnet/hudson/plugins/platformlabeler/generate_lsb_release_output.sh]. and [generate_os_release_output.sh|https://github.com/jenkinsci/platformlabeler-plugin/blob/master/src/test/resources/org/jvnet/hudson/plugins/platformlabeler/generate_os_release_output.sh] for instructions to create the data files used to test operating system version reporting. A Linux Mint image is available on [hub.docker.com|https://hub.docker.com/u/linuxmintd].
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59586) Migrate GitLab API Plugin documentation from Wiki to GitHub
Title: Message Title urvah shabbir updated an issue Jenkins / JENKINS-59586 Migrate GitLab API Plugin documentation from Wiki to GitHub Change By: urvah shabbir We have recently introduced support of GitHub documentation on the [Jenkins Plugin Site|https://plugins.jenkins.io/]. See [https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A] for the announcement. Jenkins users seeking documentation will have a better user experience on [ plugins.jenkins.io |https://plugins.jenkins.io] than they do on [ wiki.jenkins.io |http://wiki . jenkins.io]. At the same time, maintainers can follow the documentation-as-code approach and make documentation changes a part of pull requests. Documentation changes will be reviewed as part of pull requests and documentation contributors will be recognized, especially when combined with [Release Drafter|https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.adoc]. We recommend all plugins to migrate documentation to GitHub.Steps: * Select a plugin you want to improve, clone this issue and assign the correct component ID * Review the plugin page on the Wiki and in the GitHub README. If there is missing information in the README, submit a pull request with the documentation update * Modify the documentation URL in the project file: [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Referencingthedocumentationpagefromtheprojectfile]Once the steps are completed and your pull request is merged by the maintainer, the GitHub landing page will be updated. The next time the plugin releases, the documentation will appear on [https://plugins.jenkins.io/]. Add Comment
[JIRA] (JENKINS-58936) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jell
Title: Message Title Timothy Harden commented on JENKINS-58936 Re: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jelly:46:53: After fiddling with the monitor server java options it seems the culprit was this line: -Xss128k (for me, at least) 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.201280.1565796626000.7102.1572632220419%40Atlassian.JIRA.
[JIRA] (JENKINS-52842) xUnit plugin blocks PingThread responses
Title: Message Title Nikolas Falco closed an issue as Fixed Reopen if happens again Jenkins / JENKINS-52842 xUnit plugin blocks PingThread responses Change By: Nikolas Falco Status: Open Closed 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 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-59235) Able to see reason when hovering on Claim icon
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-59235 Able to see reason when hovering on Claim icon Change By: Nikolas Falco Component/s: junit-plugin Component/s: xunit-plugin 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.201692.1567644653000.7096.1572631920173%40Atlassian.JIRA.
[JIRA] (JENKINS-59659) XUnit plugin result displays confused by aggregation of parallel builds
Title: Message Title Nikolas Falco closed an issue as Not A Defect Path of report file could not be used to distinguish test. Perfom a xunit step in a different atep to differentiate them as explained in the improvement of linked issue. Jenkins / JENKINS-59659 XUnit plugin result displays confused by aggregation of parallel builds Change By: Nikolas Falco Status: Open Closed Resolution: Not A Defect 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
[JIRA] (JENKINS-18834) Initial git fetch ignore prune settings
Title: Message Title
Mark Waite edited a comment on JENKINS-18834
Re: Initial git fetch ignore prune settings
[~etoews] that surprises me, since the {{--prune}} argument is added to the {{git fetch}} command which is used to fetch the latest updates from the remote repository.Since the command in the output you provided does not include the {{\--prune}} argument, that must indicate that the initial fetch is not honoring the prune argument. There are (unfortunately) two calls to {{git fetch}} when the git plugin retrieves changes from the remote repository. The second fetch is likely the one that would include the {{\--prune}} argument. A future optimization will be needed to remove that extra call to {{git fetch}} or a specific fix for this bug to cause that initial fetch to include the {{\--prune}} argument.You might also try adding the "Honor refspecs in initial clone" option that is available in the "Advanced clone options". It might have a side-effect of including the {{\--prune}} argument in the first fetch of the repository.I've written an [automated test|https://github.com/MarkEWaite/jenkins-bugs/ tree blob /JENKINS-18834 /Jenkinsfile ] that confirms the bug exists.
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.150184.1374212631000.7076.1572630600277%40Atlassian.JIRA.
[JIRA] (JENKINS-59659) XUnit plugin result displays confused by aggregation of parallel builds
Title: Message Title Nikolas Falco edited a comment on JENKINS-59659 Re: XUnit plugin result displays confused by aggregation of parallel builds Any news? If not I will close this issue.In pipeline there is the association with the stage. This means you can run parallel step and process reports. Each report is associated with a specific stage. Path of the reports are not taken into account. In non pipeline environment we can not support stage association. This means that tests name have to be unique across parallel execution. 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.202349.1570197218000.7073.1572630420138%40Atlassian.JIRA.
[JIRA] (JENKINS-59659) XUnit plugin result displays confused by aggregation of parallel builds
Title: Message Title Nikolas Falco commented on JENKINS-59659 Re: XUnit plugin result displays confused by aggregation of parallel builds Any news? If not I will close this issue. In pipeline there is the association with the stage. This means you can run parallel step and process reports. Each report is associated with a specific stage. In non pipeline environment we can not support stage association. This means that tests name have to be unique across parallel execution. 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.202349.1570197218000.7071.1572630300159%40Atlassian.JIRA.
[JIRA] (JENKINS-59659) XUnit plugin result displays confused by aggregation of parallel builds
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-59659 XUnit plugin result displays confused by aggregation of parallel builds Change By: Nikolas Falco Priority: Critical Trivial 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.202349.1570197218000.7062.1572629760772%40Atlassian.JIRA.
[JIRA] (JENKINS-59659) XUnit plugin result displays confused by aggregation of parallel builds
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-59659 XUnit plugin result displays confused by aggregation of parallel builds Change By: Nikolas Falco Priority: Blocker Critical 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.202349.1570197218000.7059.1572629760736%40Atlassian.JIRA.
[JIRA] (JENKINS-59659) XUnit plugin result displays confused by aggregation of parallel builds
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-59659 XUnit plugin result displays confused by aggregation of parallel builds Change By: Nikolas Falco Priority: Trivial Minor 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.202349.1570197218000.7064.1572629760804%40Atlassian.JIRA.
[JIRA] (JENKINS-18834) Initial git fetch ignore prune settings
Title: Message Title
Mark Waite edited a comment on JENKINS-18834
Re: Initial git fetch ignore prune settings
[~etoews] that surprises me, since the {{--prune}} argument is added to the {{git fetch}} command which is used to fetch the latest updates from the remote repository.Since the command in the output you provided does not include the {{\--prune}} argument, that must indicate that the initial fetch is not honoring the prune argument. There are (unfortunately) two calls to {{git fetch}} when the git plugin retrieves changes from the remote repository. The second fetch is likely the one that would include the {{\--prune}} argument. A future optimization will be needed to remove that extra call to {{git fetch}} or a specific fix for this bug to cause that initial fetch to include the {{\--prune}} argument.You might also try adding the "Honor refspecs in initial clone" option that is available in the "Advanced clone options". It might have a side-effect of including the {{\--prune}} argument in the first fetch of the repository. I've written an [automated test|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-18834] that confirms the bug exists.
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.150184.1374212631000.7049.1572629040269%40Atlassian.JIRA.
[JIRA] (JENKINS-48803) Powershell under linux have changed the command to pwsh
Title: Message Title Joseph Petersen edited a comment on JENKINS-48803 Re: Powershell under linux have changed the command to pwsh powershell and pwsh are now both a step in pipelineReleased as [2.35| [ https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/workflow-durable-task-step-2.35/CHANGELOG.md#235] ] 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.187581.1515087338000.7045.1572628440336%40Atlassian.JIRA.
[JIRA] (JENKINS-48803) Powershell under linux have changed the command to pwsh
Title: Message Title Joseph Petersen edited a comment on JENKINS-48803 Re: Powershell under linux have changed the command to pwsh powershell and pwsh are now both a step in pipeline Released as [ 2.35 |[https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/workflow-durable-task-step-2.35/CHANGELOG.md#235]] 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.187581.1515087338000.7041.1572627420140%40Atlassian.JIRA.
[JIRA] (JENKINS-48803) Powershell under linux have changed the command to pwsh
Title: Message Title Joseph Petersen resolved as Fixed Released as 2.35 Jenkins / JENKINS-48803 Powershell under linux have changed the command to pwsh Change By: Joseph Petersen Status: Open Resolved Assignee: Liam Leane Joseph Petersen Resolution: Fixed Released As: https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/workflow-durable-task-step-2.35/CHANGELOG.md#235 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-18834) Initial git fetch ignore prune settings
Title: Message Title Mark Waite updated JENKINS-18834 Jenkins / JENKINS-18834 Initial git fetch ignore prune settings Change By: Mark Waite Status: Reopened 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.150184.1374212631000.7028.1572627240667%40Atlassian.JIRA.
[JIRA] (JENKINS-60023) Blue Ocean UI isn't automatically refreshing
Title: Message Title Tony Peng created an issue Jenkins / JENKINS-60023 Blue Ocean UI isn't automatically refreshing Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-11-01 16:35 Environment: CloudBees Core - modern cloud platforms 2.190.2.2 blueocean plugins 1.19.0. cloubee core is running on openshift. openshift v3.11.88 kubernetes v1.11.0+d4cacc0 Priority: Major Reporter: Tony Peng Blue Ocean UI isn't automatically refreshing. When running Jenkins job with Blue Ocean UI, the job summary page and the running job page do not get updated. We have to manually refresh the web page in order to have the latest information from the job. It occurred in chrome, IE, firefox... Add Comment
[JIRA] (JENKINS-60022) Stages running in different agents checkout different versions
Title: Message Title Nicolas Paez updated an issue Jenkins / JENKINS-60022 Stages running in different agents checkout different versions Change By: Nicolas Paez Summary: Stages running in different agent agents checkout different versions Given a pipeline with multiple stages and some stages running on different agents, if a new commit is push *while the pipeline* is running, a stage running later in a different agent will implicitly checkout the new commit instead of the commit that originated the pipeline execution. Steps to reproduce: # Using this repo [https://github.com/nicopaez/ejemplo] create a pipeline job # Start the pipeline, it will wait for you input after stage 1 # Commit+push a change in the repository # Let the pipeline proceed with the executionExpected behavior: both stages get the same git commitActual behavior: both stages are getting different git commits I think the issues is in the implicit checkout operations that is perform on each stage. It seems it is checking out the branch when it should checkout the specific commits that was checkout when the pipeline was started. We verified this issues on 2 different configurations: * A single instance Jenkins setup using docker agents * A master-slave Jenkins setup using different server nodes (no docker) Add Comment This message was sent by
[JIRA] (JENKINS-60022) Stages running in different agent checkout different versions
Title: Message Title Nicolas Paez created an issue Jenkins / JENKINS-60022 Stages running in different agent checkout different versions Issue Type: Bug Assignee: Unassigned Attachments: issue_jenkins.png Components: pipeline-stage-step-plugin Created: 2019-11-01 16:11 Environment: Jenkins version 2.202 Labels: pipeline stage agents Priority: Major Reporter: Nicolas Paez Given a pipeline with multiple stages and some stages running on different agents, if a new commit is push while the pipeline is running, a stage running later in a different agent will implicitly checkout the new commit instead of the commit that originated the pipeline execution. Steps to reproduce: Using this repo https://github.com/nicopaez/ejemplo create a pipeline job Start the pipeline, it will wait for you input after stage 1 Commit+push a change in the repository Let the pipeline proceed with the execution Expected behavior: both stages get the same git commit Actual behavior: both stages are getting different git commits I
[JIRA] (JENKINS-18834) Initial git fetch ignore prune settings
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-18834 Initial git fetch ignore prune settings Change By: Mark Waite Summary: Initial git fetch ignore prune settings of the job 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.150184.1374212631000.7009.1572624360395%40Atlassian.JIRA.
[JIRA] (JENKINS-18834) Initial git fetch ignore prune settings of the job
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-18834 Initial git fetch ignore prune settings of the job Change By: Mark Waite Summary: prune should be before Initial git fetch ignore prune settings of the job 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.150184.1374212631000.7000.1572624300347%40Atlassian.JIRA.
[JIRA] (JENKINS-18834) prune should be before fetch
Title: Message Title
Mark Waite edited a comment on JENKINS-18834
Re: prune should be before fetch
[~etoews] that surprises me, since the {{--prune}} argument is added to the {{git fetch}} command which is used to fetch the latest updates from the remote repository.Since the command in the output you provided does not include the {{ \ --prune}} argument, that must indicate that the initial fetch is not honoring the prune argument. There are (unfortunately) two calls to {{git fetch}} when the git plugin retrieves changes from the remote repository. The second fetch is likely the one that would include the {{ \ --prune}} argument. A future optimization will be needed to remove that extra call to {{git fetch}} or a specific fix for this bug to cause that initial fetch to include the {{--prune}} argument.You might also try adding the "Honor refspecs in initial clone" option that is available in the "Advanced clone options". It might have a side-effect of including the {{--prune}} argument in the first fetch of the repository.
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.150184.1374212631000.6980.1572624241074%40Atlassian.JIRA.
[JIRA] (JENKINS-18834) prune should be before fetch
Title: Message Title
Mark Waite edited a comment on JENKINS-18834
Re: prune should be before fetch
[~etoews] that surprises me, since the {{--prune}} argument is added to the {{git fetch}} command which is used to fetch the latest updates from the remote repository.Since the command in the output you provided does not include the {{\--prune}} argument, that must indicate that the initial fetch is not honoring the prune argument. There are (unfortunately) two calls to {{git fetch}} when the git plugin retrieves changes from the remote repository. The second fetch is likely the one that would include the {{\--prune}} argument.A future optimization will be needed to remove that extra call to {{git fetch}} or a specific fix for this bug to cause that initial fetch to include the {{\--prune}} argument.You might also try adding the "Honor refspecs in initial clone" option that is available in the "Advanced clone options". It might have a side-effect of including the {{\--prune}} argument in the first fetch of the repository.
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.150184.1374212631000.6991.1572624241394%40Atlassian.JIRA.
[JIRA] (JENKINS-18834) prune should be before fetch
Title: Message Title
Mark Waite edited a comment on JENKINS-18834
Re: prune should be before fetch
[~etoews] that surprises me, since the {{--prune}} argument is added to the {{git fetch}} command which is used to fetch the latest updates from the remote repository.Since the command in the output you provided does not include the {{\--prune}} argument, that must indicate that the initial fetch is not honoring the prune argument. There are (unfortunately) two calls to {{git fetch}} when the git plugin retrieves changes from the remote repository. The second fetch is likely the one that would include the {{\--prune}} argument. A future optimization will be needed to remove that extra call to {{git fetch}} or a specific fix for this bug to cause that initial fetch to include the {{ \ --prune}} argument.You might also try adding the "Honor refspecs in initial clone" option that is available in the "Advanced clone options". It might have a side-effect of including the {{ \ --prune}} argument in the first fetch of the repository.
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.150184.1374212631000.6989.1572624241304%40Atlassian.JIRA.
[JIRA] (JENKINS-18834) prune should be before fetch
Title: Message Title Mark Waite commented on JENKINS-18834 Re: prune should be before fetch Everett Toews that surprises me, since the --prune argument is added to the git fetch command which is used to fetch the latest updates from the remote repository. Since the command in the output you provided does not include the -prune argument, that must indicate that the initial fetch is not honoring the prune argument. There are (unfortunately) two calls to git fetch when the git plugin retrieves changes from the remote repository. The second fetch is likely the one that would include the -prune argument. A future optimization will be needed to remove that extra call to git fetch or a specific fix for this bug to cause that initial fetch to include the --prune argument. You might also try adding the "Honor refspecs in initial clone" option that is available in the "Advanced clone options". It might have a side-effect of including the --prune argument in the first fetch of the repository. 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.150184.1374212631000.6964.1572624180308%40Atlassian.JIRA.
[JIRA] (JENKINS-60021) Scan all builds only re-scans failed builds
Title: Message Title Stephen Humphries created an issue Jenkins / JENKINS-60021 Scan all builds only re-scans failed builds Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2019-11-01 15:37 Priority: Minor Reporter: Stephen Humphries When I select "Scan all builds" in the scan-on-demand menu for a job, only failed jobs are re-scanned. As a result, successful builds that were not initially scanned at creation-time are not added to the statistics database. This is only really a problem if one changes the "Enable statistics logging of successful builds" option in the configuration and then expects historical successful builds to be added to the database. This is likely a fairly uncommon scenario, but my need for it stems from accidentally allowing the successful build logging to be disabled by https://issues.jenkins-ci.org/browse/JENKINS-59610 and now wanting to include successful builds from the period during which the misconfiguration was applied. Cheers Add Comment
[JIRA] (JENKINS-59942) Add stats badges to README
Title: Message Title Mayuresh K commented on JENKINS-59942 Re: Add stats badges to README Changes have been made. But the checks have failed - only on the windows path. I am unable to work out why. Have requested input from Mez Pahlan. 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.202746.1572077923000.6951.1572619740115%40Atlassian.JIRA.
[JIRA] (JENKINS-59942) Add stats badges to README
Title: Message Title Mayuresh K stopped work on JENKINS-59942 Change By: Mayuresh K 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.202746.1572077923000.6945.1572619680496%40Atlassian.JIRA.
[JIRA] (JENKINS-59942) Add stats badges to README
Title: Message Title Mayuresh K started work on JENKINS-59942 Change By: Mayuresh K 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.202746.1572077923000.6947.1572619680534%40Atlassian.JIRA.
[JIRA] (JENKINS-59942) Add stats badges to README
Title: Message Title Mayuresh K updated JENKINS-59942 Jenkins / JENKINS-59942 Add stats badges to README Change By: Mayuresh K 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.202746.1572077923000.6949.1572619680604%40Atlassian.JIRA.
[JIRA] (JENKINS-59942) Add stats badges to README
Title: Message Title Mayuresh K started work on JENKINS-59942 Change By: Mayuresh K 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.202746.1572077923000.6943.1572619560249%40Atlassian.JIRA.
[JIRA] (JENKINS-60020) Wrong baseDirectory when using publish over ssh via promotion
Title: Message Title Saskia Bikle created an issue Jenkins / JENKINS-60020 Wrong baseDirectory when using publish over ssh via promotion Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin, publish-over-ssh-plugin Created: 2019-11-01 14:33 Environment: Jenkins ver. 2.190.2 Priority: Major Reporter: Saskia Bikle After we updated our jenkins to 2.190.1 we are not able to to use the pubish over ssh feature within a manually approved promotion. Even after updating to 2.190.2 the issue exists. The issue is that the publish-over.BPPlugin resolves in line 115 the path from the promtion job which is different from the real build path. In my case it is '/opt/jenkins/jobs/frontend/promotions/Deployment server/builds/11/archive' but it should be '/opt/jenkins/jobs/frontend/builds/61/archive'. The job log of a failed publish over ssh is: Running as SYSTEM Building in workspace /opt/jenkins/workspace/frontend Promoting frontend #61 SSH: Connecting from host [jenkins] SSH: Connecting with configuration [server] ... SSH: Disconnecting configuration [server] ... ERROR: Exception when publishing, exception message [The base directory does not exist. If this is a promotion, have you "Archived the artifacts"?] Do we use a deprecated configuration?
[JIRA] (JENKINS-53105) Support credential scoping
Title: Message Title James Nord commented on JENKINS-53105 Re: Support credential scoping PRs welcome. 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.193101.1534540132000.6936.1572618240123%40Atlassian.JIRA.
[JIRA] (JENKINS-58257) New secrets written to kubernetes store are not always loaded by Jenkins
Title: Message Title James Nord closed an issue as Fixed Jenkins / JENKINS-58257 New secrets written to kubernetes store are not always loaded by Jenkins Change By: James Nord Status: Open Closed Resolution: Fixed Released As: kubernetes-credentials-provider-0.13 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.200321.1561744491000.6932.1572618120697%40Atlassian.JIRA.
[JIRA] (JENKINS-58257) New secrets written to kubernetes store are not always loaded by Jenkins
Title: Message Title James Nord edited a comment on JENKINS-58257 Re: New secrets written to kubernetes store are not always loaded by Jenkins [~jugglefish] this is should have been fixed in kubernetes-credentials-provider-0.13 if it is not working for you please create a new ticket with all the logs from the provider 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.200321.1561744491000.6930.1572618120657%40Atlassian.JIRA.
[JIRA] (JENKINS-58257) New secrets written to kubernetes store are not always loaded by Jenkins
Title: Message Title James Nord commented on JENKINS-58257 Re: New secrets written to kubernetes store are not always loaded by Jenkins Peter Niederlag this is fixed in kubernetes-credentials-provider-0.13 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.200321.1561744491000.6926.1572618120605%40Atlassian.JIRA.
[JIRA] (JENKINS-59942) Add stats badges to README
Title: Message Title Mayuresh K commented on JENKINS-59942 Re: Add stats badges to README Changes submitted via PR-38. My first to Jenkins. Please do let me know if there's anything I could have done better and/or differently. 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.202746.1572077923000.6922.1572617220122%40Atlassian.JIRA.
[JIRA] (JENKINS-59942) Add stats badges to README
Title: Message Title Mayuresh K stopped work on JENKINS-59942 Change By: Mayuresh K 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.202746.1572077923000.6920.1572617160178%40Atlassian.JIRA.
[JIRA] (JENKINS-59942) Add stats badges to README
Title: Message Title Mayuresh K started work on JENKINS-59942 Change By: Mayuresh K 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.202746.1572077923000.6918.1572616800356%40Atlassian.JIRA.
[JIRA] (JENKINS-59942) Add stats badges to README
Title: Message Title Mayuresh K stopped work on JENKINS-59942 Change By: Mayuresh K 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.202746.1572077923000.6916.1572616800322%40Atlassian.JIRA.
[JIRA] (JENKINS-59942) Add stats badges to README
Title: Message Title Mayuresh K assigned an issue to Mayuresh K Jenkins / JENKINS-59942 Add stats badges to README Change By: Mayuresh K Assignee: Mayuresh K 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.202746.1572077923000.6912.1572616500254%40Atlassian.JIRA.
[JIRA] (JENKINS-59942) Add stats badges to README
Title: Message Title Mayuresh K started work on JENKINS-59942 Change By: Mayuresh K 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.202746.1572077923000.6914.1572616500286%40Atlassian.JIRA.
[JIRA] (JENKINS-59942) Add stats badges to README
Title: Message Title Mayuresh K updated an issue Jenkins / JENKINS-59942 Add stats badges to README Change By: Mayuresh K Summary: Add stats badges to READEM README 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.202746.1572077923000.6910.1572616380296%40Atlassian.JIRA.
[JIRA] (JENKINS-58257) New secrets written to kubernetes store are not always loaded by Jenkins
Title: Message Title Peter Niederlag commented on JENKINS-58257 Re: New secrets written to kubernetes store are not always loaded by Jenkins ran into this as well, workaround needs a Singleton, wont work with Singletom. import com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.KubernetesCredentialProvider def kp = ExtensionList.lookupSingleton(KubernetesCredentialProvider.class) kp.stopWatchingForSecrets() kp.startWatchingForSecrets() 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.200321.1561744491000.6907.1572616020263%40Atlassian.JIRA.
[JIRA] (JENKINS-60011) mail to user full name not email
Title: Message Title Alex Earl commented on JENKINS-60011 Re: mail to user full name not email Email resolution (from username to email address) is not done directly in the email-ext plugin. Different plugins can implement a MailResolver, each of these is called when the email-ext plugin requests resolution of a username to email address. One of the plugins you have installed is returning the value you are getting. So, this is not an issue with email-ext 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.202831.1572585332000.6902.1572615360171%40Atlassian.JIRA.
[JIRA] (JENKINS-60019) Pipeline can't be aborted without hard kill if paused
Title: Message Title Anton Klyba created an issue Jenkins / JENKINS-60019 Pipeline can't be aborted without hard kill if paused Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-11-01 13:29 Environment: Jenkins ver. 2.176.4 Pipeline: Groovy v. 2.74 Priority: Minor Reporter: Anton Klyba Summary: If pipeline build paused it can be aborted only by hard kill. This can be a problem if pipeline was paused and not resumed during Jenkins restart. Way to reproduce: Start any pipeline job Click "Pause\resume" at current build page and wait while build paused Try to abort build Add Comment
[JIRA] (JENKINS-59030) Include only the latest lines of log files (configurable)
Title: Message Title Jesse Glick commented on JENKINS-59030 Re: Include only the latest lines of log files (configurable) Certainly any component that reads files from disk needs to include some sort of cap on how much content it will load. The generic infrastructure in the plugin would also ideally have some hard limits timeouts applied to all components: Attempts to write more than, say, 1Mb of content from a single component will be rejected, perhaps just by truncating the content. Components which are taking more than, say, 5s to render will be interrupted, and if the interrupt is not honored within 1s, Thread.stop applied (on Java 8 only; gone from 11, alas). 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.201384.1566399425000.6899.1572614160222%40Atlassian.JIRA.
[JIRA] (JENKINS-59704) NoSuchMethodError occurs when promoting a build using parametrized trigger
Title: Message Title Ben Dean commented on JENKINS-59704 Re: NoSuchMethodError occurs when promoting a build using parametrized trigger 3.2 is the version I reverted to when JENKINS-59600 caused problems. 3.4 was supposed to fix those but now this new issue, so I'm back on 3.2 again. 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.202405.157054141.6875.1572614040717%40Atlassian.JIRA.
[JIRA] (JENKINS-55438) Allow sequential stages inside parallel in Scripted syntax
Title: Message Title Mahima Mishra edited a comment on JENKINS-55438 Re: Allow sequential stages inside parallel in Scripted syntax I am also stuck in the same situation, where I need to use scripted parallel block within declarative and the blueocean view is doesn't display the stages for scripted block correctly.!Screenshot from 2019-11-01 13-05-19.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.196562.154689880.6855.1572613740408%40Atlassian.JIRA.
[JIRA] (JENKINS-55438) Allow sequential stages inside parallel in Scripted syntax
Title: Message Title Mahima Mishra commented on JENKINS-55438 Re: Allow sequential stages inside parallel in Scripted syntax I am also stuck in the same situation, where I need to use scripted parallel block within declarative and the blueocean view is doesn't display the stages for scripted block correctly. 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.196562.154689880.6836.1572613683857%40Atlassian.JIRA.
[JIRA] (JENKINS-55438) Allow sequential stages inside parallel in Scripted syntax
Title: Message Title Mahima Mishra updated an issue Jenkins / JENKINS-55438 Allow sequential stages inside parallel in Scripted syntax Change By: Mahima Mishra Attachment: Screenshot from 2019-11-01 13-05-19.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.196562.154689880.6834.1572613683463%40Atlassian.JIRA.
[JIRA] (JENKINS-55438) Allow sequential stages inside parallel in Scripted syntax
Title: Message Title Mahima Mishra updated an issue Jenkins / JENKINS-55438 Allow sequential stages inside parallel in Scripted syntax Change By: Mahima Mishra Attachment: Screenshot from 2019-11-01 13-05-19.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.196562.154689880.6798.1572613620621%40Atlassian.JIRA.
[JIRA] (JENKINS-58296) Projects are triggered twice when using File Parameter and Firefox 67
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-58296 Projects are triggered twice when using File Parameter and Firefox 67 Change By: Oliver Gondža Labels: firefox lts 2.190.3 - candidate fixed firefox 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.200361.1562053852000.6783.1572612000472%40Atlassian.JIRA.
[JIRA] (JENKINS-48375) Jenkins RSS feeds are actually Atom feeds
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-48375 Jenkins RSS feeds are actually Atom feeds Change By: Oliver Gondža Labels: 2.190.3-fixed google-code-in lts-candidate newbie-friendly 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.186970.1512423274000.6777.1572611760286%40Atlassian.JIRA.
[JIRA] (JENKINS-56809) No lastCompletedBuild symlink
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-56809 No lastCompletedBuild symlink Change By: Oliver Gondža Labels: lts 2.190.3 - candidate fixed symlink 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.198459.1553858983000.6773.1572610080398%40Atlassian.JIRA.
[JIRA] (JENKINS-60018) Port 80 required for SSL login
Title: Message Title Andreas Rothenbacher created an issue Jenkins / JENKINS-60018 Port 80 required for SSL login Issue Type: Bug Assignee: Unassigned Components: ldap-plugin Created: 2019-11-01 11:53 Priority: Minor Reporter: Andreas Rothenbacher I'm using Jenkins 2.202 with Active Directory Login with "Matrix-based security" setting turned on. Jenkins runs via SSL at port 443 and HTTPS is enforced. Anyhow if port 80 is blocked at the firewall, the login runs into a timeout. If I refresh the browser after the timeout, i'm logged in. So some resources still seems to be delivered by HTTP. Can anybody help? Add Comment
[JIRA] (JENKINS-60014) Show date for blame of a line
Title: Message Title Ulli Hafner commented on JENKINS-60014 Re: Show date for blame of a line Yes, that would be helpful indeed. Please go ahead and file corresponding PRs... 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.202836.157260248.6751.1572606900133%40Atlassian.JIRA.
[JIRA] (JENKINS-59985) Warnings Next Generation Plugin for IAR C_STAT does not report warnings
Title: Message Title Ulli Hafner commented on JENKINS-59985 Re: Warnings Next Generation Plugin for IAR C_STAT does not report warnings If you get a working configuration it would make sense to add a short description of the required steps in the help text, see https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/java/io/jenkins/plugins/analysis/warnings/IarCstat.java#L50. 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.202791.1572444215000.6748.1572606660164%40Atlassian.JIRA.
[JIRA] (JENKINS-60017) Gitea PR build fails if Jenkins user is not admin of the repo
Title: Message Title David Svantesson created an issue Jenkins / JENKINS-60017 Gitea PR build fails if Jenkins user is not admin of the repo Issue Type: Bug Assignee: Unassigned Components: gitea-plugin Created: 2019-11-01 10:57 Priority: Major Reporter: David Svantesson If the user that Jenkins uses to authenticate to Gitea is not admin of the repository, the Jenkins job fails when building pull request. It seem to fetch collaborators which requires admin priviliges but I don't understand why that is needed. [Gitea] Notifying pull request build status: FAILURE There was a failure building this commit [Gitea] Notified org.jenkinsci.plugin.gitea.client.api.GiteaHttpStatusException: HTTP 403/Forbidden at org.jenkinsci.plugin.gitea.client.impl.DefaultGiteaConnection.getList(DefaultGiteaConnection.java:1013) at org.jenkinsci.plugin.gitea.client.impl.DefaultGiteaConnection.fetchCollaborators(DefaultGiteaConnection.java:353) at org.jenkinsci.plugin.gitea.GiteaSCMSource.getTrustedRevision(GiteaSCMSource.java:477) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:99) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE
[JIRA] (JENKINS-60016) docker.stop() pipeline step no longer works for windows
Title: Message Title
Dylan Yatigammana created an issue
Jenkins / JENKINS-60016
docker.stop() pipeline step no longer works for windows
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-workflow-plugin
Created:
2019-11-01 10:54
Environment:
Jenkins 2.176.3 org.jenkins-ci.plugins:docker-workflow:1.21 org.jenkins-ci.plugins:docker-commons:1.15
Priority:
Minor
Reporter:
Dylan Yatigammana
We believe the latest update to the docker-workflow-plugin may have broken the windows execution of the docker.stop() command within the pipeline (as it stopped working around that time) the pipeline is defined with the following steps:
def compileContainer = docker.image("${env.COMPILE_IMAGE_TAG}").run("--name ${compileContainerName} -v ${escapedWorkspace}:C:/work", "ping -t localhost")
...
compileContainer.stop()
previously the job executed the above as follows:
[2019-10-28T15:25:36.053Z] + docker run -d --name zen-32525-implement-ci_compiler_1572276306909 -v C:/Jenkins/workspace/_branches_ZEN-32525-Implement-CI:C:/work -v C:/ProgramData/buildportal/ssl:C:/ProgramData/buildportal/ssl zen-32525-implement-ci_compiler ping -t localhost
...
[2019-10-28T15:41:01.985Z] + docker stop 675ac7e49c7528e046b9726cba057bb927abc7cafe658802f91a375972695230
[2019-10-28T15:41:03.376Z]
[JIRA] (JENKINS-60015) Sporadic failure recoding revisions of previous build
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-60015 Sporadic failure recoding revisions of previous build Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo 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.202837.1572603091000.6736.1572603780242%40Atlassian.JIRA.
[JIRA] (JENKINS-60015) Sporadic failure recoding revisions of previous build
Title: Message Title Christoph Vogtländer created an issue Jenkins / JENKINS-60015 Sporadic failure recoding revisions of previous build Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: pipeline, subversion-plugin Created: 2019-11-01 10:11 Environment: Jenkins ver. 2.190.1 Pipeline: SCM Step 2.9 Subversion Plug-in 2.12.2 Priority: Major Reporter: Christoph Vogtländer Sometimes a build is not able to create a changelog because the previous build did not record any revisions. A Subversion post-commit hook is used to trigger the build. I use the "checkout" step with "poll: true" and "changelog: true" on one of the nodes. Normally, the polling log states something like: Started on Nov 1, 2019 9:06:07 AM no polling baseline in D:\Jenkins\jobs\JOB\jobs\trunk\jobs\CI\workspace@libs\sharedLibs on Received SCM poll call on master for CI on Nov 1, 2019 9:06:07 AM Using sole credentials jenkins/** (//server:443> VisualSVN Server) in realm ‘ VisualSVN Server’ https://server/svn/JenkinsWorkflow/JOB/trunk is at revision 971 Received SCM poll call on master for CI on Nov 1, 2019 9:06:07 AM Found credentials jenkins/** (//server:443> VisualSVN Server) in realm ‘ VisualSVN Server’ https://server/svn/Repo/trunk/Project is at revision 33,308 ... Done. Took 8.2 sec Changes found Sporadically, this fails with:
[JIRA] (JENKINS-60014) Show date for blame of a line
Title: Message Title Andreas Pabst updated an issue Jenkins / JENKINS-60014 Show date for blame of a line Change By: Andreas Pabst Currently the forensics-api-plugin provides the name and email of the author and the commit for a specific line as part of the blame. I would like to add the date of the commit here. This would help in determining not only who introduced a bug/issue, but also since when it is present.In my eyes, this would include changes in the three plugins: - forensics-api-plugin: Change FileBlame.java to include the date - git-forensics-plugin: Implement the changed API to compute the date - warnings-ng-plugin: Show the date in the blames table view I would be willing to work on this and open pull request requests , if this addition is okay with you? 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
[JIRA] (JENKINS-60014) Show date for blame of a line
Title: Message Title Andreas Pabst assigned an issue to Andreas Pabst Jenkins / JENKINS-60014 Show date for blame of a line Change By: Andreas Pabst Assignee: Ulli Hafner Andreas Pabst 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.202836.157260248.6731.1572603060322%40Atlassian.JIRA.
[JIRA] (JENKINS-60014) Show date for blame of a line
Title: Message Title Andreas Pabst created an issue Jenkins / JENKINS-60014 Show date for blame of a line Issue Type: New Feature Assignee: Ulli Hafner Components: forensics-api-plugin, git-forensics-plugin, warnings-ng-plugin Created: 2019-11-01 10:01 Priority: Minor Reporter: Andreas Pabst Currently the forensics-api-plugin provides the name and email of the author and the commit for a specific line as part of the blame. I would like to add the date of the commit here. This would help in determining not only who introduced a bug/issue, but also since when it is present. In my eyes, this would include changes in the three plugins: forensics-api-plugin: Change FileBlame.java to include the date git-forensics-plugin: Implement the changed API to compute the date warnings-ng-plugin: Show the date in the blames table view I would be willing to work on this and open pull request, if this addition is okay with you? Add Comment
[JIRA] (JENKINS-59989) Cannot Run Tests from ALM after upgrading to 5.8
Title: Message Title Maria Narcisa Galan assigned an issue to Roy Lu Jenkins / JENKINS-59989 Cannot Run Tests from ALM after upgrading to 5.8 Change By: Maria Narcisa Galan Assignee: Maria Narcisa Galan Roy Lu 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.202796.1572457328000.6727.1572601140260%40Atlassian.JIRA.
[JIRA] (JENKINS-60000) Plugin ignores jenkins proxy settings
Title: Message Title Jie Shen commented on JENKINS-6 Re: Plugin ignores jenkins proxy settings Jenkins itself is a Java program, so you can set proxy for the entire Java program when you start Jenkins. Jenkins also has proxy setting as a software. 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.202814.1572524567000.6715.1572600300178%40Atlassian.JIRA.
[JIRA] (JENKINS-47553) Pipeline 'poll' option in checkout ignored if using libraries for sync
Title: Message Title siddardha sarabu edited a comment on JENKINS-47553 Re: Pipeline 'poll' option in checkout ignored if using libraries for sync Hi Paul Allen, This issue is still present with Jenkins 2.197 version.checkout (for additional repositories) on a custom step defined in shared library with poll=false still polls for changes and triggers jenkins builds . 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.186018.1508494591000.6718.1572600300458%40Atlassian.JIRA.
[JIRA] (JENKINS-47553) Pipeline 'poll' option in checkout ignored if using libraries for sync
Title: Message Title siddardha sarabu reopened an issue This issue is still present with Jenkins 2.197 version. checkout (for additional repositories) on a custom step defined in shared library with poll=false still polls for changes and triggers jenkins builds Jenkins / JENKINS-47553 Pipeline 'poll' option in checkout ignored if using libraries for sync Change By: siddardha sarabu Resolution: Fixed Status: Closed Reopened Assignee: Karl Wirth Paul Allen Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60000) Plugin ignores jenkins proxy settings
Title: Message Title Benjamin Herbert commented on JENKINS-6 Re: Plugin ignores jenkins proxy settings What implications does it have to set the JVM properties? I am wondering as the Jenkins-Wiki states that setting the Proxy in Jenkins is preferred over setting the JVM properties: You can configure the proxy server that Jenkins will use by going to Manage Jenkins > Manage Plugins > Advanced. This is preferred over setting JVM properties. 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.202814.1572524567000.6699.1572598920127%40Atlassian.JIRA.
[JIRA] (JENKINS-59748) Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded
Title: Message Title Jie Shen resolved as Fixed Jenkins / JENKINS-59748 Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded Change By: Jie Shen Status: Open Resolved Resolution: Fixed Released As: 1.1.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.202471.1570798596000.6696.1572598380310%40Atlassian.JIRA.
[JIRA] (JENKINS-60013) Maven Artifact Repository Parameter fetches artifact from all the repositories mentioned in the global configuration.
Title: Message Title Aish R updated an issue Jenkins / JENKINS-60013 Maven Artifact Repository Parameter fetches artifact from all the repositories mentioned in the global configuration. Change By: Aish R Repository Connector:Maven Artifact Repository Parameter fetches artifact from all the repositories mentioned in the global configuration.Though in the job configuration I select one repository from the drop down for repository field it still fetches all the artifacts in both the repositories mentioned in the global configuration. I could see versions from Release repository as well as snapshot repository in the same parameter dropdown groupid and artifactid is same for the repository snapshot and release 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-60013) Maven Artifact Repository Parameter fetches artifact from all the repositories mentioned in the global configuration.
Title: Message Title Aish R created an issue Jenkins / JENKINS-60013 Maven Artifact Repository Parameter fetches artifact from all the repositories mentioned in the global configuration. Issue Type: Bug Assignee: Unassigned Components: repository-connector-plugin Created: 2019-11-01 07:45 Labels: maven-artifact-repository-parameter Priority: Blocker Reporter: Aish R Repository Connector: Maven Artifact Repository Parameter fetches artifact from all the repositories mentioned in the global configuration. Though in the job configuration I select one repository from the drop down for repository field it still fetches all the artifacts in both the repositories mentioned in the global configuration. I could see versions from Release repository as well as snapshot repository in the same parameter dropdown Add Comment
[JIRA] (JENKINS-59985) Warnings Next Generation Plugin for IAR C_STAT does not report warnings
Title: Message Title Roger Smith commented on JENKINS-59985 Re: Warnings Next Generation Plugin for IAR C_STAT does not report warnings Thank you. It appears that there are two different commands for running the IAR cstat. I had been using the iarbuild ... -cstat_analyze … command. I will try changing to the icstat and the analyze commands. It will be next week before I can try this, but I will report back here as soon as I can. 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.202791.1572444215000.6691.1572592500185%40Atlassian.JIRA.
[JIRA] (JENKINS-59748) Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded
Title: Message Title Jie Shen commented on JENKINS-59748 Re: Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded This is a bug triggered by only uploading archived file. I will make a PR to fix 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.202471.1570798596000.6688.1572592140150%40Atlassian.JIRA.
[JIRA] (JENKINS-59985) Warnings Next Generation Plugin for IAR C_STAT does not report warnings
Title: Message Title
Lorenz Aebi edited a comment on JENKINS-59985
Re: Warnings Next Generation Plugin for IAR C_STAT does not report warnings
The IAR cstat parser parses the stdout of the icstat command lines and does not parse the html files. Like this all suppressed messages are already suppressed and do not appear on the warnings chart. You need to call 'icstat' as described in the guideline: http://netstorage.iar.com/SuppDB/Public/UPDINFO/013062/ew/doc/EW_CSTATGuide.ENU.pdf on page 16:{{icstat --db a.db --checks checks.ch commands commands.txt}}commands.txt contains:{{analyze -- iccxcompiler_opts cstat1.c }} {{ analyze -- iccxcompiler_opts cstat2.c}}If you do it like this the output format matches the one mentioned by Ulli Hafner: https://github.com/jenkinsci/analysis-model/blob/master/src/test/resources/edu/hm/hafner/analysis/parser/iar-cstat.txt
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.202791.1572444215000.6686.1572591480226%40Atlassian.JIRA.
