date:20120417


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161679#comment-161679
 ] 

SCM/JIRA link daemon commented on JENKINS-13476:


Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/26974746d68043825f02abbc0c8ab6200e8d465f
Log:
  [FIXED JENKINS-13476] added filter to the update center.


Compare: https://github.com/jenkinsci/jenkins/compare/246be7c...2697474



 Broken user experience when searching on /pluginManager/available
 -

 Key: JENKINS-13476
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13476
 Project: Jenkins
  Issue Type: Bug
  Components: ui-changes
Affects Versions: current
 Environment: Jenkins 1.460
Reporter: sebastian_bergmann
 Attachments: screenshot.png


 1. Browse to /pluginManager/available
 2. CTRL+F (Find in Mozilla Firefox)
 3. Enter Git, for instance
 4. Browser scrolls to the location of the search result
 5. Search result is hidden behind the Install ... / Download ... overlay

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13476) Broken user experience when searching on /pluginManager/available


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

SCM/JIRA link daemon resolved JENKINS-13476.


Resolution: Fixed

 Broken user experience when searching on /pluginManager/available
 -

 Key: JENKINS-13476
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13476
 Project: Jenkins
  Issue Type: Bug
  Components: ui-changes
Affects Versions: current
 Environment: Jenkins 1.460
Reporter: sebastian_bergmann
 Attachments: screenshot.png


 1. Browse to /pluginManager/available
 2. CTRL+F (Find in Mozilla Firefox)
 3. Enter Git, for instance
 4. Browser scrolls to the location of the search result
 5. Search result is hidden behind the Install ... / Download ... overlay

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13479) HTML Publisher plugin deos not handle JQuert javascript correcty

2012-04-17 Thread florijn.pe...@gmail.com (JIRA)

Peter Florijn created JENKINS-13479:
---

 Summary: HTML Publisher plugin deos not handle JQuert javascript 
correcty
 Key: JENKINS-13479
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13479
 Project: Jenkins
  Issue Type: Bug
  Components: plugin
Affects Versions: current
 Environment: OSX, Firefox
Reporter: Peter Florijn
Priority: Minor


HTML Publisher plugin does not work correctly when the HTM file contains JQuery 
javascript.

A HTML testreport produced with prove -P HTML does not handle the jQuery 
collapse javascript behaviour. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13479) HTML Publisher plugin does not handle JQuery javascript correcty

2012-04-17 Thread florijn.pe...@gmail.com (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Florijn reassigned JENKINS-13479:
---

Assignee: mcrooney

 HTML Publisher plugin does not handle JQuery javascript correcty
 

 Key: JENKINS-13479
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13479
 Project: Jenkins
  Issue Type: Bug
  Components: plugin
Affects Versions: current
 Environment: OSX, Firefox
Reporter: Peter Florijn
Assignee: mcrooney
Priority: Minor
  Labels: plugin

 HTML Publisher plugin does not work correctly when the HTM file contains 
 JQuery javascript.
 A HTML testreport produced with prove -P HTML does not handle the jQuery 
 collapse javascript behaviour. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13479) HTML Publisher plugin does not handle JQuery javascript correcty

2012-04-17 Thread florijn.pe...@gmail.com (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Florijn updated JENKINS-13479:


Description: 
HTML Publisher plugin does not work correctly when the HTML file contains 
JQuery javascript.

A HTML testreport produced with prove -P HTML does not handle the jQuery 
collapse javascript behaviour. 

  was:
HTML Publisher plugin does not work correctly when the HTM file contains JQuery 
javascript.

A HTML testreport produced with prove -P HTML does not handle the jQuery 
collapse javascript behaviour. 


 HTML Publisher plugin does not handle JQuery javascript correcty
 

 Key: JENKINS-13479
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13479
 Project: Jenkins
  Issue Type: Bug
  Components: plugin
Affects Versions: current
 Environment: OSX, Firefox
Reporter: Peter Florijn
Assignee: mcrooney
Priority: Minor
  Labels: plugin

 HTML Publisher plugin does not work correctly when the HTML file contains 
 JQuery javascript.
 A HTML testreport produced with prove -P HTML does not handle the jQuery 
 collapse javascript behaviour. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-9531) choose matrix build nodes based on label matches

2012-04-17 Thread br...@whamcloud.com (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-9531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161681#comment-161681
]

Brian Murrell commented on JENKINS-9531:

{quote}
Couldn't you use the label specifier el5 lab?
{quote}

If I could, I would. But I don't see how I could. For matrix jobs, I can add
axes for the various combinations I want built. How do I specify the kind of
free-form eligible node specifier you describe above?

(As I am sure you know, but for the benefit of others reading here) note that
the Combination filter is not the place to do this. That filters the
combinations that will actually be built. I don't want to do that. I want to
filter the nodes that are eligible for any of the given combinations once a
list of nodes has been selected for a given combination.

I might also want to be able to filter on a negative expression like !lab so
that some jobs can specify el5 and be eligible on all 4 builders but others
with '!lab are not allowed to run on the lab labelled builders.

choose matrix build nodes based on label matches

Key: JENKINS-9531
URL: https://issues.jenkins-ci.org/browse/JENKINS-9531
Project: Jenkins
Issue Type: Improvement
Components: matrix
Reporter: Brian Murrell

With matrix (multiconfiguration) build jobs one can select (groups of) slaves
to build the job on with the axes. It would be nice if when an axis matches
multiple nodes (i.e. a label that applies to more than one node, such as
x86_64) the node list could be further filtered by (not) matching more labels.
For example, say I have a list of nodes with the following labels:
builder1: el5 x86_64
builder2: el5 i686
builder3: el5 x86_64 lab
builder4: el5 i686 lab
If one of my axis specifications is el5 then any one of the above nodes
would be selected as a slave to build on. However, what would be nice is to
have a further filter on the selected nodes, like lab, so that even though
the axis specification of el5 would match any of the available 4 nodes,
that additional lab filter would mean that only builder3 and builder4 are
eligible nodes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13480) Http HEAD request returns body

2012-04-17 Thread jenkin...@mailinator.com (JIRA)

a b created JENKINS-13480:
-

 Summary: Http HEAD request returns body
 Key: JENKINS-13480
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13480
 Project: Jenkins
  Issue Type: Bug
  Components: other
Affects Versions: current
Reporter: a b


Grab the war (just verified again with 1.460) and run with 'java -jar 
jenkins.war'. Then send a HEAD request and observe that the server returns a 
body (this is best done by using 'telnet localhost 8080' and sending 'HEAD / 
HTTP/1.0' - tools like curl and lwp-request will suppress any received body).

This specifically causes issues with the Eclipse Mylyn plugin as that sends a 
HEAD request followed by a GET - because the connection is kept alive between 
the two requests, the parsing of the second response fails since it tries to 
parse the body from the HEAD as the http response headers of the GET.

Note that running Jenkins in Tomcat does not have this issue.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13481) Deleting a project takes you to view All and not the Default view set in the configuration

2012-04-17 Thread monc...@raytheon.com (JIRA)

