date:20130409













































 
Chris Z
 edited a comment on  JENKINS-17443


connection refused by the server causes NullPointerException
















Answer deleted as it don't repairs your problem. I will try to prepare fix for that.

in src/main/java/hudson/scm/subversion/CheckoutUpdater.java

+import org.tmatesoft.svn.core.SVNErrorCode;

 } catch (SVNException e) {
if(e.getErrorMessage().getErrorCode() == SVNErrorCode.CL_ERROR_PROCESSING_EXTERNALS){   
listener.getLogger().println(e.getMessage());
throw (IOException) new IOException().initCause(new UpdaterException("failed to perform svn checkout", e));   
}
else if(e.getErrorMessage().getErrorCode() == SVNErrorCode.RA_DAV_REQUEST_FAILED){
listener.getLogger().println(e.getMessage());
throw (IOException) new IOException().initCause(new UpdaterException("failed to perform svn checkout", e)); 
}


this is fast 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] [subversion] (JENKINS-17443) 'connection refused by the server' causes NullPointerException













































 
Chris Z
 edited a comment on  JENKINS-17443


connection refused by the server causes NullPointerException

















in src/main/java/hudson/scm/subversion/CheckoutUpdater.java

+import org.tmatesoft.svn.core.SVNErrorCode;

 } catch (SVNException e) {
if(e.getErrorMessage().getErrorCode() == SVNErrorCode.CL_ERROR_PROCESSING_EXTERNALS){   
listener.getLogger().println(e.getMessage());
throw (IOException) new IOException().initCause(new UpdaterException("failed to perform svn checkout", e));   
}
else if(e.getErrorMessage().getErrorCode() == SVNErrorCode.RA_DAV_REQUEST_FAILED){
listener.getLogger().println(e.getMessage());
throw (IOException) new IOException().initCause(new UpdaterException("failed to perform svn checkout", e)); 
}


this is fast 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] [copyartifact] (JENKINS-17529) Broken symlinks during creating wrtifacts

2013-04-09 Thread darv...@gmail.com (JIRA)















































Marcin  I
 created  JENKINS-17529


Broken symlinks during creating wrtifacts















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


copyartifact, core



Created:


09/Apr/13 8:45 AM



Description:


During creating artifacts via "copy artifact" plugin, file with path longer than 60 chars, and created on node different than master (seperate machine), has cut path to target. 
As shown below first file is artifact located in master, and it pointed to broken path on slave where file which we want archive was created.

Bar.java
/var/fpwork/ciscnsn/jenkins_master/jhome/jobs/TUPU_1303_FSM2_build/builds/2013-04-09_10-20-27/archive/src/lteDo/exec/dsp/release/LFSPC-DLTUP-SCT-RT_0009.BIN - /var/fpwork/jenkins_slave_tupu/workspace/TUPU_1303_FSM2_build/src/lteDo/D_LTE/DL_TUP/DL_TUP_SCT/Conf





Environment:


Linux RHEL 5.x, RHEL 6.x




Project:


Jenkins



Labels:


artifact
plugin
job




Priority:


Major



Reporter:


Marcin  I

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git] (JENKINS-17326) Git Wipe Out stopped working

2013-04-09 Thread claudi0.beatr...@gmail.com (JIRA)















































omissis
 updated  JENKINS-17326


Git Wipe Out stopped working
















Change By:


omissis
(09/Apr/13 8:56 AM)




Description:


Hi,Ivejustreinstalledjenkinsonmynewserverandportedalltheoldtaskstothenewinstance.Itallworksfine,butifIenabletheWipeoutworkspacebeforebuildingitplugin(itwaspreviouslyenabledandworkingfine),theclonefailsleavingthejobsworkspacewith0666permissions(soitchmodsa-xtheworkspacedirectory);Icheckedtheumaskanditlookscorrect,its0002.IfIremovetheflag,clearlytheworkspacedoesntgetwipedoutbuteverythingworksagainprettywell.Thisistheoutputfromtheconsole(Ireplacedsomenames):Buildinginworkspace/var/lib/jenkins/jobs/MyProject/workspaceCheckout:workspace//var/lib/jenkins/jobs/MyProject/workspace-hudson.remoting.LocalChannel@20a26542Usingstrategy:DefaultLastBuiltRevision:Revisionad1e4166745f9e33c9851bdefb7494de9651df23(origin/master)UsingshallowcloneWipingoutworkspacefirst.CloningtheremoteGitrepositoryCloningrepositoryg...@git.mycompany.com:myproject/myproject-001/myrepository.gitErrortryingtodeterminethegitversion:Errorperformingcommand:git--versionAssuming1.6ERROR:Errorcloningremoterepoorigin:Couldnotcloneg...@git.mycompany.com:myproject/myproject-001/myrepository.githudson.plugins.git.GitException:Couldnotcloneg...@git.mycompany.com:myproject/myproject-001/myrepository.gitatorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.clone(CliGitAPIImpl.java:219)athudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1002)athudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941)athudson.FilePath.act(FilePath.java:865)athudson.FilePath.act(FilePath.java:838)athudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:941)athudson.plugins.git.GitSCM.checkout(GitSCM.java:1113)athudson.model.AbstractProject.checkout(AbstractProject.java:1353)athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:689)atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:594)athudson.model.Run.execute(Run.java:1567)athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)athudson.model.ResourceController.execute(ResourceController.java:88)athudson.model.Executor.run(Executor.java:237)Causedby:hudson.plugins.git.GitException:Commandgitclone-oorigin--depth1g...@git.mycompany.com:myproject/myproject-001/myrepository.git/var/lib/jenkins/jobs/MyProject/workspacereturnedstatuscode128:stdout:stderr:fatal:destinationpath/var/lib/jenkins/jobs/MyProject/workspacealreadyexistsandisnotanemptydirectory.atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:773)atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.clone(CliGitAPIImpl.java:217)...14moreTryingnextrepositoryERROR:CouldnotclonerepositoryFATAL:Couldnotclonehudson.plugins.git.GitException:Couldnotcloneathudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1014)athudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941)athudson.FilePath.act(FilePath.java:865)athudson.FilePath.act(FilePath.java:838)athudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:941)athudson.plugins.git.GitSCM.checkout(GitSCM.java:1113)athudson.model.AbstractProject.checkout(AbstractProject.java:1353)athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:689)atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:594)athudson.model.Run.execute(Run.java:1567)athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)athudson.model.ResourceController.execute(ResourceController.java:88)athudson.model.Executor.run(Executor.java:237)Andheressomeinfoonsoftwareversions:OS:Ubuntu12.
04
10
Jenkins:1.506Gitplugin:1.30Git:1.7.10.4Java:javaversion1.7.0_15OpenJDKRuntimeEnvironment(IcedTea72.3.7)(7u15-2.3.7-0ubuntu1~12.10.1)OpenJDK64-BitServerVM(build23.7-b01,mixedmode)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] [subversion] (JENKINS-17103) Apply credentials also to separate server used from svn:externals















































