date:20130124















































Jesse Glick
 commented on  JENKINS-16476


Add "Last Completed Build" to permalink list















lastSuccessfulBuild is what you want in this case.



























This message is automatically generated by JIRA.
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] (JENKINS-16009) Unable to launch cocoa application through post build script















































Sami Tikka
 commented on  JENKINS-16009


Unable to launch cocoa application through post build script















The standard Jenkins Mac installer sets up a launch daemon to run Jenkins in a system context where it has no access to the graphical display. Thus anything launched by Jenkins is unable to open windows or draw on the screen.

If that is really necessary, the user must 


sudo launchctl unload /Library/LaunchDaemons/org.jenkins-ci.plist



and then move the file into ~/Library/LaunchAgents of a real user who logs in and creates a graphical session. Also the plist file might need a couple of changes... or use https://github.com/stisti/jenkins-app

I would close this ticket but as it is owned by someone else, I'll leave the decision to him.



























This message is automatically generated by JIRA.
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] (JENKINS-15906) Jenkins Xcode Plugin Packing .ipa file Fail
















































Sami Tikka
 resolved  JENKINS-15906 as Won't Fix


Jenkins Xcode Plugin Packing .ipa file Fail
















Does not appear to be a bug in Jenkins but a side-effect of the way user runs Jenkins.





Change By:


Sami Tikka
(24/Jan/13 11:04 PM)




Status:


Open
Resolved





Resolution:


Won't Fix



























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

[JIRA] (JENKINS-15906) Jenkins Xcode Plugin Packing .ipa file Fail















































Sami Tikka
 commented on  JENKINS-15906


Jenkins Xcode Plugin Packing .ipa file Fail















A guess: Check what is the value of LANG environment variable in your shell where the build works. Set LANG to the same value in your build script.

If Jenkins is started as a launch daemon, the environment not set up similarly to the environment of a full user login environment.

I do not consider this a bug in Jenkins. I'm closing this ticket now.

If you did in fact run Jenkins inside a logged-in user session, please re-open this ticket and provide more information on how Jenkins is installed and run.



























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

[JIRA] (JENKINS-14112) The execution (build) of Project will fail on "mkdir" on remote disk.















































Sami Tikka
 commented on  JENKINS-14112


The execution (build) of Project will fail on "mkdir" on remote disk.















I would close this ticket as invalid. This is not a bug in Jenkins but a feature of Windows remote 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

[JIRA] (JENKINS-15256) Unable to launch slave agent via SSH due to OutOfMemoryError















































Sami Tikka
 commented on  JENKINS-15256


Unable to launch slave agent via SSH due to OutOfMemoryError















I would close this ticket but as it is owned by Kohsuke, maybe the decision should be his.



























This message is automatically generated by JIRA.
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] (JENKINS-15256) Unable to launch slave agent via SSH due to OutOfMemoryError















































Sami Tikka
 commented on  JENKINS-15256


Unable to launch slave agent via SSH due to OutOfMemoryError















"java.lang.OutOfMemoryError: PermGen space" suggests the memory pool where classes are loaded in jvm has run out of memory. I do not think there is anything Jenkins can do about it. This can happen if you install a lot of plugins, for example. You can increase the size of that pool by adding this to the java command line:


-XX:MaxPermSize=512m



Of course, 512 megabytes might not be enough. Keep incrementing it until it works or use fewer plugins.



























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

[JIRA] (JENKINS-16472) Add IBM XL C parser to Warnings plugin

2013-01-24 Thread johno.crawf...@gmail.com (JIRA)
















































Johno Crawford
 closed  JENKINS-16472 as Fixed


Add IBM XL C parser to Warnings plugin
















warnings-plugin 4.20 should be available soon.





Change By:


Johno Crawford
(24/Jan/13 10:44 PM)




Status:


Resolved
Closed



























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

[JIRA] (JENKINS-16289) Please bundle uninstaller with Jenkins Mac install

2013-01-24 Thread stephen.morri...@intecbilling.com (JIRA)
















































Sami Tikka
 resolved  JENKINS-16289 as Fixed


Please bundle uninstaller with Jenkins Mac install
















The Mac version of Jenkins comes with an uninstaller. You can find it in folder /Library/Application Support/Jenkins. I admit it is a fairly new addition and was added only 6 months ago.

Maybe the location of the uninstaller could be improved? I did consider placing it under /Applications/Jenkins but that isn't very usual for Mac software. Additionally, I used to make Mac software for a living and I had placed the uninstaller in the same directory with the application. Still, a frequently asked question in customer support was: "How do I uninstall this?"





Change By:


Sami Tikka
(24/Jan/13 10:43 PM)




Status:


Open
Resolved





Fix Version/s:


current





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

[JIRA] (JENKINS-16476) Add "Last Completed Build" to permalink list















































Stephen Morrison
 created  JENKINS-16476


Add "Last Completed Build" to permalink list















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Unassigned


Components:


copyartifact



Created:


24/Jan/13 10:37 PM



Description:


Would be useful to be able to select the "Last Completed Build" permalink.  I have a job where I want to get the artifacts from it whether it is unstable or stable, but this job can also run twice in quick succession.  If I use "Last Build", it just tries to get the artifacts from the newly running instance of the job rather than the one that just completed.




Project:


Jenkins



Priority:


Minor



Reporter:


Stephen Morrison

























This message is automatically generated by JIRA.
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] (JENKINS-15178) MacOS X package version does not output to logfile















































Sami Tikka
 commented on  JENKINS-15178


MacOS X package version does not output to logfile















Jenkins logs to stdout/stderr, and for launch daemons the default destination for those is the system log. You can access the system log either by using the Console.app or reading the file /var/log/system.log

This is the standard behavior on the Mac OS platform.

