[JIRA] Created: (HUDSON-6337) Mercurial Polling does not work for 'modules'

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Created: (HUDSON-6337) Mercurial Polling does not work for 'modules'

Hudson issues mailing list
Mercurial Polling does not work for 'modules'
---------------------------------------------

                 Key: HUDSON-6337
                 URL: http://issues.hudson-ci.org/browse/HUDSON-6337
             Project: Hudson
          Issue Type: Bug
          Components: mercurial
         Environment: Hudson ver. 1.351
            Reporter: m_burger
            Assignee: kohsuke


I am using the "Modules" feature of the Mercurial SCM plugin. Unfortunately, this feature does not work as expected.

After starting Hudson, a build will be triggered as soon as a file in the specified module was changed. After a change to a file outside this module, the plugin does not trigger a build as expected ("No changes").

However, although there is a change to a file within the module afterward, the plugin does not detect any change ("No changes"). Though, the "Last Mercurial Polling Log" shows these changed files; there are lines starting with "files:<MODULE>/..."

Restarting Hudson or reloading its configuration does work as a work-around: the next poll will trigger a build - until there is a change outside the module again.


--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Assigned: (HUDSON-6337) Mercurial Polling does not work for 'modules'

Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jglick reassigned HUDSON-6337:
------------------------------

    Assignee: jglick  (was: kohsuke)

> Mercurial Polling does not work for 'modules'
> ---------------------------------------------
>
>                 Key: HUDSON-6337
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6337
>             Project: Hudson
>          Issue Type: Bug
>          Components: mercurial
>         Environment: Hudson ver. 1.351
>            Reporter: m_burger
>            Assignee: jglick
>
> I am using the "Modules" feature of the Mercurial SCM plugin. Unfortunately, this feature does not work as expected.
> After starting Hudson, a build will be triggered as soon as a file in the specified module was changed. After a change to a file outside this module, the plugin does not trigger a build as expected ("No changes").
> However, although there is a change to a file within the module afterward, the plugin does not detect any change ("No changes"). Though, the "Last Mercurial Polling Log" shows these changed files; there are lines starting with "files:<MODULE>/..."
> Restarting Hudson or reloading its configuration does work as a work-around: the next poll will trigger a build - until there is a change outside the module again.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6337) Mercurial Polling does not work for 'modules'

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138644#action_138644 ]

jglick commented on HUDSON-6337:
--------------------------------

Worked last I checked, and there is test coverage for this. Is still still reproducible for you? Do you have a minimal test case?

> Mercurial Polling does not work for 'modules'
> ---------------------------------------------
>
>                 Key: HUDSON-6337
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6337
>             Project: Hudson
>          Issue Type: Bug
>          Components: mercurial
>         Environment: Hudson ver. 1.351
>            Reporter: m_burger
>            Assignee: jglick
>
> I am using the "Modules" feature of the Mercurial SCM plugin. Unfortunately, this feature does not work as expected.
> After starting Hudson, a build will be triggered as soon as a file in the specified module was changed. After a change to a file outside this module, the plugin does not trigger a build as expected ("No changes").
> However, although there is a change to a file within the module afterward, the plugin does not detect any change ("No changes"). Though, the "Last Mercurial Polling Log" shows these changed files; there are lines starting with "files:<MODULE>/..."
> Restarting Hudson or reloading its configuration does work as a work-around: the next poll will trigger a build - until there is a change outside the module again.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6337) Mercurial Polling does not work for 'modules'

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139056#action_139056 ]

maxschweitzer commented on HUDSON-6337:
---------------------------------------

The error still exists with mercurial-plugin 1.30 and hudson 1.360. Below you can find the obfuscated polling log.

"file2.java" in module "job1" was modified but "job1" build was never triggered.

Started on 01.06.2010 11:35:37
[workspace] $ hg incoming --style "/hudson/jobs/job1/workspace/tmp6554723463433914461style" --no-merges --rev default
comparing with *******************
searching for changes
id:d86b04c63d49ca532342347a93f0ce65cc95b132
files:job2/src/main/webapp/WEB-INF/templates/template1.jsp:
id:5a9ae558edb70dfdddd5979a2b1c1f3cdb43cbed
files:job2/src/main/java/file1.java:job2/src/main/java/file3.java:job2/src/main/webapp/WEB-INF/templates/template2.jsp:job2/src/main/webapp/WEB-INF/templates/template3.jsp:
id:c929549a063426434370b8bbb1e1dbc595d449c3
files:info.txt:
id:deaac939488c0c40d551234234a44da674bee588
files:job2/src/main/webapp/WEB-INF/templates/template5.jsp:
id:587ff66fca234157a20c7ec3243cfd89760f927b
files:job2/src/main/webapp/WEB-INF/templates/template6.jsp:job2/src/main/webapp/WEB-INF/templates/template7.jsp:job1/src/main/java/file2.java