Greg Moncreaff created JENKINS-13481:


 Summary: Deleting a project takes you to view All and not the 
Default view set in the configuration
 Key: JENKINS-13481
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13481
 Project: Jenkins
  Issue Type: Bug
  Components: cobertura
Reporter: Greg Moncreaff
Assignee: stephenconnolly




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13481) Deleting a project takes you to view All and not the Default view set in the configuration

2012-04-17 Thread monc...@raytheon.com (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Greg Moncreaff updated JENKINS-13481:
-

Component/s: core
 (was: cobertura)

 Deleting a project takes you to view All and not the Default view set in 
 the configuration
 --

 Key: JENKINS-13481
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13481
 Project: Jenkins
  Issue Type: Bug
  Components: core
Reporter: Greg Moncreaff
Assignee: stephenconnolly



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-10905) Deleting previous project files regularly fails the build


[ 
https://issues.jenkins-ci.org/browse/JENKINS-10905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161682#comment-161682
 ] 

pjdarton commented on JENKINS-10905:


I'm glad it's not just me - I keep getting these as well.
In my case, it's from the Accurev plugin calling 
hudson.Util.deleteContentsRecursive and getting spurious errors from the 
filesystem.

I believe that the underlying cause is an operating system bug, either that or 
a very common misconfiguration, as I (sometimes) get the same problems doing 
rd /s /q xxx from a CMD window, and (sometimes) find that Explorer fails to 
delete everything when doing a Shift+Delete on directories.
i.e. I think that Windows sometimes locks files briefly, causing deletes to 
fail.
Note: I've configured the Windows Search service to leave well alone, and also 
the anti-virus, so I don't think it's them - I've had these problems from both 
of those on previous versions of Windows, but on Windows 7 it doesn't seem to 
be enough.

However, regardless of the cause of the problem, the workaround is probably to 
delete everything that can be deleted, and to retry a number of times until 
either all files are deleted, or we've exhausted the retries.
I wouldn't call it a blocker though - just triggering the build again usually 
makes the problem disappear.  i.e. it's as annoying as hell, but it isn't a 
blocker.

 Deleting previous project files regularly fails the build
 -

 Key: JENKINS-10905
 URL: https://issues.jenkins-ci.org/browse/JENKINS-10905
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
 Environment: Window 7 operating in master/slave environment (the 
 failing machine is the slave)
Reporter: nyoung02
Priority: Blocker

 I have a project that is quite large. I'm not sure if it's coincidental or 
 not, but since upgrading to 1.428, I've been getting a number of intermittent 
 build failures, that actually fail in the cleanup stage deleting files from 
 the previous build. My svn settings are set to 'clean checkout' although I 
 also get this problem if I select 'revert and update'. Is it possible to make 
 this stage more tolerant of locked files (perhaps by increasing the number of 
 retries?)
 09:51:40  Started by user niy
 09:51:40  Building remotely on nwb-r5win32b
 09:51:40  Cleaning workspace C:\jenkins\workspace\R5_Win_Overnight
 09:52:29  hudson.util.IOException2: remote file operation failed: 
 c:\jenkins\workspace\R5_Win_Overnight at 
 hudson.remoting.Channel@470d6c27:nwb-r5win32b
 09:52:29  at hudson.FilePath.act(FilePath.java:754)
 09:52:29  at hudson.FilePath.act(FilePath.java:740)
 09:52:29  at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:731)
 09:52:29  at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:676)
 09:52:29  at 
 hudson.model.AbstractProject.checkout(AbstractProject.java:1193)
 09:52:29  at 
 hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:555)
 09:52:29  at 
 hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:443)
 09:52:29  at hudson.model.Run.run(Run.java:1376)
 09:52:29  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
 09:52:29  at 
 hudson.model.ResourceController.execute(ResourceController.java:88)
 09:52:29  at hudson.model.Executor.run(Executor.java:230)
 09:52:29  Caused by: java.io.IOException: Unable to delete 
 c:\jenkins\workspace\R5_Win_Overnight\viscob\coretech\checker\src\tools\.svn 
 - files in dir: 
 [c:\jenkins\workspace\R5_Win_Overnight\viscob\coretech\checker\src\tools\.svn\tmp]
 09:52:29  at hudson.Util.deleteFile(Util.java:265)
 09:52:29  at hudson.Util.deleteRecursive(Util.java:316)
 09:52:29  at hudson.Util.deleteContentsRecursive(Util.java:227)
 09:52:29  at hudson.Util.deleteRecursive(Util.java:307)
 09:52:29  at hudson.Util.deleteContentsRecursive(Util.java:227)
 09:52:29  at hudson.Util.deleteRecursive(Util.java:307)
 09:52:29  at hudson.Util.deleteContentsRecursive(Util.java:227)
 09:52:29  at hudson.Util.deleteRecursive(Util.java:307)
 09:52:29  at hudson.Util.deleteContentsRecursive(Util.java:227)
 09:52:29  at hudson.Util.deleteRecursive(Util.java:307)
 09:52:29  at hudson.Util.deleteContentsRecursive(Util.java:227)
 09:52:29  at hudson.Util.deleteRecursive(Util.java:307)
 09:52:29  at hudson.Util.deleteContentsRecursive(Util.java:227)
 09:52:29  at 
 hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:74)
 09:52:29  at 
 hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136)
 09:52:29  at 
 hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:773)
 09:52:29  at

[JIRA] (JENKINS-3053) Unable to delete SCM files


[ 
https://issues.jenkins-ci.org/browse/JENKINS-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161683#comment-161683
 ] 

pjdarton commented on JENKINS-3053:
---

The usual cause of this sort of problem on Windows is either the Windows Search 
service indexing the files that Hudson/Jenkins is trying to delete, or the 
Anti-Virus trying to check the files that Hudson/Jenkins is trying to delete.

However, I've found that on Windows 7, configuring both of those to leave well 
alone isn't enough to prevent this.
JENKINS-10905 is reporting the same kind of issue.

 Unable to delete SCM files
 --

 Key: JENKINS-3053
 URL: https://issues.jenkins-ci.org/browse/JENKINS-3053
 Project: Jenkins
  Issue Type: Bug
  Components: subversion
Affects Versions: current
 Environment: Platform: PC, OS: All