If the goal is to make Jenkins on Mac OS behave exactly like Jenkins on Linux, you must also include provide your own logrotate system. Unlike most Linux distress, Mac OS does not provide logrotate for log files other than /var/log/system.log.



























This message is automatically generated by JIRA.
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] (JENKINS-16472) Add IBM XL C parser to Warnings plugin















































SCM/JIRA link daemon
 commented on  JENKINS-16472


Add IBM XL C parser to Warnings plugin















Code changed in jenkins
User: Johno Crawford
Path:
 src/main/java/hudson/plugins/warnings/parser/XlcCompilerParser.java
 src/main/java/hudson/plugins/warnings/parser/XlcLinkerParser.java
 src/main/resources/hudson/plugins/warnings/parser/Messages.properties
 src/main/resources/hudson/plugins/warnings/parser/Messages_de.properties
 src/test/java/hudson/plugins/warnings/parser/ParserRegistryIntegrationTest.java
 src/test/java/hudson/plugins/warnings/parser/XlcLinkerParserTest.java
 src/test/java/hudson/plugins/warnings/parser/XlcParserTest.java
http://jenkins-ci.org/commit/warnings-plugin/33c29d3b010c4b8fb587a5a9624e6594d6bc53b2
Log:
  Merge pull request #14 from angvoz/JENKINS-16472-xlc-parser

[FIXED JENKINS-16472] Add IBM XL C parser to Warnings plugin.


Compare: https://github.com/jenkinsci/warnings-plugin/compare/34779fc5337b...33c29d3b010c




























This message is automatically generated by JIRA.
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] (JENKINS-16472) Add IBM XL C parser to Warnings plugin
















































SCM/JIRA link daemon
 resolved  JENKINS-16472 as Fixed


Add IBM XL C parser to Warnings plugin
















Change By:


SCM/JIRA link daemon
(24/Jan/13 10:33 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

[JIRA] (JENKINS-15674) Choosing strategy resets randomly from 'Gerrit Trigger' to 'Default'

2013-01-24 Thread aerick...@gmail.com (JIRA)















































Andrew Erickson
 commented on  JENKINS-15674


Choosing strategy resets randomly from 'Gerrit Trigger' to 'Default'















Currently on 1.499 with 1.1.25, but I haven't seen it happen in awhile (maybe I just haven't been editing my GerritTrigger jobs 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

[JIRA] (JENKINS-16475) Build stats graph configuration lost after Jenkins Restart

2013-01-24 Thread mstew...@riotgames.com (JIRA)















































Maxfield Stewart
 created  JENKINS-16475


Build stats graph configuration lost after Jenkins Restart















Issue Type:


Bug



Assignee:


Frédéric Camblor



Components:


global-build-stats



Created:


24/Jan/13 10:00 PM



Description:


Every time we restart jenkins we lose our configured Global build stats graphs.  It seems to me that these should persist between restart and I'm wondering if we've set something up wrong or if its a bug.

Running jenkins v1.484, global build stats plugin v1.3




Project:


Jenkins



Priority:


Major



Reporter:


Maxfield Stewart

























This message is automatically generated by JIRA.
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] (JENKINS-16474) jenkins v1.484 - Universally slow page load times/hangs

2013-01-24 Thread mstew...@riotgames.com (JIRA)

Maxfield Stewart
created JENKINS-16474

jenkins v1.484 - Universally slow page load times/hangs

Issue Type:

Bug

Assignee:

JulB4

Attachments:

threaddump.txt

Components:

jboss

Created:

24/Jan/13 9:58 PM

Description:

I'm looking for guidance on debugging slow page load times. Ever since we upgraded from 1.480 to 1.484 (and other versions beyond that) we've had very slow page load times. Sometimes upwards of 120 seconds to load a page, nearly any view tab, job configuration etc.

I've debugged many Java apps and I'm confounded. There are few, if any, Full GC's occuring, regular GC's occur somewhat frequently but take .02 or less seconds. CPU utilization for the java executeable is under %6 and and disk utilization is reasonable (we're averaging a %90+ idle time). The initial HTTP ack comes back immediately but then we wait for the page response to come back for up to 2 minutes sometimes. Othertimes it loads reasonably fast (under 4 seconds). When it's hanging, it's hanging for all requests, much like it was doing a full garbage collect. It feels like some kind of resource contention.

But I cannot find where the contention is, thread dumps look nominal (I've included one here for example). Something causes long page load times, we back revved to 1.484 thinking it had something to do with lazy loading features but clearly it does not. On 1.480 we did not have these issues. I could use some help figuring out what else to look at to identify why Jenkins is slow. There is a lack of information available on common reasons for slow page load times, this results in a terrible user experience with an otherwise fine tool.

Project:

Jenkins

Priority:

Major

Reporter:

Maxfield Stewart

This message is automatically generated by JIRA.
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] (JENKINS-15041) Proxy support

2013-01-24 Thread geoffrey.n.gre...@boeing.com (JIRA)















































Geoff Greene
 commented on  JENKINS-15041


Proxy support















Me too, me too.  I need proxy support too.

please!

Thanks

Geoff



























This message is automatically generated by JIRA.
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] (JENKINS-12950) pom.xml not deploying to Artifactory

2013-01-24 Thread rocketra...@gmail.com (JIRA)















































Raman Gupta
 commented on  JENKINS-12950


pom.xml not deploying to Artifactory