Chris Z
 commented on  JENKINS-17103


Apply credentials also to separate server used from svn:externals















It will be quite nice feature to have.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.

2013-04-09 Thread pjl...@combitel.no (JIRA)















































Per J. Lund
 updated  JENKINS-17508


The Discard Old Builds advanced option - removal of only artifacts - does not work for me after 1.503.
















Change By:


Per J. Lund
(09/Apr/13 9:05 AM)




Component/s:


core





Component/s:


disk-usage



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [ci-game] (JENKINS-17530) CI-Game Plug-in fails successful builds by throwing Null-pointer exception

2013-04-09 Thread jcho...@gmail.com (JIRA)















































Janusz Chorko
 created  JENKINS-17530


CI-Game Plug-in fails successful builds by throwing Null-pointer exception















Issue Type:


Bug



Assignee:


redsolo



Components:


ci-game



Created:


09/Apr/13 9:07 AM



Description:


After successful build of one axis of matrix project NullPointerException is thrown. Some rules are repeated while on other axis they are missing.
log:
ci-game evaluating rule: Build result
ci-game scored: 1.0
ci-game evaluating rule: Increased number of failed tests
ci-game evaluating rule: Increased number of passed tests
ci-game evaluating rule: Decreased number of failed tests
ci-game evaluating rule: Decreased number of passed tests
ci-game evaluating rule: Increased number of failed tests
ci-game evaluating rule: Increased number of passed tests
ci-game evaluating rule: Decreased number of failed tests
ci-game evaluating rule: Decreased number of passed tests
ci-game evaluating rule: Open HIGH priority tasks
ci-game evaluating rule: Open HIGH priority tasks
ci-game evaluating rule: Open NORMAL priority tasks
ci-game evaluating rule: Open NORMAL priority tasks
ci-game evaluating rule: Open LOW priority tasks
ci-game evaluating rule: Open LOW priority tasks
ci-game evaluating rule: Open HIGH priority tasks
ci-game evaluating rule: Open NORMAL priority tasks
ci-game evaluating rule: Open LOW priority tasks
ci-game evaluating rule: HIGH priority PMD warnings
ci-game evaluating rule: HIGH priority PMD warnings
ci-game evaluating rule: NORMAL priority PMD warnings
ci-game evaluating rule: NORMAL priority PMD warnings
ci-game evaluating rule: LOW priority PMD warnings
ci-game evaluating rule: LOW priority PMD warnings
ci-game evaluating rule: HIGH priority PMD warnings
ci-game evaluating rule: NORMAL priority PMD warnings
ci-game evaluating rule: LOW priority PMD warnings
ci-game evaluating rule: New HIGH priority Findbugs warnings
ci-game evaluating rule: New NORMAL priority Findbugs warnings
ci-game evaluating rule: New LOW priority Findbugs warnings
ci-game evaluating rule: Fixed HIGH priority Findbugs warnings
ci-game evaluating rule: Fixed NORMAL priority Findbugs warnings
ci-game evaluating rule: Fixed LOW priority Findbugs warnings
ci-game evaluating rule: Changed number of compiler warnings
ci-game evaluating rule: Changed number of checkstyle warnings
ERROR: Publisher hudson.plugins.cigame.GamePublisher aborted due to exception
java.lang.NullPointerException
	at java.util.LinkedList$ListItr.next(Unknown Source)
	at hudson.plugins.cigame.model.ScoreCard.record(ScoreCard.java:121)
	at hudson.plugins.cigame.GamePublisher.perform(GamePublisher.java:60)
	at hudson.plugins.cigame.GamePublisher.perform(GamePublisher.java:45)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:798)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:770)
	at hudson.model.Build$BuildExecution.cleanUp(Build.java:192)
	at hudson.model.Run.execute(Run.java:1620)
	at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:237)
Finished: FAILURE




Environment:


Windows XP, Jenkins 1.508, CI game 1.19




Project:


Jenkins



Priority:


Major



Reporter:


Janusz Chorko

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see:

[JIRA] [android-emulator] (JENKINS-17531) Create Android build files build step incorrectly configures test project

2013-04-09 Thread dan...@adapptor.com.au (JIRA)















































Daniel Murray
 created  JENKINS-17531


Create Android build files build step incorrectly configures test project















Issue Type:


Bug



Affects Versions:


current



Assignee:


Christopher Orr



Components:


android-emulator



Created:


09/Apr/13 9:09 AM



Description:


I have a setup like this:
my-project/
ActionBarSherlock/ # Third party library and some demo apps
MyProject/ # Main project
tests/ # Test project for main project
TouchDB/   # Third party library

When the Create Android build files step runs it appears to be updating MyProject/tests such that the main test project is one of the demo apps from ActionBarSherlock:

android Creating build files for test project at 'MyProject/tests'...
tests $ /var/lib/jenkins/android-sdk-linux/tools/android update test-project -p . -m ../../ActionBarSherlock/samples/demos/
Resolved location of main project to: /var/lib/jenkins/jobs/MyProject/workspace/ActionBarSherlock/samples/demos


If I can provide any more information please let me know, and thanks for an awesome product!




Environment:


Ubuntu linux 12.04/64




Project:


Jenkins



Priority:


Minor



Reporter:


Daniel Murray

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [android-emulator] (JENKINS-17531) Create Android build files build step incorrectly configures test project

2013-04-09 Thread dan...@adapptor.com.au (JIRA)















































Daniel Murray
 updated  JENKINS-17531


Create Android build files build step incorrectly configures test project
















Change By:


Daniel Murray
(09/Apr/13 9:11 AM)




Description:


Ihaveasetuplikethis:my-project/

ActionBarSherlock/#Thirdpartylibraryandsomedemoapps

MyProject/#Mainproject

tests/#Testprojectformainproject

TouchDB/#ThirdpartylibraryWhentheCreateAndroidbuildfilessteprunsitappearstobeupdatingMyProject/testssuchthatthemaintestprojectisoneofthedemoappsfromActionBarSherlock:[android]CreatingbuildfilesfortestprojectatMyProject/tests...[tests]$/var/lib/jenkins/android-sdk-linux/tools/androidupdatetest-project-p.-m../../ActionBarSherlock/samples/demos/Resolvedlocationofmainprojectto:/var/lib/jenkins/jobs/MyProject/workspace/ActionBarSherlock/samples/demosIfIcanprovideanymoreinformationpleaseletmeknow,andthanksforanawesomeproduct!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [android-emulator] (JENKINS-17531) Create Android build files build step incorrectly configures test project
















































