[JIRA] [subversion] (JENKINS-17431) 500 Internal Server Error on attempt to run a build
Slava Maslenitsyn commented on JENKINS-17431 500 Internal Server Error on attempt to run a build ok. sorry... I don't know your name... alright. let's assume it is not a svnkit problem. then explain to me please, how come, when we get this 500 error (which are getting from time to time, and when it is happening it is always when svnkit is trying to update working space with timestamp), and when build engineer by suggestion, runs build manually using mvn, this build goes just fine. so, it means svn itself is ok. code is fine... and only third party is left here... svnkit. or perhaps you another explanation? you also said I am not the first one, who is reporting this problem. you also have to admit, that this approach to calculate difference in the working space based on timestamp is not very much efficient. too much work, which takes too much time. and honestly, I don't understand why this approach has been chosen at all? it is very natural just to obtain revision before "svn update" then run "svn update" then obtain revision and compare them. or, like I suggested - even more simple. calculate working space used. run svn update. calculate used space again. which could be even faster, as you go to svn repo just once. like I said - i believe playing with time is not the best thing at all... time is not reliable property at all. two machines on the network will never have the same timestamp. besides... let me ask you - up to what precision you are requesting time in the code? and what precision machine gives on the request? and what precision returned by svn? perhaps he could a problem too? what do you think? but, in general, again - I think using timestamp is not reliable and too complicated. I am mechanical engineer by education... simpler mechanism - more reliable it is. cheers, Slava This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
kutzi
edited a comment on JENKINS-17431
500 Internal Server Error on attempt to run a build
(I know that you're not my 'enemy'. If I wrote some words which you consider insulting, I'm sorry for this)
Re 1: No, that's definitely not what the 2nd paragraph says.
Re 2: Okay, so someone in your organisation may have messed with the timestamps. Or not. After all I'm not really convinced that timestamps are your problem. At least I didn't see any conclusive hint in the stacktrace of it.
Re 3: what I wanted to say with 'loose ideas': inconcrete ideas ('lets use revisions instead of timestamps') have been expressed before (just search JIRA for duplicates). It doesn't help if you say it again. Please concrete your idea by a pull request, if you think the change is really necessary (I don't think so)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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
kutzi
edited a comment on JENKINS-17431
500 Internal Server Error on attempt to run a build
(I know that you're not my 'enemy'. If I wrote some words which you consider insulting, I'm sorry for this)
Re 1: No, that's definitely not what the 2nd paragraph says.
Re 2: Okay, so someone in your organisation may have messed with the timestamps. Or not. After all I'm not really convinced that timestamps are your problem. At least I didn't see any conclusive hint in the stacktrace of it.
Re 3: what I wanted to say with 'loose ideas': inconcrete ideas ('lets use timestamps') have been expressed before (just search JIRA for duplicates). It doesn't help if you say it again. Please concrete your idea by a pull request, if you think the change is really necessary (I don't think so)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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
kutzi
commented on JENKINS-17431
500 Internal Server Error on attempt to run a build
(I know that you're not my 'enemy'. If I wrote some words which you consider insulting, I'm sorry for this)
Re 1: No, that's definitely not what the 2nd paragraph says.
Re 2: Okay, so someone in your organisation may have messed with the timestamps. Or not. After all I'm not really convinced that timestamps are your problem. At least I didn't see any conclusive hint in the stacktrace of it.
Re 3: what I want to say with 'loose idea': inconcrete ideas ('lets use timestamps') have been expressed before (just search JIRA for duplicates). It doesn't help if you say it again. Please concrete your idea by a pull request, if you think the change is really necessary (I don't think so)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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
Chris Dore
edited a comment on JENKINS-17222
Add ability to specify more than one location when using the svn method
Yes, it is possible. The following should add a second location:
svn('https://some.repo.com/proj1/trunk', 'project1') {
it / locations . 'hudson.scm.SubversionSCM_-ModuleLocation' {
remote 'https://some.repo.com/proj2/branches/qwe'
local 'project2_qwe'
}
}
It's similar to the example posted in Justin's comment, however what's in his comment doesn't work.
You should be able to repeat the following for as many locations as you need. However, I don't know if there is a limit to the number of locations that the SVN Jenkins plugin supports.
it / locations . 'hudson.scm.SubversionSCM_-ModuleLocation' {
remote 'https://repoN'
local 'N'
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-15078) Be able to set Instance Name
Francis Upton resolved JENKINS-15078 as Fixed Be able to set Instance Name Change By: Francis Upton (10/Apr/13 5:19 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] [subversion] (JENKINS-16533) Jobs checked out from svn with pinned externals continuously run (with no changes in svn)
herve_colliaux commented on JENKINS-16533 Jobs checked out from svn with pinned externals continuously run (with no changes in svn) Sorry for the delay. I confirm this happened to me with the same kind of externals (edited with TortoiseSVN). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-15319) Failure starting slave nodes
Francis Upton resolved JENKINS-15319 as Fixed Failure starting slave nodes Change By: Francis Upton (10/Apr/13 4:13 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] [subversion] (JENKINS-17431) 500 Internal Server Error on attempt to run a build
Slava Maslenitsyn commented on JENKINS-17431 500 Internal Server Error on attempt to run a build Hello, First of all… I am not your enemy… so words about loose ideas to work with revision instead of timestamps… “you messed up with timestamps” … perhaps not so nice… Anyway… 1. I think you are mistaken. What this lines are saying is: when subversion cannot fully read and understand the timestamp, but understands it partially, it assumes that time is 00:00 (midnight) of that day. You, in your request may not mean it, right? 2. I did not delete any timestamps. I checked all the repos I am administering several thousand revisions back – all timestamps are there. Yes, they can be changed. I personally never did it for any single timestamp in any repo I am administering. Users…. might however. 3. I made my point clear many times already – timestamp are difficult to deal with and they cannot be reliable in making decision whether or not to run build. Besides, it is not efficient to use timestamp to search repo if any revision were made for this particular place in repo between these two timestamps – too much work… revisions are better and more clear defined properties to deal with, so I am proposing to make changes in the code and get rid of this approach with timestamps and use revision numbers instead. Regards, Slava This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17147) The configuration for testng method name and data provider is not saved
Bruno P. Kinoshita closed JENKINS-17147 as Fixed The configuration for testng method name and data provider is not saved Fixed in 3.3 Change By: Bruno P. Kinoshita (10/Apr/13 3:07 AM) 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-15588) TestLink is not getting Updated
Bruno P. Kinoshita closed JENKINS-15588 as Incomplete TestLink is not getting Updated Closing since we didn't get feedback and it doesn't look like a bug. Feel free to reopen with details in case you identify a bug. Cheers, Bruno Change By: Bruno P. Kinoshita (10/Apr/13 3:07 AM) 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17023) Jenkins Testlink plugin Found 0 test result is show while test is runned
Bruno P. Kinoshita closed JENKINS-17023 as Not A Defect Jenkins Testlink plugin Found 0 test result is show while test is runned Fixed in 3.3 Change By: Bruno P. Kinoshita (10/Apr/13 3:06 AM) 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16118) Testlink Plug-In: get Custom field information for Testplans and Testsuites
Bruno P. Kinoshita closed JENKINS-16118 as Not A Defect Testlink Plug-In: get Custom field information for Testplans and Testsuites Fixed in 3.3 Change By: Bruno P. Kinoshita (10/Apr/13 3:05 AM) 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17442) When connecting to TestLink, finding error ClassCastException
Bruno P. Kinoshita commented on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Hi @Supratim, When we commit our code to Jenkins repositories at GitHub, usually we include special tokens (JENKINS-, or [FIXED JENKINS-]. Jenkins has some backend jobs that read the commit log and resolve and stop the progress on the issues. Then the plug-in maintainer releases a new version and, once it's released, he/she closes the issues. I've just released Jenkins TestLink Plug-in 3.3, this new version includes the fix for this issue. Keep an eye on @jenkins_release and once you see TestLink Plug-in there, update your Jenkins instance and the issue should be gone. Let me know if that works, ok? Cheers, Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17442) When connecting to TestLink, finding error ClassCastException
Bruno P. Kinoshita closed JENKINS-17442 as Fixed When connecting to TestLink, finding error ClassCastException Fixed in 3.3 Change By: Bruno P. Kinoshita (10/Apr/13 3:05 AM) 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
Bruno P. Kinoshita commented on JENKINS-16898 Testlink plugin exception setting status with TestNG Result Seeker No worries Jeff. 3.3 just got out of my machine. It should be available in the update site in few hours. Keep an eye on @jenkins_release, and let me know if that fixes your issue, please. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
Chris Dore
commented on JENKINS-17222
Add ability to specify more than one location when using the svn method
Yes, it is possible. The following should add a second location:
svn('https://some.repo.com/proj1/trunk', 'project1') {
it / locations . 'hudson.scm.SubversionSCM_-ModuleLocation' {
remote 'https://some.repo.com/proj2/branches/qwe'
local 'project2_qwe'
}
}
It's similar to the example posted in Justin's comment, however what's in his comment doesn't work.
You should be able to repeat the following for as many locations as you need. However, I don't know if there is a limit to the number of locations that the SVN Jenkins plugin supports.
it / locations . 'hudson.scm.SubversionSCM_-ModuleLocation' {
remote 'https://repoN'
local 'N'
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17551) Add a global list of committers that will be excluded from receiving emails
Alex Earl commented on JENKINS-17551 Add a global list of committers that will be excluded from receiving emails I think this should rather be included in the MailAddressResolver, not in email-ext. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [publish-over-cifs] (JENKINS-17112) Publish over CIFS shares do not persist
Kevin Burge commented on JENKINS-17112 Publish over CIFS shares do not persist You might as well revert to 1.503. I had nothing but problems with each new update after 1.503. It took a few hours to downgrade, but it was worth it. I'm surprised such a significant feature has received so little attention. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17551) Add a global list of committers that will be excluded from receiving emails
shinsato created JENKINS-17551 Add a global list of committers that will be excluded from receiving emails Issue Type: New Feature Affects Versions: current Assignee: shinsato Components: email-ext Created: 10/Apr/13 12:15 AM Description: If a source control account is doing automated updates and checkins - if a human is attached to that account they'll be bombarded with emails with no meaning. Rather than preventing these changes from being pulled and trigger builds - we'd like to just exclude them from receiving emails entirely. We've been using a small change for this for over a year - will submit a pull request shortly. Project: Jenkins Priority: Minor Reporter: shinsato This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [xvnc] (JENKINS-17550) Xvnc plugin tries to use already allocated displays
Levon Saldamli created JENKINS-17550 Xvnc plugin tries to use already allocated displays Issue Type: Bug Affects Versions: current Assignee: Levon Saldamli Components: xvnc Created: 09/Apr/13 11:21 PM Description: Xvnc plugin creates a new allocator for each build, and forgets previously allocated ports and tries to allocate them again. Project: Jenkins Labels: plugin Priority: Major Reporter: Levon Saldamli This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-9146) Allow archiving of empty directories to be enabled/disabled
dougbrinkmeier commented on JENKINS-9146 Allow archiving of empty directories to be enabled/disabled For us, this is more than a "Minor" priority issue - it's causing the application that was written to expect the folder to be there to fail. I don't understand the logic behind why this was set to never allow you to copy empty directories. The build itself always has the ability to remove empty directories if they aren't desired before archiving. However, if you do desire empty directories in the artifacts, then with this change in, it is impossible to implement this. If, for example, we did not have the source code (vendor binary package), and we used Jenkins as our enterprise solution for "packaging", there would be no work-around. There is always a work-around for "deleting" unnecessary directories from a build, though - don't create them - delete in build script - added "batch command" build step - etc. I think this alone is enough to justify at least an option to include empty directories. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
Fred G commented on JENKINS-8916 Allowing same type of parameter for triggered build more than once seems redundant @jlpinardon This has already been fixed (see JENKINS-15834) and it's available in version 2.17 of the Parameterized Trigger Build Plugin. You can specify a comma separated list of property files now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Dallas Gutauckis commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity I'm also seeing this issue, with the same "workaround" to resolve. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17546) New Trigger: broken build -> compiling build (unstable/stable)
calculu5 commented on JENKINS-17546 New Trigger: broken build -> compiling build (unstable/stable) Sorry I used the term 'fixed' even though there is already a Fixed trigger with its own semantics. Yes, I mean 'when the compile is working.' My trigger would be from when the build is broken to when it is compiling again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException by start
Michael McCallum commented on JENKINS-17248 java.lang.NullPointerException by start Removing the /global-build-stats and /global-build-stats.xml works around the problem... but you lose the stats, that didn't bother me as much as jenkins not running... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
Jeff Rodgers commented on JENKINS-16898 Testlink plugin exception setting status with TestNG Result Seeker My bad, I see that issue I just posted is a duplicate of #17442. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17546) New Trigger: broken build -> compiling build (unstable/stable)
Alex Earl commented on JENKINS-17546 New Trigger: broken build -> compiling build (unstable/stable) So, just to make sure I am clear. You consider fixed to be when the compile is working, but not necessarily when the tests are all running? This would indeed be a new trigger. Once the script triggers are in place, you would be able to use those to define your own logic like this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17546) New Trigger: broken build -> compiling build (unstable/stable)
calculu5 commented on JENKINS-17546 New Trigger: broken build -> compiling build (unstable/stable) My understanding is that the improvement trigger would include the transition from yellow to blue (not desired in this case, too much noise). My use case is to notify users of broken builds (done and configured) and to send an email when the build is compiling again. People should not be getting mail that test x is now fixed (and thus improved), but would rather know that the build they broke previously is now fixed. Or have I misunderstood the improvement trigger? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-16898) Testlink plugin exception setting status with TestNG Result Seeker
Jeff Rodgers edited a comment on JENKINS-16898 Testlink plugin exception setting status with TestNG Result Seeker I uninstalled TestLink 1.9.5 and installed 1.9.6. I also upgraded the Jenkins TestLink plugin to 3.2. I now get the following error trying to run the tutorial example: Started by user anonymous [EnvInject] - Loading node environment variables. Building on master in workspace /home/jenkins/workspace/TestlinkPrototype Checkout:TestlinkPrototype / /home/jenkins/workspace/TestlinkPrototype - hudson.remoting.LocalChannel@6c892cb5 Using strategy: Default Last Built Revision: Revision 1462fa2ef862adbba0abd652eab83bada2fb9474 (origin/master, origin/HEAD) Fetching changes from 1 remote Git repository Fetching upstream changes from origin Commencing build of Revision 1462fa2ef862adbba0abd652eab83bada2fb9474 (origin/HEAD) Checking out Revision 1462fa2ef862adbba0abd652eab83bada2fb9474 (origin/HEAD) [EnvInject] - Executing scripts and injecting environment variables after the SCM step. Preparing TestLink client API. Using TestLink URL: http://coltrane.aus.vbridges.com/testlink/lib/api/xmlrpc.php FATAL: java.util.HashMap cannot be cast to [Ljava.lang.Object; java.lang.ClassCastException: java.util.HashMap cannot be cast to [Ljava.lang.Object; at br.eti.kinoshita.testlinkjavaapi.util.Util.castToArray(Util.java:566) at br.eti.kinoshita.testlinkjavaapi.TestProjectService.getTestProjectByName(TestProjectService.java:111) at br.eti.kinoshita.testlinkjavaapi.TestLinkAPI.getTestProjectByName(TestLinkAPI.java:438) at hudson.plugins.testlink.TestLinkBuilder.getTestLinkSite(TestLinkBuilder.java:246) at hudson.plugins.testlink.TestLinkBuilder.perform(TestLinkBuilder.java:134) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:798) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1575) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
Jeff Rodgers commented on JENKINS-16898 Testlink plugin exception setting status with TestNG Result Seeker I uninstalled TestLink 1.9.5 and installed 1.9.6. I also upgraded the Jenkins TestLink plugin to 3.2. I now get the following error trying to run the tutorial example: Started by user anonymous [EnvInject] - Loading node environment variables. Building on master in workspace /home/jenkins/workspace/TestlinkPrototype Checkout:TestlinkPrototype / /home/jenkins/workspace/TestlinkPrototype - hudson.remoting.LocalChannel@6c892cb5 Using strategy: Default Last Built Revision: Revision 1462fa2ef862adbba0abd652eab83bada2fb9474 (origin/master, origin/HEAD) Fetching changes from 1 remote Git repository Fetching upstream changes from origin Commencing build of Revision 1462fa2ef862adbba0abd652eab83bada2fb9474 (origin/HEAD) Checking out Revision 1462fa2ef862adbba0abd652eab83bada2fb9474 (origin/HEAD) [EnvInject] - Executing scripts and injecting environment variables after the SCM step. Preparing TestLink client API. Using TestLink URL: http://coltrane.aus.vbridges.com/testlink/lib/api/xmlrpc.php FATAL: java.util.HashMap cannot be cast to [Ljava.lang.Object; java.lang.ClassCastException: java.util.HashMap cannot be cast to [Ljava.lang.Object; at br.eti.kinoshita.testlinkjavaapi.util.Util.castToArray(Util.java:566) at br.eti.kinoshita.testlinkjavaapi.TestProjectService.getTestProjectByName(TestProjectService.java:111) at br.eti.kinoshita.testlinkjavaapi.TestLinkAPI.getTestProjectByName(TestLinkAPI.java:438) at hudson.plugins.testlink.TestLinkBuilder.getTestLinkSite(TestLinkBuilder.java:246) at hudson.plugins.testlink.TestLinkBuilder.perform(TestLinkBuilder.java:134) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:798) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1575) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
kutzi commented on JENKINS-17431 500 Internal Server Error on attempt to run a build Okay the 2nd paragraph is no big deal - it just says that the time defaults to 0 hour if you don't specify it. About the 1st paragraph: so what is the point you want to make? That if you really want to mess with the timestamp, you can. Yeah okay, you may, but I don't think that's something 'sane' to do. Let me tell you how I see it: Jenkins has been using timestamps in the svn-plugin for a very long time. This has worked well for the big majority of users. There's an occasional bug report about 'wrong updates' which almost always has something to do with out-of-sync clocks and so easily resolved. for some reason it is not working for you. Maybe because you messed with the timestamps. That's IMO a problem with your configuration and no bug in the svn-plugin if you have a better idea on how to handle updates in the svn-plugin, feel free to post your concrete idea (loose ideas to work with revisions instead of timestamps have already been posted before. They're IMHO no big help) - i.e. as a Github pull request. However, I think that the danger of introducing backwards incompatible changes by this is IMO very very big. So we would need to introduce it as an optional setting. Which would in turn bring up the question why we need this setting, when the plugin is working very well in the vast majority of environments ... BTW: you may also want to experiment with the @HEAD setting in the repository URLs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
Bruno P. Kinoshita commented on JENKINS-16898 Testlink plugin exception setting status with TestNG Result Seeker Hi Jeff >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. Cool, let me know if you find anything new. I'll delay the release a few hours, but will release 3.3 within hours. >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. Indeed, that suffices as an example. I sent the other example as I was working with another user on similar issue (but his was simply a job configuration issue). 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [parameters] (JENKINS-17549) Non Editable Build Parameter
George Kinlay updated JENKINS-17549 Non Editable Build Parameter Change By: George Kinlay (09/Apr/13 8:02 PM) Description: There should be an build parameter that is Non Editable in "Build Now", sometime we need to show a parameter in run-time for FYI but do not want it to be changed by the builder There could be an option that makes that parameter non editable, like a check-box This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [parameters] (JENKINS-17549) Non Editable Build Parameter
George Kinlay created JENKINS-17549 Non Editable Build Parameter Issue Type: Improvement Assignee: Unassigned Components: parameters Created: 09/Apr/13 7:59 PM Description: There should be an build parameter that is Non Editable in "Build Now", sometime we need to show a parameter in run-time for FYI but do not want it to be changed by the builder Environment: ALL Project: Jenkins Priority: Major Reporter: George Kinlay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17546) New Trigger: broken build -> compiling build (unstable/stable)
Alex Earl commented on JENKINS-17546 New Trigger: broken build -> compiling build (unstable/stable) What about the improvement trigger? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-16974) Build Now link on MultiJob page doesn't work
David Ishee commented on JENKINS-16974 Build Now link on MultiJob page doesn't work If I use the 'b' keystroke, I get this message: You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that 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] [violations] (JENKINS-17548) FxCop results not being displayed for non-source files
Jeff Hughes
created JENKINS-17548
FxCop results not being displayed for non-source files
Issue Type:
Bug
Assignee:
peterkittreilly
Attachments:
ImageMetaData.cs.xml, Jenkins_FxCop_Violations_Plugin_Problem.jpg, Project.Domain.Model.Interfaces.IProjectStub.xml
Components:
violations
Created:
09/Apr/13 7:17 PM
Description:
If a violation is found (by FxCop) for which there is no source code (such as a DLL), the Violations plugin does not display the actual violation message (just blank page with a red triangle with an "!" in it).
This appears to be due to the plugin only displaying the "popup-message" for the errors when the user mouses-over the warning in the code view.
However, if there is no code to view, there is no method to display the violations. Also, the violation "message" section is not displayed in either case (it needs to be as it contains valuable information).
More Info
Specifying FxCop output (XML) file in the Violations plugin will cause the Violation plugin to parse the (FxCop) XML file(s) generating violation (XML) files for each file (each of these XML files can contain multiple violations). These (Violation plugin) XML files are stored in the "~\jobs\\builds\\violations\file" folder with ".xml" appended to the original file name (e.g.: domain.interface.dll -> domain.interface.dll.xml). When the user clicks on a source file (within the Violations plugin results page, the Violations XML file is parsed and displayed on the screen.)
Each of these (Violations plugin) XML files contain a "file", (multiple) "violation", "line" and "type" sections.
File Section
The "file" section (of the XML file) contains the file "name", "last-modified" date, and a link to the "file" (if applicable):
last-modified="1365521927609" file="c:\Jenkins\workspace\Project_Server_FxCop\Server\Projecty.Server\Project.Domain.Model\ImageMetaData.cs"
>
Violations
The "violations" section contain the "line", violation "source", violation "severity", violation "type", violation "message", violation "severity-level", and the violation "popup-message":
line="82"
source="Naming#CA1702"
severity="Medium High"
type="fxcop"
message="
severity-level="1"
popup-message="Avoid creating compound words from terms which exist in the dictionary as discrete terms. Do not create a compound word such as 'StopWatch' or 'PopUp'. These terms are recognized in the dictionary and should be cased as 'Stopwatch' and 'Popup'."
/>
Line Number
Next, the Violations XML file contains a section containing zero or multiple "line number" entries which contain code from the source file.
public virtual bool IsMetaDataEqual(ImageMetaData imageMetaData)
{
if (Hash == imageMetaData.Hash &&
Type == imageMetaData.Type &&
FileLength == imageMetaData.FileLength
)
{
Type
Finally, the "type" section indicates that it is "fxcop" and also contains the total number of violations found:
If the file does not contain code, then all the violation line numbers are set to 0 (zero) and there is no "line number" section in the Violations plugin XML files. (See attached files: "ImageMetaData.cs.xml" and "Project.Domain.Model.Interfaces.IProjectStub.xml")
The problem is two-fold: First if the file is not a source code file then no violations are displayed at all (see attached screenshot). Second, the "message" data is not displayed in either case (and in most cases contains more valuable information than the "popup-message").
The Violations plugin should display a table of the "messages" and "popup-messages" if there is no code to display, and the "messages" text should be added to the pop-up table when there is code to display.
Environment:
Windows Server 2008 R2 Enterprise, Jenkins 1.510, Violations plugin 0.7.11
[JIRA] [core] (JENKINS-10738) Different "build now" for parameterized builds
dogfood commented on JENKINS-10738 Different "build now" for parameterized builds Integrated in jenkins_main_trunk #2447 [FIXED JENKINS-10738] Different "build now" text for parameterized builds. (Revision b22b17c0d68c95bece46818fbf9ef562902b10c1) Result = SUCCESS Jesse Glick : b22b17c0d68c95bece46818fbf9ef562902b10c1 Files : core/src/main/resources/hudson/model/Messages.properties core/src/main/java/hudson/model/AbstractProject.java changelog.html core/src/main/resources/hudson/views/BuildButtonColumn/column.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ant] (JENKINS-17547) Relative Path in Slave's Remote FS Root breaks automatically installed Tools
Mukul Sharma updated JENKINS-17547 Relative Path in Slave's Remote FS Root breaks automatically installed Tools Change By: Mukul Sharma (09/Apr/13 6:40 PM) Environment: Jenkins build number 1.509 Tried on Mac and Windows . Description: Steps to reproduce -1. Create a Jenkins slave node.2. Specify the "Remote FS Root" value of the slave as a relative path.3. Use any auto-install tool, for example Ant (by adding Ant Installation settings in Jenkins configuration)4. Run a build with "Invoke Ant" task. This task should use the version of Ant setup in the Ant-Installation settings.5. Build fails as it is unable to find the recently downloaded ant binary. Sample Build Output -Started by user anonymousBuilding remotely on Test Node in workspace Documents/jar_sources/workspace/Test MATT PluginUnpacking http://archive.apache.org/dist/ant/binaries/apache-ant-1.9.0-bin.zip to Documents/jar_sources/tools/hudson.tasks.Ant_AntInstallation/ant-test on Test Node[Test MATT Plugin] $ Documents/jar_sources/tools/hudson.tasks.Ant_AntInstallation/ant-test/bin/ant cleanFATAL: command execution failed.java.io.IOException: Cannot run program "Documents/jar_sources/tools/hudson.tasks.Ant_AntInstallation/ant-test/bin/ant" (in directory "Documents/jar_sources/workspace/Test MATT Plugin"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:763) at hudson.Launcher$ProcStarter.start(Launcher.java:353) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:988) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:955) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:680)Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:53) at java.lang.ProcessImpl.start(ProcessImpl.java:91) at java.lang.ProcessBuilder.start(ProcessBuilder.java:453) ... 15 moreBuild step 'Invoke Ant' marked build as failureFinished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ant] (JENKINS-17547) Relative Path in Slave's Remote FS Root breaks automatically installed Tools
Mukul Sharma created JENKINS-17547 Relative Path in Slave's Remote FS Root breaks automatically installed Tools Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Snapshot.jpg Components: ant Created: 09/Apr/13 6:29 PM Description: Steps to reproduce - 1. Create a Jenkins slave node. 2. Specify the "Remote FS Root" value of the slave as a relative path. 3. Use any auto-install tool, for example Ant (by adding Ant Installation settings in Jenkins configuration) 4. Run a build with "Invoke Ant" task. This task should use the version of Ant setup in the Ant-Installation settings. 5. Build fails as it is unable to find the recently downloaded ant binary. Environment: Tried on Mac and Windows Project: Jenkins Labels: jenkins slave ant soasta-cloudtest-plugin Priority: Major Reporter: Mukul Sharma This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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).
Nemoo commented on JENKINS-17545 A new default include creates unwanted commits (without config changes). Your jenkins version: Jenkins ver. 1.504 Your scm-sync-config plugin version: 0.0.7 The backed scm you use for your configuration (svn or git ?): svn Other plugins we are currently using (OMG): -- Jenkins Mailer Plugin 1.4 External Monitor Job Type Plugin 1.1 LDAP Plugin 1.2 pam-auth 1.0 Ant Plugin 1.2 Javadoc Plugin 1.1 Deploy to container Plugin This plugin allows you to deploy a war to a container after a successful build. Glassfish 3.x remote deployment 1.9 Maven 2 Project Plugin 1.504 Static Analysis Utilities This plug-in provides utilities for the static code analysis plug-ins. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 1.49 Warnings Plug-in This plug-in collects the compiler warnings of the project modules and visualizes the results. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 4.23 Git Client Plugin 1.0.3 Jenkins Subversion Plug-in 1.45 Jenkins Parameterized Trigger plugin 2.17 Git Plugin This plugin integrates GIT with Jenkins. 1.2.0 Jenkins Clone Workspace SCM Plug-in This plugin makes it possible to archive the workspace from builds of one project and reuse them as the SCM source for another project. 0.5 SSH Slaves plugin 0.22 CVS Plugin Integrates Jenkins with CVS version control system using a modified version of the Netbeans cvsclient. 2.7 Build Blocker Plugin This plugin blocks a build if one of the given jobs is running. 1.3 Checkstyle Plug-in This plug-in collects the Checkstyle analysis results of the project modules and visualizes the found warnings. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 3.35 SCM Sync Configuration Plugin This plugin allows you to synchronize your hudson configuration files with an SCM, allowing you to specify a commit message every time a config file is modified. 0.0.7 Publish Over SSH Send build artifacts over SSH 1.10 Duplicate Code Scanner Plug-in This plug-in collects the duplicate code analysis results of the project modules and visualizes the found warnings. Supported duplicate code analysis tools: PMD's Copy Paste Detector (CPD) Simian If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 2.34 Static Analysis Collector Plug-in This plug-in is an add-on for the plug-ins Checkstyle, Dry, FindBugs, PMD, Tasks, and Warnings: the plug-in collects the different analysis results and shows the results in a combined trend graph. Additionally, the plug-in provides health reporting and build stability based on these combined results. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 1.35 Build Pipeline Plugin This plugin renders upstream and downstream connected jobs that typically form a build pipeline. In addition, it offers the ability to define manual triggers for jobs that require intervention prior to execution, e.g. an approval process outside of Jenkins. 1.3.3 Email-ext plugin This plugin is a replacement for Jenkins's email publisher 2.27.1 Jenkins Throttle Concurrent Builds Plug-in This plugin allows for throttling the number of concurrent builds of a project running per node or globally. 1.7.2 Jenkins Translation Assistance plugin 1.10 Jenkins JDepend Plugin This is a plugin that runs JDepend reports on builds. 1.2.3 Hudson SCP publisher plugin This plugin uploads build artifacts to repository sites using SCP (SSH) protocol. 1.8 Promoted Builds Plugin This plugin implements a "promoted build" feature where a build of one job can be marked as "promoted" when it passes certain criteria. 2.8 Copy Artifact Plugin Adds a build step to copy artifacts from another project. 1.25 Jenkins TextFinder plugin This plugin is used to search for strings in workspace files. The outcome of this search can be used to mark the build as normal or failed. 1.9 Jenkins SSH plugin This plugin executes shell commands remotely using SSH protocol. 2.3 -- This message is automatically generated by JIRA
[JIRA] [scm-sync-configuration] (JENKINS-17545) A new default include creates unwanted commits (without config changes).
Frédéric Camblor commented on JENKINS-17545 A new default include creates unwanted commits (without config changes). I just tested to create a multimodule maven build on jenkins, having some modules/my-module/config.xml in JENKINS_HOME/jobs/myJob/ But once done, I cannot reproduce your problem (modules' config.xml files are not commited in my repo). Could you give me : Your jenkins version Your scm-sync-config plugin version The backed scm you use for your configuration (svn or git ?) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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"
dogfood commented on JENKINS-17110 Hover-over "Build Now" broken for parameterized jobs: "This page expects a form submission" Integrated in jenkins_main_trunk #2446 [FIXED JENKINS-17110] Build Now should be GET for parameterized jobs. (Revision 97da1618c52792bd675f8677b7e18df629f80eb7) Result = SUCCESS Jesse Glick : 97da1618c52792bd675f8677b7e18df629f80eb7 Files : core/src/main/resources/hudson/model/AbstractProject/sidepanel.jelly changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sectioned-view] (JENKINS-8276) Add View Job Filters to the List View Section
Michel Rasschaert commented on JENKINS-8276 Add View Job Filters to the List View Section Ok. It seems to be working after all but the Job Filters dropdown does not appear when creating the list view section. You must first create the list view section, save the sectioned view and edit it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17546) New Trigger: broken build -> compiling build (unstable/stable)
calculu5 created JENKINS-17546 New Trigger: broken build -> compiling build (unstable/stable) Issue Type: New Feature Assignee: Alex Earl Components: email-ext Created: 09/Apr/13 5:46 PM Description: I am wanting a new trigger that will send emails on the transition from a broken build (red orb) to a compiling build (yellow or blue orb). This would let us know that a build has been fixed but not necessarily that all tests are currently passing. Unfortunately the Fixed trigger does not meet this requirement as it would send an email on the transition from yellow to blue orbs (not desired), and misses the transition from red to yellow orbs. Project: Jenkins Priority: Major Reporter: calculu5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16560) Failure to rewrite files during rekeying on Windows Server 2003 R2
shinsato commented on JENKINS-16560 Failure to rewrite files during rekeying on Windows Server 2003 R2 I worked around this issue by re-keying in the background after the initial failure. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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 resolved JENKINS-10738 as Fixed Different "build now" for parameterized builds Change By: SCM/JIRA link daemon (09/Apr/13 5:15 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/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] [scm-sync-configuration] (JENKINS-17545) A new default include creates unwanted commits (without config changes).
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] [subversion] (JENKINS-17431) 500 Internal Server Error on attempt to run a build
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
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-17545) A new default include creates unwanted commits (without config changes).
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] [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).
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: false ... 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 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
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 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
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
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] [subversion] (JENKINS-16736) SVN triggers build without any SCM change
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] [analysis-core] (JENKINS-17542) Decrease thresholds after builds automatically
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 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
Johannes Huber updated JENKINS-17542 Decrease thresholds after builds automatically Change By: Johannes Huber (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 we will share the solution as well.Code name "thumbscrew" ;-) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [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] [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] [discard-old-build] (JENKINS-17528) Discard Old Builds plugin throws java.lang.UnsupportedOperationException
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] [discard-old-build] (JENKINS-17528) Discard Old Builds plugin throws java.lang.UnsupportedOperationException
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] [plugin] (JENKINS-17528) Discard Old Builds plugin throws java.lang.UnsupportedOperationException
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] [subversion] (JENKINS-16736) SVN triggers build without any SCM change
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] [android-emulator] (JENKINS-13648) Automatic Support for Intel® Hardware Accelerated Execution Manager
Christopher Orr closed JENKINS-13648 as Won't 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: 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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. :-)
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] [subversion] (JENKINS-16533) Jobs checked out from svn with pinned externals continuously run (with no changes in svn)
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] [github-oauth] (JENKINS-17539) Swarm clients fail to connect if GitHub for authentication
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
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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
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
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] [grails] (JENKINS-10266) Set grails.work.dir to something unique by default
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
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: Not A Defect 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] [copyartifact] (JENKINS-17538) When artifact is copied, add an Action to track the build this artifact has been copied for
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] [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] [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] [ec2] (JENKINS-17536) Workspace environment variable is relative on ec2 slave
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: Jenkins 1. 479 495 , EC2 plugin 1.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] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
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] [active-directory] (JENKINS-17537) An API Exception was caught! MKS124803: Internal error detected
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] [job-dsl-plugin] (JENKINS-17222) Add ability to specify more than one location when using the svn method
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] [jenkins-multijob-plugin] (JENKINS-17535) Provide env vars detailing triggered builds
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] [maven] (JENKINS-13390) "Build whenever a SNAPSHOT dependency is built" doesn't work for some builds without any reason.
evernat commented on JENKINS-13390 "Build whenever a SNAPSHOT dependency is built" doesn't 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] [ec2] (JENKINS-17536) Workspace environment variable is relative on ec2 slave
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] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
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] [subversion] (JENKINS-16736) SVN triggers build without any SCM change
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] [maven] (JENKINS-17534) Maven modules view not showing last successful build
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
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] [cvs] (JENKINS-17533) Jenkins 1.510 deletes all CVS branch checkout files
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] [xunit] (JENKINS-17491) xUnit v1.52 fails with ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception
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: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17491) xUnit v1.52 fails with ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception
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] [android-emulator] (JENKINS-17532) Creating separate jobs doesn't install system images
Christopher Orr commented on JENKINS-17532 Creating separate jobs doesn't 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] [android-emulator] (JENKINS-17532) Creating separate jobs doesn't install system images
Ruud Althuizen commented on JENKINS-17532 Creating separate jobs doesn't install system images The output for "android list target" is Available Android targets: -- id: 1 or "android-17" Name: Android 4.2.2 Type: Platform API level: 17 Revision: 2 Skins: WVGA854, WQVGA432, QVGA, WVGA800 (default), WXGA800, WXGA800-7in, WXGA720, WQVGA400, HVGA, WSVGA ABIs : no ABIs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
Ruud Althuizen edited a comment on JENKINS-17532 Creating separate jobs doesn't 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
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.