I have the same issue. I posted on the Artifactory mailing list (http://forums.jfrog.org/Jenkins-Artifactory-deploy-project-POM-in-multi-module-build-td7578470.html) but no response. I would actually be quite happy if "install" worked, but as Diane reported, using install does not work with 3.0.4.



























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

[JIRA] (JENKINS-16473) Build Pipeline View stops working after upgrading to Jenkins 1.499

2013-01-24 Thread lpu...@sproutloud.com (JIRA)















































Laurentius Purba
 created  JENKINS-16473


Build Pipeline View stops working after upgrading to Jenkins 1.499















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


build-pipeline



Created:


24/Jan/13 9:31 PM



Description:


After upgrading to Jenkins 1.499, and upgrading Build Pipeline plugin from version 1.2.3 to 1.3.3,  build-pipeline-plugin stops working.

Downgrading to version 1.2.3 fixed the issue.




Environment:


OS: FreeBSD 7.2

Jenkins: 1.499




Project:


Jenkins



Priority:


Major



Reporter:


Laurentius Purba

























This message is automatically generated by JIRA.
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] (JENKINS-16472) Add IBM XL C parser to Warnings plugin

2013-01-24 Thread angvoz....@gmail.com (JIRA)















































Andrew Gvozdev
 created  JENKINS-16472


Add IBM XL C parser to Warnings plugin















Issue Type:


Improvement



Assignee:


Ulli Hafner



Components:


warnings



Created:


24/Jan/13 9:17 PM



Description:


I would like to contribute a parser for IBM XL C compiler for AIX (C and C++). I will submit a pull request shortly. This is my first contribution to Warnings plugin and I would appreciate any guidance.




Project:


Jenkins



Priority:


Major



Reporter:


Andrew Gvozdev

























This message is automatically generated by JIRA.
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] (JENKINS-16471) Do not save config.xml of Maven modules

2013-01-24 Thread mfriedenha...@gmail.com (JIRA)
















































Mirko Friedenhagen
 assigned  JENKINS-16471 to Kathi Stutz



Do not save config.xml of Maven modules
















Kathi 





Change By:


Mirko Friedenhagen
(24/Jan/13 8:59 PM)




Assignee:


Mirko Friedenhagen
Kathi Stutz



























This message is automatically generated by JIRA.
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] (JENKINS-16468) Lock contention in executor queue















































SCM/JIRA link daemon
 commented on  JENKINS-16468


Lock contention in executor queue















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/897cab3f8d5584b2c43dc221db0e35ccaf155a72
Log:
  JENKINS-16468 Linking in changelog.
(cherry picked from commit 2f1ad0b2fbad9bb81ebbf1d0df08a24dcb3f0f16)

Conflicts:
	changelog.html





























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

[JIRA] (JENKINS-13536) File parameter causing data lost after Jenkins restart















































SCM/JIRA link daemon
 commented on  JENKINS-13536


File parameter causing data lost after Jenkins restart















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/model/FileParameterValue.java
http://jenkins-ci.org/commit/jenkins/5f7ad6e5feee4c70e2d13d68e80e086abf6a9f50
Log:
  [FIXED JENKINS-13536] Using file parameters could cause build records to not load.
Solves the issue for newly created builds by not attempting to persist the original file upload record, which is useless after the build has run (the fileParameters dir in the build already archives them).
Does not help loading pre-fix builds in which the upload temp file has been deleted; for these, you must manually delete … from the build.xml.
(Did not find a straightforward way to just instruct XStream to ignore this bit of XML: it is easy to avoid serializing a field, but deserializing is different.)(cherry picked from commit 4dde24e62037439b7b73addd7cefae83a254eb3c)

Conflicts:
	changelog.html


Compare: https://github.com/jenkinsci/jenkins/compare/8734bb733dc4...5f7ad6e5feee




























This message is automatically generated by JIRA.
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] (JENKINS-16468) Lock contention in executor queue















































SCM/JIRA link daemon
 commented on  JENKINS-16468


Lock contention in executor queue















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/2e3156dde4cf4e47db54d6fdc901146dc671d5cd
Log:
  JENKINS-16468 Marking as a bug, not an RFE.
(cherry picked from commit a156f1ebc610eae0e6e2316576d6f97a0180986b)

Conflicts:
	changelog.html





























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

[JIRA] (JENKINS-16069) Combobox component broken since 1.480















































SCM/JIRA link daemon
 commented on  JENKINS-16069


Combobox component broken since 1.480















Code changed in jenkins
User: Vincent Latombe
Path:
 changelog.html
 core/src/main/java/hudson/util/ComboBoxModel.java
http://jenkins-ci.org/commit/jenkins/580e7de701c923e5c97f94513f8672bf292e4972
Log:
  JENKINS-16069 Remove wrapping of JSON with ( )
now it is done properly on _javascript_ side so the current server
implementation triggers _javascript_ errors.

Result can be observed on DynamicComboBox within ui-samples-plugin(cherry picked from commit b6ce03878ed7523878ceffdb69e699c19a941bfc)

Conflicts:
	changelog.html





























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

[JIRA] (JENKINS-15335) Jenkins briefly displays build queue and then it disappears until the page is reloaded















































SCM/JIRA link daemon
 commented on  JENKINS-15335


Jenkins briefly displays build queue and then it disappears until the page is reloaded















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/resources/hudson/model/View/ajaxBuildQueue.jelly
http://jenkins-ci.org/commit/jenkins/cf4e3f7f3564059ec71bd1d2a668baaea3dd2a11
Log:
  [FIXED JENKINS-15335] Typo broke build queue display.(cherry picked from commit 6c4e65f576ea6fa43b06e6d677f40410a87fefc1)





























This message is automatically generated by JIRA.
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] (JENKINS-16465) Maven3Builder don't handle ToolInstallers

2013-01-24 Thread nicolas.del...@gmail.com (JIRA)















































Nicolas De Loof
 commented on  JENKINS-16465


Maven3Builder don't handle ToolInstallers















see https://issues.jfrog.org/jira/browse/HAP-374



























This message is automatically generated by JIRA.
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] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used

2013-01-24 Thread egues...@java.net (JIRA)















































eguess74
 commented on  JENKINS-15779


Parsing ivy descriptors step fails on a slave when custom ivy settings file is used















