[JIRA] (JENKINS-58982) Jenkins unable to connect to Windows Docker Toolbox Daemon
Title: Message Title NILANJAN DUTTA assigned an issue to openopen openopen Jenkins / JENKINS-58982 Jenkins unable to connect to Windows Docker Toolbox Daemon Change By: NILANJAN DUTTA Assignee: Carlos Sanchez openopen openopen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201331.156618715.5303.1566194040181%40Atlassian.JIRA.
[JIRA] (JENKINS-36929) Add the version of protocols used by connectors
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-36929 Add the version of protocols used by connectors Change By: Allan BURDAJEWICZ Assignee: Steven Christou Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172983.1469467906000.5299.1566191460640%40Atlassian.JIRA.
[JIRA] (JENKINS-35345) Allow to automatically purge old bundles
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-35345 Allow to automatically purge old bundles Change By: Allan BURDAJEWICZ Assignee: Minudika Malshan Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171133.146497733.5294.1566191460530%40Atlassian.JIRA.
[JIRA] (JENKINS-35345) Allow to automatically purge old bundles
Title: Message Title Allan BURDAJEWICZ stopped work on JENKINS-35345 Change By: Allan BURDAJEWICZ Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171133.146497733.5296.1566191460561%40Atlassian.JIRA.
[JIRA] (JENKINS-35344) Allow to browse the content of bundles
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-35344 Allow to browse the content of bundles Change By: Allan BURDAJEWICZ Assignee: Minudika Malshan Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171132.1464976624000.5287.1566191400548%40Atlassian.JIRA.
[JIRA] (JENKINS-35342) Allow to download a bundle
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-35342 Allow to download a bundle Change By: Allan BURDAJEWICZ Assignee: Minudika Malshan Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171130.1464976236000.5290.1566191400626%40Atlassian.JIRA.
[JIRA] (JENKINS-33394) Generate support bundle before providing download
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-33394 Generate support bundle before providing download Change By: Allan BURDAJEWICZ Assignee: Minudika Malshan Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168802.1457451818000.5283.1566191400500%40Atlassian.JIRA.
[JIRA] (JENKINS-33628) Support bundle corrupt via UI
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-33628 Re: Support bundle corrupt via UI Félix Belzunce Arcos This is fixed and released in version 2.57. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169075.145823170.5279.1566191280166%40Atlassian.JIRA.
[JIRA] (JENKINS-53931) Role Strategy: Configuration-as-Code compatibility
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53931 Role Strategy: Configuration-as-Code compatibility Change By: Oleg Nenashev Released As: Role Strategy 1 2 . 17 11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194532.1538926073000.5271.1566191220578%40Atlassian.JIRA.
[JIRA] (JENKINS-53931) Role Strategy: Configuration-as-Code compatibility
Title: Message Title Oleg Nenashev updated JENKINS-53931 Jenkins / JENKINS-53931 Role Strategy: Configuration-as-Code compatibility Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Role Strategy 1.17 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194532.1538926073000.5264.1566191160574%40Atlassian.JIRA.
[JIRA] (JENKINS-58590) simple them plugin not compatible w/JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-58590 simple them plugin not compatible w/JCasC Change By: Oleg Nenashev Component/s: configuration-as-code-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200746.1563767491000.5258.1566191100610%40Atlassian.JIRA.
[JIRA] (JENKINS-58590) simple them plugin not compatible w/JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-58590 simple them plugin not compatible w/JCasC Change By: Oleg Nenashev Labels: jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200746.1563767491000.5255.1566191100416%40Atlassian.JIRA.
[JIRA] (JENKINS-58590) simple them plugin not compatible w/JCasC
Title: Message Title Oleg Nenashev assigned an issue to Tobias Gruetzmacher Jenkins / JENKINS-58590 simple them plugin not compatible w/JCasC Change By: Oleg Nenashev Assignee: Ewelina Wilkosz Tobias Gruetzmacher Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200746.1563767491000.5262.1566191100773%40Atlassian.JIRA.
[JIRA] (JENKINS-58710) Classes with Same name and Different Packages are being triggered JCASC
Title: Message Title Oleg Nenashev commented on JENKINS-58710 Re: Classes with Same name and Different Packages are being triggered JCASC FTR https://github.com/jenkinsci/configuration-as-code-plugin/issues/964 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201002.1564416625000.5252.1566191040344%40Atlassian.JIRA.
[JIRA] (JENKINS-58710) Classes with Same name and Different Packages are being triggered JCASC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-58710 Classes with Same name and Different Packages are being triggered JCASC Change By: Oleg Nenashev Labels: jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201002.1564416625000.5249.1566191040290%40Atlassian.JIRA.
[JIRA] (JENKINS-53865) Cannot configure BFA permissions with CasC and matrix-auth
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53865 Cannot configure BFA permissions with CasC and matrix-auth Change By: Oleg Nenashev Labels: jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194391.1538436863000.5246.1566190980645%40Atlassian.JIRA.
[JIRA] (JENKINS-54920) Refactor AboutJenkins class
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-54920 Refactor AboutJenkins class Change By: Allan BURDAJEWICZ Assignee: Emilio Escobar Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195928.1543416904000.5241.1566190980474%40Atlassian.JIRA.
[JIRA] (JENKINS-54662) hudson.model.UsageStatistics not compatible with CasC plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54662 hudson.model.UsageStatistics not compatible with CasC plugin Change By: Oleg Nenashev Labels: jca jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195453.1542317055000.5238.1566190980413%40Atlassian.JIRA.
[JIRA] (JENKINS-50010) Config page for excluding components when bundle is generated in background
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-50010 Config page for excluding components when bundle is generated in background Change By: Allan BURDAJEWICZ Assignee: Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189008.1520505678000.5243.1566190980554%40Atlassian.JIRA.
[JIRA] (JENKINS-54662) hudson.model.UsageStatistics not compatible with CasC plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54662 hudson.model.UsageStatistics not compatible with CasC plugin Change By: Oleg Nenashev Labels: jca Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195453.1542317055000.5236.1566190920688%40Atlassian.JIRA.
[JIRA] (JENKINS-58983) Jual Obat Erogan Asli Di Riau 0812-8282-3454 Gratis Ongkir
Title: Message Title obat supremasi updated an issue Jenkins / JENKINS-58983 Jual Obat Erogan Asli Di Riau 0812-8282-3454 Gratis Ongkir Change By: obat supremasi Summary: Jual Obat Supremasi Erogan Asli Di Riau 0812-8282-3454 Gratis Ongkir Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201332.1566190633000.5234.1566190920635%40Atlassian.JIRA.
[JIRA] (JENKINS-58983) Jual Obat Supremasi Asli Di Riau 0812-8282-3454 Gratis Ongkir
Title: Message Title obat supremasi updated an issue Jenkins / JENKINS-58983 Jual Obat Supremasi Asli Di Riau 0812-8282-3454 Gratis Ongkir Change By: obat supremasi Environment: PEMESANAN CEPET HUBUNGI KONTAK KAMITELPON Hp ; Jual Obat Erogan Asli Di Riau 081-2828-23454 Watshapp : 081-2828-23454 Harga Obat Erogan: 500-000CARA PEMESANAN DI TOKO KAMI :Untuk Pembelian Atau Pemesanan Jual Obat Erogan Di NTB- EROGAN USA Obat Erogan Pria Bisa Melalui Telepon Langsung Atau Untuk Pemesanan Cepat Dengan Hanya SMS Atau Watshapp Di Customer Service Kami. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201332.1566190633000.5232.1566190740254%40Atlassian.JIRA.
[JIRA] (JENKINS-58983) Jual Obat Supremasi Asli Di Riau 0812-8282-3454 Gratis Ongkir
Title: Message Title obat supremasi created an issue Jenkins / JENKINS-58983 Jual Obat Supremasi Asli Di Riau 0812-8282-3454 Gratis Ongkir Issue Type: Task Assignee: Joseph Petersen Attachments: erogan asli.jpg Components: accurev-plugin Created: 2019-08-19 04:57 Environment: PEMESANAN CEPET HUBUNGI KONTAK KAMI TELPON Hp ; 081-2828-23454 Watshapp : 081-2828-23454 Harga Obat Erogan: 500-000 CARA PEMESANAN DI TOKO KAMI : Untuk Pembelian Atau Pemesanan Jual Obat Erogan Di NTB- EROGAN USA Obat Erogan Pria Bisa Melalui Telepon Langsung Atau Untuk Pemesanan Cepat Dengan Hanya SMS Atau Watshapp Di Customer Service Kami. Labels: plugin Priority: Minor Reporter: obat supremasi Jual Obat Erogan Asli Di Riau, Jual Obat Erogan Di Riau, Jual Erogan Di Riau, Erogan Asli Di Riau, Harga Jual Obat Erogan Di Riau, Erogan Di Riau, Agen Jual Erogan Di Riau. Jual Obat Erogan Asli Di Riau Obat Erogan Dalam Berkeluarga Kehidupan seksual — Merupakan Bagian Terpenting Dari Hubungan Yang Bahagia dan langgeng. Kualitas seks dipengaruhi oleh banyak faktor, salah satunya — karakteristik struktur fisiologis organ genital pasangan. Panjang ukuran penis mempengaruhi kelanjutan hubungan seksual dan sensasi pasangan selama berhubungan seks, oleh karena itu ukuran organ utama laki-laki selalu menjadi peranan yang tinggi. Banyak pria membuat kesalahan dengan berpikir bahwa
[JIRA] (JENKINS-58880) NPE from support core plugin attaching bundle
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-58880 Re: NPE from support core plugin attaching bundle Mark Waite What version of support-core are you running ? I am pretty sure this is fixed in version 2.58, addressed by JENKINS-57602. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201213.1565382062000.5228.1566188280111%40Atlassian.JIRA.
[JIRA] (JENKINS-47449) support-core bundles jsr305 annotations
Title: Message Title Allan BURDAJEWICZ updated JENKINS-47449 Jenkins / JENKINS-47449 support-core bundles jsr305 annotations Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185896.1508157391000.5226.1566187320153%40Atlassian.JIRA.
[JIRA] (JENKINS-47449) support-core bundles jsr305 annotations
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-47449 Change By: Allan BURDAJEWICZ Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185896.1508157391000.5224.1566187200346%40Atlassian.JIRA.
[JIRA] (JENKINS-58982) Jenkins unable to connect to Windows Docker Toolbox Daemon
Title: Message Title NILANJAN DUTTA created an issue Jenkins / JENKINS-58982 Jenkins unable to connect to Windows Docker Toolbox Daemon Issue Type: Task Assignee: Carlos Sanchez Attachments: image-2019-08-19-09-26-35-730.png Components: docker Created: 2019-08-19 03:59 Environment: Windows 7,Windows Docker ToolBox, Docker version 18.03.0-ce, build 0520e24302,Jenkins,Jenkins ver. 2.164.2 Labels: jenkins docker windows Priority: Blocker Reporter: NILANJAN DUTTA I have installed Docker ToolBox for Windows and Jenkins in my Windows 7 Desktop.I am attempting to create a Jenkins Job which will list down docker images available. However, in doing so I am getting the following error :- Started by user Nilanjan Dutta Building on master in workspace C:\Program Files (x86)\Jenkins\workspace\Docker [Docker] $ cmd /c call C:\Windows\TEMP\jenkins1754863637345314489.bat C:\Program Files (x86)\Jenkins\workspace\Docker>docker images error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.37/images/json : open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running. C:\Program Files (x86)\Jenkins\workspace\Docker>exit 1 Build step 'Execute Windows batch command' marked build as failure
[JIRA] (JENKINS-47449) support-core bundles jsr305 annotations
Title: Message Title Allan BURDAJEWICZ edited a comment on JENKINS-47449 Re: support-core bundles jsr305 annotations This comes from the metric plugin https://github.com/jenkinsci/metrics-plugin/blob/metrics-3.0.0/pom.xml#L103-L107 . The metrics plugin pom has been updated accordingly in version [3.1.2.6|https://github.com/jenkinsci/metrics-plugin/commit/43a7ced861bb8d41b77375a7ad0e29d18ed2d29e#diff-600376dffeb79835ede4a0b285078036]. We can bump the version of the dependent metrics plugin in support-core. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185896.1508157391000.5220.1566187020098%40Atlassian.JIRA.
[JIRA] (JENKINS-47449) support-core bundles jsr305 annotations
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-47449 Re: support-core bundles jsr305 annotations This comes from the metric plugin https://github.com/jenkinsci/metrics-plugin/blob/metrics-3.0.0/pom.xml#L103-L107 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185896.1508157391000.5218.1566186900213%40Atlassian.JIRA.
[JIRA] (JENKINS-50947) Could not attach 'nodes/master/pipeline-timings.txt' to support bundle
Title: Message Title Allan BURDAJEWICZ resolved as Fixed Jenkins / JENKINS-50947 Could not attach 'nodes/master/pipeline-timings.txt' to support bundle Change By: Allan BURDAJEWICZ Status: Open Resolved Resolution: Fixed Released As: workflow-cps:2.68 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190088.152449611.5214.1566186240385%40Atlassian.JIRA.
[JIRA] (JENKINS-50947) Could not attach 'nodes/master/pipeline-timings.txt' to support bundle
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-50947 Could not attach 'nodes/master/pipeline-timings.txt' to support bundle Change By: Allan BURDAJEWICZ Component/s: workflow-cps-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190088.152449611.5210.1566186180205%40Atlassian.JIRA.
[JIRA] (JENKINS-50947) Could not attach 'nodes/master/pipeline-timings.txt' to support bundle
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-50947 Re: Could not attach 'nodes/master/pipeline-timings.txt' to support bundle This is solved by https://github.com/jenkinsci/workflow-cps-plugin/commit/8edc46b5acb7b7c45d176f4eb43e939fa63a27c4 in workflow-cps 2.68 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190088.152449611.5206.1566186120189%40Atlassian.JIRA.
[JIRA] (JENKINS-56245) Add the instanceId in the bundle
Title: Message Title Allan BURDAJEWICZ updated JENKINS-56245 Jenkins / JENKINS-56245 Add the instanceId in the bundle Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197812.155082788.5203.1566185760320%40Atlassian.JIRA.
[JIRA] (JENKINS-58980) support-core should only collect the latest GC logs
Title: Message Title Allan BURDAJEWICZ updated JENKINS-58980 Jenkins / JENKINS-58980 support-core should only collect the latest GC logs Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201329.1566177465000.5204.1566185760335%40Atlassian.JIRA.
[JIRA] (JENKINS-56245) Add the instanceId in the bundle
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-56245 Change By: Allan BURDAJEWICZ Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197812.155082788.5201.1566185700208%40Atlassian.JIRA.
[JIRA] (JENKINS-58981) Successful build marked as failed
Title: Message Title
Lukas Behal updated an issue
Jenkins / JENKINS-58981
Successful build marked as failed
Change By:
Lukas Behal
Successfully finished builds are marked as Failed. The build is using Performance Plugin. Console output:{code:java}...13:36:22 Archiving artifacts13:36:22 Recording fingerprints13:36:22 Creating parser with percentiles:'0,50,90,100,' filterRegex:null13:36:22 Performance: Recording JMeterCsv reports '_test_results\jmeter_tests\*.jtl'13:36:22 Performance: JMeterCsv copying reports to master, files '[E:\x.jtl]'13:36:22 Performance: JMeterCsv parsing local reports '[C:\x.jtl]'13:36:22 Performance: Parsing report file 'C:\x.jtl' with filterRegex 'null'.13:36:22 Performance: Percentage of errors greater or equal than 1% sets the build as unstable13:36:22 Performance: Percentage of errors greater or equal than 2% sets the build as failure13:36:22 Performance: File JMeterTestsResults.jtl reported 0.0% of errors [SUCCESS]. Build status is: SUCCESS13:36:22 Disk usage plugin fails during calculation disk usage of this build.13:36:22 Notifying upstream projects of job completion13:36:22 Finished: SUCCESS{code}This build is displayed in Jenkins as:!image-2019-08-19-14-44-52-341.png!I tried to search where the build status is stored on file system and found following record in _all_builds.mr_ in the jobs folder.{code:java}...67,1566178385513,197137,SUCCESS{code}This issue is intermittent. I would really appreciate any help.
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-33350) Does not support Amazon's automatic Windows admin password system
Title: Message Title Raihaan Shouhell updated JENKINS-33350 Jenkins / JENKINS-33350 Does not support Amazon's automatic Windows admin password system Change By: Raihaan Shouhell Status: Fixed but Unreleased Resolved Released As: 1.45 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168755.1457344701000.5186.1566184141468%40Atlassian.JIRA.
[JIRA] (JENKINS-58981) Successful build marked as failed
Title: Message Title
Lukas Behal updated an issue
Jenkins / JENKINS-58981
Successful build marked as failed
Change By:
Lukas Behal
Successfully finished builds are marked as Failed. The build is using Performance Console output:{code:java}...13:36:22 Archiving artifacts13:36:22 Recording fingerprints13:36:22 Creating parser with percentiles:'0,50,90,100,' filterRegex:null13:36:22 Performance: Recording JMeterCsv reports '_test_results\jmeter_tests\*.jtl'13:36:22 Performance: JMeterCsv copying reports to master, files '[E:\x.jtl]'13:36:22 Performance: JMeterCsv parsing local reports '[C:\x.jtl]'13:36:22 Performance: Parsing report file 'C:\x.jtl' with filterRegex 'null'.13:36:22 Performance: Percentage of errors greater or equal than 1% sets the build as unstable13:36:22 Performance: Percentage of errors greater or equal than 2% sets the build as failure13:36:22 Performance: File JMeterTestsResults.jtl reported 0.0% of errors [SUCCESS]. Build status is: SUCCESS13:36:22 Disk usage plugin fails during calculation disk usage of this build.13:36:22 Notifying upstream projects of job completion13:36:22 Finished: SUCCESS{code}This build is displayed in Jenkins as:!image-2019-08-19-14-44-52-341.png!I tried to search where the build status is stored on file system and found following record in _all_builds.mr_ in the jobs folder.{code:java}...67,1566178385513,197137,SUCCESS{code}This issue is intermittent. I would really appreciate any help.
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-33350) Does not support Amazon's automatic Windows admin password system
Title: Message Title Raihaan Shouhell commented on JENKINS-33350 Re: Does not support Amazon's automatic Windows admin password system Tim Brown this is in the latest release 1.45 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168755.1457344701000.5198.1566184141653%40Atlassian.JIRA.
[JIRA] (JENKINS-58981) Successful build marked as failed
Title: Message Title Lukas Behal created an issue Jenkins / JENKINS-58981 Successful build marked as failed Issue Type: Bug Assignee: Unassigned Attachments: image-2019-08-19-14-44-52-341.png Components: core Created: 2019-08-19 03:07 Environment: OS: MS Windows server 2012 R2 Java version: 1.8.0_144-b01 (Oracle corp) Jenkins version: 2.176.2 Web browser: Chrome v76.0.3809.100 this build is using Performance Plugin 3.17 All plugins: ace-editor 1.1 active-directory 2.16 allure-jenkins-plugin 2.28.1 analysis-core 1.96 analysis-model-api 5.3.0 ansicolor 0.6.1 ant 1.9 antisamy-markup-formatter 1.5 apache-httpcomponents-client-4-api 4.5.5-3.0 authentication-tokens 1.3 authorize-project 1.3.0 badge 1.8 bitbucket-approve 1.0.3 bitbucket-build-status-notifier 1.4.1 bitbucket-oauth 0.9 blueocean-commons 1.18.1 blueocean-config 1.18.1 blueocean-core-js 1.18.1 blueocean-dashboard 1.18.1 blueocean-display-url 2.3.0 blueocean-i18n 1.18.1 blueocean-jira 1.18.1 blueocean-jwt 1.18.1 blueocean-personalization 1.18.1 blueocean-pipeline-scm-api 1.18.1 blueocean-rest 1.18.1 blueocean-rest-impl 1.18.1 blueocean-web 1.18.1 bouncycastle-api 2.17 branch-api 2.5.4 build-failure-analyzer 1.22.0 build-history-metrics-plugin 1.2 build-name-setter 2.0.1 build-pipeline-plugin 1.5.8 build-publisher 1.22 build-time-blame 1.2.0 build-timeout 1.19 build-user-vars-plugin 1.5 build-with-parameters 1.4 checkmarx 8.90.4 chucknorris 1.2 claim 2.15 cloudbees-bitbucket-branch-source 2.4.5 cloudbees-folder 6.9 cobertura 1.14 code-coverage-api 1.0.13 command-launcher 1.3 conditional-buildstep 1.3.6 config-file-provider 3.6.2 copyartifact 1.42.1 credentials 2.2.1 credentials-binding 1.20 cucumber-living-documentation 2.2.2 cucumber-reports 4.8.0 dashboard-view 2.11 delivery-pipeline-plugin 1.3.1 disk-usage 0.28 display-url-api 2.3.2 docker-commons 1.15 docker-workflow 1.19 downstream-buildview 1.9 dtkit-api 2.1.1-1 durable-task 1.30 email-ext 2.66 emailext-template 1.1 embeddable-build-status 2.0.2 envinject 2.2.0 envinject-api 1.6 external-monitor-job 1.7 extra-columns 1.20 favorite 2.3.2 flyway-runner 1.9 git 3.11.0 git-client 3.0.0-rc git-parameter 0.9.11 git-server 1.8 github-api 1.95 global-build-stats 1.5 gradle 1.33 greenballs 1.15 groovy 2.2 groovy-postbuild 2.5 handlebars 1.1.1 handy-uri-templates-2-api 2.1.7-1.0 htmlpublisher 1.18
[JIRA] (JENKINS-50523) setami doesn't update global config file
Title: Message Title Raihaan Shouhell commented on JENKINS-50523 Re: setami doesn't update global config file You have to save the config after setting the ami. Normally you would have to replace the entire cloud since Normally you only get a non-modifiable list Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189588.152269220.5173.1566184080316%40Atlassian.JIRA.
[JIRA] (JENKINS-58961) Cannot provision vm because of 'specify OS disk size' issue
Title: Message Title Jie Shen commented on JENKINS-58961 Re: Cannot provision vm because of 'specify OS disk size' issue Different image configuration need different different disk size setting. Need more investigation on how to set os disk size for this case. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201308.1565947259000.5170.1566183600285%40Atlassian.JIRA.
[JIRA] (JENKINS-58961) Cannot provision vm because of 'specify OS disk size' issue
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-58961 Cannot provision vm because of 'specify OS disk size' issue Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201308.1565947259000.5168.1566183480251%40Atlassian.JIRA.
[JIRA] (JENKINS-54502) Jenkins crashed when a running build was aborted.
Title: Message Title Owen Mehegan commented on JENKINS-54502 Re: Jenkins crashed when a running build was aborted. Vipul Madaan I can't say for certain, having never run Jenkins on Windows. I see no reason why just running the installer wouldn't work. I expect the difference between the installer and the bare jar file is that the installer sets up the Windows service, puts the jar in the right place, and includes other Windows-specific things like the WinP library. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195272.1541539669000.5158.1566181380249%40Atlassian.JIRA.
[JIRA] (JENKINS-56245) Add the instanceId in the bundle
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-56245 Re: Add the instanceId in the bundle There is the legacy instance ID. And also the InstanceIdentity: https://github.com/jenkinsci/jenkins/blob/jenkins-2.176.2/core/src/main/java/jenkins/model/identity/InstanceIdentityProvider.java Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197812.155082788.5156.1566181140111%40Atlassian.JIRA.
[JIRA] (JENKINS-58745) P4Groovy p4.run() does not locate credentials in folder
Title: Message Title Joel Brown updated an issue Jenkins / JENKINS-58745 P4Groovy p4.run() does not locate credentials in folder Change By: Joel Brown Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201048.156461302.5154.1566181080292%40Atlassian.JIRA.
[JIRA] (JENKINS-58165) support-core doesn't take into account %t on GC logs
Title: Message Title Allan BURDAJEWICZ updated JENKINS-58165 Jenkins / JENKINS-58165 support-core doesn't take into account %t on GC logs Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200216.1561384273000.5150.1566180600213%40Atlassian.JIRA.
[JIRA] (JENKINS-54502) Jenkins crashed when a running build was aborted.
Title: Message Title Vipul Madaan commented on JENKINS-54502 Re: Jenkins crashed when a running build was aborted. Yes I can see jenkins in list of installed package. So now if I use jenkins.msi to upgrade, do i need to follow any special instructions or just installing it in same location will upgrade it. Thanks Vipul Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195272.1541539669000.5141.1566180480317%40Atlassian.JIRA.
[JIRA] (JENKINS-54502) Jenkins crashed when a running build was aborted.
Title: Message Title Owen Mehegan commented on JENKINS-54502 Re: Jenkins crashed when a running build was aborted. Vipul Madaan manually downloading the jar and using the upgrade button in the Jenkins UI are effectively the same thing. This page shows a few ways that you can list installed MSI packages on Windows: https://www.makeuseof.com/tag/list-installed-programs-windows/ I would try this and see if Jenkins is in this list. If so, that would indicate that the Windows package was used to install Jenkins. If that is the case, I would recommend that you use the Windows package to upgrade it. You can get it from here: https://jenkins.io/download/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195272.1541539669000.5132.1566179640227%40Atlassian.JIRA.
[JIRA] (JENKINS-58165) support-core doesn't take into account %t on GC logs
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-58165 Change By: Allan BURDAJEWICZ Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200216.1561384273000.5129.1566179220172%40Atlassian.JIRA.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Vincent Yan edited a comment on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Thanks for the hard work. I've just recently started to use Jenkins but on a older version. Then came along this issue while I was googling about the stage result issue. Glad there's already a solution in the recent version! :D(y) Appreciate it! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.4883.1566179164491%40Atlassian.JIRA.
[JIRA] (JENKINS-54502) Jenkins crashed when a running build was aborted.
Title: Message Title Vipul Madaan commented on JENKINS-54502 Re: Jenkins crashed when a running build was aborted. Thank you Stephan Reiter and Owen Mehegan I have tried placing a new jar file and also tried to upgrade using Jenkins GUI under manage jenkins. Had same issue both times. I am not sure how it was originally installed. Is there a way to check it? Also I will be trying again this week and will update the crash logs here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195272.1541539669000.5127.1566179168601%40Atlassian.JIRA.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Vincent Yan commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Thanks for the hard work. I've just recently started to use but on a older version. Then came along this issue while I was googling about the stage result issue. Glad there's already a solution in the recent version! Appreciate it! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.4645.1566179044855%40Atlassian.JIRA.
[JIRA] (JENKINS-58980) support-core should only collect the latest GC logs
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-58980 Change By: Allan BURDAJEWICZ Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201329.1566177465000.4642.1566178980080%40Atlassian.JIRA.
[JIRA] (JENKINS-54502) Jenkins crashed when a running build was aborted.
Title: Message Title Owen Mehegan commented on JENKINS-54502 Re: Jenkins crashed when a running build was aborted. Stephan Reiter that's a good question. I actually have no personal experience running Jenkins on Windows, I just wanted to add some context to this Jira after meeting Vipul Madaan at Jenkins World last week. Vipul, am I remembering correctly that you have been upgrading Jenkins by just downloading the newer jar file and putting it in place? Did you originally use a Windows installer package to install Jenkins? Maybe this is related. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195272.1541539669000.4634.1566178740316%40Atlassian.JIRA.
[JIRA] (JENKINS-58980) support-core should only collect the latest GC logs
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-58980 Re: support-core should only collect the latest GC logs It is usually up to the admin to set up a rotation process (such as logrotate or a cron) although it would be useful to limit this in support-core to avoid performances issues when generating the bundle or producing huge bundles. A time limit might of the last 48 hours might be a good start. We could make this configurable via a system property. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201329.1566177465000.4632.1566177720056%40Atlassian.JIRA.
[JIRA] (JENKINS-58980) support-core should only collect the latest GC logs
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-58980 support-core should only collect the latest GC logs Issue Type: Bug Assignee: Emilio Escobar Components: support-core-plugin Created: 2019-08-19 01:17 Environment: support-core:2.34+ Priority: Major Reporter: Allan BURDAJEWICZ When an instance has gigabytes of GC log files, the support bundle generator can effectively take forever. This not only causes high load for Jenkins, but can prevent from generating a support bundle. Steps to reproduce 1. Add 100's GB of log files to the GC folder (specified in JVM startup flags) 2. Try to collect a Bundle Expected Behavior: The bundle is generated in a reasonable amount of time and just includes the most recent data from the GC logs instead of trying to include all of them. Actual Behavior: You will see that the bundle collection times out or runs forever. Add Comment
[JIRA] (JENKINS-58980) support-core should only collect the latest GC logs
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-58980 support-core should only collect the latest GC logs Change By: Allan BURDAJEWICZ Assignee: Emilio Escobar Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201329.1566177465000.4631.1566177480271%40Atlassian.JIRA.
[JIRA] (JENKINS-58979) Random Name generator may produce offensive replacements
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-58979 Random Name generator may produce offensive replacements Issue Type: Bug Assignee: Emilio Escobar Components: support-core-plugin Created: 2019-08-19 00:06 Environment: support-core:2.60 Priority: Major Reporter: Allan BURDAJEWICZ The Support Bundle anonymization uses the https://github.com/kohsuke/wordnet-random-name that may produce some weird and sometimes offensive replacements. For example https://github.com/kohsuke/wordnet-random-name/blob/wordnet-random-name-1.3/src/main/resources/org/kohsuke/randname/a.txt#L254. Add Comment
[JIRA] (JENKINS-58979) Random Name generator may produce offensive replacements
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-58979 Random Name generator may produce offensive replacements Change By: Allan BURDAJEWICZ Assignee: Emilio Escobar Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201328.1566173191000.4627.1566173220301%40Atlassian.JIRA.
[JIRA] (JENKINS-58880) NPE from support core plugin attaching bundle
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-58880 NPE from support core plugin attaching bundle Change By: Allan BURDAJEWICZ Assignee: Emilio Escobar Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201213.1565382062000.4623.1566171960419%40Atlassian.JIRA.
[JIRA] (JENKINS-50947) Could not attach 'nodes/master/pipeline-timings.txt' to support bundle
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-50947 Could not attach 'nodes/master/pipeline-timings.txt' to support bundle Change By: Allan BURDAJEWICZ Assignee: Emilio Escobar Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190088.152449611.4618.1566171960295%40Atlassian.JIRA.
[JIRA] (JENKINS-39595) UX: Prevent setting performance-killer configurations in custom system log Web UIs
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-39595 UX: Prevent setting performance-killer configurations in custom system log Web UIs Change By: Allan BURDAJEWICZ Assignee: Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176152.1478630328000.4611.1566171540366%40Atlassian.JIRA.
[JIRA] (JENKINS-58165) support-core doesn't take into account %t on GC logs
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-58165 support-core doesn't take into account %t on GC logs Change By: Allan BURDAJEWICZ Assignee: Emilio Escobar Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200216.1561384273000.4614.1566171540585%40Atlassian.JIRA.
[JIRA] (JENKINS-42011) Support bundle generation block at some situation when Jenkins is not responding
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-42011 Support bundle generation block at some situation when Jenkins is not responding Change By: Allan BURDAJEWICZ Assignee: Steven Christou Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178879.1487071677000.4606.1566171240176%40Atlassian.JIRA.
[JIRA] (JENKINS-54922) Generated markdown should work in MacDown.app
Title: Message Title Allan BURDAJEWICZ updated JENKINS-54922 Jenkins / JENKINS-54922 Generated markdown should work in MacDown.app Change By: Allan BURDAJEWICZ Status: Fixed but Unreleased Resolved Released As: support-core:2.53 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195930.1543420221000.4603.1566171060199%40Atlassian.JIRA.
[JIRA] (JENKINS-56190) Master /proc files are added twice to the support bundle
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-56190 Re: Master /proc files are added twice to the support bundle This is release in version 2.56 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197739.1550554747000.4597.1566171000248%40Atlassian.JIRA.
[JIRA] (JENKINS-58978) Bump version of CF Plugin Java Library dependency to latest release
Title: Message Title Kristian Kraljic updated an issue Jenkins / JENKINS-58978 Bump version of CF Plugin Java Library dependency to latest release Change By: Kristian Kraljic Summary: Bump version of CF Plugin Java Library dependency to latest release The CF Java library used in the plugin is very outdated. Please bump the dependency to a later release. Thanks ! you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201327.1566170772000.4599.1566171000278%40Atlassian.JIRA.
[JIRA] (JENKINS-56190) Master /proc files are added twice to the support bundle
Title: Message Title Allan BURDAJEWICZ updated JENKINS-56190 Jenkins / JENKINS-56190 Master /proc files are added twice to the support bundle Change By: Allan BURDAJEWICZ Status: Fixed but Unreleased Resolved Released As: support-core:2.56 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197739.1550554747000.4601.1566171000303%40Atlassian.JIRA.
[JIRA] (JENKINS-58978) Bump version of CF Plugin Java Library dependency latest release
Title: Message Title Kristian Kraljic created an issue Jenkins / JENKINS-58978 Bump version of CF Plugin Java Library dependency latest release Issue Type: Improvement Assignee: Olivier Lamy Components: cloudfoundry-plugin Created: 2019-08-18 23:26 Priority: Major Reporter: Kristian Kraljic The CF Java library used in the plugin is very outdated. Please bump the dependency to a later release. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57403) Use natural order to sort Details table
Title: Message Title Ulli Hafner started work on JENKINS-57403 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199187.1557487169000.4591.1566164040350%40Atlassian.JIRA.
[JIRA] (JENKINS-57403) Use natural order to sort Details table
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-57403
Use natural order to sort Details table
Change By:
Ulli Hafner
URL:
https://github.com/jenkinsci/warnings-ng-plugin/pull/177
If you sort by "File" in "Details" -> "Source Control" I'm getting currently following result:{noformat}my_file.cpp:109my_file.cpp:120my_file.cpp:125my_file.cpp:26my_file.cpp:27my_file.cpp:109my_file.cpp:363{noformat}Expected order:{noformat}my_file.cpp:26my_file.cpp:27my_file.cpp:109my_file.cpp:120my_file.cpp:125my_file.cpp:109my_file.cpp:363{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199187.1557487169000.4589.1566164040313%40Atlassian.JIRA.
[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title Ulli Hafner started work on JENKINS-58977 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201326.1566161283000.4593.1566164040398%40Atlassian.JIRA.
[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-58977 publishIssues() should use default ID instead of ID of first scan tool in list Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/179 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201326.1566161283000.4587.1566163920177%40Atlassian.JIRA.
[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title
Stefan Thurnherr updated an issue
Jenkins / JENKINS-58977
publishIssues() should use default ID instead of ID of first scan tool in list
Change By:
Stefan Thurnherr
When using several {{scanForIssues()}} steps and a single {{publishIssues()}} step at the end, the default id used for {{publishIssues()}} should be 'analysis', not taken from the first tool in the scanned tools list.Here is a simple example:{noformat}def pmdIssues = scanForIssues tool: pmdParser(pattern: '**/target/pmd.xml')def cpdIssues = scanForIssues tool: cpd(pattern: '**/target/cpd.xml')def taskScannerIssues = scanForIssuestool: taskScanner(normalTags: 'TODO,FIXME', excludePattern: '*/target/**')def javaIssues = scanForIssues tool: java()def mavenConsoleIssues = scanForIssues tool: mavenConsole()publishIssues name: 'Static Analysis',issues: [pmdIssues, cpdIssues, taskScannerIssues, javaIssues, mavenConsoleIssues]{noformat}In the current version of warnings-ng plugin, the build will use 'pmd' as ID for links and controlling the icon when not specifying a custom ID for {{publishIssues()}} step.*Expected behaviour* would be that the default ID is 'analysis' when using {{publishIssues()}} without specifying a custom ID. (follow-up from [gitter discussion 2019-08-18|https://gitter.im/jenkinsci/warnings-plugin?at=5d59b9ffbfd2887f53146b16])
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title Stefan Thurnherr created an issue Jenkins / JENKINS-58977 publishIssues() should use default ID instead of ID of first scan tool in list Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-08-18 20:48 Environment: Jenkins 2.189 warnings-ng 5.3.0 Priority: Minor Reporter: Stefan Thurnherr When using several scanForIssues() steps and a single publishIssues() step at the end, the default id used for publishIssues() should be 'analysis', not taken from the first tool in the scanned tools list. Here is a simple example: def pmdIssues = scanForIssues tool: pmdParser(pattern: '**/target/pmd.xml') def cpdIssues = scanForIssues tool: cpd(pattern: '**/target/cpd.xml') def taskScannerIssues = scanForIssues tool: taskScanner(normalTags: 'TODO,FIXME', excludePattern: '*/target/**') def javaIssues = scanForIssues tool: java() def mavenConsoleIssues = scanForIssues tool: mavenConsole() publishIssues name: 'Static Analysis', issues: [pmdIssues, cpdIssues, taskScannerIssues, javaIssues, mavenConsoleIssues] In the current version of warnings-ng plugin, the build will use 'pmd' as ID for links and controlling the icon when not specifying a custom ID for publishIssues() step. *Expected behaviour * would be that the default ID is 'analysis' when using publishIssues() without specifying a custom ID.
[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title
Stefan Thurnherr updated an issue
Jenkins / JENKINS-58977
publishIssues() should use default ID instead of ID of first scan tool in list
Change By:
Stefan Thurnherr
When using several {{ scanForIssues() }} steps and a single {{ publishIssues() }} step at the end, the default id used for {{ publishIssues() }} should be 'analysis', not taken from the first tool in the scanned tools list.Here is a simple example:{noformat}def pmdIssues = scanForIssues tool: pmdParser(pattern: '**/target/pmd.xml')def cpdIssues = scanForIssues tool: cpd(pattern: '**/target/cpd.xml')def taskScannerIssues = scanForIssuestool: taskScanner(normalTags: 'TODO,FIXME', excludePattern: '*/target/**')def javaIssues = scanForIssues tool: java()def mavenConsoleIssues = scanForIssues tool: mavenConsole()publishIssues name: 'Static Analysis',issues: [pmdIssues, cpdIssues, taskScannerIssues, javaIssues, mavenConsoleIssues]{noformat}In the current version of warnings-ng plugin, the build will use 'pmd' as ID for links and controlling the icon when not specifying a custom ID for {{publishIssues()}} step.*Expected behaviour* would be that the default ID is 'analysis' when using {{publishIssues()}} without specifying a custom ID.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to
[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title
Stefan Thurnherr updated an issue
Jenkins / JENKINS-58977
publishIssues() should use default ID instead of ID of first scan tool in list
Change By:
Stefan Thurnherr
When using several scanForIssues() steps and a single publishIssues() step at the end, the default id used for publishIssues() should be 'analysis', not taken from the first tool in the scanned tools list.Here is a simple example:{noformat}def pmdIssues = scanForIssues tool: pmdParser(pattern: '**/target/pmd.xml')def cpdIssues = scanForIssues tool: cpd(pattern: '**/target/cpd.xml')def taskScannerIssues = scanForIssuestool: taskScanner(normalTags: 'TODO,FIXME', excludePattern: '*/target/**')def javaIssues = scanForIssues tool: java()def mavenConsoleIssues = scanForIssues tool: mavenConsole()publishIssues name: 'Static Analysis',issues: [pmdIssues, cpdIssues, taskScannerIssues, javaIssues, mavenConsoleIssues]{noformat}In the current version of warnings-ng plugin, the build will use 'pmd' as ID for links and controlling the icon when not specifying a custom ID for {{publishIssues()}} step.*Expected behaviour * would be that the default ID is 'analysis' when using {{publishIssues()}} without specifying a custom ID.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-58976) Mail "Test configuration" not working with SMTP auth
Title: Message Title Norbert Harrer edited a comment on JENKINS-58976 Re: Mail "Test configuration" not working with SMTP auth Just to be sure, I did a fresh install of Jenkins from the msi (jenkins-2.189.zip) in a VM running Windows 10 1903 which never had Jenkins installed before.During install I selected "install suggested plugins".It show shows the same behavior.!ssl-log-windows-vm.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201325.1566072785000.4573.1566153180148%40Atlassian.JIRA.
[JIRA] (JENKINS-58976) Mail "Test configuration" not working with SMTP auth
Title: Message Title Norbert Harrer commented on JENKINS-58976 Re: Mail "Test configuration" not working with SMTP auth Just to be sure, I did a fresh install of Jenkins from the msi (jenkins-2.189.zip) in a VM running Windows 10 1903 which never had Jenkins installed before. During install I selected "install suggested plugins". It show the same behavior. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201325.1566072785000.4571.1566153120105%40Atlassian.JIRA.
[JIRA] (JENKINS-58976) Mail "Test configuration" not working with SMTP auth
Title: Message Title Norbert Harrer updated an issue Jenkins / JENKINS-58976 Mail "Test configuration" not working with SMTP auth Change By: Norbert Harrer Attachment: ssl-log-windows-vm.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201325.1566072785000.4569.1566153000241%40Atlassian.JIRA.
[JIRA] (JENKINS-58595) rssAll feed doesn't have published field after 2.176.2 upgrade
Title: Message Title Uwe Schindler commented on JENKINS-58595 Re: rssAll feed doesn't have published field after 2.176.2 upgrade Is there any schedule for the fix? Apache Lucene's analysis of build failures is affected by this issue: https://lists.apache.org/thread.html/f6c2073a47b1d1cac9549129a522e439d23f598407a7d4ebb5c01036@%3Cdev.lucene.apache.org%3E Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200752.1563783758000.4561.1566123015025%40Atlassian.JIRA.
[JIRA] (JENKINS-57817) Job DSL + Warnings-NG + Spotbugs not working
Title: Message Title Ulli Hafner edited a comment on JENKINS-57817 Re: Job DSL + Warnings-NG + Spotbugs not working I'm not sure if I am making something wrong but the fix in the 1.75 release seems not to work for me, see https://github.com/jenkinsci/warnings-ng-plugin/pull/178. Test report: https://ci.jenkins.io/job/Plugins/job/warnings-ng-plugin/job/JENKINS-57817/1/testReport/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199771.1559562134000.4558.1566122040160%40Atlassian.JIRA.
[JIRA] (JENKINS-57817) Job DSL + Warnings-NG + Spotbugs not working
Title: Message Title Ulli Hafner reopened an issue I'm not sure if I am making something wrong but the fix in the 1.75 release seems not to work for me, see https://github.com/jenkinsci/warnings-ng-plugin/pull/178. Jenkins / JENKINS-57817 Job DSL + Warnings-NG + Spotbugs not working Change By: Ulli Hafner Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199771.1559562134000.4555.1566121980514%40Atlassian.JIRA.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title
René Scheibe updated an issue
Jenkins / JENKINS-35081
Separate authorization configuration page
Change By:
René Scheibe
* Separate the authorization configuration from the project configuration. This allows Jenkins to decide the authorization of builds during configuring projects.* When a plugin lists up credentials,{code :java }public ListBoxModel doFillCredentialsIdItems(@AncestorInPath Job project) {Authentication auth = Tasks.getAuthenticationOf(project);return new StandardUsernameListBoxModel().includeEmptyValue().includeAs(auth, project, StandardUsernameCredentials.class);}{code} * Even if the authorization is changed after the project configuration is saved, it doesn't cause a security issue as the access to the credential is blocked at build time.Issues: * How to control permissions to configure jobs** You don't want to allow other users configure jobs when you use "Run as Specific User".* Should the configuration file be separated ftom from config.xml?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-58692) Change in treatment of Success - Stable vs. Unstable
Title: Message Title Ben Cooksley commented on JENKINS-58692 Re: Change in treatment of Success - Stable vs. Unstable Mark Waite I'm not sure how it managed to make an impact either, however the behaviour we were seeing prior to the restoration of the maintenance of the symlinks by the plugin was the behaviour noted above - namely, that changes to the branch name weren't being picked up. Interestingly, it picked up that the last successful build was 'Applications/19.08', yet for reasons unknown continued to poll an older branch - 'Applications/19.04'. You can find copies of the Pipeline templates, along with the Job DSL scripts we use to provision all the jobs on our Jenkins instance at https://invent.kde.org/sysadmin/ci-tooling/tree/master/ (running of helpers/gather-jobs.py is required prior to trying to evaluate the dsl/*.groovy scripts) To provide a bit of background, we reuse the same jobs when the stable branches for our software changes, and just update the job to refer to the new branches as needed. This functionality has to date worked perfectly reliably, until the release of Jenkins 2.185/2.186 (we jumped straight from 2.184 to 2.186 due to the Trilead SSH issues in 2.185). The solution for us was to install the Symlink plugin, after which normal functionality was restored with 2.186+ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200981.1564306537000.4547.1566116100127%40Atlassian.JIRA.