Reporter: jfdionne

 When our projects are under source code management(in our case SVN) an error
 occurs while trying to delete the associated project workspace before the
 checkout. This always leads to a failed project and it forces us to do the
 remove workspace and checkout directly from the execute shell. It happens
 randomly, file permissions allow us to delete the files and there is no other
 concurrent process that could have a handle on these files.
 Hudson is at the latest version on a Windows Server Enterprise 2007 machine. 
 started
 FATAL: Unable to delete
 D:\hudson_config\jobs\Trunk\workspace\trunk\win32\DebuggingApps\obj\netborder_win32_vc8\DetermineAddress.obj
 java.io.IOException: Unable to delete
 D:\hudson_config\jobs\Trunk\workspace\trunk\win32\DebuggingApps\obj\netborder_win32_vc8\DetermineAddress.obj
   at hudson.Util.deleteFile(Util.java:212)
   at hudson.Util.deleteRecursive(Util.java:244)
   at hudson.Util.deleteContentsRecursive(Util.java:178)
   at hudson.Util.deleteRecursive(Util.java:243)
   at hudson.Util.deleteContentsRecursive(Util.java:178)
   at hudson.Util.deleteRecursive(Util.java:243)
   at hudson.Util.deleteContentsRecursive(Util.java:178)
   at hudson.Util.deleteRecursive(Util.java:243)
   at hudson.Util.deleteContentsRecursive(Util.java:178)
   at hudson.Util.deleteRecursive(Util.java:243)
   at hudson.Util.deleteContentsRecursive(Util.java:178)
   at hudson.Util.deleteRecursive(Util.java:243)
   at hudson.Util.deleteContentsRecursive(Util.java:178)
   at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:460)
   at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:405)
   at hudson.FilePath.act(FilePath.java:389)
   at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:398)
   at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:347)
   at hudson.model.AbstractProject.checkout(AbstractProject.java:681)
   at 
 hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:264)
   at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:238)
   at hudson.model.Run.run(Run.java:842)
   at hudson.model.Build.run(Build.java:88)
   at hudson.model.ResourceController.execute(ResourceController.java:70)
   at hudson.model.Executor.run(Executor.java:90)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-10905) Deleting previous project files regularly fails the build

[
https://issues.jenkins-ci.org/browse/JENKINS-10905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161682#comment-161682
]

pjdarton edited comment on JENKINS-10905 at 4/17/12 2:23 PM:
-

I'm glad it's not just me - I keep getting these as well.
In my case, it's from the Accurev plugin calling
hudson.Util.deleteContentsRecursive and getting spurious errors from the
filesystem.

I believe that the underlying cause is an operating system bug, either that or
a very common misconfiguration, as I (sometimes) get the same problems doing
rd /s /q xxx from a CMD window, and (sometimes) find that Explorer fails to
delete everything when doing a Shift+Delete on directories.
i.e. I think that Windows sometimes locks files briefly, causing deletes to
fail.
Note: I've configured the Windows Search service to leave well alone, and also
the anti-virus, so I don't think it's them - I've had these problems from both
of those on previous versions of Windows, but on Windows 7 it doesn't seem to
be enough.

However, regardless of the cause of the problem, the workaround is probably to
delete everything that can be deleted, and to retry a number of times until
either all files are deleted, or we've exhausted the retries.
I wouldn't call it a blocker though - just triggering the build again usually
makes the problem disappear. i.e. it's as annoying as hell, but it isn't a
blocker.

Note: JENKINS-3052 appears to be reporting the same problem.

was (Author: pjdarton):
I'm glad it's not just me - I keep getting these as well.
In my case, it's from the Accurev plugin calling
hudson.Util.deleteContentsRecursive and getting spurious errors from the
filesystem.

Deleting previous project files regularly fails the build
-

Key: JENKINS-10905
URL: https://issues.jenkins-ci.org/browse/JENKINS-10905
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Environment: Window 7 operating in master/slave environment (the
failing machine is the slave)
Reporter: nyoung02
Priority: Blocker

I have a project that is quite large. I'm not sure if it's coincidental or
not, but since upgrading to 1.428, I've been getting a number of intermittent
build failures, that actually fail in the cleanup stage deleting files from
the previous build. My svn settings are set to 'clean checkout' although I
also get this problem if I select 'revert and update'. Is it possible to make
this stage more tolerant of locked files (perhaps by increasing the number of
retries?)
09:51:40 Started by user niy
09:51:40 Building remotely on nwb-r5win32b
09:51:40 Cleaning workspace C:\jenkins\workspace\R5_Win_Overnight
09:52:29 hudson.util.IOException2: remote file operation failed:
c:\jenkins\workspace\R5_Win_Overnight at
hudson.remoting.Channel@470d6c27:nwb-r5win32b
09:52:29 at hudson.FilePath.act(FilePath.java:754)
09:52:29 at hudson.FilePath.act(FilePath.java:740)
09:52:29 at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:731)
09:52:29 at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:676)
09:52:29 at
hudson.model.AbstractProject.checkout(AbstractProject.java:1193)
09:52:29 at
hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:555)
09:52:29 at
hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:443)
09:52:29 at hudson.model.Run.run(Run.java:1376)
09:52:29 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
09:52:29 at
hudson.model.ResourceController.execute(ResourceController.java:88)
09:52:29 at hudson.model.Executor.run(Executor.java:230)
09:52:29 Caused by: java.io.IOException:

[JIRA] (JENKINS-10905) Deleting previous project files regularly fails the build

[
https://issues.jenkins-ci.org/browse/JENKINS-10905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161682#comment-161682
]

pjdarton edited comment on JENKINS-10905 at 4/17/12 2:24 PM:
-

I'm glad it's not just me - I keep getting these as well.
In my case, it's from the Accurev plugin calling
hudson.Util.deleteContentsRecursive and getting spurious errors from the
filesystem.

Note: JENKINS-3053 appears to be reporting the same problem.

Note: JENKINS-3052 appears to be reporting the same problem.

Deleting previous project files regularly fails the build
-

[JIRA] (JENKINS-13482) Summary-graph of all trends

2012-04-17 Thread ander...@java.net (JIRA)

anderius created JENKINS-13482:
--

 Summary: Summary-graph of all trends
 Key: JENKINS-13482
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13482
 Project: Jenkins
  Issue Type: New Feature
  Components: performance-plugin
Reporter: anderius
Assignee: Manuel Carrasco
Priority: Minor


If the build produces several graphs, it would be very useful to be able to 
monitor overall performance with ONE graph, that (for example) displayed all 
trends, average time in different colors, with labels.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-3197) RFE: Use AccuRev server without doing logins


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pjdarton resolved JENKINS-3197.
---

Resolution: Fixed

The changes done as part of JENKINS-9629 effectively resolves this issue, in 
that it prevents logins from interfering any more than necessary.

 RFE: Use AccuRev server without doing logins
 

 Key: JENKINS-3197
 URL: https://issues.jenkins-ci.org/browse/JENKINS-3197
 Project: Jenkins
  Issue Type: Improvement
  Components: accurev
Affects Versions: current
 Environment: Platform: All, OS: All
Reporter: vessel
Assignee: Scott Tatum

 Hi,
 in case there is only one AccuRev server around, it would be sufficient to 
 have
 a cronjob in the background that sets a permanent AccuRev login token (login
 -n) and then Hudson itself does not have to do logins anymore.
 Currently, all of our Hudson jobs for safety do also login to AccuRev (there 
 are
 jobs that do not use the Hudson AccuRev stream configuration feature), which
 means we have many many login operations every day, sometimes we get failures
 because job logins interfer with Hudson logins, sometimes Hudson takes a long
 time (or hangs) when Authenticating with AccuRev.
 We could get rid of that if Hudson only tried to login to a server if there 
 is a
 user name specified in the AccuRev server configuration.
 Thanks!
 Thomas

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

2012-04-17 Thread fri...@gmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161685#comment-161685
 ] 

