Please use the Apache issue tracking system for new NetBeans issues (https://issues.apache.org/jira/projects/NETBEANS0/issues) !!

Bug 178308

Summary: Enable deployment of maven release and snapshot artifacts to http://bits.netbeans.org/maven2/
Product: www Reporter: cemerick <cemerick>
Component: AdminAssignee: Milos Kleint <mkleint>
Status: RESOLVED WORKSFORME QA Contact: Admins <izadmins>
Priority: P1 CC: anebuzelsky, jglick, kganfield, mkleint
Version: 6.x   
Target Milestone: 6.x   
Hardware: All   
OS: All   
Whiteboard:
Issue Type: DEFECT Exception Report:

Description cemerick 2009-12-08 10:13:09 UTC
It appears that whatever system(s) host http://bits.netbeans.org/maven2/ is so short on disk space that the maintainer of the NetBeans maven repository cannot deploy updated artifacts to it (quoting Milos.Kleint@Sun.COM) (I'd link to the post, but the NB dev list archive @ http://netbeans.org/projects/openide/lists/dev/archive is 500 right now):

>----------
for 6.7.1 I don't currently plan any uploads. only for 6.8. The reason is simple. I didn't get any assurance from NB Release engineering that they will not pull the plug on the repository when problems arise. The 6.5 and 6.7 releases occupy 1.5 GB (according to du -s, but it could be physically more as it's a lot of small files not sure) There is currently 3.4 GB free space left on the device. I would rather have a working incomplete repo, than one that doesn't work. Sad but reality.

Same goes for snapshots, but in a more extreme manner. the snapshots need to be numbered, if scheduled daily it's 300+ GB a year, if scheduled weekly it's significantly less but still. We would have to install Nexus on the machine and maintain it. That would allow is to get rid of older snapshots.. If widely used, we might get problems with bandwidth usage. If and when I don't know..
>----------

It's just good hygiene to deploy -- at the very least -- artifacts from all releases, but only NB 6.5 and 6.7 artifacts are available at the moment.  No 6.7.1, no 6.8 RC artifacts, and no nightly snapshots.  Not having the latter isn't a huge deal, but not being able to deploy release artifacts because of *disk space* is **crazy**.
Comment 1 Michal Zlamal 2009-12-08 12:02:36 UTC
I'm little bit puzzled what is the request for me.
There is 75GB of free disk space on this system (bits.netbeans.org), isn't it enough?
Comment 2 cemerick 2009-12-08 13:03:08 UTC
I'm entirely outside of the Sun/NetBeans organization, simply responding with a ticket (as requested) related to the apparent inability to deploy updated maven artifacts due to disk space constraints.

Milos?
Comment 3 fredjean 2009-12-08 14:01:24 UTC
(In reply to comment #0)
> It appears that whatever system(s) host http://bits.netbeans.org/maven2/ is so
> short on disk space that the maintainer of the NetBeans maven repository cannot
> deploy updated artifacts to it (quoting Milos.Kleint@Sun.COM) (I'd link to the
> post, but the NB dev list archive @
> http://netbeans.org/projects/openide/lists/dev/archive is 500 right now):
> 

The openide project on NetBeans.org doesn't have mailing lists. It is only used to store the (old?) HTML content. This certainly explain the error message. I should be able to point you in the right direction if you provide the mailing list that this message was sent to.

Fred
Comment 4 fredjean 2009-12-08 14:05:43 UTC
(In reply to comment #3)
> (In reply to comment #0)
> > It appears that whatever system(s) host http://bits.netbeans.org/maven2/ is so
> > short on disk space that the maintainer of the NetBeans maven repository cannot
> > deploy updated artifacts to it (quoting Milos.Kleint@Sun.COM) (I'd link to the
> > post, but the NB dev list archive @
> > http://netbeans.org/projects/openide/lists/dev/archive is 500 right now):
> > 
> 
> The openide project on NetBeans.org doesn't have mailing lists. It is only used
> to store the (old?) HTML content. This certainly explain the error message. I
> should be able to point you in the right direction if you provide the mailing
> list that this message was sent to.
> 
> Fred

The OpenIDE project was replaced by the Platform project in the recent NetBeans.org migration. I believe that you are looking for this archive: http://netbeans.org/projects/platform/lists/dev/archive and this message: http://netbeans.org/projects/platform/lists/dev/archive/2009-12/message/68

bits.netbeans.org isn't maintained by the Kenai team from what I can tell. 

Fred
Comment 5 cemerick 2009-12-08 14:10:01 UTC
(In reply to comment #4)
> 
> The OpenIDE project was replaced by the Platform project in the recent
> NetBeans.org migration. I believe that you are looking for this archive:
> http://netbeans.org/projects/platform/lists/dev/archive and this message:
> http://netbeans.org/projects/platform/lists/dev/archive/2009-12/message/68
> 
> bits.netbeans.org isn't maintained by the Kenai team from what I can tell. 
> 
> Fred

I was aware of the re-org, but didn't notice that the link on http://netbeans.org/community/lists/top.html had simply gone stale.
Comment 6 Milos Kleint 2009-12-09 03:48:50 UTC
well, if there *is* space great, however when I yesterday tried to figure out, I got this:
mkleint@us2-mirror:/space/releng/www$ du -s --si maven2/
1.4G    maven2/
mkleint@us2-mirror:/space/releng/www$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/hdv1             362G  340G  3.7G  99% /
/dev/hdb1             367G  349G     0 100% /space

I guess I misinterpreted the information and only looked at the Avail and Use fields. There is some quoting going on?

I made cemerick to file this issue as the current setup we have just doesn't scale for snapshots/milestones and I would like to start a discussion how to go forward especially with regard to 6.9 being the RCP+enterprise release.

Let me describe shortly what I currently do. I loosely follow the steps described here: http://mojo.codehaus.org/nbm-maven-plugin/repository.html
However deploying to bits.n.o from my local machine doesn't work. It's too slow. So I ZIP the existing repository content, download it to my local machine. unzip. deploy to the local file:// based repo then. Zip again and push to bits.n.o. Unzip there and the replace the existing repo with the new one with 2 "mv" commands. 
The reason for this setup is that maven not only uploads new files, but updates existing metadata as well. 
I tried to do the same on the bits.n.o server but there's just no java, no maven, nothing. Additionally if I mess something up, I would not only have to redeploy the current release, but reconstruct the whole repo (thus 2+ additional older releases)

if we are to provide snapshots the full process needs to become fully automated. Not only addition of new snapshots but also removal of old ones. And that is very hardly to do without a repository manager like Nexus. And that one would have to be installed and maintained on the server.
Comment 7 Milos Kleint 2010-01-04 06:28:26 UTC
6.8 binaries are deployed to bits.netbeans.org
Comment 8 Antonin Nebuzelsky 2010-07-30 15:15:49 UTC
Obsolete. Closing.
By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo