Quantcast

[JIRA] Created: (JENKINS-10011) Building on a remote node does not preserve the Violations

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] Created: (JENKINS-10011) Building on a remote node does not preserve the Violations

JIRA noreply@jenkins-ci.org
Building on a remote node does not preserve the Violations
----------------------------------------------------------

                 Key: JENKINS-10011
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10011
             Project: Jenkins
          Issue Type: Bug
          Components: violations
    Affects Versions: current
            Reporter: chemphill
            Assignee: peterkittreilly
            Priority: Critical


I am building on a remove slave node and all Violations are reported as none.

jslint No reports pmd No reports

There are, however, violations.  From the console output:

jslint:
   [jslint] JSLint: 85 errors in 5 files


I have the project setup to report Violations for PMD and jslint and I have confirmed that the xml files listed in the configuration do exist and have data.

The master's builds/#/violations/violations.xml file is basically empty:

<violations>
</violations>

The only thing in the log is the success from the run:

INFO: fnd-webserver-backoffice #7 main build action completed: SUCCESS

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] Issue Comment Edited: (JENKINS-10011) Building on a remote node does not preserve the Violations

JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-10011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150729#comment-150729 ]

Laurent Roger edited comment on JENKINS-10011 at 7/21/11 11:05 AM:
-------------------------------------------------------------------

did you check the "report violation" configuration settings : filename pattern ?

i had the same problem with jslint : using **/**/jslint.xml solved the problem

if it's corrected with this, i suggest to close the issue.

      was (Author: lc3t35):
    did you check the "report violation" configuration settings : filename pattern ?

i had the same problem with jslint : using **/**/jslint.xml solved the problem
 

> Building on a remote node does not preserve the Violations
> ----------------------------------------------------------
>
>                 Key: JENKINS-10011
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10011
>             Project: Jenkins
>          Issue Type: Bug
>          Components: violations
>    Affects Versions: current
>            Reporter: chemphill
>            Assignee: peterkittreilly
>            Priority: Critical
>
> I am building on a remove slave node and all Violations are reported as none.
> jslint No reports pmd No reports
> There are, however, violations.  From the console output:
> jslint:
>    [jslint] JSLint: 85 errors in 5 files
> I have the project setup to report Violations for PMD and jslint and I have confirmed that the xml files listed in the configuration do exist and have data.
> The master's builds/#/violations/violations.xml file is basically empty:
> <violations>
> </violations>
> The only thing in the log is the success from the run:
> INFO: fnd-webserver-backoffice #7 main build action completed: SUCCESS

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] Commented: (JENKINS-10011) Building on a remote node does not preserve the Violations

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-10011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150729#comment-150729 ]

Laurent Roger commented on JENKINS-10011:
-----------------------------------------

did you check the "report violation" configuration settings : filename pattern ?

i had the same problem with jslint : using **/**/jslint.xml solved the problem

> Building on a remote node does not preserve the Violations
> ----------------------------------------------------------
>
>                 Key: JENKINS-10011
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10011
>             Project: Jenkins
>          Issue Type: Bug
>          Components: violations
>    Affects Versions: current
>            Reporter: chemphill
>            Assignee: peterkittreilly
>            Priority: Critical
>
> I am building on a remove slave node and all Violations are reported as none.
> jslint No reports pmd No reports
> There are, however, violations.  From the console output:
> jslint:
>    [jslint] JSLint: 85 errors in 5 files
> I have the project setup to report Violations for PMD and jslint and I have confirmed that the xml files listed in the configuration do exist and have data.
> The master's builds/#/violations/violations.xml file is basically empty:
> <violations>
> </violations>
> The only thing in the log is the success from the run:
> INFO: fnd-webserver-backoffice #7 main build action completed: SUCCESS

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] Issue Comment Edited: (JENKINS-10011) Building on a remote node does not preserve the Violations

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-10011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150729#comment-150729 ]

Laurent Roger edited comment on JENKINS-10011 at 7/21/11 11:07 AM:
-------------------------------------------------------------------

did you check the "report violation" configuration settings : filename pattern ?

i had the same problem with jslint : using **/**/jslint.xml solved the problem

the files must be visible in the workspace, where does the remote node write xml files ?


      was (Author: lc3t35):
    did you check the "report violation" configuration settings : filename pattern ?

i had the same problem with jslint : using **/**/jslint.xml solved the problem

if it's corrected with this, i suggest to close the issue.
 