frew schmidt commented on JENKINS-12927:


I have the opposite problem with two git repos, that is, no changes and it 
still makes a build.  I got around it by just not using the Multiple SCM 
plugin, setting up a single repo, and then using the shell to check out the 
other one and update it.  Sucks though.

 Changes doesn't trigger a build - unknown revision
 

 Key: JENKINS-12927
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12927
 Project: Jenkins
  Issue Type: Bug
  Components: multiple-scms
Affects Versions: current
 Environment: RHEL 6, Mercurial 1.4, Jenkins 1.452
Reporter: Marcus Eriksson
Assignee: Kevin Bell

 With two Mercurial repositories configured, even though the plug-in detects a 
 changeset it still doesn't trigger a new build because it is referring to a 
 (previous?) known revision.
 Here's the polling log from where it detects a change:
 Started on Feb 29, 2012 7:41:20 AM
 [public] $ /usr/bin/hg pull --rev default
 pulling from http://gbglcrd10/hg/jsf/
 searching for changes
 adding changesets
 adding manifests
 adding file changes
 added 1 changesets with 2 changes to 2 files
 (run 'hg update' to get a working copy)
 [public] $ /usr/bin/hg log --style 
 /ssd/Jenkins/jobs/newjsf/workspace/tmp5480491059555742578style --branch 
 default --no-merges --prune 8ee1ae92f8aa040c970d64c992ece871b994dab9
 abort: unknown revision '8ee1ae92f8aa040c970d64c992ece871b994dab9'!
 [private] $ /usr/bin/hg pull --rev default
 pulling from http://gbglcrd10/hg-jsf/licensing/
 no changes found
 [private] $ /usr/bin/hg log --style 
 /ssd/Jenkins/jobs/newjsf/workspace/tmp4214498074041391865style --branch 
 default --no-merges --prune 8ee1ae92f8aa040c970d64c992ece871b994dab9
 Done. Took 0.92 sec
 No changes
 Is this revision coming from the second configured repository? In any case, 
 this always fails.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-5730) Dispatch transactions trigger a build


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pjdarton resolved JENKINS-5730.
---

Resolution: Fixed

That release got done some time ago - marking as resolved.

 Dispatch transactions trigger a build
 -

 Key: JENKINS-5730
 URL: https://issues.jenkins-ci.org/browse/JENKINS-5730
 Project: Jenkins
  Issue Type: Bug
  Components: accurev
Affects Versions: current
Reporter: ajanes
Assignee: Scott Tatum

 The accurev plugin sees the dispatch transactions as a trigger to run a 
 build. Transactions with a type of dispatch are accuwork changes and do not 
 have any file changes. The only transaction typs I am interested in are 
 promote transactions. Is there a way to specify the transaction type to 
 trigger a build? I want to ignore all dispatch transactions.
 Here is the changes page. The file change is the promote transactions 48953 
 and 48952. The others are dispatch changes that trigger a build
 Changes
 #4 (Feb 22, 2010 12:21:18 PM)
 48957. —administrator/detail
 48956. —administrator/detail
 #3 (Feb 22, 2010 12:15:53 PM)
 48955. —administrator/detail
 #2 (Feb 22, 2010 12:10:53 PM)
 48954. —administrator/detail
 #1 (Feb 22, 2010 12:00:51 PM)
 48953. This is a valid change. —user/detail
 48952. Another valid change. —user/detail
 Here is the accurev history for the transaction
 C:\egaming_es_qc_buildaccurev hist -t 48957 -fx
 AcResponse
 Command=hist
 TaskId=851102
   transaction
   id=48957
   type=dispatch
   time=1266855575
   user=administrator/
 /AcResponse

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13483) Hide snapshots created by accurev plugin

pjdarton created JENKINS-13483:
--

 Summary: Hide snapshots created by accurev plugin
 Key: JENKINS-13483
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13483
 Project: Jenkins
  Issue Type: Improvement
  Components: accurev
Reporter: pjdarton
Assignee: pjdarton
Priority: Minor


I'm finding that the accurev show streams command takes forever to run, and 
this causes the AccuRev GUI program's View Streams panel to take forever to 
load.  I've also found that I have an awful lot of snapshots in my stream, most 
of which were created by the accurev plugin.

It would be nice if these didn't appear, and the best way of making them not 
appear would be to do an accurev remove stream XXX on the snapshot that was 
created.
(whether a stream is removed or not doesn't have any functional effect on it)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13485) Subversion 1.7 Support

2012-04-17 Thread jtruel...@kingstreet.com (JIRA)

J T created JENKINS-13485:
-

 Summary: Subversion 1.7 Support
 Key: JENKINS-13485
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13485
 Project: Jenkins
  Issue Type: Improvement
  Components: subversion
 Environment: Jenkins 1.460 on Windows 7
Jenkins Subversion Plug-in 1.39
Reporter: J T


Any idea when Jenkins will support Subversion 1.7? It's been out for quite a 
while, 1.8 will be out soon, and we've moved on to 1.7 but have to keep Jenkins 
back at 1.6 which can cause a number of headaches.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7

2012-04-17 Thread jtruel...@kingstreet.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161690#comment-161690
 ] 

J T commented on JENKINS-11381:
---

Any updates on this? It appears there is a stable release of SVNKit which 
supports 1.7

 Subversion Plugin does not support Subversion 1.7
 -

 Key: JENKINS-11381
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
 Project: Jenkins
  Issue Type: Improvement
  Components: subversion
Reporter: soundworker
Priority: Blocker



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13485) Subversion 1.7 Support

2012-04-17 Thread jtruel...@kingstreet.com (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J T resolved JENKINS-13485.
---

Resolution: Duplicate

duplicate of https://issues.jenkins-ci.org/browse/JENKINS-11381

 Subversion 1.7 Support
 --

 Key: JENKINS-13485
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13485
 Project: Jenkins
  Issue Type: Improvement
  Components: subversion
 Environment: Jenkins 1.460 on Windows 7
 Jenkins Subversion Plug-in 1.39
Reporter: J T

 Any idea when Jenkins will support Subversion 1.7? It's been out for quite a 
 while, 1.8 will be out soon, and we've moved on to 1.7 but have to keep 
 Jenkins back at 1.6 which can cause a number of headaches.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13487) Junit-attachments plugin not retaining long output

2012-04-17 Thread mythriki...@gmail.com (JIRA)

Kiran P created JENKINS-13487:
-

 Summary: Junit-attachments plugin not retaining long output
 Key: JENKINS-13487
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13487
 Project: Jenkins
  Issue Type: Bug
  Components: junit-attachments
Affects Versions: current
 Environment: Current Jenkins version is 1.451
Junit-attachments version is 1.2
Reporter: Kiran P
Assignee: huybrechts


Test reports publish failed test log. Attachments plugin list files before 
this log. When there are too many test cases in a Test, the file list is large. 
Plugin is not retaining the complete file list and log that follows the list. I 
think it has some limit. Plugin is not inheriting 'Retain long output' option 
from parent.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13317) Mail not sent: NullPointerException in plugins.ContentBuilder.transformText(ContentBuilder.java:68)