Christopher Orr
 resolved  JENKINS-17531 as Fixed


Create Android build files build step incorrectly configures test project
















I actually fixed this yesterday; it will be in the next release.





Change By:


Christopher Orr
(09/Apr/13 9:33 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] [job-dsl-plugin] (JENKINS-17513) For SVN only one workspaceupdater is supported

2013-04-09 Thread chmo...@eurofunk.com (JIRA)















































Christoph Moser
 commented on  JENKINS-17513


For SVN only one workspaceupdater is supported















Here is the now working script:

 def unittestNamesList = test1, test2, test3
 def versions = v1, v2, v3, v4
  for (int versionsIt = 0; versionsIt  versions.size(); versionsIt++) {
 for (int i = 0; i  unittestNamesList.size(); i++) {
 def jobName = versionsversionsIt + '_' + unittestNamesListi
 job {
 name jobName
 scm {
 svn('svn://svn-server/dev/trunk/checkTools', 'checkTools') { svnNode -
 svnNode / excludedRegions('regionToExclude')
 svnNode / excludedUsers('userToExclude') 
 def toChange = svnNode / workspaceUpdater
 toChange.attributes().put('class', 'hudson.scm.subversion.UpdateWithRevertUpdater')
 }
 }
 }
 }
 }

_

Before your hint I tried following line instead of your suggestion:
 svnNode / workspaceUpdater(class:'hudson.scm.subversion.UpdateWithRevertUpdater')

The above line did not work, but did also not result in any errormessage ... but it prevented every new/changed config.xml from saving.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [android-emulator] (JENKINS-17517) Support for dynamic skins (a la JellyBean devices)















































Christopher Orr
 commented on  JENKINS-17517


Support for dynamic skins (a la JellyBean devices)















Ahh, thanks for the update! I'll take a look.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [job-dsl-plugin] (JENKINS-17513) For SVN only one workspaceupdater is supported

2013-04-09 Thread chmo...@eurofunk.com (JIRA)













































 
Christoph Moser
 edited a comment on  JENKINS-17513


For SVN only one workspaceupdater is supported
















Here is the now working script:


def unittestNamesList = ["test1", "test2", "test3"]
def versions = ["v1", "v2", "v3", "v4"]
 for (int versionsIt = 0; versionsIt  versions.size(); versionsIt++) {
for (int i = 0; i  unittestNamesList.size(); i++) {
def jobName = versions[versionsIt] + '_' + unittestNamesList[i]
job {
name jobName
scm {
svn('svn://svn-server/dev/trunk/checkTools', 'checkTools') { svnNode -
svnNode / excludedRegions('regionToExclude')
svnNode / excludedUsers('userToExclude') 
def toChange = svnNode / workspaceUpdater
toChange.attributes().put('class', 'hudson.scm.subversion.UpdateWithRevertUpdater')
}
}
}
}
}

_

Before your hint I tried following line instead of your suggestion:
 svnNode / workspaceUpdater(class:'hudson.scm.subversion.UpdateWithRevertUpdater')

The above line did not work, but did also not result in any errormessage ... but it prevented every new/changed config.xml from saving.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [android-emulator] (JENKINS-17532) Creating separate jobs doesn't install system images

2013-04-09 Thread r...@stack.nl (JIRA)

Ruud Althuizen
created JENKINS-17532

Creating separate jobs doesnt install system images

Issue Type:

Bug

Assignee:

Christopher Orr

Components:

android-emulator

Created:

09/Apr/13 9:39 AM

Description:

For a project we have three separate jobs:
1. Installs the SDK and creates build files
2. Builds the s/w
3. Builds the tests, starts an emulator and executes tests

The problem that I run into is that the system images aren't installed. After some experimentation I figured out the following: The "Install Android project prerequisites" build step only installs system images when the job also has an fully configured emulator enabled.

Adding an "Install Android project prerequisites" build step in the same job (third) as the which holds the emulator configuration, the system images won't be installed. In this instance it's only checked if the SDK is available, not if it also includes the system images.

Project:

Jenkins

Priority:

Major

Reporter:

Ruud Althuizen

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [m2release] (JENKINS-12076) m2 Release Plugin lock builds















































SCM/JIRA link daemon
 commented on  JENKINS-12076


m2 Release Plugin lock builds















Code changed in jenkins
User: David Venable
Path:
 src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper.java
http://jenkins-ci.org/commit/m2release-plugin/456179363429f366e3bacc28bd8290986aae7a0b
Log:
  FIXED JENKINS-12076 The build parameter for the number of release builds to keep was not being saved and thus not used.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [m2release] (JENKINS-12076) m2 Release Plugin lock builds















































SCM/JIRA link daemon
 commented on  JENKINS-12076


m2 Release Plugin lock builds















Code changed in jenkins
User: jtnord
Path:
 src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper.java
http://jenkins-ci.org/commit/m2release-plugin/a46f076df1c2cbcbb6d2577e27053148644f714c
Log:
  Merge pull request #10 from dlvenable/fix-number-of-releases-to-keep

FIXED JENKINS-12076 Correctly save "number of release builds to keep" parameter


Compare: https://github.com/jenkinsci/m2release-plugin/compare/2e22caafe9cb...a46f076df1c2




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [android-emulator] (JENKINS-17532) Creating separate jobs doesn't install system images















































Christopher Orr
 commented on  JENKINS-17532


Creating separate jobs doesnt install system images















Hmm, I think I did this intentionally.

People may want to just build APKs without then starting an emulator, so it's a waste of time and bandwidth to download the system images unnecessarily when just using the "install prerequisites" step.

In your third build, if you do not use the "install prerequisites" step, but do start an emulator, are the system images not automatically downloaded?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [ansicolor] (JENKINS-11752) ANSI color plugin adds garbage to log

2013-04-09 Thread pjlby...@gmail.com (JIRA)















































Patrick Byrne
 commented on  JENKINS-11752


ANSI color plugin adds garbage to log















This affects us at the moment.

Jenkins ver 1.508
ANSIColor 0.31

It makes our log files 1000x larger - this is ridiculous!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [nested-view] (JENKINS-6961) Add the possibility to move existing views to a nested view.

2013-04-09 Thread a-he...@smacl.fr (JIRA)















































