[JIRA] [cli] (JENKINS-31417) Extract connect-node CLI command from Core to CLI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31417 Re: Extract connect-node CLI command from Core to CLI Code changed in jenkins User: Pavel Janousek Path: core/src/main/java/hudson/cli/ConnectNodeCommand.java core/src/main/java/hudson/model/Computer.java core/src/main/resources/hudson/cli/Messages.properties core/src/main/resources/hudson/cli/Messages_da.properties core/src/main/resources/hudson/cli/Messages_de.properties core/src/main/resources/hudson/cli/Messages_es.properties core/src/main/resources/hudson/cli/Messages_it.properties core/src/main/resources/hudson/cli/Messages_ja.properties core/src/main/resources/hudson/cli/Messages_pt_BR.properties core/src/main/resources/hudson/cli/Messages_zh_CN.properties core/src/main/resources/hudson/cli/Messages_zh_TW.properties core/src/main/resources/hudson/model/Messages.properties core/src/main/resources/hudson/model/Messages_bg.properties core/src/main/resources/hudson/model/Messages_da.properties core/src/main/resources/hudson/model/Messages_de.properties core/src/main/resources/hudson/model/Messages_es.properties core/src/main/resources/hudson/model/Messages_it.properties core/src/main/resources/hudson/model/Messages_ja.properties core/src/main/resources/hudson/model/Messages_lt.properties core/src/main/resources/hudson/model/Messages_pt_BR.properties core/src/main/resources/hudson/model/Messages_zh_CN.properties core/src/main/resources/hudson/model/Messages_zh_TW.properties test/src/test/java/hudson/cli/ConnectNodeCommandTest.java http://jenkins-ci.org/commit/jenkins/6b328e10d8aedd02e61a2d49863f302046588b86 Log: JENKINS-31417 CLI command connect-node extracted from core to CLI (#1923) JENKINS-31417 CLI command connect-node extracted from core to CLI connect-node extended to accept multiple node names connect-node covered by test-cases Slighty modified Javadoc Fixed translations after rebase Add Comment
[JIRA] [cli] (JENKINS-34531) Extend online-node to cover more agents at once
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34531 Re: Extend online-node to cover more agents at once Code changed in jenkins User: Pavel Janousek Path: core/src/main/java/hudson/cli/OnlineNodeCommand.java test/src/test/java/hudson/cli/OnlineNodeCommandTest.java http://jenkins-ci.org/commit/jenkins/8d5afe877bfd75f606aad43868d49a6b4311fef6 Log: JENKINS-34531 Extended CLI online-node for accepting multiple agents (#2343) JENKINS-34531 Extended CLI online-node for accepting multiple agents Polished and extended related TC as well. Simplified string composition Simplified initialization of HashSet 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-35008) hudson.tasks.Mailer cannot be used in a composable manner
Title: Message Title mdonohue closed an issue as Fixed Jenkins / JENKINS-35008 hudson.tasks.Mailer cannot be used in a composable manner Change By: mdonohue Status: Open Closed 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] [core] (JENKINS-35008) hudson.tasks.Mailer cannot be used in a composable manner
Title: Message Title mdonohue commented on JENKINS-35008 Re: hudson.tasks.Mailer cannot be used in a composable manner Okay, I finally got the pom updated, and now that I tested against 1.635, i see this was already fixed. Sorry for the noise. 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-25249) Post-commit hook for P4 plugin
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-25249 Re: Post-commit hook for P4 plugin I did some work on this to make it work with Pipeline: https://github.com/Dohbedoh/p4-plugin/commit/8602fddd4e1ebb45e45e8ed886b4fa9eccc2deed I am gonna enrich this with tests and submit a PR as soon as possible. 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-29979) Workflow plugin unable to save perforce paramters
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-29979 Re: Workflow plugin unable to save perforce paramters I proposed a PR for this: https://github.com/jenkinsci/p4-plugin/pull/23 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-35008) hudson.tasks.Mailer cannot be used in a composable manner
Title: Message Title mdonohue updated an issue Jenkins / JENKINS-35008 hudson.tasks.Mailer cannot be used in a composable manner Change By: mdonohue The join plugin includes select post-build actions as 'join' actions. This requires a certain amount of composability in the configuration screen to work - the email trigger doesn't work here, for example. The problem is that the join trigger post-build actions appear first, and consume the form keys before the main action. Using the JSON format data submission should fix this, and would provide a better example for future plugin creators. See JENKINS-7529 for the motivation for this change Tested with Jenkins 1.424 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-35008) hudson.tasks.Mailer cannot be used in a composable manner
Title: Message Title mdonohue updated an issue Jenkins / JENKINS-35008 hudson.tasks.Mailer cannot be used in a composable manner Change By: mdonohue The join plugin includes select post-build actions as 'join' actions. This requires a certain amount of composability in the configuration screen to work - the email trigger doesn't work here, for example. The problem is that the join trigger post-build actions appear first, and consume the form keys before the main action. Using the JSON format data submission should fix this, and would provide a better example for future plugin creators. See JENKINS-7529 for the motivation for this change 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-35008) hudson.tasks.Mailer cannot be used in a composable manner
Title: Message Title mdonohue created an issue Jenkins / JENKINS-35008 hudson.tasks.Mailer cannot be used in a composable manner Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/May/22 1:03 AM Priority: Minor Reporter: mdonohue The join plugin includes select post-build actions as 'join' actions. This requires a certain amount of composability in the configuration screen to work - the email trigger doesn't work here, for example. The problem is that the join trigger post-build actions appear first, and consume the form keys before the main action. Using the JSON format data submission should fix this, and would provide a better example for future plugin creators. Add Comment
[JIRA] [join-plugin] (JENKINS-7529) Allow an email to be sent following a successful join activation
Title: Message Title mdonohue commented on JENKINS-7529 Re: Allow an email to be sent following a successful join activation The problem is still present in Jenkins 1.424. So this is a bug in core jenkins - it's easy to add the email post-build action to the join trigger, but it breaks the email functionality for non-join cases, so it is left out intentionally. 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] [join-plugin] (JENKINS-7529) Allow an email to be sent following a successful join activation
Title: Message Title mdonohue commented on JENKINS-7529 Re: Allow an email to be sent following a successful join activation This was removed because the email trigger wasn't able to be used in multiple places on the same form: see JENKINS-4384 I'll see if it behaves better in 2016, compared to 2009. 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-33874) Upgrade git-plugin to new parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33874 Re: Upgrade git-plugin to new parent POM Code changed in jenkins User: Andres Rodriguez Path: pom.xml http://jenkins-ci.org/commit/git-plugin/82e929e8b3b041f76a144151f695440c5e464b1c Log: JENKINS-33874 Pick up master and POM 2.6 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-33874) Upgrade git-plugin to new parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33874 Re: Upgrade git-plugin to new parent POM Code changed in jenkins User: Andres Rodriguez Path: pom.xml src/test/java/hudson/plugins/git/AbstractGitProject.java src/test/java/hudson/plugins/git/AbstractGitTestCase.java src/test/java/hudson/plugins/git/GitPublisherTest.java src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/081576eb220806b9fc4c15f1326c5132f7b5d63e Log: JENKINS-33874 Update to parent POM 2.5 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-33874) Upgrade git-plugin to new parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33874 Re: Upgrade git-plugin to new parent POM Code changed in jenkins User: Andres Rodriguez Path: src/main/java/hudson/plugins/git/BranchSpec.java src/main/java/hudson/plugins/git/GitStatus.java src/main/java/hudson/plugins/git/browser/GitoriousWeb.java src/main/java/hudson/plugins/git/browser/RhodeCode.java src/main/java/hudson/plugins/git/browser/Stash.java src/main/java/hudson/plugins/git/util/BuildData.java http://jenkins-ci.org/commit/git-plugin/8ca347bb54a3dc1cc85d70159baac768d610de0e Log: JENKINS-33874 Javadoc Fixes 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-33874) Upgrade git-plugin to new parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33874 Re: Upgrade git-plugin to new parent POM Code changed in jenkins User: Andres Rodriguez Path: pom.xml http://jenkins-ci.org/commit/git-plugin/8e4ca0fb72d1b7b91a7baed57a52b7f9c8b7c416 Log: JENKINS-33874 Pick up parent POM 2.8 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-33874) Upgrade git-plugin to new parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33874 Re: Upgrade git-plugin to new parent POM Code changed in jenkins User: Mark Waite Path: pom.xml src/main/java/hudson/plugins/git/BranchSpec.java src/main/java/hudson/plugins/git/GitSCM.java src/main/java/hudson/plugins/git/GitStatus.java src/main/java/hudson/plugins/git/browser/GitoriousWeb.java src/main/java/hudson/plugins/git/browser/RhodeCode.java src/main/java/hudson/plugins/git/browser/Stash.java src/main/java/hudson/plugins/git/util/BuildData.java src/test/java/hudson/plugins/git/AbstractGitProject.java src/test/java/hudson/plugins/git/AbstractGitTestCase.java src/test/java/hudson/plugins/git/GitPublisherTest.java src/test/java/hudson/plugins/git/GitSCMTest.java src/test/java/hudson/plugins/git/RevisionParameterActionTest.java src/test/java/hudson/plugins/git/TestGitRepo.java src/test/java/hudson/plugins/git/browser/TFS2013GitRepositoryBrowserTest.java http://jenkins-ci.org/commit/git-plugin/4289aacbb493cfcb78c8276c52e945802942ffd5 Log: Merge pull request #390 from andresrc/JENKINS-33874 JENKINS-33874 Upgrade to Parent POM Compare: https://github.com/jenkinsci/git-plugin/compare/dd53701fdbe8...4289aacbb493 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-33874) Upgrade git-plugin to new parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33874 Re: Upgrade git-plugin to new parent POM Code changed in jenkins User: Andres Rodriguez Path: src/test/java/hudson/plugins/git/AbstractGitTestCase.java src/test/java/hudson/plugins/git/GitSCMTest.java src/test/java/hudson/plugins/git/TestGitRepo.java src/test/java/hudson/plugins/git/browser/TFS2013GitRepositoryBrowserTest.java http://jenkins-ci.org/commit/git-plugin/dbf9ab66296863e30133f3c113fd8db77c602fc3 Log: JENKINS-33874 Migrate tests from `HudsonTestCase` to `JenkinsRule` 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-33874) Upgrade git-plugin to new parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33874 Re: Upgrade git-plugin to new parent POM Code changed in jenkins User: Andres Rodriguez Path: src/main/java/hudson/plugins/git/GitSCM.java src/main/java/hudson/plugins/git/browser/GitoriousWeb.java src/main/java/hudson/plugins/git/browser/RhodeCode.java src/main/java/hudson/plugins/git/browser/Stash.java src/main/java/hudson/plugins/git/util/BuildData.java src/test/java/hudson/plugins/git/AbstractGitProject.java src/test/java/hudson/plugins/git/AbstractGitTestCase.java src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/4e3fdca78dc86777f587167f23b0f729cd0d7715 Log: JENKINS-33874 Address review comments. 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-28840) Deadlock between Queue.maintain and Executor.interrupt
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28840 Re: Deadlock between Queue.maintain and Executor.interrupt Code changed in jenkins User: Andres Rodriguez Path: pom.xml src/test/java/hudson/plugins/git/AbstractGitProject.java src/test/java/hudson/plugins/git/AbstractGitTestCase.java src/test/java/hudson/plugins/git/RevisionParameterActionTest.java http://jenkins-ci.org/commit/git-plugin/daf453dfc43db81ede5cde60d0469fda0b3321ab Log: JENKINS-33874 Move to 1.609.3 (because of JENKINS-28840 ) 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-33874) Upgrade git-plugin to new parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33874 Re: Upgrade git-plugin to new parent POM Code changed in jenkins User: Andres Rodriguez Path: src/test/java/hudson/plugins/git/AbstractGitProject.java src/test/java/hudson/plugins/git/AbstractGitTestCase.java src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/7631c2912545ae92c1eec6df647e6f6f4628c1b2 Log: JENKINS-33874 Clean up unused imports. 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-33874) Upgrade git-plugin to new parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33874 Re: Upgrade git-plugin to new parent POM Code changed in jenkins User: Andres Rodriguez Path: src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/b33c6a59d6d0c2d196431d11c368e9e4647c0e59 Log: JENKINS-33874 Clean environment before builds. 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-33874) Upgrade git-plugin to new parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33874 Re: Upgrade git-plugin to new parent POM Code changed in jenkins User: Andres Rodriguez Path: pom.xml src/test/java/hudson/plugins/git/AbstractGitProject.java src/test/java/hudson/plugins/git/AbstractGitTestCase.java src/test/java/hudson/plugins/git/RevisionParameterActionTest.java http://jenkins-ci.org/commit/git-plugin/daf453dfc43db81ede5cde60d0469fda0b3321ab Log: JENKINS-33874 Move to 1.609.3 (because of JENKINS-28840 ) 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] [docker] (JENKINS-35007) Add tag for official Docker repository for version 2.5
Title: Message Title Sascha Gaspar updated an issue Jenkins / JENKINS-35007 Add tag for official Docker repository for version 2.5 Change By: Sascha Gaspar Please update the docker container ([https://hub.docker.com/r/_/jenkins/]) to version 2.5 and in the future to the newest 2.x version. The newest Tag is 2.3.I'm not shure sure , but does the issue [https://issues.jenkins-ci.org/browse/JENKINS-33718] mean the same think for an other version? 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] [docker] (JENKINS-35007) Add tag for official Docker repository for version 2.5
Title: Message Title Sascha Gaspar created an issue Jenkins / JENKINS-35007 Add tag for official Docker repository for version 2.5 Issue Type: Bug Assignee: Nicolas De Loof Components: docker Created: 2016/May/21 11:48 PM Priority: Major Reporter: Sascha Gaspar Please update the docker container (https://hub.docker.com/r/_/jenkins/) to version 2.5 and in the future to the newest 2.x version. The newest Tag is 2.3. I'm not shure, but does the issue https://issues.jenkins-ci.org/browse/JENKINS-33718 mean the same think for an other version? Add Comment
[JIRA] [join-plugin] (JENKINS-9946) join should be able to wait for all downstream jobs
Title: Message Title mdonohue closed an issue as Duplicate Jenkins / JENKINS-9946 join should be able to wait for all downstream jobs Change By: mdonohue Status: Open Closed Resolution: Duplicate 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] [join-plugin] (JENKINS-9946) join should be able to wait for all downstream jobs
Title: Message Title mdonohue commented on JENKINS-9946 Re: join should be able to wait for all downstream jobs JENKINS-11274 appears better thought out. Closing this as a duplicate. 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] [join-plugin] (JENKINS-16212) Exception thrown from join plugin as it can't find BuildTrigger class in Parameterized Trigger plugin
Title: Message Title mdonohue commented on JENKINS-16212 Re: Exception thrown from join plugin as it can't find BuildTrigger class in Parameterized Trigger plugin "Latest everything as of now..." I'm glad you were up to date in 2012, but following up on this bug 4 years later, this description is very hard to follow. This is why software has version numbers - please use them. 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] [join-plugin] (JENKINS-25290) Join configuration not updated when job is renamed
Title: Message Title mdonohue resolved as Fixed I didn't write the code, but this was fixed by join-1.15-4-g4f4922b Jenkins / JENKINS-25290 Join configuration not updated when job is renamed Change By: mdonohue 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] [join-plugin] (JENKINS-25290) Join configuration not updated when job is renamed
Title: Message Title mdonohue commented on JENKINS-25290 Re: Join configuration not updated when job is renamed Reviewing the commit history, it looks like Nicolas De Loof fixed this after the 1.15 release of the join plugin. Since this is reported against 1.15, I see that it was fixed later. 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] [join-plugin] (JENKINS-25290) Join configuration not updated when job is renamed
Title: Message Title mdonohue commented on JENKINS-25290 Re: Join configuration not updated when job is renamed I just tested this with freestyle projects - i have start, left, right, finish. I have left and right triggered by 'start' and finish is the join-trigger post build action. Jenkins 1.424, with a fresh build of the join plugin, but it should be functionally the same as join 1.19 I renamed left to left2, and that was picked up, as expected. I also renamed 'finish' to 'finish3' and the 'start' project now triggers 'finish3' as the join-trigger post build action. So it seems everything works correctly. Can you give me more specifics to reproduce the problem you are seeing? 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-24070) Error: Wipe Out Workspace blocked by SCM
Title: Message Title dan tran commented on JENKINS-24070 Re: Error: Wipe Out Workspace blocked by SCM ah, it works now, i just need to setup the global configuration for perforce plugin to remove client as well. s 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-24070) Error: Wipe Out Workspace blocked by SCM
Title: Message Title dan tran resolved as Fixed Jenkins / JENKINS-24070 Error: Wipe Out Workspace blocked by SCM Change By: dan tran Status: Reopened 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] [p4-plugin] (JENKINS-24070) Error: Wipe Out Workspace blocked by SCM
Title: Message Title dan tran reopened an issue still see this issue at 1.3.9. I am not going to revert back to 1.3.5 and see if I can help Paul to trouble shoot this issue Jenkins / JENKINS-24070 Error: Wipe Out Workspace blocked by SCM Change By: dan tran Resolution: Fixed Status: Closed 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] [docker-custom-build-environment-plugin] (JENKINS-35006) Allow 'sudo' in all docker commands; docker-custom-build-environment
Title: Message Title ayache khettar created an issue Jenkins / JENKINS-35006 Allow 'sudo' in all docker commands; docker-custom-build-environment Issue Type: New Feature Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 2016/May/21 7:46 PM Priority: Minor Reporter: ayache khettar Hi It would be good if we can run docker commands with sudo mode. Currently the plugin does not allow to run docker commands with 'sudo'. This is needed where Jenkins is run as a docker container with mounted docker socket of the host machine (not docker in docker case which is not recommended). Add Comment
[JIRA] [cmakebuilder-plugin] (JENKINS-34998) Make CMake plugin compatible with pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34998 Re: Make CMake plugin compatible with pipeline Code changed in jenkins User: 15knots Path: src/main/java/hudson/plugins/cmake/AbstractCmakeBuilder.java src/main/java/hudson/plugins/cmake/CToolBuilder.java src/main/java/hudson/plugins/cmake/CmakeBuilder.java http://jenkins-ci.org/commit/cmakebuilder-plugin/e95ede2fb3a5850c2dfb90e3b647fe6627121e52 Log: JENKINS-34998: Make CMake plugin compatible with pipeline 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] [cmakebuilder-plugin] (JENKINS-35005) Cannot build ih 'Use cmake' is true
Title: Message Title Martin Weber created an issue Jenkins / JENKINS-35005 Cannot build ih 'Use cmake' is true Issue Type: Bug Assignee: Martin Weber Components: cmakebuilder-plugin Created: 2016/May/21 5:34 PM Priority: Major Reporter: Martin Weber Build output: [kjadshfakshfdkaj] $ /home/wr/devel/src/cmakebuilder-plugin/work/tools/hudson.plugins.cmake.CmakeTool/3.5.2/bin/cmake --build /home/wr/devel/src/cmakebuilder-plugin/work/jobs/aaa/workspace/kjadshfakshfdkaj clean all Unknown argument clean Unknown argument all Usage: cmake --build [options] [-- [native-options]] Options: = Project binary directory to be built. --target = Build instead of default targets. --config = For multi-configuration tools, choose . --clean-first = Build target 'clean' first, then build. (To clean only, use --target 'clean'.) --use-stderr = Ignored. Behavior is default in CMake >= 3.0. -- = Pass remaining options to the native tool. Build step 'CMake Build' changed build result to FAILURE
[JIRA] [cmakebuilder-plugin] (JENKINS-34998) Make CMake plugin compatible with pipeline
Title: Message Title Martin Weber started work on JENKINS-34998 Change By: Martin Weber 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] [core] (JENKINS-33396) Add fancy 2.0 tabs UX to System config UI
Title: Message Title Tom FENNELLY commented on JENKINS-33396 Re: Add fancy 2.0 tabs UX to System config UI The master PR was created last week: https://github.com/jenkinsci/jenkins/pull/2339 Yes, needs some tests. 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] [jacoco-plugin] (JENKINS-22776) Jacoco: spaces don't work when listing multiple class/source folders
Title: Message Title Ori Danus commented on JENKINS-22776 Re: Jacoco: spaces don't work when listing multiple class/source folders I'm getting this error with configuration of only one "Path to class directory" and one "Path to source", but 6 exec files, configured like this - results/jacoco_worker*.output is this related? 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] [bitbucket-branch-source-plugin] (JENKINS-33507) Bitbucket Server webhooks and Bitbucket Cloud build status notifications
Title: Message Title Ben Middleton commented on JENKINS-33507 Re: Bitbucket Server webhooks and Bitbucket Cloud build status notifications Is there any scope to modify the hook implemention to use https://github.com/Nerdwin15/stash-jenkins-postreceive-webhook - which works with the default Git plugin? 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] [bitbucket-branch-source-plugin] (JENKINS-33507) Bitbucket Server webhooks and Bitbucket Cloud build status notifications
Title: Message Title Ben Middleton edited a comment on JENKINS-33507 Re: Bitbucket Server webhooks and Bitbucket Cloud build status notifications Is there any scope to modify the hook implemention implementation to use https://github.com/Nerdwin15/stash-jenkins-postreceive-webhook - which works with the default Git plugin? 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-33396) Add fancy 2.0 tabs UX to System config UI
Title: Message Title Spike Washburn commented on JENKINS-33396 Re: Add fancy 2.0 tabs UX to System config UI Status: Tom needs to move the PR over to master and add tests for the new config UI. Best done after the 2.6 weekly so that it has time to gel. 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] [vmware-vrealize-orchestrator-plugin] (JENKINS-34178) There *may* be a problem with the vm@VC:VirtualMachine parameter name.
Title: Message Title Agila Govindaraju edited a comment on JENKINS-34178 Re: There *may* be a problem with the vm@VC:VirtualMachine parameter name. I still see an @ in your rdvm.mydomain.com * @ * vm-244555 value it should be having / in the value instead of @ for ex: rdvm.mydomain.com * / * vm-244555 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] [vmware-vrealize-orchestrator-plugin] (JENKINS-34178) There *may* be a problem with the vm@VC:VirtualMachine parameter name.
Title: Message Title Agila Govindaraju commented on JENKINS-34178 Re: There *may* be a problem with the vm@VC:VirtualMachine parameter name. I still see an @ in your rdvm.mydomain.com*@vm-244555 value it should be rdvm.mydomain.com/*vm-244555 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] [android-emulator-plugin] (JENKINS-35004) Android Emulator plugin fails to shutdown AVD since SDK emulator 25.1.6 release
Title: Message Title Andrey Kopeyko created an issue Jenkins / JENKINS-35004 Android Emulator plugin fails to shutdown AVD since SDK emulator 25.1.6 release Issue Type: Bug Assignee: Christopher Orr Components: android-emulator-plugin Created: 2016/May/21 9:34 AM Environment: Ubuntu 16.04 64bit Android SDK revision 25.1.6 Jenkins 2.5 and 1.651.2 Android Emulator Plugin 2.14.1 Priority: Critical Reporter: Andrey Kopeyko Android Emulator plugin fails to correctly shutdown the emulator started for the test, but this fact is not logged in console output: [android] Starting Android emulator [android] Erasing existing emulator data... $ /var/lib/jenkins/tools/android-sdk/tools/emulator -engine classic -ports 5748,5749 -report-console tcp:5832,max=60 -prop persist.sys.language=en -prop persist.sys.country=US -avd hudson_en-US_160_HVGA_android-19 -no-snapshot-load -no-snapshot-save -wipe-data -no-window -no-audio -gpu off [android] Emulator reported that the console is available on port 5,748 [android] Waiting for emulator to finish booting... $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s emulator-5748 wait-for-device shell getprop init.svc.bootanim [android] Emulator reported that the startup process is 'stopped' $
[JIRA] [gradle-jpi-plugin] (JENKINS-34945) Build fails for jenkinsCore >= 2.0
Title: Message Title Fredrik Bruzelius commented on JENKINS-34945 Re: Build fails for jenkinsCore >= 2.0 Of course! I have made test builds against Jenkins Core 2.5 and 1.658 using the patched plugin. Servlet API JAR is now resolved properly in both cases. 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] [valgrind-plugin] (JENKINS-35003) Allow to specify source directory mappings (aka substitute paths).
Title: Message Title Jacek Tomaka created an issue Jenkins / JENKINS-35003 Allow to specify source directory mappings (aka substitute paths). Issue Type: Improvement Assignee: Jacek Tomaka Components: valgrind-plugin Created: 2016/May/21 8:04 AM Priority: Major Reporter: Jacek Tomaka Somethimes you do not want to build a program and execute lengthy valgrind/memcheck/hellgrind examination from within the same JENKINS jobs. When workspace where a program is run under valgrind is different from the workspace where program was built the vagrant plugin will not be able to find sources. In gdb this problem is solved using set-substitute-path. In valgring JENKINS plugin it is proposed that a source mappings are added. Here is the link to gdb command documentation: https://sourceware.org/gdb/onlinedocs/gdb/Source-Path.html#set%20substitute%2dpath Add Comment
[JIRA] [maven-plugin] (JENKINS-34900) Naginator plugin throwing Null Pointer Exception
Title: Message Title ikedam commented on JENKINS-34900 Re: Naginator plugin throwing Null Pointer Exception https://github.com/jenkinsci/naginator-plugin/pull/31 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] [maven-plugin] (JENKINS-34900) Naginator plugin throwing Null Pointer Exception
Title: Message Title ikedam started work on JENKINS-34900 Change By: ikedam 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] [core] (JENKINS-31870) Unable to use LDAP user credentials in build configuration
Title: Message Title
ikedam commented on JENKINS-31870
Re: Unable to use LDAP user credentials in build configuration
stephenconnolly Let me see what you mean:
Separate the authorization configuration from the project configuration. This allows Jenkins to decide the authorization of builds during configuring projects.
When a plugin lists up credentials,
public ListBoxModel doFillCredentialsIdItems(@AncestorInPath Job project) {
Authentication auth = Tasks.getAuthenticationOf(project);
return new StandardUsernameListBoxModel().withEmptySelection().withAll(
CredentialsProvider.lookupCredentials(StandardUsernameCredentials.class, auth);
}
Even if the authorization is changed after the project configuration is saved, it doesn't cause a security issue as the access to the credential is blocked at build time.
That makes sense 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] [junit-plugin] (JENKINS-34666) JUnit test durations accounted improperly
Title: Message Title Christopher Head updated an issue Jenkins / JENKINS-34666 JUnit test durations accounted improperly Change By: Christopher Head Environment: Linux amd64, Jenkins v2. 2 5 , jUnit plugin v1.13 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-timeout-plugin] (JENKINS-32968) BuildTimeOut plugin throws NullPointerException
Title: Message Title ikedam resolved as Won't Fix I decided to close this issue with "Won't Fix" as: 1. There's no way to reproduce the issue. It looks caused by a broken configuration and I can't ensure behaviors for those cases. 2. Even if I fixed the NPE, build-timeout shouldn't work as expected without configurations. Jenkins / JENKINS-32968 BuildTimeOut plugin throws NullPointerException Change By: ikedam Status: Open Resolved Resolution: Won't Fix 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.