2012-04-17 Thread harold.shins...@sap.com (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shinsato resolved JENKINS-13317.


Fix Version/s: current
   Resolution: Fixed

This was fixed in 2.20

 Mail not sent: NullPointerException in 
 plugins.ContentBuilder.transformText(ContentBuilder.java:68)
 ---

 Key: JENKINS-13317
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13317
 Project: Jenkins
  Issue Type: Bug
  Components: email-ext
Affects Versions: current
 Environment: jdk1.6.0_29  Linux
Reporter: Chris J
Assignee: shinsato
Priority: Blocker
  Labels: email-ext, exception, plugin
 Fix For: current

 Attachments: email-ext.hpi


 email-ext fails with a NullPointerException when sending some emails (not 
 all).
 I am not a java developer but if someone could send me a version of email-ext 
 having this line (ContentBuilder.java:68) devided in several lines, next time 
 it fails we could locate more precisely the error.
 Here is the stack I have:
 --
 Build step 'Execute shell' marked build as failure
 Email was triggered for: Failure
 Sending email for trigger: Failure
 ERROR: Could not send email as a part of the post-build publishers.
 java.lang.NullPointerException
   at java.util.regex.Matcher.quoteReplacement(Matcher.java:598)
   at 
 hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:68)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.setSubject(ExtendedEmailPublisher.java:463)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:311)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:259)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:251)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:211)
   at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
   at 
 hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
   at 
 hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678)
   at 
 hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656)
   at hudson.model.Build$RunnerImpl.cleanUp(Build.java:171)
   at hudson.model.Run.run(Run.java:1454)
   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:238)
 Finished: FAILURE

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13469) Prototype.Selector is undefined


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161693#comment-161693
 ] 

domi commented on JENKINS-13469:


which version of the plugin and Jenkins are you using?

 Prototype.Selector is undefined
 ---

 Key: JENKINS-13469
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13469
 Project: Jenkins
  Issue Type: Bug
  Components: conditional-buildstep
Affects Versions: current
 Environment: IE 8, IE 9, Firefox 11.
Reporter: James Lee
Assignee: domi
Priority: Blocker

 Try to add 2 or more conditional steps, without success.  Can only add 1.  
 Firefox error console showed the following:
 Prototype.Selector is undefined
 Source File: http://localhost/static/c5afde5e/scripts/behavior.js
 Line: 132

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13468) Would like to create/use a central catalog . . .


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161694#comment-161694
 ] 

domi commented on JENKINS-13468:


That sounds like a good idea and actually the current implementation does 
already allow you to do something in the same direction...

The directory at 'JENKINS_HOME/scriptler/scripts' gets synchronized at every 
startup of Jenkins and automatically imports every *.groovy file. I agree, this 
is not perfect yet, but It might help you to get started.
Based on that functionality I could think of a second (userdefined) directory 
where you could just dump new scripts and we could add some 
functionality/button to trigger the sync - instead of having to restart Jenkins.
I'll think about it a bit more, but I'm sure we can do something useful here...

 Would like to create/use a central catalog . . .
 --

 Key: JENKINS-13468
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13468
 Project: Jenkins
  Issue Type: New Feature
  Components: scriptler
 Environment: Windows . . .
Reporter: Frank Merrow
Assignee: domi

 We have a large and growing number of Jenkins instances . . . We don't have 
 many Groovy script, but rather than carrying them around by hand, it would be 
 nice to be able to put them in once place (network share for instance) and 
 access them from any Jenkins.
 Note this isn't exactly like your public repositories, because I don't want 
 to have to import them . . . while certain scripts might be local to a given 
 Jenkins, for the global Jenkins script . . . if they are changed in one 
 Jenkins, I would like that update to appear for all Jenkins attached to the 
 repository.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13469) Prototype.Selector is undefined


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161693#comment-161693
 ] 

domi edited comment on JENKINS-13469 at 4/17/12 6:03 PM:
-

Which version of the conditional-buildstep-plugin and Jenkins are you using?

I only know this error from the mangaaged-scripts-plugin, ant there it should 
be fixed with the latest version...

  was (Author: domi):
which version of the plugin and Jenkins are you using?
  
 Prototype.Selector is undefined
 ---

 Key: JENKINS-13469
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13469
 Project: Jenkins
  Issue Type: Bug
  Components: conditional-buildstep
Affects Versions: current
 Environment: IE 8, IE 9, Firefox 11.
Reporter: James Lee
Assignee: domi
Priority: Blocker

 Try to add 2 or more conditional steps, without success.  Can only add 1.  
 Firefox error console showed the following:
 Prototype.Selector is undefined
 Source File: http://localhost/static/c5afde5e/scripts/behavior.js
 Line: 132

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13469) Prototype.Selector is undefined


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161693#comment-161693
 ] 

domi edited comment on JENKINS-13469 at 4/17/12 6:03 PM:
-

Which version of the conditional-buildstep-plugin and Jenkins are you using?

I only know this error from the mangaged-scripts-plugin, ant there it should be 
fixed with the latest version...

  was (Author: domi):
Which version of the conditional-buildstep-plugin and Jenkins are you using?

I only know this error from the mangaaged-scripts-plugin, ant there it should 
be fixed with the latest version...
  
 Prototype.Selector is undefined
 ---

 Key: JENKINS-13469
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13469
 Project: Jenkins
  Issue Type: Bug
  Components: conditional-buildstep
Affects Versions: current
 Environment: IE 8, IE 9, Firefox 11.
Reporter: James Lee
Assignee: domi
Priority: Blocker

 Try to add 2 or more conditional steps, without success.  Can only add 1.  
 Firefox error console showed the following:
 Prototype.Selector is undefined
 Source File: http://localhost/static/c5afde5e/scripts/behavior.js
 Line: 132

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13174) Stop changeset tags from being counted as a change in Mercurial Plugin polling

2012-04-17 Thread k...@iliumsoft.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161695#comment-161695
 ] 

Ken Morse commented on JENKINS-13174:
-

This is a big problem if the build tags its own release. I believe this issues 
is new with 1.38; we upgraded the plugin today and didn't have this problem 
earlier.

 Stop changeset tags from being counted as a change in Mercurial Plugin polling
 --

 Key: JENKINS-13174
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13174
 Project: Jenkins
  Issue Type: Improvement
  Components: mercurial
Affects Versions: current
Reporter: Neil Kay
Assignee: Kohsuke Kawaguchi

 We have the slave build machines polling Mercurial repositories, using the 
 Mercurial plugin, to trigger builds.
 During the Jenkins job, we create and push a tag changeset as part of the 
 build process.
 This tag changeset is detected by polling and causing an infinite loop of 
 builds.
 I've looked into other options, I notice the notice away from polling to be 
 more push activated, which sounds good, but it seems this still relies on 
 polling to detect what has changed, so it seems this would still be a problem.
 The other thing that sounded like it may help was modules in the Mercurial 
 plugin, but this is a huge change to move lots of repositories to put 
 everything except the hgtags file into a sub folder and then specify that sub 
 folder as a module.
 If tag changesets were ignorred by polling, similar to a change that was made 
 to ignore merge changesets, all would be good in the world :)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-11991) Polling shows changes after job commits and pushes changes

