[JIRA] (JENKINS-12881) Allow reading custom build message from a workspace file, in case of non-success

[ https://issues.jenkins-ci.org/browse/JENKINS-12881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159475#comment-159475 ] Joe Hansche edited comment on JENKINS-12881 at 2/29/12 7:14 AM: --

[JIRA] (JENKINS-12881) Allow reading custom build message from a workspace file, in case of non-success

[ https://issues.jenkins-ci.org/browse/JENKINS-12881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159475#comment-159475 ] Joe Hansche edited comment on JENKINS-12881 at 2/29/12 7:14 AM: --

[JIRA] (JENKINS-12881) Allow reading custom build message from a workspace file, in case of non-success

[ https://issues.jenkins-ci.org/browse/JENKINS-12881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Hansche reassigned JENKINS-12881: - Assignee: rsandell (was: Joe Hansche) The pull request is at https://github.com/jenki

[JIRA] (JENKINS-12927) Changes doesn't trigger a build - "unknown revision"

[ https://issues.jenkins-ci.org/browse/JENKINS-12927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159651#comment-159651 ] Marcus Eriksson commented on JENKINS-12927: --- The used unknown revision is remember

[JIRA] (JENKINS-12881) Allow reading custom build message from a workspace file, in case of non-success

[ https://issues.jenkins-ci.org/browse/JENKINS-12881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12881 stopped by Joe Hansche. > Allow reading custom build message from a workspace file, in case of > non-success > --

[JIRA] (JENKINS-12927) Changes doesn't trigger a build - "unknown revision"

Marcus Eriksson created JENKINS-12927: - Summary: Changes doesn't trigger a build - "unknown revision" Key: JENKINS-12927 URL: https://issues.jenkins-ci.org/browse/JENKINS-12927 Project: Jenkins

[JIRA] (JENKINS-12881) Allow reading custom build message from a workspace file, in case of non-success

[ https://issues.jenkins-ci.org/browse/JENKINS-12881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12881 started by Joe Hansche. > Allow reading custom build message from a workspace file, in case of > non-success > --

[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases

[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159650#comment-159650 ] Jaroslavas D. commented on JENKINS-12810: - Hi Bruno. I have one question about 3.1

[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )

[ https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159649#comment-159649 ] Nikolay Myakushkin commented on JENKINS-12916: -- Hi, Bruno Thank you for your a

[JIRA] (JENKINS-12925) Build is failed when using Jenkins on windows

[ https://issues.jenkins-ci.org/browse/JENKINS-12925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159648#comment-159648 ] cholan dhamodaran commented on JENKINS-12925: - Is there any update?

[JIRA] (JENKINS-10856) Incorrect Cyrillic symbols in Console output

[ https://issues.jenkins-ci.org/browse/JENKINS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159647#comment-159647 ] Dmitry Sviridov commented on JENKINS-10856: --- Can I push changes in repo?

[JIRA] (JENKINS-10856) Incorrect Cyrillic symbols in Console output

[ https://issues.jenkins-ci.org/browse/JENKINS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159646#comment-159646 ] Dmitry Sviridov commented on JENKINS-10856: --- No. I just clone repository and fix p

[JIRA] (JENKINS-6747) Support concurrent runs of matrix builds

[ https://issues.jenkins-ci.org/browse/JENKINS-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159645#comment-159645 ] Andrew Melo commented on JENKINS-6747: -- I'm in the same boat as the others. We actually

[JIRA] (JENKINS-12037) CLI - I/O error in channel Chunked connection/Unexpected termination of the channel - still occurring in Jenkins 1.449

[ https://issues.jenkins-ci.org/browse/JENKINS-12037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mark streit updated JENKINS-12037: -- Priority: Critical (was: Major) > CLI - I/O error in channel Chunked connection/Unexpect

[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )

[ https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159644#comment-159644 ] Bruno P. Kinoshita commented on JENKINS-12916: -- Hi Nikolay! I just finished r

[JIRA] (JENKINS-12926) Rolling console per executor - when one job finishes, automatically switches to next job on executor

Greg Moncreaff created JENKINS-12926: Summary: Rolling console per executor - when one job finishes, automatically switches to next job on executor Key: JENKINS-12926 URL: https://issues.jenkins-ci.org/browse/

[JIRA] (JENKINS-10856) Incorrect Cyrillic symbols in Console output

[ https://issues.jenkins-ci.org/browse/JENKINS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159643#comment-159643 ] gbois commented on JENKINS-10856: - Could it be closed? > Incorrect Cyrillic

[JIRA] (JENKINS-12730) Going to pages via global shortcuts doesn't use the current url/url set in config

[ https://issues.jenkins-ci.org/browse/JENKINS-12730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandeep Rai reopened JENKINS-12730: --- As per my comment (https://issues.jenkins-ci.org/browse/JENKINS-12730?focusedCommentId=159550&

[JIRA] (JENKINS-6209) Continuous polling bug in svn

[ https://issues.jenkins-ci.org/browse/JENKINS-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pgweiss updated JENKINS-6209: - Description: I have a build where polling always returns: Started on Apr 9, 2010 1:30:48 AM Workspace d

[JIRA] (JENKINS-12730) Going to pages via global shortcuts doesn't use the current url/url set in config

[ https://issues.jenkins-ci.org/browse/JENKINS-12730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann resolved JENKINS-12730. Resolution: Fixed > Going to pages via global shortcuts doesn't use the current url/u

[JIRA] (JENKINS-12730) Going to pages via global shortcuts doesn't use the current url/url set in config

[ https://issues.jenkins-ci.org/browse/JENKINS-12730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159641#comment-159641 ] Alex Lehmann commented on JENKINS-12730: the head version works, looks like the fix

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

[ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159640#comment-159640 ] S P commented on JENKINS-12427: --- yep, thanks for the reminder, however the cron is fine in thi

[JIRA] (JENKINS-12037) CLI - I/O error in channel Chunked connection/Unexpected termination of the channel - still occurring in Jenkins 1.449

[ https://issues.jenkins-ci.org/browse/JENKINS-12037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159639#comment-159639 ] Richard Mortimer commented on JENKINS-12037: If I build a test version for you w

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

[ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159638#comment-159638 ] gbois commented on JENKINS-12427: - OK, Be careful for your cron expression '* * * * *' or '

[JIRA] (JENKINS-12912) URLTtrigger does not poll on jobs which are tied to disconnected slaves

[ https://issues.jenkins-ci.org/browse/JENKINS-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159637#comment-159637 ] gbois commented on JENKINS-12912: - If I understand your use case: If slave are disconnected,

[JIRA] (JENKINS-12912) URLTtrigger does not poll on jobs which are tied to disconnected slaves

[ https://issues.jenkins-ci.org/browse/JENKINS-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12912 started by gbois. > URLTtrigger does not poll on jobs which are tied to disconnected slaves >

[JIRA] (JENKINS-11149) JNLP slave fails to connect if Anonymous has not permission READ

[ https://issues.jenkins-ci.org/browse/JENKINS-11149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159636#comment-159636 ] candrews commented on JENKINS-11149: Still exists in 1.452 > JNLP slave

[JIRA] (JENKINS-12037) CLI - I/O error in channel Chunked connection/Unexpected termination of the channel - still occurring in Jenkins 1.449

[ https://issues.jenkins-ci.org/browse/JENKINS-12037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159635#comment-159635 ] mark streit commented on JENKINS-12037: --- with regard to your question about the cli co

[JIRA] (JENKINS-12924) FSTrigger triggers builds on jenkins restart

[ https://issues.jenkins-ci.org/browse/JENKINS-12924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-12924. - Resolution: Fixed > FSTrigger triggers builds on jenkins restart >

[JIRA] (JENKINS-12924) FSTrigger triggers builds on jenkins restart

[ https://issues.jenkins-ci.org/browse/JENKINS-12924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159634#comment-159634 ] SCM/JIRA link daemon commented on JENKINS-12924: Code changed in jenkins Use

[JIRA] (JENKINS-12208) More information in log file

[ https://issues.jenkins-ci.org/browse/JENKINS-12208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois closed JENKINS-12208. --- Resolution: Won't Fix Yes and no. If FSTrigger monitors a folder with 1000 files, I will not show files in

[JIRA] (JENKINS-12423) Password masked by Mask Passwords are visible when using envinject plugin

[ https://issues.jenkins-ci.org/browse/JENKINS-12423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-12423. - Resolution: Fixed In >Manage Jenkins> Configure System Add global password Then, in the job configurat

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

[ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S P reopened JENKINS-12427: --- > BuildResultTrigger Plug-in not triggering job > -- > >

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

[ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S P updated JENKINS-12427: -- Attachment: TEST-TRY.config-2.xml updated to include more build results > BuildResultTrigger

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

[ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159631#comment-159631 ] S P commented on JENKINS-12427: --- OK, that is weird. The drop downs were selected when I opened

[JIRA] (JENKINS-12634) Java bin files directory installed under subdir on Solaris 8 & 10 sparc

[ https://issues.jenkins-ci.org/browse/JENKINS-12634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159629#comment-159629 ] Loic SF commented on JENKINS-12634: --- I got the same issue. The Sun/Oracle has been instal

[JIRA] (JENKINS-12730) Going to pages via global shortcuts doesn't use the current url/url set in config

[ https://issues.jenkins-ci.org/browse/JENKINS-12730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann reopened JENKINS-12730: > Going to pages via global shortcuts doesn't use the current url/url set in > config >

[JIRA] (JENKINS-12730) Going to pages via global shortcuts doesn't use the current url/url set in config

[ https://issues.jenkins-ci.org/browse/JENKINS-12730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159628#comment-159628 ] Alex Lehmann commented on JENKINS-12730: this is still not working in plugin release

[JIRA] (JENKINS-12925) Build is failed when using Jenkins on windows

cholan dhamodaran created JENKINS-12925: --- Summary: Build is failed when using Jenkins on windows Key: JENKINS-12925 URL: https://issues.jenkins-ci.org/browse/JENKINS-12925 Project: Jenkins

[JIRA] (JENKINS-12423) Password masked by Mask Passwords are visible when using envinject plugin

[ https://issues.jenkins-ci.org/browse/JENKINS-12423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Walter Kacynski reopened JENKINS-12423: --- I'm trying to work thru this issue as well but I can't seem to find the necessary opti

[JIRA] (JENKINS-11222) Mercurial Plugin does not support SCM polling on slaves

[ https://issues.jenkins-ci.org/browse/JENKINS-11222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159626#comment-159626 ] Guillermo Schwarz commented on JENKINS-11222: - Today I reproduced the problem us

[JIRA] (JENKINS-12924) FSTrigger triggers builds on jenkins restart

Jim Searle created JENKINS-12924: Summary: FSTrigger triggers builds on jenkins restart Key: JENKINS-12924 URL: https://issues.jenkins-ci.org/browse/JENKINS-12924 Project: Jenkins Issue Type:

[JIRA] (JENKINS-12452) WallDisplay Plugin incompatible with IE8

[ https://issues.jenkins-ci.org/browse/JENKINS-12452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159625#comment-159625 ] Bart Shappee commented on JENKINS-12452: Additionally, no visible error is presented

[JIRA] (JENKINS-10672) Non-admin users can not see the slave logs. They are not able to launch the slave (even they have CONFIGURE) permission on the slave. They also can not mark the slave to tempora

[ https://issues.jenkins-ci.org/browse/JENKINS-10672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159624#comment-159624 ] Case Taintor commented on JENKINS-10672: Can this fix please be pulled in? It's frus

[JIRA] (JENKINS-10197) Matrix jobs default to "locked" (and are difficult to delete)

[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159623#comment-159623 ] Jason Stanley commented on JENKINS-10197: - This problem also occurs on Jenkins versi

[JIRA] (JENKINS-6962) Unable to delete projects on occasion with jobconfighistory plugin installed when on nfs mount

[ https://issues.jenkins-ci.org/browse/JENKINS-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jacob_robertson resolved JENKINS-6962. -- Resolution: Fixed Putting back to Fixed status. I will open a new ticket.

[JIRA] (JENKINS-6962) Unable to delete projects on occasion with jobconfighistory plugin installed when on nfs mount

[ https://issues.jenkins-ci.org/browse/JENKINS-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159621#comment-159621 ] jacob_robertson commented on JENKINS-6962: -- I think I just really failed to look clo

[JIRA] (JENKINS-12452) WallDisplay Plugin incompatible with IE8

[ https://issues.jenkins-ci.org/browse/JENKINS-12452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159620#comment-159620 ] Bart Shappee commented on JENKINS-12452: I have encountered the same problem in both

[JIRA] (JENKINS-12849) NullPointerException when parsing changeset

[ https://issues.jenkins-ci.org/browse/JENKINS-12849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159619#comment-159619 ] dogfood commented on JENKINS-12849: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/

[JIRA] (JENKINS-12849) NullPointerException when parsing changeset

[ https://issues.jenkins-ci.org/browse/JENKINS-12849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159618#comment-159618 ] SCM/JIRA link daemon commented on JENKINS-12849: Code changed in jenkins Use

[JIRA] (JENKINS-12849) NullPointerException when parsing changeset

[ https://issues.jenkins-ci.org/browse/JENKINS-12849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12849. Resolution: Fixed > NullPointerException when parsing changeset > ---

[JIRA] (JENKINS-12923) Deadlock if one of the triggered projects is deactivated

[ https://issues.jenkins-ci.org/browse/JENKINS-12923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hansgeorg Schwibbe updated JENKINS-12923: - Summary: Deadlock if one of the triggered projects is deactivated (was: Job is

[JIRA] (JENKINS-12923) Job is locked if one of the triggered projects is deactivated

[ https://issues.jenkins-ci.org/browse/JENKINS-12923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159616#comment-159616 ] Hansgeorg Schwibbe commented on JENKINS-12923: -- Another deadlock comes up with

[JIRA] (JENKINS-6962) Unable to delete projects on occasion with jobconfighistory plugin installed when on nfs mount

[ https://issues.jenkins-ci.org/browse/JENKINS-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159617#comment-159617 ] stefanbrausch commented on JENKINS-6962: Maybe is this your problem? http://bugs.sun

[JIRA] (JENKINS-6962) Unable to delete projects on occasion with jobconfighistory plugin installed when on nfs mount

[ https://issues.jenkins-ci.org/browse/JENKINS-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159615#comment-159615 ] jacob_robertson commented on JENKINS-6962: -- Actually, I'm not positive this is the e

[JIRA] (JENKINS-12923) Job is locked if one of the triggered projects is deactivated

[ https://issues.jenkins-ci.org/browse/JENKINS-12923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159614#comment-159614 ] Hansgeorg Schwibbe edited comment on JENKINS-12923 at 2/28/12 2:03 PM: ---

[JIRA] (JENKINS-12923) Job is locked if one of the triggered projects is deactivated

[ https://issues.jenkins-ci.org/browse/JENKINS-12923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159614#comment-159614 ] Hansgeorg Schwibbe edited comment on JENKINS-12923 at 2/28/12 2:01 PM: ---

[JIRA] (JENKINS-12923) Job is locked if one of the triggered projects is deactivated

[ https://issues.jenkins-ci.org/browse/JENKINS-12923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159614#comment-159614 ] Hansgeorg Schwibbe edited comment on JENKINS-12923 at 2/28/12 2:00 PM: ---

[JIRA] (JENKINS-12923) Job is locked if one of the triggered projects is deactivated

[ https://issues.jenkins-ci.org/browse/JENKINS-12923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hansgeorg Schwibbe updated JENKINS-12923: - Attachment: screenshot-1.jpg If "deployMocks" is deactivated, the Job is runnin

[JIRA] (JENKINS-12923) Job is locked if one of the triggered projects is deactivated

[ https://issues.jenkins-ci.org/browse/JENKINS-12923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hansgeorg Schwibbe updated JENKINS-12923: - Description: The "Trigger/call builds on other projects" build step locks the j

[JIRA] (JENKINS-12923) Job is locked if one of the triggered projects is deactivated

[ https://issues.jenkins-ci.org/browse/JENKINS-12923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hansgeorg Schwibbe reassigned JENKINS-12923: Assignee: Kohsuke Kawaguchi (was: Hansgeorg Schwibbe) > Job is locke

[JIRA] (JENKINS-6962) Unable to delete projects on occasion with jobconfighistory plugin installed when on nfs mount

[ https://issues.jenkins-ci.org/browse/JENKINS-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159613#comment-159613 ] jacob_robertson commented on JENKINS-6962: -- I'm still seeing this exact error. I'm

[JIRA] (JENKINS-6962) Unable to delete projects on occasion with jobconfighistory plugin installed when on nfs mount

[ https://issues.jenkins-ci.org/browse/JENKINS-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jacob_robertson reopened JENKINS-6962: -- > Unable to delete projects on occasion with jobconfighistory plugin installed > when

[JIRA] (JENKINS-12923) Job is locked if one of the triggered projects is deactivated

Hansgeorg Schwibbe created JENKINS-12923: Summary: Job is locked if one of the triggered projects is deactivated Key: JENKINS-12923 URL: https://issues.jenkins-ci.org/browse/JENKINS-12923 Proj

[JIRA] (JENKINS-12787) LOADING overlay does not go away on the Configure System page

[ https://issues.jenkins-ci.org/browse/JENKINS-12787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159612#comment-159612 ] Maarten van den Ende commented on JENKINS-12787: Same for Firefox

[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases

[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159611#comment-159611 ] Bruno P. Kinoshita commented on JENKINS-12810: -- Hi Jaroslavas, I was aware of

[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases

[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159610#comment-159610 ] Jaroslavas D. commented on JENKINS-12810: - Bruno, Yes, it would be nice to try it b

[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )

[ https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159609#comment-159609 ] Bruno P. Kinoshita commented on JENKINS-12916: -- Hi Nikolay! > I'm using testli

[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases

[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslavas D. updated JENKINS-12810: Attachment: screenshot20120228152511.jpg screenshot20120228152415.jpg

[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases

[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159608#comment-159608 ] Bruno P. Kinoshita commented on JENKINS-12810: -- Hi there! @Vignesh: I will att

[JIRA] (JENKINS-12369) when upgrading from 1.1.14 to 1.1.15 all git builds shown no succesfull builds on jenkins dashboard

[ https://issues.jenkins-ci.org/browse/JENKINS-12369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159607#comment-159607 ] dogfood commented on JENKINS-12369: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/

[JIRA] (JENKINS-12369) when upgrading from 1.1.14 to 1.1.15 all git builds shown no succesfull builds on jenkins dashboard

[ https://issues.jenkins-ci.org/browse/JENKINS-12369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159606#comment-159606 ] SCM/JIRA link daemon commented on JENKINS-12369: Code changed in jenkins Use

[JIRA] (JENKINS-12922) Support changing maven version to multiple jobs at once using configuration slicing plugin

Eyal Edri created JENKINS-12922: --- Summary: Support changing maven version to multiple jobs at once using configuration slicing plugin Key: JENKINS-12922 URL: https://issues.jenkins-ci.org/browse/JENKINS-12922

[JIRA] (JENKINS-12921) Trigger fails to build with "Null value not allowed as an environment variable: GIT_BRANCH" error

[ https://issues.jenkins-ci.org/browse/JENKINS-12921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159605#comment-159605 ] Ron K commented on JENKINS-12921: - There is also an exception visible in the Jenkins log, w

[JIRA] (JENKINS-12369) when upgrading from 1.1.14 to 1.1.15 all git builds shown no succesfull builds on jenkins dashboard

[ https://issues.jenkins-ci.org/browse/JENKINS-12369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159604#comment-159604 ] dogfood commented on JENKINS-12369: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/

[JIRA] (JENKINS-12369) when upgrading from 1.1.14 to 1.1.15 all git builds shown no succesfull builds on jenkins dashboard

[ https://issues.jenkins-ci.org/browse/JENKINS-12369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12369. Resolution: Fixed > when upgrading from 1.1.14 to 1.1.15 all git buil

[JIRA] (JENKINS-12369) when upgrading from 1.1.14 to 1.1.15 all git builds shown no succesfull builds on jenkins dashboard

[ https://issues.jenkins-ci.org/browse/JENKINS-12369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159603#comment-159603 ] SCM/JIRA link daemon commented on JENKINS-12369: Code changed in jenkins Use

[JIRA] (JENKINS-12921) Trigger fails to build with "Null value not allowed as an environment variable: GIT_BRANCH" error

[ https://issues.jenkins-ci.org/browse/JENKINS-12921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron K updated JENKINS-12921: Summary: Trigger fails to build with "Null value not allowed as an environment variable: GIT_BRANCH" erro

[JIRA] (JENKINS-12921) Trigger fails to build with "ull value not allowed as an environment variable: GIT_BRANCH" error

Ron K created JENKINS-12921: --- Summary: Trigger fails to build with "ull value not allowed as an environment variable: GIT_BRANCH" error Key: JENKINS-12921 URL: https://issues.jenkins-ci.org/browse/JENKINS-12921

[JIRA] (JENKINS-12369) when upgrading from 1.1.14 to 1.1.15 all git builds shown no succesfull builds on jenkins dashboard

[ https://issues.jenkins-ci.org/browse/JENKINS-12369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159602#comment-159602 ] Nicolas De Loof commented on JENKINS-12369: --- git bisect to the rescue, this regres

[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases

[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159591#comment-159591 ] Jaroslavas D. edited comment on JENKINS-12810 at 2/28/12 12:00 PM: ---

[JIRA] (JENKINS-12369) when upgrading from 1.1.14 to 1.1.15 all git builds shown no succesfull builds on jenkins dashboard

[ https://issues.jenkins-ci.org/browse/JENKINS-12369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159601#comment-159601 ] Nicolas De Loof commented on JENKINS-12369: --- I can reproduce the issue : git co g

[JIRA] (JENKINS-12510) Custom xcodebuild arguments values are not persisted

[ https://issues.jenkins-ci.org/browse/JENKINS-12510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159600#comment-159600 ] Simon Strandgaard commented on JENKINS-12510: - Since I upgraded to Xcode 4.3, I

[JIRA] (JENKINS-12302) Remote call on CLI channel from [ip] failed

[ https://issues.jenkins-ci.org/browse/JENKINS-12302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159599#comment-159599 ] dogfood commented on JENKINS-12302: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/

[JIRA] (JENKINS-12920) LDAP autentication has incorrect credentials for user

Radek Chromy created JENKINS-12920: -- Summary: LDAP autentication has incorrect credentials for user Key: JENKINS-12920 URL: https://issues.jenkins-ci.org/browse/JENKINS-12920 Project: Jenkins

[JIRA] (JENKINS-12919) RSS-feed. Title is missing when job is running.

Jeroen Knoops created JENKINS-12919: --- Summary: RSS-feed. Title is missing when job is running. Key: JENKINS-12919 URL: https://issues.jenkins-ci.org/browse/JENKINS-12919 Project: Jenkins Is

[JIRA] (JENKINS-12302) Remote call on CLI channel from [ip] failed

[ https://issues.jenkins-ci.org/browse/JENKINS-12302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12302. Resolution: Fixed > Remote call on CLI channel from [ip] failed > ---

[JIRA] (JENKINS-12302) Remote call on CLI channel from [ip] failed

[ https://issues.jenkins-ci.org/browse/JENKINS-12302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159598#comment-159598 ] SCM/JIRA link daemon commented on JENKINS-12302: Code changed in jenkins Use

[JIRA] (JENKINS-12917) New Disk Usage Link in LHS menu navigates to incorrect URL when clicked from non-default views

[ https://issues.jenkins-ci.org/browse/JENKINS-12917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159597#comment-159597 ] dogfood commented on JENKINS-12917: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/

[JIRA] (JENKINS-12917) New Disk Usage Link in LHS menu navigates to incorrect URL when clicked from non-default views

[ https://issues.jenkins-ci.org/browse/JENKINS-12917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159596#comment-159596 ] SCM/JIRA link daemon commented on JENKINS-12917: Code changed in jenkins Use

[JIRA] (JENKINS-12917) New Disk Usage Link in LHS menu navigates to incorrect URL when clicked from non-default views

[ https://issues.jenkins-ci.org/browse/JENKINS-12917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12917. Resolution: Fixed > New Disk Usage Link in LHS menu navigates to inco

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

[ https://issues.jenkins-ci.org/browse/JENKINS-12619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159595#comment-159595 ] Flominator commented on JENKINS-12619: -- Same here on Windows XP Pro SP2. We went back t