0

DevOptics pollutes build logs with DevOpticsMavenPublisher entries

Hello,

 

When using the DevOptics plugin on Jenkins, we notice that many of our build logs are polluted with many entries such as:

[DevOpticsMavenPublisher] produced artifact - label: ..., id: ...

and

[DevOpticsMavenPublisher] consumed dependency - label: ..., id: ...

For some jobs, these traces account for a large % of the total log. It may be because the module is large and contains lots of sub-modules and consumes lots of artifacts, but still, these entries are not really useful and essentially pollute the logs.

Is there a way to keep DevOptics less verbose here?

Thanks,

David

4 comments

  • 0
    Avatar
    Alejandro Jurado Walls

    Hi David,

     

    Thank you for opening this thread. There is no way to remove those build log messages yet though.

    Your post will help us improve DevOptics logging. We already have an internal ticket to accomplish it and we've added your comments in the ticket.

    Regards,

    Alejandro.

    Edited by Alejandro Jurado Walls
  • 0
    Avatar
    David Raymond

    Thanks Alejandro.

    Is there a way for my to follow the progress and know when some improvement will be implemented?

    DevOptics seems like a very useful plugin, for which we may eventually go with a paying license, but for now, we have to disable it because of this problem.

    Thanks,

    David

  • 0
    Avatar
    Alejandro Jurado Walls

    Hi David,

    There are two places where you can follow the release notes for DevOptics:

    Regards,

    Alejandro.

  • 0
    Avatar
    Alejandro Jurado Walls

    Hi David,

    We have released a new version that addresses this: https://release-notes.cloudbees.com/release/145/1.1863

    Now, instead of excessive logging, you just get a single, brief summary line:

    [DevOpticsMavenPublisher] dependencies consumed: 106, artifacts produced: 3

     

    Regards,

    Alejandro.

    Edited by Alejandro Jurado Walls
Please sign in to leave a comment.