[JIRA] [core] (JENKINS-31791) Cannot load job pages due to HistoryWidget hanging
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-31791 Cannot load job pages due to HistoryWidget hanging Change By: Daniel Beck Labels: HistoryWidget regression Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31791) Cannot load job pages due to HistoryWidget hanging
Title: Message Title Daniel Beck commented on JENKINS-31791 Re: Cannot load job pages due to HistoryWidget hanging Tom FENNELLY Thanks for the update. Would still appreciate if you could take a closer look some time this month. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [email-ext-plugin] (JENKINS-32889) Configurable delimiter
Title: Message Title Roman80 created an issue Jenkins / JENKINS-32889 Configurable delimiter Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 11/Feb/16 5:44 AM Priority: Major Reporter: Roman80 it would be very useful if someone could change/configure the delimiter for e.g. "Project Recipient List" and "Project Reply-To List". Because in outlook for example the delimiter between email addresses are a semicolon ";" and not a comma ",". So for parameterized builds the email notification doesn't work most of the time because the users are typing a semicolon instead of a comma. Add Comment
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-32888) Throttle Concurrent Builds plugin doesn't work
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-32888 Throttle Concurrent Builds plugin doesn't work Change By: Grigoriy Milman One job at the end started 8 other jobs.All jobs belong to the same category.Maximum Total Concurrent Builds is set to 0 and Maximum Concurrent Builds Per Node to is set 1. 3 jobs started simultaneously * (I have 4 executors on the system)! Than only one was executed sequentially, as it should.I need to have only one job running from this category at any time! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [throttle-concurrent-builds-plugin] (JENKINS-32888) Throttle Concurrent Builds plugin doesn't work
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-32888 Throttle Concurrent Builds plugin doesn't work Change By: Grigoriy Milman One job at the end started 8 other jobs.All jobs belong to the same category.Maximum Total Concurrent Builds is set to 0 and Maximum Concurrent Builds Per Node to is set 1. 3 jobs started simultaneously * (I have 4 executors on the system)! Than only one was executed ! sequentially, as it should. I need to have only one job running from this category at any time! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [throttle-concurrent-builds-plugin] (JENKINS-32888) Throttle Concurrent Builds plugin doesn't work
Title: Message Title Grigoriy Milman created an issue Jenkins / JENKINS-32888 Throttle Concurrent Builds plugin doesn't work Issue Type: Bug Assignee: Oleg Nenashev Components: throttle-concurrent-builds-plugin Created: 11/Feb/16 5:24 AM Environment: Jenkins 1.644 Priority: Major Reporter: Grigoriy Milman One job at the end started 8 other jobs. All jobs belong to the same category. Maximum Total Concurrent Builds is set to 0 and Maximum Concurrent Builds Per Node to is set 1. 3 jobs started simultaneously (I have 4 executors on the system)! Than only one was executed! I need to have only one job running from this category at any time! Add Comment
[JIRA] [amazon-ecs-plugin] (JENKINS-32887) Unable to install aws-credentials dependency
Title: Message Title Chris Zeeb created an issue Jenkins / JENKINS-32887 Unable to install aws-credentials dependency Issue Type: Bug Assignee: Nicolas De Loof Components: amazon-ecs-plugin Created: 11/Feb/16 5:03 AM Environment: Jenkins version: 1.647 OpenJDK 1.7.0_95 O/S: Amazon Linux AMI 2015.09 Priority: Blocker Reporter: Chris Zeeb When trying to install the latest (version 1.2) Amazon ECS Container Service plugin, I get the following error. It seems to be related to some recent updates. Several weeks ago with version 1.1 of the Amazon ECS Container Service plugin it installed without issue. I was trying to install the plugin on a fresh EC2 instance with only OpenJDK and Jenkins installed. Looking at https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Container+Service+Plugin, aws-credentials is listed as a dependency but is not a hyperlink. Searching for the aws-credentials plugin on jenkins-ci.org brings up https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+AWS+Credentials+Plugin. Searching in jenkins does not bring up any results. If I do some searching I can find the github repo (https://github.com/jenkinsci/aws-credentials-plugin) for aws-credentials which links to https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Amazon+Web+Ser
[JIRA] [amazon-ecs-plugin] (JENKINS-32865) InvalidKeyException: ECDH key agreement requires ECPublicKey for doPhase
Title: Message Title dogfood commented on JENKINS-32865 Re: InvalidKeyException: ECDH key agreement requires ECPublicKey for doPhase Integrated in jenkins_main_trunk #4445 JENKINS-32865 Bump instance-identity to 1.5.1 this indirectly (Revision a6ce5a899364624d28f571934d22931874f632b3) Result = SUCCESS nicolas de loof : a6ce5a899364624d28f571934d22931874f632b3 Files : war/pom.xml Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [amazon-ecs-plugin] (JENKINS-32865) InvalidKeyException: ECDH key agreement requires ECPublicKey for doPhase
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32865 Re: InvalidKeyException: ECDH key agreement requires ECPublicKey for doPhase Code changed in jenkins User: Nicolas De loof Path: war/pom.xml http://jenkins-ci.org/commit/jenkins/a4698bacf938022844fd8cddde220ec439e9af6d Log: Merge pull request #2022 from jenkinsci/ndeloof-patch-1 JENKINS-32865 Bump instance-identity to 1.5.1 Compare: https://github.com/jenkinsci/jenkins/compare/c11e26504e39...a4698bacf938 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [authorize-project-plugin] (JENKINS-32770) Provide a mechanism to run specific projects as ACL.SYSTEM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32770 Re: Provide a mechanism to run specific projects as ACL.SYSTEM Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy.java http://jenkins-ci.org/commit/authorize-project-plugin/77cd5e8403be19bc3017cd8c78660b85d725f15e Log: JENKINS-32770 Fix compilation error Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [authorize-project-plugin] (JENKINS-32770) Provide a mechanism to run specific projects as ACL.SYSTEM
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-32770 Provide a mechanism to run specific projects as ACL.SYSTEM Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [authorize-project-plugin] (JENKINS-32770) Provide a mechanism to run specific projects as ACL.SYSTEM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32770 Re: Provide a mechanism to run specific projects as ACL.SYSTEM Code changed in jenkins User: Stephen Connolly Path: src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy/help-permitReconfiguration.html http://jenkins-ci.org/commit/authorize-project-plugin/05252731e3a01375bd2ce84b75bdd07e4e4567a3 Log: JENKINS-32770 Add help file about RUN_SCRIPTS Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [authorize-project-plugin] (JENKINS-32770) Provide a mechanism to run specific projects as ACL.SYSTEM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32770 Re: Provide a mechanism to run specific projects as ACL.SYSTEM Code changed in jenkins User: Stephen Connolly Path: src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy/config.jelly http://jenkins-ci.org/commit/authorize-project-plugin/4e5fa858f1fefe0ccd7d7569404317ef753ab186 Log: JENKINS-32770 Fix jelly pages to enforce RUN_SCRIPTS Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [authorize-project-plugin] (JENKINS-32770) Provide a mechanism to run specific projects as ACL.SYSTEM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32770 Re: Provide a mechanism to run specific projects as ACL.SYSTEM Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy.java src/test/java/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest.java http://jenkins-ci.org/commit/authorize-project-plugin/b9b6925839e5e4d4f164d200263559c7b3e08783 Log: JENKINS-32770 Copyright headers Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [authorize-project-plugin] (JENKINS-32770) Provide a mechanism to run specific projects as ACL.SYSTEM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32770 Re: Provide a mechanism to run specific projects as ACL.SYSTEM Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy.java src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/Messages.properties src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy/config.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy/global-security.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy/help.html src/test/java/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest.java src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/testLoadOnStart/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/testLoadOnStart/jobs/test/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/testLoadOnStart/users/admin/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/testLoadOnStart/users/test1/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/testLoadOnStart/users/test2/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/users/admin/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/users/test1/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/users/test2/config.xml http://jenkins-ci.org/commit/authorize-project-plugin/5550847cc7aaf09f48bfadd609768ccbf15d1624 Log: [FIXED JENKINS-32770] Provide a mechanism to run specific projects as ACL.SYSTEM Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [authorize-project-plugin] (JENKINS-32770) Provide a mechanism to run specific projects as ACL.SYSTEM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32770 Re: Provide a mechanism to run specific projects as ACL.SYSTEM Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy.java http://jenkins-ci.org/commit/authorize-project-plugin/cca87b5e5e47d4e049b0b2ee1ddf2bb9ef6bb4db Log: JENKINS-32770 Address issues identified by jglick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [authorize-project-plugin] (JENKINS-32770) Provide a mechanism to run specific projects as ACL.SYSTEM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32770 Re: Provide a mechanism to run specific projects as ACL.SYSTEM Code changed in jenkins User: ikedam Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy.java src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/Messages.properties src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy/config.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy/global-security.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy/help-permitReconfiguration.html src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy/help.html src/test/java/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest.java src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/testLoadOnStart/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/testLoadOnStart/jobs/test/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/testLoadOnStart/users/admin/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/testLoadOnStart/users/test1/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/testLoadOnStart/users/test2/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/users/admin/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/users/test1/config.xml src/test/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest/users/test2/config.xml http://jenkins-ci.org/commit/authorize-project-plugin/12a36be51c8f0362bfabc3350721bb53e9421714 Log: Merge pull request #16 from stephenc/jenkins-32770 JENKINS-32770 Provide a mechanism to run specific projects as ACL.SYSTEM Compare: https://github.com/jenkinsci/authorize-project-plugin/compare/43af1ff853d2...12a36be51c8f Add Comment
[JIRA] [authorize-project-plugin] (JENKINS-32769) SpecificUsersAuthorizationStrategy cannot work for ACL.SYSTEM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32769 Re: SpecificUsersAuthorizationStrategy cannot work for ACL.SYSTEM Code changed in jenkins User: ikedam Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/Messages.properties http://jenkins-ci.org/commit/authorize-project-plugin/43af1ff853d222c7b2a0a45ad4f65ad7c87b38d7 Log: Merge pull request #15 from stephenc/jenkins-32769 JENKINS-32769 SpecificUsersAuthorizationStrategy cannot work for ACL.SYSTEM Compare: https://github.com/jenkinsci/authorize-project-plugin/compare/5f567fcfb978...43af1ff853d2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [authorize-project-plugin] (JENKINS-32769) SpecificUsersAuthorizationStrategy cannot work for ACL.SYSTEM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32769 Re: SpecificUsersAuthorizationStrategy cannot work for ACL.SYSTEM Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/Messages.properties http://jenkins-ci.org/commit/authorize-project-plugin/2c0799f5d929e419d474d591cc7c47f6bf6fd810 Log: JENKINS-32769 SpecificUsersAuthorizationStrategy cannot work for ACL.SYSTEM Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31039) Queue items are ephemeral leading to api users to lose track of builds.
Title: Message Title Itay Donanhirsh edited a comment on JENKINS-31039 Re: Queue items are ephemeral leading to api users to lose track of builds. Hi, this happens as well to us. A few moments after the job is scheduled (out of the queue), the queue item is 404. Is there a parameter to adjust this behavior? Jenkins version: 1.625.2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [authorize-project-plugin] (JENKINS-30574) Support global default authorization strategy in Authorize Project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30574 Re: Support global default authorization strategy in Authorize Project Code changed in jenkins User: Stephen Connolly Path: src/main/resources/org/jenkinsci/plugins/authorizeproject/form/dropdownDescriptorSelector.jelly http://jenkins-ci.org/commit/authorize-project-plugin/1999e626b2ece4f7169b9c05552a1afd98cf3366 Log: JENKINS-30574 Note tag unneeded after Jenkins 1.645+ Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [authorize-project-plugin] (JENKINS-30574) Support global default authorization strategy in Authorize Project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30574 Re: Support global default authorization strategy in Authorize Project Code changed in jenkins User: Stephen Connolly Path: src/test/java/org/jenkinsci/plugins/authorizeproject/GlobalQueueItemAuthenticatorTest.java http://jenkins-ci.org/commit/authorize-project-plugin/136fe6120e721c3302baf8bfba2d1917171b68cc Log: JENKINS-30574 Fix compilation errors Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [authorize-project-plugin] (JENKINS-30574) Support global default authorization strategy in Authorize Project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30574 Re: Support global default authorization strategy in Authorize Project Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/authorizeproject/GlobalQueueItemAuthenticator.java http://jenkins-ci.org/commit/authorize-project-plugin/9f626de2e7403a4f8c20d4a50be0e87a3ade443e Log: JENKINS-30574 Fix form binding and change default to anonymous Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [authorize-project-plugin] (JENKINS-30574) Support global default authorization strategy in Authorize Project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30574 Re: Support global default authorization strategy in Authorize Project Code changed in jenkins User: ikedam Path: src/main/java/org/jenkinsci/plugins/authorizeproject/GlobalQueueItemAuthenticator.java src/main/resources/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty/config.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/GlobalQueueItemAuthenticator/config.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/GlobalQueueItemAuthenticator/help.html src/main/resources/org/jenkinsci/plugins/authorizeproject/Messages.properties src/main/resources/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticator/config.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticator/help.html src/main/resources/org/jenkinsci/plugins/authorizeproject/form/dropdownDescriptorSelector.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/form/taglib src/test/java/org/jenkinsci/plugins/authorizeproject/GlobalQueueItemAuthenticatorTest.java http://jenkins-ci.org/commit/authorize-project-plugin/5f567fcfb978ce39fea263c5b10e34d67ef60a00 Log: Merge pull request #14 from stephenc/jenkins-30574-redux [FIXED JENKINS-30574] Support global default authorization strategy in Authorize Project Compare: https://github.com/jenkinsci/authorize-project-plugin/compare/c6507c759b15...5f567fcfb978 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [authorize-project-plugin] (JENKINS-30574) Support global default authorization strategy in Authorize Project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30574 Re: Support global default authorization strategy in Authorize Project Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/authorizeproject/GlobalQueueItemAuthenticator.java src/main/resources/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty/config.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/GlobalQueueItemAuthenticator/config.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/GlobalQueueItemAuthenticator/help.html src/main/resources/org/jenkinsci/plugins/authorizeproject/Messages.properties src/main/resources/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticator/config.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticator/help.html src/main/resources/org/jenkinsci/plugins/authorizeproject/form/dropdownDescriptorSelector.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/form/taglib src/test/java/org/jenkinsci/plugins/authorizeproject/GlobalQueueItemAuthenticatorTest.java http://jenkins-ci.org/commit/authorize-project-plugin/20d2ba35fa7aebd062987a7e9c3070d597c1a4c6 Log: [FIXED JENKINS-30574] Support global default authorization strategy in Authorize Project Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [authorize-project-plugin] (JENKINS-30574) Support global default authorization strategy in Authorize Project
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-30574 Support global default authorization strategy in Authorize Project Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [tfs-plugin] (JENKINS-16207) "Changes Summary" diff link broken after migration to TFS 2012
Title: Message Title Manfred Moser commented on JENKINS-16207 Re: "Changes Summary" diff link broken after migration to TFS 2012 Here is a PR that fixes this https://github.com/jenkinsci/tfs-plugin/pull/71 by adopting the new pattern. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [promoted-builds-plugin] (JENKINS-29776) Job DSL support for Promoted Builds Plugin
Title: Message Title David Chou commented on JENKINS-29776 Re: Job DSL support for Promoted Builds Plugin +1 for this. Thanks Dennis Schulte for taking the time to create that PR. Looks like no activity yet on your updated https://github.com/jenkinsci/promoted-builds-plugin/pull/82 Was wondering if anyone has a work around for this while we wait for the process? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31791) Cannot load job pages due to HistoryWidget hanging
Title: Message Title Tom FENNELLY commented on JENKINS-31791 Re: Cannot load job pages due to HistoryWidget hanging Daniel Beck I don't think HistoryPageFilter is the issue as it's only short lived object (during rendering) + it only ever holds maxEntries, which is typically just 30. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [extra-columns-plugin] (JENKINS-32871) add environment variable view
Title: Message Title Fred G assigned an issue to mor lajb Jenkins / JENKINS-32871 add environment variable view Change By: Fred G Assignee: Fred G mor lajb Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [extra-columns-plugin] (JENKINS-32871) add environment variable view
Title: Message Title Fred G commented on JENKINS-32871 Re: add environment variable view So you are requesting a new column that shows one or more environment variables, correct? Please provide a use case why you need this kind of column. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-32886) Tool installer data should be downloaded when a new plugin is installed
Title: Message Title Christopher Orr commented on JENKINS-32886 Re: Tool installer data should be downloaded when a new plugin is installed This already works for plugins that are dynamically loaded at runtime. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-32886) Tool installer data should be downloaded when a new plugin is installed
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-32886 Tool installer data should be downloaded when a new plugin is installed Change By: Christopher Orr Comment: This already works for plugins that are dynamically loaded at runtime. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-32886) Tool installer data should be downloaded when a new plugin is installed
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-32886 Tool installer data should be downloaded when a new plugin is installed Issue Type: Improvement Assignee: Daniel Beck Components: core Created: 10/Feb/16 10:48 PM Priority: Minor Reporter: Christopher Orr When a tool installer plugin is installed after a Jenkins restart — either due to a user clicking "Download now and install after restart" in the plugin manager, or because they manually placed the .jpi file in the plugins directory — the tool installer JSON file is currently not downloaded. Therefore the user must wait up to 24 hours for the tool installer data to be downloaded by Jenkins, or manually navigate to Manage Plugins > Advanced > Check Now. Ideally Jenkins would download missing tool installer data as soon as possible after such a plugin is loaded into Jenkins. Add Comment
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Title: Message Title Javier Palacios commented on JENKINS-25267 Re: Gitlab hook not building on merge request object I've started looking at this, and plugin should be able to trigger also jobs with https urls. Might it happen that your url are a bit more complex than standard ones? Something don't matching https://server/group/repository.git Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-27694) Download update data immediately when installing a new tool installer plugin
Title: Message Title Daniel Beck commented on JENKINS-27694 Re: Download update data immediately when installing a new tool installer plugin Christopher Orr File a new bug, assign to me. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-27694) Download update data immediately when installing a new tool installer plugin
Title: Message Title Christopher Orr commented on JENKINS-27694 Re: Download update data immediately when installing a new tool installer plugin A user of the Go plugin emailed me to ask about this problem, and we discovered that they were installing the plugin using the "Download now and install after restart" option. Indeed, I can reproduce that the tool installer data is downloaded automatically if you install a plugin by clicking "Install without restart", but if you click on "Download now and install after restart", then the tool installer metadata is not downloaded automatically after the download, nor when Jenkins restarts. Users should preferably install plugins without restarting, but so long as the other option exists, people are going to click on it. Or they'll install new plugins at the same time as updating older ones. There's also a (probably very rare) chance that a plugin update will add a tool installer. Jenkins should also download the tool installer data in these situations. Should this go into a new ticket? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [gitlab-hook-plugin] (JENKINS-31179) Gitlab web hook is not working.
Title: Message Title Javier Palacios closed an issue as Cannot Reproduce Jenkins / JENKINS-31179 Gitlab web hook is not working. Change By: Javier Palacios Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [gitlab-hook-plugin] (JENKINS-30861) Ignore 'Polling ignores commits from certain users' on GitLab WebHooks
Title: Message Title Javier Palacios closed an issue as Postponed Jenkins / JENKINS-30861 Ignore 'Polling ignores commits from certain users' on GitLab WebHooks Change By: Javier Palacios Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [gitlab-hook-plugin] (JENKINS-28808) 'undefined method `extensions'' on processing Multiple SCMs projects
Title: Message Title Javier Palacios closed an issue as Fixed Jenkins / JENKINS-28808 'undefined method `extensions'' on processing Multiple SCMs projects Change By: Javier Palacios Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [gitlab-hook-plugin] (JENKINS-29309) Jenkins cannot start with gitlab-hook plugin
Title: Message Title Javier Palacios closed an issue as Cannot Reproduce Jenkins / JENKINS-29309 Jenkins cannot start with gitlab-hook plugin Change By: Javier Palacios Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [gitlab-hook-plugin] (JENKINS-32378) Trigger build when the url is an http/https one
Title: Message Title Javier Palacios started work on JENKINS-32378 Change By: Javier Palacios Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [gitlab-hook-plugin] (JENKINS-32789) Implement commit status API
Title: Message Title Javier Palacios started work on JENKINS-32789 Change By: Javier Palacios Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-client-plugin] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work
Title: Message Title Mark Waite commented on JENKINS-20879 Re: SSH Credentials (private key with passphrase) do not work What do you mean with "command line git"? I'm able to configure and successfully run a project which uses an RSA private key which requires a passphrase, if I use the JGIt implementation. I have not been able to successfully run a project using an RSA private key which requires a passphrase if I use the command line git (default) implementation. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-32840) Step ‘Git Publisher’ failed when pushing the build tag of a job inside a folder
Title: Message Title Mark Waite commented on JENKINS-32840 Re: Step ‘Git Publisher’ failed when pushing the build tag of a job inside a folder It is quite rare that I'll change a default behavior, even when the default behavior seems counter-intuitive. With over 5 installations, there are too many cases where a user is critically dependent on the existing default behavior. There are some noteworthy exceptions (like the transition from git plugin 1.x to git plugin 2.x, when a number of defaults changed, or the upcoming release of git plugin 2.5 which will change the internal implementation of the authentication so that submodule authentication can be supported). Those are truly exceptions. That pattern is frequently reinforced. I introduced a git client plugin 1.19.3 change to fail faster if authentication was being prompted to the user. I removed that change in 1.19.4 because it broke a previously working use case with passphrase protected RSA private keys. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31039) Queue items are ephemeral leading to api users to lose track of builds.
Title: Message Title Itay Donanhirsh commented on JENKINS-31039 Re: Queue items are ephemeral leading to api users to lose track of builds. Hi, this happens as well to us. A few moments after the job is scheduled (out of the queue), the queue item is 404. Is there a parameter to adjust this behavior? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [build-name-setter-plugin] (JENKINS-10613) The build name setter does not work for multi-configuration jobs
Title: Message Title
Jeremy Rampon commented on JENKINS-10613
Re: The build name setter does not work for multi-configuration jobs
Jenkins 1.647 with plugin version 1.5.1.
Here is how my matrix project is setup.
Part 1 In the Build Environment section, I set the build-name-setter option to #${BUILD_NUMBER} ${ENV,var="VERSION"}. This is so that as soon as the build starts, we can tell what base version it's building. This works fine – meaning the parent matrix job is correctly renamed, while the children still have their original name based on the project matrix values.
Part 2 In addition to the above, in the Build section, I have an "Update build name" build type, with "use macro" set to #${BUILD_NUMBER} ${PROPFILE,file="properties.txt",property="BUILD_TAG"}. At the end of the builds for each of the matrix project's children I see in the log that it seems to work as expected:
Evaluated macro: '#1_some-tag'
Setting build name to '#1_some-tag'
But the actual matrix project build name still shows the name set in part 1 above.
Any idea what could be causing this?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [build-pipeline-plugin] (JENKINS-32885) Build Pipeline Plugin doesn't link the jobs to it's corresponding build number after successful re-build.
Title: Message Title Niraj Khanal created an issue Jenkins / JENKINS-32885 Build Pipeline Plugin doesn't link the jobs to it's corresponding build number after successful re-build. Issue Type: Bug Assignee: Unassigned Attachments: Capture.JPG, Capture1.JPG, Capture3.JPG Components: build-pipeline-plugin Created: 10/Feb/16 7:21 PM Environment: Jenkins: 1.609.1 Build Pipeline Plugin Version: 1.4.7 Labels: plugin Priority: Major Reporter: Niraj Khanal In addition to JENKINS-28478 ( where the pipeline shows failed even though the job is successful) , I am seeing that Build Pipeline when run from the middle of the pipeline doesn't seem to link the job to it's correct build number . However, i
[JIRA] [aws-beanstalk-publisher-plugin] (JENKINS-32877) AWS Beanstalk Plugin should be able to use server role credentials
Title: Message Title Ashley Mercer commented on JENKINS-32877 Re: AWS Beanstalk Plugin should be able to use server role credentials Thanks for the swift response! I made a small pull request to document this in the README on github Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [ansible-plugin] (JENKINS-32384) Password-protected private keys are still unusable
Title: Message Title Rob Duff commented on JENKINS-32384 Re: Password-protected private keys are still unusable Hi Tomasz, In your description you mentioned that this is still unusable. Do you know as of when? Has this always been the case that you're aware of, or did you notice this in a specific version before 4.0? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [parameterized-remote-trigger-plugin] (JENKINS-28637) Unable to select stored credentials from the credential plug-in
Title: Message Title
Michael Wenig commented on JENKINS-28637
Re: Unable to select stored credentials from the credential plug-in
We have the same problem at our side using certificate based credentials. It seems that the plugin is only designed to support Username/passwort via the Credentials Plugin.
We get an exception
Caused by: java.lang.NullPointerException
at org.jenkinsci.plugins.ParameterizedRemoteTrigger.Auth.getUsername(Auth.java:80)
... 238 more
Looking into the code:
} else if (authType.equals(CREDENTIALS_PLUGIN)) {
username = this.getCredentials().getUsername();
}
and
private UsernamePasswordCredentials getCredentials() {
String credetialId = this.getCreds();
StandardUsernameCredentials matchedCredentials = null;
Item item = null;
List listOfCredentials = CredentialsProvider.lookupCredentials(
StandardUsernameCredentials.class, item, ACL.SYSTEM, Collections. emptyList());
for (StandardUsernameCredentials cred : listOfCredentials) {
if (credetialId.equals(cred.getId())) {
matchedCredentials = cred;
break;
}
}
// now we have matchedCredentials.getPassword() and matchedCredentials.getUsername();
return (UsernamePasswordCredentials) matchedCredentials;
}
this will not give anything at our side as we do not have any UserNamePasswortCredentials.
so it seems that certificate based credentials are not supported at the moment
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [token-macro-plugin] (JENKINS-28951) Allow for bash type variable expansion in token-macro-plugin
Title: Message Title Alex Earl started work on JENKINS-28951 Change By: Alex Earl Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [email-ext-plugin] (JENKINS-32828) Jelly Template not working and Variables not expanding
Title: Message Title Alex Earl closed an issue as Incomplete Jenkins / JENKINS-32828 Jelly Template not working and Variables not expanding Change By: Alex Earl Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-plugin] (JENKINS-32819) Pipeline compilation error detection broken when using CSRF detection
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32819 Re: Pipeline compilation error detection broken when using CSRF detection Code changed in jenkins User: Antonio Muñiz Path: cps/src/main/js/workflow-editor.js http://jenkins-ci.org/commit/workflow-plugin/a5fdddee3fb14028612df3032414f9d5a1f6dcea Log: JENKINS-32819 Fix script compilation check when CSRF is enabled Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-plugin] (JENKINS-32819) Pipeline compilation error detection broken when using CSRF detection
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32819 Re: Pipeline compilation error detection broken when using CSRF detection Code changed in jenkins User: Jesse Glick Path: CHANGES.md cps/src/main/js/workflow-editor.js http://jenkins-ci.org/commit/workflow-plugin/8a56225d34f61f9400b621977f99dea2ffd49b0f Log: [FIXED JENKINS-32819] Merging #339. Compare: https://github.com/jenkinsci/workflow-plugin/compare/5bede7cff5c3...8a56225d34f6 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-plugin] (JENKINS-32819) Pipeline compilation error detection broken when using CSRF detection
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-32819 Pipeline compilation error detection broken when using CSRF detection Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [aws-beanstalk-publisher-plugin] (JENKINS-32877) AWS Beanstalk Plugin should be able to use server role credentials
Title: Message Title David Tanner commented on JENKINS-32877 Re: AWS Beanstalk Plugin should be able to use server role credentials https://github.com/jenkinsci/aws-beanstalk-publisher-plugin/blob/aws-beanstalk-publisher-plugin-1.5.6/src/main/java/org/jenkinsci/plugins/awsbeanstalkpublisher/AWSEBEnvironmentUpdater.java#L50-L58 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [amazon-ecs-plugin] (JENKINS-32865) InvalidKeyException: ECDH key agreement requires ECPublicKey for doPhase
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32865 Re: InvalidKeyException: ECDH key agreement requires ECPublicKey for doPhase Code changed in jenkins User: Nicolas De loof Path: war/pom.xml http://jenkins-ci.org/commit/jenkins/a6ce5a899364624d28f571934d22931874f632b3 Log: JENKINS-32865 Bump instance-identity to 1.5.1 this indirectly upgrades bouncycaslte to 1.54 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [aws-beanstalk-publisher-plugin] (JENKINS-32877) AWS Beanstalk Plugin should be able to use server role credentials
Title: Message Title David Tanner closed an issue as Done The latest version of the plugin is built to handle this situation. You are not required to input the key and secret key information. Jenkins / JENKINS-32877 AWS Beanstalk Plugin should be able to use server role credentials Change By: David Tanner Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [ssh-slaves-plugin] (JENKINS-22320) High CPU consumption because of SSH communication
Title: Message Title Roy Arnon commented on JENKINS-22320 Re: High CPU consumption because of SSH communication Sorry, attached the image incorrectly: Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [ssh-slaves-plugin] (JENKINS-22320) High CPU consumption because of SSH communication
Title: Message Title Roy Arnon commented on JENKINS-22320 Re: High CPU consumption because of SSH communication Hi, Using jenkins 1.625.3 and ssh-slave plugin 1.10, it seems this issue occurs intermenitally for us. Lately, it happens at least once a day. Most of the threads are wasting CPU time exactly the same as in the example above. I've attached call tree from yourkit. I can provide more data if required. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [jira-plugin] (JENKINS-32884) JIRA Integration doesn't include entire git commit message in issue comments
Title: Message Title ben s created an issue Jenkins / JENKINS-32884 JIRA Integration doesn't include entire git commit message in issue comments Issue Type: Bug Assignee: Unassigned Attachments: changelog_on_jenkins.png, comment_on_jira.png Components: jira-plugin Created: 10/Feb/16 5:00 PM Priority: Minor Reporter: ben s The git plugin truncates changelog by adding linebreaks in the commit message for improved presentation. See: JENKINS-29977 This is all well and good for the changelog page in Jenkins, but a side-effect is that when Jenkins updates referenced Jira issues with a comment, only the first line of the modified commit message is included in the Jira comment. This can often result in broken, partial sentences that aren't of much use to issue watchers who don't have necessary Jenkins access. This didn't used to be a problem, and my guess it started when the linebreaks were added to the git plugin.
[JIRA] [p4-plugin] (JENKINS-31061) [P4 plugin]Post-build publish does not support .p4ignore file
Title: Message Title dan tran commented on JENKINS-31061 Re: [P4 plugin]Post-build publish does not support .p4ignore file is it fixed? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [htmlpublisher-plugin] (JENKINS-32843) ReportNG is blank after upgrade to the html publishing latest release
Title: Message Title Daniel Beck commented on JENKINS-32843 Re: ReportNG is blank after upgrade to the html publishing latest release Jenkins tells the browser to prohibit things like frames and _javascript_ for security reasons and your report likely uses these. The rules what is allowed therefore need to be adjusted. To learn how, read https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy from top to bottom. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [htmlpublisher-plugin] (JENKINS-32843) ReportNG is blank after upgrade to the html publishing latest release
Title: Message Title Shalev Utnik commented on JENKINS-32843 Re: ReportNG is blank after upgrade to the html publishing latest release Daniel, I don't understand from that link what should be done can you please explain? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files
Title: Message Title
Nickolay Rumyantsev updated an issue
Jenkins / JENKINS-32869
Artifactory plugin creates directories instead of uploading files
Change By:
Nickolay Rumyantsev
My job builds some tgz and rpms. I configured it to use Artifactory plugin as a Generic deployer to my test Artifactory instance.During the execution plugin reports in the log that it found the artifacts and deployed them successfully. But it ran too fast so I check the artifacts on the Artifactory page. There I saw that instead of files there were directories with the same names!Publishing rules are the following (yes, there are version-named directories as the dest):{code:java}/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.COREOS.tgz=>com/foo/bar/coreos/1.5.0.0-155.COREOS/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.RHEL.rpm=>com/foo/bar/rhel7/1.5.0.0-155.RHEL{code}I also tried appending the filename to the each rule, and a trailing slash too but it didn't help.I found a stackoverflow question about the same issue but there is not much information: http://stackoverflow.com/questions/30633080/artifactory-creating-folders-instead-of-deploying-artifact.Also raised: https://www.jfrog.com/jira/browse/HAP-690I couldn't find a workaround so this is blocking me at the moment. * UPDATE: * all works fine if I don't use "Deployment properties" option.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it,
[JIRA] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files
Title: Message Title
Nickolay Rumyantsev updated an issue
Jenkins / JENKINS-32869
Artifactory plugin creates directories instead of uploading files
Change By:
Nickolay Rumyantsev
My job builds some tgz and rpms. I configured it to use Artifactory plugin as a Generic deployer to my test Artifactory instance.During the execution plugin reports in the log that it found the artifacts and deployed them successfully. But it ran too fast so I check the artifacts on the Artifactory page. There I saw that instead of files there were directories with the same names!Publishing rules are the following (yes, there are version-named directories as the dest):{code:java}/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.COREOS.tgz=>com/foo/bar/coreos/1.5.0.0-155.COREOS/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.RHEL.rpm=>com/foo/bar/rhel7/1.5.0.0-155.RHEL{code}I also tried appending the filename to the each rule, and a trailing slash too but it didn't help.I found a stackoverflow question about the same issue but there is not much information: http://stackoverflow.com/questions/30633080/artifactory-creating-folders-instead-of-deploying-artifact.Also raised: https://www.jfrog.com/jira/browse/HAP-690I couldn't find a workaround so this is blocking me at the moment. UPDATE: all works fine if I don't use "Deployment properties" option.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send
[JIRA] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files
Title: Message Title Nickolay Rumyantsev updated an issue Jenkins / JENKINS-32869 Artifactory plugin creates directories instead of uploading files Change By: Nickolay Rumyantsev Priority: Blocker Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files
Title: Message Title Nickolay Rumyantsev updated an issue Jenkins / JENKINS-32869 Artifactory plugin creates directories instead of uploading files Change By: Nickolay Rumyantsev Environment: Jenkins 1.625.3Artifactory plugin 2.4.7 (2.2.4 too) Artifactory OSS (latest docker image: 29d2cd2e846a) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [build-pipeline-plugin] (JENKINS-28478) Build Pipeline plugin loses track of upstream build when retrying of a failed build
Title: Message Title Niraj Khanal commented on JENKINS-28478 Re: Build Pipeline plugin loses track of upstream build when retrying of a failed build Could you please be a little more specific about the workaround? I am unable to run the pipeline and not sure what to delete. Thank You. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-22008) buildTimeTrend only shows the last 20 builds
Title: Message Title Manuel Jesús Recena Soto stopped work on JENKINS-22008 Change By: Manuel Jesús Recena Soto Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-client-plugin] (JENKINS-32883) replace custom temporary script with GIT_SSH_COMMAND
Title: Message Title Nicolas De Loof created an issue Jenkins / JENKINS-32883 replace custom temporary script with GIT_SSH_COMMAND Issue Type: Improvement Assignee: Nicolas De Loof Components: git-client-plugin Created: 10/Feb/16 4:02 PM Priority: Minor Reporter: Nicolas De Loof git-client plugin do create a custom temporary script to pass SSH key to git. Since 2.3.0 `GIT_SSH_COMMAND` can be use to just pass plain ssh command like `ssh -i xxx` Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-32882) Add support for loglines param for notification plugin
Title: Message Title Denis Shvedchenko created an issue Jenkins / JENKINS-32882 Add support for loglines param for notification plugin Issue Type: Improvement Assignee: Denis Shvedchenko Components: job-dsl-plugin Created: 10/Feb/16 3:41 PM Priority: Minor Reporter: Denis Shvedchenko I need job-dsl support loglines parameter for notification plugin. Implementation is in https://github.com/jenkinsci/job-dsl-plugin/pull/741. Please, consider including it in future release Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-32882) Add support for loglines param for notification plugin
Title: Message Title Denis Shvedchenko started work on JENKINS-32882 Change By: Denis Shvedchenko Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [htmlpublisher-plugin] (JENKINS-32843) ReportNG is blank after upgrade to the html publishing latest release
Title: Message Title Daniel Beck resolved as Not A Defect The protection by Jenkins is still active, so will still require you to customize the rules. HTML Publisher ≤1.9 was completely broken. Jenkins / JENKINS-32843 ReportNG is blank after upgrade to the html publishing latest release Change By: Daniel Beck Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [multijob-plugin] (JENKINS-32881) multi-job-plugin: use previous hash on resume
Title: Message Title Trevor Riles created an issue Jenkins / JENKINS-32881 multi-job-plugin: use previous hash on resume Issue Type: Improvement Assignee: Unassigned Components: multijob-plugin Created: 10/Feb/16 3:18 PM Environment: Jenkins: 1.644 multi-job: 1.20 Priority: Minor Reporter: Trevor Riles When a jobs scm (git in our case) is tied to branch and we resume a build with failed sub-jobs, it should use the same hash (instead of branch) as the initial run. Add Comment
[JIRA] [htmlpublisher-plugin] (JENKINS-32843) ReportNG is blank after upgrade to the html publishing latest release
Title: Message Title Shalev Utnik reopened an issue Jenkins / JENKINS-32843 ReportNG is blank after upgrade to the html publishing latest release Change By: Shalev Utnik Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [htmlpublisher-plugin] (JENKINS-32843) ReportNG is blank after upgrade to the html publishing latest release
Title: Message Title Shalev Utnik commented on JENKINS-32843 Re: ReportNG is blank after upgrade to the html publishing latest release Hello Daniel, I have the most updated version of the htmp publisher plugin installed (1.11) but still see this problem. any idea why? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [distfork-plugin] (JENKINS-32648) distfork should print name of node it is executing command on
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-32648 distfork should print name of node it is executing command on Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [parameterized-trigger-plugin] (JENKINS-11280) Downstream project name is not accepting env variable/build parameters
Title: Message Title Adrian Popa commented on JENKINS-11280 Re: Downstream project name is not accepting env variable/build parameters Still hasn't been fixed in Jenkins v1.634 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [distfork-plugin] (JENKINS-32648) distfork should print name of node it is executing command on
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32648 Re: distfork should print name of node it is executing command on Code changed in jenkins User: James Nord Path: src/main/java/hudson/plugins/distfork/DistForkCommand.java src/test/java/hudson/plugins/distfork/DistForkCommandTest.java http://jenkins-ci.org/commit/distfork-plugin/6889f3201c6d45327728b5ea991e54e5593a976c Log: [FIXED JENKINS-32648] log the name of the node. When running print the name of the node that executes the remote command. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [distfork-plugin] (JENKINS-32648) distfork should print name of node it is executing command on
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32648 Re: distfork should print name of node it is executing command on Code changed in jenkins User: James Nord Path: src/main/java/hudson/plugins/distfork/DistForkCommand.java src/test/java/hudson/plugins/distfork/DistForkCommandTest.java http://jenkins-ci.org/commit/distfork-plugin/1f7b851f71da51017682f8d441a1c1aba8b2e7ba Log: Merge pull request #5 from jtnord/ JENKINS-32648 [FIXED JENKINS-32648] log the name of the node. Compare: https://github.com/jenkinsci/distfork-plugin/compare/880cda795b58...1f7b851f71da Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [logging-plugin] (JENKINS-32880) Job DSL ability to specify level ALL and custom logLevel
Title: Message Title Martin Mosegaard Amdisen created an issue Jenkins / JENKINS-32880 Job DSL ability to specify level ALL and custom logLevel Issue Type: Improvement Assignee: Praqma Support Components: logging-plugin Created: 10/Feb/16 2:50 PM Priority: Minor Reporter: Martin Mosegaard Amdisen Using Job DSL, I would like to obtain this XML: ALL net.praqma -2147483648 but run into 2 issues: 1) target level 'ALL' does not seem to be supported 2) target has no child element to specify logLevel. Instead, it seems to get a default value The workaround for now is to use the Job DSL configure block. Add Comment
[JIRA] [git-client-plugin] (JENKINS-32834) Failed to connect to repository with password-protected ssh key
Title: Message Title Mark Waite commented on JENKINS-32834 Re: Failed to connect to repository with password-protected ssh key I've confirmed the update center now shows git client plugin 1.19.4. Be sure you refresh the update center by pressing the "Check Now" button in the Jenkins Update Center web page. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31791) Cannot load job pages due to HistoryWidget hanging
Title: Message Title CL Kao commented on JENKINS-31791 Re: Cannot load job pages due to HistoryWidget hanging This has affected the latest LTS (1.642.1) and rendered jobs with 2000+ builds not responsive Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [envinject-plugin] (JENKINS-32532) User build variables are not injected on "Before Build" step
Title: Message Title Oleg Nenashev commented on JENKINS-32532 Re: User build variables are not injected on "Before Build" step Yes, I have. It Build User vars plugin there should be a fix like: https://github.com/oleg-nenashev/ownership-plugin/commit/9871283990bd76c8f04bb61cfdeb4a1c30159a4c . The plugin should inject EnvironmentContributingAction, which would produce the vars at any build stage Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [p4-plugin] (JENKINS-32879) Integration with mailer plugin is broken
Title: Message Title
Alexey Sergin updated an issue
Jenkins / JENKINS-32879
Integration with mailer plugin is broken
Change By:
Alexey Sergin
*Use case:*I have a Freestyle project with sources fetched by p4 plugin in "manual (custom view)" mode. The project has a post-build action "E-mail Notification" with a "Send separate e-mails to individuals who broke the build" checkbox checked. Mailer Plugin tries to compose a notification when build fails. The problem is that Mailer Plugin is not able to get emails corresponding to Perforce accounts.*Example Console Output:*{noformat}Building in workspace /var/lib/jenkins/workspace/backup... p4 client -o jenkins-master-backup +... p4 info +P4 Task: establishing connection server: ... node: ... p4 client -o jenkins-master-backup +... p4 client -i +... client: jenkins-master-backup... p4 client -o jenkins-master-backup +... p4 info +... p4 counter change +... p4 changes -m1 //jenkins-master-backup/... +Building on Node: master... p4 client -o jenkins-master-backup +... p4 info +P4 Task: establishing connection server: ... node: P4 Task: syncing files at change: 1657621... p4 sync -q /var/lib/jenkins/workspace/backup/...@1657621 +duration: (25ms)P4 Task: saving built changes p4 client -o jenkins-master-backup +... p4 info +... p4 client -o jenkins-master-backup +... p4 info +... p4 client -o jenkins-master-backup +... p4 info +... p4 changes -l @=1657621 +... p4 user -o Smith +... p4 files -m51 @=1657621 +... p4 fixes -c1657621 +... done[backup] $ /bin/sh -ex /tmp/hudson3013805400501810634.sh+ exit 1Build step 'Execute shell' marked build as failureFailed to send e-mail to Smith because no e-mail address is known, and no default e-mail domain is configuredAn attempt to send an e-mail to empty list of recipients, ignored.Finished: FAILURE{noformat}The problem is this: "Failed to send e-mail to Smith because no e-mail address is known, and no default e-mail domain is configured"* Info on user Smith : *{noformat}# /opt/perforce/bin/p4 user -o Smith# A Perforce User Specification.# User: SmithEmail: john.sm...@company.comUpdate: Access: FullName: John SmithPassword: **# cat /var/lib/jenkins/users/smith/config.xml Smith censored All false false false john.sm...@company.com {noformat}*Example log on org.jenkinsci.plugins.p4 + hudson.tasks :*{noformat}Feb 10, 2016 4:48:30 PM FINE org.jenkinsci.plugins.p4.client.ConnectionHelperP4: opened connection OKFeb 10, 2016 4:48:31 PM FINE org.jenkinsci.plugins.p4.changes.P4ChangeEntrySetting email for user: Smith:john.sm...@company.comFeb 10, 2016 4:48:31 PM FINE org.jenkinsci.plugins.p4.client.ConnectionHelperP4: closed connection OKFeb 10, 2016 4:48:31 PM FINE org.jenkinsci.plugins.p4.client.ConnectionHelperP4: opened connection OKFeb 10, 2016 4:48:33 PM FINE org.jenkinsci.plugins.p4.client.ConnectionHelperP4: opened connection OKFeb 10, 2016 4:48:34 PM FINE org.jenkinsci.plugins.p4.client.ConnectionHelperP4: opened connection OKFeb 10, 2016 4:48:35 PM FINE org.jenkinsci.plugins.p4.client.ConnectionHelperP4: opened connection OKFeb 10, 2016 4:48:38 PM FINE hudson.tasks.MailAddressResolverRe
[JIRA] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files
Title: Message Title
Nickolay Rumyantsev updated an issue
Jenkins / JENKINS-32869
Artifactory plugin creates directories instead of uploading files
Change By:
Nickolay Rumyantsev
My job builds some tgz and rpms. I configured it to use Artifactory plugin as a Generic deployer to my test Artifactory instance.During the execution plugin reports in the log that it found the artifacts and deployed them successfully. But it ran too fast so I check the artifacts on the Artifactory page. There I saw that instead of files there were directories with the same names!Publishing rules are the following (yes, there are version-named directories as the dest):{code:java}/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.COREOS.tgz=>com/foo/bar/coreos/1.5.0.0-155.COREOS/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.RHEL.rpm=>com/foo/bar/rhel7/1.5.0.0-155.RHEL{code}I also tried appending the filename to the each rule, and a trailing slash too but it didn't help.I found a stackoverflow question about the same issue but there is not much information: http://stackoverflow.com/questions/30633080/artifactory-creating-folders-instead-of-deploying-artifact. Also raised: https://www.jfrog.com/jira/browse/HAP-690 I couldn't find a workaround so this is blocking me at the moment.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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 mo
[JIRA] [p4-plugin] (JENKINS-32879) Integration with mailer plugin is broken
Title: Message Title Alexey Sergin created an issue Jenkins / JENKINS-32879 Integration with mailer plugin is broken Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 10/Feb/16 1:53 PM Environment: Host OS: CentOS Linux release 7.2.1511 Java: java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64 Jenkins: jenkins-1.625.3-1.1.noarch (official rpm from jenkins-ci.org) P4 Plugin: version 1.3.6 (from http://updates.jenkins-ci.org/latest/p4.hpi) Mailer Plugin: version 1.11 (bundled with Jenkins) Perforce server: P4D/LINUX26X86_64/2015.1/1227227 Priority: Major Reporter: Alexey Sergin Use case: I have a Freestyle project with sources fetched by p4 plugin in "manual (custom view)" mode. The project has a post-build action "E-mail Notification" with a "Send separate e-mails to individuals who broke the build" checkbox checked. Mailer Plugin tries to compose a notification when build fails. The problem is that Mailer Plugin is not able to get emails corresponding to Perforce accounts. Example Console Output: Building in workspace /var/lib/jenkins/workspace/backup ... p4 client -o jenkins-master-backup + ... p4 info + P4 Task: establishing conne
[JIRA] [junit-plugin] (JENKINS-32878) Misleading information if parsing xml report failed
Title: Message Title Lucie Votypkova created an issue Jenkins / JENKINS-32878 Misleading information if parsing xml report failed Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 10/Feb/16 1:33 PM Priority: Minor Reporter: Lucie Votypkova When parsing xml report failed with know bug: java.util.MissingResourceException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages plugin marks test result as failure and shows output of "failed" test its error message during parsing. This is really confusing. I think that there would be some state like unknow or unreachable and output should not be definitely error message during parsing result xml. Or at least build should faild and inform user that results of his tests was not parsed. Add Comment
[JIRA] [aws-beanstalk-publisher-plugin] (JENKINS-32877) AWS Beanstalk Plugin should be able to use server role credentials
Title: Message Title Ashley Mercer created an issue Jenkins / JENKINS-32877 AWS Beanstalk Plugin should be able to use server role credentials Issue Type: Improvement Assignee: David Tanner Components: aws-beanstalk-publisher-plugin Created: 10/Feb/16 1:23 PM Priority: Minor Reporter: Ashley Mercer The AWS Beanstalk Publisher plugin currently allows a key ID and secret key to be set. However, when jenkins is itself running inside AWS (eg on an EC2 instance) we should be able assume the credentials provided by the IAM role assigned to the server. This removes the need to store secret keys in jenkins. This is already implemented in the S3 plugin, for reference: https://github.com/jenkinsci/s3-plugin/blob/master/src/main/java/hudson/plugins/s3/S3Profile.java Add Comment
[JIRA] [subversion-plugin] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Axel Müller edited a comment on JENKINS-31455 Re: Build instability with "ISVNAuthentication provider did not provide credentials" We have exactly the same problem on a Jenkins slave. The checkout involves SNV externals as well. I can provide the job configuration if required. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [subversion-plugin] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Axel Müller commented on JENKINS-31455 Re: Build instability with "ISVNAuthentication provider did not provide credentials" We have exactly the same problem on a Jenkins slave. The checkout involves SNV externals as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [multi-branch-project-plugin] (JENKINS-32388) Multi-branch plugin: Temporal error when syncing branches during build
Title: Message Title Fedor Dobrotvorsky assigned an issue to Matthew DeTullio Jenkins / JENKINS-32388 Multi-branch plugin: Temporal error when syncing branches during build Change By: Fedor Dobrotvorsky Assignee: Matthew DeTullio Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [subversion-plugin] (JENKINS-30293) Make Subversion plugin support Subversion 1.9
Title: Message Title Daniel Schürmann edited a comment on JENKINS-30293 Re: Make Subversion plugin support Subversion 1.9 -I am still suffering this bug because SubWCRev.exe insists to work only with a 1.9 working copy. -Edit: After setting the working copy format from 1.4 (8) to 1.8 (31) AND deleting the workspace folder it works. (Sorry for the noise) It would be nice if you could change working copy format combobox to "1.8/1.9 (31)" to avoid the confusion in future. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [subversion-plugin] (JENKINS-30293) Make Subversion plugin support Subversion 1.9
Title: Message Title Daniel Schürmann edited a comment on JENKINS-30293 Re: Make Subversion plugin support Subversion 1.9 - I am still suffering this bug because SubWCRev.exe insists to work only with a 1.9 working copy. - Output: SubWCRev Edit : E155036: The After setting the working copy at 'C:\Program Files (x86)\Jenkins\jobs\dpt\workspace\DPT2009\Source_dpt\dpt\Module\KonfigurationLoopkarte3500V1'is too old ( format from 1.4 ( 8) to work with client version ' 1. 9.3 8 ( r1718519)' (expects format 31) . You need to upgrade AND deleting the working copy first workspace folder it works . (Sorry for the noise) It would be nice if you could change working copy format combobox to be able to create a " 1. 8/1. 9 working copy (31)" to solve this issue avoid the confusion in future . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [subversion-plugin] (JENKINS-30293) Make Subversion plugin support Subversion 1.9
Title: Message Title Daniel Schürmann updated an issue Jenkins / JENKINS-30293 Make Subversion plugin support Subversion 1.9 Change By: Daniel Schürmann Comment: Changelog SVNKit== version 1.8.12 ==+ Support for Subversion 1.9 new FSFS repository format. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [multi-branch-project-plugin] (JENKINS-32388) Multi-branch plugin: Temporal error when syncing branches during build
Title: Message Title Fedor Dobrotvorsky commented on JENKINS-32388 Re: Multi-branch plugin: Temporal error when syncing branches during build Also it was revealed in Jenkins v1.646 with Multi-Branch Project Plugin v0.4.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [multi-branch-project-plugin] (JENKINS-32388) Multi-branch plugin: Temporal error when syncing branches during build
Title: Message Title Fedor Dobrotvorsky assigned an issue to Unassigned Jenkins / JENKINS-32388 Multi-branch plugin: Temporal error when syncing branches during build Change By: Fedor Dobrotvorsky Assignee: Fedor Dobrotvorsky Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [multi-branch-project-plugin] (JENKINS-32388) Multi-branch plugin: Temporal error when syncing branches during build
Title: Message Title Fedor Dobrotvorsky assigned an issue to Fedor Dobrotvorsky Jenkins / JENKINS-32388 Multi-branch plugin: Temporal error when syncing branches during build Change By: Fedor Dobrotvorsky Assignee: Matthew DeTullio Fedor Dobrotvorsky Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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.