I can now confirm that the build is not failing anymore on the slave as the parsing step was removed for builds not using the modules. The build still fails with the same exception if "build modules as separate jobs" or "incremental build" is selected.



























This message is automatically generated by JIRA.
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] (JENKINS-16278) "Remember me on this computer" does not work, cookie is not accepted in new session
















































Jesse Glick
 resolved  JENKINS-16278 as Fixed


"Remember me on this computer" does not work, cookie is not accepted in new session
















Not sure why this did not already get marked fixed automatically.





Change By:


Jesse Glick
(24/Jan/13 7:22 PM)




Status:


In Progress
Resolved





Resolution:


Fixed



























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

[JIRA] (JENKINS-3002) TFS Support to get labels

2013-01-24 Thread skaz...@gmail.com (JIRA)













































  
William Lichtenberger
 edited a comment on  JENKINS-3002


TFS Support to get labels
















Please send it to me also.  

I'm happy to code myself, as long as I'm not duplicating effort and coding in vain.  

Update:
Francesco forwarded it to me.  Thank you!



























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

[JIRA] (JENKINS-9852) expr evaluating to zero stops shell script

2013-01-24 Thread b.w.doughe...@gmail.com (JIRA)
















































Brendan Dougherty
 resolved  JENKINS-9852 as Not A Defect


expr evaluating to zero stops shell script
















Change By:


Brendan Dougherty
(24/Jan/13 6:37 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























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

[JIRA] (JENKINS-9852) expr evaluating to zero stops shell script

2013-01-24 Thread b.w.doughe...@gmail.com (JIRA)















































Brendan Dougherty
 commented on  JENKINS-9852


expr evaluating to zero stops shell script















This is actually the correct behavior. By default, Jenkins invokes /bin/sh with the -e (errexit) flag, and expr has an exit status of 1 when the _expression_ evaluates to zero.

Some potential ways to deal with this:

	Use the shell's arithmetic evaluation: 
foo=$((foo-1))

	Use bc: 
foo=`echo "$foo-1" | bc`

	Change the shell invocation as described by the help button for the Execute Shell build step





























This message is automatically generated by JIRA.
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] (JENKINS-16278) "Remember me on this computer" does not work, cookie is not accepted in new session















































Jesse Glick
 commented on  JENKINS-16278


"Remember me on this computer" does not work, cookie is not accepted in new session















@pickgr1 it is already on the 1.480.3 backport candidate list.



























This message is automatically generated by JIRA.
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] (JENKINS-16426) Backup fails while copying a file from the jobs folder

2013-01-24 Thread tofuatj...@java.net (JIRA)















































Thomas Fürer
 commented on  JENKINS-16426


Backup fails while copying a file from the jobs folder















There is no special reason why I would not include files in the job directory to the back up. The idea of thinBackup is to back up only a minimum set of configuration to keep it small and handy. As normally the jobs folder is under control of jenkins. I never would put files in this folder by my own. However, you have done it. I suggest to put the configurations under JENKINS_HOME (where all other global configurations are placed), alternativly I would suggest the userContent folder.
Including files in the job folder to the backup will also open the question why not include files in other jenkins controlled folders. So this will open a neverending task because several plugins (e.g. CloudBees Folders or Matrix Job Configuration) will have their own folder structure, which makes it complicated to back up only a minimal set of files.

Is, moving the files to the suggested folders, an option for you? If not I need to refactor some code and redefine some ideas, technical it is possible, but I'm not sure if I should do it at the moment.



























This message is automatically generated by JIRA.
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] (JENKINS-16465) Maven3Builder don't handle ToolInstallers

2013-01-24 Thread yos...@jfrog.org (JIRA)















































yossis
 commented on  JENKINS-16465


Maven3Builder don't handle ToolInstallers















The freestyle builder exists for some time and it is still used. I opened an issue on our issue tracker https://issues.jfrog.org/jira/browse/HAP-374 and we will check how we can adjust it to work with the latest changes in Jenkins.



























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

[JIRA] (JENKINS-16471) Do not save config.xml of Maven modules















































Jesse Glick
 created  JENKINS-16471


Do not save config.xml of Maven modules















Issue Type:


Bug



Assignee:


Mirko Friedenhagen



Components:


jobconfighistory



Created:


24/Jan/13 5:56 PM



Description:


Seems that JobConfigHistory.isSaveable assumes any AbstractProject should be saved. This makes sense for a MavenModuleSet but rarely makes sense for a MavenModule. I think you should only save a TopLevelItem (at least by default); otherwise you wind up saving tons of config records for things which users rarely if ever save changes to.

BTW showing config changes to a Maven module does not even work, though they are recorded:


java.lang.IllegalArgumentException: A job with this name could not be found: test:b
	at hudson.plugins.jobConfigHistory.JobConfigHistoryBaseAction.getConfigXml(JobConfigHistoryBaseAction.java:163)
	at hudson.plugins.jobConfigHistory.JobConfigHistoryBaseAction.getDiffFile(JobConfigHistoryBaseAction.java:300)
	at hudson.plugins.jobConfigHistory.JobConfigHistoryBaseAction.getDiffLines(JobConfigHistoryBaseAction.java:316)


Seems like you fail to use getItemByFullName correctly.




Project:


Jenkins



Labels:


performance




Priority:


Critical



Reporter:


Jesse Glick

























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

[JIRA] (JENKINS-9093) Deploy: Allow specification of Context Path

2013-01-24 Thread lei...@gmail.com (JIRA)















































Leif Gruenwoldt
 commented on  JENKINS-9093


Deploy: Allow specification of Context Path















For those who reopened this bug, I recommend you check your web project for a META-INF/context.xml file. My project contained this file and had a context "path" param. I removed the context.xml file entirely (to use defaults) and now the Jenkins deploy plugin responds to the "Context path" specified in the 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

[JIRA] (JENKINS-16278) "Remember me on this computer" does not work, cookie is not accepted in new session