Anthony HERBÉ
 commented on  JENKINS-6961


Add the possibility to move existing views to a nested view.















Any clue to accomplish this without GUI at this time ?
I agree too. GUI for this would be very nice.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [android-emulator] (JENKINS-16392) Hardware properties like hw.ramSize and vm.heapSize should be set in hardware-qemu.ini instead of config.ini for newer Android SDKs

2013-04-09 Thread u...@kubosch.no (JIRA)















































Uwe Kubosch
 commented on  JENKINS-16392


Hardware properties like hw.ramSize and vm.heapSize should be set in hardware-qemu.ini instead of config.ini for newer Android SDKs















Not so sure anymore.  This may have been with an older Android SDK.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [android-emulator] (JENKINS-17532) Creating separate jobs doesn't install system images

2013-04-09 Thread r...@stack.nl (JIRA)















































Ruud Althuizen
 commented on  JENKINS-17532


Creating separate jobs doesnt install system images















It does not. I get this output:


Building in workspace /var/lib/jenkins/jobs/test_install_sdk_emu/workspace
$ /var/lib/jenkins/tools/android-sdk/tools/android list target
[android] Using Android SDK: /var/lib/jenkins/tools/android-sdk
[android] Creating Android AVD: /var/lib/jenkins/.android/avd/hudson_en-US_330_1280x768_android-17_armeabi-v7a.avd
[android] /var/lib/jenkins/tools/android-sdk/tools/android create avd -f -a -s 1280x768 -n hudson_en-US_330_1280x768_android-17_armeabi-v7a -t android-17 --abi armeabi-v7a
	Error: Unable to find a 'userdata.img' file for ABI armeabi-v7a to copy into the AVD folder.
	
[android] Could not create Android emulator: Failed to run AVD creation command
Finished: NOT_BUILT





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [android-emulator] (JENKINS-17532) Creating separate jobs doesn't install system images

2013-04-09 Thread r...@stack.nl (JIRA)













































 
Ruud Althuizen
 edited a comment on  JENKINS-17532


Creating separate jobs doesnt install system images
















It does not. I get this output:


Building in workspace /var/lib/jenkins/jobs/test_install_sdk_emu/workspace
$ /var/lib/jenkins/tools/android-sdk/tools/android list target
[android] Using Android SDK: /var/lib/jenkins/tools/android-sdk
[android] Creating Android AVD: /var/lib/jenkins/.android/avd/hudson_en-US_330_1280x768_android-17_armeabi-v7a.avd
[android] /var/lib/jenkins/tools/android-sdk/tools/android create avd -f -a -s 1280x768 -n hudson_en-US_330_1280x768_android-17_armeabi-v7a -t android-17 --abi armeabi-v7a
	Error: Unable to find a 'userdata.img' file for ABI armeabi-v7a to copy into the AVD folder.
	
[android] Could not create Android emulator: Failed to run AVD creation command
Finished: NOT_BUILT



This test job only has an emulator configured, nothing else.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [parameterized-trigger] (JENKINS-8916) Allowing same type of parameter for triggered build more than once seems redundant

2013-04-09 Thread jlpinar...@java.net (JIRA)















































jlpinardon
 commented on  JENKINS-8916


Allowing same type of parameter for triggered build more than once seems redundant















Dear all,

I support several teams for which it is really annoying to not be able to add several property files.
So please could you either :

	let the possibility to add several times property file type
	or have a single property file type but allow to give a comma separated list of files.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [android-emulator] (JENKINS-17532) Creating separate jobs doesn't install system images















































Christopher Orr
 commented on  JENKINS-17532


Creating separate jobs doesnt install system images















Thanks for the info. I'll take a look.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [xunit] (JENKINS-17491) xUnit v1.52 fails with ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception

2013-04-09 Thread pedro.r...@mog-solutions.com (JIRA)
















































pedro reis
 resolved  JENKINS-17491 as Not A Defect


xUnit v1.52 fails with ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception
















Problem must be at Java 1.6.0.11





Change By:


pedro reis
(09/Apr/13 10:34 AM)




Status:


Open
Resolved





Fix Version/s:


current





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] [xunit] (JENKINS-17491) xUnit v1.52 fails with ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception

2013-04-09 Thread pedro.r...@mog-solutions.com (JIRA)















































pedro reis
 commented on  JENKINS-17491


xUnit v1.52 fails with ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception















Thanks Gregory!

The problem was solved updating Java (JRE and JDK), and reinstalling Jenkins service at the slave. (Don't know if a restart of the Jenkins service would also do the trick)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [cvs] (JENKINS-17533) Jenkins 1.510 deletes all CVS branch checkout files

2013-04-09 Thread abhishek.chik...@gmail.com (JIRA)















































Abhishek Chikane
 created  JENKINS-17533


Jenkins 1.510 deletes all CVS branch checkout files















Issue Type:


Bug



Assignee:


Unassigned


Components:


cvs



Created:


09/Apr/13 10:34 AM



Description:


I am using Jenkins, 1.510.

It working well with all CVS checkout from head.

However if I use checkout from branch, it checks out all files successfully shows the message as successfully checked out. But the checkouted directory contains nothing. When I checked the files while the build is in progress the files are copied to directory however at end of build all the files are getting deleted.

Can you please help me?




Project:


Jenkins



Priority:


Major



Reporter:


Abhishek Chikane

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [maven] (JENKINS-17534) Maven modules view not showing last successful build

2013-04-09 Thread joris.dewi...@gmail.com (JIRA)















































Joris De Winne
 created  JENKINS-17534


Maven modules view not showing last successful build















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


example.png



Components:


maven



Created:


09/Apr/13 11:07 AM



Description:


When looking at the Modules page of a maven project I see that the last successful modules are at build number 425 (1 month ago), while the build history (panel on the left side) shows that last successful build is 440.

Restarting Jenkins did not help.




Environment:


Jenkins 1.510 (and previous)

Running within tomcat on linux environment with multiple slaves




Project:


Jenkins



Priority:


Major



Reporter:


Joris De Winne

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-multijob-plugin] (JENKINS-17535) Provide env vars detailing triggered builds

2013-04-09 Thread ki...@java.net (JIRA)















































kiall
 created  JENKINS-17535


Provide env vars detailing triggered builds















Issue Type:


New Feature



Assignee:


Unassigned


Components:


jenkins-multijob-plugin



Created:


09/Apr/13 11:07 AM



Description:


Providing env vars similar to the Param Trigger Plugin would allow for more complex chains to be build.

See https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin#ParameterizedTriggerPlugin-UsageasaBuildstep




Project:


Jenkins



