Excessive "checking for updates" on Travis CI

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Excessive "checking for updates" on Travis CI

org.apache.maven.user
Hello.

I use the free Travis CI service to build my various projects on each
commit. I have a project that has a rather large number of modules (~90)
and upon building each module, I see lots of this in the log:

[INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype
[INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype-apache
[INFO] artifact com.io7m.jequality:com.io7m.jequality.core: checking for updates from sonatype
[INFO] artifact com.io7m.jequality:com.io7m.jequality.core: checking for updates from sonatype-apache
[INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype
[INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype-apache
[INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype
[INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype-apache
[INFO] artifact com.io7m.jtensors:com.io7m.jtensors.core: checking for updates from sonatype
[INFO] artifact com.io7m.jtensors:com.io7m.jtensors.core: checking for updates from sonatype-apache
[INFO] artifact it.unimi.dsi:fastutil: checking for updates from sonatype
[INFO] artifact it.unimi.dsi:fastutil: checking for updates from sonatype-apache
[INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype
[INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype-apache
[INFO] artifact com.io7m.mutable.numbers:com.io7m.mutable.numbers.core: checking for updates from sonatype
[INFO] artifact com.io7m.mutable.numbers:com.io7m.mutable.numbers.core: checking for updates from sonatype-apache
[INFO] artifact com.io7m.jtensors:com.io7m.jtensors.storage.bytebuffered: checking for updates from sonatype
[INFO] artifact com.io7m.jtensors:com.io7m.jtensors.storage.bytebuffered: checking for updates from sonatype-apache
[INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype
[INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype-apache
[INFO] artifact com.io7m.mutable.numbers:com.io7m.mutable.numbers.core: checking for updates from sonatype
[INFO] artifact com.io7m.mutable.numbers:com.io7m.mutable.numbers.core: checking for updates from sonatype-apache
[INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype
[INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype-apache
[INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype
[INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype-apache
[INFO] artifact com.io7m.ieee754b16:com.io7m.ieee754b16.core: checking for updates from sonatype
[INFO] artifact com.io7m.ieee754b16:com.io7m.ieee754b16.core: checking
for updates from sonatype-apache

Note that not only are these artifacts being checked redundantly (because
an artifact may be checked at least once per module), they're also being
checked multiple times in the same plugin execution!

You can see an example of a build log here:

  https://api.travis-ci.org/jobs/248453940/log.txt

I'm actually starting to hit the 4mb log file size limit on Travis due
to the sheer amount of output produced.

The project's source code, for the curious, is here:

  https://github.com/io7m/r2

Is there some way to get these redundant checks to stop? Failing that,
is there a way to get Maven to shut up about it?

M

attachment0 (871 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Excessive "checking for updates" on Travis CI

Karl Heinz Marbaise-3
HI,

first you are using version ranges...that's the reason for that...

Simple recommendation I can give is:  Don't use version ranges...


Kind regards
Karl Heinz Marbaise

On 29/06/17 19:13, Mark Raynsford wrote:

> Hello.
>
> I use the free Travis CI service to build my various projects on each
> commit. I have a project that has a rather large number of modules (~90)
> and upon building each module, I see lots of this in the log:
>
> [INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype
> [INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype-apache
> [INFO] artifact com.io7m.jequality:com.io7m.jequality.core: checking for updates from sonatype
> [INFO] artifact com.io7m.jequality:com.io7m.jequality.core: checking for updates from sonatype-apache
> [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype
> [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype-apache
> [INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype
> [INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype-apache
> [INFO] artifact com.io7m.jtensors:com.io7m.jtensors.core: checking for updates from sonatype
> [INFO] artifact com.io7m.jtensors:com.io7m.jtensors.core: checking for updates from sonatype-apache
> [INFO] artifact it.unimi.dsi:fastutil: checking for updates from sonatype
> [INFO] artifact it.unimi.dsi:fastutil: checking for updates from sonatype-apache
> [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype
> [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype-apache
> [INFO] artifact com.io7m.mutable.numbers:com.io7m.mutable.numbers.core: checking for updates from sonatype
> [INFO] artifact com.io7m.mutable.numbers:com.io7m.mutable.numbers.core: checking for updates from sonatype-apache
> [INFO] artifact com.io7m.jtensors:com.io7m.jtensors.storage.bytebuffered: checking for updates from sonatype
> [INFO] artifact com.io7m.jtensors:com.io7m.jtensors.storage.bytebuffered: checking for updates from sonatype-apache
> [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype
> [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype-apache
> [INFO] artifact com.io7m.mutable.numbers:com.io7m.mutable.numbers.core: checking for updates from sonatype
> [INFO] artifact com.io7m.mutable.numbers:com.io7m.mutable.numbers.core: checking for updates from sonatype-apache
> [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype
> [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype-apache
> [INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype
> [INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype-apache
> [INFO] artifact com.io7m.ieee754b16:com.io7m.ieee754b16.core: checking for updates from sonatype
> [INFO] artifact com.io7m.ieee754b16:com.io7m.ieee754b16.core: checking
> for updates from sonatype-apache
>
> Note that not only are these artifacts being checked redundantly (because
> an artifact may be checked at least once per module), they're also being
> checked multiple times in the same plugin execution!
>
> You can see an example of a build log here:
>
>    https://api.travis-ci.org/jobs/248453940/log.txt
>
> I'm actually starting to hit the 4mb log file size limit on Travis due
> to the sheer amount of output produced.
>
> The project's source code, for the curious, is here:
>
>    https://github.com/io7m/r2
>
> Is there some way to get these redundant checks to stop? Failing that,
> is there a way to get Maven to shut up about it?
>
> M
>

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

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

Re: Excessive "checking for updates" on Travis CI

org.apache.maven.user
On 2017-06-29T19:38:40 +0200
Karl Heinz Marbaise <[hidden email]> wrote:

> HI,
>
> first you are using version ranges...that's the reason for that...
>
> Simple recommendation I can give is:  Don't use version ranges...
>
>

Hello.

I maintain ~70 projects with complex interdependencies (this graph
shows a subset of them):

  https://raw.githubusercontent.com/io7m/universe/master/io7m.png

If I don't use version ranges, then when I update one dependency, I get
to update a ton of other packages too. I make frequent releases. Without
version ranges, my day would quickly be consumed by
version-number-incrementing busy work across a large number of packages
instead of getting actual development work done.

I make strong guarantees about API compatibility with my own packages,
including using japicmp to analyze the bytecode to ensure that I follow
semantic versioning correctly. Therefore, I use version ranges, and
have been for years.

Is there something else I could be doing?

M

attachment0 (871 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Excessive "checking for updates" on Travis CI

org.apache.maven.user
Apologies if that came off as rude, it wasn't intended to be. Upon
re-reading it, I think it came off as a bit harsh.

M

attachment0 (871 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Excessive "checking for updates" on Travis CI

Karl Heinz Marbaise-3
Hi Mark,

On 30/06/17 11:44, Mark Raynsford wrote:
> Apologies if that came off as rude, it wasn't intended to be. Upon
> re-reading it, I think it came off as a bit harsh.

No problem.

It's a real good behaviour of yours that you appologize for that...which
I didn't take as rude etc.

Kind regards
Karl Heinz Marbaise

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

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

Re: Excessive "checking for updates" on Travis CI

Karl Heinz Marbaise-3
In reply to this post by org.apache.maven.user
Hi Mark,

On 29/06/17 19:50, Mark Raynsford wrote:

> On 2017-06-29T19:38:40 +0200
> Karl Heinz Marbaise <[hidden email]> wrote:
>
>> HI,
>>
>> first you are using version ranges...that's the reason for that...
>>
>> Simple recommendation I can give is:  Don't use version ranges...
>>
>>
>
> Hello.
>
> I maintain ~70 projects with complex interdependencies (this graph
> shows a subset of them):
>
>    https://raw.githubusercontent.com/io7m/universe/master/io7m.png
>
> If I don't use version ranges, then when I update one dependency, I get
> to update a ton of other packages too. I make frequent releases. Without
> version ranges, my day would quickly be consumed by
> version-number-incrementing busy work across a large number of packages
> instead of getting actual development work done.
>
> I make strong guarantees about API compatibility with my own packages,
> including using japicmp to analyze the bytecode to ensure that I follow
> semantic versioning correctly. Therefore, I use version ranges, and
> have been for years.
>
> Is there something else I could be doing?

Maybe you can do this by using versions-maven-plugin to update deps etc.
via CI solution so you don't use versions ranges and prevent the request
against your repository manager and have the job done via the computer
instead of doing it manually and waisting your time with updating this...


Kind regards
Karl Heinz Marbaise

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

Loading...