2013-01-24 Thread pick...@java.net (JIRA)















































pickgr1
 commented on  JENKINS-16278


"Remember me on this computer" does not work, cookie is not accepted in new session















Please create a new LTS version including this 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

[JIRA] (JENKINS-16434) thinBackup plugin puts Jenkins into shutdown mode and does not come out of it

2013-01-24 Thread tofuatj...@java.net (JIRA)















































Thomas Fürer
 commented on  JENKINS-16434


thinBackup plugin puts Jenkins into shutdown mode and does not come out of it















Hi Sandra,

many thanks for the upload. No, I do not think that it is neccessary to have the config.xml(s). I think the problem is clear and valid, I just need to findout how I can detect the deadlock.

BTW: interesting build structure  looks like something realy awesome will be builded

thomas



























This message is automatically generated by JIRA.
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] (JENKINS-16470) gerrit trigger does not deal with ref-updated very well

2013-01-24 Thread br...@whamcloud.com (JIRA)

Brian Murrell
created JENKINS-16470

gerrit trigger does not deal with ref-updated very well

Issue Type:

Bug

Affects Versions:

current

Assignee:

rsandell

Components:

gerrit-trigger

Created:

24/Jan/13 5:35 PM

Description:

When configuring the Gerrit Trigger to act on ref-updated Gerrit events on a push-direct branch (i.e. for a push to refs/heads/master rather than refs/for/master) it does not deal with multiple commit pushes very well.

The Gerrit stream event looks like:

{"type":"ref-updated","submitter":{"name":"John Doe","email":"j...@example.com"},"refUpdate":{"oldRev":"a9...","newRev":"72...","refName":"FOO-1234","project":"foo"}}

where there can be any number of actual commits between oldRev and newRev. The jenkins reporting for such a build is misleading in that it only lists 1 of the commits (can't remember if it was first or last) in the changelog. Further the "parameters" are also typically wrong. They seem to reflect the parameters for perhaps the previous job.

I strongly suggest whoever is assigned this bug to actually try this use-case and reproduce the problem to see the various issues.

Environment:

Jenkins 1.498

Gerrit-Trigger: 2.7.0

Project:

Jenkins

Labels:

plugin

Priority:

Major

Reporter:

Brian Murrell

[JIRA] (JENKINS-16468) Lock contention in executor queue

2013-01-24 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-16468


Lock contention in executor queue















Integrated in  jenkins_main_trunk #2215
 JENKINS-16468 Linking in changelog. (Revision 2f1ad0b2fbad9bb81ebbf1d0df08a24dcb3f0f16)
JENKINS-16468 Marking as a bug, not an RFE. (Revision a156f1ebc610eae0e6e2316576d6f97a0180986b)

 Result = SUCCESS
Jesse Glick : 2f1ad0b2fbad9bb81ebbf1d0df08a24dcb3f0f16
Files : 

	changelog.html



Jesse Glick : a156f1ebc610eae0e6e2316576d6f97a0180986b
Files : 

	changelog.html





























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

[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used

2013-01-24 Thread egues...@java.net (JIRA)

eguess74
commented on JENKINS-15779

Parsing ivy descriptors step fails on a slave when custom ivy settings file is used

it seems we got to the root of the problem:

Before the actual build starts Jenkins attempts to parse the ivy descriptors in order to determine which ivy modules are supposed to be built. This step doesn't exist when ivy build trigger is used, only when the ivy type job is used. This step is failing to parse ivy descriptors when running on slave as the environment variables are not passed to the slave from master. More than that - this step is not needed unless the build is specified to be incremental or the build is having modules as separate jobs.
It works on master because we are specifying a default value for the JAVA_VERSION property in jenkins startup script. Interestingly enough injecting this variable into the build or slave configuration (Node proeprties) doesn't help, so it keeps failing on the slave.

Therefore the issue is now broken to two parts:
1. The parsing descriptors step should not be executed if the build doesn't require it (that should solve our problem as we are not using neither incremental or separate module-job kind of builds) For that latest changes are provided here:

https://github.com/jenkinsci/ivy-plugin/tree/ivy-descriptors

2. It still open question how to make this parsing step to work on a slave with this kind of variables in case of incremental build or separate module-jobs

[JIRA] (JENKINS-3002) TFS Support to get labels

2013-01-24 Thread skaz...@gmail.com (JIRA)















































William Lichtenberger
 commented on  JENKINS-3002


TFS Support to get labels















Please send it to me also.  skaz...@gmail.com

I'm happy to code myself, as long as I'm not duplicating effort and coding in vain.  



























This message is automatically generated by JIRA.
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] (JENKINS-16469) When using the include region commits to unrelated folders should be masked.

2013-01-24 Thread scar...@vmware.com (JIRA)















































Scott Carter
 created  JENKINS-16469


When using the include region commits to unrelated folders should be masked.















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


git



Created:


24/Jan/13 4:55 PM



Description:


With the git plugin you can set your include regions so that builds are only triggered when a commit comes in on a specific subset of files within the git repo.  The problem with this is when builds finally do get triggered in the "changes" section you see all the commits from the unrelated folders as well.  As a result of this if the person who made the commit which actually did trigger the build causes an instability then all the people who made unrelated commits in the meantime are spammed with emails that they broke the build when in fact their commit has nothing to do with the actual breakage.




Project:


Jenkins



Priority:


Major



Reporter:


Scott Carter

























This message is automatically generated by JIRA.
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] (JENKINS-16467) Error 500 - No Protocol

2013-01-24 Thread bgig...@bradgignac.com (JIRA)















































Brad Gignac
 commented on  JENKINS-16467


Error 500 - No Protocol















After digging through the source, it looks like it might be an issue in the GitHub OAuth plugin. This line removes the protocol prefix from the GitHub URL before calling connectUsingOAuth on the GitHub class. I'm sure there's a reason that it strips protocol, but it isn't obvious to me. Can anyone shed some light on this?



























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

[JIRA] (JENKINS-12619) "Failed to test the validity of the user name" on all security matrices since upgrade

2013-01-24 Thread chris_willia...@dell.com (JIRA)















































Chris Williams
 commented on  JENKINS-12619


"Failed to test the validity of the user name" on all security matrices since upgrade















I can reproduce this on Win2k8R2 but it works on RHEL5:
Jenkins 1.480.2, Jenkins AD plugin 1.30

On RHEL5, I can see the fields "Site", "Bind DN", "Bind Password", and the button "Test" on the Jenkins Config page. Using Project-based Matrix Auth, both individual users and groups are validated properly. The master config.xml file contains tags for both  and .

On Win2k8R2, Jenkins running as a Windows service using a domain account, I do not see the Site/Bind DN/Bind Password fields nor the Test button. I only get "Domain Name" and "Domain controller". Using either Matrix auth, both individual and groups fail to validate and throw the org.acegisecurity.BadCredentialsException error listed above. The master config.xml file contains only a  tag, presumably the value of the encrypted password is the password from the domain account used for the Windows service. If I manually add a  entry to config.xml and reload, Jenkins fails to start and throws the same BadCred exception.



























This message is automatically generated by JIRA.
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] (JENKINS-16468) Lock contention in executor queue















































SCM/JIRA link daemon
 commented on  JENKINS-16468


Lock contention in executor queue















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/a156f1ebc610eae0e6e2316576d6f97a0180986b
Log:
  JENKINS-16468 Marking as a bug, not an RFE.































This message is automatically generated by JIRA.
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] (JENKINS-16468) Lock contention in executor queue















































SCM/JIRA link daemon
 commented on  JENKINS-16468


Lock contention in executor queue















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/2f1ad0b2fbad9bb81ebbf1d0df08a24dcb3f0f16
Log:
  JENKINS-16468 Linking in changelog.































This message is automatically generated by JIRA.
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] (JENKINS-16468) Lock contention in executor queue















































Jesse Glick
 created  JENKINS-16468


Lock contention in executor queue















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


24/Jan/13 4:26 PM



Description:


Filing this retroactively.

https://github.com/jenkinsci/jenkins/commit/f1aa7ba07e3fa5ddf34888a7f10bf04a56de1c74 and follow-up fix https://github.com/jenkinsci/jenkins/commit/6c4e65f576ea6fa43b06e6d677f40410a87fefc1




Project:


Jenkins



Priority:


Major



Reporter:


Jesse Glick

























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

[JIRA] (JENKINS-16468) Lock contention in executor queue
















































Jesse Glick
 resolved  JENKINS-16468 as Fixed


Lock contention in executor queue
















Change By:


Jesse Glick
(24/Jan/13 4:26 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

[JIRA] (JENKINS-16273) Slaves forbidden to request JNLP anonymously but -jnlpCredentials not offered















































Jesse Glick
 commented on  JENKINS-16273


Slaves forbidden to request JNLP anonymously but -jnlpCredentials not offered















Tested workaround for the combination of this and JENKINS-9679 in 1.480.2 for Windows service users on XP:


	Remove any existing service. (jenkins-slave.exe uninstall or see http://stackoverflow.com/a/197941/12916 for removing the service entry; and delete the slave directory.)
	From Windows slave machine, log in, browse to slave page, and click on the JNLP launch button; slave should start.
	Request Windows service installation.
	Stop service if you started it. (Control Panel » Admin Tools » Services)
	Copy your downloaded jenkins-slave.jnlp somewhere permanent, such as the slave FS root.
	Open jenkins-slave.xml in Notepad, find the -jnlpUrl, and change it to point to the downloaded JNLP. This will be a file-protocol URL and must use forward slashes like any URL, e.g.: 
-jnlpUrl file:/C:/jenkins/slave-agent.jnlp

	Start service. The slave should now be connected, and should reconnect properly after a reboot.





























This message is automatically generated by JIRA.
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] (JENKINS-15533) Jobs disappearing with Jenkins 1.485 and 1.486

2013-01-24 Thread bieringer.domi...@gmx.at (JIRA)















































Dominik Bieringer
 commented on  JENKINS-15533


Jobs disappearing with Jenkins 1.485 and 1.486















Does anyone have a workaround or a patch for the described problem? We are facing the same issue with 1.494


Caused by: java.lang.NullPointerException
	at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:207)
	at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:349)
	at hudson.model.Run.onLoad(Run.java:315)
	at hudson.model.RunMap.retrieve(RunMap.java:221)
	at hudson.model.RunMap.retrieve(RunMap.java:59)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:638)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:601)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:344)
	at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:207)
	at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:100)
	at hudson.model.RunMap$1.next(RunMap.java:107)
	at hudson.model.RunMap$1.next(RunMap.java:96)
	at hudson.widgets.HistoryWidget.getRenderList(HistoryWidget.java:133)
	... 122 more




























This message is automatically generated by JIRA.
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] (JENKINS-16467) Error 500 - No Protocol

2013-01-24 Thread bgig...@bradgignac.com (JIRA)















































Brad Gignac
 created  JENKINS-16467


Error 500 - No Protocol















Issue Type:


Bug



Affects Versions:


current



Assignee:


Michael O'Cleirigh



Components:


github-oauth



Created:


24/Jan/13 3:31 PM



Description:


When attempting to use the GitHub OAuth plugin with GitHub Enterprise, I'm receiving a 500 status code after GitHub redirects back to Jenkins.

URL: http://ci.canon.rackspace.com/securityRealm/finishLogin?code=REDACTED
Stacktrace: https://gist.github.com/4623038

It's unclear to me whether this is an issue in the Java API bindings or the GitHub OAuth plugin.




Environment:


