[JIRA] (JENKINS-50841) When I check become and save, but it is not reflected.
Title: Message Title Dennis Philpot commented on JENKINS-50841 Re: When I check become and save, but it is not reflected. Hi, this bug is sill around, the only workaround we've found was to add the -b parameter to the Additional parameters in the Advanced section. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57334) "Run on planned host" from Build section not working
Title: Message Title Daniel Gront commented on JENKINS-57334 Re: "Run on planned host" from Build section not working Govind Sureka, was this tested on the latest version of the plugin as well? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57334) "Run on planned host" from Build section not working
Title: Message Title Daniel Gront assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-57334 "Run on planned host" from Build section not working Change By: Daniel Gront Assignee: Daniel Gront Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57334) "Run on planned host" from Build section not working
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-57334 "Run on planned host" from Build section not working Change By: Daniel Gront Labels: UFT Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57334) "Run on planned host" from Build section not working
Title: Message Title Govind Sureka created an issue Jenkins / JENKINS-57334 "Run on planned host" from Build section not working Issue Type: Bug Assignee: Daniel Gront Components: hp-application-automation-tools-plugin Created: 2019-05-06 03:02 Environment: CloudBees Jenkins Enterprise-2.150.3.2-rollong Plugin: Micro Focus Application Automation tools: 5.2 ALM: 12.55 Priority: Minor Reporter: Govind Sureka Integrated UFT Automation test cases from ALM to CloudBees Jenkins Enterprise using Add Ins: Micro Focus Application Automation Tools--> Execute HPE functional tests from HPE ALM. When designing the job assign 'Label _expression_' in the 'General' section. In the Build section click on 'Advanced...' option and select 'Run on planned host' from drop down of 'Run mode'. Save this job. When we run this job on any workstation it ran but no test case gets executed Test set: X_REGRESSION, finished at 05/05/2019 22:59:49 Run status: Job succeeded, total tests: 5, succeeded: 0, failures: 0, errors: 0 Unknown: Unknown: Unknown: Unknown: Unknown:
[JIRA] (JENKINS-56909) Allow to unlock/lock keychain on demand
Title: Message Title Kazuhide Takahashi edited a comment on JENKINS-56909 Re: Allow to unlock/lock keychain on demand [~ma]This is one of my proposal for a solution.I've always thought that the information about the Xcode Plugin's keychain should be in "Creditals" instead of "Configure System".By setting the keychain information in "Credencials" and making them compatible with "Credentials Binding Plugin", it becomes easier to manipulate the keychain even in your own script as follows: .[ link title JENKINS-57333 |https://issues.jenkins-ci.org/browse/JENKINS-57333] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56909) Allow to unlock/lock keychain on demand
Title: Message Title Kazuhide Takahashi commented on JENKINS-56909 Re: Allow to unlock/lock keychain on demand Mathieu Delrocq This is one of my proposal for a solution. I've always thought that the information about the Xcode Plugin's keychain should be in "Creditals" instead of "Configure System". By setting the keychain information in "Credencials" and making them compatible with "Credentials Binding Plugin", it becomes easier to manipulate the keychain even in your own script as follows: . link title Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57333) Move macOS keychain information from "Configure System" to "Credentials".
Title: Message Title Kazuhide Takahashi created an issue Jenkins / JENKINS-57333 Move macOS keychain information from "Configure System" to "Credentials". Issue Type: New Feature Assignee: Unassigned Components: xcode-plugin Created: 2019-05-06 01:58 Labels: plugin security configuration Priority: Minor Reporter: Kazuhide Takahashi This is a proposal. I would like to change the macOS keychain information defined in "Configure System" in the current Xcode Plugin to defined in "Credentials". Because "macOS key chain information" is credential information in the first place. And if it is credential, it will be easy to use in other places such as shell script. Add Comment
[JIRA] (JENKINS-57330) git deploy dealing with locked files
Title: Message Title Jie Shen commented on JENKINS-57330 Re: git deploy dealing with locked files Thanks for reporting this, I will investigate it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57330) git deploy dealing with locked files
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-57330 git deploy dealing with locked files Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57332) PipelineMavenPluginDao#getGeneratedArtifacts() mixes artifact version and baseVersion
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-57332 PipelineMavenPluginDao#getGeneratedArtifacts() mixes artifact version and baseVersion Issue Type: Bug Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2019-05-05 22:22 Priority: Minor Reporter: Cyrille Le Clerc The MavenArtifact returned by org.jenkinsci.plugins.pipeline.maven.dao.PipelineMavenPluginDao#getGeneratedArtifacts() mix artifact.version and artifact.baseVersion. Add Comment This
[JIRA] (JENKINS-57331) Installation on Mac OS 10.14.4 fails
Title: Message Title Arkady Lokhovitskiy created an issue Jenkins / JENKINS-57331 Installation on Mac OS 10.14.4 fails Issue Type: Bug Assignee: Unassigned Attachments: Screenshot 2019-05-05 at 23.29.51.png Components: _unsorted Created: 2019-05-05 21:52 Environment: Jenkins 2.164.2 Mac OS 10.14.4 Java 8 121 Labels: jenkins installation Priority: Major Reporter: Arkady Lokhovitskiy A "stable" installer for MacOS fails most likely at the validation with a generic error message you can see in the screenshot. A war file in /Applications/Jenkins is copied. That's all. Add Comment
[JIRA] (JENKINS-54010) Support two levels of parallelity in stages
Title: Message Title Alaiksei Savanchuk commented on JENKINS-54010 Re: Support two levels of parallelity in stages Shahaf Duenyas I'm not sure that you are talking about the BlueOcean plugin. Jenkins pipeline already supports multiple levels of parallelism, this is only about Blue Ocean's UI Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Sven Strittmatter commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records I digged into it: 0x3 seems to be a control character (ETX) which is not allowed in XML. There is one in the parsed log output. Could you please look into the Darcs XML log output at given line/column mentioned at the bottom of the exception? Maybe darcs is screwing up the log output? I'm not sure if I can handle this malformed XML input in an useful way. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32679) Audit Trail plugin fails to track queue item api calls
Title: Message Title Pierre Beitz closed an issue as Cannot Reproduce Jenkins / JENKINS-32679 Audit Trail plugin fails to track queue item api calls Change By: Pierre Beitz Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32679) Audit Trail plugin fails to track queue item api calls
Title: Message Title Pierre Beitz commented on JENKINS-32679 Re: Audit Trail plugin fails to track queue item api calls Cannot reproduce on the latest version of the plugin. Closing, feel free to reopen if I missed something. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32679) Audit Trail plugin fails to track queue item api calls
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-32679 Audit Trail plugin fails to track queue item api calls Change By: Pierre Beitz Assignee: Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37273) can not install plugin audit-trail
Title: Message Title Pierre Beitz commented on JENKINS-37273 Re: can not install plugin audit-trail Serg Pr I'm a bit late to the party, I guess/hope this issue is not reproduced anymore? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43161) Audit Trail Plugin : Failed Loading plugin Audit Trail v2.2 (audit-trail)
Title: Message Title Pierre Beitz closed an issue as Cannot Reproduce Jenkins / JENKINS-43161 Audit Trail Plugin : Failed Loading plugin Audit Trail v2.2 (audit-trail) Change By: Pierre Beitz Status: Open Closed Assignee: Pierre Beitz Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43161) Audit Trail Plugin : Failed Loading plugin Audit Trail v2.2 (audit-trail)
Title: Message Title Pierre Beitz commented on JENKINS-43161 Re: Audit Trail Plugin : Failed Loading plugin Audit Trail v2.2 (audit-trail) Closing as the issue was resolved. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53915) Audit Trail Plugin Configuration Save Error
Title: Message Title Pierre Beitz commented on JENKINS-53915 Re: Audit Trail Plugin Configuration Save Error tom b Do you still reproduce the issue? Would you mind describing the exact steps you are using to reproduce? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53915) Audit Trail Plugin Configuration Save Error
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-53915 Audit Trail Plugin Configuration Save Error Change By: Pierre Beitz Assignee: Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56108) AuditTrail java.nio.file.NoSuchFileException for log file handler
Title: Message Title Pierre Beitz commented on JENKINS-56108 Re: AuditTrail java.nio.file.NoSuchFileException for log file handler Attached a PR for the original issue. Here is the linked hpi: https://ci.jenkins.io/job/Plugins/job/audit-trail-plugin/job/PR-13/1/artifact/target/audit-trail.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56108) AuditTrail java.nio.file.NoSuchFileException for log file handler
Title: Message Title Pierre Beitz updated JENKINS-56108 Jenkins / JENKINS-56108 AuditTrail java.nio.file.NoSuchFileException for log file handler Change By: Pierre Beitz Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56108) AuditTrail java.nio.file.NoSuchFileException for log file handler
Title: Message Title Pierre Beitz started work on JENKINS-56108 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56108) AuditTrail java.nio.file.NoSuchFileException for log file handler
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-56108 AuditTrail java.nio.file.NoSuchFileException for log file handler Change By: Pierre Beitz Assignee: Tomasz Sęk Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56108) AuditTrail java.nio.file.NoSuchFileException for log file handler
Title: Message Title Pierre Beitz commented on JENKINS-56108 Re: AuditTrail java.nio.file.NoSuchFileException for log file handler Apologies, I missed the bug report, somehow the plugin default assignee wasn't changed on plugin ownership transfer. Regarding the reported issue, it appears that the path you are specifying doesn't exist on the host and the FileHandler used by the plugin is not able to create the intermediate missing directories. I'll make a fix for this, in the meantime, workaround is to manually create the intermediate directories. After further testing, it appears that the initial configuration of this plugin does not work (I deployed Jenkins using a helm chart, so the plugin was configured as code). After the deployment, I am getting the same error when performing some action that would trigger the plugin to create a log file. Then, I went into the Jenkins Configure System UI and manually update one of the values in the plugin configuration, say, Log File Size, save the configuration, then the error goes away, and the plugin started working correctly Sylvia Qi this description makes me think that you are describing a different issue, with an incompatibility between the jcasc plugin in the audit trail plugin. I can see that you logged JENKINS-57232 that seems to cover the issue, I propose to discuss this specific issue in there and keep JENKINS-56108 for the issue reported initially. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54786) Launch command should include an env var for the name of the node
Title: Message Title Josh Phillips assigned an issue to Harold Jackson Jenkins / JENKINS-54786 Launch command should include an env var for the name of the node Change By: Josh Phillips Assignee: Josh Soref Harold Jackson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53167) Add ability to always run particular stages when restarting
Title: Message Title Jonathan Kuleff commented on JENKINS-53167 Re: Add ability to always run particular stages when restarting I would really like this feature too. I have 2 use cases for this feature, the first is I would like to send a notification when a pipeline starts regardless of how it was triggered, there is no real nice way to do this currently for stage restarts. The second use case is I want to load some config/metadata that was generated from a skipped stage allowing me to restart from any stage, however because I can't know which will be the restarted stage I need to try load it in every stage and this just makes my Jenkinsfile look unnecessarily cluttered. In both cases having a pipeline pre stage would simplify my Jenkinsfile and declutter it making it easier to read and maintain Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57218) NPE from SymbolLookup after job-dsl update without configuration-as-code
Title: Message Title Joseph Petersen commented on JENKINS-57218 Re: NPE from SymbolLookup after job-dsl update without configuration-as-code Jesse Glick jobdsl #1175 should hopefully fix it unless you are referring to another issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54010) Support two levels of parallelity in stages
Title: Message Title Shahaf Duenyas commented on JENKINS-54010 Re: Support two levels of parallelity in stages This feature will help us a lot. Multiple levels of parallelizm are currently supported only by creating new jobs, which is a poor solution given that Jenkins groovy supports it out of the box. I'm sure this feature will help a lot of users since many applications test themselves on multiple platforms today. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57330) git deploy dealing with locked files
Title: Message Title zirain he created an issue Jenkins / JENKINS-57330 git deploy dealing with locked files Issue Type: Improvement Assignee: Azure DevOps Components: azure-app-service-plugin Created: 2019-05-05 09:51 Priority: Minor Reporter: zirain he Hey guys, I'm using this plugin to deploy my aspnetcore project to Azure App Service. Some times the locked files issue make the deployment fails. Is there any setting to support App_offline mode or other way to avoid this? Add Comment This
[JIRA] (JENKINS-57329) Should support namespace
Title: Message Title Share Cheng created an issue Jenkins / JENKINS-57329 Should support namespace Issue Type: New Feature Assignee: James Nord Components: kubernetes-credentials-provider-plugin Created: 2019-05-05 07:50 Priority: Major Reporter: Share Cheng This plugin seems only to watch secret from one namespace. It is better to watch secret from all namespaces. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57328) Should not use secret name as credential ID
Title: Message Title
Share Cheng created an issue
Jenkins / JENKINS-57328
Should not use secret name as credential ID
Issue Type:
Bug
Assignee:
James Nord
Components:
kubernetes-credentials-provider-plugin
Created:
2019-05-05 07:22
Priority:
Major
Reporter:
Share Cheng
Currently, this plugin will use secret's name as the credential ID to create a credential. It may cause problems when there are secrets have the same name but in different namespaces. It is better to use namespace and name to generate the credential ID - like '{namespace}-{name}'.
Add Comment
