[JIRA] [p4-plugin] (JENKINS-24512) Add option to lock the created workspace to a host
dan tran edited a comment on JENKINS-24512 Add option to lock the created workspace to a host You should set the host at every build. I now running into performance issue where P4Maven takes a log time to discover the current workspace client where it has to scan thru a long list of clients created by my Jenkins/CI cluster on the same P4 build account This is a crucial feature for me to have p4jenkins to setup build host correctly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-24512) Add option to lock the created workspace to a host
dan tran commented on JENKINS-24512 Add option to lock the created workspace to a host You should set the host at every build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-26589) p4jenkins set client root to "null"
dan tran updated JENKINS-26589 p4jenkins set client root to "null" Change By: dan tran (25/Jan/15 7:38 AM) Description: my jenkins job uses p4jenkins (1.1.2) custom view with an assigned workspace name, and run runs on a jenkins slave. When the job starts, p4jenkins create the workspace client and set the root directory to "null" string ( literally 4 chars "null" string)The prefer way should be the valid root directly at the slaveThis causes a problem when using the same workspace client with P4Maven where it expects a valid root directory. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-26589) p4jenkins set client root to "null"
dan tran created JENKINS-26589 p4jenkins set client root to "null" Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 25/Jan/15 7:35 AM Description: my jenkins job uses p4jenkins custom view with an assigned workspace name, and run on slave. When the job starts, p4jenkins create the workspace client and set the root directory to "null" string ( literally 4 chars "null" string) The prefer way should be the root directly at the slave This causes a problem when using the same workspace client with P4Maven where it expects a valid root directory. Environment: linux Project: Jenkins Priority: Major Reporter: dan tran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-26491) Make ircbot interrupteble
ikedam updated JENKINS-26491 Make ircbot interrupteble Please report followings: Versions of your Jenkins, instant-messaging-plugin, ircbot-plugin. Was there log outputs? Especially, I expect there was a log like "There was an error sending notification to: ". What happens if you click "x" of a build when the build stucks with ircbot? (that is, abort the build by yourself) As long as I know, the first click works like build-timeout plugin. There's a case that the first click is ignored. In that case, the second click forcibly aborts the build. Change By: ikedam (25/Jan/15 3:12 AM) Summary: CountDownLatch interruptable? Make ircbot interrupteble Issue Type: Bug Improvement Component/s: instant-messaging-plugin Component/s: ircbot-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [copyartifact-plugin] (JENKINS-24887) Workflow support of Copyartifact
ikedam closed JENKINS-24887 as Fixed Workflow support of Copyartifact Released 1.34. It will be available in a day. Change By: ikedam (25/Jan/15 2:40 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [youtrack-plugin] (JENKINS-24487) Possibility to fail builds when there is problems applying youtrack commands
SCM/JIRA link daemon commented on JENKINS-24487 Possibility to fail builds when there is problems applying youtrack commands Code changed in jenkins User: ikedam Path: src/test/java/hudson/plugins/copyartifact/CopyArtifactWorkflowTest.java http://jenkins-ci.org/commit/copyartifact-plugin/6e1aeb1f5878f8bb6cd0424f4affc9e8aa9b9608 Log: JENKINS-24487 Uses writeFile instead of sh, which allows tests run on Windows. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [youtrack-plugin] (JENKINS-24487) Possibility to fail builds when there is problems applying youtrack commands
SCM/JIRA link daemon commented on JENKINS-24487 Possibility to fail builds when there is problems applying youtrack commands Code changed in jenkins User: ikedam Path: src/test/java/hudson/plugins/copyartifact/CopyArtifactWorkflowTest.java http://jenkins-ci.org/commit/copyartifact-plugin/34632521abb7e18fe3b4559b534d3e01c61d0177 Log: Merge pull request #56 from ikedam/feature/JENKINS-24887_UseWriteFile JENKINS-24487 Allows tests run on Windows Compare: https://github.com/jenkinsci/copyartifact-plugin/compare/325f16adb3fc...34632521abb7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-26571) Job page becomes un responsive when there are a lot of builds in the queue
Daniel Beck commented on JENKINS-26571 Job page becomes un responsive when there are a lot of builds in the queue We recently moved the parameters into a tool tip for JENKINS-22311. This will be in 1.598. This should at least lessen the impact. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [google-play-android-publisher-plugin] (JENKINS-26542) Cannot change Google Service Account
Alex V commented on JENKINS-26542 Cannot change Google Service Account So after doing more checks, there are two small behaviors that were confusing me: In the job configuration page, the dropdown list of google play accounts always show the first one (even with different names), instead of showing the one actually in the config file (might be the number 2 in the list) The name of the google play account is used in the config file as the ID of that account. As a result you shouldnt have multiple accounts with the same name ( but the credential config page allows you to ), and you cannot rename your account in jenkins settings without reconfiguring your jobs. I dont remember seeing any warning in the credential configuration about it though. Cheers ! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-26583) Env-inject plugin suppress variables contributed by extension points
Daniel Beck commented on JENKINS-26583 Env-inject plugin suppress variables contributed by extension points Should be considered a blocker if it affects jobs that don't enable any env-inject related config options. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [embeddable-build-status-plugin] (JENKINS-26585) Exclude view name from links and/or add fields for links with without view name
Daniel Beck commented on JENKINS-26585 Exclude view name from links and/or add fields for links with without view name FWIW Jenkins core behavior of Item.getUrl() changed (consistent with previous documentation) around 1.540-1.560, so if the plugin is only tested against older versions, this issue may not appear. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-26588) Can't disable the "private repository" setting for "Invoke top-level Maven targets" build step
Daniel Beck updated JENKINS-26588 Can't disable the "private repository" setting for "Invoke top-level Maven targets" build step Be more specific as to what the problem is. How do you determine that it uses a private repository? How is your job configured? Change By: Daniel Beck (24/Jan/15 11:56 PM) Priority: Blocker Major Component/s: core Component/s: maven-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-26587) Checkout fails with Multiple SCMs plugin on commit notification
Vasili Kvockin updated JENKINS-26587 Checkout fails with Multiple SCMs plugin on commit notification Change By: Vasili Kvockin (24/Jan/15 10:28 PM) Component/s: git-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-26588) Can't disable the "private repository" setting for "Invoke top-level Maven targets" build step
Jeff VIncent updated JENKINS-26588 Can't disable the "private repository" setting for "Invoke top-level Maven targets" build step Change By: Jeff VIncent (24/Jan/15 10:29 PM) Description: I have a multi-module test project that due to shared code needs to be built together. However I need to run only a subset of tests from one specific module.I have been unsuccessful in crafting a command-line that will run maven to build everything, but only run some sub-module tests. I tried splitting up the build step and test run steps by using the "Invoke top-level Maven targets" build job, but it uses a private repository and even though there is an option to disable the private repository, it does not seem to take effect.The result is that the test run step can't resolve the build artifacts and fails to run. I need to be able to run a build of the test modules as a separate step in a way that allows subsequent build steps to see the same maven repository and artifacts. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-26588) Can't disable the "private repository" setting for "Invoke top-level Maven targets" build step
Jeff VIncent updated JENKINS-26588 Can't disable the "private repository" setting for "Invoke top-level Maven targets" build step Change By: Jeff VIncent (24/Jan/15 10:26 PM) Description: I have a multi-module test project that due to shared code needs to be built together. However I need to run only a subset of tests from one specific module.I have been unsuccessful in crafting a command-line that will run maven to build everything, but only run some sub-module tests. I tried splitting up the build step and test run steps by using the "Invoke top-level Maven targets" build job, but it uses a private repository and even though there is an option to disable the private repository, it does not seem to take effect.The result is that the test run step can't resolve the build artifacts and fails to run. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-26588) Can't disable the "private repository" setting for "Invoke top-level Maven targets" build step
Jeff VIncent created JENKINS-26588 Can't disable the "private repository" setting for "Invoke top-level Maven targets" build step Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 24/Jan/15 10:23 PM Project: Jenkins Priority: Blocker Reporter: Jeff VIncent This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [multiple-scms-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification
Vasili Kvockin commented on JENKINS-26587 Checkout fails with Multiple SCMs plugin on commit notification possible fix in https://github.com/jenkinsci/git-plugin/pull/296 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [multiple-scms-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification
Vasili Kvockin
created JENKINS-26587
Checkout fails with Multiple SCMs plugin on commit notification
Issue Type:
Bug
Assignee:
Kevin Bell
Components:
multiple-scms-plugin
Created:
24/Jan/15 8:55 PM
Description:
also similar to https://github.com/janinko/ghprb/issues/171
Setup:
free style project
multiple scms repository setting
two git repositories configured
stash notifications for both repositories
a commit is pushed to second repository
Build console output:
commit notification 108127644b30e28d326702752aa1150e05227156
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Injecting as environment variables the properties content
[EnvInject] - Variables injected successfully.
[EnvInject] - Injecting contributions.
Building on master in workspace /home/jenkins/workspace/TestNotification
> /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> /usr/local/bin/git config remote.origin.url ssh://g...@git.mydomain.com:7999/project/repo1.git # timeout=10
Fetching upstream changes from ssh://g...@git.mydomain.com:7999/project/repo1.git
> /usr/local/bin/git --version # timeout=10
> /usr/local/bin/git -c core.askpass=true fetch --tags --progress ssh://g...@git.mydomain.com:7999/project/repo1.git +refs/heads/*:refs/remotes/origin/*
> /usr/local/bin/git rev-parse 108127644b30e28d326702752aa1150e05227156^{commit} # timeout=10
FATAL: Command "/usr/local/bin/git rev-parse 108127644b30e28d326702752aa1150e05227156^{commit}" returned status code 128:
stdout: 108127644b30e28d326702752aa1150e05227156^{commit}
stderr: fatal: ambiguous argument '108127644b30e28d326702752aa1150e05227156^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
hudson.plugins.git.GitException: Command "/usr/local/bin/git rev-parse 108127644b30e28d326702752aa1150e05227156^{commit}" returned status code 128:
stdout: 108127644b30e28d326702752aa1150e05227156^{commit}
stderr: fatal: ambiguous argument '108127644b30e28d326702752aa1150e05227156^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1457)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1433)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1429)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1117)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1127)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:523)
at hudson.plugins.git.GitAPI.revParse(GitAPI.java:258)
at hudson.plugins.git.RevisionParameterAction.toRevision(RevisionParameterAction.java:85)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:872)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:985)
at hudson.scm.SCM.checkout(SCM.java:488)
at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:118)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1252)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:624)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:530)
at hudson.model.Run.execute(Run.java:1732)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:234)
Environment:
Jenkins 1.568
multiple-scms-plugin 0.4-beta-1
git-plugin 2.3.5-SNAPSHOT
[JIRA] [envinject-plugin] (JENKINS-26583) Env-inject plugin suppress variables contributed by extension points
Oliver Gondža commented on JENKINS-26583 Env-inject plugin suppress variables contributed by extension points https://github.com/jenkinsci/envinject-plugin/pull/37 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [test-results-analyzer-plugin] (JENKINS-26567) Tests result analyzer plugin not working
Rana Ranjit Singh commented on JENKINS-26567 Tests result analyzer plugin not working Just to be clear regarding the above comment, the plugin is still buggy with errors and not working. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-20499) unable to retry job execution for failed job in build-pipeline
Patrik Boström commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Created a PR with a proposed fix: https://github.com/jenkinsci/build-pipeline-plugin/pull/65 Please test it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-25234) Improve readability of the 'schedule build' tooltip
dogfood commented on JENKINS-25234 Improve readability of the 'schedule build' tooltip Integrated in jenkins_main_trunk #3948 [FIXED JENKINS-25234] Improve readability of the 'schedule build' tooltip (Revision 2533e0ed7adfac09841d9ff31902ee2b7100d14a) Result = SUCCESS pmarcoen : 2533e0ed7adfac09841d9ff31902ee2b7100d14a Files : core/src/main/resources/hudson/views/BuildButtonColumn/column.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-26417) Allow to customize refspec/tags of the clone/fetch commands
SCM/JIRA link daemon commented on JENKINS-26417 Allow to customize refspec/tags of the clone/fetch commands Code changed in jenkins User: Vincent LATOMBE Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/main/java/org/jenkinsci/plugins/gitclient/CloneCommand.java src/main/java/org/jenkinsci/plugins/gitclient/FetchCommand.java src/main/java/org/jenkinsci/plugins/gitclient/JGitAPIImpl.java src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java http://jenkins-ci.org/commit/git-client-plugin/1a5f40df2473cc3c05e4bb8fc177631a440e3b0f Log: JENKINS-26417 Allow customization of refspec/tags of the clone/fetch commands Add the option to omit tags to FetchCommand and CloneCommand Allow use of custom refspecs for CloneCommand This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-26417) Allow to customize refspec/tags of the clone/fetch commands
SCM/JIRA link daemon commented on JENKINS-26417 Allow to customize refspec/tags of the clone/fetch commands Code changed in jenkins User: Vincent LATOMBE Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java http://jenkins-ci.org/commit/git-client-plugin/ada4ade93e2f19ec9e788eb1fa862e1dd54820ee Log: JENKINS-26417 Add a unit test for clone with multiple refspecs Rolling back the change to #getBranches() This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-25234) Improve readability of the 'schedule build' tooltip
SCM/JIRA link daemon resolved JENKINS-25234 as Fixed Improve readability of the 'schedule build' tooltip Change By: SCM/JIRA link daemon (24/Jan/15 5:35 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-25234) Improve readability of the 'schedule build' tooltip
SCM/JIRA link daemon commented on JENKINS-25234 Improve readability of the 'schedule build' tooltip Code changed in jenkins User: Peter Marcoen Path: core/src/main/resources/hudson/views/BuildButtonColumn/column.jelly http://jenkins-ci.org/commit/jenkins/2533e0ed7adfac09841d9ff31902ee2b7100d14a Log: [FIXED JENKINS-25234] Improve readability of the 'schedule build' tooltip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-25234) Improve readability of the 'schedule build' tooltip
SCM/JIRA link daemon commented on JENKINS-25234 Improve readability of the 'schedule build' tooltip Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/views/BuildButtonColumn/column.jelly core/src/main/resources/hudson/views/BuildButtonColumn/column.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_ar.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_bg.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_ca.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_cs.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_da.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_de.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_el.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_eo.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_es.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_es_AR.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_et.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_eu.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_fi.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_fr.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_ga_IE.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_he.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_hi_IN.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_hu.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_id.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_is.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_it.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_ja.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_kn.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_ko.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_lt.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_lv.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_mk.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_mr.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_nb_NO.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_nl.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_pl.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_pt_BR.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_pt_PT.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_ro.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_ru.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_sk.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_sl.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_sr.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_sv_SE.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_te.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_tr.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_uk.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_zh_CN.properties core/src/main/resources/hudson/views/BuildButtonColumn/column_zh_TW.properties http://jenkins-ci.org/commit/jenkins/ac22cf9e24c67e43c562f6e6a1ba02abac97e33f Log: Merge pull request #1539 from petermarcoen/JENKINS-25234 [FIXED JENKINS-25234] Improve readability of the 'schedule build' tooltip Compare: https://github.com/jenkinsci/jenkins/compare/b37af2950492...ac22cf9e24c6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Gro
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
akshay_abd started work on JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted Change By: akshay_abd (24/Jan/15 3:09 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-26580) For JNLP slaves the master-slave communication should be encrypted
akshay_abd commented on JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted Added a pull request to the remoting project: https://github.com/jenkinsci/remoting/pull/28 This is a refactor-only pull request. It should make it easier for developers to add support for more protocols in the slave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-25683) EnvInjectException: hudson.remoting.ChannelClosedException: channel is already closed
Oliver Gondža resolved JENKINS-25683 as Won't Fix EnvInjectException: hudson.remoting.ChannelClosedException: channel is already closed There is nothing to do about it. Since JENKINS-26411 the message is more descriptive. Change By: Oliver Gondža (24/Jan/15 2:14 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-25683) EnvInjectException: hudson.remoting.ChannelClosedException: channel is already closed
Oliver Gondža updated JENKINS-25683 EnvInjectException: hudson.remoting.ChannelClosedException: channel is already closed Change By: Oliver Gondža (24/Jan/15 2:13 PM) Component/s: core Component/s: envinject-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [mashup-portlets-plugin] (JENKINS-26586) Allow to show alerts in Sonar Portlet
Georg Henzler resolved JENKINS-26586 as Fixed Allow to show alerts in Sonar Portlet Change By: Georg Henzler (24/Jan/15 1:48 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [mashup-portlets-plugin] (JENKINS-26556) Method ajaxViaJenkins() does not work in GenericJsPortlet without credentials anymore
Georg Henzler resolved JENKINS-26556 as Fixed Method ajaxViaJenkins() does not work in GenericJsPortlet without credentials anymore Change By: Georg Henzler (24/Jan/15 1:48 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [mashup-portlets-plugin] (JENKINS-26556) Method ajaxViaJenkins() does not work in GenericJsPortlet without credentials anymore
SCM/JIRA link daemon commented on JENKINS-26556 Method ajaxViaJenkins() does not work in GenericJsPortlet without credentials anymore Code changed in jenkins User: georg.henzler Path: src/main/java/javagh/jenkins/mashupportlets/GenericJsPortlet.java src/main/resources/javagh/jenkins/mashupportlets/GenericJsPortlet/genericjsportlet.jelly http://jenkins-ci.org/commit/mashup-portlets-plugin/160d3c7d9312e93890fc41e5e4493ed38a5de794 Log: JENKINS-26556 fixing by not trying to overload @_javascript_Method methods anymore This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [mashup-portlets-plugin] (JENKINS-26586) Allow to show alerts in Sonar Portlet
SCM/JIRA link daemon commented on JENKINS-26586 Allow to show alerts in Sonar Portlet Code changed in jenkins User: georg.henzler Path: src/main/java/javagh/jenkins/mashupportlets/SonarIssuesPortlet.java src/main/resources/javagh/jenkins/mashupportlets/SonarIssuesPortlet/config.jelly src/main/resources/javagh/jenkins/mashupportlets/SonarIssuesPortlet/config.properties src/main/resources/javagh/jenkins/mashupportlets/SonarIssuesPortlet/help-alwaysShowMetrics.html src/main/resources/javagh/jenkins/mashupportlets/SonarIssuesPortlet/help-metricsCheckedForAlerts.html src/main/resources/javagh/jenkins/mashupportlets/SonarIssuesPortlet/help-showAlerts.html src/main/resources/javagh/jenkins/mashupportlets/SonarIssuesPortlet/sonarissuesportlet.jelly http://jenkins-ci.org/commit/mashup-portlets-plugin/7bc6f8ab0c359bbc6f9b4df98baafdaf12b1e74d Log: JENKINS-26586 Allow to show alerts within the sonar issues portlet This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [mashup-portlets-plugin] (JENKINS-26586) Allow to show alerts in Sonar Portlet
Georg Henzler created JENKINS-26586 Allow to show alerts in Sonar Portlet Issue Type: New Feature Assignee: Georg Henzler Components: mashup-portlets-plugin Created: 24/Jan/15 1:32 PM Description: It would be nice to be able to see alerts for a project/metric in the jenkins portlet. Project: Jenkins Priority: Minor Reporter: Georg Henzler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-25889) InputStepExecution.node is null after restart
Jesse Glick commented on JENKINS-25889 InputStepExecution.node is null after restart Observed in WorkflowPluginTest.linearFlow, for example. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [sonargraph-plugin] (JENKINS-26584) Sonargraph: NPE after updating to 1.6.2
SCM/JIRA link daemon commented on JENKINS-26584 Sonargraph: NPE after updating to 1.6.2 Code changed in jenkins User: Ingmar Kellner Path: Sonargraph-Jenkins-Project.sonargraph src/main/java/com/hello2morrow/sonargraph/jenkinsplugin/controller/AbstractSonargraphRecorder.java src/main/java/com/hello2morrow/sonargraph/jenkinsplugin/controller/SonargraphReportAnalyzer.java src/main/java/com/hello2morrow/sonargraph/jenkinsplugin/controller/SonargraphReportBuilder.java http://jenkins-ci.org/commit/sonargraph-plugin/8a1025f6a9b20f25f2d03bfa2166addf1363 Log: JENKINS-26584: Sonargraph: NPE after updating to 1.6.2. After plugin update and without saving the configuration, the additionalMetrics member variable might be null. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [embeddable-build-status-plugin] (JENKINS-26585) Exclude view name from links and/or add fields for links with without view name
Christian Galsterer created JENKINS-26585 Exclude view name from links and/or add fields for links with without view name Issue Type: New Feature Assignee: Christian Galsterer Components: embeddable-build-status-plugin Created: 24/Jan/15 12:20 PM Description: Currently links contain always the full path for the selected job, i.e. when a job is listed as part of view the link contains the view name. Nonetheless there are use cases where the view name is changed (i.e reorganization of view) but the job name stays. In order to not have broken links in your Wikis, etc. it would be good to have the URL pointing always to the job name without the view name in the path even if the job is currently listed in a view. Two options I see: Change the URL of the current implementation so that URL is always using only the job name (without the view name). This is changing the current behaviour. Add additional fields in the badge containing the direct URL without the view name. Any preferences? Project: Jenkins Priority: Major Reporter: Christian Galsterer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [sonargraph-plugin] (JENKINS-26584) Sonargraph: NPE after updating to 1.6.2
Ingmar Kellner created JENKINS-26584 Sonargraph: NPE after updating to 1.6.2 Issue Type: Bug Assignee: Ingmar Kellner Components: sonargraph-plugin Created: 24/Jan/15 11:40 AM Description: [INFO] Sonargraph Jenkins Plugin, Version '1.6.2', post-build step 'com.hello2morrow.sonargraph.jenkinsplugin.controller.SonargraphReportAnalyzer' Start structural analysis on project 'SGNG-CI-Feature', build number '99' ERROR: Publisher com.hello2morrow.sonargraph.jenkinsplugin.controller.SonargraphReportAnalyzer aborted due to exception java.lang.NullPointerException at com.hello2morrow.sonargraph.jenkinsplugin.controller.AbstractSonargraphRecorder.processMetricsForCharts(AbstractSonargraphRecorder.java:189) at com.hello2morrow.sonargraph.jenkinsplugin.controller.SonargraphReportAnalyzer.perform(SonargraphReportAnalyzer.java:49) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Project: Jenkins Priority: Critical Reporter: Ingmar Kellner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [sonargraph-plugin] (JENKINS-26584) Sonargraph: NPE after updating to 1.6.2
Ingmar Kellner started work on JENKINS-26584 Sonargraph: NPE after updating to 1.6.2 Change By: Ingmar Kellner (24/Jan/15 11:40 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [chromedriver-plugin] (JENKINS-26524) Null Pointer Exception on github payload push AND polling to/from Jenkins
Mark Waite updated JENKINS-26524 Null Pointer Exception on github payload push AND polling to/from Jenkins The stack trace seems to point to a null pointer exception in org.jenkisnci.plugins.chromedriver, not in either the git plugin or the github plugin. Yes, the null pointer exception is happening because Run.getEnvironment() is being called, but the bug seems to be inside chromedriver. Change By: Mark Waite (24/Jan/15 11:38 AM) Component/s: chromedriver-plugin Component/s: git-plugin Component/s: github-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [sonargraph-plugin] (JENKINS-26566) Sonargraph: No graphs displayed due to wrong default setting after updating
Ingmar Kellner closed JENKINS-26566 as Fixed Sonargraph: No graphs displayed due to wrong default setting after updating Change By: Ingmar Kellner (24/Jan/15 11:39 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [sonargraph-plugin] (JENKINS-26566) Sonargraph: No graphs displayed due to wrong default setting after updating
Ingmar Kellner resolved JENKINS-26566 as Fixed Sonargraph: No graphs displayed due to wrong default setting after updating Change By: Ingmar Kellner (24/Jan/15 11:39 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-26583) Env-inject plugin suppress variables contributed by extension points
Oliver Gondža created JENKINS-26583 Env-inject plugin suppress variables contributed by extension points Issue Type: Bug Assignee: Oliver Gondža Components: envinject-plugin Created: 24/Jan/15 11:17 AM Description: Whenever envvar is available on slave (either inherited from system or configured on slave), its value can not be overridden during build by envvar contributing extension points: EnvironmentContributor BuildWrapper possibly others This works correctly when envinject is not installed. The culprit seems to be that EnvInjectPluginAction retains all envvars (not only those envinject contributed) early in the build and put this values back as it implements EnvironmentContributingAction. Any value that was overridden by a plugin is then reset to its original value. Project: Jenkins Priority: Major Reporter: Oliver Gondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-12092) Allow a job to completely block a category
Seán Dunne commented on JENKINS-12092 Allow a job to completely block a category Hi Christian, I don't believe the UI that's presented in the jobs configuration is there for this purpose. As far as I can see, if you select Throttle this project as part of one or more categories the 2 Maximum Concurrent Builds textboxes are ignored. Those textboxes are only used when the Throttle this project alone radio is selected. At least, from my limited understanding of the plugin that's how it works. I've been spending a bit of time on this issue. The solution I have implemented so far is, I added a new checkbox that belongs to the Throttle this project as part of one or more categories radio The new checkbox Let this Job be blocked by selected Categories (it's a working title) will block a job if any builds from any of the selected categories are queued or executing This in effect lets you select 1 or more jobs that will not execute while jobs from it's categories are executing. What do you think of this solution? I'd like to get some community feedback before I make a pull request. Thanks! P.S: I was also considering fixing the UI so the "child" options only show up when you select it's parent radio button. But that's part of a different issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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.