Priority:


Major



Reporter:


kiall

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [subversion] (JENKINS-16736) SVN triggers build without any SCM change

2013-04-09 Thread 1990.a...@gmail.com (JIRA)















































Alex Vesely
 commented on  JENKINS-16736


SVN triggers build without any SCM change















The "Manage nodes" screen lists all slaves as "In sync".



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.

2013-04-09 Thread jenk...@gcummings.com (JIRA)















































Geoff Cummings
 commented on  JENKINS-17508


The Discard Old Builds advanced option - removal of only artifacts - does not work for me after 1.503.
















Wondering if it's related to this change:

What's new in 1.503 (2013/02/26)

	"Discard old build records" behavior is now pluggable, allowing plugins to define custom logic.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [ec2] (JENKINS-17536) Workspace environment variable is relative on ec2 slave

2013-04-09 Thread jenk...@sjonny.dyndns.org (JIRA)















































John van der Kamp
 created  JENKINS-17536


Workspace environment variable is relative on ec2 slave















Issue Type:


Bug



Affects Versions:


current



Assignee:


Francis Upton



Components:


ec2



Created:


09/Apr/13 11:32 AM



Description:


The WORKSPACE environment variable is inconsistent with normal slaves in Jenkins.
Normal slave:
{
WORKSPACE=/home/jenkins/workspace/job_name
}
EC2 slave:
{
WORKSPACE=workspace/job_name
}

Please make it the same as normal slaves.




Environment:


Jenkins 1.479, EC2 plugin 1.17




Project:


Jenkins



Priority:


Major



Reporter:


John van der Kamp

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [maven] (JENKINS-13390) Build whenever a SNAPSHOT dependency is built doesn't work for some builds without any reason.

2013-04-09 Thread ever...@free.fr (JIRA)















































evernat
 commented on  JENKINS-13390


Build whenever a SNAPSHOT dependency is built doesnt work for some builds without any reason.















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-multijob-plugin] (JENKINS-17535) Provide env vars detailing triggered builds

2013-04-09 Thread ki...@java.net (JIRA)















































kiall
 commented on  JENKINS-17535


Provide env vars detailing triggered builds















Pull request @ https://github.com/jenkinsci/tikal-multijob-plugin/pull/22



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [job-dsl-plugin] (JENKINS-17222) Add ability to specify more than one location when using the svn method

2013-04-09 Thread chmo...@eurofunk.com (JIRA)















































Christoph Moser
 commented on  JENKINS-17222


Add ability to specify more than one location when using the svn method















Hi - is it already possible to configure more than one location in some way?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [active-directory] (JENKINS-17537) An API Exception was caught! MKS124803: Internal error detected

2013-04-09 Thread irofte.io...@gmail.com (JIRA)















































ioana  irofte
 created  JENKINS-17537


An API Exception was caught! MKS124803: Internal error detected















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


active-directory



Created:


09/Apr/13 12:01 PM



Description:


I have two Jenkins Servers running  using the PTC MKS plug-in. Both servers show the following error in all build jobs:

Preparing to execute si projectinfo for #/XX/YY
An API Exception was caught!
MKS124803: Internal error detected: Exception was: java.lang.ArrayIndexOutOfBoundsException
si projectinfo --user= --port= --hostname= --project=#/XX/YY  returned exit code 125
Retrying after 10 seconds

Which could be the problem here?

Thank you!




Due Date:


10/Apr/13 12:00 AM




Environment:


Windows 7




Fix Versions:


current



Project:


Jenkins



Priority:


Major



Reporter:


ioana  irofte

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.

2013-04-09 Thread pjl...@combitel.no (JIRA)















































Per J. Lund
 commented on  JENKINS-17508


The Discard Old Builds advanced option - removal of only artifacts - does not work for me after 1.503.















Yes, it is related to that change.
Unfortunately I don't have the insight to fix the problem, because it is causing us full disks...



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [ec2] (JENKINS-17536) Workspace environment variable is relative on ec2 slave

2013-04-09 Thread jenk...@sjonny.dyndns.org (JIRA)















































John van der Kamp
 updated  JENKINS-17536


Workspace environment variable is relative on ec2 slave
















Change By:


John van der Kamp
(09/Apr/13 1:07 PM)




Environment:


Jenkins1.
479
495
,EC2plugin1.17



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [subversion] (JENKINS-16533) Jobs checked out from svn with pinned externals continuously run (with no changes in svn)















































Chris Z
 commented on  JENKINS-16533


Jobs checked out from svn with pinned externals continuously run (with no changes in svn)















Can someone create test case ? I tried to recreate this issue but everything seems to work fine. 

My test, jenkins 1.509, subversion 1.6 externals to file, svn plugin 1.45(1.46) on windows:
pooling set on: /svn/test_repo/plugin/trunk
and there I have pinned external
/svn/test_repo/plugin/branches/test_external@6 here

And in revision.txt I have: 

svn/test_repo/plugin/trunk/17
svn/test_repo/plugin/branches/test_external/6:



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [subversion] (JENKINS-16533) Jobs checked out from svn with pinned externals continuously run (with no changes in svn)













































 
Chris Z
 edited a comment on  JENKINS-16533


Jobs checked out from svn with pinned externals continuously run (with no changes in svn)
















Can someone create test case ? I tried to recreate this issue but everything seems to work fine. 

My test, jenkins 1.509, subversion 1.6 externals to file, svn plugin 1.45(1.46) on windows:
pooling set on: /svn/test_repo/plugin/trunk
and there I have pinned external
/svn/test_repo/plugin/branches/test_external@6 here

And in revision.txt I have: 

svn/test_repo/plugin/trunk/17
svn/test_repo/plugin/branches/test_external/6::p




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [copyartifact] (JENKINS-17538) When artifact is copied, add an Action to track the build this artifact has been copied for

2013-04-09 Thread nicolas.del...@gmail.com (JIRA)















































Nicolas De Loof
 created  JENKINS-17538


When artifact is copied, add an Action to track the build this artifact has been copied for















Issue Type:


Improvement



Assignee:


Nicolas De Loof



Components:


copyartifact



Created:


09/Apr/13 1:15 PM



Description:


fingerprint can be used to track the build that created same artifact used by copyartifact, anyway it can integrate more than one build (subsequent builds may produce the same artifact). An action added to the current build to track the artifact source could help to track builds relations.




Project:


Jenkins



Priority:


Minor



Reporter:


Nicolas De Loof

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online

2013-04-09 Thread yora...@tikalk.com (JIRA)















































Yoram Michaeli
 reopened  JENKINS-17519


After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online 
