> Building on a remote node does not preserve the Violations
> ----------------------------------------------------------
>
>                 Key: JENKINS-10011
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10011
>             Project: Jenkins
>          Issue Type: Bug
>          Components: violations
>    Affects Versions: current
>            Reporter: chemphill
>            Assignee: peterkittreilly
>            Priority: Critical
>
> I am building on a remove slave node and all Violations are reported as none.
> jslint No reports pmd No reports
> There are, however, violations.  From the console output:
> jslint:
>    [jslint] JSLint: 85 errors in 5 files
> I have the project setup to report Violations for PMD and jslint and I have confirmed that the xml files listed in the configuration do exist and have data.
> The master's builds/#/violations/violations.xml file is basically empty:
> <violations>
> </violations>
> The only thing in the log is the success from the run:
> INFO: fnd-webserver-backoffice #7 main build action completed: SUCCESS

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] Issue Comment Edited: (JENKINS-10011) Building on a remote node does not preserve the Violations

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-10011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150729#comment-150729 ]

Laurent Roger edited comment on JENKINS-10011 at 7/21/11 11:07 AM:
-------------------------------------------------------------------

did you check the "report violation" configuration settings : filename pattern ?

i had the same problem with jslint : using \*\*/\*\*/jslint.xml solved the problem

the files must be visible in the workspace, where does the remote node write xml files ?


      was (Author: lc3t35):
    did you check the "report violation" configuration settings : filename pattern ?

i had the same problem with jslint : using **/**/jslint.xml solved the problem

the files must be visible in the workspace, where does the remote node write xml files ?

 

> Building on a remote node does not preserve the Violations
> ----------------------------------------------------------
>
>                 Key: JENKINS-10011
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10011
>             Project: Jenkins
>          Issue Type: Bug
>          Components: violations
>    Affects Versions: current
>            Reporter: chemphill
>            Assignee: peterkittreilly
>            Priority: Critical
>
> I am building on a remove slave node and all Violations are reported as none.
> jslint No reports pmd No reports
> There are, however, violations.  From the console output:
> jslint:
>    [jslint] JSLint: 85 errors in 5 files
> I have the project setup to report Violations for PMD and jslint and I have confirmed that the xml files listed in the configuration do exist and have data.
> The master's builds/#/violations/violations.xml file is basically empty:
> <violations>
> </violations>
> The only thing in the log is the success from the run:
> INFO: fnd-webserver-backoffice #7 main build action completed: SUCCESS

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] Issue Comment Edited: (JENKINS-10011) Building on a remote node does not preserve the Violations

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-10011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150729#comment-150729 ]

Laurent Roger edited comment on JENKINS-10011 at 7/21/11 12:38 PM:
-------------------------------------------------------------------

did you check the "report violation" configuration settings : filename pattern ?

i had the same problem with jslint : using \*\*/\*\*/jslint.xml seems to solve the problem

i have a graphic output now but the data is not correct : multiple and old files/violations ...

Needs deeper investigation ...

      was (Author: lc3t35):
    did you check the "report violation" configuration settings : filename pattern ?

i had the same problem with jslint : using \*\*/\*\*/jslint.xml solved the problem

the files must be visible in the workspace, where does the remote node write xml files ?

 

> Building on a remote node does not preserve the Violations
> ----------------------------------------------------------
>
>                 Key: JENKINS-10011
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10011
>             Project: Jenkins
>          Issue Type: Bug
>          Components: violations
>    Affects Versions: current
>            Reporter: chemphill
>            Assignee: peterkittreilly
>            Priority: Critical
>
> I am building on a remove slave node and all Violations are reported as none.
> jslint No reports pmd No reports
> There are, however, violations.  From the console output:
> jslint:
>    [jslint] JSLint: 85 errors in 5 files
> I have the project setup to report Violations for PMD and jslint and I have confirmed that the xml files listed in the configuration do exist and have data.
> The master's builds/#/violations/violations.xml file is basically empty:
> <violations>
> </violations>
> The only thing in the log is the success from the run:
> INFO: fnd-webserver-backoffice #7 main build action completed: SUCCESS

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-10011) Building on a remote node does not preserve the Violations

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
evernat resolved Bug JENKINS-10011 as Incomplete

No response from the reporter, so closing as incomplete.
Please reopen if needed.

Change By: evernat (20/Jul/12 4:51 PM)
Status: Open Resolved
Resolution: Incomplete
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
Loading...