2012-04-17 Thread k...@iliumsoft.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-11991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161696#comment-161696
 ] 

Ken Morse commented on JENKINS-11991:
-

We're seeing this happen too with 1.38; our build tags itself but that now 
seems to cause an infinite loop of building. Maybe versions prior to 1.38 
ignored the .hgtags file?

 Polling shows changes after job commits and pushes changes
 --

 Key: JENKINS-11991
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11991
 Project: Jenkins
  Issue Type: Bug
  Components: mercurial
Reporter: Jarek Potiuk
Assignee: Kohsuke Kawaguchi

 As of latest version of mercurial plugin (1.38) the behaviour of the plugin 
 changed. We used to make some manuals release jobs to commit some changes 
 (increase build number and set a tag) and push it to the origin repo. It 
 seems that now every time after release job is executed (and commit and push 
 happen), the plugin detects that the repo has changed and triggers another 
 build. It was not working like that before...
 Some outputs:
 1st job (release job run manually):
 21:25:04  [workspace] $ hg showconfig paths.default
 21:25:04  [workspace] $ hg pull --rev 1_0
 21:25:04  [workspace] $ hg update --clean --rev 1_0
 21:25:04  0 files updated, 0 files merged, 0 files removed, 0 files unresolved
 21:25:04  [workspace] $ hg log --rev . --template {node}
 21:25:05  [workspace] $ hg log --rev cc3b37d8df1298eabedfad328cbd4a068e27abf8
 21:25:05  [workspace] $ hg log --template changeset node='{node}' 
 author='{author|xmlescape}' rev='{rev}' 
 date='{date}'msg{desc|xmlescape}/msgadded{file_adds|stringify|xmlescape}/addeddeleted{file_dels|stringify|xmlescape}/deletedfiles{files|stringify|xmlescape}/filesparents{parents}/parents/changeset\n
  --rev 1_0:0 --follow --prune cc3b37d8df1298eabedfad328cbd4a068e27abf8
 Inside the job:
 hg commit -m Incrementing application version to 1.0-TEST (345 -u 
 b...@polidea.pl AndroidManifest.xml 
 hg tag -f Release_1.0-TEST_345 -u b...@polidea.pl
 hg push 
 Then polling triggers another job:
 21:27:04  Started by an SCM change
 21:27:04  Building on master
 21:27:04  [workspace] $ hg showconfig paths.default
 21:27:04  [workspace] $ hg pull --rev 1_0
 21:27:04  [workspace] $ hg update --clean --rev 1_0
 21:27:04  0 files updated, 0 files merged, 0 files removed, 0 files unresolved
 21:27:04  [workspace] $ hg log --rev . --template {node}
 21:27:05  [workspace] $ hg log --rev cc3b37d8df1298eabedfad328cbd4a068e27abf8
 21:27:05  [workspace] $ hg log --template changeset node='{node}' 
 author='{author|xmlescape}' rev='{rev}' 
 date='{date}'msg{desc|xmlescape}/msgadded{file_adds|stringify|xmlescape}/addeddeleted{file_dels|stringify|xmlescape}/deletedfiles{files|stringify|xmlescape}/filesparents{parents}/parents/changeset\n
  --rev 1_0:0 --follow --prune cc3b37d8df1298eabedfad328cbd4a068e27abf8

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12577) Email notification hangs due to NullPointerException

2012-04-17 Thread harold.shins...@sap.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161697#comment-161697
 ] 

shinsato commented on JENKINS-12577:


The fix for 13317 prevented null values for default subject and body fields 
which I thought might be related - but it isn't.

The line of code that is causing a NullPointerException is return line in Slave:

public Launcher createLauncher(TaskListener listener) {
SlaveComputer c = getComputer();
return new RemoteLauncher(listener, c.getChannel(), 
c.isUnix()).decorateFor(this);
}

The only thing that could cause a NPE are the dereferences of c, which is the 
computer. Something has gotten pretty broken in the configuration for 
Slave.getComputer() to return null. I'd agree I doubt this is the email-ext 
plugin.

 Email notification hangs due to NullPointerException
 

 Key: JENKINS-12577
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12577
 Project: Jenkins
  Issue Type: Bug
  Components: email-ext
Affects Versions: current
 Environment: Windows 2008 Server x64, Java 1.6.0_25
Reporter: Costin Caraivan
Priority: Blocker
 Attachments: template.jelly


 We have an email notification which uses a Jelly template. So far it worked 
 ok, but recently we started getting these:
 Jan 25, 2012 2:11:23 PM hudson.plugins.emailext.ExtendedEmailPublisher 
 sendMail
 WARNING: Could not send email.
 java.lang.NullPointerException
   at hudson.model.Slave.createLauncher(Slave.java:311)
   at 
 hudson.plugins.perforce.PerforceMailResolver.findMailAddressFor(PerforceMailResolver.java:60)
   at 
 hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:100)
   at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:488)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:331)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:251)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:243)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:203)
   at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
   at 
 hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:694)
   at 
 hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:669)
   at 
 hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:647)
   at hudson.model.Build$RunnerImpl.cleanUp(Build.java:171)
   at hudson.model.Run.run(Run.java:1448)
   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:230)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13057) Support for integrated changelists in Changes view

2012-04-17 Thread rob.pe...@gmail.com (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rob Petti resolved JENKINS-13057.
-

Resolution: Fixed

 Support for integrated changelists in Changes view
 

 Key: JENKINS-13057
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13057
 Project: Jenkins
  Issue Type: Improvement
  Components: perforce
Reporter: Mikko Tapaninen

 Especially with Streams, you are most probably merging lot between 
 development-main-release type streams. For better visibility of the build 
 content, the Changes view should show also integrated changes. So instead 
 for running {{p4 changes}} run {{p4 changes -i}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13109) Huge changelogs eat all the Java memory

2012-04-17 Thread rob.pe...@gmail.com (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rob Petti resolved JENKINS-13109.
-

Resolution: Fixed

 Huge changelogs eat all the Java memory
 ---

 Key: JENKINS-13109
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13109
 Project: Jenkins
  Issue Type: Bug
  Components: perforce
 Environment: Windows Server 2008 HPC Edition
 64-bit JVM 1.6.0_29
 Running Jenkins service with arguments-Xrs -Xmx2048m 
 -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar 
 %BASE%\jenkins.war --httpPort=8080/arguments
Reporter: Mikko Tapaninen

 With really huge changelists the p4 plugin can run out of java heap space. At 
 least it looks like the reason for memory problems would be huge 
 changelog.xml files. An example case:
 - a changelist with  40 files
 - results in a changelog.xml size  110MB
 - Jenkins runs out of memory: {{java.lang.OutOfMemoryError: Java heap space}}
 Maybe there should be an option to limit the amount of files that p4 plugin 
 reads to from changelists?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13469) Prototype.Selector is undefined

2012-04-17 Thread jamesh...@yahoo.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161698#comment-161698
 ] 