Happens to me as well (Master on Linux). No downgrade of SSH plugin or jenkins.war help in any way!





Change By:


Yoram Michaeli
(09/Apr/13 1:24 PM)




Resolution:


NotADefect





Status:


Closed
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] [grails] (JENKINS-10266) Set grails.work.dir to something unique by default

2013-04-09 Thread agander...@cantab.net (JIRA)













































 
Alex Anderson
 edited a comment on  JENKINS-10266


Set grails.work.dir to something unique by default
















Available here: https://github.com/jenkinsci/grails-plugin/pull/3 (mixed with another pull request, fixing JENKINS-8535 - will happily separate if required).




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online

2013-04-09 Thread yora...@tikalk.com (JIRA)















































Yoram Michaeli
 updated  JENKINS-17519


After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online 
















Change By:


Yoram Michaeli
(09/Apr/13 1:32 PM)




Priority:


Blocker
Critical



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online

2013-04-09 Thread steve_hawo...@xyratex.com (JIRA)















































Steve Haworth
 commented on  JENKINS-17519


After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online 















The install tries to resolve your existing SSH credentials by making entries in in Manage Jenkins\Manage Credentials.
In my case it got it wrong by assuming I was using a Private Key.
So I deleted all the erroneous entries and added an authentication using user and password, I then selected this credential in the node and it worked.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online

2013-04-09 Thread yora...@tikalk.com (JIRA)















































Yoram Michaeli
 commented on  JENKINS-17519


After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online 















Problem overcome using a workaround: setting user/password to a local server user instead of the default (leaving the user/password setting empty so it uses a special jenkins account) - seems something has been changed reguarding the jenkins local 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] [github-oauth] (JENKINS-17539) Swarm clients fail to connect if GitHub for authentication

2013-04-09 Thread kofem...@java.net (JIRA)















































kofemann
 created  JENKINS-17539


Swarm clients fail to connect if GitHub for authentication















Issue Type:


Bug



Affects Versions:


current



Assignee:


Sam Kottler



Components:


github-oauth, swarm



Created:


09/Apr/13 1:36 PM



Description:


We use swarm plugin to manage slaves. No we decided to use github-oauth2 and cant get slaves to work with it, 




Project:


Jenkins



Labels:


plugin




Priority:


Major



Reporter:


kofemann

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [cppcheck] (JENKINS-17540) ConversionException reading build.xml

2013-04-09 Thread ja...@howeswho.co.uk (JIRA)















































James Howe
 created  JENKINS-17540


ConversionException reading build.xml















Issue Type:


Bug



Assignee:


Gregory Boissinot



Attachments:


build_xml_snippet.txt, stacktrace.txt



Components:


cppcheck



Created:


09/Apr/13 1:37 PM



Description:


It seems every time a build with cppcheck results is loaded, an exception following the pattern of the attached stacktrace is logged.

Also attached is a snippet of build.xml around the line indicated.




Environment:


Jenkins 1.510

Cppcheck plugin 1.13




Project:


Jenkins



Priority:


Major



Reporter:


James Howe

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [subversion] (JENKINS-16533) Jobs checked out from svn with pinned externals continuously run (with no changes in svn)

2013-04-09 Thread emil.sty...@gmail.com (JIRA)















































Emil Styrke
 commented on  JENKINS-16533


Jobs checked out from svn with pinned externals continuously run (with no changes in svn)















I can't speak for the reporter, but at least for me this happens not with peg revisions, but with a specified operational revision, as in:


-r 1234 http://svn/repo/some/external here


I don't really want to try to reproduce this here as I only have a live Jenkins environment to try on.  If necessary I can try to set up a lab instance though.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [jacoco] (JENKINS-16786) Please make the N/A white, not black. :-)

2013-04-09 Thread andrea.gual...@imavis.com (JIRA)















































Andrea Gualano
 commented on  JENKINS-16786


Please make the N/A white, not black. :-)















My problem exactly. I have only one job using Jacoco at the moment out of about 100 projects (many of them not using Java at all).
It is nice to be able to add the coverage column to a specific view, but I would not want it in the "All" view.
It should be possible to disable the coverage column from the main view; otherwise it should only be available in the other views, whose columns are editable.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [android-emulator] (JENKINS-13648) Automatic Support for Intel® Hardware Accelerated Execution Manager
















































Christopher Orr
 closed  JENKINS-13648 as Wont Fix


Automatic Support for Intel® Hardware Accelerated Execution Manager
















This requires running a graphical installer, which has multiple steps and requires admin privileges. By default it also causes a kernel panic on OS X 10.8 unless you download an additional hotfix...

This should be done manually on systems which require it.





Change By:


Christopher Orr
(09/Apr/13 1:57 PM)




Status:


Open
Closed





Resolution:


WontFix



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [subversion] (JENKINS-16736) SVN triggers build without any SCM change

2013-04-09 Thread ku...@gmx.de (JIRA)















































kutzi
 commented on  JENKINS-16736


SVN triggers build without any SCM change















That's not quite what I asked. I wanted to know if your subversion server is in sync with your Jenkins nodes.
Maybe your subversion server is also on (one of your) Jenkins machines, but I don't know that.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [plugin] (JENKINS-17528) Discard Old Builds plugin throws java.lang.UnsupportedOperationException

2013-04-09 Thread jgl...@cloudbees.com (JIRA)
















































Jesse Glick
 assigned  JENKINS-17528 to nkns165



Discard Old Builds plugin throws java.lang.UnsupportedOperationException 
















Change By:


Jesse Glick
(09/Apr/13 2:21 PM)




Assignee:


nkns165



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [discard-old-build] (JENKINS-17528) Discard Old Builds plugin throws java.lang.UnsupportedOperationException

2013-04-09 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 updated  JENKINS-17528


Discard Old Builds plugin throws java.lang.UnsupportedOperationException 
















Change By:


Jesse Glick
(09/Apr/13 2:24 PM)




Affects Version/s:


current





Component/s:


discard-old-build





Component/s:


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] [discard-old-build] (JENKINS-17528) Discard Old Builds plugin throws java.lang.UnsupportedOperationException

2013-04-09 Thread jgl...@cloudbees.com (JIRA)
















































Jesse Glick
 resolved  JENKINS-17528 as Fixed


Discard Old Builds plugin throws java.lang.UnsupportedOperationException 
















Seems to be fixed in 1.03 by https://github.com/jenkinsci/discard-old-build-plugin/commit/04aab74b161919db790ccee4f7ff0b897107663c I guess.





Change By:


Jesse Glick
(09/Apr/13 2:22 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] [xcode] (JENKINS-13886) Settings in Configure System are reset when the server is reset
















































