[JIRA] Created: (HUDSON-8529) Perforce plug-in isn't showing changes in polling
Locked
[JIRA] Created: (HUDSON-8529) Perforce plug-in isn't showing changes in polling
 
Administrator
|
Perforce plug-in isn't showing changes in polling
------------------------------------------------- Key: HUDSON-8529 URL: http://issues.hudson-ci.org/browse/HUDSON-8529 Project: Hudson Issue Type: Bug Components: perforce Affects Versions: current Environment: CentOS 4.8 (slave configuration) Reporter: halostatue Priority: Minor The front page of a given build says that it was started by an SCM change. Clicking through the link shows a log that simply says "Workspace not up to date" without any details of the files that have been changed. We're using "Disable Auto Sync" but I still expect the changed files would be included in the output from either the Polling Log or the Perforce Polling Log (it's not in either). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] Commented: (HUDSON-8529) Perforce plug-in isn't showing changes in polling
|
Administrator
|
[ http://issues.hudson-ci.org/browse/HUDSON-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145040#action_145040 ] rpetti commented on HUDSON-8529: -------------------------------- Good idea, it would help debugging polling issues quite a bit, since the output right now can be rather vague. > Perforce plug-in isn't showing changes in polling > ------------------------------------------------- > > Key: HUDSON-8529 > URL: http://issues.hudson-ci.org/browse/HUDSON-8529 > Project: Hudson > Issue Type: Bug > Components: perforce > Affects Versions: current > Environment: CentOS 4.8 (slave configuration) > Reporter: halostatue > Priority: Minor > > The front page of a given build says that it was started by an SCM change. Clicking through the link shows a log that simply says "Workspace not up to date" without any details of the files that have been changed. > We're using "Disable Auto Sync" but I still expect the changed files would be included in the output from either the Polling Log or the Perforce Polling Log (it's not in either). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] Assigned: (HUDSON-8529) Perforce plug-in isn't showing changes in polling
|
Administrator
|
In reply to this post by Kohsuke Kawaguchi
[ http://issues.hudson-ci.org/browse/HUDSON-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rpetti reassigned HUDSON-8529: ------------------------------ Assignee: rpetti > Perforce plug-in isn't showing changes in polling > ------------------------------------------------- > > Key: HUDSON-8529 > URL: http://issues.hudson-ci.org/browse/HUDSON-8529 > Project: Hudson > Issue Type: Bug > Components: perforce > Affects Versions: current > Environment: CentOS 4.8 (slave configuration) > Reporter: halostatue > Assignee: rpetti > Priority: Minor > > The front page of a given build says that it was started by an SCM change. Clicking through the link shows a log that simply says "Workspace not up to date" without any details of the files that have been changed. > We're using "Disable Auto Sync" but I still expect the changed files would be included in the output from either the Polling Log or the Perforce Polling Log (it's not in either). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] Updated: (HUDSON-8529) Perforce plug-in isn't showing changes in polling
|
Administrator
|
In reply to this post by Kohsuke Kawaguchi
[ http://issues.hudson-ci.org/browse/HUDSON-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] halostatue updated HUDSON-8529: ------------------------------- Attachment: screenshot-1.jpg The first screen in the bug. > Perforce plug-in isn't showing changes in polling > ------------------------------------------------- > > Key: HUDSON-8529 > URL: http://issues.hudson-ci.org/browse/HUDSON-8529 > Project: Hudson > Issue Type: Bug > Components: perforce > Affects Versions: current > Environment: CentOS 4.8 (slave configuration) > Reporter: halostatue > Assignee: rpetti > Priority: Minor > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg > > > The front page of a given build says that it was started by an SCM change. Clicking through the link shows a log that simply says "Workspace not up to date" without any details of the files that have been changed. > We're using "Disable Auto Sync" but I still expect the changed files would be included in the output from either the Polling Log or the Perforce Polling Log (it's not in either). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] Updated: (HUDSON-8529) Perforce plug-in isn't showing changes in polling
|
Administrator
|
In reply to this post by Kohsuke Kawaguchi
[ http://issues.hudson-ci.org/browse/HUDSON-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] halostatue updated HUDSON-8529: ------------------------------- Attachment: screenshot-2.jpg The 'standard' polling log (Perforce Polling Log doesn't always appear?) > Perforce plug-in isn't showing changes in polling > ------------------------------------------------- > > Key: HUDSON-8529 > URL: http://issues.hudson-ci.org/browse/HUDSON-8529 > Project: Hudson > Issue Type: Bug > Components: perforce > Affects Versions: current > Environment: CentOS 4.8 (slave configuration) > Reporter: halostatue > Assignee: rpetti > Priority: Minor > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg > > > The front page of a given build says that it was started by an SCM change. Clicking through the link shows a log that simply says "Workspace not up to date" without any details of the files that have been changed. > We're using "Disable Auto Sync" but I still expect the changed files would be included in the output from either the Polling Log or the Perforce Polling Log (it's not in either). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] Updated: (HUDSON-8529) Perforce plug-in isn't showing changes in polling
|
Administrator
|
In reply to this post by Kohsuke Kawaguchi
[ http://issues.hudson-ci.org/browse/HUDSON-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] halostatue updated HUDSON-8529: ------------------------------- Attachment: screenshot-3.jpg The Perforce Polling Log > Perforce plug-in isn't showing changes in polling > ------------------------------------------------- > > Key: HUDSON-8529 > URL: http://issues.hudson-ci.org/browse/HUDSON-8529 > Project: Hudson > Issue Type: Bug > Components: perforce > Affects Versions: current > Environment: CentOS 4.8 (slave configuration) > Reporter: halostatue > Assignee: rpetti > Priority: Minor > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg > > > The front page of a given build says that it was started by an SCM change. Clicking through the link shows a log that simply says "Workspace not up to date" without any details of the files that have been changed. > We're using "Disable Auto Sync" but I still expect the changed files would be included in the output from either the Polling Log or the Perforce Polling Log (it's not in either). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] Updated: (HUDSON-8529) Perforce plug-in isn't showing changes in polling
|
Administrator
|
In reply to this post by Kohsuke Kawaguchi
[ http://issues.hudson-ci.org/browse/HUDSON-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] halostatue updated HUDSON-8529: ------------------------------- Attachment: screenshot-4.jpg Output from our build script that shows the files that were updated. > Perforce plug-in isn't showing changes in polling > ------------------------------------------------- > > Key: HUDSON-8529 > URL: http://issues.hudson-ci.org/browse/HUDSON-8529 > Project: Hudson > Issue Type: Bug > Components: perforce > Affects Versions: current > Environment: CentOS 4.8 (slave configuration) > Reporter: halostatue > Assignee: rpetti > Priority: Minor > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg > > > The front page of a given build says that it was started by an SCM change. Clicking through the link shows a log that simply says "Workspace not up to date" without any details of the files that have been changed. > We're using "Disable Auto Sync" but I still expect the changed files would be included in the output from either the Polling Log or the Perforce Polling Log (it's not in either). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] Commented: (HUDSON-8529) Perforce plug-in isn't showing changes in polling
|
Administrator
|
In reply to this post by Kohsuke Kawaguchi
[ http://issues.hudson-ci.org/browse/HUDSON-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145047#action_145047 ] halostatue commented on HUDSON-8529: ------------------------------------ Added the screenshots that I couldn't figure out how to add when I first filed the bug. If I understood how the Perforce plug-in worked a bit better, I might be able to help work on this. > Perforce plug-in isn't showing changes in polling > ------------------------------------------------- > > Key: HUDSON-8529 > URL: http://issues.hudson-ci.org/browse/HUDSON-8529 > Project: Hudson > Issue Type: Bug > Components: perforce > Affects Versions: current > Environment: CentOS 4.8 (slave configuration) > Reporter: halostatue > Assignee: rpetti > Priority: Minor > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg > > > The front page of a given build says that it was started by an SCM change. Clicking through the link shows a log that simply says "Workspace not up to date" without any details of the files that have been changed. > We're using "Disable Auto Sync" but I still expect the changed files would be included in the output from either the Polling Log or the Perforce Polling Log (it's not in either). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] Commented: (HUDSON-8529) Perforce plug-in isn't showing changes in polling
|
Administrator
|
In reply to this post by Kohsuke Kawaguchi
[ http://issues.hudson-ci.org/browse/HUDSON-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145048#action_145048 ] rpetti commented on HUDSON-8529: -------------------------------- Ok, I think there's some confusion here. The polling log only shows the LAST poll that was done, regardless of what the result was. It's primarily used for debugging, nothing more. Since you are using "Disable Auto Sync", no perforce actions are performed in the build, including changeset retrieval. This behavior is also stated in the documentation for this option: "Disable Auto Sync: allows you to tell this plugin to not sync a workspace before the build begins. Changeset retrieval will also be disabled. Default behavior is to sync to the head revision." The option should definitely be renamed to avoid confusion (to "Disable Sync and Changelog" or something similar). The behavior you are looking for is covered by HUDSON-8260, and isn't yet implemented. I'll leave this bug open, though, since having the changes dumped to the polling log can still be useful for debugging. > Perforce plug-in isn't showing changes in polling > ------------------------------------------------- > > Key: HUDSON-8529 > URL: http://issues.hudson-ci.org/browse/HUDSON-8529 > Project: Hudson > Issue Type: Bug > Components: perforce > Affects Versions: current > Environment: CentOS 4.8 (slave configuration) > Reporter: halostatue > Assignee: rpetti > Priority: Minor > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg > > > The front page of a given build says that it was started by an SCM change. Clicking through the link shows a log that simply says "Workspace not up to date" without any details of the files that have been changed. > We're using "Disable Auto Sync" but I still expect the changed files would be included in the output from either the Polling Log or the Perforce Polling Log (it's not in either). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
«
Return to Jenkins issues
|
1 view|%1 views
| Free forum by Nabble | Edit this page |