James Lee commented on JENKINS-13469:
-

I am using Jenkins 1.460, and conditional-buildstep 1.0.  I tried both IE 8 and 
9 as well as firefox 11, and got the same error.

But later yesterday I was able to add multiple steps by adding and saving one 
at a time, then repeating the same to add and save the second one, and so on.  
So I will change this ticket from blocker to lower level since it does have a 
workaround.  But hope you can fix the can only add one step at a time issue 
soon.

 Prototype.Selector is undefined
 ---

 Key: JENKINS-13469
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13469
 Project: Jenkins
  Issue Type: Bug
  Components: conditional-buildstep
Affects Versions: current
 Environment: IE 8, IE 9, Firefox 11.
Reporter: James Lee
Assignee: domi
Priority: Blocker

 Try to add 2 or more conditional steps, without success.  Can only add 1.  
 Firefox error console showed the following:
 Prototype.Selector is undefined
 Source File: http://localhost/static/c5afde5e/scripts/behavior.js
 Line: 132

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13469) Prototype.Selector is undefined

2012-04-17 Thread jamesh...@yahoo.com (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Lee updated JENKINS-13469:


Priority: Major  (was: Blocker)

Found a workaround by adding one at a time.

 Prototype.Selector is undefined
 ---

 Key: JENKINS-13469
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13469
 Project: Jenkins
  Issue Type: Bug
  Components: conditional-buildstep
Affects Versions: current
 Environment: IE 8, IE 9, Firefox 11.
Reporter: James Lee
Assignee: domi

 Try to add 2 or more conditional steps, without success.  Can only add 1.  
 Firefox error console showed the following:
 Prototype.Selector is undefined
 Source File: http://localhost/static/c5afde5e/scripts/behavior.js
 Line: 132

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13488) Copy Artifacts plugin's Optional not working

2012-04-17 Thread br...@whamcloud.com (JIRA)

Brian Murrell created JENKINS-13488:
---

 Summary: Copy Artifacts plugin's Optional not working
 Key: JENKINS-13488
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13488
 Project: Jenkins
  Issue Type: Bug
  Components: copyartifact
Affects Versions: current
 Environment: Jenkins 1.457
Reporter: Brian Murrell
Assignee: Alan Harder


I have a matrix-configuration job in which I am trying to copy artifacts from 
an upstream matrix-configuration job where some of the axes combinations of the 
upstream job are not run and therefore do not produce artifacts.  In the job I 
am running the copy artifacts action I use 
{{upstream_job/arch=$arch,distro=$distro}} as the Project name so that each 
combination copies it's respective upstream artifacts.

However knowing that there upstream combinations that are not run and therefore 
don't have artifacts I have selected Optional for this copy artifacts action 
but it's still failing with:

{code}
Unable to find project for artifact copy: upstream/arch=x86_64,distro=el5
This may be due to incorrect project name or permission settings; see help for 
project name in job configuration.
Build step 'Copy artifacts from another project' marked build as failure
{code}

I can't simply exclude the same axes combinations in the job I am doing the 
artifact copying in as I do upstream since there are other actions that need to 
be done even when then are no artifacts from the upstream job.

Am I misunderstanding the use of *Optional* in the Copy Artifacts plugin?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13080) Wipe Out Workspace fails if Mapping is parametrized


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161700#comment-161700
 ] 

SCM/JIRA link daemon commented on JENKINS-13080:


Code changed in jenkins
User: Rob Petti
Path:
 src/main/java/hudson/plugins/perforce/PerforceSCM.java
http://jenkins-ci.org/commit/perforce-plugin/13f9f49dc23a48124cc707a169454ee574d350ad
Log:
  [FIXED JENKINS-13080] don't update client view before flushing to 0 on 
workspace deletion






 Wipe Out Workspace fails if Mapping is parametrized
 ---

 Key: JENKINS-13080
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13080
 Project: Jenkins
  Issue Type: Bug
  Components: perforce
 Environment: 1.450
 Perforce version 1.3.7
Reporter: Jeff Maxwell
Assignee: Rob Petti

 h2. Workaround
 If possible add a default value for the parameter like *
 h2. Details
 Mapping setting: //depot/my-project/releases/${RELEASE}/... 
 //my-project-release/...
 Mar 14, 2012 12:17:36 PM hudson.plugins.perforce.PerforceSCM 
 processWorkspaceBeforeDeletion
 SEVERE: null
 com.tek42.perforce.PerforceException:  Error in client specification. Error 
 detected at line 9. Null directory (//) not allowed in 
 '//depot/my-project/releases//...'.
 For Command: /usr/bin/p4 -s client -i 
 With Data:
 ===
 Client: my-project-release
 Owner: perforce
 Description: Created by perforce.
 Root: opt/jenkins-data/jobs/my-project-release/workspace
 Options: noallwrite clobber nocompress unlocked nomodtime rmdir
 SubmitOptions: submitunchanged
 LineEnd: 
 View:
   //depot/my-project/releases//... //my-project-release/...
 ===
   at 
 com.tek42.perforce.parse.AbstractPerforceTemplate.saveToPerforce(AbstractPerforceTemplate.java:261)
   at com.tek42.perforce.parse.Workspaces.saveWorkspace(Workspaces.java:69)
   at 
 hudson.plugins.perforce.PerforceSCM.saveWorkspaceIfDirty(PerforceSCM.java:1373)
   at 
 hudson.plugins.perforce.PerforceSCM.processWorkspaceBeforeDeletion(PerforceSCM.java:2353)
   at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:575)
   at hudson.model.AbstractProject.checkout(AbstractProject.java:1195)
   at 
 hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:579)
   at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:468)
   at hudson.model.Run.run(Run.java:1408)
   at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:238)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13080) Wipe Out Workspace fails if Mapping is parametrized


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

SCM/JIRA link daemon resolved JENKINS-13080.


Resolution: Fixed

 Wipe Out Workspace fails if Mapping is parametrized
 ---

 Key: JENKINS-13080
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13080
 Project: Jenkins
  Issue Type: Bug
  Components: perforce
 Environment: 1.450
 Perforce version 1.3.7
