[JIRA] [clone-workspace] (JENKINS-7260) Clone workspace doesn't copy empty directories when cloning entire workspace
jfigler commented on JENKINS-7260 Clone workspace doesnt copy empty directories when cloning entire workspace Hi I'm curious if anyone knows of a workaround for this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13314) Remote API does not include downstream/upstream build info
jfigler commented on JENKINS-13314 Remote API does not include downstream/upstream build info Agreed. It would be great to be able to ask an upstream build which downstream builds it was responsible for triggering via that API. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16474) Slow/hung web UI in 1.483+ (stuck in parseURI)
jfigler commented on JENKINS-16474 Slow/hung web UI in 1.483+ (stuck in parseURI) Thanks Jesse, I'm unable to reproduce it as well. Can anyone confirm if they were experiencing this issue, and now with this partial (or full) fix, they're not? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16474) Slow/hung web UI in 1.483+ (stuck in parseURI)
jfigler commented on JENKINS-16474 Slow/hung web UI in 1.483+ (stuck in parseURI) Does anyone have any advice on how to reproduce this problem in 1.480.1? In large environments with a lot of real traffic, 1.480.1 appears to be experiencing this issue and becomes essentially unusable. However, in a smaller environment with much less traffic, I cannot get this defect to appear. What I'm trying to do is prove that a) this is the issue we are seeing and not something else, and b) that it is indeed gone in 1.480.3. I've tried Apache Benchmark with 20+ concurrency, and I've tried simulating traffic with 20+ tabs open with auto-refresh on... This upgrade is a little more risky since the whole 're-keying' process will take effect, so I want to make sure we won't have to rollback... again... Any advice would be greatly apprciated! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14755) Mail address resolution can take a significant amount of time
jfigler commented on JENKINS-14755 Mail address resolution can take a significant amount of time Just to follow up on bbonn's comment, we were finally able to figure this out in our environment. We began experiencing this problem when we upgraded our Jenkins core from 1.424.6 to 1.447.2. We were using Email Ext version 1.8 at the time. We updated to the latest Email Ext (2.24.1) with no luck. Then we updated our Active Directory plug-in from version 1.6 to 2.9, again with no luck. Finally, in the main configuration for the AD plug-in we removed our domain name from the advanced configuration. For us, that's what got our configuration of Jenkins resolving email addresses normally again. I doubt the email-ext plug-in is even related in our case. I have NOT proven that out, but I'm assuming that if we had kept our email ext plug-in version on 1.8 but made all the other changes, we would have had success there as well. Just in case anyone has a similar setup, this is what worked for us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12911) Clearecase Plugin Not Detecting Changes
[
https://issues.jenkins-ci.org/browse/JENKINS-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161015#comment-161015
]
jfigler commented on JENKINS-12911:
---
We're seeing this too... did you ever figure it out?
Clearecase Plugin Not Detecting Changes
---
Key: JENKINS-12911
URL: https://issues.jenkins-ci.org/browse/JENKINS-12911
Project: Jenkins
Issue Type: Bug
Components: clearcase
Environment: Windows 7
Reporter: Justin Bailey
Assignee: Vincent Latombe
I am using the Clearcase plugin to poll for changes and trigger a build.
However, even when changes are clearly present, no build is triggered. Here's
the log from a poll showing a change:
{quote}
Started on Feb 27, 2012 5:05:09 PM
[baileyj_master_Build_OF012_hudson] $ c:\Program
Files\IBM\RationalSDLC\ClearCase\bin\cleartool pwv -root
C:\Users\baileyj\.jenkins\jobs\Build
OF012\workspace\baileyj_master_Build_OF012_hudson
[workspace] $ c:\Program Files\IBM\RationalSDLC\ClearCase\bin\cleartool
lsview baileyj_master_Build_OF012_hudson
baileyj_master_Build_OF012_hudson
\\ds-wccreg2.ds.ad.foo.com\viewstore\DS\baileyj\baileyj_master_Build_OF012_hudson.vws
[baileyj_master_Build_OF012_hudson] $ c:\Program
Files\IBM\RationalSDLC\ClearCase\bin\cleartool lshistory -all -since
28-feb-12.00:46:58utc+ -fmt '\%Nd\ \%u\ \%En\ \%Vn\ \%e\ \%o\
\n%c\n' -branch brtype:of012 -nco web2000/of_app/of
20120227.170348 baileyj C:\Users\baileyj\.jenkins\jobs\Build
OF012\workspace\baileyj_master_Build_OF012_hudson\web2000\mm_app\we\sdk\test\autoload\ofadmin.ppk
\main\of012\4 create version checkin
Done. Took 0.93 sec
No changes
{quote}
As should be clear, the file ofadmin.ppk shows a change, but the plugin did
not detect it.
I'm running Jenkins v1.451 and ClearCase Plug-in v1.3.7.
If there is a mailing list where I can ask this question, please let me know.
--
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