Ubuntu 12.04




Project:


Jenkins



Priority:


Minor



Reporter:


Brad Gignac

























This message is automatically generated by JIRA.
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] (JENKINS-16465) Maven3Builder don't handle ToolInstallers

2013-01-24 Thread nicolas.del...@gmail.com (JIRA)















































Nicolas De Loof
 commented on  JENKINS-16465


Maven3Builder don't handle ToolInstallers















according to javadoc, jfrog Maven3Builder is designed as a "Maven3 builder for free style projects. Hudson 1.392 added native support for maven 3 but this one is useful for free style." 

jenkins standard Maven freestyle build step fully supports maven3, so I really don't understand why this build step exists. Should at least re-use maven-plugin's Maven3ProcessFactory to avoid this bug, or probably be deprecated with migration code to convert to hudson.task.Maven



























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

[JIRA] (JENKINS-16466) cmakebuilder launches cmake with PATH defined at node level, ignores PATH expansions by EnvInject plugin

2013-01-24 Thread brett.dellegra...@gmail.com (JIRA)















































Brett Delle Grazie
 created  JENKINS-16466


cmakebuilder launches cmake with PATH defined at node level, ignores PATH expansions by EnvInject plugin















Issue Type:


Bug



Assignee:


Unassigned


Components:


cmakebuilder



Created:


24/Jan/13 3:19 PM



Description:


in our master / slave environment cmakebuilder launches CMake with the PATH environment variable set to that as defined on the node, not as potentially expanded by the job via EnvInject.

We use EnvInject to expand the Job's PATH so that it includes the build tool (ninja in our case) and this fails with file not found.

Can cmakebuilder be adjusted to support the use of EnvInject /CustomTool paths?

Thanks,

Brett




Environment:


Windows 7 and Server 2008




Project:


Jenkins



Priority:


Major



Reporter:


Brett Delle Grazie

























This message is automatically generated by JIRA.
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] (JENKINS-16465) Maven3Builder don't handle ToolInstallers

2013-01-24 Thread nicolas.del...@gmail.com (JIRA)















































Nicolas De Loof
 created  JENKINS-16465


Maven3Builder don't handle ToolInstallers















Issue Type:


Bug



Assignee:


yossis



Components:


artifactory



Created:


24/Jan/13 3:04 PM



Description:


When used with a maven installation set to automatically install maven, build fails with "ERROR: Maven 'Maven 3.0.4' doesn't have its home set"

hudson.maven.AbstractMavenProcessFactory.getMavenInstallation and hudson.tasks.Maven performs the node translation (which is responsible for running installers etc. as well).

org.jfrog.hudson.maven3.Maven3Builder don't.






Project:


Jenkins



Priority:


Major



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

[JIRA] (JENKINS-16462) Run parameters do not support folders















































Jesse Glick
 updated  JENKINS-16462


Run parameters do not support folders
















Workaround plugin (source and binary).





Change By:


Jesse Glick
(24/Jan/13 2:58 PM)




Attachment:


workaround16462.zip





Attachment:


workaround16462.hpi



























This message is automatically generated by JIRA.
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] (JENKINS-16278) "Remember me on this computer" does not work, cookie is not accepted in new session

2013-01-24 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-16278


"Remember me on this computer" does not work, cookie is not accepted in new session















Integrated in  jenkins_main_trunk #2213
 [FIXED JENKINS-16278] Fixed RememberMe cookie signature generation (bugfix on SECURITY-49) (Revision 91bbae3c35230734fd2cf6926a7ac1239119fc6e)
changelog entry for JENKINS-16278 (Revision 0b5a4a3550dcff91b1bedeb77415f683b659634b)

 Result = SUCCESS
hendrik.millner : 91bbae3c35230734fd2cf6926a7ac1239119fc6e
Files : 

	core/src/main/java/hudson/security/TokenBasedRememberMeServices2.java



Olivier Lamy : 0b5a4a3550dcff91b1bedeb77415f683b659634b
Files : 

	changelog.html





























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

[JIRA] (JENKINS-15674) Choosing strategy resets randomly from 'Gerrit Trigger' to 'Default'

2013-01-24 Thread joel.kame...@sas.com (JIRA)















































Joel Kamentz
 commented on  JENKINS-15674


Choosing strategy resets randomly from 'Gerrit Trigger' to 'Default'















1.491 with 1.1.26



























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

[JIRA] (JENKINS-16464) Could not create scheduler















































Walter Kacynski
 commented on  JENKINS-16464


Could not create scheduler















Since I don't really know how this test suite works, I was wondering if the links provided in the output should be updated to reflect the installation options.  Since the link that is provided doesn't "work".



























This message is automatically generated by JIRA.
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] (JENKINS-16278) "Remember me on this computer" does not work, cookie is not accepted in new session















































SCM/JIRA link daemon
 commented on  JENKINS-16278


"Remember me on this computer" does not work, cookie is not accepted in new session















Code changed in jenkins
User: Olivier Lamy
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/0b5a4a3550dcff91b1bedeb77415f683b659634b
Log:
  changelog entry for JENKINS-16278































This message is automatically generated by JIRA.
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] (JENKINS-16278) "Remember me on this computer" does not work, cookie is not accepted in new session















































SCM/JIRA link daemon
 commented on  JENKINS-16278


"Remember me on this computer" does not work, cookie is not accepted in new session















Code changed in jenkins
User: Olivier Lamy
Path:
 core/src/main/java/hudson/security/TokenBasedRememberMeServices2.java
http://jenkins-ci.org/commit/jenkins/4325e006d84113f8e100ec59d03f94f98a6ef3a5
Log:
  Merge pull request #673 from denebolar/JENKINS-16278

[FIXED JENKINS-16278] Fixed RememberMe cookie signature generation (bugfix on SECURITY-49)
Thanks


