|
'Recently deployed' system feed source
I'm currently evaluating Nexus for my company. It works great, thanks for that :-) But I do have a question.
For security reasons we need to log all deployment to all repositories. I found the 'Recently deployed' system feed; it contains everything I need (who deployed what to where and when). However, I would like to have the 'source' of this information, e.g. an XML or log file, so we can easily store it. This will also ensure that we get *all* information, not only the last n messages from the RSS feed.
Is this possible? Thank you for your reply in advance,
Rob ten Hove
|
|
Re: 'Recently deployed' system feed source
Hi Rob,
currently, you can access that information in programmatic way only. Or by pulling the feed. The truth is, that we were adding a lot of useful RSS feeds (and hence, we store a lot of interesting information in our "timeline"), but the actual feed implementation was neglected a bit.
The original idea was to make feeds: * searchable * parametrizable * pageable/shiftable in time
For example:
Will show you recent deployments into Sonatype Snapshots repository only.
Will show you the latest 100 instead of default 40, etc.
Recognized parameters:
r - repository ID, if not present will give entries for all
from - from entry (defaults to 0)
count - entry count (defaults to something like 40)
Please be aware, that implementation is not perfect, so for example, the "count" parameter gets applied _before_ permission filtering (we filter RSS feed entries against permissions that requester user has).... so again, there are known problems with feed implementation, and those will be fixed soon.
~t~ On Fri, Sep 25, 2009 at 10:23 AM, Rob ten Hove <rob@...> wrote:
I'm currently evaluating Nexus for my company. It works great, thanks for
that :-) But I do have a question.
For security reasons we need to log all deployment to all repositories. I
found the 'Recently deployed' system feed; it contains everything I need
(who deployed what to where and when). However, I would like to have the
'source' of this information, e.g. an XML or log file, so we can easily
store it. This will also ensure that we get *all* information, not only the
last n messages from the RSS feed.
Is this possible? Thank you for your reply in advance,
Rob ten Hove
--
View this message in context: http://www.nabble.com/%27Recently-deployed%27-system-feed-source-tp25608313p25608313.html
Sent from the Nexus Maven Repository Manager Users List mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...
|
|
Re: 'Recently deployed' system feed source
I guess with the new plugin framework in v1.4, it will also be easy for someone to create a plugin that stores this info an xml files for instance (thus, not relying on the timeline being intact)? /Anders
2009/9/25 Tamás Cservenák <tamas@...>
Hi Rob,
currently, you can access that information in programmatic way only. Or by pulling the feed. The truth is, that we were adding a lot of useful RSS feeds (and hence, we store a lot of interesting information in our "timeline"), but the actual feed implementation was neglected a bit.
The original idea was to make feeds: * searchable * parametrizable * pageable/shiftable in time
For example:
Will show you recent deployments into Sonatype Snapshots repository only.
Will show you the latest 100 instead of default 40, etc.
Recognized parameters:
r - repository ID, if not present will give entries for all
from - from entry (defaults to 0)
count - entry count (defaults to something like 40)
Please be aware, that implementation is not perfect, so for example, the "count" parameter gets applied _before_ permission filtering (we filter RSS feed entries against permissions that requester user has).... so again, there are known problems with feed implementation, and those will be fixed soon.
~t~ On Fri, Sep 25, 2009 at 10:23 AM, Rob ten Hove <rob@...> wrote:
I'm currently evaluating Nexus for my company. It works great, thanks for
that :-) But I do have a question.
For security reasons we need to log all deployment to all repositories. I
found the 'Recently deployed' system feed; it contains everything I need
(who deployed what to where and when). However, I would like to have the
'source' of this information, e.g. an XML or log file, so we can easily
store it. This will also ensure that we get *all* information, not only the
last n messages from the RSS feed.
Is this possible? Thank you for your reply in advance,
Rob ten Hove
--
View this message in context: http://www.nabble.com/%27Recently-deployed%27-system-feed-source-tp25608313p25608313.html
Sent from the Nexus Maven Repository Manager Users List mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...
|
|
Re: 'Recently deployed' system feed source
Something like this?
~t~ On Fri, Sep 25, 2009 at 10:55 AM, Anders Hammar <anders@...> wrote:
I guess with the new plugin framework in v1.4, it will also be easy for someone to create a plugin that stores this info an xml files for instance (thus, not relying on the timeline being intact)?
/Anders
2009/9/25 Tamás Cservenák <tamas@...>
Hi Rob,
currently, you can access that information in programmatic way only. Or by pulling the feed. The truth is, that we were adding a lot of useful RSS feeds (and hence, we store a lot of interesting information in our "timeline"), but the actual feed implementation was neglected a bit.
The original idea was to make feeds: * searchable * parametrizable * pageable/shiftable in time
For example:
Will show you recent deployments into Sonatype Snapshots repository only.
Will show you the latest 100 instead of default 40, etc.
Recognized parameters:
r - repository ID, if not present will give entries for all
from - from entry (defaults to 0)
count - entry count (defaults to something like 40)
Please be aware, that implementation is not perfect, so for example, the "count" parameter gets applied _before_ permission filtering (we filter RSS feed entries against permissions that requester user has).... so again, there are known problems with feed implementation, and those will be fixed soon.
~t~ On Fri, Sep 25, 2009 at 10:23 AM, Rob ten Hove <rob@...> wrote:
I'm currently evaluating Nexus for my company. It works great, thanks for
that :-) But I do have a question.
For security reasons we need to log all deployment to all repositories. I
found the 'Recently deployed' system feed; it contains everything I need
(who deployed what to where and when). However, I would like to have the
'source' of this information, e.g. an XML or log file, so we can easily
store it. This will also ensure that we get *all* information, not only the
last n messages from the RSS feed.
Is this possible? Thank you for your reply in advance,
Rob ten Hove
--
View this message in context: http://www.nabble.com/%27Recently-deployed%27-system-feed-source-tp25608313p25608313.html
Sent from the Nexus Maven Repository Manager Users List mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...
|
|
Re: 'Recently deployed' system feed source
Yes. I wonder who's going to be the first to release such an open source plugin... /A 2009/9/25 Tamás Cservenák <tamas@...>
Something like this?
~t~On Fri, Sep 25, 2009 at 10:55 AM, Anders Hammar <anders@...> wrote:
I guess with the new plugin framework in v1.4, it will also be easy for someone to create a plugin that stores this info an xml files for instance (thus, not relying on the timeline being intact)?
/Anders
2009/9/25 Tamás Cservenák <tamas@...>
Hi Rob,
currently, you can access that information in programmatic way only. Or by pulling the feed. The truth is, that we were adding a lot of useful RSS feeds (and hence, we store a lot of interesting information in our "timeline"), but the actual feed implementation was neglected a bit.
The original idea was to make feeds: * searchable * parametrizable * pageable/shiftable in time
For example:
Will show you recent deployments into Sonatype Snapshots repository only.
Will show you the latest 100 instead of default 40, etc.
Recognized parameters:
r - repository ID, if not present will give entries for all
from - from entry (defaults to 0)
count - entry count (defaults to something like 40)
Please be aware, that implementation is not perfect, so for example, the "count" parameter gets applied _before_ permission filtering (we filter RSS feed entries against permissions that requester user has).... so again, there are known problems with feed implementation, and those will be fixed soon.
~t~ On Fri, Sep 25, 2009 at 10:23 AM, Rob ten Hove <rob@...> wrote:
I'm currently evaluating Nexus for my company. It works great, thanks for
that :-) But I do have a question.
For security reasons we need to log all deployment to all repositories. I
found the 'Recently deployed' system feed; it contains everything I need
(who deployed what to where and when). However, I would like to have the
'source' of this information, e.g. an XML or log file, so we can easily
store it. This will also ensure that we get *all* information, not only the
last n messages from the RSS feed.
Is this possible? Thank you for your reply in advance,
Rob ten Hove
--
View this message in context: http://www.nabble.com/%27Recently-deployed%27-system-feed-source-tp25608313p25608313.html
Sent from the Nexus Maven Repository Manager Users List mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...
|
|
Re: 'Recently deployed' system feed source
Hi all,
Thanks for the quick replies. As you can imagine, I'm particularly interested in the 1.4 plugin framework. When it is scheduled to be released?
In the meantime, we will poll the feed.
Best regards,
Rob
|
|
Re: 'Recently deployed' system feed source
As I understand it, it's quite stable right now in the dev stream. There has been post about this earlier in this list. /Anders
|
|
Re: 'Recently deployed' system feed source
It's already in "eat your own dogfood" test drive mode. Checkout the version: http://repository.sonatype.org/On Tue, Sep 29, 2009 at 11:36 AM, Anders Hammar <anders@...> wrote:
As I understand it, it's quite stable right now in the dev stream. There has been post about this earlier in this list.
/Anders
|
|
Re: 'Recently deployed' system feed source
I did see that this morning when I tested a search issue. So, the release is just around the corner? :-) /A 2009/9/29 Tamás Cservenák <tamas@...>
It's already in "eat your own dogfood" test drive mode. Checkout the version:
http://repository.sonatype.org/On Tue, Sep 29, 2009 at 11:36 AM, Anders Hammar <anders@...> wrote:
As I understand it, it's quite stable right now in the dev stream. There has been post about this earlier in this list.
/Anders
|
|
Re: 'Recently deployed' system feed source
is knocking.... :)
This will be a true "Snow Nexus" release, not too much new on the surface... but under it...
~t~ On Tue, Sep 29, 2009 at 2:57 PM, Anders Hammar <anders@...> wrote:
I did see that this morning when I tested a search issue. So, the release is just around the corner? :-)
/A
2009/9/29 Tamás Cservenák <tamas@...>
It's already in "eat your own dogfood" test drive mode. Checkout the version:
http://repository.sonatype.org/On Tue, Sep 29, 2009 at 11:36 AM, Anders Hammar <anders@...> wrote:
As I understand it, it's quite stable right now in the dev stream. There has been post about this earlier in this list.
/Anders
|
|
Re: 'Recently deployed' system feed source
OK, sounds good. Will the release also include a plugin like mentioned in NEXUS-2615? What I need is a plugin that simply logs additions and deletions of artefacts in all repositories to a (XML, CSV, plaintext, whatever) file. Or should such a plugin be written after the release?
Tamás Cservenák wrote:
is knocking.... :)
This will be a true "Snow Nexus" release, not too much new on the surface...
but under it...
~t~
|
|
Re: 'Recently deployed' system feed source
You can already start writing plugins, since the core API (with plugin APIs inclusive) are already built and deployed to repository.sonatype.org.
Soon, we will publish a Maven Archetype for writing Nexus plugins, but this is kinda "can do after releases" problem (archetype needs 1.4 to be released, to generate valid POM). But the POM could be manually "downgraded" to 1.4-SNAPSHOT until 1.4 comes out.
The POM from archetype is here:
But is not up2date: plugin-api is released, version "1.0.1". nexus-api remains version "1.4.0-SNAPSHOT" until we release "1.4.0"
The "app-lifecycle-*" maven plugins needed to build nexus plugins are also released as "1.0".
~t~ On Tue, Sep 29, 2009 at 3:14 PM, Rob ten Hove <rob@...> wrote:
OK, sounds good. Will the release also include a plugin like mentioned in
NEXUS-2615? What I need is a plugin that simply logs additions and deletions
of artefacts in all repositories to a (XML, CSV, plaintext, whatever) file.
Or should such a plugin be written after the release?
Tamás Cservenák wrote:
>
> is knocking.... :)
> This will be a true "Snow Nexus" release, not too much new on the
> surface...
> but under it...
>
> ~t~
>
--
View this message in context: http://www.nabble.com/%27Recently-deployed%27-system-feed-source-tp25608313p25662836.html
Sent from the Nexus Maven Repository Manager Users List mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...
|
