|
Staging help
HI
all,
I'm stuck with
staging and need some help.
I have a deployment
user in maven that can deploy to the stage area.
I then want to have
a different user that can close promote the stage (but can not themselves deploy
to the stage - or direct to the repo). To do this I defined a new user
(lets call them bob)
I gave bob the
following roles:
Nexus Anonymous role,
UI Base UI Privileges [this should be in admin but without it they can not log
on?]
Staging: Deployer (Release Staging Profile)
Staging: Deployer (admin) [as a test - I only want to grant access to the
Release Staging Profile]
Repo: All repositories (read)
Repo: Release Repo (no redeploy) [as a test]
However when I log
into nexus ui as bob going to either "Staging Profiles" or "Staging
Repositories" results in a 401 error.
What
privileges/roles does a user need to be able to promote
stages?
Regards,
/James ************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **************************************************************************************
|
|
RE: Staging help
I'm stuck with
staging and need some help.
I have a
deployment user in maven that can deploy to the stage
area.
I then want to
have a different user that can close promote the stage (but can not themselves
deploy to the stage - or direct to the repo). To do this I defined a new
user (lets call them bob)
I gave bob the
following roles:
Nexus Anonymous role,
UI Base UI Privileges [this should be in admin but
without it they can not log on?]
That's a typo I mean anonymous
role...
Staging: Deployer (Release Staging Profile)
Staging: Deployer (admin) [as a test - I only want to grant access to
the Release Staging Profile]
Repo: All repositories (read)
Repo: Release Repo (no redeploy) [as a test]
However when I log
into nexus ui as bob going to either "Staging Profiles" or "Staging
Repositories" results in a 401 error.
What
privileges/roles does a user need to be able to promote
stages?
Regards,
/James ************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **************************************************************************************
|
|
Re: Staging help
James,
You should also give the user the UI: Staging Profiles (and/or UI: Staging Repositories; may not exist in version you are running) role. This should give access to the pages properly. The deployer role(s) auto created for each profile allow deployment, but not UI access themselves.
Damian
On Wed, Jul 1, 2009 at 6:52 AM, Nord, James <JNord@...> wrote:
I'm stuck with staging and need some help.
I have a deployment user in maven that can deploy to the stage area.
I then want to have a different user that can close promote the stage (but can not themselves deploy to the stage - or direct to the repo). To do this I defined a new user (lets call them bob)
I gave bob the following roles:
Nexus Anonymous role,
UI Base UI Privileges [this should be in admin but without it they can not log on?]
That's a typo I mean anonymous role...
Staging: Deployer (Release Staging Profile)
Staging: Deployer (admin) [as a test - I only want to grant access to the Release Staging Profile]
Repo: All repositories (read)
Repo: Release Repo (no redeploy) [as a test]
However when I log into nexus ui as bob going to either "Staging Profiles" or "Staging Repositories" results in a 401 error.
What privileges/roles does a user need to be able to promote stages?
Regards,
/James ************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **************************************************************************************
|
|
RE: Staging help
Hi Damian,
Something's still not quite right.
I added the UI: Staging Repositories role and the user can
now close the repo, but when they try to promote it returns a 401
un-authorised.
Strangely enough they have enough rights to be able to drop
the staged repo!
I tried adding the UI Staging profiles as well and they
still can not promote.
I'm using 1.3.1.1 - I had a quick scan of the change logs
and couldn't see anything related in 1.3.2 - 1.3.4.
I even added "Repo: All repositories (Full Control) to see
if it was the "no redeploy" role causing the issue but this made no
difference
below are the logs from nexus - which looks like it's doing
exactly what its reporting...
2009-07-01 15:17:45 ERROR
[qtp0-4728 ] - o.s.p.r.r.PlexusRes~:Staging~ -
Illegal access of staging
profile
org.sonatype.nexus.proxy.AccessDeniedException: Illegal access of
staging profile
at
com.sonatype.nexus.staging.DefaultStagingManager.checkPermission(Unknown
Source)
at
com.sonatype.nexus.staging.DefaultStagingManager.promoteStagingRepository(Unknown
Source)
at
com.sonatype.nexus.staging.api.StagingWPromotePlexusResource.post(Unknown
Source)
at
org.sonatype.plexus.rest.resource.RestletResource.acceptRepresentation(RestletResource.java:264)
at
org.restlet.resource.Resource.post(Resource.java:688)
at
org.restlet.resource.Resource.handlePost(Resource.java:537)
at
org.restlet.Finder.handle(Finder.java:357)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Router.handle(Router.java:504)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Router.handle(Router.java:504)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.sonatype.plexus.rest.RetargetableRestlet.doHandle(RetargetableRestlet.java:39)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
com.noelios.restlet.StatusFilter.doHandle(StatusFilter.java:130)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
com.noelios.restlet.ChainHelper.handle(ChainHelper.java:124)
at
com.noelios.restlet.application.ApplicationHelper.handle(ApplicationHelper.java:112)
at
org.restlet.Application.handle(Application.java:341)
at
org.restlet.ext.wadl.WadlApplication.handle(WadlApplication.java:705)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Router.handle(Router.java:504)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Router.handle(Router.java:504)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
com.noelios.restlet.ChainHelper.handle(ChainHelper.java:124)
at
org.restlet.Component.handle(Component.java:673)
at
org.restlet.Server.handle(Server.java:331)
at
com.noelios.restlet.ServerHelper.handle(ServerHelper.java:68)
at
com.noelios.restlet.http.HttpServerHelper.handle(HttpServerHelper.java:147)
at
com.noelios.restlet.ext.servlet.ServerServlet.service(ServerServlet.java:884)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1124)
at
org.jsecurity.web.servlet.FilterChainWrapper.doFilter(FilterChainWrapper.java:52)
at
org.jsecurity.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:105)
at
org.jsecurity.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:135)
at
org.jsecurity.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:180)
at
org.jsecurity.web.servlet.FilterChainWrapper.doFilter(FilterChainWrapper.java:57)
at
org.jsecurity.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:105)
at
org.jsecurity.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:135)
at
org.jsecurity.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:180)
at
org.jsecurity.web.servlet.FilterChainWrapper.doFilter(FilterChainWrapper.java:57)
at
org.jsecurity.web.servlet.JSecurityFilter.doFilterInternal(JSecurityFilter.java:382)
at
org.sonatype.nexus.security.filter.NexusJSecurityFilter.doFilterInternal(NexusJSecurityFilter.java:76)
at
org.jsecurity.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:180)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:361)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at
org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at
org.mortbay.jetty.Server.handle(Server.java:324)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
at
org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:741)
at
org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
at
org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
2009-07-01
15:22:24 INFO [qtp0-4732 ] -
o.s.n.p.r.Repositor~:default - Removed repository
ID='release-staging-profile-005' (contentClass='maven2',
mainFacet='org.sonatype.nexus.proxy.maven.MavenHostedRepository')
2009-07-01
15:22:24 INFO [qtp0-4732 ] -
o.s.n.c.a.NexusConf~:default - Applying Nexus
Configuration...
2009-07-01 15:22:24 INFO
[qtp0-4732 ] -
o.s.n.t.Timeline:default - Stopping
Timeline...
2009-07-01 15:22:24 INFO
[qtp0-4732 ] -
o.s.n.t.Timeline:default - Starting
Timeline...
2009-07-01 15:22:24 INFO
[qtp0-4732 ] -
c.s.n.s.StagingMana~:default - Staged repository from Profile
ID='40365b31e0dc2b', repository ID='release-staging-profile-005' is being
dropped.
2009-07-01 15:22:24 INFO [ool-1-thread-10] -
o.s.n.f.FeedRecorder:default - Removing folder with repository ID:
release-staging-profile-005 : Process started on Wed Jul 01 15:22:24 BST 2009,
not yet finished.
2009-07-01 15:22:24 INFO [ool-1-thread-10] -
o.s.n.Nexus:default
- Removing storage folder of repository
release-staging-profile-005
/James
James,
You should also give the user the UI: Staging Profiles (and/or UI:
Staging Repositories; may not exist in version you are running) role.
This should give access to the pages properly. The deployer role(s) auto
created for each profile allow deployment, but not UI access themselves.
Damian
On Wed, Jul 1, 2009 at 6:52 AM, Nord, James <JNord@...>
wrote:
I'm stuck with staging and need some
help.
I have a deployment user in maven that
can deploy to the stage area.
I then want to have a different user
that can close promote the stage (but can not themselves deploy to the
stage - or direct to the repo). To do this I defined a new user
(lets call them bob)
I gave bob the following roles:
Nexus Anonymous
role,
UI Base UI
Privileges [this should be in admin but without it they can not log
on?]
That's a typo I mean anonymous
role...
Staging: Deployer
(Release Staging Profile)
Staging: Deployer
(admin) [as a test - I only want to grant access to the Release Staging
Profile]
Repo: All
repositories (read)
Repo: Release Repo
(no redeploy) [as a test]
However when I log into nexus ui as
bob going to either "Staging Profiles" or "Staging Repositories"
results in a 401 error.
What privileges/roles does a user need
to be able to promote stages?
Regards,
/James ************************************************************************************** This
message is confidential and intended only for the addressee. If you have
received this message in error, please immediately notify the postmaster@... and
delete it from your system as well as any copies. The content of e-mails as
well as traffic data may be monitored by NDS for employment and security
purposes. To protect the environment please do not print this e-mail unless
necessary. NDS Limited. Registered Office: One London Road, Staines,
Middlesex, TW18 4EX, United Kingdom. A company registered in England and
Wales. Registered no. 3080780. VAT no. GB 603 8808
40-00 **************************************************************************************
************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **************************************************************************************
|
|
Re: Staging help
James, sorry, i just gave you role so that you could view the page :)
To enable promote for a user, you will need to add the 'Staging Profile ${profile-name} - promote' privilege to a role your user contains. We purposefully kept promotion out of the staging deployer roles because of the fact that you don't typically want every deployer to be able to promote releases
Damian
On Wed, Jul 1, 2009 at 10:32 AM, Nord, James <JNord@...> wrote:
Hi Damian,
Something's still not quite right.
I added the UI: Staging Repositories role and the user can now close the repo, but when they try to promote it returns a 401 un-authorised.
Strangely enough they have enough rights to be able to drop the staged repo!
I tried adding the UI Staging profiles as well and they still can not promote.
I'm using 1.3.1.1 - I had a quick scan of the change logs and couldn't see anything related in 1.3.2 - 1.3.4.
I even added "Repo: All repositories (Full Control) to see if it was the "no redeploy" role causing the issue but this made no difference
below are the logs from nexus - which looks like it's doing exactly what its reporting...
2009-07-01 15:17:45 ERROR [qtp0-4728 ] - o.s.p.r.r.PlexusRes~:Staging~ - Illegal access of staging profile
org.sonatype.nexus.proxy.AccessDeniedException: Illegal access of staging profile
at com.sonatype.nexus.staging.DefaultStagingManager.checkPermission(Unknown Source)
at com.sonatype.nexus.staging.DefaultStagingManager.promoteStagingRepository(Unknown Source)
at com.sonatype.nexus.staging.api.StagingWPromotePlexusResource.post(Unknown Source)
at org.sonatype.plexus.rest.resource.RestletResource.acceptRepresentation(RestletResource.java:264)
at org.restlet.resource.Resource.post(Resource.java:688)
at org.restlet.resource.Resource.handlePost(Resource.java:537)
at org.restlet.Finder.handle(Finder.java:357)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Router.handle(Router.java:504)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Router.handle(Router.java:504)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.sonatype.plexus.rest.RetargetableRestlet.doHandle(RetargetableRestlet.java:39)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Filter.doHandle(Filter.java:150)
at com.noelios.restlet.StatusFilter.doHandle(StatusFilter.java:130)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at com.noelios.restlet.ChainHelper.handle(ChainHelper.java:124)
at com.noelios.restlet.application.ApplicationHelper.handle(ApplicationHelper.java:112)
at org.restlet.Application.handle(Application.java:341)
at org.restlet.ext.wadl.WadlApplication.handle(WadlApplication.java:705)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Router.handle(Router.java:504)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Router.handle(Router.java:504)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at com.noelios.restlet.ChainHelper.handle(ChainHelper.java:124)
at org.restlet.Component.handle(Component.java:673)
at org.restlet.Server.handle(Server.java:331)
at com.noelios.restlet.ServerHelper.handle(ServerHelper.java:68)
at com.noelios.restlet.http.HttpServerHelper.handle(HttpServerHelper.java:147)
at com.noelios.restlet.ext.servlet.ServerServlet.service(ServerServlet.java:884)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1124)
at org.jsecurity.web.servlet.FilterChainWrapper.doFilter(FilterChainWrapper.java:52)
at org.jsecurity.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:105)
at org.jsecurity.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:135)
at org.jsecurity.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:180)
at org.jsecurity.web.servlet.FilterChainWrapper.doFilter(FilterChainWrapper.java:57)
at org.jsecurity.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:105)
at org.jsecurity.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:135)
at org.jsecurity.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:180)
at org.jsecurity.web.servlet.FilterChainWrapper.doFilter(FilterChainWrapper.java:57)
at org.jsecurity.web.servlet.JSecurityFilter.doFilterInternal(JSecurityFilter.java:382)
at org.sonatype.nexus.security.filter.NexusJSecurityFilter.doFilterInternal(NexusJSecurityFilter.java:76)
at org.jsecurity.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:180)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:361)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:741)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
2009-07-01 15:22:24 INFO [qtp0-4732 ] - o.s.n.p.r.Repositor~:default - Removed repository ID='release-staging-profile-005' (contentClass='maven2', mainFacet='org.sonatype.nexus.proxy.maven.MavenHostedRepository')
2009-07-01 15:22:24 INFO [qtp0-4732 ] - o.s.n.c.a.NexusConf~:default - Applying Nexus Configuration...
2009-07-01 15:22:24 INFO [qtp0-4732 ] - o.s.n.t.Timeline:default - Stopping Timeline...
2009-07-01 15:22:24 INFO [qtp0-4732 ] - o.s.n.t.Timeline:default - Starting Timeline...
2009-07-01 15:22:24 INFO [qtp0-4732 ] - c.s.n.s.StagingMana~:default - Staged repository from Profile ID='40365b31e0dc2b', repository ID='release-staging-profile-005' is being dropped.
2009-07-01 15:22:24 INFO [ool-1-thread-10] - o.s.n.f.FeedRecorder:default - Removing folder with repository ID: release-staging-profile-005 : Process started on Wed Jul 01 15:22:24 BST 2009, not yet finished.
2009-07-01 15:22:24 INFO [ool-1-thread-10] - o.s.n.Nexus:default - Removing storage folder of repository release-staging-profile-005
/James
James,
You should also give the user the UI: Staging Profiles (and/or UI: Staging Repositories; may not exist in version you are running) role. This should give access to the pages properly. The deployer role(s) auto created for each profile allow deployment, but not UI access themselves.
Damian
On Wed, Jul 1, 2009 at 6:52 AM, Nord, James <JNord@...> wrote:
I'm stuck with staging and need some help.
I have a deployment user in maven that can deploy to the stage area.
I then want to have a different user that can close promote the stage (but can not themselves deploy to the stage - or direct to the repo). To do this I defined a new user (lets call them bob)
I gave bob the following roles:
Nexus Anonymous role,
UI Base UI Privileges [this should be in admin but without it they can not log on?]
That's a typo I mean anonymous role...
Staging: Deployer (Release Staging Profile)
Staging: Deployer (admin) [as a test - I only want to grant access to the Release Staging Profile]
Repo: All repositories (read)
Repo: Release Repo (no redeploy) [as a test]
However when I log into nexus ui as bob going to either "Staging Profiles" or "Staging Repositories" results in a 401 error.
What privileges/roles does a user need to be able to promote stages?
Regards,
/James ************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **************************************************************************************
************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **************************************************************************************
|
|
RE: Staging help
Ah right, that nailed it.. now to the follow on question
:-0
I previously had the release repo setup automatically
prevent re-deployment of artifacts. But it now looks like the staging has
completely bypassed this - as it does the deployment behind the
scenes.
How can I prevent someone re-publishing an artifact via a
staged repo?
/James
James, sorry, i just gave you role so that you could view the page
:)
To enable promote for a user, you will need to add the 'Staging Profile
${profile-name} - promote' privilege to a role your user contains. We
purposefully kept promotion out of the staging deployer roles because of the
fact that you don't typically want every deployer to be able to promote
releases
Damian
On Wed, Jul 1, 2009 at 10:32 AM, Nord, James <JNord@...>
wrote:
Hi
Damian,
Something's still not quite right.
I added
the UI: Staging Repositories role and the user can now close the repo, but
when they try to promote it returns a 401 un-authorised.
Strangely enough they have enough rights to be able to drop the
staged repo!
I tried
adding the UI Staging profiles as well and they still can not
promote.
I'm
using 1.3.1.1 - I had a quick scan of the change logs and couldn't see
anything related in 1.3.2 - 1.3.4.
I even added "Repo: All
repositories (Full Control) to see if it was the "no redeploy" role causing
the issue but this made no difference
below
are the logs from nexus - which looks like it's doing exactly what its
reporting...
2009-07-01 15:17:45 ERROR [qtp0-4728
] - o.s.p.r.r.PlexusRes~:Staging~ - Illegal access of staging
profile
org.sonatype.nexus.proxy.AccessDeniedException: Illegal access
of staging profile
at
com.sonatype.nexus.staging.DefaultStagingManager.checkPermission(Unknown
Source)
at
com.sonatype.nexus.staging.DefaultStagingManager.promoteStagingRepository(Unknown
Source)
at
com.sonatype.nexus.staging.api.StagingWPromotePlexusResource.post(Unknown
Source)
at
org.sonatype.plexus.rest.resource.RestletResource.acceptRepresentation(RestletResource.java:264)
at
org.restlet.resource.Resource.post(Resource.java:688)
at
org.restlet.resource.Resource.handlePost(Resource.java:537)
at
org.restlet.Finder.handle(Finder.java:357)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Router.handle(Router.java:504)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Router.handle(Router.java:504)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.sonatype.plexus.rest.RetargetableRestlet.doHandle(RetargetableRestlet.java:39)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
com.noelios.restlet.StatusFilter.doHandle(StatusFilter.java:130)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
com.noelios.restlet.ChainHelper.handle(ChainHelper.java:124)
at
com.noelios.restlet.application.ApplicationHelper.handle(ApplicationHelper.java:112)
at
org.restlet.Application.handle(Application.java:341)
at
org.restlet.ext.wadl.WadlApplication.handle(WadlApplication.java:705)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Router.handle(Router.java:504)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
org.restlet.Router.handle(Router.java:504)
at
org.restlet.Filter.doHandle(Filter.java:150)
at
org.restlet.Filter.handle(Filter.java:195)
at
com.noelios.restlet.ChainHelper.handle(ChainHelper.java:124)
at
org.restlet.Component.handle(Component.java:673)
at
org.restlet.Server.handle(Server.java:331)
at
com.noelios.restlet.ServerHelper.handle(ServerHelper.java:68)
at
com.noelios.restlet.http.HttpServerHelper.handle(HttpServerHelper.java:147)
at
com.noelios.restlet.ext.servlet.ServerServlet.service(ServerServlet.java:884)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1124)
at
org.jsecurity.web.servlet.FilterChainWrapper.doFilter(FilterChainWrapper.java:52)
at
org.jsecurity.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:105)
at
org.jsecurity.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:135)
at
org.jsecurity.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:180)
at
org.jsecurity.web.servlet.FilterChainWrapper.doFilter(FilterChainWrapper.java:57)
at
org.jsecurity.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:105)
at
org.jsecurity.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:135)
at
org.jsecurity.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:180)
at
org.jsecurity.web.servlet.FilterChainWrapper.doFilter(FilterChainWrapper.java:57)
at
org.jsecurity.web.servlet.JSecurityFilter.doFilterInternal(JSecurityFilter.java:382)
at
org.sonatype.nexus.security.filter.NexusJSecurityFilter.doFilterInternal(NexusJSecurityFilter.java:76)
at
org.jsecurity.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:180)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:361)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at
org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at
org.mortbay.jetty.Server.handle(Server.java:324)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
at
org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:741)
at
org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
at
org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
2009-07-01
15:22:24 INFO [qtp0-4732 ] -
o.s.n.p.r.Repositor~:default - Removed repository
ID='release-staging-profile-005' (contentClass='maven2',
mainFacet='org.sonatype.nexus.proxy.maven.MavenHostedRepository')
2009-07-01
15:22:24 INFO [qtp0-4732 ] -
o.s.n.c.a.NexusConf~:default - Applying Nexus
Configuration...
2009-07-01 15:22:24 INFO
[qtp0-4732 ] -
o.s.n.t.Timeline:default - Stopping
Timeline...
2009-07-01 15:22:24 INFO
[qtp0-4732 ] -
o.s.n.t.Timeline:default - Starting
Timeline...
2009-07-01 15:22:24 INFO
[qtp0-4732 ] -
c.s.n.s.StagingMana~:default - Staged repository from Profile
ID='40365b31e0dc2b', repository ID='release-staging-profile-005' is being
dropped.
2009-07-01 15:22:24 INFO [ool-1-thread-10] -
o.s.n.f.FeedRecorder:default - Removing folder with repository ID:
release-staging-profile-005 : Process started on Wed Jul 01 15:22:24 BST
2009, not yet finished.
2009-07-01 15:22:24 INFO
[ool-1-thread-10] -
o.s.n.Nexus:default
- Removing storage folder of repository
release-staging-profile-005
/James
James,
You should also give the user the UI: Staging Profiles (and/or UI:
Staging Repositories; may not exist in version you are running)
role. This should give access to the pages properly. The
deployer role(s) auto created for each profile allow deployment, but not
UI access themselves.
Damian
On Wed, Jul 1, 2009 at 6:52 AM, Nord, James <JNord@...> wrote:
I'm stuck with staging and need
some help.
I have a deployment user in maven
that can deploy to the stage area.
I then want to have a different
user that can close promote the stage (but can not themselves deploy
to the stage - or direct to the repo). To do this I defined a
new user (lets call them bob)
I gave bob the following roles:
Nexus Anonymous
role,
UI Base UI
Privileges [this should be in admin but without it they can not log
on?]
That's a typo I mean
anonymous role...
Staging:
Deployer (Release Staging Profile)
Staging:
Deployer (admin) [as a test - I only want to grant access to the
Release Staging Profile]
Repo: All
repositories (read)
Repo: Release
Repo (no redeploy) [as a test]
However when I log into nexus ui as
bob going to either "Staging Profiles" or "Staging Repositories"
results in a 401 error.
What privileges/roles does a user
need to be able to promote stages?
Regards,
/James ************************************************************************************** This
message is confidential and intended only for the addressee. If you have
received this message in error, please immediately notify the postmaster@...
and delete it from your system as well as any copies. The content of
e-mails as well as traffic data may be monitored by NDS for employment
and security purposes. To protect the environment please do not print
this e-mail unless necessary. NDS Limited. Registered Office: One
London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company
registered in England and Wales. Registered no. 3080780. VAT no. GB 603
8808
40-00 **************************************************************************************
************************************************************************************** This
message is confidential and intended only for the addressee. If you have
received this message in error, please immediately notify the postmaster@... and
delete it from your system as well as any copies. The content of e-mails as
well as traffic data may be monitored by NDS for employment and security
purposes. To protect the environment please do not print this e-mail unless
necessary. NDS Limited. Registered Office: One London Road, Staines,
Middlesex, TW18 4EX, United Kingdom. A company registered in England and
Wales. Registered no. 3080780. VAT no. GB 603 8808
40-00 **************************************************************************************
************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **************************************************************************************
|
|
Re: Staging help
Unfortunately, you currently can't. The promotion runs as a task in a seperate context outside of the rest request to promote the repo (as it can take a period of time for it to complete). Because of this, the task has no notion of current user, so is treated effectively as admin and can do anything (you'll also notice that you can promote to any repository, regardless of permissions).
We are currently working on resolution to this, and are hoping to have fixed in 1.4 release.
Damian
On Wed, Jul 1, 2009 at 10:54 AM, Nord, James <JNord@...> wrote:
Ah right, that nailed it.. now to the follow on question :-0
I previously had the release repo setup automatically prevent re-deployment of artifacts. But it now looks like the staging has completely bypassed this - as it does the deployment behind the scenes.
How can I prevent someone re-publishing an artifact via a staged repo?
/James
James, sorry, i just gave you role so that you could view the page :)
To enable promote for a user, you will need to add the 'Staging Profile ${profile-name} - promote' privilege to a role your user contains. We purposefully kept promotion out of the staging deployer roles because of the fact that you don't typically want every deployer to be able to promote releases
Damian
On Wed, Jul 1, 2009 at 10:32 AM, Nord, James <JNord@...> wrote:
Hi Damian,
Something's still not quite right.
I added the UI: Staging Repositories role and the user can now close the repo, but when they try to promote it returns a 401 un-authorised.
Strangely enough they have enough rights to be able to drop the staged repo!
I tried adding the UI Staging profiles as well and they still can not promote.
I'm using 1.3.1.1 - I had a quick scan of the change logs and couldn't see anything related in 1.3.2 - 1.3.4.
I even added "Repo: All repositories (Full Control) to see if it was the "no redeploy" role causing the issue but this made no difference
below are the logs from nexus - which looks like it's doing exactly what its reporting...
2009-07-01 15:17:45 ERROR [qtp0-4728 ] - o.s.p.r.r.PlexusRes~:Staging~ - Illegal access of staging profile
org.sonatype.nexus.proxy.AccessDeniedException: Illegal access of staging profile
at com.sonatype.nexus.staging.DefaultStagingManager.checkPermission(Unknown Source)
at com.sonatype.nexus.staging.DefaultStagingManager.promoteStagingRepository(Unknown Source)
at com.sonatype.nexus.staging.api.StagingWPromotePlexusResource.post(Unknown Source)
at org.sonatype.plexus.rest.resource.RestletResource.acceptRepresentation(RestletResource.java:264)
at org.restlet.resource.Resource.post(Resource.java:688)
at org.restlet.resource.Resource.handlePost(Resource.java:537)
at org.restlet.Finder.handle(Finder.java:357)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Router.handle(Router.java:504)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Router.handle(Router.java:504)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.sonatype.plexus.rest.RetargetableRestlet.doHandle(RetargetableRestlet.java:39)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Filter.doHandle(Filter.java:150)
at com.noelios.restlet.StatusFilter.doHandle(StatusFilter.java:130)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at com.noelios.restlet.ChainHelper.handle(ChainHelper.java:124)
at com.noelios.restlet.application.ApplicationHelper.handle(ApplicationHelper.java:112)
at org.restlet.Application.handle(Application.java:341)
at org.restlet.ext.wadl.WadlApplication.handle(WadlApplication.java:705)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Router.handle(Router.java:504)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Router.handle(Router.java:504)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at com.noelios.restlet.ChainHelper.handle(ChainHelper.java:124)
at org.restlet.Component.handle(Component.java:673)
at org.restlet.Server.handle(Server.java:331)
at com.noelios.restlet.ServerHelper.handle(ServerHelper.java:68)
at com.noelios.restlet.http.HttpServerHelper.handle(HttpServerHelper.java:147)
at com.noelios.restlet.ext.servlet.ServerServlet.service(ServerServlet.java:884)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1124)
at org.jsecurity.web.servlet.FilterChainWrapper.doFilter(FilterChainWrapper.java:52)
at org.jsecurity.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:105)
at org.jsecurity.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:135)
at org.jsecurity.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:180)
at org.jsecurity.web.servlet.FilterChainWrapper.doFilter(FilterChainWrapper.java:57)
at org.jsecurity.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:105)
at org.jsecurity.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:135)
at org.jsecurity.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:180)
at org.jsecurity.web.servlet.FilterChainWrapper.doFilter(FilterChainWrapper.java:57)
at org.jsecurity.web.servlet.JSecurityFilter.doFilterInternal(JSecurityFilter.java:382)
at org.sonatype.nexus.security.filter.NexusJSecurityFilter.doFilterInternal(NexusJSecurityFilter.java:76)
at org.jsecurity.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:180)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:361)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:741)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
2009-07-01 15:22:24 INFO [qtp0-4732 ] - o.s.n.p.r.Repositor~:default - Removed repository ID='release-staging-profile-005' (contentClass='maven2', mainFacet='org.sonatype.nexus.proxy.maven.MavenHostedRepository')
2009-07-01 15:22:24 INFO [qtp0-4732 ] - o.s.n.c.a.NexusConf~:default - Applying Nexus Configuration...
2009-07-01 15:22:24 INFO [qtp0-4732 ] - o.s.n.t.Timeline:default - Stopping Timeline...
2009-07-01 15:22:24 INFO [qtp0-4732 ] - o.s.n.t.Timeline:default - Starting Timeline...
2009-07-01 15:22:24 INFO [qtp0-4732 ] - c.s.n.s.StagingMana~:default - Staged repository from Profile ID='40365b31e0dc2b', repository ID='release-staging-profile-005' is being dropped.
2009-07-01 15:22:24 INFO [ool-1-thread-10] - o.s.n.f.FeedRecorder:default - Removing folder with repository ID: release-staging-profile-005 : Process started on Wed Jul 01 15:22:24 BST 2009, not yet finished.
2009-07-01 15:22:24 INFO [ool-1-thread-10] - o.s.n.Nexus:default - Removing storage folder of repository release-staging-profile-005
/James
James,
You should also give the user the UI: Staging Profiles (and/or UI: Staging Repositories; may not exist in version you are running) role. This should give access to the pages properly. The deployer role(s) auto created for each profile allow deployment, but not UI access themselves.
Damian
On Wed, Jul 1, 2009 at 6:52 AM, Nord, James <JNord@...> wrote:
I'm stuck with staging and need some help.
I have a deployment user in maven that can deploy to the stage area.
I then want to have a different user that can close promote the stage (but can not themselves deploy to the stage - or direct to the repo). To do this I defined a new user (lets call them bob)
I gave bob the following roles:
Nexus Anonymous role,
UI Base UI Privileges [this should be in admin but without it they can not log on?]
That's a typo I mean anonymous role...
Staging: Deployer (Release Staging Profile)
Staging: Deployer (admin) [as a test - I only want to grant access to the Release Staging Profile]
Repo: All repositories (read)
Repo: Release Repo (no redeploy) [as a test]
However when I log into nexus ui as bob going to either "Staging Profiles" or "Staging Repositories" results in a 401 error.
What privileges/roles does a user need to be able to promote stages?
Regards,
/James ************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **************************************************************************************
************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **************************************************************************************
************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **************************************************************************************
|
|
Re: Staging help
We are currently working on resolution to this, and are hoping to have fixed in 1.4 release.
Not hope...will ;-)
|
|
RE: Staging help
We are currently working on resolution to this, and are hoping to have
fixed in 1.4 release.
Not hope...will ;-)
I know you try for 3 monthly release cycles - which would make 1.4
released erm earlier last month ;-)
And the obvious answer to my next question is "when it's ready!"
but are close or are we weeks away for the best ever release of
Nexus?
I'd like to be able to work out if I should prevent corruption of my repo
or go for the release process from the outset. The shorter the window for
someone to corrupt stuff the more likely I am to roll the process
out.
/James ************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **************************************************************************************
|
|
Re: Staging help
1.3.5 is up next week, 1.4 is still 3-4 weeks out. On Wed, Jul 1, 2009 at 1:04 PM, Nord, James <JNord@...> wrote:
We are currently working on resolution to this, and are hoping to have
fixed in 1.4 release.
Not hope...will ;-)
I know you try for 3 monthly release cycles - which would make 1.4
released erm earlier last month ;-)
And the obvious answer to my next question is "when it's ready!"
but are close or are we weeks away for the best ever release of
Nexus?
I'd like to be able to work out if I should prevent corruption of my repo
or go for the release process from the outset. The shorter the window for
someone to corrupt stuff the more likely I am to roll the process
out.
/James ************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **************************************************************************************
|
