[JIRA] (JENKINS-60383) Remote nodes unable to checkout code
Title: Message Title Will Wagner commented on JENKINS-60383 Re: Remote nodes unable to checkout code So looking at this some more, I believe it is the LFS Pull step that is using the wrong credentials. For some reason it previously used to say 'Enabling Git LFS pull' before it started this and did the config core.sparsecheckout. 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.203433.1575577992000.3375.1575967020401%40Atlassian.JIRA.
[JIRA] (JENKINS-60416) Poll MailBox Trigger : The attached files are not found on the server
Title: Message Title NGAT Dev created an issue Jenkins / JENKINS-60416 Poll MailBox Trigger : The attached files are not found on the server Issue Type: Bug Assignee: Nick Grealy Components: poll-mailbox-trigger-plugin Created: 2019-12-10 08:43 Priority: Major Reporter: NGAT Dev When the build is triggered, it runs on a Windows slave, however, the timestamp directory value is not a windows path for example : /tpm/1575299700263-0. Thus, we don't find the directory on the server nor the files. We've tried to force a value on "attachmentsDirectory" variable, but still no file was found either. Add Comment
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Daniel Steiert reopened an issue Jenkins / JENKINS-41308 support Use Groovy Sandbox scripts in activeChoiceParams Change By: Daniel Steiert Resolution: Fixed Status: Closed Reopened Assignee: Daniel Spilker Steiert 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.178082.148516094.3391.1575968280895%40Atlassian.JIRA.
[JIRA] (JENKINS-59973) rtUpload / rtDownload fail with HTTP 401 / 403
Title: Message Title
ethorsa commented on JENKINS-59973
Re: rtUpload / rtDownload fail with HTTP 401 / 403
This is really wired ... I have tested with Username + API key (Username Password) and API Key only (Secret Text) Credentials. Interestingly the access.log shows only anonymous access when running the build:
[ACCEPTED LOGIN] for client : anonymous / .
The connection test in the global config uses the correct user though. Sending the AQL shown in the error via curl responds the correct Json result. Here's my call:
curl --insecure \
-H 'X-JFrog-Art-Api:' \
-i "https:///artifactory/api/search/aql" \
-X POST \
-H 'Content-Type:text/plain' \
--data 'items.find({"repo": "jenkins-artifactory-test","$or": [{"$and": [{"path": { "$match": "*"},"name": { "$match": "*"}}]}]}).include("name","repo","path","actual_md5","actual_sha1","size","type","property")'
The API key is the same as configured in the jenkins credentials.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this messa
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Daniel Steiert commented on JENKINS-41308 Re: support Use Groovy Sandbox scripts in activeChoiceParams To fix this issue, I created a PR according to the guidelines with the addition of the sandbox option for scripts. I made sure all the old functionality is untouched (works the same) and added tests for the new options. The build should also go through (https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fjob-dsl-plugin/detail/PR-1211/1/pipeline) and I tested it on my own Jenkins instance. Please review and let me know if you need any changes before it can be merged. The PR can be found here: https://github.com/jenkinsci/job-dsl-plugin/pull/1211 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.178082.148516094.3451.1575970202146%40Atlassian.JIRA.
[JIRA] (JENKINS-59973) rtUpload / rtDownload fail with HTTP 401 / 403
Title: Message Title ethorsa commented on JENKINS-59973 Re: rtUpload / rtDownload fail with HTTP 401 / 403 Using the rtServer() yields the same 403 error: rtServer( id: 'Artifactory-1', url: 'https:///artifactory', credentialsId: 'artifactory-test' // Username and api key configured by the credentials plugin ) rtDownload(serverId: 'Artifactory-1', specPath: 'spec-dl.json') 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.202777.157235158.3453.1575970680191%40Atlassian.JIRA.
[JIRA] (JENKINS-60417) Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Title: Message Title
shubham srivastava created an issue
Jenkins / JENKINS-60417
Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-12-10 09:42
Priority:
Critical
Reporter:
shubham srivastava
Filtration feature of warning-ng 7.0.0 or above version is not working After upgrading the warning-ng plugin from 6.1.1 version to 7.0.0 version, the filtration feature of warning-ng plugin is stoped working and hyperlink on the file having issues are also disabled. {{}}
}}{{}} [Tasking ctc ] -> found 596 issues (skipped 594 duplicates) [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #222'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #220' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 596, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] Created analysis result for 596 issues (found 0 new issues, fixed 0 issues {{
Entire post processing is missing, if warning ng 7.0.0 or above version is used. The same functionality is working fine for warning-ng 6.1.1 or below version
[JIRA] (JENKINS-60417) Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Title: Message Title
shubham srivastava updated an issue
Jenkins / JENKINS-60417
Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Change By:
shubham srivastava
Filtration feature of warning-ng 7.0.0 or above version is not workingAfter upgrading the warning-ng plugin from 6.1.1 version to 7.0.0 version, the filtration feature of warning-ng plugin is stoped working andhyperlink on the file having issues are also disabled. { {}}{{{ panel} }}{{}} [Tasking ctc ] -> found 596 issues (skipped 594 duplicates) [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #222'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #220' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 596, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] Created analysis result for 596 issues (found 0 new issues, fixed 0 issues { {{ panel} }} Entire post processing is missing, if warning ng 7.0.0 or above version is used. The same functionality is working fine for warning-ng 6.1.1 or below version {{{panel}}}[Tasking ctc ] Successfully parsed file D:\Jenkins\TestProject\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW\APP\CD\SYS\Test\out\Test.ec [Tasking ctc ] -> found 594 issues (skipped 492 duplicates) [Tasking ctc ] Applying 322 filters on the set of 594 issues (545 issues have been removed, 49 issues will be published) [Tasking ctc ] Creating fingerprints for all affected code blocks to track issues over different builds [Tasking ctc ] -> created fingerprints for 47 issues [Tasking ctc ] Copying affected files to Jenkins' build folder '/var/jenkins_home/builds/Playground/HIL_Interface/Test_entire_pipeline/205/files-with-issues' [Tasking ctc ] -> 11 copied, 0 not in workspace, 0 not-found, 0 with I/O error [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #205'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #2' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 49, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] Created analysis result for 49 issues (found 0 new issues, fixed 0 issues){{{panel}}}{{}}
[JIRA] (JENKINS-60417) Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Title: Message Title
shubham srivastava updated an issue
Jenkins / JENKINS-60417
Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Change By:
shubham srivastava
Filtration feature of warning-ng 7.0.0 or above version is not working After upgrading the warning-ng plugin from 6.1.1 version to 7.0.0 version, the filtration feature of warning-ng plugin is stoped working and hyperlink on the file having issues are also disabled.{panel}[Tasking ctc ] -> found 596 issues (skipped 594 duplicates) [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #222'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #220' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 596, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] Created analysis result for 596 issues (found 0 new issues, fixed 0 issues{panel}Entire post processing is missing, if warning ng 7.0.0 or above version is used. The same functionality is working fine for warning-ng 6.1.1 or below version { {{ panel} }} [Tasking ctc ] Successfully parsed file D:\Jenkins\TestProject\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW\APP\CD\SYS\Test\out\Test.ec [Tasking ctc ] -> found 594 issues (skipped 492 duplicates) [Tasking ctc ] Applying 322 filters on the set of 594 issues (545 issues have been removed, 49 issues will be published) [Tasking ctc ] Creating fingerprints for all affected code blocks to track issues over different builds [Tasking ctc ] -> created fingerprints for 47 issues [Tasking ctc ] Copying affected files to Jenkins' build folder '/var/jenkins_home/builds/Playground/HIL_Interface/Test_entire_pipeline/205/files-with-issues' [Tasking ctc ] -> 11 copied, 0 not in workspace, 0 not-found, 0 with I/O error [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #205'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #2' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 49, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] Created analysis result for 49 issues (found 0 new issues, fixed 0 issues) { {{ panel} }} {{}}
[JIRA] (JENKINS-60417) Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Title: Message Title
shubham srivastava updated an issue
Jenkins / JENKINS-60417
Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Change By:
shubham srivastava
Filtration feature of warning-ng 7.0.0 or above version is not working After upgrading the warning-ng plugin from 6.1.1 version to 7.0.0 version, the filtration feature of warning-ng plugin is stoped working and hyperlink on the file having issues are also disabled.{panel}[Tasking ctc ] -> found 596 issues (skipped 594 duplicates) [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #222'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #220' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 596, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] Created analysis result for 596 issues (found 0 new issues, fixed 0 issues{panel}Entire post processing is missing, if warning ng 7.0.0 or above version is used. The same functionality is working fine for warning-ng 6.1.1 or below version {panel}[Tasking ctc ] Successfully parsed file D:\Jenkins\TestProject\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW\APP\CD\SYS\Test\out\Test.ec [Tasking ctc ] -> found 594 issues (skipped 492 duplicates) [Tasking ctc ] * Applying 322 filters * on the set of 594 issues (545 issues have been removed, 49 issues will be published) [Tasking ctc ] Creating fingerprints for all affected code blocks to track issues over different builds [Tasking ctc ] -> created fingerprints for 47 issues [Tasking ctc ] Copying affected files to Jenkins' build folder '/var/jenkins_home/builds/Playground/HIL_Interface/Test_entire_pipeline/205/files-with-issues' [Tasking ctc ] -> 11 copied, 0 not in workspace, 0 not-found, 0 with I/O error [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #205'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #2' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 49, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] Created analysis result for 49 issues (found 0 new issues, fixed 0 issues){panel}{{}}
[JIRA] (JENKINS-60417) Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Title: Message Title
shubham srivastava updated an issue
Jenkins / JENKINS-60417
Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Change By:
shubham srivastava
Filtration feature of warning-ng 7.0.0 or above version is not working After upgrading the warning-ng plugin from 6.1.1 version to 7.0.0 version, the filtration feature of warning-ng plugin is stoped working and hyperlink on the file having issues are also disabled.{panel}[Tasking ctc ] -> found 596 issues (skipped 594 duplicates) [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #222'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #220' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 596, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] Created analysis result for 596 issues (found 0 new issues, fixed 0 issues{panel}Entire post processing is missing, if warning ng 7.0.0 or above version is used. The same functionality is working fine for warning-ng 6.1.1 or below version {panel}[Tasking ctc ] Successfully parsed file D:\Jenkins\TestProject\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW\APP\CD\SYS\Test\out\Test.ec [Tasking ctc ] -> found 594 issues (skipped 492 duplicates) [Tasking ctc ] *Applying 322 filters* on the set of 594 issues (545 issues have been removed, 49 issues will be published) [Tasking ctc ] Creating fingerprints for all affected code blocks to track issues over different builds [Tasking ctc ] -> created fingerprints for 47 issues [Tasking ctc ] Copying affected files to Jenkins' build folder '/var/jenkins_home/builds/Playground/HIL_Interface/Test_entire_pipeline/205/files-with-issues' [Tasking ctc ] -> 11 copied, 0 not in workspace, 0 not-found, 0 with I/O error [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #205'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #2' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 49, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] * Created analysis result for 49 * issues (found 0 new issues, fixed 0 issues){panel}{{}}
[JIRA] (JENKINS-60417) Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Title: Message Title
shubham srivastava updated an issue
Jenkins / JENKINS-60417
Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Change By:
shubham srivastava
Filtration feature of warning-ng 7.0.0 or above version is not working After upgrading the warning-ng plugin from 6.1.1 version to 7.0.0 version, the filtration feature of warning-ng plugin is stoped working and hyperlink on the file having issues are also disabled.{panel}[Tasking ctc ] -> found 596 issues (skipped 594 duplicates) [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #222'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #220' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 596, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] * Created analysis result for 596 issues * (found 0 new issues, fixed 0 issues{panel}Entire post processing is missing, if warning ng 7.0.0 or above version is used. The same functionality is working fine for warning-ng 6.1.1 or below version {panel}[Tasking ctc ] Successfully parsed file D:\Jenkins\TestProject\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW\APP\CD\SYS\Test\out\Test.ec [Tasking ctc ] -> found 594 issues (skipped 492 duplicates) [Tasking ctc ] *Applying 322 filters* on the set of 594 issues (545 issues have been removed, 49 issues will be published) [Tasking ctc ] Creating fingerprints for all affected code blocks to track issues over different builds [Tasking ctc ] -> created fingerprints for 47 issues [Tasking ctc ] Copying affected files to Jenkins' build folder '/var/jenkins_home/builds/Playground/HIL_Interface/Test_entire_pipeline/205/files-with-issues' [Tasking ctc ] -> 11 copied, 0 not in workspace, 0 not-found, 0 with I/O error [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #205'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #2' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 49, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] *Created analysis result for 49* issues (found 0 new issues, fixed 0 issues){panel}{{}}
[JIRA] (JENKINS-60417) Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Title: Message Title
shubham srivastava updated an issue
Jenkins / JENKINS-60417
Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Change By:
shubham srivastava
Filtration feature of warning-ng 7.0.0 or above version is not working After upgrading the warning-ng plugin from 6.1.1 version to 7.0.0 version, the filtration feature of warning-ng plugin is stoped working and hyperlink on the file having issues are also disabled.{panel}[Tasking ctc ] -> found 596 issues (skipped 594 duplicates) [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #222'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #220' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 596, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] *Created analysis result for 596 issues* (found 0 new issues, fixed 0 issues{panel}Entire post processing is missing, if warning ng 7.0.0 or above version is used. The same functionality is working fine for warning-ng 6.1.1 or below version {panel}[Tasking ctc ] Successfully parsed file D:\Jenkins\TestProject\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW\APP\CD\SYS\Test\out\Test.ec [Tasking ctc ] -> found 594 issues (skipped 492 duplicates) [Tasking ctc ] *Applying 322 filters* on the set of 594 issues (545 issues have been removed, 49 issues will be published) [Tasking ctc ] Creating fingerprints for all affected code blocks to track issues over different builds [Tasking ctc ] -> created fingerprints for 47 issues [Tasking ctc ] Copying affected files to Jenkins' build folder '/var/jenkins_home/builds/Playground/HIL_Interface/Test_entire_pipeline/205/files-with-issues' [Tasking ctc ] -> 11 copied, 0 not in workspace, 0 not-found, 0 with I/O error [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #205'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #2' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 49, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] *Created analysis result for 49* issues (found 0 new issues, fixed 0 issues){panel} {{}}
[JIRA] (JENKINS-57576) node and label parameters try to allocate flyweight executor when used in Pipeline jobs
Title: Message Title Joerg Schwaerzler updated an issue Jenkins / JENKINS-57576 node and label parameters try to allocate flyweight executor when used in Pipeline jobs Change By: Joerg Schwaerzler Summary: node and label parameters try to allocated allocate flyweight executor when used in Pipeline jobs 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.199490.1558426372000.3479.1575971700244%40Atlassian.JIRA.
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Daniel Steiert updated JENKINS-41308 Jenkins / JENKINS-41308 support Use Groovy Sandbox scripts in activeChoiceParams Change By: Daniel Steiert 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.178082.148516094.3490.1575971942442%40Atlassian.JIRA.
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Daniel Steiert assigned an issue to Daniel Spilker Jenkins / JENKINS-41308 support Use Groovy Sandbox scripts in activeChoiceParams Change By: Daniel Steiert Assignee: Daniel Steiert Spilker 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.178082.148516094.3493.1575971942602%40Atlassian.JIRA.
[JIRA] (JENKINS-57576) node and label parameters try to allocate flyweight executor when used in Pipeline jobs
Title: Message Title Joerg Schwaerzler commented on JENKINS-57576 Re: node and label parameters try to allocate flyweight executor when used in Pipeline jobs Today we found some even more strange behavior of the plugin in this matter: One job using the LABEL parameter was started on machine 'vm-008'. However this run for some reason uses a flyweight executor on 'vm-011'. This really puzzles me. I can just assume that - since the label _expression_ would match machine 'vm-011', too - the plugin does not necessarily allocate the very flyweight executor it later used for the actual execution. Would be great to at least get some feedback on this topic. 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.199490.1558426372000.3483.1575971942272%40Atlassian.JIRA.
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title
Daniel Steiert edited a comment on JENKINS-41308
Re: support Use Groovy Sandbox scripts in activeChoiceParams
To fix this issue, I created a PR according to the guidelines with the addition The documentation of the {{sandbox}} option for scripts. I made sure all the old functionality course also is untouched (works the same) and added tests for the new options updated . The build should also go through ([https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fjob-dsl-plugin/detail/PR-1211/1/pipeline)] and I tested it on my own Jenkins instance. Please review and let me know if you need any changes before it can be merged.The PR can be found here: https://github.com/jenkinsci/job-dsl-plugin/pull/1211
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.178082.148516094.3500.1575972480350%40Atlassian.JIRA.
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Daniel Steiert edited a comment on JENKINS-41308 Re: support Use Groovy Sandbox scripts in activeChoiceParams The To fix this issue, I created a PR ([https://github.com/jenkinsci/job-dsl-plugin/pull/1211)] with a green build ([https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fjob-dsl-plugin/detail/PR-1211/1/pipeline/).] All the old functionality stays unchanged and only the `sandbox` option was added in. There are tests, documentation of course also is updated and the contribution guidelines have been followed . Please have a look and let me know if any changes need to be made before this can be integrated. Please have a look at the PR Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178082.148516094.3507.1575972660470%40Atlassian.JIRA.
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title
Karl Wirth edited a comment on JENKINS-60142
Re: ConnectionHelper.java constructors call connectionRetry()
Confirmed. One invocation of the above script against a freestyle job that had 8 successful executions caused 24 P4 commands to be run:{code:java} 2019/12/03 17:32:31 pid 1868 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1869 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1870 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1871 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1872 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1873 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1874 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1875 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1876 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1877 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1878 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1879 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1880 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1881 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1882 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1883 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1884 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1885 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1886 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1887 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1888 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1889 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1890 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1891 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s'$ grep user- tmpa.txt | wc -l24{code}For a job with 4 successful runs I saw 11 commands kicked off:{code:java} 2019/12/03 17:40:17 pid 2509 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:40:17 pid 2510 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:40:48 pid 2512 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:40:48 pid 2513 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:40:48 pid 2514 super@_CLIENT_UNSET
[JIRA] (JENKINS-60417) Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-60417
Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Change By:
Ulli Hafner
Filtration feature of warning-ng 7.0.0 or above version is not working After upgrading the warning-ng plugin from 6.1.1 version to 7.0.0 version, the filtration feature of warning-ng plugin is stoped working and hyperlink on the file having issues are also disabled.{ panel noformat }[Tasking ctc ] -> found 596 issues (skipped 594 duplicates) [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #222'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #220' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 596, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] *Created analysis result for 596 issues* (found 0 new issues, fixed 0 issues{ panel noformat }Entire post processing is missing, if warning ng 7.0.0 or above version is used. The same functionality is working fine for warning-ng 6.1.1 or below version { panel noformat }[Tasking ctc ] Successfully parsed file D:\Jenkins\TestProject\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW\APP\CD\SYS\Test\out\Test.ec [Tasking ctc ] -> found 594 issues (skipped 492 duplicates) [Tasking ctc ] *Applying 322 filters* on the set of 594 issues (545 issues have been removed, 49 issues will be published) [Tasking ctc ] Creating fingerprints for all affected code blocks to track issues over different builds [Tasking ctc ] -> created fingerprints for 47 issues [Tasking ctc ] Copying affected files to Jenkins' build folder '/var/jenkins_home/builds/Playground/HIL_Interface/Test_entire_pipeline/205/files-with-issues' [Tasking ctc ] -> 11 copied, 0 not in workspace, 0 not-found, 0 with I/O error [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #205'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #2' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 49, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] *Created analysis result for 49* issues (found 0 new issues, fixed 0 issues){ panel noformat }
[JIRA] (JENKINS-60417) Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-60417
Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Change By:
Ulli Hafner
Filtration feature of warning-ng 7.0.0 or above version is not working After upgrading the warning-ng plugin from 6.1.1 version to 7.0.0 version, the filtration feature of warning-ng plugin is stoped working and hyperlink on the file having issues are also disabled.{noformat}[Tasking ctc ] -> found 596 issues (skipped 594 duplicates) [Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #222'. [Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #220' to compute new, fixed, and outstanding issues [Tasking ctc ] Issues delta (vs. reference build): outstanding: 596, new: 0, fixed: 0 [Tasking ctc ] No quality gates have been set - skipping [Tasking ctc ] Health report is disabled - skipping [Tasking ctc ] * Created analysis result for 596 issues * (found 0 new issues, fixed 0 issues{noformat}Entire post processing is missing, if warning ng 7.0.0 or above version is used. The same functionality is working fine for warning-ng 6.1.1 or below version {noformat}[Tasking ctc ] Successfully parsed -> found 596 issues (skipped 594 duplicates)[Tasking ctc ] [-ERROR-] Can't resolve absolute paths for some files:[Tasking ctc ] [-ERROR-] Can't create fingerprints for some files:[Tasking ctc ] [-ERROR-] - 'D:/Jenkins/shubhamTest/workspace/Playground/HIL_Interface/Test_entire_pipeline/SW/APP/CD/SF/OsSf/ABC/src/Test.c', provided encoding 'UTF-8' seems to be wrong[Tasking ctc ] [-ERROR-] - 'D:/Jenkins/shubhamTest/workspace/Playground/HIL_Interface/Test_entire_pipeline/SW/APP/CD/SF/OsSf/ABC/src/Test1.c', provided encoding 'UTF-8' seems to be wrong[Tasking ctc ] Post processing issues on 'FRVSF56M' with source code encoding 'UTF-8'[Tasking ctc ] Resolving absolute file names for all issues in workspace ' D:\Jenkins\ TestProject shubhamTest \workspace\Playground\HIL_Interface\Test_entire_pipeline\SW \APP\CD\SYS\Test\out\Test '[Tasking ctc ] -> 211 resolved, 1 unresolved, 1 already resolved[Tasking ctc ] Resolving module names from module definitions (build . ec xml, pom.xml, or Manifest.mf files) [Tasking ctc ] -> found 594 resolved module names for 596 issues [Tasking ctc ] Resolving package names ( skipped 492 duplicates or namespaces ) by parsing the affected files [Tasking ctc ] * -> resolved package names of 213 affected files[Tasking ctc ] Applying 322 filters * on the set of 594 596 issues ( 545 547 issues have been removed, 49 issues will be published) [Tasking ctc ] Creating fingerprints for all affected code blocks to track issues over different builds [Tasking ctc ] -> created fingerprints for 47 issues [Tasking ctc ] Copying affected files to Jenkins' build folder '/var/jenkins_home/builds/Playground/HIL_Interface/Test_entire_pipeline/ 205 223 /files-with-issues' [Tasking ctc ] -> 11 copied
[JIRA] (JENKINS-60417) Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-60417
Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Change By:
Ulli Hafner
Filtration feature of warning-ng 7.0.0 or above version is not working Steps invoked:{noformat}recordIssues tools: [taskingVx(name: 'Tasking ctc', pattern: '**/*.ec')],filters: files,healthy: 0 ,unhealthy: 100 ,minimumSeverity: 'HIGH'{noformat} After upgrading the warning-ng plugin from 6.1.1 version to 7.0.0 version, the filtration feature of warning-ng plugin is stoped working and hyperlink on the file having issues are also disabled.{noformat}[Tasking ctc ] -> found 596 issues (skipped 594 duplicates)[Tasking ctc ] Attaching ResultAction with ID 'tasking-vx' to run 'Playground/HIL_Interface/Test_entire_pipeline #222'.[Tasking ctc ] Using reference build 'Playground/HIL_Interface/Test_entire_pipeline #220' to compute new, fixed, and outstanding issues[Tasking ctc ] Issues delta (vs. reference build): outstanding: 596, new: 0, fixed: 0[Tasking ctc ] No quality gates have been set - skipping[Tasking ctc ] Health report is disabled - skipping[Tasking ctc ] Created analysis result for 596 issues (found 0 new issues, fixed 0 issues{noformat}Entire post processing is missing, if warning ng 7.0.0 or above version is used. The same functionality is working fine for warning-ng 6.1.1 or below version {noformat}[Tasking ctc ] -> found 596 issues (skipped 594 duplicates)[Tasking ctc ] [-ERROR-] Can't resolve absolute paths for some files:[Tasking ctc ] [-ERROR-] Can't create fingerprints for some files:[Tasking ctc ] [-ERROR-] - 'D:/Jenkins/shubhamTest/workspace/Playground/HIL_Interface/Test_entire_pipeline/SW/APP/CD/SF/OsSf/ABC/src/Test.c', provided encoding 'UTF-8' seems to be wrong[Tasking ctc ] [-ERROR-] - 'D:/Jenkins/shubhamTest/workspace/Playground/HIL_Interface/Test_entire_pipeline/SW/APP/CD/SF/OsSf/ABC/src/Test1.c', provided encoding 'UTF-8' seems to be wrong[Tasking ctc ] Post processing issues on 'FRVSF56M' with source code encoding 'UTF-8'[Tasking ctc ] Resolving absolute file names for all issues in workspace 'D:\Jenkins\shubhamTest\workspace\Playground\HIL_Interface\Test_entire_pipeline\SW'[Tasking ctc ] -> 211 resolved, 1 unresolved, 1 already resolved[Tasking ctc ] Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)[Tasking ctc ] -> resolved module names for 596 issues[Tasking ctc ] Resolving package names (or namespaces) by parsing the affected files[Tasking ctc ] -> resolved package names of 213 affected files[Tasking ctc ] Applying 322 filters on the set of 596 issues (547 issues have been removed, 49 issues will be published)[Tasking ctc ] Creating fingerprints for all affected code blocks to track issues over different builds[Tasking ctc ] -> created fingerprints for 47 issues[Tasking ctc ] Copying affected files to Jenkins' build folder '/var/jenkins_home/builds/Playground/HIL_Interface/Test_entire_pipeline/223/f
[JIRA] (JENKINS-60417) Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Title: Message Title Ulli Hafner commented on JENKINS-60417 Re: Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version Are there any exceptions in the Jenkins log? What version of forensics-api and analysis-mode-api do you have installed? Is the build invoked on the master or agent? 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.203478.1575970934000.3522.1575974220137%40Atlassian.JIRA.
[JIRA] (JENKINS-60066) "when changeset" not working in P4 multibranch pipeline with Windows Jenkins Master
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60066 "when changeset" not working in P4 multibranch pipeline with Windows Jenkins Master Change By: Karl Wirth Summary: "when changeset" not working in P4 multibranch pipeline with Windows Jenkins Master 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.202899.1572988612000.3528.1575974640479%40Atlassian.JIRA.
[JIRA] (JENKINS-60066) "when changeset" not working in P4 multibranch pipeline
Title: Message Title Karl Wirth assigned an issue to Unassigned Jenkins / JENKINS-60066 "when changeset" not working in P4 multibranch pipeline Change By: Karl Wirth Assignee: Karl Wirth 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.202899.1572988612000.3526.1575974640411%40Atlassian.JIRA.
[JIRA] (JENKINS-60066) "when changeset" not working in P4 multibranch pipeline
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60066 "when changeset" not working in P4 multibranch pipeline Change By: Karl Wirth Labels: P4_SUPPORT p4-plugin 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.202899.1572988612000.3524.1575974640377%40Atlassian.JIRA.
[JIRA] (JENKINS-60066) "when changeset" not working in P4 multibranch pipeline with Windows Jenkins Master
Title: Message Title Karl Wirth closed an issue as Won't Fix There is possibly a bug here but it's outside the p4-plugin code. It's also posssible a different syntax is needed for Windows. Marking as Won't fix for now as there isn't an 'unable to fix' category. Jenkins / JENKINS-60066 "when changeset" not working in P4 multibranch pipeline with Windows Jenkins Master Change By: Karl Wirth Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-60417) Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version
Title: Message Title shubham srivastava commented on JENKINS-60417 Re: Issue in Post Processing functionality(Apply filter) in warning-ng 7.0.0 or above version I didn't find any exception in the log. currently the following version of plugin is installed warning-ng 7.2.2, forensics-api 0.6.1 and Analysis model API 7.0.2 build is invoked on agent if warning-ng 6.1.1, forensics-api 0.4.1 and Analysis model api 7.0.2 is used. then there is no issue, everything works fine 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.203478.1575970934000.3532.1575974880133%40Atlassian.JIRA.
[JIRA] (JENKINS-60395) ALM jenkins plugin: ALM results upload issue
Title: Message Title Maria Narcisa Galan assigned an issue to Roy Lu Jenkins / JENKINS-60395 ALM jenkins plugin: ALM results upload issue 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.203449.1575673998000.3535.1575975720351%40Atlassian.JIRA.
[JIRA] (JENKINS-60395) ALM jenkins plugin: ALM results upload issue
Title: Message Title Maria Narcisa Galan updated an issue Jenkins / JENKINS-60395 ALM jenkins plugin: ALM results upload issue Change By: Maria Narcisa Galan Labels: ALM 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.203449.1575673998000.3538.1575975780225%40Atlassian.JIRA.
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title Matthew Smeeth edited a comment on JENKINS-60142 Re: ConnectionHelper.java constructors call connectionRetry() Hi [~jbateman],"getEnvironment" fetches various Perforce variables including p4ticket, unfortunately some of our customers require a Perforce ticket to be added to the environment for their scripts. However if If you set the "Hide TICKET" option in the "Perforce: Secure P4_TICKET" section on the Jenkins configuration page, this will prevent Jenkins from getting a ticket when you call the "getEnvironment" function. 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.203003.1573562093000.3545.1575976982184%40Atlassian.JIRA.
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title Matthew Smeeth commented on JENKINS-60142 Re: ConnectionHelper.java constructors call connectionRetry() Hi James Bateman, "getEnvironment" fetches various Perforce variables including p4ticket, unfortunately some of our customers require a Perforce ticket to be added to the environment for their scripts. However if you set the "Hide TICKET" option in the "Perforce: Secure P4_TICKET" section on the Jenkins configuration page, this will prevent Jenkins from getting a ticket when you call the "getEnvironment" function. 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.203003.1573562093000.3543.1575976982014%40Atlassian.JIRA.
[JIRA] (JENKINS-60228) AdoptOpenJDK Plugin missed Java 13 support
Title: Message Title Andreas Thiel commented on JENKINS-60228 Re: AdoptOpenJDK Plugin missed Java 13 support Working perfectly, thanks a lot! 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.203203.1574254744000.3549.1575977040264%40Atlassian.JIRA.
[JIRA] (JENKINS-60418) issue of Integration webhook with bitbucket when using bitbucket pull and push plugin
Title: Message Title vikas goyal created an issue Jenkins / JENKINS-60418 issue of Integration webhook with bitbucket when using bitbucket pull and push plugin Issue Type: Bug Assignee: Christian Del Monte Components: bitbucket-push-and-pull-request-plugin Created: 2019-12-10 11:40 Priority: Minor Reporter: vikas goyal Hi Team, we have faced some kind of issue. As you suggested in the documentation the Bitbucket pull and push plugin will not work if Bitbucket plugin is still installed. But when we uninstall the Bitbucket plugin the jenkins_url/bitbucket-hook/ throws 404. when I again install the Bitbucket plugin it gives 200 but the job is not invoked. Can you please help us ASAP as we are blocked due to this. Add Comment
[JIRA] (JENKINS-60418) issue of Integration webhook with bitbucket when using bitbucket pull and push plugin
Title: Message Title vikas goyal updated an issue Jenkins / JENKINS-60418 issue of Integration webhook with bitbucket when using bitbucket pull and push plugin Change By: vikas goyal Hi Team, we have faced some kind of issue issues . As you suggested in the documentation the Bitbucket pull and push plugin will not work if Bitbucket plugin is still installed. But when we uninstall the Bitbucket plugin the jenkins_url/bitbucket-hook/ throws 404. when I again install the Bitbucket plugin it gives 200 but the job is not invoked. Can you please help us ASAP as we are blocked due to this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203480.1575978042000.356
[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Philippe Kocher updated an issue Jenkins / JENKINS-54654 A recent update breaks builds by escaping slashes to percent signs in workspace paths Change By: Philippe Kocher Attachment: GitRepoBranchName.png Attachment: JenkinsBuildWorkspace.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.195445.1542295531000.3565.1575979920722%40Atlassian.JIRA.
[JIRA] (JENKINS-46722) alwaysLinkToLastBuild not linking to last job result
Title: Message Title Senthilkumar Palanisamy edited a comment on JENKINS-46722 Re: alwaysLinkToLastBuild not linking to last job result Hi,We are also facing same issue for failed build HTML publish is not creating any link in Jenkins Project level, we have to enable alwaysLinkToLastBuild: true,keepAll: true,In order to see in particular build , Please can i know is there any other workaround to see HTML publish result in project level or any permanent fix.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.185068.1504796587000.3576.1575980220472%40Atlassian.JIRA.
[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Philippe Kocher updated an issue Jenkins / JENKINS-54654 A recent update breaks builds by escaping slashes to percent signs in workspace paths Change By: Philippe Kocher Attachment: JenkinsBuildWorkspace.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.195445.1542295531000.3591.1575980643517%40Atlassian.JIRA.
[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Philippe Kocher updated an issue Jenkins / JENKINS-54654 A recent update breaks builds by escaping slashes to percent signs in workspace paths Change By: Philippe Kocher Attachment: GitRepoBranchName.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.195445.1542295531000.3602.1575980643751%40Atlassian.JIRA.
[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Philippe Kocher updated an issue Jenkins / JENKINS-54654 A recent update breaks builds by escaping slashes to percent signs in workspace paths Change By: Philippe Kocher Attachment: JenkinsBuildWorkspace.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.195445.1542295531000.3636.1575981061536%40Atlassian.JIRA.
[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Philippe Kocher updated an issue Jenkins / JENKINS-54654 A recent update breaks builds by escaping slashes to percent signs in workspace paths Change By: Philippe Kocher Attachment: GitRepoBranchName.png Attachment: JenkinsBuildWorkspace.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.195445.1542295531000.3625.1575981061237%40Atlassian.JIRA.
[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Philippe Kocher updated an issue Jenkins / JENKINS-54654 A recent update breaks builds by escaping slashes to percent signs in workspace paths Change By: Philippe Kocher Attachment: GitRepoBranchName.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.195445.1542295531000.3647.1575981061763%40Atlassian.JIRA.
[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Philippe Kocher updated an issue Jenkins / JENKINS-54654 A recent update breaks builds by escaping slashes to percent signs in workspace paths Change By: Philippe Kocher Attachment: JenkinsBuildWorkspace.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.195445.1542295531000.3658.1575981120858%40Atlassian.JIRA.
[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Philippe Kocher commented on JENKINS-54654 Re: A recent update breaks builds by escaping slashes to percent signs in workspace paths Deat Community, I'm facing the same problem with my multibranch pipeline project: "feature/branch" from a git repository is transformed to "feature%2Fbranch" which causes build to fail because the build process cannot find the files. As mentionned above, I did an update of Jenkins and the branch API plugin but the problem is still remaining. I'm working with: Jenkins version 2.190.3 Branch API Plugin Version 2.5.5 I saw tat PR#137 should solve the problem. Is this PR already merged, i.e. available in the latest release of Jenkins Branch API Plugin available? If yes, I think that the issue is still active and not resolved. Any update about this issue? Find also attached to this message two screenshot conerning the issue: the Branch name on git and the result on the Jenkins Workspace. 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.195445.1542295531000.3669.1575981121129%40Atlassian.JIRA.
[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Philippe Kocher commented on JENKINS-54654 Re: A recent update breaks builds by escaping slashes to percent signs in workspace paths ** Dear Community, (same message with alle picture) I'm facing the same problem with my multibranch pipeline project: "feature/branch" from a git repository is transformed to "feature%2Fbranch" which causes build to fail because the build process cannot find the files. As mentionned above, I did an update of Jenkins and the branch API plugin but the problem is still remaining. I'm working with: Jenkins version 2.190.3 Branch API Plugin Version 2.5.5 I saw tat PR#137 should solve the problem. Is this PR already merged, i.e. available in the latest release of Jenkins Branch API Plugin available? If yes, I think that the issue is still active and not resolved. Any update about this issue? Find also attached to this message two screenshot conerning the issue: the Branch name on git and the result on the Jenkins Workspace. Thanks a lot for your help Best regards 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.195445.1542295531000.3691.1575981180957%40Atlassian.JIRA.
[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Philippe Kocher updated an issue Jenkins / JENKINS-54654 A recent update breaks builds by escaping slashes to percent signs in workspace paths Change By: Philippe Kocher Attachment: GitRepoBranchName.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.195445.1542295531000.3680.1575981180738%40Atlassian.JIRA.
[JIRA] (JENKINS-60377) Support cucumber test-runnner converter for ALM Octane testing framework
Title: Message Title Radi Berkovich updated JENKINS-60377 Jenkins / JENKINS-60377 Support cucumber test-runnner converter for ALM Octane testing framework Change By: Radi Berkovich Status: Open Fixed but Unreleased 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.203424.1575549869000.3805.1575982260256%40Atlassian.JIRA.
[JIRA] (JENKINS-60377) Support cucumber test-runnner converter for ALM Octane testing framework
Title: Message Title Radi Berkovich updated JENKINS-60377 Jenkins / JENKINS-60377 Support cucumber test-runnner converter for ALM Octane testing framework Change By: Radi Berkovich Status: Fixed but Unreleased 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.203424.1575549869000.3806.1575982265116%40Atlassian.JIRA.
[JIRA] (JENKINS-60376) Support vulnerabilities injection to ALM Octane via Pipeline as code (Fortify SSC)
Title: Message Title Radi Berkovich updated JENKINS-60376 Jenkins / JENKINS-60376 Support vulnerabilities injection to ALM Octane via Pipeline as code (Fortify SSC) Change By: Radi Berkovich Status: Fixed but Unreleased 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.203423.1575549773000.3808.1575982321245%40Atlassian.JIRA.
[JIRA] (JENKINS-60379) Sometimes Git line enricher is failing if checkout was done on slave
Title: Message Title Radi Berkovich updated JENKINS-60379 Jenkins / JENKINS-60379 Sometimes Git line enricher is failing if checkout was done on slave Change By: Radi Berkovich Status: Open Fixed but Unreleased 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.203426.1575550236000.3824.1575982321754%40Atlassian.JIRA.
[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Philippe Kocher updated an issue Jenkins / JENKINS-54654 A recent update breaks builds by escaping slashes to percent signs in workspace paths Change By: Philippe Kocher Comment: **Dear Community, (same message with alle picture)I'm facing the same problem with my multibranch pipeline project: "feature/branch" from a git repository is transformed to "feature%2Fbranch" which causes build to fail because the build process cannot find the files. As mentionned above, I did an update of Jenkins and the branch API plugin but the problem is still remaining. I'm working with:Jenkins version 2.190.3Branch API Plugin Version 2.5.5I saw tat PR#137 should solve the problem. Is this PR already merged, i.e. available in the latest release of Jenkins Branch API Plugin available? If yes, I think that the issue is still active and not resolved.Any update about this issue?Find also attached to this message two screenshot conerning the issue: the Branch name on git and the result on the Jenkins Workspace. Thanks a lot for your help Best regards !GitRepoBranchName.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
[JIRA] (JENKINS-60374) Support Code Coverage injection to ALM Octane via pipeline as a code
Title: Message Title Radi Berkovich updated JENKINS-60374 Jenkins / JENKINS-60374 Support Code Coverage injection to ALM Octane via pipeline as a code Change By: Radi Berkovich Status: Open Fixed but Unreleased 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.203421.1575549681000.3809.1575982321263%40Atlassian.JIRA.
[JIRA] (JENKINS-60378) Simplify user impersonation
Title: Message Title Radi Berkovich updated JENKINS-60378 Jenkins / JENKINS-60378 Simplify user impersonation Change By: Radi Berkovich Status: Fixed but Unreleased 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.203425.1575550056000.3823.1575982321742%40Atlassian.JIRA.
[JIRA] (JENKINS-60374) Support Code Coverage injection to ALM Octane via pipeline as a code
Title: Message Title Radi Berkovich updated JENKINS-60374 Jenkins / JENKINS-60374 Support Code Coverage injection to ALM Octane via pipeline as a code Change By: Radi Berkovich Status: Fixed but Unreleased 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.203421.1575549681000.3810.1575982321289%40Atlassian.JIRA.
[JIRA] (JENKINS-60376) Support vulnerabilities injection to ALM Octane via Pipeline as code (Fortify SSC)
Title: Message Title Radi Berkovich updated JENKINS-60376 Jenkins / JENKINS-60376 Support vulnerabilities injection to ALM Octane via Pipeline as code (Fortify SSC) Change By: Radi Berkovich Status: Open Fixed but Unreleased 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.203423.1575549773000.3807.1575982321192%40Atlassian.JIRA.
[JIRA] (JENKINS-60378) Simplify user impersonation
Title: Message Title Radi Berkovich updated JENKINS-60378 Jenkins / JENKINS-60378 Simplify user impersonation Change By: Radi Berkovich Status: Open Fixed but Unreleased 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.203425.1575550056000.3822.1575982321710%40Atlassian.JIRA.
[JIRA] (JENKINS-60379) Sometimes Git line enricher is failing if checkout was done on slave
Title: Message Title Radi Berkovich updated JENKINS-60379 Jenkins / JENKINS-60379 Sometimes Git line enricher is failing if checkout was done on slave Change By: Radi Berkovich Status: Fixed but Unreleased 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.203426.1575550236000.3825.1575982380463%40Atlassian.JIRA.
[JIRA] (JENKINS-60103) Cannot send junit results to Octane, because there is no permission on slave to create log folder
Title: Message Title Radi Berkovich commented on JENKINS-60103 Re: Cannot send junit results to Octane, because there is no permission on slave to create log folder Version 6.0 released with the fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202949.1573206476000.3827.1575982380593%40Atlassian.JIRA.
[JIRA] (JENKINS-60103) Cannot send junit results to Octane, because there is no permission on slave to create log folder
Title: Message Title Radi Berkovich updated JENKINS-60103 Jenkins / JENKINS-60103 Cannot send junit results to Octane, because there is no permission on slave to create log folder Change By: Radi Berkovich 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.202949.1573206476000.3831.1575982380690%40Atlassian.JIRA.
[JIRA] (JENKINS-60103) Cannot send junit results to Octane, because there is no permission on slave to create log folder
Title: Message Title Radi Berkovich updated JENKINS-60103 Jenkins / JENKINS-60103 Cannot send junit results to Octane, because there is no permission on slave to create log folder Change By: Radi Berkovich Status: Reopened Fixed but Unreleased 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.202949.1573206476000.3829.1575982380647%40Atlassian.JIRA.
[JIRA] (JENKINS-59754) Jenkins Micro Focus Application Automation Tools Plugin losing connection with Octane after running pipelines
Title: Message Title Radi Berkovich commented on JENKINS-59754 Re: Jenkins Micro Focus Application Automation Tools Plugin losing connection with Octane after running pipelines Official version 6.0 is release . Please check if issue is reproduced on this version. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202477.1570821116000.3837.1575982440594%40Atlassian.JIRA.
[JIRA] (JENKINS-59754) Jenkins Micro Focus Application Automation Tools Plugin losing connection with Octane after running pipelines
Title: Message Title Radi Berkovich edited a comment on JENKINS-59754 Re: Jenkins Micro Focus Application Automation Tools Plugin losing connection with Octane after running pipelines Official version 6.0 is release released .Please check if issue is reproduced on this version. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202477.1570821116000.3839.1575982440660%40Atlassian.JIRA.
[JIRA] (JENKINS-60103) Cannot send junit results to Octane, because there is no permission on slave to create log folder
Title: Message Title Radi Berkovich closed an issue as Fixed Jenkins / JENKINS-60103 Cannot send junit results to Octane, because there is no permission on slave to create log folder Change By: Radi Berkovich 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.202949.1573206476000.3833.1575982440498%40Atlassian.JIRA.
[JIRA] (JENKINS-58312) Pipeline from SCM tag already exists
Title: Message Title Bogdan Ailiesei commented on JENKINS-58312 Re: Pipeline from SCM tag already exists Hi, You can tell your checkout not to pull tags in your local copy. checkout([$class: 'GitSCM', branches: [[name: 'master' ]], extensions: [[$class: 'CloneOption', noTags: true, shallow: true, reference: '']], userRemoteConfigs: [[credentialsId: 'hudstech-checkout-git', url: https://bitbucket.myserver/repositories/MyProject.git" ]]]) Then your git tag command would work Regards 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.200420.1562140814000.3867.1575983940260%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Michael McGrath commented on JENKINS-56500 Re: Declarative pipeline restricted in code size Liam Newman Updated plugin, removed any def vars, set JVM property on script console. I am still encountering "method too large" on a test job. Reaching this issue on a shared library approach as well, where we have stripped everything out into vars. Work arounds? 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.198107.1552302995000.3872.1575984420723%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title M McGrath edited a comment on JENKINS-56500 Re: Declarative pipeline restricted in code size [~bitwiseman]Updated plugin, removed any def vars, set JVM property on script console.I am still encountering "method too large" on a test job.Reaching this issue on a shared library approach as well, where we have stripped everything out into vars / global methods . Work arounds? 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.198107.1552302995000.3884.1575984540404%40Atlassian.JIRA.
[JIRA] (JENKINS-1304) Add a "Use Export" option to the Subversion config section of a job
Title: Message Title karan dave commented on JENKINS-1304 Re: Add a "Use Export" option to the Subversion config section of a job +1 it is very useful feature to have 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.131377.1203007776000.3895.1575984841280%40Atlassian.JIRA.
[JIRA] (JENKINS-59227) Global Pipeline Libraries configuration lost
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-59227 Global Pipeline Libraries configuration lost Change By: Oleg Nenashev Assignee: R. Tyler Croy 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.201684.1567609146000.3915.1575985560288%40Atlassian.JIRA.
[JIRA] (JENKINS-59227) Global Pipeline Libraries configuration lost
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59227 Global Pipeline Libraries configuration lost Change By: Oleg Nenashev Component/s: 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.201684.1567609146000.3918.1575985560347%40Atlassian.JIRA.
[JIRA] (JENKINS-59227) Global Pipeline Libraries configuration lost
Title: Message Title Oleg Nenashev commented on JENKINS-59227 Re: Global Pipeline Libraries configuration lost CC Liam Newman Devin Nusbaum who are the Pipeline maintainers ATM 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.201684.1567609146000.3922.1575985620178%40Atlassian.JIRA.
[JIRA] (JENKINS-60419) Blocked classpaths are not shown on script approvals page (workflow job)
Title: Message Title Aleksei Vesnin created an issue Jenkins / JENKINS-60419 Blocked classpaths are not shown on script approvals page (workflow job) Issue Type: Bug Assignee: vimil Attachments: config.xml Components: extended-choice-parameter-plugin Created: 2019-12-10 13:48 Priority: Major Reporter: Aleksei Vesnin Groovy classpaths for Extended Choice Parameter in a workflow/pipeline job are blocked with message `You have unapproved groovy scripts that need approval before they can be executed. Go to In-Process Script Approval page to approve your scripts.`, which is expected. But on the scrip approval page it says `No pending classpath entry approvals.`. For freestyle jobs it kind of works, I can approve or deny a classpath entries, but if multiple classpaths are defined and approved for a parameter, the parameter script doesn't see them. E. g. there are `src` and `resources` folders and class `src/io/domain/Config.groovy` which loads `resources/io/domain/config.yml`. When I only add `src` to the classpath it complains that it can't find `io/domain/config.yml` file, which is expected, but when both `src` and `resources` are added to the classpath (and both are approved), then the same script fails with `unable to resolve class io.domain.Config` exception, which is a bummer. These are probably two different classpath issues, please let me know if you need a separate ticket for the latter.
[JIRA] (JENKINS-60419) Blocked classpaths are not shown on script approvals page (workflow job)
Title: Message Title Aleksei Vesnin updated an issue Jenkins / JENKINS-60419 Blocked classpaths are not shown on script approvals page (workflow job) Change By: Aleksei Vesnin Groovy classpaths for Extended Choice Parameter in a workflow/pipeline job are blocked with message `You have unapproved groovy scripts that need approval before they can be executed. Go to In-Process Script Approval page to approve your scripts.`, which is expected. But on the scrip script approval page it says `No pending classpath entry approvals.`.For freestyle jobs it kind of works, I can approve or deny a classpath entries, but if multiple classpaths are defined and approved for a parameter, the parameter script doesn't see them. E. g. there are `src` and `resources` folders and class `src/io/domain/Config.groovy` which loads `resources/io/domain/config.yml`. When I only add `src` to the classpath it complains that it can't find `io/domain/config.yml` file, which is expected, but when both `src` and `resources` are added to the classpath (and both are approved), then the same script fails with `unable to resolve class io.domain.Config` exception, which is a bummer.These are probably two different classpath issues, please let me know if you need a separate ticket for the latter. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60419) Blocked classpaths are not shown on script approvals page (workflow job)
Title: Message Title Aleksei Vesnin updated an issue Jenkins / JENKINS-60419 Blocked classpaths are not shown on script approvals page (workflow job) Change By: Aleksei Vesnin Groovy classpaths for Extended Choice Parameter in a workflow/pipeline job are blocked with message `You have unapproved groovy scripts that need approval before they can be executed. Go to In-Process Script Approval page to approve your scripts.`, which is expected. But on the script approval page it says `No pending classpath entry approvals.`.For freestyle jobs it kind of works, I can approve or deny a classpath entries, but if multiple classpaths are defined and approved for a parameter, the parameter script doesn't see them. E. g. there are `src` and `resources` folders and class `src/io/domain/Config.groovy` which loads `resources/io/domain/config.yml`. When I only add `src` to the classpath it complains that it can't find `io/domain/config.yml` file, which is expected, but when both `src` and `resources` are added to the classpath (and both are approved), then the same script fails with `unable to resolve class io.domain.Config` exception, which is a bummer.These are probably two different classpath issues, please let me know if you need a separate ticket for the latter. Jenkins version: 2.190.3Extended Choice Parameter plugin version: 0.78 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman commented on JENKINS-56500 Re: Declarative pipeline restricted in code size I'm on vacation for the next week. When I get back I'll add a patch to log when this feature is turned on. Maybe some debug information about what it is doing. There should not be a need for further workarounds. How big is your pipeline? Would you be willing to share it with me for debugging? 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.198107.1552302995000.3942.1575986040567%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Cloud Configuration Length Cap
Title: Message Title Mahmoud Ksemtini edited a comment on JENKINS-60409 Re: Cloud Configuration Length Cap I get the same error when trying to replay a job from the UI. (Jenkins Version 2.205) !Screenshot 2019-12-10 at 15.27.37.png|width=732,height=395! 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.203466.1575915955000.3960.1575988141510%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Cloud Configuration Length Cap
Title: Message Title Mahmoud Ksemtini commented on JENKINS-60409 Re: Cloud Configuration Length Cap I get the same error when trying to replay a job from the UI. 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.203466.1575915955000.3958.1575988141370%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Cloud Configuration Length Cap
Title: Message Title Mahmoud Ksemtini updated an issue Jenkins / JENKINS-60409 Cloud Configuration Length Cap Change By: Mahmoud Ksemtini Attachment: Screenshot 2019-12-10 at 15.27.37.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.203466.1575915955000.3955.1575988140880%40Atlassian.JIRA.
[JIRA] (JENKINS-60420) Skip notifications plugin fails after 1.0.4 release
Title: Message Title Michel Zanini created an issue Jenkins / JENKINS-60420 Skip notifications plugin fails after 1.0.4 release Issue Type: Bug Assignee: Alex Dubrouski Components: skip-notifications-trait-plugin Created: 2019-12-10 14:37 Environment: Install Gihub and Bitbucket on the same Jenkins instance Priority: Minor Reporter: Michel Zanini If you have Github and Bitbucket installed as plugins and you use Skip Notifications Trait you will get this error after `1.0.4` release: ERROR: Found multiple extensions which provide method skipNotificationsTrait with arguments []: [[com.cloudbees.jenkins.plugins.bitbucket.notifications.SkipNotificationsTrait, org.jenkinsci.plugins.github.notifications.SkipNotificationsTrait]]
[JIRA] (JENKINS-60420) Skip notifications plugin fails after 1.0.4 release
Title: Message Title
Michel Zanini updated an issue
Jenkins / JENKINS-60420
Skip notifications plugin fails after 1.0.4 release
Change By:
Michel Zanini
If you have Github and Bitbucket installed as plugins and you use Skip Notifications Trait you will get this error after `1.0.4` release: {code:java}ERROR: Found multiple extensions which provide method skipNotificationsTrait with arguments []: [[com.cloudbees.jenkins.plugins.bitbucket.notifications.SkipNotificationsTrait, org.jenkinsci.plugins.github.notifications.SkipNotificationsTrait]]{code} This problem was introduced by this PR:[https://github.com/jenkinsci/skip-notifications-trait-plugin/pull/5]
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://grou
[JIRA] (JENKINS-20992) possible endless loop getting index for interface hudson.Extension from classLoader hudson.PluginManager$UberClassLoader
Title: Message Title Jesse Glick resolved as Cannot Reproduce Do not recall seeing this recently. Jenkins / JENKINS-20992 possible endless loop getting index for interface hudson.Extension from classLoader hudson.PluginManager$UberClassLoader Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...
[JIRA] (JENKINS-60404) Warning exception after upgrading to Folders 6.10
Title: Message Title Michel Zanini commented on JENKINS-60404 Re: Warning exception after upgrading to Folders 6.10 This is a duplicate of JENKINS-60393 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.203459.1575899541000.3969.1575988860341%40Atlassian.JIRA.
[JIRA] (JENKINS-38354) Failure to resume a wrapper step leads to hanging build
Title: Message Title Jesse Glick resolved as Won't Fix After JENKINS-39134 we are not using Guice in this way so this is probably obsolete. Jenkins / JENKINS-38354 Failure to resume a wrapper step leads to hanging build Change By: Jesse Glick Status: Open Resolved Assignee: Kohsuke Kawaguchi Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You
[JIRA] (JENKINS-59227) Global Pipeline Libraries configuration lost
Title: Message Title Devin Nusbaum commented on JENKINS-59227 Re: Global Pipeline Libraries configuration lost Based on the comments here, in JENKINS-57171, and JENKINS-59145 (which looks like the same issue but when configuring a Pipeline job from SCM instead of a shared library SCM), the issue seems to be specific to Permissive Script Security 0.5 (I think this is the only change in that release), so I am changing the component. There may be some issue in the interaction between Permission Script Security and Script Security, but I'm not sure. If anyone has any relevant error messages or stack traces in your Jenkins logs, or any error messages in your browser console, that would be helpful. 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.201684.1567609146000.3973.1575990060237%40Atlassian.JIRA.
[JIRA] (JENKINS-59227) Global Pipeline Libraries configuration lost
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-59227 Global Pipeline Libraries configuration lost Change By: Devin Nusbaum Component/s: permissive-script-security-plugin Component/s: core Component/s: 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.201684.1567609146000.3981.1575990180608%40Atlassian.JIRA.
[JIRA] (JENKINS-60216) Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible
Title: Message Title Bogomil Vasilev commented on JENKINS-60216 Re: Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible Yes, the builds continue working as usual. The Node plugin is also working, despite the conversion warning. I just don't know how to fix it in order to suppress the message from showing up. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203189.1574194043000.3994.1575990541164%40Atlassian.JIRA.
[JIRA] (JENKINS-60404) Warning exception after upgrading to Folders 6.10
Title: Message Title Francisco Fernández closed an issue as Duplicate Jenkins / JENKINS-60404 Warning exception after upgrading to Folders 6.10 Change By: Francisco Fernández Status: Open Closed Resolution: Duplicate 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.203459.1575899541000.3992.1575990541010%40Atlassian.JIRA.
[JIRA] (JENKINS-23496) Notify user that put slave temporarily offline that it has become idle
Title: Message Title Kevin Cruise commented on JENKINS-23496 Re: Notify user that put slave temporarily offline that it has become idle Oliver Gondža This is occurring again in version 1.16, should this ticket be re-opened or a new one created? 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.155811.1403205036000.3996.1575990900312%40Atlassian.JIRA.
[JIRA] (JENKINS-23496) Notify user that put slave temporarily offline that it has become idle
Title: Message Title Kevin Cruise edited a comment on JENKINS-23496 Re: Notify user that put slave temporarily offline that it has become idle [~olivergondza] This is occurring again no longer working in version 1.16, should this ticket be re-opened or a new one created? 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.155811.1403205036000.4000.1575991020450%40Atlassian.JIRA.
[JIRA] (JENKINS-60421) NPE when saving Jenkins configuration if audit console logger is added in JCASC
Title: Message Title Alexander Smirnov created an issue Jenkins / JENKINS-60421 NPE when saving Jenkins configuration if audit console logger is added in JCASC Issue Type: Bug Assignee: Pierre Beitz Components: audit-trail-plugin Created: 2019-12-10 15:27 Priority: Minor Reporter: Alexander Smirnov Audit Trail plugin 3.0 is installed in Jenkins 2.190.3. Audit console logger is added in JCASC block: audit-trail: logBuildCause: true loggers: - console: dateFormat: "-MM-dd HH:mm:ss:SSS" logPrefix: "audit" output: STD_OUT pattern: ".*/(?:configSubmit|doDelete|postBuildResult|enable|disable|cancelQueue|stop|toggleLogKeep|doWipeOutWorkspace|createItem|createView|toggleOffline|cancelQuietDown|quietDown|restart|exit|safeExit)" The following exception is thrown when clicking on save or apply button: java.lang.NullPointerException at hudson.plugins.audit_trail.ConsoleAuditLogger.log(ConsoleAuditLogger.java:49) at hudson.plugins.audit_trail.AuditTrailFilter.onRequest(AuditTrailFilter.java:129) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:105) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(Servlet
[JIRA] (JENKINS-60422) keep all build history when using jiraSendBuildInfo
Title: Message Title walid boussafa updated an issue Jenkins / JENKINS-60422 keep all build history when using jiraSendBuildInfo Change By: walid boussafa Summary: keep all build history when using jiraSendBuildInfo 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.203494.157599220.4010.1575992221351%40Atlassian.JIRA.
[JIRA] (JENKINS-60422) keep all build history
Title: Message Title walid boussafa created an issue Jenkins / JENKINS-60422 keep all build history Issue Type: Improvement Assignee: Rafal Myslek Components: atlassian-jira-software-cloud-plugin Created: 2019-12-10 15:36 Priority: Major Reporter: walid boussafa right now, jiraSendBuildInfo only keep the status of the last build. it would be very practical to provide an option to keep all build history. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60422) keep all build history when using jiraSendBuildInfo
Title: Message Title walid boussafa updated an issue Jenkins / JENKINS-60422 keep all build history when using jiraSendBuildInfo Change By: walid boussafa right now, jiraSendBuildInfo only keep the status of the last build.it would be very practical to provide an option to keep all full build history. 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.203494.157599220.4012.1575992280400%40Atlassian.JIRA.
[JIRA] (JENKINS-60423) Powershell fails when the script starts with 'CmdletBinding' attribut
Title: Message Title Aleksander Kasprzyk created an issue Jenkins / JENKINS-60423 Powershell fails when the script starts with 'CmdletBinding' attribut Issue Type: Bug Assignee: Unassigned Components: powershell-plugin Created: 2019-12-10 15:58 Labels: powershell Priority: Major Reporter: Aleksander Kasprzyk Hi, Since upgrade to the latest version of PowerShell Plugin (1.4) a lot of my scripts does not work any more. Especially when inline or script files starts with the 'CmdletBinding' attribut. [workspace] $ powershell.exe -NoProfile -NonInteractive -ExecutionPolicy Bypass -File C:\Users\ATHICS~1\AppData\Local\Temp\jenkins8862236051379677851.ps1 Au caractŠre C:\Users\AthicService\AppData\Local\Temp\jenkins8862236051379677851.ps1:3 : 1 + [CmdletBinding()] ~+ ~~ Attribut inattendu ®ÿCmdletBindingÿ¯. Au caractŠre C:\Users\AthicService\AppData\Local\Temp\jenkins8862236051379677851.ps1:4 : 1 + param([switch]$Elevated ~+ ~~ Jeton inattendu ®ÿparamÿ¯ dans l'_expression_ ou l'instruction. + CategoryInfo : ParserError: ( [], ParentContainsErrorRecordException + FullyQualifiedErrorId : UnexpectedAttribute Build step 'PowerShell' marked build as failure As I have a lot of PS scripts like that, I have to downgrade to 1.3 version.
[JIRA] (JENKINS-60110) Update AWS Java SDK
Title: Message Title Chris Kilding commented on JENKINS-60110 Re: Update AWS Java SDK I recently got a request to downgrade the AWS SDK dependency on the Secrets Manager Credentials Provider plugin, to make it compatible with Cloudbees Core 2.176.4.3. The SDK downgrade also broke support for fine-grained IAM policies in that plugin. I’ve already received a bug report from a user affected by this, so this needs fixing soon. 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.202956.1573228427000.4016.1575993960357%40Atlassian.JIRA.
[JIRA] (JENKINS-60394) Can't load http://localhost:8080
Title: Message Title Jorge Cordoba updated JENKINS-60394 Jenkins / JENKINS-60394 Can't load http://localhost:8080 Change By: Jorge Cordoba 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.203448.1575669122000.4018.1575994500753%40Atlassian.JIRA.
[JIRA] (JENKINS-60394) Can't load http://localhost:8080
Title: Message Title Jorge Cordoba updated JENKINS-60394 Jenkins / JENKINS-60394 Can't load http://localhost:8080 Change By: Jorge Cordoba Status: In Review Resolved 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 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.203448.1575669122000.4020.1575994500960%40Atlassian.JIRA.
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title Karl Wirth commented on JENKINS-51552 Re: Cannot replay pipelines - files are read-only Hi Erez Arbell - I have to thank the developers for this. Your definition was mostly correct. For ModernSCM the 'identifier' should be '@' followed by the changelist number. For example: def lib = library( identifier : '@23312',retriever: modernSCM(globalLib(charset: 'none', credential: 'JenkinsMaster', id: '9bb4320c-c31c-46ce-8c5f-68872f519067', path: '//depot/lib_autoload/libs/...'))) Note that it also doesnt allow you to specify the workspace path so I specified the depot path just above 'src' which seems to work for me. 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.190940.1527360591000.4022.1575994620305%40Atlassian.JIRA.
[JIRA] (JENKINS-60110) Update AWS Java SDK
Title: Message Title Chris Kilding edited a comment on JENKINS-60110 Re: Update AWS Java SDK I recently got a request to downgrade the AWS SDK dependency on the Secrets Manager Credentials Provider plugin, to make it compatible with Cloudbees Core 2.176.4.3. I imagine the SSM plugin would have the constraint when used with Cloudbees Core. The SDK downgrade also broke support for fine-grained IAM policies in that my plugin. And I’ve already received a bug report from a user affected by this , so this .So Cloudbees Core needs fixing soon its AWS SDK dependency upgraded ASAP, to enable both of our plugins to upgrade in turn . 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.202956.1573228427000.4043.1575995340153%40Atlassian.JIRA.
[JIRA] (JENKINS-60110) Update AWS Java SDK
Title: Message Title Chris Kilding edited a comment on JENKINS-60110 Re: Update AWS Java SDK I recently got a request to downgrade the AWS SDK dependency on the Secrets Manager Credentials Provider plugin, to make it compatible with Cloudbees Core 2.176.4.3. I imagine any other plugin that uses AWS SDK, including the SSM plugin one, would have the same constraint when used with Cloudbees Core.The SDK downgrade also broke support for fine-grained IAM policies in my plugin . And , and I’ve already received a bug report from a user affected by this.So Cloudbees Core needs its AWS SDK dependency upgraded ASAP, to enable both of our plugins to upgrade in turn. 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.202956.1573228427000.4046.1575995520185%40Atlassian.JIRA.
