[JIRA] (JENKINS-17223) Failed build unity3d project with message Building Player from editor scripts requires Unity PRO
Roy Inganta Ginting commented on JENKINS-17223 Failed build unity3d project with message Building Player from editor scripts requires Unity PRO 1. 100% sure. 2. Not it is not. The license costs us $1500. Here are my steps to activate unity license. First i return default license from license manager and then i activate the paid license, Help- Manage License - Activate New License - Paste license number into provided text field. 3. Here is the command line, "C:\Program Files (x86)\Unity\Editor\Unity.exe" -batchMode -nographics -quit -executeMethod Build.Windows -projectPath "C:\Program Files (x 86)\Jenkins\workspace\Grand-Indonesia\client\unity" Do i have to registered my license in different way? if so, could you please point me a thorough guidance. 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] (JENKINS-16694) Config-file-provider does not submit modified file (submit button simply does nothing at all)
SCM/JIRA link daemon resolved JENKINS-16694 as Fixed Config-file-provider does not submit modified file (submit button simply does nothing at all) Change By: SCM/JIRA link daemon (15/Mar/13 6:58 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16694) Config-file-provider does not submit modified file (submit button simply does nothing at all)
SCM/JIRA link daemon commented on JENKINS-16694 Config-file-provider does not submit modified file (submit button simply does nothing at all) Code changed in jenkins User: imod Path: src/main/resources/org/jenkinsci/plugins/configfiles/ConfigFilesManagement/edit.jelly http://jenkins-ci.org/commit/config-file-provider-plugin/f2e34e708a30f5626c06a926bad4e9d23c9f429e Log: FIXED JENKINS-16694 fix form submission in IE You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
white paper commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Thanks cray fellow. 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] (JENKINS-16276) NPE cause dead thread slave
Bart Vanhaute commented on JENKINS-16276 NPE cause dead thread slave Reproduced on Jenkins ver. 1.505: java.lang.NullPointerException at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:240) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:70) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1294) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:140) at hudson.model.Executor.run(Executor.java:212) It looks like this is happening when the first project to execute on a slave is a Matrix 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/groups/opt_out.
[JIRA] (JENKINS-16694) Config-file-provider does not submit modified file (submit button simply does nothing at all)
Markus KARG commented on JENKINS-16694 Config-file-provider does not submit modified file (submit button simply does nothing at all) Tried with Jenkins 1.504 + IE9: Submission is working well! 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] (JENKINS-16276) NPE cause dead thread slave
Bart Vanhaute edited a comment on JENKINS-16276 NPE cause dead thread slave Reproduced on Jenkins ver. 1.505: java.lang.NullPointerException at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:240) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:70) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1294) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:140) at hudson.model.Executor.run(Executor.java:212) It looks like this is happening when the first project to execute on a slave is a Matrix 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/groups/opt_out.
[JIRA] (JENKINS-16694) Config-file-provider does not submit modified file (submit button simply does nothing at all)
Markus KARG edited a comment on JENKINS-16694 Config-file-provider does not submit modified file (submit button simply does nothing at all) Tried with Jenkins 1.504 + IE10: Submission is working well! 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] (JENKINS-15356) NPE caused executor thread death
Bart Vanhaute commented on JENKINS-15356 NPE caused executor thread death Reproduced on Jenkins ver. 1.505: java.lang.NullPointerException at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:240) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:70) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1294) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:140) at hudson.model.Executor.run(Executor.java:212) It looks like this is happening when the first project to execute on a slave is a Matrix 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/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Mikhail Andreev commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ I have similar problem with Timothy Appnel, and I downloaded: http://mirrors.karan.org/jenkins/plugins/git/1.2.0/ http://mirrors.karan.org/jenkins/plugins/git-client/1.0.3/ Copy *.hpi to JENKINS_HOME/plugins and Downgrade to these plugins. 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] (JENKINS-14161) SVN checkout failure doesn't prevent the build from starting
Sabine Neubauer commented on JENKINS-14161 SVN checkout failure doesnt prevent the build from starting We have the same problem in our project with Jenkins 1.486. The problem are not only wrong results in the build report but also an unknown state of the build artefact if no compile or test failure occurs. 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] (JENKINS-17223) Failed build unity3d project with message Building Player from editor scripts requires Unity PRO
lacostej commented on JENKINS-17223 Failed build unity3d project with message Building Player from editor scripts requires Unity PRO Roy, The plugin is supposed to execute the exact same operation. So this is weird. Other questions to understand your setup are you running in a master/slave setup ? are you running Jenkins as a special user ? How was jenkins installed ? could you please compare the editor.log output when running from the command line and the one when running from jenkins ? It will be copied into the jenkins console? Also make sure that when running jenkins you find the editor.log in the same location (if jenkins runs as a different user, try running the command line as that user) 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] (JENKINS-17223) Failed build unity3d project with message Building Player from editor scripts requires Unity PRO
lacostej edited a comment on JENKINS-17223 Failed build unity3d project with message Building Player from editor scripts requires Unity PRO Roy, The plugin is supposed to execute the exact same operation. So this is weird. Other questions to understand your setup are you running in a master/slave setup ? are you running Jenkins as a special user ? How was jenkins installed ? could you please compare the editor.log output when running from the command line and the one when running from jenkins ? It will be copied into the jenkins console. Also make sure that when running jenkins you find the editor.log in the same location (if jenkins runs as a different user, try running the command line as that user) 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] (JENKINS-16974) Build Now link on MultiJob page doesn't work
Jurgen Van Bouchaute commented on JENKINS-16974 Build Now link on MultiJob page doesnt work Same issue here. Please fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17073) Support specifying logger for phing
Alexander Obuhovich commented on JENKINS-17073 Support specifying logger for phing If you install and enable "AnsiColor Plugin" (for Jenkins) it should work, because it will grab all bash escape sequences, that makes colors and convert them to HTML markup. 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] (JENKINS-15156) Builds disappear from build history after completion
Voiculescu Bogdan Alexandru commented on JENKINS-15156 Builds disappear from build history after completion I confirm regression! please re-open this. Is getting annoying. 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] (JENKINS-5396) Support tags instead of branches
ricktw commented on JENKINS-5396 Support tags instead of branches Since this feature is still not implemented, I've found a work-around which works for me: Configure the 'default' Branch in the job and configure a 'windows command' or 'shell script' as first build step which executes: hg update -r TAGNAME 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] (JENKINS-17223) Failed build unity3d project with message Building Player from editor scripts requires Unity PRO
Roy Inganta Ginting commented on JENKINS-17223 Failed build unity3d project with message Building Player from editor scripts requires Unity PRO are you running in a master/slave setup ? No, just 1 machine without slave. are you running Jenkins as a special user ? How was jenkins installed ? I used windows native package. However, i changed the user to be my log on user, not jenkins default (Local System). could you please compare the editor.log output when running from the command line and the one when running from jenkins ? It will be copied into the jenkins console. Also make sure that when running jenkins you find the editor.log in the same location (if jenkins runs as a different user, try running the command line as that user) Jenkins output LICENSE SYSTEM 2013315 15:59:42 No start/stop license dates set LICENSE SYSTEM 2013315 15:59:42 Opening https://license.unity3d.com/update/poll?cmd=2tx_id=8cb1e5b67fd9dd445b596e41cc053899 LICENSE SYSTEM 2013315 15:59:42 Posting rootSystemInfoIsoCodeen/IsoCodeUserNameGI/UserNameOperatingSystemWindows 7 Service Pack 1 (6.1.7601) 64bit/OperatingSystemOperatingSystemNumeric610/OperatingSystemNumericProcessorTypeIntel(R) Core(TM) i7 CPU U 640 @ 1.20GHz/ProcessorTypeProcessorSpeed1197/ProcessorSpeedProcessorCount4/ProcessorCountProcessorCores2/ProcessorCoresPhysicalMemoryMB7990/PhysicalMemoryMBComputerNameGDP-ALIENWARE-1/ComputerNameComputerModelIntel(R) Core(TM) i7 CPU U 640 @ 1.20GHz (7990 MB)/ComputerModelUnityVersion4.1.0f4/UnityVersion/SystemInfo TimeStamp Value="ikMt89t6MldHHg=="/ But not in command line log. My guess, it is licensing problem on unity3d plugin. I have set up a new build server on windows 7 32 bit , with unity 4.1 default license and everything run flawlessly. 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] (JENKINS-17223) Failed build unity3d project with message Building Player from editor scripts requires Unity PRO
lacostej commented on JENKINS-17223 Failed build unity3d project with message Building Player from editor scripts requires Unity PRO My guess, it is licensing problem on unity3d plugin. As said earlier, the plugin only invokes the unity3d command line. So if it fails from jenkins, it means the context in which it runs from the command line on your CMD and from jenkins is different in some way. Can you try creating a new free-style Jenkins job, add a "Execute Windows bash command" build step and add 3 things env "C:\Program Files (x86)\Unity\Editor\Unity.exe" -batchMode -nographics -quit -executeMethod Build.Windows -projectPath "C:\Program Files (x86)\Jenkins\workspace\Grand-Indonesia\client\unity" cat PATH\TO\YOUR\editor.log (you can start with just env and cat to make sure they are correct before adding the unity command that takes time) Let's see what happens: 1. Let's see if this works or fail (note don't just look at the jenkins job result (it might report error/pass status incorrectly based on return codes of your batch script). Make sure the artifact created by your Build.Windows command was created properly - and check its timestamp and location. 2. Let's compare env output from jenkins and from your CMD. 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] (JENKINS-13972) Concurrent matrix builds abort
Jeremy Van Haren commented on JENKINS-13972 Concurrent matrix builds abort We are seeing this behavior back as well, we aren't using NTFS symlinks so not sure that recent change will address the issue for us 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] (JENKINS-16873) Root workspace directory is removed when doing initial clone
Thomas Schmidt reopened JENKINS-16873 Root workspace directory is removed when doing initial clone Please fix the problem with non actual but newer than 1.3.3 git versions (e.g. 1.6.0.2) with the directory to clone to. Or adjust the git version requirement. Change By: Thomas Schmidt (15/Mar/13 10:20 AM) Resolution: Fixed Status: Resolved Reopened 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] (JENKINS-17224) HudsonTestCase cannot be run in parallel
Roland Gruber created JENKINS-17224 HudsonTestCase cannot be run in parallel Issue Type: Bug Assignee: Unassigned Components: core Created: 15/Mar/13 11:44 AM Description: The temporary folder for the Jenkins installation is always the same on Windows. Therefore, running multiple JUnit tests in parallel does not work. Solution: use some random prefix for the folders Project: Jenkins Priority: Minor Reporter: Roland Gruber 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] (JENKINS-17225) Parantheses in a regex make regex never match
Fabian Pachner
created JENKINS-17225
Parantheses in a regex make regex never match
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
tasks-plugin
Created:
15/Mar/13 12:00 PM
Description:
I tried to use parantheses '(', ')' when searching for open tasks with the Task Scanner Plugin (v4.35). I need the parantheses to group my regex and to apply * operator. For example, I want to search for "TODO(A-Za-z0-9)*. This delivers zero reults, also I have TODOs matching this regex. My actual regex is more complicated, so I definitely need parantheses to group it, this is just a simple example.
If I escape the parantheses, I get hundreds of thousands of results. So this can't be the correct approach. How can I get grouping and using * in my regex to work?
Project:
Jenkins
Priority:
Major
Reporter:
Fabian Pachner
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] (JENKINS-4433) log4j upgrade to version 1.2.12 or later
Ryszard Łach commented on JENKINS-4433 log4j upgrade to version 1.2.12 or later We've just upgraded log4j to 1.2.16 (simply replacing .jar file) in jenkins 1.503. So far we didn't notice any problems. What's the problem with upgrade in jenkins ditribution? Did we miss something important before jar replacement? Cheers, R. 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] (JENKINS-17226) Checksum mismatch in svn update - but still marked as success
Bernhard Hiller created JENKINS-17226 Checksum mismatch in svn update - but still marked as success Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 15/Mar/13 12:23 PM Description: Sometimes updating the source fails with a checksum error: ERROR: Failed to update svn://server/trunk/folder org.tmatesoft.svn.core.SVNException: svn: E155017: Checksum mismatch while updating 'F:\Path\to\some\project\.svn\text-base\someclass.cs.svn-base'; expected: 'fabb3e1e4f6a89438445a281518a5a11', actual: 'fc03e7e936e1d2a88fff6f888f4c613c' Futher updates are done succesfully (there are more than one Repository URLs), and finally the "update sources" project finishes with: Finished: SUCCESS Consequently, dependent projects are built and may end with failures due to inconsistent source code. We have to manually check the log files of our update projects, and in case of errors do a manual clean-up and upate with tortoise. Environment: Jenkins runs on a virtual machine with Windows XP SP3 (32bit), the source code repository is Silksvn 1.7.8.43435 (64bit) running on a WIndows 2008 R2 (64bit) server. Project: Jenkins Labels: subversion ignored-failure Priority: Critical Reporter: Bernhard Hiller 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] (JENKINS-17227) global search when in nested view doesn't reset breadcrumb
Marc Günther created JENKINS-17227 global search when in nested view doesnt reset breadcrumb Issue Type: Bug Assignee: Unassigned Components: nested-view Created: 15/Mar/13 12:48 PM Description: When I'm in some sub view, and I do a search in the global search box and click on a job in the result list, the breadcrumb still shows that sub view. So it appears that the found job is in that sub view, although it isn't. Example: I'm in "Jenkins - Project A" and search for "some job in B", I end up with "Jenkins - Project A - some job in B", although that job is not in Project A. Project: Jenkins Priority: Trivial Reporter: Marc Günther 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] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Jon Radon commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Michael: My module is on a TAG. The project polls hourly for changes on a tag named RTB_13_4. I can probably provide a config or log if needed. I also looked at the code a little, but wasn't sure where to start. 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] (JENKINS-17228) Fail build when subversion workspace is locked
Paavo Helde created JENKINS-17228 Fail build when subversion workspace is locked Issue Type: Improvement Assignee: Unassigned Components: subversion Created: 15/Mar/13 1:20 PM Description: This is a request to backport a Hudson fix into Jenkins. This is a 2-line change done in Hudson Subversion plugin 2.3.3, SHA 37ca9c134702878e6bb824dde108d63c6df043d8 https://github.com/hudson-plugins/subversion-plugin/commit/37ca9c134702878e6bb824dde108d63c6df043d8 Rationale: subversion workspace often remains locked if previous svn update failed because of bad network connection, wiping the workspace is not useful for anything in this situation, rather the opposite. Project: Jenkins Labels: subversion Priority: Major Reporter: Paavo Helde 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] (JENKINS-13709) ClassCast Exception when parsing JUnit surefire reports during website generation
Ronoaldo Pereira commented on JENKINS-13709 ClassCast Exception when parsing JUnit surefire reports during website generation I am still having this on Jenkins 1.505. The same error is happening on surefire reports: [INFO] --- maven-surefire-plugin:2.13:test (default-test) @ mailmarketing-api --- [JENKINS] Recording test results hudson.util.IOException2: Failed to read /var/lib/tomcat6/data/jenkins/jobs/mailmarketing-api/workspace/target/surefire-reports/TEST-webappj.framework.ext.mailmarketing.api.BatchSubscribeFileTest.xml at hudson.tasks.junit.TestResult.parse(TestResult.java:284) at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:223) at hudson.tasks.junit.TestResult.parse(TestResult.java:192) at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:148) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:453) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:435) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) 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$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: org.dom4j.DocumentException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory Nested exception: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory at org.dom4j.io.SAXReader.read(SAXReader.java:484) at org.dom4j.io.SAXReader.read(SAXReader.java:264) at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:129) at hudson.tasks.junit.TestResult.parse(TestResult.java:267) ... 35 more Caused by: java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory at org.dom4j.DocumentFactory.getInstance(DocumentFactory.java:97) at org.dom4j.io.SAXReader.getDocumentFactory(SAXReader.java:645) at org.dom4j.io.SAXReader.createContentHandler(SAXReader.java:969) at org.dom4j.io.SAXReader.read(SAXReader.java:449) ... 38 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators.
[JIRA] (JENKINS-17228) Fail build when subversion workspace is locked
jan_ruzicka commented on JENKINS-17228 Fail build when subversion workspace is locked current location of the fixed section in jenkinsci/subversion-plugin is src/main/java/hudson/scm/subversion/UpdateUpdater.java lines 181 and 182 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] (JENKINS-17228) Fail build when subversion workspace is locked
jan_ruzicka commented on JENKINS-17228 Fail build when subversion workspace is locked Will the failing build unlock the workspace? or will all the fallowing builds fail? 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] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita started work on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Change By: Bruno P. Kinoshita (15/Mar/13 2:06 PM) Status: Open InProgress 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] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita stopped work on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Change By: Bruno P. Kinoshita (15/Mar/13 2:06 PM) Status: InProgress Open 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] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita started work on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Change By: Bruno P. Kinoshita (15/Mar/13 2:06 PM) Status: Open InProgress 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] (JENKINS-17229) Config Rotator does not trig on new baseline (our case 8789)
Jens Brejner created JENKINS-17229 Config Rotator does not trig on new baseline (our case 8789) Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: config-rotator Created: 15/Mar/13 2:14 PM Description: We use Jenkins version 1.502 and Config Rotator version 1.0.2. If a job is configured: and the baseline baseline has promotion level TESTED then this job will not trig on new baselines of that component with promotion level INITIAL. But if changing the promotion level for baseline baseline then the job trigger on new baselines. So when searching for new baselines the promotion level for the current baseline must not be used! Project: Jenkins Priority: Major Reporter: Jens Brejner 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] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Marc Seeger commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel I get this on Linux - Linux with Jenkins ver. 1.504 Different data centers though, so probably not the most stable network connection. 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] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Marc Seeger edited a comment on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel I get this on Linux - Linux with Jenkins ver. 1.504 Different data centers though, so probably not the most stable network connection. FATAL: Unable to delete script file /tmp/hudson9103641402954770242.sh hudson.util.IOException2: remote file operation failed: /tmp/hudson9103641402954770242.sh at hudson.remoting.Channel@3ce3262f:django at hudson.FilePath.act(FilePath.java:861) at hudson.FilePath.act(FilePath.java:838) at hudson.FilePath.delete(FilePath.java:1223) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:101) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:593) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:494) at hudson.remoting.Request.call(Request.java:129) at hudson.remoting.Channel.call(Channel.java:672) at hudson.FilePath.act(FilePath.java:854) ... 13 more Caused by: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Channel$CloseCommand.execute(Channel.java:850) at hudson.remoting.Channel$2.handle(Channel.java:435) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command close created at at hudson.remoting.Command.init(Command.java:56) at hudson.remoting.Channel$CloseCommand.init(Channel.java:844) at hudson.remoting.Channel$CloseCommand.init(Channel.java:842) at hudson.remoting.Channel.close(Channel.java:909) at hudson.remoting.Channel.close(Channel.java:892) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:849) ... 2 more FATAL: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:672) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $Proxy46.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:915) at hudson.Launcher$ProcStarter.join(Launcher.java:360) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:91) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:593) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:850) at hudson.remoting.Channel$2.handle(Channel.java:435) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: hudson.remoting.Channel$OrderlyShutdown ... 3 more Caused by: Command close created at at hudson.remoting.Command.init(Command.java:56) at hudson.remoting.Channel$CloseCommand.init(Channel.java:844) at hudson.remoting.Channel$CloseCommand.init(Channel.java:842) at hudson.remoting.Channel.close(Channel.java:909) at hudson.remoting.Channel.close(Channel.java:892) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:849) ... 2 more
[JIRA] (JENKINS-17230) Unload component from Config Rotator job does not work (our case 8790)
Jens Brejner created JENKINS-17230 Unload component from Config Rotator job does not work (our case 8790) Issue Type: Bug Assignee: Praqma Support Components: config-rotator Created: 15/Mar/13 2:16 PM Description: The following is a screenshot from the configure page of a config rotator job. It is possible to Add a new component or delete an existing. But if deleting an existing component the component is not unloaded when running the Jenkins job again. This is an error. Project: Jenkins Priority: Major Reporter: Jens Brejner 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] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Marc Seeger edited a comment on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel I get this on Linux - Linux with Jenkins ver. 1.504 Different data centers though, so probably not the most stable network connection. FATAL: Unable to delete script file /tmp/hudson9103641402954770242.sh hudson.util.IOException2: remote file operation failed: /tmp/hudson9103641402954770242.sh at hudson.remoting.Channel@3ce3262f:django at hudson.FilePath.act(FilePath.java:861) at hudson.FilePath.act(FilePath.java:838) at hudson.FilePath.delete(FilePath.java:1223) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:101) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:593) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:494) at hudson.remoting.Request.call(Request.java:129) at hudson.remoting.Channel.call(Channel.java:672) at hudson.FilePath.act(FilePath.java:854) ... 13 more Caused by: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Channel$CloseCommand.execute(Channel.java:850) at hudson.remoting.Channel$2.handle(Channel.java:435) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command close created at at hudson.remoting.Command.init(Command.java:56) at hudson.remoting.Channel$CloseCommand.init(Channel.java:844) at hudson.remoting.Channel$CloseCommand.init(Channel.java:842) at hudson.remoting.Channel.close(Channel.java:909) at hudson.remoting.Channel.close(Channel.java:892) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:849) ... 2 more FATAL: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:672) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $Proxy46.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:915) at hudson.Launcher$ProcStarter.join(Launcher.java:360) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:91) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:593) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:850) at hudson.remoting.Channel$2.handle(Channel.java:435) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: hudson.remoting.Channel$OrderlyShutdown ... 3 more Caused by: Command close created at at hudson.remoting.Command.init(Command.java:56) at hudson.remoting.Channel$CloseCommand.init(Channel.java:844) at hudson.remoting.Channel$CloseCommand.init(Channel.java:842) at hudson.remoting.Channel.close(Channel.java:909) at hudson.remoting.Channel.close(Channel.java:892) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:849) ... 2 more The
[JIRA] (JENKINS-17221) You must use POST method to trigger builds warning message pops up preventing remote triggering of builds with parameters using wget URL http://server/job/myjob/buildWithParam
Jesse Glick resolved JENKINS-17221 as Not A Defect You must use POST method to trigger builds warning message pops up preventing remote triggering of builds with parameters using wget URL http://server/job/myjob/buildWithParameters?PARAMETER=Value As the message says, you must now use POST requests for things like this. Consult the documentation for wget or whatever you use. Pull requests with more emphatic/clearer messages welcome. Change By: Jesse Glick (15/Mar/13 2:28 PM) Status: Open Resolved Resolution: NotADefect 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] (JENKINS-15156) Builds disappear from build history after completion
Jesse Glick commented on JENKINS-15156 Builds disappear from build history after completion Better to not reopen long-running issues like this, which just results in an unreadable mess, and results in confusion about whether fixes were really applied. In this case they were, so it is likely that your problem has a different origin. Please file a fresh issue blocking JENKINS-8754 and clearly stating your Jenkins version, platform, list of plugins, exact observed behavior, and any other information you have which might help developers reproduce the problem or even guess at its cause. 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] (JENKINS-17231) Remote API: Exception on /computer/xyz/api/json?depth=2 fails when jlnp connection is broken
Dan Savilonis
created JENKINS-17231
Remote API: Exception on /computer/xyz/api/json?depth=2 fails when jlnp connection is broken
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
15/Mar/13 2:35 PM
Description:
If a slave jlnp connection is broken (to a Windows host?), it looks like the offlineCause element is not computed correctly.
Accessing jenkins/computer/xxx/api/json works fine, but jenkins/computer/qual-a/api/json?depth=2 fails with a 500 error:
{ "actions" : [ ], "displayName" : "xxx", "executors" : [ { "currentExecutable" : null, "currentWorkUnit" : null, "idle" : true, "likelyStuck" : false, "number" : 0, "progress" : -1 } ], "icon" : "computer-x.png", "idle" : true, "jnlpAgent" : true, "launchSupported" : false, "loadStatistics" : { "busyExecutors" : { "hour" : { }, "min" : { }, "sec10" : { } }, "queueLength" : { "hour" : { }, "min" : { }, "sec10" : { } }, "totalExecutors" : { "hour" : { }, "min" : { }, "sec10" : { } } }, "manualLaunchAllowed" : true, "monitorData" : { "hudson.node_monitors.SwapSpaceMonitor" : null, "hudson.node_monitors.ArchitectureMonitor" : null, "hudson.node_monitors.ResponseTimeMonitor" : null, "hudson.node_monitors.TemporarySpaceMonitor" : null, "hudson.node_monitors.DiskSpaceMonitor" : null, "hudson.node_monitors.ClockMonitor" : null }, "numExecutors" : 1, "offline" : true, "offlineCause" : { "cause" : {
Status Code: 500
Exception: org.kohsuke.stapler.export.NotExportableException: class java.net.SocketException doesn't have @ExportedBean
Stacktrace:
javax.servlet.ServletException: org.kohsuke.stapler.export.NotExportableException: class java.net.SocketException doesn't have @ExportedBean
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487)
at org.kohsuke.stapler.Stapler.service(Stapler.java:164)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
[JIRA] (JENKINS-16244) View.hasPeople too slow to use in sidepanel.jelly
eguess74 edited a comment on JENKINS-16244 View.hasPeople too slow to use in sidepanel.jelly We are running 1.504 and we still have problem with very long load of the main page view at times. If I specify the URL for particular job - it works fine. It also works fine for few days after restart, but then suddenly gets stuck. But the at some point releases and works fast again. We have about 800+ jobs and about 100 users 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] (JENKINS-10502) Add an option to make archiving the artifacts non-fatal if they don't exist
Jesse Glick updated JENKINS-10502 Add an option to make archiving the artifacts non-fatal if they dont exist Change By: Jesse Glick (15/Mar/13 2:50 PM) URL: https://github.com/jenkinsci/jenkins/pull/732 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] (JENKINS-17232) Jenkins mixes-up form fields when Back browser button is used
Radek Chromy created JENKINS-17232 Jenkins mixes-up form fields when Back browser button is used Issue Type: Bug Affects Versions: current Assignee: huybrechts Components: parameterized-trigger Created: 15/Mar/13 2:55 PM Description: Do the following: Goto an parametrized job start page. Fill-out all paramteters fields Start the task Go to the task's console Use browser's Back button to return to the task start page. The form seems to be filled in, but the values are mixed between fields. E.g. The previous PARAM1 value is now in the PARAM2 field. This makes reusing the form very difficult and error-prone, as upon a first look the form seems to be filled correctly. Project: Jenkins Labels: jenkins Priority: Major Reporter: Radek Chromy 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] (JENKINS-17228) Fail build when subversion workspace is locked
Paavo Helde commented on JENKINS-17228 Fail build when subversion workspace is locked In principle the workspace might also be locked because somebody else has logged into the slave computer and doing some svn operations manually. Therefore I would not suggest automatic "svn cleanup" or something like that, just failing the build (as the Hudson fix does) would be fine IMO. A user can always wipe the workspace explicitly if he/she is not able to solve the problem otherwise. 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] (JENKINS-5396) Support tags instead of branches
Jakob Malm commented on JENKINS-5396 Support tags instead of branches @ricktw A downside is that Jenkins won't record the correct changeset... 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] (JENKINS-17218) Environment variables broken in git 1.3 plug-in
Nicolas De Loof commented on JENKINS-17218 Environment variables broken in git 1.3 plug-in This "feature" was only supported due to GitAPI using a forked process to run git-cli. Need to be implemented as a parameter expansion 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] (JENKINS-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Nicolas De Loof commented on JENKINS-17198 Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files short term workaround is either to run jenkins with -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true, or check "clean workspace after checkout" - this option will clean workspace ...before (sic!) checkout and avoid conflict. Could you also tell me if there is anything during your build that could have touched support/tools/relink/macholib/MachO.py ? I'm looking for a public git repository I could use to reproduce 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/groups/opt_out.
[JIRA] (JENKINS-16244) View.hasPeople too slow to use in sidepanel.jelly
Jesse Glick resolved JENKINS-16244 as Fixed View.hasPeople too slow to use in sidepanel.jelly @eguess74 the bug reported here has been fixed. Whatever problem you are encountering is probably unrelated. File it separately and include a thread dump, without which it is impossible to guess at what is going on in your instance. Change By: Jesse Glick (15/Mar/13 3:25 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/groups/opt_out.
[JIRA] (JENKINS-17233) Maven release fails when password contains space
Alexander Bunkenburg created JENKINS-17233 Maven release fails when password contains space Issue Type: Bug Affects Versions: current Assignee: teilo Components: m2release Created: 15/Mar/13 3:25 PM Description: My password contains a space, like "one two". When I start a mvn release, the build fails with an error message that contains the second part of my password. Project: Jenkins Priority: Minor Reporter: Alexander Bunkenburg 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] (JENKINS-17212) Git clean broken on Windows
Nicolas De Loof commented on JENKINS-17212 Git clean broken on Windows short term workaround is either to run jenkins with -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true possible workaround is to copy JGit CleanCommand into git-client and force IGNORE on such failure, not sure this is a good option (from a code duplication perspective, it isn't) 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] (JENKINS-17225) Allow regular expressions as tags
Ulli Hafner updated JENKINS-17225 Allow regular expressions as tags Actually the plug-in has no "official" support for regexps yet. It feeds the string to a regular _expression_ matcher internally. Up to now it was supposed that the tag itself will be a plain string. Change By: Ulli Hafner (15/Mar/13 3:38 PM) Summary: Paranthesesinaregexmakeregexnevermatch Allowregularexpressionsastags Issue Type: Bug Improvement Priority: Major Minor 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] (JENKINS-17219) HTTPS URLs to Git repositories fail with 1.3.0
Nicolas De Loof commented on JENKINS-17219 HTTPS URLs to Git repositories fail with 1.3.0 I just tried to reproduce this issue, setting a jenkins instance to build https://github.com/bloomberg/ci-slave-recipes.git, and fetch is working fine. Can you please describe your installation ? 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] (JENKINS-17219) HTTPS URLs to Git repositories fail with 1.3.0
Nicolas De Loof commented on JENKINS-17219 HTTPS URLs to Git repositories fail with 1.3.0 didn't you just missed the ".git" in repository URL https://github.com/bloomberg/ci-slave-recipes.git ? https://github.com/bloomberg/ci-slave-recipes/info/refs?service=git-upload-pack indeed doesn't exist, but https://github.com/bloomberg/ci-slave-recipes.git/info/refs?service=git-upload-pack is ok 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] (JENKINS-17234) email-ext gives a misleading message when there is an error in a template
Alex Earl
created JENKINS-17234
email-ext gives a misleading message when there is an error in a template
Issue Type:
Bug
Affects Versions:
current
Assignee:
Alex Earl
Components:
email-ext
Created:
15/Mar/13 3:48 PM
Description:
When using a template or custom script and there is a syntax error in the script/template, the email-ext plugin tells the user to report the item as a bug. Instead it should report it as a syntax error in the template/script.
[[ Exception while replacing SCRIPT. Please report this as a bug. ]] {{ groovy.lang.MissingPropertyException: No such property: failing for class: SimpleTemplateScript12 }}
Project:
Jenkins
Priority:
Minor
Reporter:
Alex Earl
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] (JENKINS-17211) HTTP authentication is not possible with JGit implementation of git-client plugin
alf1alf commented on JENKINS-17211 HTTP authentication is not possible with JGit implementation of git-client plugin Support for direct Username/Password config would be great so we do not need to configure each slave - like in the Subversion 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/groups/opt_out.
[JIRA] (JENKINS-17219) HTTPS URLs to Git repositories fail with 1.3.0
Kevin Fleming commented on JENKINS-17219 HTTPS URLs to Git repositories fail with 1.3.0 GitHub (and in my experience, Git in general) does not require the '.git' suffix, and I've been using these URLs for quite some time with no issue. I changed them to use the Git protocol (s/https/git/) and they work fine this morning, still without the .git suffix. I suppose it is possible that something changed on the GitHub end around the same time I upgraded the Git plugin, so I saw an unfortunate coincidence. If it's working in your testing, feel free to close 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/groups/opt_out.
[JIRA] (JENKINS-12188) GIT plug-ins keep lock on workspace file if branch use default insted of master. So unable to clean workspace.
Arkadiy Shapkin commented on JENKINS-12188 GIT plug-ins keep lock on workspace file if branch use default insted of master. So unable to clean workspace. This applied to git plugin version 1.3.0? I have this bug with version 1.3.0 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] (JENKINS-12188) GIT plug-ins keep lock on workspace file if branch use default insted of master. So unable to clean workspace.
Arkadiy Shapkin edited a comment on JENKINS-12188 GIT plug-ins keep lock on workspace file if branch use default insted of master. So unable to clean workspace. This patch applied to git plugin version 1.3.0? I have this bug with version 1.3.0 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] (JENKINS-17235) No error message displayed even on failure if I try to run the same job with same params in parallel
Patrik Johansson
created JENKINS-17235
No error message displayed even on failure if I try to run the same job with same params in parallel
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
build-flow
Created:
15/Mar/13 4:20 PM
Description:
If I run the following flow script all goes well:
parallel (
{ build("Job1", param:1); build("Job2", param:1) },
{ build("Job1", param:2); build("Job2", param:2) }
)
However, when I change it so that I try to run the same job twice, in parallel, with the same params, the build flow job fails without any error traces in the log. So the following script:
parallel (
{ build("Job1", param:1); build("Job2", param:1) },
{ build("Job1", param:1); build("Job2", param:1) }
)
gives the following console output (and a FAILED status):
Started by user anonymous
Building in workspace C:\xxx\.jenkins\jobs\Flow1\workspace
parallel {
Trigger job Job1
Trigger job Job1
Job1 #15 completed
Trigger job Job2
Job2 #12 completed
}
Collecting metadata...
Metadata collection done.
Finished: FAILURE
It would help alot if there was a clear error message saying something like: "Could not run parallel job 'Job1' since identical instances of it were scheduled"
Environment:
Jenkins 1.505, Windows Vista, Build Flow 0.8
Project:
Jenkins
Priority:
Major
Reporter:
Patrik Johansson
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] (JENKINS-12188) GIT plug-ins keep lock on workspace file if branch use default insted of master. So unable to clean workspace.
Arkadiy Shapkin edited a comment on JENKINS-12188 GIT plug-ins keep lock on workspace file if branch use default insted of master. So unable to clean workspace. I have this bug with git plugin version 1.3.0 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] (JENKINS-15319) Failure starting slave nodes
John Dyer commented on JENKINS-15319 Failure starting slave nodes Any idea when this build will be available 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] (JENKINS-17190) Help for Content Token Reference in plugin email-ext is in cryptic format
Karina Guenther commented on JENKINS-17190 Help for Content Token Reference in plugin email-ext is in cryptic format It's happening to us as well. I think it's related to us upgrading Jenkins yesterday. 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] (JENKINS-17029) update-center.json seems to be broken
Daniel Lehmann commented on JENKINS-17029 update-center.json seems to be broken The issue seems to be fixed for me since yesterday. 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] (JENKINS-17029) update-center.json seems to be broken
Daniel Lehmann edited a comment on JENKINS-17029 update-center.json seems to be broken The issue seems to be fixed for me since yesterday without updating 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/groups/opt_out.
[JIRA] (JENKINS-17236) Pluggable artifact transfer storage
Jesse Glick
created JENKINS-17236
Pluggable artifact transfer storage
Issue Type:
New Feature
Assignee:
Jesse Glick
Components:
core
Created:
15/Mar/13 4:50 PM
Description:
Currently artifact archiving follows a fixed model: artifacts are defined in ArtifactArchiver (or MavenArtifactArchiver) configuration; they are copied from slave to master using FilePath.copyRecursiveTo; they are stored in ${Run.rootDir}/archive; and they are served by browsing this directory in master.
This system has obvious scalability limitations: channel transfer is not particularly efficient; and storing enormous files in the builds directory can cause disk overruns.
The CloudBees Fast Archiver plugin tries to address the transfer speed issue by using a better algorithm. This helps, but the implementation (replacing the ArtifactArchiver build step) is very awkward, and cannot be made to work properly with Maven projects, fingerprints, etc.
Some installations may anyway not need to copy files at all. The master and slave might share a common network filesystem, or might have a way of efficiently transferring file references (e.g. ZFS send).
Finally, there should be the option to store artifacts in a better way: on a big slow drive, in a compressed archive, etc.
To handle all these requirements we need an extension point that encompasses both transfer and storage of artifacts for each build.
Project:
Jenkins
Priority:
Major
Reporter:
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/groups/opt_out.
[JIRA] (JENKINS-10436) Jenkins Environment Variables are not set when using a freestyle Invoke top-level Maven Targets that is restricted to execute on a slave
evernat commented on JENKINS-10436 Jenkins Environment Variables are not set when using a freestyle Invoke top-level Maven Targets that is restricted to execute on a slave Is it reproduced with a recent Jenkins version? 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] (JENKINS-13035) Duplicate Views Tab Bar option
evernat commented on JENKINS-13035 Duplicate Views Tab Bar option I do not reproduce the issue, but I do not have the Countjobs Viewstabbar plugin. Do you reproduce the 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/groups/opt_out.
[JIRA] (JENKINS-13035) Duplicate Views Tab Bar option
evernat assigned JENKINS-13035 to Ignacio Albors Duplicate Views Tab Bar option Attributing the issue to the plugin author. Change By: evernat (15/Mar/13 5:16 PM) Assignee: IgnacioAlbors 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] (JENKINS-17029) update-center.json seems to be broken
k n updated JENKINS-17029 update-center.json seems to be broken now it's fixed Change By: k n (15/Mar/13 5:33 PM) Fix Version/s: current 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] (JENKINS-17029) update-center.json seems to be broken
k n closed JENKINS-17029 as Fixed update-center.json seems to be broken fixed Change By: k n (15/Mar/13 5:34 PM) Status: Open Closed 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] (JENKINS-17238) Allow FingerprintCleanupThread to be disabled
Scott Fisler created JENKINS-17238 Allow FingerprintCleanupThread to be disabled Issue Type: Improvement Assignee: Unassigned Components: core Created: 15/Mar/13 6:11 PM Description: Add option for -Dhudson.model.FingerprintCleanupThread.disabled=true just like WorkspaceCleanupThread uses. Scenario:fingerprint is deleted when build-job is shelved, but build-artifact still lives in production server (but can't be fingerprinted). Project: Jenkins Priority: Major Reporter: Scott Fisler 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] (JENKINS-14637) Maven Deployment Linker does not support all permalinks types
SCM/JIRA link daemon commented on JENKINS-14637 Maven Deployment Linker does not support all permalinks types Code changed in jenkins User: imod Path: src/main/java/hudson/plugins/mavendeploymentlinker/MavenDeploymentDownloader.java http://jenkins-ci.org/commit/maven-deployment-linker-plugin/b80b10e246bdc802624265f04a04ec9697e312da Log: FIXED JENKINS-14637 if possible, get all permalinks from target project Compare: https://github.com/jenkinsci/maven-deployment-linker-plugin/compare/1e3eed66f818...b80b10e246bd You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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] (JENKINS-14637) Maven Deployment Linker does not support all permalinks types
SCM/JIRA link daemon resolved JENKINS-14637 as Fixed Maven Deployment Linker does not support all permalinks types Change By: SCM/JIRA link daemon (15/Mar/13 6:12 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] (JENKINS-17239) Last Success and Last Failure time negative on 'public Jenkins'
Raphael Oliveira created JENKINS-17239 Last Success and Last Failure time negative on public Jenkins Issue Type: Bug Assignee: vjuranek Attachments: Screen Shot 2013-03-15 at 3.13.44 PM.png Components: build-publisher Created: 15/Mar/13 6:14 PM Description: The last success and last failure time are negative on the public Jenkins. In the private one it is correct. Project: Jenkins Priority: Minor Reporter: Raphael Oliveira 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] (JENKINS-17236) Pluggable artifact transfer storage
SCM/JIRA link daemon commented on JENKINS-17236 Pluggable artifact transfer storage Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Run.java core/src/main/java/hudson/tasks/ArtifactArchiver.java core/src/main/java/jenkins/model/ArtifactManager.java core/src/main/java/jenkins/model/StandardArtifactManager.java maven-plugin/src/main/java/hudson/maven/MavenBuild.java maven-plugin/src/main/java/hudson/maven/MavenBuildProxy.java maven-plugin/src/main/java/hudson/maven/reporters/MavenArtifact.java maven-plugin/src/main/java/hudson/maven/reporters/MavenArtifactArchiver.java maven-plugin/src/main/java/hudson/maven/reporters/MavenArtifactRecord.java http://jenkins-ci.org/commit/jenkins/e1eea67bb2fa1a356492e91313d84a523f441b34 Log: JENKINS-17236 Initial version of ArtifactManager (no Maven support yet). You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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] (JENKINS-17236) Pluggable artifact transfer storage
Jesse Glick updated JENKINS-17236 Pluggable artifact transfer storage Change By: Jesse Glick (15/Mar/13 6:35 PM) URL: https://github.com/jenkinsci/jenkins/pull/736 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] (JENKINS-17236) Pluggable artifact transfer storage
Jesse Glick started work on JENKINS-17236 Pluggable artifact transfer storage Change By: Jesse Glick (15/Mar/13 6:35 PM) Status: Open InProgress 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] (JENKINS-17240) GitHub Web Hook API Key configuration is not documented
Eric Schoonover created JENKINS-17240 GitHub Web Hook API Key configuration is not documented Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: github Created: 15/Mar/13 7:21 PM Description: I'm trying to figure out where to get the GitHub Web Hook API key mentioned in the configuration section, but it is not documented. Project: Jenkins Priority: Major Reporter: Eric Schoonover 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] (JENKINS-12785) Groovy script console SCMTrigger example causes invalid configuration
Baptiste Mathus updated JENKINS-12785 Groovy script console SCMTrigger example causes invalid configuration Change By: Baptiste Mathus (15/Mar/13 8:39 PM) Summary: GroovyscriptconsoleSCMTriggerexamplecausesinvalid configurationw configuration 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] (JENKINS-12785) Groovy script console SCMTrigger example causes invalid configuration
Baptiste Mathus resolved JENKINS-12785 as Fixed Groovy script console SCMTrigger example causes invalid configuration Thanks Change By: Baptiste Mathus (15/Mar/13 8:47 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] (JENKINS-17241) GEM_PATH env variable wrong when using
Brian Goad created JENKINS-17241 GEM_PATH env variable wrong when using Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: envinject Created: 15/Mar/13 8:55 PM Description: The GEM_PATH environmental variable is not getting set correctly on master nodes. On slave nodes, it works just fine. Here is a sample of how it looks: GEM_PATH: "file:/var/lib/jenkins/jenkins-data/plugins/ruby-runtime/WEB-INF/lib/stapler-jruby-1.177.jar!/gem" Here is an example of how I expect it to render: GEM_PATH: "/var/lib/jenkins/.rvm/gems/ree-1.8.7-2012.02rn:/var/lib/jenkins/.rvm/gems/ree-1.8.7-2012.02@global" --- Disabling the envinject plugin renders the GEM_PATH environmental variable correctly. Also, we can use the plugin to override the GEM_PATH manually, but this is not ideal. We should be able to render this environmental variable via rvm. Environment: jenkins workspace $ uname -a Linux jenkins.compute-1.internal 3.6.10-4.fc18.x86_64 #1 SMP Tue Dec 11 18:01:27 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Project: Jenkins Labels: plugin jenkins envinject environment-variables linux, gem_path Priority: Major Reporter: Brian Goad 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] (JENKINS-7653) Apparently aborted build w/ incomplete artifacts marked as stable
Jesse Glick commented on JENKINS-7653 Apparently aborted build w/ incomplete artifacts marked as stable Now: https://github.com/hudson/hudson-2.x/commit/3c65bb06b22317d40dd9261e831dfbcfb7daeb36 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] (JENKINS-8616) cannot use spot instances
Jai Ram Rideout commented on JENKINS-8616 cannot use spot instances I agree, it would be great to have this feature. Has anyone starting working on this, or are there plans to add this feature in the near future? If not, I can take a shot at it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7653) Apparently aborted build w/ incomplete artifacts marked as stable
Jesse Glick resolved JENKINS-7653 as Duplicate Apparently aborted build w/ incomplete artifacts marked as stable Change By: Jesse Glick (15/Mar/13 9:20 PM) Status: Open Resolved Resolution: Duplicate 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] (JENKINS-7140) Archive the artifacts fails, still build successful
Jesse Glick updated JENKINS-7140 Archive the artifacts fails, still build successful Using JENKINS-2058 for core bug; leaving this open for clone workspace plugin which I guess has its own copy of the code. Change By: Jesse Glick (15/Mar/13 9:22 PM) Component/s: core 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] (JENKINS-11087) Failure to archive artifacts doesn't cause build to fail
Jesse Glick resolved JENKINS-11087 as Duplicate Failure to archive artifacts doesnt cause build to fail Change By: Jesse Glick (15/Mar/13 9:23 PM) Status: Open Resolved Resolution: Duplicate 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] (JENKINS-2058) success even when archive artifact java error
SCM/JIRA link daemon resolved JENKINS-2058 as Fixed success even when archive artifact java error Change By: SCM/JIRA link daemon (15/Mar/13 9:25 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] (JENKINS-2058) success even when archive artifact java error
SCM/JIRA link daemon commented on JENKINS-2058 success even when archive artifact java error Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/tasks/ArtifactArchiver.java http://jenkins-ci.org/commit/jenkins/6d904f5c195fe63e340afd19d18579a321fd5d5b Log: FIXED JENKINS-2058 Fail the build if artifact archiving fails with an IOException. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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] (JENKINS-15868) Cannot archive big remote log files using Archive the artifacts post-build action
Jesse Glick updated JENKINS-15868 Cannot archive big remote log files using Archive the artifacts post-build action Change By: Jesse Glick (15/Mar/13 9:34 PM) Component/s: core Component/s: postbuild-task 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] (JENKINS-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Nicolas Berniolles edited a comment on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly Yes Martin. I have some recursive symlinks in my github's repo. The downgrade resolved successfully the issue. My projects are back online. 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] (JENKINS-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Nicolas Berniolles commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly Yes Martin. I have some recursive symlinks in my github's repo. The downgrade resolved successfully the issue. My project are back online. 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] (JENKINS-15015) Add support for the NodeLabel Parameter Plugin
Rob Petti commented on JENKINS-15015 Add support for the NodeLabel Parameter Plugin I've created a pull request that adds this ability to the plugin: https://github.com/jenkinsci/build-flow-plugin/pull/24 This is not specific to NodeLabel parameter, so it may work with other special parameter types as well. 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] (JENKINS-17242) pushes no longer being recorded in destination repository
A K created JENKINS-17242 pushes no longer being recorded in destination repository Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 15/Mar/13 10:38 PM Description: Rolled fwd jenkins installation to use latest git plugin, and now post-build task of pushing no longer registers in repository. It says it is doing it, but checking the repository confirms that the branch has not been updated. No changes were made to project, it just stopped working. Environment: Linux Ubuntu jdk6 Project: Jenkins Priority: Major Reporter: A K 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] (JENKINS-2058) success even when archive artifact java error
dogfood commented on JENKINS-2058 success even when archive artifact java error Integrated in jenkins_main_trunk #2376 FIXED JENKINS-2058 Fail the build if artifact archiving fails with an IOException. (Revision 6d904f5c195fe63e340afd19d18579a321fd5d5b) Result = SUCCESS Jesse Glick : 6d904f5c195fe63e340afd19d18579a321fd5d5b Files : changelog.html core/src/main/java/hudson/tasks/ArtifactArchiver.java 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] (JENKINS-17242) pushes no longer being recorded in destination repository
A K commented on JENKINS-17242 pushes no longer being recorded in destination repository Pushing HEAD to branch master of test_local repository Opening connection Counting objects Finding sources Writing objects Pushing HEAD to branch master at repo test_local Opening connection Counting objects Finding sources Writing objects Except, master doesn't update. :S 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] (JENKINS-17242) pushes no longer being recorded in destination repository
A K updated JENKINS-17242 pushes no longer being recorded in destination repository Change By: A K (15/Mar/13 10:49 PM) Priority: Major Blocker 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] (JENKINS-17242) pushes no longer being recorded in destination repository
A K commented on JENKINS-17242 pushes no longer being recorded in destination repository Rolling back to Git Plugin version 1.1.26, and restarting jenkins fixed the problem. fyi. 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] (JENKINS-17236) Pluggable artifact transfer storage
Jesse Glick
commented on JENKINS-17236
Pluggable artifact transfer storage
API should be fleshed out; still need to add Maven support. Working on a prototype plugin archiving to ${build.rootDir}/archive.zip.
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.
