[JIRA] [core] (JENKINS-24550) When I update my Jenkins from 1.563 to 1.566 or later，my Internet Explorer gets warning：Your Internet Explorer appears to be set to a non-defalut 'Document Mode'
Jean Detoeuf commented on JENKINS-24550 When I update my Jenkins from 1.563 to 1.566 or later，my Internet Explorer gets warning：Your Internet Explorer appears to be set to a non-defalut 'Document Mode' One quick workaround is to use IP address instead of DNS name. In my case, DNS name is marked as intranet site and intranet site are required to show in compatibility modes as a group policy. Refering to IP address instead of DNS name solved the issue, although there could be a better way. Searched a bit on the subject. File layout.jelly contains which should override compatibility mode in some cases. I also tried adding the following before tag as Microsoft recommended adding a header with the same values to enforce view policy before page rendering (cf http://msdn.microsoft.com/en-us/library/ff955275%28v=vs.85%29.aspx) Hope this helps 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] [monitoring] (JENKINS-24838) Monitoring Plugin links from slaves are incorrect when Jenkins deployed with a context
Yves Martin updated JENKINS-24838 Monitoring Plugin links from slaves are incorrect when Jenkins deployed with a context Change By: Yves Martin (24/Sep/14 6:37 AM) Summary: Monitoring Plugin links from slaves are incorrect when Jenkins deployed with a context Description: The When browsing " Monitoring Plugin expects Jenkins to be deployed as " ROOT" webapp without any context. section If Jenkins is deployed with for a context, like specific slave http://myhost/jenkins/ ,the computer/SLAVE/ monitoring plugin is unusable as /, links all do not take care of the Jenkins context and point to "http://myhost/monitoring/" Please use relative links even when possible Jenkins is deployed with a context , or like http://myhost/jenkins/Please prepend the Jenkins webapp context when generating links 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] (JENKINS-24454) Windows GIT SCM Polling hung
sharon xia commented on JENKINS-24454 Windows GIT SCM Polling hung Any possibility there is issue with jenkins slave process clean up? 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] (JENKINS-24454) Windows GIT SCM Polling hung
sharon xia commented on JENKINS-24454 Windows GIT SCM Polling hung Hi, We meet this issue again on another slave node: We are seeing a number of git processes on the slave node when this issue happen. It often happens when user cancelled task during git fetch code step. The git process is not killed properly. And for a while, there are a bunch of git process not killed on the slave. Here is the output, we have to restart jenkins service on slave node to let it work: Started by user XXX [EnvInject] - Loading node environment variables. Building remotely on GPS-NODE (x86-windows-6.1 6.1 x86-windows windows-6.1 windows x86) in workspace d:\hudson-slave\workspace\Andy_Dev_Branch > git rev-parse --is-inside-work-tree Fetching changes from the remote Git repository > git config remote.origin.url ssh://g...@hardware.corp.emc.com:7999/bf/uefi_bios_moons.git Cleaning workspace > git rev-parse --verify HEAD Resetting working tree > git reset --hard > git clean -fdx Fetching upstream changes from ssh://git@:7999/bf/uefi_bios_moons.git > git --version > git fetch --tags --progress ssh://git@***:7999/bf/uefi_bios_moons.git +refs/heads/:refs/remotes/origin/* FATAL: Failed to fetch from ssh://git@:7999/bf/uefi_bios_moons.git hudson.plugins.git.GitException: Failed to fetch from ssh://git@:7999/bf/uefi_bios_moons.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:623) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:855) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:880) at hudson.model.AbstractProject.checkout(AbstractProject.java:1252) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:615) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524) at hudson.model.Run.execute(Run.java:1706) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://git@***:7999/bf/uefi_bios_moons.git +refs/heads/:refs/remotes/origin/*" returned status code 128: stdout: stderr: Could not create directory 'c/Users/buildfarmadmin/.ssh'. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1325) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1186) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:87) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:257) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) 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] [jenkins-reviewbot] (JENKINS-24305) ReviewBot can't apply the diff and failed to patch file
Alex Kor edited a comment on JENKINS-24305 ReviewBot can't apply the diff and failed to patch file Yardena, Thanks for information and sorry for creating several same issues in different places. My comments can be found here: https://github.com/vmware/jenkins-reviewbot/issues/11 Thanks. 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] [monitoring] (JENKINS-24838) Monitoring Plugin links are incorrect when Jenkins deployed with a context
Yves Martin created JENKINS-24838 Monitoring Plugin links are incorrect when Jenkins deployed with a context Issue Type: Bug Assignee: Unassigned Components: monitoring Created: 24/Sep/14 5:52 AM Description: The Monitoring Plugin expects Jenkins to be deployed as "ROOT" webapp without any context. If Jenkins is deployed with a context, like http://myhost/jenkins/, the monitoring plugin is unusable as links all point to "http://myhost/monitoring/" Please use relative links when possible, or prepend the Jenkins webapp context when generating links Project: Jenkins Priority: Blocker Reporter: Yves Martin 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] [jenkins-reviewbot] (JENKINS-24305) ReviewBot can't apply the diff and failed to patch file
Alex Kor commented on JENKINS-24305 ReviewBot can't apply the diff and failed to patch file Yardena, Thanks for information and sorry for creating several issues in different places. My comments can be found here: https://github.com/vmware/jenkins-reviewbot/issues/11 Thanks. 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-24821) Jenkins missing build size in Build History Trend
Kent Granström commented on JENKINS-24821 Jenkins missing build size in Build History Trend No. They don't come back with a restart of the browser 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-24821) Jenkins missing build size in Build History Trend
Kent Granström updated JENKINS-24821 Jenkins missing build size in Build History Trend Older builds that disappear when I look into the build Change By: Kent Granström (24/Sep/14 5:22 AM) Attachment: Missing_size_2.png 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-24821) Jenkins missing build size in Build History Trend
Kent Granström commented on JENKINS-24821 Jenkins missing build size in Build History Trend Ver: 0.24 of the disk usage plugin No. Reloading the page doesn't change the outcome No. They are older. Added another pic to demonstrate this If I restart the computer, then I get them back. They will probably be visible if I restart the whole browser (Chrome). I'll test that in a minute 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] [external-monitor-job] (JENKINS-24837) Viewing In Progress Status for "external-monitor-job"
Anand Juli created JENKINS-24837 Viewing In Progress Status for "external-monitor-job" Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: external-monitor-job Created: 24/Sep/14 5:21 AM Description: Not sure if this is a bug but what I was looking for is to be able to know from Jenkins Dashboard that a job I am monitoring has 'started'. In other, I want to know that the job is 'In Progress'. On Jenkins dashboard, I can see that a new build gets registered straight away after the external job completes but there was no indication that the job was 'running'. I am using Jenkins 1.581 (localhost) in a MAC and the process being monitored in a java process running locally as well. Project: Jenkins Priority: Minor Reporter: Anand Juli 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] [fitnesse] (JENKINS-13696) Fitnesse should run on the slave of the build, not on the head node
David T commented on JENKINS-13696 Fitnesse should run on the slave of the build, not on the head node If I understand this issue correctly, I am having the same problem. It appears that the plugin is trying to connect to FitNesse on the master (the FitNesse server is started correctly on the slave). As a work around, I need to start the FitNesse server manually on the slave machine, and specify the option "Fitnesse instance is already running" My error is Connnecting to http://localhost:8085/RiskManagement.SomeSuitePage.AnotherSuitePage?suite&format=xml&includehtml java.net.ConnectException: Connection refused: connect My versions are Jenkins: 1.578 Hudson Fitnesse plugin: 1.9 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-24836) Ability to fail a build when no executors are available
Ilya Ivanov created JENKINS-24836 Ability to fail a build when no executors are available Issue Type: New Feature Assignee: Unassigned Components: core Created: 24/Sep/14 3:05 AM Description: When using Jenkins to run automatic tasks, it's almost foolproof. Unfotunately, there's a loophole: if a slave goes offline, the job will just stay in waiting state. It's not acceptable for critical tasks (backups, etc). They should either run in time or fail. Thus, this feature request. Please add an option to fail a build when it cannot run. Project: Jenkins Priority: Major Reporter: Ilya Ivanov 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-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported We cannot reproduce this issue on 1.532.3, but we can reproduce it on 1.565.2. Is there any related change during these two version? We are stuck at this issue now. 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-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia edited a comment on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported I did another experiments for 1.565.2, and saw 3 failed requests out of 300. Concurrency Level: 2 Time taken for tests: 10396.019 seconds Complete requests: 300 Failed requests:3 Here is the log (Just keep a small part as I checked the other pasts are just the same. ). Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 9:33:09 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 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-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported Any progress on this 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.
[JIRA] [jenkins-multijob-plugin] (JENKINS-23161) Aborted or failed job in a phase does not immediately cause the multi-job to fail
James Levinson commented on JENKINS-23161 Aborted or failed job in a phase does not immediately cause the multi-job to fail The killPhaseOn, introduced in 1.11, defaults to Failure, as indicated in your screenshot, so this should fail the phase after any job failure and abort the other running jobs. On my systems, I have observed this does in fact work. I am now on plugin version 1.13. I would also argue that the developers changed the behavior of the plugin when they selected Failure as a default and it should have been set to Never. 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] [hp-application-automation-tools-plugin] (JENKINS-24835) Question on supported versions
Donald Morton created JENKINS-24835 Question on supported versions Issue Type: Task Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 24/Sep/14 12:47 AM Description: I am running HP ALM 12.01 and UFT 12.01. Looking at the supported versions of the various components, it is not clear to me what functionality will and won't work. Does this plugin support running functional and performance tests from Jenkins in v12.01? It says PC 12.00 is supported, but it also says QTP only supports 11.00. And then, ALM is listed at version 11.52. If the answer is that it won't work, then when will the plugin be updated to work with the latest versions? Please forgive my ignorance of the various components. I tried to open a ticket with HP, but they told me they don't support the plugin and told me to come here. Environment: HP ALM 12.01 HP UFT 12.01 Project: Jenkins Priority: Minor Reporter: Donald Morton 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] (JENKINS-24809) Github-Jenkins Trigger issue with slave
Mark Waite commented on JENKINS-24809 Github-Jenkins Trigger issue with slave There are certainly many installations worldwide which use a wide mix of Windows and Linux computers, and which successfully poll whether or not "Force polling workspace" is set. You may have a configuration error in your Jenkins setup. Some things you might try as a way to test that theory: Configure a freestyle job with Git as scm from a repository accessible from all your machines (maybe https://github.com/jenkinsci/git-client-plugin.git) Configure that job to "Force polling using workspace" and configure it to poll once a minute Configure the job to limit which node can run the job, limit it to the master node Read the polling log to confirm it was successful Configure the job to limit which node can run the job, limit it to another node Wait for it to poll from that node Read the polling log to see if the polling commands are successful from that node Iterate through each of your nodes, confirming that each is able to poll with git If one of the nodes is discovered that it cannot poll with git, then you can review the configuration of that node, looking to see if it has incorrectly declared the location of the git program, or if it is incorrectly using the git location of the master node. 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] [groovy-postbuild] (JENKINS-13024) Error in log indicating a missing descriptor
ikedam resolved JENKINS-13024 as Fixed Error in log indicating a missing descriptor @brian3791 It sounds a problem completely different from the one originally reported in this issue. Create a new issue if you still have that problem. Change By: ikedam (23/Sep/14 11:43 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] [groovy-postbuild] (JENKINS-9992) Execute Groovy script after the launch of the downstream jobs
ikedam commented on JENKINS-9992 Execute Groovy script after the launch of the downstream jobs Promoted Builds plugin helps you. 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] [parameterized-trigger] (JENKINS-24810) The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop
ikedam commented on JENKINS-24810 The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop It sounds the correct behavior of nodelabelparameter plugin. You should uncheck "Run on all nodes matching the label" of NODE_LABEL. 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-24831) Executor gets assigned multiple times
Octavian Ciuhandu commented on JENKINS-24831 Executor gets assigned multiple times As a note, it's something that happens only occasionally, we have seen this happening about around 5 times in the last week or so, and we have not been able to identify any possible reason for this. 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] [parameterized-trigger] (JENKINS-24810) The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop
Clinton Barr commented on JENKINS-24810 The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop I just ran the setup again with only one properties file and it built two child project jobs. As for your second question, yes - I can't believe I didn't mention this before. The child project accepts a node label-type parameter. Just now, I found that without the node label parameter, this bug does not show up. If I remove the node label parameter from the child (but still pass it in the .properties file), no build duplication occurs. If I restore the node label parameter and manually build the child project, entering an existing node, no build duplication occurs. If the parent project triggers a child project build using a .properties file (that contains an existing node label), build duplication DOES occur. By the way, thank you both for paying attention to this 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.
[JIRA] [core] (JENKINS-24831) Executor gets assigned multiple times
Octavian Ciuhandu commented on JENKINS-24831 Executor gets assigned multiple times Job 2 calls another job (Job 3) that actually uses both parameters. Job 1 config.xml: http://paste.openstack.org/show/114710/ Job 2 config.xml: http://paste.openstack.org/show/114711/ By "gets assigned 2 times" I mean that when I check the 2 parameters (that are set in Job 1 and Job 2) they have the same value, e.g.: hyperv01: node1.domain.tld hyperv02: node1.domain.tld Since each job states that the parameter hyperv01/hyperv02 takes value $NODE_NAME and there's only one executor per slave node, this should be impossible. 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-24831) Executor gets assigned multiple times
Daniel Beck commented on JENKINS-24831 Executor gets assigned multiple times Please explain what you mean here: gets assigned 2 times (we always assign 2 executors to a run). The jobs' config.xml would also be helpful. Why are you passing in a parameter to 02 if it doesn't take parameters? 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] [jenkins-reviewbot] (JENKINS-24305) ReviewBot can't apply the diff and failed to patch file
Yardena Meymann commented on JENKINS-24305 ReviewBot can't apply the diff and failed to patch file Not sure what is wrong, but couple things to try: a) Make sure you are using "wipe out the repository and force clone" in git options of the Jenkins job b) Try your diff with Patch Parameter plugin. If it fails there too - the issue is probably with cloudbees diff4j. HTH 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-24831) Executor gets assigned multiple times
Octavian Ciuhandu commented on JENKINS-24831 Executor gets assigned multiple times I'm attaching 2 screenshots with the definitions of Job 1 and Job 2. As for plugins, we use: Gearman 0.0.7, Build timeout 1.14, Event Publisher 0.0.3, Node and Label parameter 1.5.1, Parameterized Trigger 2.25, Throttle Concurrent Builds 1.8.3 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-24831) Executor gets assigned multiple times
Octavian Ciuhandu updated JENKINS-24831 Executor gets assigned multiple times Job 01 Change By: Octavian Ciuhandu (23/Sep/14 9:51 PM) Attachment: Screen Shot 2014-09-23 at 22.53.09.png 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-24831) Executor gets assigned multiple times
Octavian Ciuhandu updated JENKINS-24831 Executor gets assigned multiple times Job 02 Change By: Octavian Ciuhandu (23/Sep/14 9:52 PM) Attachment: Screen Shot 2014-09-23 at 22.54.26.png 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] [parameterized-trigger] (JENKINS-24810) The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop
Daniel Beck commented on JENKINS-24810 The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop I assume for the condition to occur you need more than one properties file, so there can actually be queued builds? Does child need the node parameter? 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] (JENKINS-13086) Clone to directory named for repository
Marc Breslow commented on JENKINS-13086 Clone to directory named for repository With Multiple-SCM plugin you also don't get the GIT_URL and GIT_SHA for all the repos. 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] [parameterized-trigger] (JENKINS-24810) The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop
Clinton Barr edited a comment on JENKINS-24810 The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop New information: Ignore everything before this. Environment: 1. Parent project runs on master, child project runs on slave (allocated by node label) 2. Windows 2012 Server master, Windows 2008 R2 slave 3. Jenkins v1.581, Parameterized Trigger Plugin v2.25 4. Parent project copies one .properties file into workspace, triggers child project from it using ParameterFactory, finishes 5. See attachments for configs and properties file used to trigger child project I can condense the behavior of this issue down to the following: Each child build triggered by the parent has a chance to be built twice. The duplicate chance occurs each time a child build finishes and the executor of the slave that just built it is freed (to consume a queued child build). The parent project does not need to be running for duplicate child builds to be created. Jenkins Master reboots have no effect (we reboot our master each day) EDIT: Couldn't remove obsolete attachments. #5 above is referring to ParentProject_config.xml, ChildProject_config.xml and 0.properties. 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] [parameterized-trigger] (JENKINS-24810) The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop
Clinton Barr updated JENKINS-24810 The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop New information: Ignore everything before this. Environment: 1. Parent project runs on master, child project runs on slave (allocated by node label) 2. Windows 2012 Server master, Windows 2008 R2 slave 3. Jenkins v1.581, Parameterized Trigger Plugin v2.25 4. Parent project copies one .properties file into workspace, triggers child project from it using ParameterFactory, finishes 5. See attachments for configs and properties file used to trigger child project I can condense the behavior of this issue down to the following: Each child build triggered by the parent has a chance to be built twice. The duplicate chance occurs each time a child build finishes and the executor of the slave that just built it is freed (to consume a queued child build). The parent project does not need to be running for duplicate child builds to be created. Jenkins Master reboots have no effect (we reboot our master each day) Change By: Clinton Barr (23/Sep/14 9:23 PM) Attachment: 0.properties Attachment: ChildProject_config.xml Attachment: ParentProject_config.xml 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] [cppcheck] (JENKINS-24834) CPP check report background colours not displaying for new or resolved issues since upgrade
Craig Phillips created JENKINS-24834 CPP check report background colours not displaying for new or resolved issues since upgrade Issue Type: Bug Assignee: Gregory Boissinot Components: cppcheck Created: 23/Sep/14 9:18 PM Description: Since upgrading to 1.581, the background colours on the CPP check page are not showing (red for new, green for resolved). I wonder if it's down to this change in the changelog "Explicitly set background color of various UI elements to white. (issue 24625)" Project: Jenkins Priority: Minor Reporter: Craig Phillips 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-24453) Jenkins server got blue screen to death
dogfood commented on JENKINS-24453 Jenkins server got blue screen to death Integrated in jenkins_main_trunk #3700 [FIXED JENKINS-24453] (Revision d000cd65a7b0152334532bc7abd148095d5cee09) Result = SUCCESS kohsuke : d000cd65a7b0152334532bc7abd148095d5cee09 Files : changelog.html 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] [deploy] (JENKINS-5790) Parameterize Tomcat Context Path and URL Fields
Ranjit Vadakkan
edited a comment on JENKINS-5790
Parameterize Tomcat Context Path and URL Fields
Note that using URL parameters like so -
http://${DEPLOY_SERVER}:${DEPLOY_PORT}
does not work. It complains about ${DEPLOY_PORT}.
FATAL: java.net.MalformedURLException: For input string: "${DEPLOY_PORT}"
java.lang.AssertionError: java.net.MalformedURLException: For input string: "${DEPLOY_PORT}"
at hudson.plugins.deploy.tomcat.TomcatAdapter.configure(TomcatAdapter.java:35)
at hudson.plugins.deploy.CargoContainerAdapter.getContainer(CargoContainerAdapter.java:56)
at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:114)
at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:103)
at hudson.FilePath.act(FilePath.java:912)
at hudson.FilePath.act(FilePath.java:885)
at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:103)
at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:61)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:781)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:753)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706)
at hudson.model.Run.execute(Run.java:1690)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:230)
Caused by: java.net.MalformedURLException: For input string: "${DEPLOY_PORT}"
at java.net.URL.(URL.java:601)
at java.net.URL.(URL.java:464)
at java.net.URL.(URL.java:413)
at hudson.plugins.deploy.tomcat.TomcatAdapter.configure(TomcatAdapter.java:32)
... 16 more
So I assumed it didn't like 2 parameters separated by the ':' and so I tried http://${DEPLOY_SERVER}, but no luck with that either -
ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to exception
org.codehaus.cargo.container.ContainerException: Failed to redeploy [C:\Program Files (x86)\Jenkins\jobs\EPC DEV Emma\workspace\build\artifacts\wars\ecosys-instr.war]
at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:193)
at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:73)
at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:116)
at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:103)
at hudson.FilePath.act(FilePath.java:912)
at hudson.FilePath.act(FilePath.java:885)
at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:103)
at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:61)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:781)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:753)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706)
at hudson.model.Run.execute(Run.java:1690)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:230)
Caused by: java.net.UnknownHostException: ${DEPLOY_SERVER}
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at java.net.Socket.connect(Socket.java:478)
at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
at sun.net.www.http.HttpClient.(HttpClient.java:233)
at sun.net.www.http.HttpClient.New(HttpClient.java:306)
at sun.net.www.http.HttpClient.New(HttpClient.java:323)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:975)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:916)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:841)
at org.codehaus.cargo.container.tomcat.internal.TomcatManag
[JIRA] [deploy] (JENKINS-5790) Parameterize Tomcat Context Path and URL Fields
Ranjit Vadakkan
updated JENKINS-5790
Parameterize Tomcat Context Path and URL Fields
Note that using 2 parameters like so -
http://${DEPLOY_SERVER}:${DEPLOY_PORT}
does not work. It complains about ${DEPLOY_PORT}.
FATAL: java.net.MalformedURLException: For input string: "${DEPLOY_PORT}"
java.lang.AssertionError: java.net.MalformedURLException: For input string: "${DEPLOY_PORT}"
at hudson.plugins.deploy.tomcat.TomcatAdapter.configure(TomcatAdapter.java:35)
at hudson.plugins.deploy.CargoContainerAdapter.getContainer(CargoContainerAdapter.java:56)
at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:114)
at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:103)
at hudson.FilePath.act(FilePath.java:912)
at hudson.FilePath.act(FilePath.java:885)
at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:103)
at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:61)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:781)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:753)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706)
at hudson.model.Run.execute(Run.java:1690)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:230)
Caused by: java.net.MalformedURLException: For input string: "${DEPLOY_PORT}"
at java.net.URL.(URL.java:601)
at java.net.URL.(URL.java:464)
at java.net.URL.(URL.java:413)
at hudson.plugins.deploy.tomcat.TomcatAdapter.configure(TomcatAdapter.java:32)
... 16 more
So I assumed it didn't like 2 parameters separated by the ':' and so I tried http://${DEPLOY_SERVER}, but no luck with that either -
ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to exception
org.codehaus.cargo.container.ContainerException: Failed to redeploy [C:\Program Files (x86)\Jenkins\jobs\EPC DEV Emma\workspace\build\artifacts\wars\ecosys-instr.war]
at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:193)
at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:73)
at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:116)
at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:103)
at hudson.FilePath.act(FilePath.java:912)
at hudson.FilePath.act(FilePath.java:885)
at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:103)
at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:61)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:781)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:753)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706)
at hudson.model.Run.execute(Run.java:1690)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:230)
Caused by: java.net.UnknownHostException: ${DEPLOY_SERVER}
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at java.net.Socket.connect(Socket.java:478)
at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
at sun.net.www.http.HttpClient.(HttpClient.java:233)
at sun.net.www.http.HttpClient.New(HttpClient.java:306)
at sun.net.www.http.HttpClient.New(HttpClient.java:323)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:975)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:916)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:841)
at org.codehaus.cargo.container.tomcat.internal.TomcatManager.
[JIRA] [maven] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Eugen Paraschiv commented on JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap Any news on getting the version fixed officially so that these kinds of workarounds are necessary? Cheers, Eugen. 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] (JENKINS-24833) Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Loren Klingman created JENKINS-24833 Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds Issue Type: Bug Assignee: Nicolas De Loof Attachments: Screen Shot 2014-09-23 at 4.34.48 PM.png Components: git Created: 23/Sep/14 8:42 PM Description: Git Publisher, but the task is getting run even though a part failed. (As a note, a Post build task runs as well so I'm thinking some variable use must have changed over time.) Here is the output: CRAP4J fails as you can see, but push runs. Then, at the end the build is labeled a failure. I'm attaching a screenshot of the configuration. build: BUILD SUCCESSFUL Total time: 1 minute 23 seconds [CHECKSTYLE] Collecting checkstyle analysis files... [CHECKSTYLE] Finding all files that match the pattern build/logs/checkstyle.xml [CHECKSTYLE] Parsing 1 files in /var/lib/jenkins/workspace/SBTS Portal [CHECKSTYLE] Successfully parsed file /var/lib/jenkins/workspace/SBTS Portal/build/logs/checkstyle.xml of module with 253 warnings. [CHECKSTYLE] Computing warning deltas based on reference build #108 [PMD] Collecting PMD analysis files... [PMD] Finding all files that match the pattern build/logs/pmd.xml [PMD] Parsing 1 files in /var/lib/jenkins/workspace/SBTS Portal [PMD] Successfully parsed file /var/lib/jenkins/workspace/SBTS Portal/build/logs/pmd.xml of module with 8 warnings. [PMD] Computing warning deltas based on reference build #108 [DRY] Collecting duplicate code analysis files... [DRY] Finding all files that match the pattern build/logs/pmd-cpd.xml [DRY] Parsing 1 files in /var/lib/jenkins/workspace/SBTS Portal [DRY] Successfully parsed file /var/lib/jenkins/workspace/SBTS Portal/build/logs/pmd-cpd.xml of module with 36 warnings. [DRY] Computing warning deltas based on reference build #108 Recording plot data Publishing Clover coverage report... Clover xml file does not exist in: /var/lib/jenkins/workspace/SBTS Portal called: build/logs/clover.xml and will not be copied to: /var/lib/jenkins/jobs/SBTS Portal/builds/2014-09-23_15-43-35/cloverphp/clover.xml Could not find 'build/coverage/build/logs/clover.xml'. Did you generate the XML report for Clover? [CRAP4J] Collecting Crap4J analysis files... [CRAP4J] Searching for report files within build/logs/crap4j.xml [CRAP4J] Using the new FileSetBuilder [CRAP4J] No crap4j report files were found. Configuration error? Build step 'Report Crap' marked build as failure [htmlpublisher] Archiving HTML reports... [htmlpublisher] Archiving at BUILD level /var/lib/jenkins/workspace/SBTS Portal/build/api to /var/lib/jenkins/jobs/SBTS Portal/builds/2014-09-23_15-43-35/htmlreports/API_Documentation [htmlpublisher] Archiving at BUILD level /var/lib/jenkins/workspace/SBTS Portal/build/phpdoc to /var/lib/jenkins/jobs/SBTS Portal/builds/2014-09-23_15-43-35/htmlreports/PHPDoc_Documentation [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing PHPUnit-3.x (default) [xUnit] [INFO] - [PHPUnit-3.x (default)] - 1 test report file(s) were found with the pattern 'build/logs/junit.xml' relative to '/var/lib/jenkins/workspace/SBTS Portal' for the testing framework 'PHPUnit-3.x (default)'. [xUnit] [INFO] - Converting '/var/lib/jenkins/workspace/SBTS Portal/build/logs/junit.xml' . [xUnit] [INFO] - Check 'Failed Tests' threshold. [xUnit] [INFO] - Check 'Skipped Tests' threshold. [xUnit] [INFO] - Setting the build status to SUCCESS [xUnit] [INFO] - Stopping recording. [JDepend] JDepend plugin is ready [JDepend] Found 273 classes in 21 packages Performing Post build task... Match found for : : True Logical operation result is TRUE Running script : git add --all ./build/api git commit -m "Jenkins Updating Doc Files" [SBTS Portal] $ /bin/sh -xe /tmp/hudson3629220943294003302.sh + git add --all ./build/api + git commit -m Jenkins Updating Doc Files [detached HEAD 42c8f11] Jenkins Updating Doc Files 1 file changed, 1 insertion, 1 deletion POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 > git tag -l jenkins-SBTS_Portal-111 # timeout=10 > git tag -a
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
Kohsuke Kawaguchi commented on JENKINS-24453 Jenkins server got blue screen to death csrss.exe wouldn't have the right environment variables, so it should never match the killing criteria. In 1.583 we made a change to winp so that at least it won't terminate a critical process, but we'll likely still have to figure out why that process was selected as a target of killing. 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-24453) Jenkins server got blue screen to death
SCM/JIRA link daemon resolved JENKINS-24453 as Fixed Jenkins server got blue screen to death Change By: SCM/JIRA link daemon (23/Sep/14 8:15 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] [core] (JENKINS-24453) Jenkins server got blue screen to death
SCM/JIRA link daemon commented on JENKINS-24453 Jenkins server got blue screen to death Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html http://jenkins-ci.org/commit/jenkins/d000cd65a7b0152334532bc7abd148095d5cee09 Log: [FIXED JENKINS-24453] The actual fix is made in 040b7d4047b324f17c0971f2511f954eb173fa23 through winp. 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-24832) Failed builds are showing up as Aborted
swolk commented on JENKINS-24832 Failed builds are showing up as Aborted I can try if you can point me at a maven multi-module project 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-15819) The name of the archived directory/file is garbled.(保存された成果物のディレクトリ/ファイル名が文字化けする)
Daniel Beck commented on JENKINS-15819 The name of the archived directory/file is garbled.(保存された成果物のディレクトリ/ファイル名が文字化けする) Lars: Please file a new issue against the 'core' component. Include all of the information you mentioned here. 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-15819) The name of the archived directory/file is garbled.(保存された成果物のディレクトリ/ファイル名が文字化けする)
Lars Lykke edited a comment on JENKINS-15819 The name of the archived directory/file is garbled.(保存された成果物のディレクトリ/ファイル名が文字化けする) I'm able to reproduce this issue (or something apparently similar) on Jenkins v. 1.581. My steps to reproduce is to 1) Check out files from our SCM (StarTeam plugin) 2) Verify files containing special characters are correct in the workspace (which they are) 3) After the files have been archived using the standard Archive Artifacts Post build step, the filenames containing special chars have been garbled. So files are retrieved correctly from SCM but get their filename garbled upon archiving. In my particular case the filenames contain the characters 'æ', 'ø' and 'å'. These are the chars being garbled by the archiving step. I've been searching for a way of testing whether or not I could influence the setting via some sort of startup parameter to Jenkins but with no luck in finding such. Is this just because I've failed to supply the right locale setting or encoding? Master is a Windows 7 pc. Slave is also Windows 7. I tried changing the checkout and archiving task to run on the master instead of the slave. The filenames were then no longer garbled!? 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-24832) Failed builds are showing up as Aborted
Daniel Beck commented on JENKINS-24832 Failed builds are showing up as Aborted Is this something that could be reproduced by compiling e.g. some Maven-based open source project? 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-24832) Failed builds are showing up as Aborted
Daniel Beck updated JENKINS-24832 Failed builds are showing up as Aborted Change By: Daniel Beck (23/Sep/14 7:47 PM) Component/s: maven 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-24831) Executor gets assigned multiple times
Daniel Beck commented on JENKINS-24831 Executor gets assigned multiple times Could you provide a minimal, complete, verifiable example of jobs that have this problem? Which plugins are used (e.g. to trigger + wait, to require two executors per run, ...), in which versions? 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-24832) Failed builds are showing up as Aborted
swolk commented on JENKINS-24832 Failed builds are showing up as Aborted We were previously running 1.565.1 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-15819) The name of the archived directory/file is garbled.(保存された成果物のディレクトリ/ファイル名が文字化けする)
Lars Lykke edited a comment on JENKINS-15819 The name of the archived directory/file is garbled.(保存された成果物のディレクトリ/ファイル名が文字化けする) I'm able to reproduce this issue (or something apparently similar) on Jenkins v. 1.581. My steps to reproduce is to 1) Check out files from our SCM (StarTeam plugin) 2) Verify files containing special characters are correct in the workspace (which they are) 3) After the files have been archived using the standard Archive Artifacts Post build step, the filenames containing special chars have been garbled. So files are retrieved correctly from SCM but get their filename garbled upon archiving. In my particular case the filenames contain the characters 'æ', 'ø' and 'å'. These are the chars being garbled by the archiving step. I've been searching for a way of testing whether or not I could influence the setting via some sort of startup parameter to Jenkins but with no luck in finding such. Is this just because I've failed to supply the right locale setting or encoding? Master is a Windows 7 pc. Slave is also Windows 7. 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] [role-strategy] (JENKINS-24819) Please add an "Apply" button and make "Apply" and "Save" button sticky
Daniel Beck updated JENKINS-24819 Please add an "Apply" button and make "Apply" and "Save" button sticky Change By: Daniel Beck (23/Sep/14 7:38 PM) Component/s: role-strategy Component/s: matrix-auth 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-15819) The name of the archived directory/file is garbled.(保存された成果物のディレクトリ/ファイル名が文字化けする)
Lars Lykke commented on JENKINS-15819 The name of the archived directory/file is garbled.(保存された成果物のディレクトリ/ファイル名が文字化けする) I'm able to reproduce this issue (or something apparently similar) on Jenkins v. 1.581. My steps to reproduce is to 1) Check out files from our SCM (StarTeam plugin) 2) Verify files containing special characters are correct in the workspace (which they are) 3) After the files have been archived using the standard Archive Artifacts Post build step, the filenames containing special chars have been garbled. So files are retrieved correctly from SCM but get their filename garbled upon archiving. In my particular case the filenames contain the characters 'æ', 'ø' and 'å'. These are the chars being garbled by the archiving step. I've been searching for a way of testing whether or not I could influence the setting via some sort of startup parameter to Jenkins but with no luck. Master is a Windows 7 pc. Slave is also Windows 7. 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-24832) Failed builds are showing up as Aborted
Daniel Beck commented on JENKINS-24832 Failed builds are showing up as Aborted Which version were you upgrading from? 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-24832) Failed builds are showing up as Aborted
swolk updated JENKINS-24832 Failed builds are showing up as Aborted Changing to critical as this makes it so folks don't get notified on build failures. I can add a build notification for Aborted but it is confusing to users. Change By: swolk (23/Sep/14 7:01 PM) Priority: Major Critical 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-24832) Failed builds are showing up as Aborted
swolk created JENKINS-24832 Failed builds are showing up as Aborted Issue Type: Bug Assignee: Unassigned Attachments: 13179.tgz Components: core Created: 23/Sep/14 6:24 PM Description: After upgrading to Jenkins 1.565.2, I'm seeing some builds showing up with status Aborted instead of Failed when there is a compilation issue. We use maven jobs and have incremental building enabled (this has worked fine for us for a long time.) We also use multiple threads for the maven build. Seems if one thread is in the middle of running unit tests where as the other one compiles and fails, then the other thread gets killed and status for module shows as ABORTED in main server log. Could this be caused by https://issues.jenkins-ci.org/browse/JENKINS-22641 fix introduced in latest LTS release? [woot@eng301 logs]$ grep 13179 catalina.out | grep apps-nonstop INFO: SCM changes detected in apps-nonstop. Triggering #13179 INFO: apps-nonstop/com.netbase:deploy #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:app-prospero-widget #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:app-stream-server #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:prospero-framework #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:transformer #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:app-cb-closure #13179 main build action completed: ABORTED INFO: apps-nonstop/com.netbase:dailyupdate #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:persist-api #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:alert-manager #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:content-api #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:app-iodocs #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:persist-cb #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:log #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:rosalind #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:acc-block-result #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:content-rosalind #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:app-ariel #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:consumerbase2 #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:app-ix #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:nlp #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:test #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:cb-insight-api-tools #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:app-cb #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:prospero-api #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:prospero-lucene4 #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:applications #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:megatron #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:engine-lucene4 #13179 main build action completed: NOT_BUILT INFO: apps-nonstop #13179 main build action completed: FAILURE Environment: Jenkins 1.565.2 Project: Jenkins Priority: Major Reporter: swolk
[JIRA] [matrix-auth] (JENKINS-24819) Please add an "Apply" button and make "Apply" and "Save" button sticky
Jesse Glick assigned JENKINS-24819 to Unassigned Please add an "Apply" button and make "Apply" and "Save" button sticky Change By: Jesse Glick (23/Sep/14 6:16 PM) Assignee: Jesse Glick 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] [repository-connector] (JENKINS-24781) Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 -> 1.0.1)
Dejan Stojadinovic resolved JENKINS-24781 as Not A Defect Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 -> 1.0.1) Actually, version 1.0.1 works as expected for known dependencies fetched from Maven central (tested with junit:junit:4.11). Somehow 1.0.1 can't fetch in-house built dependencies from in-house Nexus repository (version 2.8.1) created with Maven 3.1.1 (while version 0.8.2 works flawlessly). All-in-all root cause is obviously on my side; solving as not a defect. Change By: Dejan Stojadinovic (23/Sep/14 6:14 PM) Status: Open Resolved Resolution: Not A Defect 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] [parameterized-trigger] (JENKINS-24810) The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop
Clinton Barr commented on JENKINS-24810 The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop After re-creating a parent-child project configuration with new projects, I've found that as soon as I add slave creation (and deletion at the end) and trigger builds to run on the label given to them, I can reproduce this issue. I will continue to hone in on my configuration of projects to see where the issue may reside. Intuitively, the creation of Jenkins slaves should have no correlation to the trigger build step that causes the runaway ChildProject builds, but the runaway happens explicitly when slave creation is added. I apologize for my shotgun approach earlier. Additionally, do you have any idea when the next release will happen? I know that FileBuildParameterFactory logging would be of paramount use here. 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-24825) Missing build history moving a job when BuildDir is set to a custom location
Jesse Glick updated JENKINS-24825 Missing build history moving a job when BuildDir is set to a custom location Like a bug in core. Change By: Jesse Glick (23/Sep/14 6:11 PM) Labels: folders Component/s: cloudbees-folder 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-24831) Executor gets assigned multiple times
Octavian Ciuhandu created JENKINS-24831 Executor gets assigned multiple times Issue Type: Bug Assignee: Unassigned Components: core Created: 23/Sep/14 6:02 PM Description: We have multiple slave nodes, on windows, all having the number of executors set to 1. Our workflow is as follows: Job 1 requests an executor with a specific label and calls Job 2 (waiting for it's completion) Job 2 requests another executor with same label and calls Job 3 (waiting for it's completion). Very seldom, we have runs where the same node (with the number of executors set to 1) gets assigned 2 times (we always assign 2 executors to a run). Environment: Jenkins 1.575 Project: Jenkins Labels: jenkins windows executor Priority: Major Reporter: Octavian Ciuhandu 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] [maven2] (JENKINS-8711) Post build action deploy to maven repository does not honor the "private maven repository" setting
Daniel Serodio commented on JENKINS-8711 Post build action deploy to maven repository does not honor the "private maven repository" setting Why is the deploy done from the master, shouldn't it be done from the slave where the job was built? 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] [credentials] (JENKINS-22568) Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
Steven Christou
commented on JENKINS-22568
Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
Nick Brown The fix for this issue was specifically for parameterized builds, and not the 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] [parameterized-trigger] (JENKINS-24810) The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop
Clinton Barr commented on JENKINS-24810 The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop I will see if I can reproduce this behavior in a simpler project. 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] [backup] (JENKINS-9141) Cannot restore a Hudson config backup to Jenkins
jan host commented on JENKINS-9141 Cannot restore a Hudson config backup to Jenkins I have found a workaround. Put your backup file(tar.gz) into root of your file system and setup the path to backup folder as / After that you will see options to choose what file you want to use. 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] [backup] (JENKINS-9141) Cannot restore a Hudson config backup to Jenkins
jan host edited a comment on JENKINS-9141 Cannot restore a Hudson config backup to Jenkins I have found a workaround. Put your backup file(tar.gz) into root of your file system ( / ) and setup the path to backup folder as / After that you will see options to choose what file you want to use. 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] [cloudbees-folder] (JENKINS-24825) Missing build history moving a job when BuildDir is set to a custom location
Daniel Beck commented on JENKINS-24825 Missing build history moving a job when BuildDir is set to a custom location Related: RM-1712 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] [parameterized-trigger] (JENKINS-24810) The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop
Daniel Beck commented on JENKINS-24810 The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop Could you please try to provide a minimal example that demonstrates the problem? Preferably working on a pristine Jenkins instance with as few non-default plugins as possible? A job configuration with 20+ build steps, countless plugin dependencies, and hundreds of lines of script code isn't exactly easy to analyze... See also http://www.catb.org/esr/faqs/smart-questions.html#volume and http://stackoverflow.com/help/mcve 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] [analysis-collector] (JENKINS-17187) Add columns to the main view that show the number of warnings
Ulli Hafner commented on JENKINS-17187 Add columns to the main view that show the number of warnings The android lint plug-in is not part of the analysis collector plug-in. (See also JENKINS-17168) 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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Baptiste Mathus commented on JENKINS-23924 New div layout breaks Radiator view I'm gonna work in this one ASAP. But a bit time lacking just now, so if anyone cares about carving a pool request on the current master HEAD that would definitely help to fix it quicker. Thanks 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] [parameterized-trigger] (JENKINS-24810) The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop
Clinton Barr updated JENKINS-24810 The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop I have attached the config.xml and log in a text file, complete except for exclusions of any sensitive product information. Change By: Clinton Barr (23/Sep/14 4:34 PM) Attachment: ParameterizedTriggerBugReport_ParentProject_config.xml Attachment: ParameterizedTriggerBugReport_ParentProject_Log.txt 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] (JENKINS-24786) Since 2.2.6, environment variables are not expanded in git publisher
Thomas Spalinger commented on JENKINS-24786 Since 2.2.6, environment variables are not expanded in git publisher I'm still stuck on 2.2.5. You are more expert than me, but because of the error message, I didn't try anything else, because the error states clearly to me that it's a permission problem. The error for unknown host or not a valid url, when the var is not expanded is usually different. I will check if I find time tomorrow to test it with a fixed value instead of an env variable. 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] [analysis-collector] (JENKINS-17187) Add columns to the main view that show the number of warnings
Sebastian Schuberth commented on JENKINS-17187 Add columns to the main view that show the number of warnings Thanks. I did this now, but when adding the "Number of warnings" column to a view I see only a checkbox labeled "FindBugs warnings" below the column description. I'm using a self--compiled version of the Android Lint plugin on my Jenkins which has view column support merged [1], so I was expecting Android Lint to also show up as a checkbox to the "Number of warnings" column provided by the analysis-collector. Any idea why that checkbox does not show up? [1] https://github.com/jenkinsci/android-lint-plugin/pull/4 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-24826) Parametrized build with file parameter does not return QueueItem location
Daniel Beck commented on JENKINS-24826 Parametrized build with file parameter does not return QueueItem location Is this a regression from an earlier version of Jenkins? 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-24821) Jenkins missing build size in Build History Trend
Daniel Beck commented on JENKINS-24821 Jenkins missing build size in Build History Trend Which version of the disk usage plugin? When you reload the page, does it work then? Are the newest two builds newer than when the page was originally loaded (and therefore inserted by AJAX updates)? 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] [skip-certificate-check] (JENKINS-24830) Certificate isn't ignored when using Javamail
Daniel Beck commented on JENKINS-24830 Certificate isn't ignored when using Javamail Is this about https://wiki.jenkins-ci.org/display/JENKINS/Skip+Certificate+Check+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] [subversion] (JENKINS-24802) notifyCommit don't trigger a build if two svn repositories have same url start
Daniel Beck commented on JENKINS-24802 notifyCommit don't trigger a build if two svn repositories have same url start Please only mark as fixed once it's merged, otherwise it's confusing. 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] [ec2] (JENKINS-24676) Region list not being populated when keys are entered
Francis Upton commented on JENKINS-24676 Region list not being populated when keys are entered @recampbell, yes makes sense, and maybe I'm just being pedantic, but with your change, wouldn't we be testing the connection with some default region (and it might work) and be misleading for the user, rather than failing the Test Connection with some reasonable message. I agree the current situation is bad. 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] [analysis-collector] (JENKINS-17187) Add columns to the main view that show the number of warnings
Ulli Hafner commented on JENKINS-17187 Add columns to the main view that show the number of warnings I thought the functionality is quite self explanatory. In order to show the FindBugs results in a column you need to add the FindBugs column. In order to show the results of all tools in one column you need to install and activate the analysis-collector plug-in. Then you need to add the "Number of warnings" column. 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] [parameterized-trigger] (JENKINS-24810) The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop
Clinton Barr commented on JENKINS-24810 The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop Does that problem always occur? (every time you launch a build of that parent project?) I have about 10 consecutive builds (last 10) of the parent project that displayed this issue and needed to be aborted, so yes. Do parent builds run on slaves? Parent builds run on the master, triggers another separate project to create slaves for the child project discussed here, and then builds the child project. Does that problem occur on any slaves? Or only on a specific slave? The build trigger duplication issue happens on the master, since it is the executor that triggers the child project. The slaves that are created earlier in the parent project are only connected to the child project through a node label (so that they will accept child project builds). Do builds stop to proceed after parameterized-trigger starts? (that is, parameterized-trigger doesn't finish?) It appears as if the build trigger step does finish (as you will see in the log), since the console continues to the next build step. I suspect this doesn't matter, necessarily, since the trigger for the Child project has the "Block until triggered projects finish" setting unchecked. Config.xml and Console output? Sure. I'll go get them. 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] [skip-certificate-check] (JENKINS-24830) Certificate isn't ignored when using Javamail
Corneil du Plessis created JENKINS-24830 Certificate isn't ignored when using Javamail Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: skip-certificate-check Created: 23/Sep/14 3:42 PM Description: We get the following exception after installing the plugin. javax.mail.MessagingException: Could not connect to SMTP host: mail.tsctech.com, port: 465; nested exception is: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1934) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:638) Is there a way to verify the functioning of the plugin? Project: Jenkins Priority: Critical Reporter: Corneil du Plessis 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] [parameterized-trigger] (JENKINS-24810) The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop
ikedam
commented on JENKINS-24810
The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop
Unfortunately, FileBuildParameterFactory never outputs valid logs (not only for you case). That will be fixed in a future release.
Let me know:
Does that problem always occur? (every time you launch a build of that parent project?)
Do parent builds run on slaves?
Does that problem occur on any slaves? Or only on a specific slave?
Do builds stop to proceed after parameterized-trigger starts? (that is, parameterized-trigger doesn't finish?)
Could you attach config.xml of that project? That is placed at ${JENKINS_HOME}/jobs/(project name)/config.xml.
Could you attach whole console output of that parent 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] [git] (JENKINS-24786) Since 2.2.6, environment variables are not expanded in git publisher
Mark Waite commented on JENKINS-24786 Since 2.2.6, environment variables are not expanded in git publisher I'm not as persuaded that it is authentication related, since there were no significant authentication related changes in the transition from git plugin 2.2.5 to 2.2.6. There were updates to newer versions of the dependencies so that the credentials dependencies now depend on the most recently released versions of the credentials plugins and so that the plugin now depends on the most recent version of the git client plugin. Several new credentials tests were added in git client plugin 1.10.2, but no significant authentication related changes in the transition from git client plugin 1.10.1 to 1.10.2. Have you been able to make local authentication changes which resolved the issue, or are you still stuck having to run plugin 2.2.5? 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] [ec2] (JENKINS-24676) Region list not being populated when keys are entered
recampbell edited a comment on JENKINS-24676 Region list not being populated when keys are entered @Francis the problem is that you currently get an unhelpful stacktrace when you try to test the connection. My patch does not select a default region for you, it just uses a default region for the sake of the test (and does not save this anywhere) – you still must select a region to complete the configuration. Make sense? 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] [ec2] (JENKINS-24676) Region list not being populated when keys are entered
recampbell commented on JENKINS-24676 Region list not being populated when keys are entered @Francis the problem is that you currently get an unhelpful stacktrace when you try to test the connection. My patch does not select a default region for you, it just uses a default region for the sake of the test – you still must select a region. Make sense? 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] [disk-usage] (JENKINS-24829) Calculationg Disk usage on a slave is way too slow
Hrusikesh Panda created JENKINS-24829 Calculationg Disk usage on a slave is way too slow Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage Created: 23/Sep/14 3:20 PM Description: For a simple dummy build job whose workspace size is 380KB, disk usage plugin takes almost 4 minutes to come back with results. Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 3 minutes 39 seconds Using Jenkins ver. 1.580 and this is a Windows slave machine where the usage is being calculated. Project: Jenkins Labels: plugin Priority: Major Reporter: Hrusikesh Panda 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-24827) maven-hpi-plugin should be upgraded to Jetty 8
recampbell commented on JENKINS-24827 maven-hpi-plugin should be upgraded to Jetty 8 Discussion: https://groups.google.com/forum/#!topic/jenkinsci-dev/QCGogzAeP4Q 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-24826) Parametrized build with file parameter does not return QueueItem location
Daniel Beck updated JENKINS-24826 Parametrized build with file parameter does not return QueueItem location Change By: Daniel Beck (23/Sep/14 3:21 PM) Assignee: huybrechts Component/s: core Component/s: parameterized-trigger 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-24827) maven-hpi-plugin should be upgraded to Jetty 8
recampbell commented on JENKINS-24827 maven-hpi-plugin should be upgraded to Jetty 8 I was able to get this partially complete here: https://github.com/jenkinsci/maven-hpi-plugin/pull/11 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-24828) BuildPipeline view is mangled by latest css changes
Klaus Bittrich created JENKINS-24828 BuildPipeline view is mangled by latest css changes Issue Type: Bug Assignee: Unassigned Attachments: pipeline.png Components: core Created: 23/Sep/14 3:08 PM Description: The BuildPipeline view is looking weird now, because of the forced white background color for table cells. I believe it's caused by of the changes made in #JENKINS-24625. Environment: Jenkins 1.581 Build Pipeline Plugin 1.4.3 Project: Jenkins Labels: user-experience Priority: Minor Reporter: Klaus Bittrich 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-24827) maven-hpi-plugin should be upgraded to Jetty 8
recampbell created JENKINS-24827 maven-hpi-plugin should be upgraded to Jetty 8 Issue Type: Improvement Assignee: Unassigned Components: core Created: 23/Sep/14 2:57 PM Description: hpi:run currently starts Jetty 6, whereas the default container for jenkins.war is Jetty 8. So we should upgrade hpi:run to launch a Jetty 8 container. Project: Jenkins Labels: jetty Priority: Minor Reporter: recampbell 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] [job-dsl-plugin] (JENKINS-21328) Support for StabilityTestDataPublisher plugin
Daniel Spilker edited a comment on JENKINS-21328 Support for StabilityTestDataPublisher plugin Will be released in 1.26. 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] [job-dsl-plugin] (JENKINS-21328) Support for StabilityTestDataPublisher plugin
Daniel Spilker commented on JENKINS-21328 Support for StabilityTestDataPublisher plugin Will be release in 1.26. 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] [parameterized-trigger] (JENKINS-24826) Parametrized build with file parameter does not return QueueItem location
Aleksey Maksimov created JENKINS-24826 Parametrized build with file parameter does not return QueueItem location Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger Created: 23/Sep/14 2:55 PM Description: Triggering build w/o file parameters returns HTTP 201 with response header having 'location' parameter pointing to queue item. Triggering build with file parameter(s) returns HTTP 303 redirecting to a build page. The behaviour shall be the same in both cases. Environment: 1.581/Ubuntu 14.04 LTS Trusty Tahr Project: Jenkins Priority: Minor Reporter: Aleksey Maksimov 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] [job-dsl-plugin] (JENKINS-24823) Support for Mask Passwords Plugin
Daniel Spilker resolved JENKINS-24823 as Fixed Support for Mask Passwords Plugin Will be released in 1.26. Change By: Daniel Spilker (23/Sep/14 2:55 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] [job-dsl-plugin] (JENKINS-24823) Support for Mask Passwords Plugin
SCM/JIRA link daemon commented on JENKINS-24823 Support for Mask Passwords Plugin Code changed in jenkins User: Daniel Spilker Path: docs/Home.md docs/Job-DSL-Commands.md docs/Job-reference.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/wrapper/WrapperContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/wrapper/WrapperHelperSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/77d8ef89ed328c7505e4c94741f1bd6cfcbf6ceb Log: Merge branch 'JENKINS-24823' Conflicts: docs/Home.md Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/8bd57500e994...77d8ef89ed32 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] [job-dsl-plugin] (JENKINS-21328) Support for StabilityTestDataPublisher plugin
Daniel Spilker resolved JENKINS-21328 as Fixed Support for StabilityTestDataPublisher plugin Change By: Daniel Spilker (23/Sep/14 2:38 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] [ec2] (JENKINS-19845) EC2 plugin incorrectly reports current instance count
SCM/JIRA link daemon commented on JENKINS-19845 EC2 plugin incorrectly reports current instance count Code changed in jenkins User: Roland Groen Path: src/main/java/hudson/plugins/ec2/EC2Cloud.java src/main/java/hudson/plugins/ec2/EC2Tag.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java http://jenkins-ci.org/commit/ec2-plugin/5286a643db63d6199f1a99e2015046e0948c7867 Log: JENKINS-19845, EC2 plugin incorrectly reports current instance count Changed tag name to jenkins_slave_type Made the tag name a static value Cleaned up indentation Removed eclipse import format changes 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] [ec2] (JENKINS-19845) EC2 plugin incorrectly reports current instance count
SCM/JIRA link daemon commented on JENKINS-19845 EC2 plugin incorrectly reports current instance count Code changed in jenkins User: Roland Groen Path: src/main/java/hudson/plugins/ec2/EC2Cloud.java http://jenkins-ci.org/commit/ec2-plugin/dd2d1e63d423e0cfb4ee0a9ca38bfdc2c0c223eb Log: JENKINS-19845, EC2 plugin incorrectly reports current instance count Improvement, not a fix. This code checks if the tags match the configured tags 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] [ec2] (JENKINS-19845) EC2 plugin incorrectly reports current instance count
SCM/JIRA link daemon commented on JENKINS-19845 EC2 plugin incorrectly reports current instance count Code changed in jenkins User: Francis Upton Path: src/main/java/hudson/plugins/ec2/EC2Cloud.java src/main/java/hudson/plugins/ec2/EC2Tag.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java http://jenkins-ci.org/commit/ec2-plugin/2b28c7acb1d45e558c0ad8b306c960ed91d8a43d Log: Merge pull request #107 from EdiaEducationTechnology/master JENKINS-19845 Compare: https://github.com/jenkinsci/ec2-plugin/compare/b99f8191e990...2b28c7acb1d4 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.