Reporter: Jeff Maxwell
Assignee: Rob Petti

 h2. Workaround
 If possible add a default value for the parameter like *
 h2. Details
 Mapping setting: //depot/my-project/releases/${RELEASE}/... 
 //my-project-release/...
 Mar 14, 2012 12:17:36 PM hudson.plugins.perforce.PerforceSCM 
 processWorkspaceBeforeDeletion
 SEVERE: null
 com.tek42.perforce.PerforceException:  Error in client specification. Error 
 detected at line 9. Null directory (//) not allowed in 
 '//depot/my-project/releases//...'.
 For Command: /usr/bin/p4 -s client -i 
 With Data:
 ===
 Client: my-project-release
 Owner: perforce
 Description: Created by perforce.
 Root: opt/jenkins-data/jobs/my-project-release/workspace
 Options: noallwrite clobber nocompress unlocked nomodtime rmdir
 SubmitOptions: submitunchanged
 LineEnd: 
 View:
   //depot/my-project/releases//... //my-project-release/...
 ===
   at 
 com.tek42.perforce.parse.AbstractPerforceTemplate.saveToPerforce(AbstractPerforceTemplate.java:261)
   at com.tek42.perforce.parse.Workspaces.saveWorkspace(Workspaces.java:69)
   at 
 hudson.plugins.perforce.PerforceSCM.saveWorkspaceIfDirty(PerforceSCM.java:1373)
   at 
 hudson.plugins.perforce.PerforceSCM.processWorkspaceBeforeDeletion(PerforceSCM.java:2353)
   at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:575)
   at hudson.model.AbstractProject.checkout(AbstractProject.java:1195)
   at 
 hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:579)
   at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:468)
   at hudson.model.Run.run(Run.java:1408)
   at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:238)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13080) Wipe Out Workspace fails if Mapping is parametrized

2012-04-17 Thread dogf...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161701#comment-161701
 ] 

dogfood commented on JENKINS-13080:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! 
[plugins_perforce #218|http://ci.jenkins-ci.org/job/plugins_perforce/218/]
 [FIXED JENKINS-13080] don't update client view before flushing to 0 on 
workspace deletion (Revision 13f9f49dc23a48124cc707a169454ee574d350ad)

 Result = SUCCESS
Rob Petti : 
Files : 
* src/main/java/hudson/plugins/perforce/PerforceSCM.java


 Wipe Out Workspace fails if Mapping is parametrized
 ---

 Key: JENKINS-13080
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13080
 Project: Jenkins
  Issue Type: Bug
  Components: perforce
 Environment: 1.450
 Perforce version 1.3.7
Reporter: Jeff Maxwell
Assignee: Rob Petti

 h2. Workaround
 If possible add a default value for the parameter like *
 h2. Details
 Mapping setting: //depot/my-project/releases/${RELEASE}/... 
 //my-project-release/...
 Mar 14, 2012 12:17:36 PM hudson.plugins.perforce.PerforceSCM 
 processWorkspaceBeforeDeletion
 SEVERE: null
 com.tek42.perforce.PerforceException:  Error in client specification. Error 
 detected at line 9. Null directory (//) not allowed in 
 '//depot/my-project/releases//...'.
 For Command: /usr/bin/p4 -s client -i 
 With Data:
 ===
 Client: my-project-release
 Owner: perforce
 Description: Created by perforce.
 Root: opt/jenkins-data/jobs/my-project-release/workspace
 Options: noallwrite clobber nocompress unlocked nomodtime rmdir
 SubmitOptions: submitunchanged
 LineEnd: 
 View:
   //depot/my-project/releases//... //my-project-release/...
 ===
   at 
 com.tek42.perforce.parse.AbstractPerforceTemplate.saveToPerforce(AbstractPerforceTemplate.java:261)
   at com.tek42.perforce.parse.Workspaces.saveWorkspace(Workspaces.java:69)
   at 
 hudson.plugins.perforce.PerforceSCM.saveWorkspaceIfDirty(PerforceSCM.java:1373)
   at 
 hudson.plugins.perforce.PerforceSCM.processWorkspaceBeforeDeletion(PerforceSCM.java:2353)
   at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:575)
   at hudson.model.AbstractProject.checkout(AbstractProject.java:1195)
   at 
 hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:579)
   at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:468)
   at hudson.model.Run.run(Run.java:1408)
   at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:238)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12386) Self Promotion is broken - missing index.jelly file

2012-04-17 Thread r...@lidalia.org.uk (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161702#comment-161702
 ] 

Robert Elliot commented on JENKINS-12386:
-

This only happens for me when the build itself fails.  It looks like it is 
because this makes 
hudson.plugins.promoted_builds.conditions.SelfPromotionCondition an unmet 
condition of the build (unsurprisingly) and 
hudson.plugins.promoted_builds.PromotionProcess.getUnmetConditions returns the 
SelfPromotionCondition rather than the SelfPromotionBadge.  
https://github.com/jenkinsci/promoted-builds-plugin/tree/master/src/main/resources/hudson/plugins/promoted_builds/conditions/SelfPromotionCondition
 does indeed not contain an index.jelly, hence the 500 error.

I guess this is not a massive deal as it's already obvious that the build did 
not succeed, but it should be fixed.  I presume the missing index.jelly could 
be very simple indeed - something like:

{code}
div
  ${%Build failed - cannot be automatically promoted}
/div
{code}

though as it is possible to configure this condition to trigger even if the 
build is unstable it might be desirable to have a button to over-ride and 
forcefully meet this qualification.


 Self Promotion is broken - missing index.jelly file
 ---

 Key: JENKINS-12386
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12386
 Project: Jenkins
  Issue Type: Bug
  Components: promoted-builds
Affects Versions: current
 Environment: Jenkins version 1.447
 Build Promotion plugin versions 2.3 and 2.4
Reporter: Valerie Wagner

 My project is configured to Promote immediately once the build is complete. 
 After the project builds, there is no star indicating that a promotion has 
 taken place. I click on the latest build and then on Promotion Status link. 
 A stack trace is generated: 
 Status Code: 500
 Exception:
 Stacktrace:
 org.apache.commons.jelly.JellyTagException: 
 file:/jenkins/plugins/promoted-builds/WEB-INF/classes/hudson/plugins/promoted_builds/PromotedBuildAction/index.jelly:115:54:
  st:include No page found 'index.jelly' for class 
 hudson.plugins.promoted_builds.conditions.SelfPromotionCondition
   at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:124)
   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
   at 
 org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
   at 
 org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at 
 org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
   at 
 org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at 
 org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at 
 org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
   at 
 org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at 
 org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
   at 
 org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
   at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at

[JIRA] (JENKINS-13324) Perforce mail address resolver should fall back to other resolvers if mail address is invalid

[
https://issues.jenkins-ci.org/browse/JENKINS-13324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

SCM/JIRA link daemon resolved JENKINS-13324.

Resolution: Fixed

Perforce mail address resolver should fall back to other resolvers if mail
address is invalid
-

Key: JENKINS-13324
URL: https://issues.jenkins-ci.org/browse/JENKINS-13324
Project: Jenkins
Issue Type: Bug
Components: perforce
Environment: Perforce 2011.1
perforce-plugin 1.3.12
Reporter: Mikko Tapaninen

Perforce mail address resolver is always returning a string, no matter what
the actual email address is. I don't know what is the order how Jenkins loops
through the various MailAddressResolver instances but if some instance
returns an actual string (i.e. non-null), it will stick with that. I don't
think it's feasible to really check whether the email address provided by
Perforce is valid, but PerforceMailResolver could check for some value (e.g.
n/a) and return null if it matches. At least with Perforce 2011.1 you can't
have an empty value for an email address.
There could be an UI element for configuring which email address would be
thought as invalid, but I'm fine with hardcoding n/a there and documenting
it somewhere. Would this be ok?

[JIRA] (JENKINS-13324) Perforce mail address resolver should fall back to other resolvers if mail address is invalid