Christopher Orr
 resolved  JENKINS-13886 as Fixed


Settings in Configure System are reset when the server is reset
















Fixed by https://jenkins-ci.org/commit/xcode-plugin/fd0816eeda





Change By:


Christopher Orr
(09/Apr/13 2:58 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] [subversion] (JENKINS-16533) Jobs checked out from svn with pinned externals continuously run (with no changes in svn)















































Chris Z
 commented on  JENKINS-16533


Jobs checked out from svn with pinned externals continuously run (with no changes in svn)















Ok with this indeed it's running continuously. I will check this. And that 6209 test.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [subversion] (JENKINS-16865) SVN fail to revert working dir : NullPointerException















































Chris Z
 commented on  JENKINS-16865


SVN fail to revert working dir : NullPointerException















Which SVN version you have set in Jenkins ? 1.6 or 1.7 ?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [analysis-core] (JENKINS-17542) Decrease thresholds after builds automatically

2013-04-09 Thread johannes.hu...@hmmh.de (JIRA)

Johannes Huber
created JENKINS-17542

Decrease thresholds after builds automatically

Issue Type:

New Feature

Affects Versions:

current

Assignee:

Ulli Hafner

Components:

analysis-core

Created:

09/Apr/13 3:20 PM

Description:

We want to decrease thresholds with an offset after builds automatically. This enforces the source code quality. The offset should be configurable.

For example: We have 50 FindBugs warnings before the build, high priority warnings of 60 and a offset of 10. After the build there are just 45 FindBugs warnings, the new threshold should be 55.

Our solution would be to add an input field for each priority and level. The problem is that we had to extend analysis-core constructor with many new parameters and all depending plugins too...

We are thankful for any better solution and suggestions. Hopfully you like the idea, in that case we would try to implement the feature and will share the solution as well.

Code name "thumbscrew"

Project:

Jenkins

Priority:

Minor

Reporter:

Johannes Huber

[JIRA] [analysis-core] (JENKINS-17542) Decrease thresholds after builds automatically

2013-04-09 Thread johannes.hu...@hmmh.de (JIRA)















































Johannes Huber
 updated  JENKINS-17542


Decrease thresholds after builds automatically
















Change By:


Johannes Huber
(09/Apr/13 3:20 PM)




Description:


Wewanttodecreasethresholdswithanoffsetafterbuildsautomatically.Thisenforcesthesourcecodequality.Theoffsetshouldbeconfigurable.Forexample:Wehave50FindBugswarningsbeforethebuild,highprioritywarningsof60andaoffsetof10.Afterthebuildtherearejust45FindBugswarnings,thenewthresholdshouldbe55.Oursolutionwouldbetoaddaninputfieldforeachpriorityandlevel.Theproblemisthatwehadtoextendanalysis-coreconstructorwithmanynewparametersandalldependingpluginstoo...Wearethankfulforanybettersolutionandsuggestions.Hopfullyyouliketheidea,inthatcasewewouldtrytoimplementthefeatureand
we
willsharethesolutionaswell.Codenamethumbscrew;-)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [subversion] (JENKINS-16736) SVN triggers build without any SCM change

2013-04-09 Thread 1990.a...@gmail.com (JIRA)















































Alex Vesely
 commented on  JENKINS-16736


SVN triggers build without any SCM change















... Sorry, it turns out I wasn't quite well-informed about that specific SVN trunk setup, so I failed to describe the most important detail. 
The externals in question appeared to be bound to a specific SVN revision (not HEAD). This is what was different in this specific job.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [maven] (JENKINS-17543) maven plugin fails to terminate (submodule build), when permgen runs out of memory

2013-04-09 Thread riteofw...@gmail.com (JIRA)















































Mark Lemay
 created  JENKINS-17543


maven plugin fails to terminate (submodule build), when permgen runs out of memory















Issue Type:


Bug



Assignee:


Unassigned


Components:


maven



Created:


09/Apr/13 3:48 PM



Description:


Sub module projects do not terminate, they run forever in a hanging state.

for instance when you mouse over the jobs load bar (in the module), "started null ago" "estimated remaining time: null"

thanks

console output:

INFO pmd:pmd {execution: default-cli}
WARNING Unable to locate Source XRef to link to - DISABLED
WARNING File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent!
INFO 
ERROR FATAL ERROR
INFO 
Apr 8, 2013 3:55:23 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run
SEVERE: Unexpected error in channel channel
java.lang.OutOfMemoryError: PermGen space
channel stopped
Exception in thread "Channel reader thread: channel" java.lang.OutOfMemoryError: PermGen space
Terminating xvnc.
$ /usr/bin/vncserver -kill :2
Killing Xvnc process ID 3769
Build was aborted
Finished: ABORTED




Environment:


versions:

maven-plugin	1.510

Jenkins ver. 1.510






Project:


Jenkins



Priority:


Major



Reporter:


Mark Lemay

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [testlink] (JENKINS-16898) Testlink plugin exception setting status with TestNG Result Seeker

2013-04-09 Thread jrodg...@vbridges.com (JIRA)















































Jeff Rodgers
 commented on  JENKINS-16898


Testlink plugin exception setting status with TestNG Result Seeker















I'm beginning to think something may have gone wrong in upgrading from 1.9.3 - 1.9.4 - 1.9.5. I'm going to try this with a clean install. BTW, I am only using the test project from your tutorial "Jenkins TestLink Plug-in Tutorial" at https://github.com/tupilabs/jenkins-testlink-plugin-tutorial so I would assume that would suffice as an example.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [promoted-builds] (JENKINS-17544) Promoted Build Plugin shows 404 on promotion log.

2013-04-09 Thread pres...@gilchrist.org (JIRA)

Preston Gilchrist
created JENKINS-17544

Promoted Build Plugin shows 404 on promotion log.

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Components:

promoted-builds

Created:

09/Apr/13 4:03 PM

Description:

Upon a restart of Jenkins, all data related to the promoted build plugin displays correctly. After Jenkins has been up for a period of time (usually 30 minutes to 1 hour), data will start to display incorrectly. Examples:

1. If a promotion failed, the icon in the Build History area will show a normal promotion star as opposed to the failed promotion icon.
2. In the "Promotion Status", all promotions will show as "No build promoted so far." despite the fact that there are multiple promotions.
3. After drilling into a specific build, and clicking on "Promotion Status", no details are shown in the "Promotion History" and if your click on the "log" link, you receive a "Status Code: 404" error without a stacktrace or exception.