> Mercurial Polling does not work for 'modules'
> ---------------------------------------------
>
>                 Key: HUDSON-6337
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6337
>             Project: Hudson
>          Issue Type: Bug
>          Components: mercurial
>         Environment: Hudson ver. 1.351
>            Reporter: m_burger
>            Assignee: jglick
>
> I am using the "Modules" feature of the Mercurial SCM plugin. Unfortunately, this feature does not work as expected.
> After starting Hudson, a build will be triggered as soon as a file in the specified module was changed. After a change to a file outside this module, the plugin does not trigger a build as expected ("No changes").
> However, although there is a change to a file within the module afterward, the plugin does not detect any change ("No changes"). Though, the "Last Mercurial Polling Log" shows these changed files; there are lines starting with "files:<MODULE>/..."
> Restarting Hudson or reloading its configuration does work as a work-around: the next poll will trigger a build - until there is a change outside the module again.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6337) Mercurial Polling does not work for 'modules'

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139284#action_139284 ]

jglick commented on HUDSON-6337:
--------------------------------

I would need a test case to investigate.

> Mercurial Polling does not work for 'modules'
> ---------------------------------------------
>
>                 Key: HUDSON-6337
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6337
>             Project: Hudson
>          Issue Type: Bug
>          Components: mercurial
>         Environment: Hudson ver. 1.351
>            Reporter: m_burger
>            Assignee: jglick
>
> I am using the "Modules" feature of the Mercurial SCM plugin. Unfortunately, this feature does not work as expected.
> After starting Hudson, a build will be triggered as soon as a file in the specified module was changed. After a change to a file outside this module, the plugin does not trigger a build as expected ("No changes").
> However, although there is a change to a file within the module afterward, the plugin does not detect any change ("No changes"). Though, the "Last Mercurial Polling Log" shows these changed files; there are lines starting with "files:<MODULE>/..."
> Restarting Hudson or reloading its configuration does work as a work-around: the next poll will trigger a build - until there is a change outside the module again.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6337) Mercurial Polling does not work for 'modules'

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139289#action_139289 ]

dznz commented on HUDSON-6337:
------------------------------

I get this reliably on my system as well. Not sure what you need as a test case?

> Mercurial Polling does not work for 'modules'
> ---------------------------------------------
>
>                 Key: HUDSON-6337
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6337
>             Project: Hudson
>          Issue Type: Bug
>          Components: mercurial
>         Environment: Hudson ver. 1.351
>            Reporter: m_burger
>            Assignee: jglick
>
> I am using the "Modules" feature of the Mercurial SCM plugin. Unfortunately, this feature does not work as expected.
> After starting Hudson, a build will be triggered as soon as a file in the specified module was changed. After a change to a file outside this module, the plugin does not trigger a build as expected ("No changes").
> However, although there is a change to a file within the module afterward, the plugin does not detect any change ("No changes"). Though, the "Last Mercurial Polling Log" shows these changed files; there are lines starting with "files:<MODULE>/..."
> Restarting Hudson or reloading its configuration does work as a work-around: the next poll will trigger a build - until there is a change outside the module again.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Work started: (HUDSON-6337) Mercurial Polling does not work for 'modules'

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on HUDSON-6337 started by jglick.

> Mercurial Polling does not work for 'modules'
> ---------------------------------------------
>
>                 Key: HUDSON-6337
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6337
>             Project: Hudson
>          Issue Type: Bug
>          Components: mercurial
>         Environment: Hudson ver. 1.351
>            Reporter: m_burger
>            Assignee: jglick
>
> I am using the "Modules" feature of the Mercurial SCM plugin. Unfortunately, this feature does not work as expected.
> After starting Hudson, a build will be triggered as soon as a file in the specified module was changed. After a change to a file outside this module, the plugin does not trigger a build as expected ("No changes").
> However, although there is a change to a file within the module afterward, the plugin does not detect any change ("No changes"). Though, the "Last Mercurial Polling Log" shows these changed files; there are lines starting with "files:<MODULE>/..."
> Restarting Hudson or reloading its configuration does work as a work-around: the next poll will trigger a build - until there is a change outside the module again.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6337) Mercurial Polling does not work for 'modules'

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139349#action_139349 ]

jglick commented on HUDSON-6337:
--------------------------------

kohsuke's 27063 seems to have broken things; if {{parseIncomingOutput}} gets

{noformat}
id:123
files:ignored:
id:456
files:relevant:
{noformat}

where 123 was present in a previous poll,

{noformat}
                if (id.equals(baseline.id)) {
                    break; // no need to go beyond this line
                }
{noformat}

stops the parsing at 123 since that is baseline.id. Passing {{--newest-first}} to incoming seems to work.