Compare: https://github.com/jenkinsci/jenkins/compare/de9002b3985c...4325e006d841




























This message is automatically generated by JIRA.
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] (JENKINS-16278) "Remember me on this computer" does not work, cookie is not accepted in new session















































SCM/JIRA link daemon
 commented on  JENKINS-16278


"Remember me on this computer" does not work, cookie is not accepted in new session















Code changed in jenkins
User: Hendrik Millner
Path:
 core/src/main/java/hudson/security/TokenBasedRememberMeServices2.java
http://jenkins-ci.org/commit/jenkins/91bbae3c35230734fd2cf6926a7ac1239119fc6e
Log:
  [FIXED JENKINS-16278] Fixed RememberMe cookie signature generation (bugfix on SECURITY-49)

New cookie signature generation was not implemented in creation of RememberMe cookie, but only in its verification.
Fixed by new override TokenBasedRememberMeServices2.loginSuccess





























This message is automatically generated by JIRA.
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] (JENKINS-16464) Could not create scheduler

2013-01-24 Thread ofir.sha...@hp.com (JIRA)















































Ofir Shaked
 commented on  JENKINS-16464


Could not create scheduler















As Walter mentioned you can use also: http://AlmServer:8080/qcbin/start_a.jsp?common=true to install the ALM client



























This message is automatically generated by JIRA.
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] (JENKINS-16464) Could not create scheduler















































Walter Kacynski
 commented on  JENKINS-16464


Could not create scheduler















Yes, I am running this on a Slave.



























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

[JIRA] (JENKINS-16464) Could not create scheduler















































Walter Kacynski
 commented on  JENKINS-16464


Could not create scheduler















The Wiki was just recently updated with this suggestion which also solved my problem.


Alain Faure says:
I had same issue. I solved it by using the link that download all HP stuff.

http://AlmServer:8080/qcbin/start_a.jsp?common=true

Maybe the link in the HPToolsLauncher.exe should be updated?



























This message is automatically generated by JIRA.
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] (JENKINS-15466) Fatal Error No Class Definition found for Kernel32

2013-01-24 Thread alexander.j...@gmail.com (JIRA)













































  
Alexander Jipa
 edited a comment on  JENKINS-15466


Fatal Error No Class Definition found for Kernel32
















I was having a similar issue on windows, and here's what helped me:

In case the problem is triggered by JNA's UnsatisfiedLinkError on a library, say, "kernel.32.dll" I suggest checking that the jnidispatch.dll that is being linked is the one from JNA, not from any other location in Path.

Debugging java.exe with a simple test case that loads the problematic library using JNA's Native.loadLibrary (say, kernel32.dll) in Visual Studio (I suggest checking all the exceptions) will show you which library was actually used.

That helped me, and I hope will help with this issue too.

In case it doesn't I would recommend checking jnidispatch.dll from JNA's jar (choose the appropriate .dll for you 32-bit or 64-bit platform) and check that there are no errors or missing libraries.



























This message is automatically generated by JIRA.
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] (JENKINS-15156) Builds disappear from build history after completion

2013-01-24 Thread nn...@neulinger.org (JIRA)















































Nathan Neulinger
 commented on  JENKINS-15156


Builds disappear from build history after completion















Running on fc17 x86_64. 



























This message is automatically generated by JIRA.
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] (JENKINS-15156) Builds disappear from build history after completion

2013-01-24 Thread nn...@neulinger.org (JIRA)















































Nathan Neulinger
 commented on  JENKINS-15156


Builds disappear from build history after completion















I've seen it regularly with renamed jobs. We have heavy use of copy artifacts, no matrix use, several ssh slaves. Almost all free-style jobs (though may have a maven one in there too).



























This message is automatically generated by JIRA.
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] (JENKINS-16464) Could not create scheduler

2013-01-24 Thread ofir.sha...@hp.com (JIRA)















































Ofir Shaked
 commented on  JENKINS-16464


Could not create scheduler















Are you working with a slave? 
If so, sis you checked "Restrict where this project can be run" on the 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

[JIRA] (JENKINS-13536) File parameter causing data lost after Jenkins restart

2013-01-24 Thread then...@gmail.com (JIRA)













































  
Thennam Pandian
 edited a comment on  JENKINS-13536


File parameter causing data lost after Jenkins restart

















We are using the jenkin version 1.487
Could you please explain the how do we show the last build manually?

Why the history is not loaded based on timestamps ?



























This message is automatically generated by JIRA.
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] (JENKINS-13536) File parameter causing data lost after Jenkins restart

2013-01-24 Thread then...@gmail.com (JIRA)













































  
Thennam Pandian
 edited a comment on  JENKINS-13536


File parameter causing data lost after Jenkins restart
















Could you please explain the how do we show the last build manually?

Why the history is not loaded based on timestamps ?



























This message is automatically generated by JIRA.
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] (JENKINS-15466) Fatal Error No Class Definition found for Kernel32

2013-01-24 Thread alexander.j...@gmail.com (JIRA)















































Alexander Jipa
 commented on  JENKINS-15466


Fatal Error No Class Definition found for Kernel32















I was having a similar issue on windows, and here's what helped me:

In case the problem is triggered by JNA's UnsatisfiedLinkError on a library, say, "kernel.32.dll" I suggest checking that the jnidispatch.dll that is being linked is the one from JNA, not from any other location in Path.

Debugging java.exe with a simple test case that loads the problematic library using JNA's Native.loadLibrary (say, kernel32.dll) in Visual Studio (I suggest checking all the exceptions) will show you which library was actually used.

That helped me, and I hope will helps this issue too.

In case it doesn't I would recommend checking jnidispatch.dll from JNA's jar (choose the appropriate .dll for you 32-bit or 64-bit platform) and check that there are no errors or missing libraries.



























This message is automatically generated by JIRA.
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] (JENKINS-16464) Could not create scheduler