If Jenkins is restarted, all of the above examples will display correctly again for a limited amount of time before reverting back to the incorrect behavior.

Environment:

Windows 2008

Jenkins 1.510

Run under Winstone/Windows Service

Promoted Build Plugin 2.10

Project Based Security Matrix

Active Directory Authentication and Group ACLs

Project:

Jenkins

Priority:

Minor

Reporter:

Preston Gilchrist

[JIRA] [scm-sync-configuration] (JENKINS-17545) A new default include creates unwanted commits (without config changes).

2013-04-09 Thread jo...@yahoo.com (JIRA)

Nemoo
created JENKINS-17545

A new default include creates unwanted commits (without config changes).

Issue Type:

Bug

Affects Versions:

current

Assignee:

Frédéric Camblor

Components:

scm-sync-configuration

Created:

09/Apr/13 4:09 PM

Description:

The jenkins scm sync plugin has been rendered quite useless for us since about 4 months because it creates loads of commits that are not related to configuration changes.
They commits look like this: "Job *jobname* configuration updated by SYSTEM"

The culprit is one of the default includes (Let me quote from the configuration page):

Following includes are brought "out of the box" by scm-sync-configuration default includes :
config.xml
hudson*.xml
scm-sync-configuration.xml
jobs/*/config.xml
-

This include: jobs/*/config.xml monitors all config.xml files in our project for changes and commits them to svn.

Obviously this is not very helpful and can be considered pretty intrusive.
It would be nice if this entry could be removed from the default includes or ignored easily.

The affected config file starts like this:
?xml version='1.0' encoding='UTF-8'?
maven2-module-set plugin="maven-plugin@1.498"
keepDependenciesfalse/keepDependencies
...

It contains lots of data of the maven pom(s) of the source that is built by the job. To save these changes in the poms in svn is beside the scope of the scm plugin. That is what we have version control for.

I did not find a way to override this predefined include. But maybe there is a way or maybe it should be removed.

Environment:

centos

Project:

Jenkins

Priority:

Major

Reporter:

Nemoo

[JIRA] [android-emulator] (JENKINS-13943) java 7 support to build plugin
















































Christopher Orr
 resolved  JENKINS-13943 as Fixed


java 7 support to build plugin
















I moved the Jenkins dependency to 1.466 and now the plugin builds with Java 7.





Change By:


Christopher Orr
(09/Apr/13 4:20 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] [scm-sync-configuration] (JENKINS-17545) A new default include creates unwanted commits (without config changes).

2013-04-09 Thread fcamb...@java.net (JIRA)















































Frédéric Camblor
 commented on  JENKINS-17545


A new default include creates unwanted commits (without config changes).















I understand your problem, but looking at source code I don't see where problem resides.
Could you be more precise and provide path of unwanted commited files ?

In fact, I rely on DirectoryScanner for file-to-commit inclusion.
Regarding javadoc of this class, providing an include pattern of "jobs/*/config.xml" should only commit config.xml files located in root directory (only!) of every jobs.
If this is not the case, this is not the intended behaviour and should be considered as a bug.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [core] (JENKINS-17110) Hover-over Build Now broken for parameterized jobs: This page expects a form submission
















































SCM/JIRA link daemon
 resolved  JENKINS-17110 as Fixed


Hover-over Build Now broken for parameterized jobs: This page expects a form submission
















Change By:


SCM/JIRA link daemon
(09/Apr/13 4:59 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] [core] (JENKINS-17110) Hover-over Build Now broken for parameterized jobs: This page expects a form submission















































SCM/JIRA link daemon
 commented on  JENKINS-17110


Hover-over Build Now broken for parameterized jobs: This page expects a form submission















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/resources/hudson/model/AbstractProject/sidepanel.jelly
http://jenkins-ci.org/commit/jenkins/97da1618c52792bd675f8677b7e18df629f80eb7
Log:
  FIXED JENKINS-17110 Build Now should be GET for parameterized jobs.






























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [subversion] (JENKINS-17431) 500 Internal Server Error on attempt to run a build

2013-04-09 Thread smasl...@visa.com (JIRA)

Slava Maslenitsyn
commented on JENKINS-17431

500 Internal Server Error on attempt to run a build

just FYI:
http://svnbook.red-bean.com/en/1.7/svn.tour.revs.specifiers.html

Since the timestamp of a revision is stored as an unversioned, modifiable property of the revision (see the section called “Properties”), revision timestamps can be changed to represent complete falsifications of true chronology, or even removed altogether. Subversion's ability to correctly convert revision dates into real revision numbers depends on revision datestamps maintaining a sequential ordering—the younger the revision, the younger its timestamp. If this ordering isn't maintained, you will likely find that trying to use dates to specify revision ranges in your repository doesn't always return the data you might have expected.

...and this... (on the same page)

Is Subversion a Day Early?

If you specify a single date as a revision without specifying a time of day (for example 2006-11-27), you may think that Subversion should give you the last revision that took place on the 27th of November. Instead, you'll get back a revision from the 26th, or even earlier. Remember that Subversion will find the most recent revision of the repository as of the date you give. If you give a date without a timestamp, such as 2006-11-27, Subversion assumes a time of 00:00:00, so looking for the most recent revision won't return anything on the 27th.

If you want to include the 27th in your search, you can either specify the 27th with the time ({"2006-11-27 23:59"}), or just specify the next day ({2006-11-28}).

so, I believe, using time/date stamps is not the best and most reliable approach to make a decision for a build nor it will correctly update your working space.

regards,
Slava

[JIRA] [scm-sync-configuration] (JENKINS-17545) A new default include creates unwanted commits (without config changes).

2013-04-09 Thread jo...@yahoo.com (JIRA)















































Nemoo
 commented on  JENKINS-17545


A new default include creates unwanted commits (without config changes).















Sure, the path for the unwanted commited files is: 
/jenkinsConfiguration/jenkinsServer/jobs/job-A/modules/com.example.myapp$myapp/config.xml



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [core] (JENKINS-10738) Different build now for parameterized builds















































SCM/JIRA link daemon
 commented on  JENKINS-10738


Different build now for parameterized builds















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/model/AbstractProject.java
 core/src/main/resources/hudson/model/Messages.properties
 core/src/main/resources/hudson/views/BuildButtonColumn/column.jelly
http://jenkins-ci.org/commit/jenkins/b22b17c0d68c95bece46818fbf9ef562902b10c1
Log:
  FIXED JENKINS-10738 Different "build now" text for parameterized builds.
(Not touching the icon since I do not feel like playing with Inkscape; would be a nice pull request for somebody.)






























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [core] (JENKINS-10738) Different build now for parameterized builds