[JIRA] [concurrent-build] (JENKINS-15098) svnexternals causing issues with concurrent builds
kutzi updated JENKINS-15098 svnexternals causing issues with concurrent builds Change By: kutzi (02/Mar/14 9:21 AM) Due Date: 9/Mar/14 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/groups/opt_out.
[JIRA] [nodelabelparameter] (JENKINS-16574) IllegalArgumentException when Rebuilding a project with nodelabel
Dominik Bartholdi resolved JENKINS-16574 as Cannot Reproduce IllegalArgumentException when Rebuilding a project with nodelabel closing as of no feedback... Change By: Dominik Bartholdi (02/Mar/14 10:45 AM) Status: Open Resolved Resolution: CannotReproduce 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/groups/opt_out.
[JIRA] [youtrack] (JENKINS-22007) Only run commands that has not been run before
Erik Zielke created JENKINS-22007 Only run commands that has not been run before Issue Type: Improvement Assignee: Erik Zielke Components: youtrack Created: 02/Mar/14 11:26 AM Description: The problem is that if a user has two jobs one for each branch in a scm then when changes are merged from one branch to another, the commands are applied again. Project: Jenkins Priority: Minor Reporter: Erik Zielke 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-22002) Copy Artifact doesn't support jobs in different Folders
ikedam commented on JENKINS-22002 Copy Artifact doesnt support jobs in different Folders As long as I tested, it should work. Please report how to reproduce the problem. Job configurations. Structures of jobs and folders. And "folder" means cloudbees-folder plugin? Artifacts they archive. Copyartifact configurations. Especially, how you specify job names. Absolute/relative, static/dynamic (using variables). Expected result. Actual result. I don't know what is the attached file. If you want a support for your Jenkins Enterprise, you cannot get that here. Please contact cloudbees professional support. 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/groups/opt_out.
[JIRA] [core] (JENKINS-22008) buildTimeTrend only shows the last 20 builds
Dominik Bartholdi created JENKINS-22008 buildTimeTrend only shows the last 20 builds Issue Type: Bug Assignee: Unassigned Components: core Created: 02/Mar/14 6:45 PM Description: The buildTimeTrend currently only shows the last 20 build, this is caused by an other change made with JENKINS-20892 (related to lazy loading). To fix this issues, 20 builds should handled by using a lazy iterator from the build widget. the issue can be seen here: https://ci.jenkins-ci.org/computer/remote-slave-6/builds Project: Jenkins Labels: lazy-loading Priority: Major Reporter: Dominik Bartholdi 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/groups/opt_out.
[JIRA] [git] (JENKINS-22009) Git Polling Keeps Detecting Changes When Variables in refspec
Christian Goetze
created JENKINS-22009
Git Polling Keeps Detecting Changes When Variables in refspec
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git
Created:
02/Mar/14 8:25 PM
Description:
I have a job where the git refspec and branch are set to +refs/heads/${branch}:refs/remotes/origin/${branch} and the branch is set to ${branch}.
With that configuration, the SCM polling keeps triggering new builds from the same change.
If I replace the variables with their values, the SCM polling works correctly.
Project:
Jenkins
Priority:
Major
Reporter:
Christian Goetze
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/groups/opt_out.
[JIRA] [git] (JENKINS-22003) Null pointer on notifyCommit
jpschewe commented on JENKINS-22003 Null pointer on notifyCommit Will that make it to the stable channel? 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/groups/opt_out.
[JIRA] [cpptest] (JENKINS-18727) The cppTest 9.5 xml output doesn't match the current parser rule
SCM/JIRA link daemon commented on JENKINS-18727 The cppTest 9.5 xml output doesnt match the current parser rule Code changed in jenkins User: Gregory Boissinot Path: .gitignore src/main/java/com/thalesgroup/hudson/plugins/cpptest/CpptestInputMetric.java src/main/java/com/thalesgroup/hudson/plugins/cpptest/VersionComparator.java src/main/resources/com/thalesgroup/hudson/plugins/cpptest/cpptestunit-9.0-to-junit-1.0.xsl src/test/java/com/thalesgroup/hudson/plugins/cpptest/CpptestXSLTest.java src/test/java/com/thalesgroup/hudson/plugins/cpptest/VersionComparatorTest.java src/test/resources/com/thalesgroup/hudson/plugins/cpptest/testcase2/junit-result.xml src/test/resources/com/thalesgroup/hudson/plugins/cpptest/testcase2/result.xml http://jenkins-ci.org/commit/cpptest-plugin/d15f2f0dca4e2e1621fffe87d3ce7e44a6100f0c Log: Merge pull request #6 from Zenika/cpptest-9.0-support JENKINS-18727 Cpptest 9.0+ support Compare: https://github.com/jenkinsci/cpptest-plugin/compare/56b6679cb820...d15f2f0dca4e 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/groups/opt_out.
[JIRA] [cpptest] (JENKINS-18727) The cppTest 9.5 xml output doesn't match the current parser rule
SCM/JIRA link daemon commented on JENKINS-18727 The cppTest 9.5 xml output doesnt match the current parser rule Code changed in jenkins User: Dridi Boukelmoune Path: src/main/java/com/thalesgroup/hudson/plugins/cpptest/CpptestInputMetric.java src/test/java/com/thalesgroup/hudson/plugins/cpptest/CpptestXSLTest.java src/test/resources/com/thalesgroup/hudson/plugins/cpptest/testcase2/junit-result.xml src/test/resources/com/thalesgroup/hudson/plugins/cpptest/testcase2/result.xml http://jenkins-ci.org/commit/cpptest-plugin/e607affb871ea1a3c157ae3cba8d7e942a90a248 Log: Choose the XSL file based on the report version Starting with cpptest 9.0, the report file format changed slightly, fortunately the tool version can be found at the same address xml-wise. This implementation uses a stream reader to avoid completely reading the report twice: once for the version, and once for the conversion. This is convenient since the tool version is in the very first element. The file `cpptestunit-9.0-to-junit-1.0.xsl` isn't actually part of this commit. refs JENKINS-18727 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/groups/opt_out.
[JIRA] [cpptest] (JENKINS-18727) The cppTest 9.5 xml output doesn't match the current parser rule
SCM/JIRA link daemon commented on JENKINS-18727 The cppTest 9.5 xml output doesnt match the current parser rule Code changed in jenkins User: Dridi Boukelmoune Path: src/main/java/com/thalesgroup/hudson/plugins/cpptest/VersionComparator.java src/test/java/com/thalesgroup/hudson/plugins/cpptest/VersionComparatorTest.java http://jenkins-ci.org/commit/cpptest-plugin/714cc2cf56cebfd46d655f964b3bbd47d565de44 Log: Add a simple version number comparator refs JENKINS-18727 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/groups/opt_out.
[JIRA] [git] (JENKINS-22003) Null pointer on notifyCommit
Mark Waite commented on JENKINS-22003 Null pointer on notifyCommit jpschewe yes, the change will be available to all Jenkins update centers once it is released. 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/groups/opt_out.
[JIRA] [cpptest] (JENKINS-18727) The cppTest 9.5 xml output doesn't match the current parser rule
Gregory Boissinot resolved JENKINS-18727 as Fixed The cppTest 9.5 xml output doesnt match the current parser rule Change By: Gregory Boissinot (02/Mar/14 11:52 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/groups/opt_out.
[JIRA] [violations] (JENKINS-14291) Unavailable violations per file view for jslint
rogerhu commented on JENKINS-14291 Unavailable violations per file view for jslint The problem has to do with Java reflection when using Jelly templates: This PR fixes the issue and should be merged: https://github.com/jenkinsci/violations-plugin/pull/13 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/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
ikedam commented on JENKINS-21932 Job hangs if one of multiple triggered builds was aborted I found it reproduces even with only one downstream project: Install parameterized-trigger plugin Create a node "slave1" from Manage Jenkins Manage Nodes New Node No need to launch that node. Create a free style project "downstream". Check "Restrict where this project can be run" (this is displayed only when there are slaves) and enter "slave1" to "Label _expression_" Create a free style project "upstream" Add "Trigger/call builds on other projects" "downstream" for "Projects to build" Check Block until the triggered projects finish their builds Click "Build Now" of "upstream". Cancel the build of "downstream" that should be pending. Result: "upstream" should finish, but actually does not finish. And as long I tested, it does not reproduce with Jenkins = 1.509. Jenkins result 1.480.3 don't reproduce 1.509.2 don't reproduce 1.532.1 reproduce I should find the version of Jenkins that starts produce this problem. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20941) Stored git credentials not used when submodule is updated
su shi commented on JENKINS-20941 Stored git credentials not used when submodule is updated "Cannot reproduce on Mac slave"? I ran into this issue on a mac slave with https protocol 00:00:16.330 originally caused by: 00:00:16.330 Started by user anonymous 00:00:16.435 EnvInject - Loading node environment variables. 00:00:16.482 Building remotely on slave_ios_02 in workspace 00:00:16.552 Fetching changes from the remote Git repository 00:00:16.665 Fetching upstream changes from https://xxx 00:00:17.499 using .gitcredentials to set credentials 00:00:19.708 Checking out Revision b9230db5cf984dfe268bbe4dd6e4aa203743dc0b (origin/master) 00:00:21.652 FATAL: Command "git submodule update --init --recursive" returned status code 1: 00:00:21.652 stdout: Cloning into 'xxx'... 00:00:21.652 00:00:21.652 stderr: fatal: Authentication failed for 'xxx' 00:00:21.652 Clone of 'xxx' into submodule path xxx' failed 00:00:21.652 00:00:21.653 hudson.plugins.git.GitException: Command "git submodule update --init --recursive" returned status code 1: 00:00:21.654 stdout: Cloning into 'xxx'... 00:00:21.654 00:00:21.654 stderr: fatal: Authentication failed for 'xxx' 00:00:21.654 Clone of 'xxx' into submodule path 'xxx' failed 00:00:21.654 00:00:21.654 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1148) 00:00:21.654 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1125) 00:00:21.654 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1121) 00:00:21.654 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:937) 00:00:21.654 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.submoduleUpdate(CliGitAPIImpl.java:598) 00:00:21.654 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.submoduleUpdate(CliGitAPIImpl.java:579) 00:00:21.654 at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source) 00:00:21.654 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 00:00:21.654 at java.lang.reflect.Method.invoke(Method.java:606) 00:00:21.654 at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299) 00:00:21.654 at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280) 00:00:21.654 at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239) 00:00:21.654 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 00:00:21.654 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 00:00:21.654 at hudson.remoting.Request$2.run(Request.java:326) 00:00:21.654 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 00:00:21.654 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 00:00:21.654 at java.util.concurrent.FutureTask.run(FutureTask.java:166) 00:00:21.654 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 00:00:21.654 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 00:00:21.654 at java.lang.Thread.run(Thread.java:724) 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21362) Multiple (User Defined) Global Templates
Alex Earl commented on JENKINS-21362 Multiple (User Defined) Global Templates I'm implementing this as a separate plugin. There will be a link the "Manage Jenkins" page that lets an admin create different templates. Then there will be a separate post-build item that will allow you to add one or more templates to the job. Still some implementation and testing to do, but its coming along nicely. 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21466) Impossible to connect to the VSphere Cloud Anymore
Jason Swager assigned JENKINS-21466 to Jason Swager Impossible to connect to the VSphere Cloud Anymore Change By: Jason Swager (03/Mar/14 5:00 AM) Assignee: JasonSwager 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
chikigai commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Same issue here with Jenkins 1.552 and Subversion Plugin 2.2 using Windows7 slaves. All of our jobs configured to access SVN repositories via the svn:externals property are failing due to authentication failures. Externals set to paths within the same repository and with different repositories both fail. Setting "Additional Credentials" makes no difference whatsoever. 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/groups/opt_out.
[JIRA] [core] (JENKINS-21954) Jenkins can not enter Job's api page with latest version 1.552
Bao Xiaopan(Bob) edited a comment on JENKINS-21954 Jenkins can not enter Jobs api page with latest version 1.552 @darrell.no...@gmail.com hopefully git-plugin can quickly fix this problem... thx for your investigation 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/groups/opt_out.
[JIRA] [core] (JENKINS-21954) Jenkins can not enter Job's api page with latest version 1.552
Bao Xiaopan(Bob) commented on JENKINS-21954 Jenkins can not enter Jobs api page with latest version 1.552 @Darrell Hamilton hopefully git-plugin can quickly fix this problem... thx for your investigation 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/groups/opt_out.
[JIRA] [deploy] (JENKINS-22010) Allow Deploy Plugin to be run more than once on a build
Michael Wiles created JENKINS-22010 Allow Deploy Plugin to be run more than once on a build Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: deploy Created: 03/Mar/14 7:16 AM Description: My build creates two WAR files. The deploy plugin is only able to deploy one of these as I want to customise the context-path in both cases. Would it not be possible to just allow the deploy plugin to be run more than once on a build? Project: Jenkins Priority: Minor Reporter: Michael Wiles 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/groups/opt_out.
