[JIRA] (JENKINS-38898) Managed artifacts fails to upload to S3 - no errors logged
Title: Message Title Thomy Moore commented on JENKINS-38898 Re: Managed artifacts fails to upload to S3 - no errors logged I got it running. I reentered the aws s3 creds in the jenkins configuration, mysteriously they were empty. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-31871) Jenkins improperly handles single quotes in item names
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31871 Jenkins improperly handles single quotes in item names Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-31871) Jenkins improperly handles single quotes in item names
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31871 Re: Jenkins improperly handles single quotes in item names Code changed in jenkins User: Felix Belzunce Arcos Path: core/src/main/java/hudson/util/FormValidation.java http://jenkins-ci.org/commit/jenkins/bee66ede31d45b9d0814e4a45cbf2223585817e2 Log: [FIXED JENKINS-31871] Properly handle single quotes in item names (#1943) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-35967) Jenkins allows creating users like " system " or "anonymous "
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35967 Re: Jenkins allows creating users like " system " or "anonymous " Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/User.java core/src/test/java/hudson/model/UserTest.java http://jenkins-ci.org/commit/jenkins/7d886ce9fbcb04b627aed34be8f6382f42cf788c Log: [FIXED JENKINS-35967] - Make User#isIdOrFullnameAllowed() more robust against restricted usernames (#2413) This change hardens username verification in user creation commands. See the issue to get rexamples. https://issues.jenkins-ci.org/browse/JENKINS-35967 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-35967) Jenkins allows creating users like " system " or "anonymous "
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-35967 Jenkins allows creating users like " system " or "anonymous " Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-36859) EZ-Templates support MultiBranch plugin
Title: Message Title Marc Carter updated an issue Jenkins / JENKINS-36859 EZ-Templates support MultiBranch plugin Change By: Marc Carter Priority: Critical Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-32267) Allow replacement based on parameters at creation time
Title: Message Title Marc Carter updated an issue Jenkins / JENKINS-32267 Allow replacement based on parameters at creation time Change By: Marc Carter Priority: Major Trivial Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-39009) User#isIdOrFullnameAllowed() should disallow system names with special symbols
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-39009 User#isIdOrFullnameAllowed() should disallow system names with special symbols Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Oct/15 11:55 PM Priority: Minor Reporter: Oleg Nenashev Follow-up to JENKINS-35967 In https://github.com/jenkinsci/jenkins/pull/2413 James Nord said that usernames with special symbols should be filtered as well. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-38978) Plugin needs updating to address SECURITY-170
Title: Message Title Ebrahim Moshaya updated an issue Jenkins / JENKINS-38978 Plugin needs updating to address SECURITY-170 Change By: Ebrahim Moshaya Version 1.7 of the [Matrix Project Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Project+Plugin]JENKINS-34758 Parameters visibility in child builds (related to SECURITY-170)Broke the maven-metadata-plugin in that the parameters are no longer passed down to child matrix jobs. https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-31612) Stack trace shown with suppress-stack-trace plugin installed
Title: Message Title Ivan Fernandez Calvo updated JENKINS-31612 Jenkins / JENKINS-31612 Stack trace shown with suppress-stack-trace plugin installed Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-31612) Stack trace shown with suppress-stack-trace plugin installed
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-31612 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-31612) Stack trace shown with suppress-stack-trace plugin installed
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-31612 Re: Stack trace shown with suppress-stack-trace plugin installed tested now all access denied exceptions are controlled. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-31612) Stack trace shown with suppress-stack-trace plugin installed
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-31612 Re: Stack trace shown with suppress-stack-trace plugin installed tested now all access denied exceptions are controlled. I made the [PR|https://github.com/jenkinsci/reverse-proxy-auth-plugin/pull/28] with the fix. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38142) Posibility to specify JIRA site in jenkins pipeline project
Title: Message Title Vitalius Marcinkevicius assigned an issue to Vitalius Marcinkevicius Jenkins / JENKINS-38142 Posibility to specify JIRA site in jenkins pipeline project Change By: Vitalius Marcinkevicius Assignee: Vitalius Marcinkevicius Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38967) job-params select for local override grayed out.
Title: Message Title Marc Carter updated an issue Jenkins / JENKINS-38967 job-params select for local override grayed out. Removing Blocker status as it messes the kanban board Change By: Marc Carter Priority: Blocker Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38755) Merge Choice Parameter values more intelligently
Title: Message Title Marc Carter started work on JENKINS-38755 Change By: Marc Carter Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-23786) Permit "Execute shell" jobs to return 2 for "unstable"
Title: Message Title Oleg Nenashev commented on JENKINS-23786 Re: Permit "Execute shell" jobs to return 2 for "unstable" The fix also includes https://github.com/jenkinsci/jenkins/pull/2563/commits/359548efa074f9ed3537552f5f9f2b51faf33e25 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-23786) Permit "Execute shell" jobs to return 2 for "unstable"
Title: Message Title Daniel Beck resolved as Fixed Fixed towards 2.26 Jenkins / JENKINS-23786 Permit "Execute shell" jobs to return 2 for "unstable" Change By: Daniel Beck Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Jason Davis edited a comment on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin I've noticed this issue with the P4 plugin. The overall project changes list is OK, but the change report for a single build is still showing the html for the link instead of actually showing the link. !p4-changes.png|thumbnail!jenkins 2.25, JIRA plugin 2.2.1, p4 plugin 1.4.8 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Jason Davis commented on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin I've noticed this issue with the P4 plugin. The overall project changes list is OK, but the change report for a single build is still showing the html for the link instead of actually showing the link. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-29075 List of changes escapes HTML output of jira-plugin Change By: Jason Davis Attachment: p4-changes.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-32004) HP Automation Tools Unable to Export Job Results to QC
Title: Message Title Hari Nallani edited a comment on JENKINS-32004 Re: HP Automation Tools Unable to Export Job Results to QC Any Update on this?I still face the issue with latest plug-inTestNG Reports Processing: STARTLooking for TestNG results report in workspace using pattern: **/testng-results.xmlSaving reports...Processing '/Users/Shared/Jenkins/Home/jobs/XXXTestAutomation/builds/97/testng/testng-results.xml'TestNG Reports Processing: FINISHINFO: 'Upload test result to ALM' Post Build Step is being invoked.INFO: 1 test result file found.INFO: Start to upload /Users/Shared/Jenkins/Home/jobs/XXXTestAutomation/builds/97/XXXTestAutomation$XXXTestAutomation/junitResult.xmlINFO: Start to parse file: /Users/Shared/Jenkins/Home/jobs/XXXTestAutomation/builds/97/XXXTestAutomation$XXXAutomation/junitResult.xmlINFO: parse resut file succeed.INFO: Start to login to ALM Server.Logged in successfully to ALM Server https://qualitycenter. whirlpool XX .com/qcbin/ using XXINFO: Checking test folder...INFO: Checking testset folder...INFO: Uploading ALM Entities...Failed to create Entity:test-sets:subtype-id=hp.qc.test-set.externalname=TestSuiteparent-id=9980WARN: there's exception while uploading /Users/Shared/Jenkins/Home/jobs/XXXTestAutomation/builds/97/XXXAutomation$XXXAutomation/junitResult.xml.INFO: 'Upload test result to ALM' Completed.Build step 'Upload test result to ALM' changed build result to UNSTABLEFinished: UNSTABLE Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-32004) HP Automation Tools Unable to Export Job Results to QC
Title: Message Title Hari Nallani commented on JENKINS-32004 Re: HP Automation Tools Unable to Export Job Results to QC Any Update on this? I still face the issue with latest plug-in TestNG Reports Processing: START Looking for TestNG results report in workspace using pattern: **/testng-results.xml Saving reports... Processing '/Users/Shared/Jenkins/Home/jobs/XXXTestAutomation/builds/97/testng/testng-results.xml' TestNG Reports Processing: FINISH INFO: 'Upload test result to ALM' Post Build Step is being invoked. INFO: 1 test result file found. INFO: Start to upload /Users/Shared/Jenkins/Home/jobs/XXXTestAutomation/builds/97/XXXTestAutomation$XXXTestAutomation/junitResult.xml INFO: Start to parse file: /Users/Shared/Jenkins/Home/jobs/XXXTestAutomation/builds/97/XXXTestAutomation$XXXAutomation/junitResult.xml INFO: parse resut file succeed. INFO: Start to login to ALM Server. Logged in successfully to ALM Server https://qualitycenter.whirlpool.com/qcbin/ using XX INFO: Checking test folder... INFO: Checking testset folder... INFO: Uploading ALM Entities... Failed to create Entity:test-sets:subtype-id=hp.qc.test-set.externalname=TestSuiteparent-id=9980 WARN: there's exception while uploading /Users/Shared/Jenkins/Home/jobs/XXXTestAutomation/builds/97/XXXAutomation$XXXAutomation/junitResult.xml. INFO: 'Upload test result to ALM' Completed. Build step 'Upload test result to ALM' changed build result to UNSTABLE Finished: UNSTABLE Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and
[JIRA] (JENKINS-39008) Create PR jobs inside a PR folder for multi branch pipeline plugin
Title: Message Title Pedro Algarvio updated an issue Jenkins / JENKINS-39008 Create PR jobs inside a PR folder for multi branch pipeline plugin Change By: Pedro Algarvio Component/s: workflow-multibranch-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-39008) Create PR jobs inside a PR folder for multi branch pipeline plugin
Title: Message Title Pedro Algarvio created an issue Jenkins / JENKINS-39008 Create PR jobs inside a PR folder for multi branch pipeline plugin Issue Type: New Feature Assignee: Unassigned Components: pipeline Created: 2016/Oct/15 6:34 PM Priority: Minor Reporter: Pedro Algarvio Currently, the multibranch pipeline plugin creates all jobs inside the project folder. Optionally, it would be greater to make the PR jobs be created inside a nested folder, PR(for example) Add Comment This message was
[JIRA] (JENKINS-23244) Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master
Title: Message Title SCM/JIRA link daemon commented on JENKINS-23244 Re: Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master Code changed in jenkins User: Akbashev Alexander Path: core/src/main/resources/hudson/model/BuildTimelineWidget/control.jelly http://jenkins-ci.org/commit/jenkins/2a0ac4f0989407a20e277444a7737e9c5f7ea78a Log: [FIX JENKINS-23244] Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master (#2584) Mainly commit are doing two things: 1) Show only selected (visible) builds 2) Query build one-by-one - not it parallel Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38650) Typos in CLI commands: "comama-separated"
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-38650 Typos in CLI commands: "comama-separated" Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38650) Typos in CLI commands: "comama-separated"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38650 Re: Typos in CLI commands: "comama-separated" Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/cli/CLICommand.java core/src/main/java/hudson/cli/CancelQuietDownCommand.java core/src/main/java/hudson/cli/ClearQueueCommand.java core/src/main/java/hudson/cli/ConnectNodeCommand.java core/src/main/java/hudson/cli/DeleteJobCommand.java core/src/main/java/hudson/cli/DeleteNodeCommand.java core/src/main/java/hudson/cli/DeleteViewCommand.java core/src/main/java/hudson/cli/DisconnectNodeCommand.java core/src/main/java/hudson/cli/OfflineNodeCommand.java core/src/main/java/hudson/cli/OnlineNodeCommand.java core/src/main/java/hudson/cli/QuietDownCommand.java core/src/main/java/hudson/cli/ReloadConfigurationCommand.java core/src/main/java/hudson/cli/ReloadJobCommand.java core/src/main/java/hudson/cli/WaitNodeOfflineCommand.java core/src/main/java/hudson/cli/WaitNodeOnlineCommand.java test/src/test/java/hudson/cli/ConnectNodeCommandTest.java test/src/test/java/hudson/cli/DeleteJobCommandTest.java test/src/test/java/hudson/cli/DeleteNodeCommandTest.java test/src/test/java/hudson/cli/DeleteViewCommandTest.java test/src/test/java/hudson/cli/DisconnectNodeCommandTest.java test/src/test/java/hudson/cli/OfflineNodeCommandTest.java test/src/test/java/hudson/cli/OnlineNodeCommandTest.java test/src/test/java/hudson/cli/ReloadJobCommandTest.java http://jenkins-ci.org/commit/jenkins/b50034c9bffb704acfce0bc49d99855b689eace6 Log: [FIXED JENKINS-38650] - Cleanup spelling in CLi commands + Javadoc updates (#2571) [FIXED JENKINS-38650] - Cleanup spelling in CLi commands. Also adds some javadoc and since definitions. JENKINS-38650 - Move common warning message to the constant JENKINS-38650 - DeleteViewCommand should also use the constant string JENKINS-38650 - Rename the constant in order to make the name more explicit Add Comment
[JIRA] (JENKINS-35642) Multibranch plugin is missing "Discard Old Builds"
Title: Message Title
Robert Paasche edited a comment on JENKINS-35642
Re: Multibranch plugin is missing "Discard Old Builds"
Take a look at the comment:https://issues.jenkins-ci.org/browse/JENKINS-34738?focusedCommentId=263489=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-263489{ qoute quote }You simply need to add to your pipline somthing like:properties [[$class: 'BuildDiscarderProperty', strategy: [$class: 'LogRotator', artifactDaysToKeepStr: '20', artifactNumToKeepStr: '30', daysToKeepStr: '20', numToKeepStr: '30']]]{ qoute quote }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google 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-35642) Multibranch plugin is missing "Discard Old Builds"
Title: Message Title
Robert Paasche commented on JENKINS-35642
Re: Multibranch plugin is missing "Discard Old Builds"
Take a look at the comment: https://issues.jenkins-ci.org/browse/JENKINS-34738?focusedCommentId=263489=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-263489 {qoute} You simply need to add to your pipline somthing like: properties [[$class: 'BuildDiscarderProperty', strategy: [$class: 'LogRotator', artifactDaysToKeepStr: '20', artifactNumToKeepStr: '30', daysToKeepStr: '20', numToKeepStr: '30']]]{qoute}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google 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-35642) Multibranch plugin is missing "Discard Old Builds"
Title: Message Title Pedro Algarvio commented on JENKINS-35642 Re: Multibranch plugin is missing "Discard Old Builds" I believe you can set those in the Jenkins file using set property. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-34439) Clover plugin still has problems with pipeline builds
Title: Message Title
Andor Dávid edited a comment on JENKINS-34439
Re: Clover plugin still has problems with pipeline builds
Same problem here{code}step([ $class: 'CloverPublisher', cloverReportDir: 'tests/_output/coverage', cloverReportFileName: 'coverage.xml']){code}{code}[Pipeline] stepPublishing Clover coverage report...Publishing Clover HTML report...Publishing Clover XML report...Publishing Clover coverage results...[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // wrap[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.lang.NullPointerException at hudson.plugins.clover.CloverPublisher.processCloverXml(CloverPublisher.java:250) at hudson.plugins.clover.CloverPublisher.performImpl(CloverPublisher.java:202) at hudson.plugins.clover.CloverPublisher.perform(CloverPublisher.java:167) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:59) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:221) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Finished: FAILURE{code} The error above comes with Jenkins v2.25Clover plugin v4.7.0Downgrade the Clover plugin to v4.6.0 solves the problem
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38932) Support the ScriptTrigger (via XTrigger) plugin
Title: Message Title Baptiste Mathus commented on JENKINS-38932 Re: Support the ScriptTrigger (via XTrigger) plugin Done for XTriggerCause. Just released the 2.6, it should be available for install in a few hours from now (time to propagate through mirrors and so on). Looking at XTriggerCause class, there would be ways to support underlying causes, though with the current code it would most probably require to use reflection, even to access the private attribute org.jenkinsci.lib.xtrigger.XTriggerCause#causeFrom So does not seem like the resulting code would be State Of The Art Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Andor Dávid commented on JENKINS-34439 Re: Clover plugin still has problems with pipeline builds Same problem here step([ $class: 'CloverPublisher', cloverReportDir: 'tests/_output/coverage', cloverReportFileName: 'coverage.xml' ]) [Pipeline] step Publishing Clover coverage report... Publishing Clover HTML report... Publishing Clover XML report... Publishing Clover coverage results... [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // wrap [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline java.lang.NullPointerException at hudson.plugins.clover.CloverPublisher.processCloverXml(CloverPublisher.java:250) at hudson.plugins.clover.CloverPublisher.performImpl(CloverPublisher.java:202) at hudson.plugins.clover.CloverPublisher.perform(CloverPublisher.java:167) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:59) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:221) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Finished: FAILURE Add Comment
[JIRA] (JENKINS-38932) Support the ScriptTrigger (via XTrigger) plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38932 Re: Support the ScriptTrigger (via XTrigger) plugin Code changed in jenkins User: Baptiste Mathus Path: src/main/java/org/jenkinsci/plugins/buildtriggerbadge/IconFinder.java src/main/webapp/images/xtrigger.png http://jenkins-ci.org/commit/buildtriggerbadge-plugin/9f474dc16cd46d5952a07ec87a92cade96a8d5b7 Log: JENKINS-38932 Support XTrigger Plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38932) Support the ScriptTrigger (via XTrigger) plugin
Title: Message Title Baptiste Mathus commented on JENKINS-38932 Re: Support the ScriptTrigger (via XTrigger) plugin Yeah, out of the box, it's not possible. If I want to support and show the "underlying" causes behind XTrigger, it will force me to write specific code for it. That does not mean I won't do it, it's just that it's not possible currently with the code and it may not feel very clean to me to define specific cause per cause. Until now, the code has been kept generic and the class=>icon is totally declarative. So, in the short term, I'm gonna define at least something for the global XTriggerCause using one of your icon. Will keep you posted. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-39007) Build uses Jenkinsfile from previous build/commit
Title: Message Title Peter Leibiger created an issue Jenkins / JENKINS-39007 Build uses Jenkinsfile from previous build/commit Issue Type: Bug Assignee: Andrew Bayer Attachments: build.log Components: pipeline-model-definition-plugin Created: 2016/Oct/15 12:36 PM Priority: Minor Reporter: Peter Leibiger I am not exactly sure if the model-definition plugin is at fault here or some other plugin/configuration but I discovered this after the update from 0.3 to 0.4. My develop branch has a last build with a Jenkinsfile that worked in 0.3 but is now invalid in 0.4. So I made a feature branch with an updated Jenkinsfile which build successfully and merged that into the develop branch which triggered an automatic develop build. The log shows git checking out the new (merge)-commit into the WORKSPACE@scripts folder and a global library into the WORKSPACE@libs folder. And then it starts building with the Jenkinsfile from the WORKSPACE folder which is still on the commit from the previous build with the invalid Jenkinsfile and thus the build files.
[JIRA] (JENKINS-38110) Library section within declarative syntax to explicitly load shared libraries
Title: Message Title
Peter Leibiger commented on JENKINS-38110
Re: Library section within declarative syntax to explicitly load shared libraries
Actually this works as well. Until 0.4 it worked without the import, now it doesn't.
@org.jenkinsci.plugins.workflow.libs.Library('foo@master')
import foo.Util
// doesn't work anymore
// def util = new foo.Util()
def util = new Util()
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google 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-38110) Library section within declarative syntax to explicitly load shared libraries
Title: Message Title
Peter Leibiger edited a comment on JENKINS-38110
Re: Library section within declarative syntax to explicitly load shared libraries
Not sure if this is the right issue but there are probably some things to consider for this issue.Up until version 0.4 I was able to use {{@Library}} like this:{code}@Library('foo@master')def util = new foo.Util()timestamps { pipeline {agent docker: 'maven:3-jdk-8'stages { stage('Pre-Build') {util.doSomething() } // more stages}notifications { success {util.notifyBuildStatusSuccess() } ...}}{code} Now with 0.4 it fails to find the {{@Library}} annotation, I can work around by using the FQN.But I can't get a single {{Util}} instance to work anymore, best I came up with is this: {code}@ org.jenkinsci.plugins.workflow.libs. Library('foo@master')import foo.Util// timestamps don't work anymore//timestamps { pipeline {agent docker: 'maven:3-jdk-8'stages { stage('Pre-Build') {script { def util = new Util() util.doSomething()} } // more stages}notifications { success {script { def util = new Util() util.notifyBuildStatusSuccess()} } ...} }//}{code}I tried putting the {{Util}} in {{environment}} but that throws {{sandbox.RejectedAccessException}}:{code}@ org.jenkinsci.plugins.workflow.libs. Library('foo@master')import foo.Util// timestamps don't work anymore//timestamps { pipeline {agent docker: 'maven:3-jdk-8'environment { util = new Util()}stages { stage('Pre-Build') {script { env.util.doSomething()} } // more stages}notifications { success {script { env.util.notifyBuildStatusSuccess()} } ...} }//}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38110) Library section within declarative syntax to explicitly load shared libraries
Title: Message Title
Peter Leibiger commented on JENKINS-38110
Re: Library section within declarative syntax to explicitly load shared libraries
Not sure if this is the right issue but there are probably some things to consider for this issue. Up until version 0.4 I was able to use @Library like this:
@Library('foo@master')
def util = new foo.Util()
timestamps {
pipeline {
agent docker: 'maven:3-jdk-8'
stages {
stage('Pre-Build') {
util.doSomething()
}
// more stages
}
notifications {
success {
util.notifyBuildStatusSuccess()
}
...
}
}
Now with 0.4 it fails to find the @Library annotation, I can work around by using the FQN. But I can't get a single Util instance to work anymore, best I came up with is this:
@Library('foo@master')
import foo.Util
// timestamps don't work anymore
//timestamps {
pipeline {
agent docker: 'maven:3-jdk-8'
stages {
stage('Pre-Build') {
script {
def util = new Util()
util.doSomething()
}
}
// more stages
}
notifications {
success {
script {
def util = new Util()
util.notifyBuildStatusSuccess()
}
}
...
}
}
//}
I tried putting the Util in environment but that throws sandbox.RejectedAccessException:
@Library('foo@master')
import foo.Util
// timestamps don't work anymore
//timestamps {
pipeline {
agent docker: 'maven:3-jdk-8'
environment {
util = new Util()
}
stages {
stage('Pre-Build') {
script {
env.util.doSomething()
}
}
// more stages
}
notifications {
success {
script {
env.util.notifyBuildStatusSuccess()
}
}
...
}
}
//}
Add Comment
[JIRA] (JENKINS-38663) HTML viewer is broken in version:1.629
Title: Message Title pooja shah edited a comment on JENKINS-38663 Re: HTML viewer is broken in version:1.629 however Mcrooney: i ; ' m curious to figure how to even resolve these warnings, though till now i dnt see any side effects and even this discussion confirms it http://stackoverflow.com/questions/12291258/unrecognized-content-security-policy-directiveI tried as Mike's ideas but results the same, if i use default-src etc, it doesn't work !screenshot-1.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title
Martin Vehovsky commented on JENKINS-38963
Re: User-scoped credentials cannot be looked up in pipeline
Just found out, that it's possible to look-up user-scoped sredentials with '${Credentials}'
node {
withCredentials([[$class : 'UsernamePasswordMultiBinding', credentialsId: '${Credentials}',
usernameVariable: 'USERNAME', passwordVariable: 'PASSWORD']]) {
}
}
Could someone please clarify documentation for this? Thank you
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google 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-38267) job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job
Title: Message Title Yogesh Lonkar assigned an issue to Paul Schubert Fixed Jenkins / JENKINS-38267 job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job Change By: Yogesh Lonkar Assignee: Yogesh Lonkar Paul Schubert Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38267) job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job
Title: Message Title Yogesh Lonkar updated an issue Jenkins / JENKINS-38267 job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job Change By: Yogesh Lonkar Comment: Fixed in job-fan-in-plugin 1.1.2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38267) job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job
Title: Message Title Yogesh Lonkar updated JENKINS-38267 fixed in job-fan-in-plugin 1.1.2 Jenkins / JENKINS-38267 job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job Change By: Yogesh Lonkar Status: In Review Resolved Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38267) job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job
Title: Message Title Yogesh Lonkar updated an issue Jenkins / JENKINS-38267 job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job Change By: Yogesh Lonkar Comment: Fixed in job-fan-in-plugin 1.1.2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38267) job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job
Title: Message Title Yogesh Lonkar updated JENKINS-38267 Jenkins / JENKINS-38267 job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job Change By: Yogesh Lonkar Status: Resolved In Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38267) job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job
Title: Message Title Yogesh Lonkar resolved as Fixed Fixed in job-fan-in-plugin 1.1.2 Jenkins / JENKINS-38267 job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job Change By: Yogesh Lonkar Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-38267) job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job
Title: Message Title Yogesh Lonkar commented on JENKINS-38267 Re: job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job Fixed in job-fan-in-plugin 1.1.2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38898) Managed artifacts fails to upload to S3 - no errors logged
Title: Message Title Alexander A commented on JENKINS-38898 Re: Managed artifacts fails to upload to S3 - no errors logged Try to upload from slave, it's common setting in both failed cases. I will check how uploading from master differs from uploading from slave later. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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.