Still trying to reproduce in a test case, however; calling {{Project.poll(TaskListener)}} appears to work fine.

> Mercurial Polling does not work for 'modules'
> ---------------------------------------------
>
>                 Key: HUDSON-6337
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6337
>             Project: Hudson
>          Issue Type: Bug
>          Components: mercurial
>         Environment: Hudson ver. 1.351
>            Reporter: m_burger
>            Assignee: jglick
>
> I am using the "Modules" feature of the Mercurial SCM plugin. Unfortunately, this feature does not work as expected.
> After starting Hudson, a build will be triggered as soon as a file in the specified module was changed. After a change to a file outside this module, the plugin does not trigger a build as expected ("No changes").
> However, although there is a change to a file within the module afterward, the plugin does not detect any change ("No changes"). Though, the "Last Mercurial Polling Log" shows these changed files; there are lines starting with "files:<MODULE>/..."
> Restarting Hudson or reloading its configuration does work as a work-around: the next poll will trigger a build - until there is a change outside the module again.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6337) Mercurial Polling does not work for 'modules'

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139350#action_139350 ]

scm_issue_link commented on HUDSON-6337:
----------------------------------------

Code changed in hudson
User: : jglick
Path:
 trunk/hudson/plugins/mercurial/src/main/java/hudson/plugins/mercurial/MercurialSCM.java
 trunk/hudson/plugins/mercurial/src/main/java/hudson/plugins/mercurial/MercurialTagAction.java
 trunk/hudson/plugins/mercurial/src/test/java/hudson/plugins/mercurial/MercurialSCMTest.java
http://hudson-ci.org/commit/31922
Log:
[HUDSON-6337] Polling logic broken for modules.


> Mercurial Polling does not work for 'modules'
> ---------------------------------------------
>
>                 Key: HUDSON-6337
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6337
>             Project: Hudson
>          Issue Type: Bug
>          Components: mercurial
>         Environment: Hudson ver. 1.351
>            Reporter: m_burger
>            Assignee: jglick
>
> I am using the "Modules" feature of the Mercurial SCM plugin. Unfortunately, this feature does not work as expected.
> After starting Hudson, a build will be triggered as soon as a file in the specified module was changed. After a change to a file outside this module, the plugin does not trigger a build as expected ("No changes").
> However, although there is a change to a file within the module afterward, the plugin does not detect any change ("No changes"). Though, the "Last Mercurial Polling Log" shows these changed files; there are lines starting with "files:<MODULE>/..."
> Restarting Hudson or reloading its configuration does work as a work-around: the next poll will trigger a build - until there is a change outside the module again.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Resolved: (HUDSON-6337) Mercurial Polling does not work for 'modules'

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jglick resolved HUDSON-6337.
----------------------------

    Resolution: Fixed

> Mercurial Polling does not work for 'modules'
> ---------------------------------------------
>
>                 Key: HUDSON-6337
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6337
>             Project: Hudson
>          Issue Type: Bug
>          Components: mercurial
>         Environment: Hudson ver. 1.351
>            Reporter: m_burger
>            Assignee: jglick
>
> I am using the "Modules" feature of the Mercurial SCM plugin. Unfortunately, this feature does not work as expected.
> After starting Hudson, a build will be triggered as soon as a file in the specified module was changed. After a change to a file outside this module, the plugin does not trigger a build as expected ("No changes").
> However, although there is a change to a file within the module afterward, the plugin does not detect any change ("No changes"). Though, the "Last Mercurial Polling Log" shows these changed files; there are lines starting with "files:<MODULE>/..."
> Restarting Hudson or reloading its configuration does work as a work-around: the next poll will trigger a build - until there is a change outside the module again.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6337) Mercurial Polling does not work for 'modules'

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139364#action_139364 ]

dznz commented on HUDSON-6337:
------------------------------

Wonderful, looking forward to applying that fix. Thanks for looking into that!

> Mercurial Polling does not work for 'modules'
> ---------------------------------------------
>
>                 Key: HUDSON-6337
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6337
>             Project: Hudson
>          Issue Type: Bug
>          Components: mercurial
>         Environment: Hudson ver. 1.351
>            Reporter: m_burger
>            Assignee: jglick
>
> I am using the "Modules" feature of the Mercurial SCM plugin. Unfortunately, this feature does not work as expected.
> After starting Hudson, a build will be triggered as soon as a file in the specified module was changed. After a change to a file outside this module, the plugin does not trigger a build as expected ("No changes").
> However, although there is a change to a file within the module afterward, the plugin does not detect any change ("No changes"). Though, the "Last Mercurial Polling Log" shows these changed files; there are lines starting with "files:<MODULE>/..."
> Restarting Hudson or reloading its configuration does work as a work-around: the next poll will trigger a build - until there is a change outside the module again.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]