Quality of repository
|
View:
New views
12 Messages
—
Rating Filter:
Alert me
|
 |
Quality of repository
by MALICE
::
Rate this Message:
Hi all,
I've got a feeling that some of my deployed artifacts have an incorrect checksum. This probably happened during the time we didn't use Nexus yet or during the restructuring of the repositories I just did. Anyway, I was thinking that it might be nice to have a way of asking Nexus to validate all artifacts in hosted repositories and report on the result. Or maybe have Nexus delete all checksums and recreate them. Is this currently possible or do I need to play around with extensions myself? If I have to look into extensions, could on of the devs perhaps give me some pointers on where I can look at the checksum-code? Thanks, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
|
|
Re: Quality of repository
by Anders Hammar
::
Rate this Message:
There is a task in Nexus to recreate the checksums. Use that and you should be fine!
See "Rebuild Maven Metadata Files" at http://www.sonatype.com/people/2009/09/nexus-scheduled-tasks/ /Anders On Mon, Nov 2, 2009 at 00:25, Roland Asmann <Roland.Asmann@...> wrote: Hi all, |
|
|
Re: Quality of repository
by MALICE
::
Rate this Message:
According to the description you pointed to it only VALIDATES the checksums...
And no mention about reporting on it... On Monday 02 November 2009 06:32, Anders Hammar wrote: > There is a task in Nexus to recreate the checksums. Use that and you should > be fine! > See "Rebuild Maven Metadata Files" at > http://www.sonatype.com/people/2009/09/nexus-scheduled-tasks/ > > /Anders > > On Mon, Nov 2, 2009 at 00:25, Roland Asmann <Roland.Asmann@...> wrote: > > Hi all, > > > > I've got a feeling that some of my deployed artifacts have an incorrect > > checksum. This probably happened during the time we didn't use Nexus yet > > or during the restructuring of the repositories I just did. > > > > Anyway, I was thinking that it might be nice to have a way of asking > > Nexus to validate all artifacts in hosted repositories and report on the > > result. Or maybe have Nexus delete all checksums and recreate them. Is > > this currently possible or do I need to play around with extensions > > myself? > > > > If I have to look into extensions, could on of the devs perhaps give me > > some pointers on where I can look at the checksum-code? > > > > Thanks, > > > > Roland > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: nexus-user-unsubscribe@... > > For additional commands, e-mail: nexus-user-help@... -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: Roland.Asmann@... Web: www.cfc.at --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
|
|
Re: Quality of repository
by Tamás Cservenák
::
Rate this Message:
Nope, the task recreates checksums and maven-metadata.xml files, but reporting is not yet done.
Hope helps, ~t~
On Mon, Nov 2, 2009 at 11:32 AM, Roland Asmann <Roland.Asmann@...> wrote: According to the description you pointed to it only VALIDATES the checksums... |
|
|
Re: Quality of repository
by MALICE
::
Rate this Message:
OK, great! I'll use that on my hosted repo's then!
Thanks! On Monday 02 November 2009 11:36, Tamás Cservenák wrote: > Nope, the task recreates checksums and maven-metadata.xml files, but > reporting is not yet done. > > > Hope helps, > ~t~ > > On Mon, Nov 2, 2009 at 11:32 AM, Roland Asmann <Roland.Asmann@...> wrote: > > According to the description you pointed to it only VALIDATES the > > checksums... > > And no mention about reporting on it... > > > > On Monday 02 November 2009 06:32, Anders Hammar wrote: > > > There is a task in Nexus to recreate the checksums. Use that and you > > > > should > > > > > be fine! > > > See "Rebuild Maven Metadata Files" at > > > http://www.sonatype.com/people/2009/09/nexus-scheduled-tasks/ > > > > > > /Anders > > > > > > On Mon, Nov 2, 2009 at 00:25, Roland Asmann <Roland.Asmann@...> > > > > wrote: > > > > Hi all, > > > > > > > > I've got a feeling that some of my deployed artifacts have an > > > > incorrect checksum. This probably happened during the time we didn't > > > > use Nexus > > > > yet > > > > > > or during the restructuring of the repositories I just did. > > > > > > > > Anyway, I was thinking that it might be nice to have a way of asking > > > > Nexus to validate all artifacts in hosted repositories and report on > > > > the > > > > > > result. Or maybe have Nexus delete all checksums and recreate them. > > > > Is this currently possible or do I need to play around with > > > > extensions myself? > > > > > > > > If I have to look into extensions, could on of the devs perhaps give > > > > me some pointers on where I can look at the checksum-code? > > > > > > > > Thanks, > > > > > > > > Roland > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: nexus-user-unsubscribe@... > > > > For additional commands, e-mail: nexus-user-help@... > > > > -- > > Roland Asmann > > > > CFC Informationssysteme Entwicklungsgesellschaft m.b.H > > Bäckerstrasse 1/2/7 > > A-1010 Wien > > FN 266155f, Handelsgericht Wien > > > > Tel.: +43/1/513 88 77 - 27 > > Fax.: +43/1/513 88 62 > > Email: Roland.Asmann@... > > Web: www.cfc.at > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: nexus-user-unsubscribe@... > > For additional commands, e-mail: nexus-user-help@... -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: Roland.Asmann@... Web: www.cfc.at --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
|
|
Re: Quality of repository
by Holger Hoffstätte-4
::
Rate this Message:
On Mon, 02 Nov 2009 06:32:03 +0100, Anders Hammar wrote:
> There is a task in Nexus to recreate the checksums. Use that and you > should be fine! > See "Rebuild Maven Metadata Files" at > http://www.sonatype.com/people/2009/09/nexus-scheduled-tasks/ So how does the server know whether the artifact is actually corrupt or not? It's not enough to simply advertise "any" checksum, recreated or not - it has to be the correct one, and the only one who can make that call is the original creator. -h --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
|
|
Re: Re: Quality of repository
by MALICE
::
Rate this Message:
I was just thinking of that... I think this job should just report what it
found, so that the creator can fix check if the artifact is correct and then somehow tell Nexus to create a new checksum. And on proxied repos it might be a good idea to delete both the checksum and artifact and have Nexus download it anew... Or if the checksum is wrong on the remote server, somehow mark this and report about it... Guess, I'll check out the sources to Nexus and poke around a bit... Maybe something I'll even come around to writing my first plugin one of these days... :-) On Monday 02 November 2009 13:01, Holger Hoffstaette wrote: > On Mon, 02 Nov 2009 06:32:03 +0100, Anders Hammar wrote: > > There is a task in Nexus to recreate the checksums. Use that and you > > should be fine! > > See "Rebuild Maven Metadata Files" at > > http://www.sonatype.com/people/2009/09/nexus-scheduled-tasks/ > > So how does the server know whether the artifact is actually corrupt or > not? It's not enough to simply advertise "any" checksum, recreated or not > - it has to be the correct one, and the only one who can make that call is > the original creator. > > -h > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: nexus-user-unsubscribe@... > For additional commands, e-mail: nexus-user-help@... -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: Roland.Asmann@... Web: www.cfc.at --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
|
|
Re: Re: Quality of repository
by Anders Hammar
::
Rate this Message:
I don't think it checks the jar artifact, it checks the Maven metadata including the checksum file(s). If they are not correct, they are fixed.
As you point out, verifying the actual jar artifact is tougher. Possibly you need to write your own plugin to do that. It all depends what you want to verify. /Anders On Mon, Nov 2, 2009 at 13:01, Holger Hoffstaette <holger.hoffstaette@...> wrote: On Mon, 02 Nov 2009 06:32:03 +0100, Anders Hammar wrote: |
|
|
Re: Re: Quality of repository
by Anders Hammar
::
Rate this Message:
It could be a bad idea to delete a proxied artifact. If any of your old builds depends on it (depends on how corrupt it is) and it doesn't exist in the remote repo any more, you would not be able to re-build that project.
/Anders On Mon, Nov 2, 2009 at 14:05, Roland Asmann <Roland.Asmann@...> wrote: I was just thinking of that... I think this job should just report what it |
|
|
Re: Re: Quality of repository
by Tamás Cservenák
::
Rate this Message:
Proxy repository cache is just as it's name says: cache. It is (or should be considered as) transient. So, if your remote repository does not contain an artifact that is in your cache, would mean:
a) you changed the remote storage URL, and that repo is not that repo anymore (more about this strange sentence below)
b) you are proxying a repository maintained by "bad people".... (nothing much to do here). Remote repository is (should be) eternal. No deletion should happen in there. "not that repo anymore" --- we have a discussion within sonatype: let's say you have a proxy repository set up to point to remote repository with URL http://repoA/. You use it, and then you change the remote repository URL to http://repoB/.
So, now the object of discussion: IMO. the cache of your proxy repository should be _deleted_, since there is no way to detect is http://repoA/ and http://repoB/ actually the "same repository".
Other claims that current behaviour of Nexus is "correct": just the URL is changed and nothing happens with cache. The 2nd case may you bring to a state, that you _intentionally_ "reuse" an existing proxy repository to point it from remote repo A to remote repo B (two different reposes!), and to still be able to build stuff that should be _not_ buildable with repoB (no artifacts needed in there).
Thanks, ~t~ On Mon, Nov 2, 2009 at 3:52 PM, Anders Hammar <anders@...> wrote: It could be a bad idea to delete a proxied artifact. If any of your old builds depends on it (depends on how corrupt it is) and it doesn't exist in the remote repo any more, you would not be able to re-build that project. |
|
|
Re: Re: Quality of repository
by Anders Hammar
::
Rate this Message:
Well, there are examples of maven repositories where people change releases. I was just aware of that a week ago or so regarding eviware's soapUI maven repo. They deploy new stuff on top of already released artifacts. Could have very bad effects on your builds, but making sure your cache stays intact would prevent you from some headache...
In my opinion, you should never delete your cache unless you know what your doing. And if you still trying to delete it, then you don't know what you're doing. :-) /Anders 2009/11/2 Tamás Cservenák <tamas@...> Proxy repository cache is just as it's name says: cache. It is (or should be considered as) transient. So, if your remote repository does not contain an artifact that is in your cache, would mean: |
|
|
Re: Re: Quality of repository
by Tamás Cservenák
::
Rate this Message:
Changing releases := bad
Remote repository should be eternal. Solving this with proxy cache is also a veery hokey(*) workaround... * = term used by Brian for "dirty tricks" ;)
Thanks, ~t~ On Mon, Nov 2, 2009 at 4:18 PM, Anders Hammar <anders@...> wrote: Well, there are examples of maven repositories where people change releases. I was just aware of that a week ago or so regarding eviware's soapUI maven repo. They deploy new stuff on top of already released artifacts. Could have very bad effects on your builds, but making sure your cache stays intact would prevent you from some headache... |
| Free embeddable forum powered by Nabble | Forum Help |
