Re: [RELEASE]: source release script
Hi, I forgot yesterday to follow up on this a little bit. I did some further tests and have figured out that ant doesn't do a bad job here. I added targets for creating a zip, tar.gz and tar.bz2 and tested them independently. I did the same test native with zip and tar (on a MacOS system of course) on a directory aoo3.4 containing the relevant files (unzipped the ant created zip file ;-)) Time native: aoo-3.4.zip - 2min 5sec aoo-3.4.tar.gz - 4min 17sec aoo-3.4.tar.bz2 - 9min 20sec Time with ant: aoo-3.4.zip - 2min 46sec aoo-3.4.tar.gz - ~4min aoo-3.4.tar.bz2 - ~10min All 3 output files together with ant takes 14min 28sec The ant script creates one tar and used it for both zip files. Probably the time will be varying on the different platforms but the difference is not huge and I will continue with the ant approach. I have to do a little bit more minor things. File sizes by the way are: aoo-3.4.zip - ~382 MB aoo-3.4.tar.gz - ~330MB aoo-3.4.tar.bz2 - ~260MB I can probably add some signing targets to automate some more things... I have to read the docu for managing releases again. Juergen On 2/7/12 9:34 AM, Jürgen Schmidt wrote: On 2/6/12 7:22 PM, Rob Weir wrote: 2012/2/6 Jürgen Schmidtjogischm...@googlemail.com: Hi, I am currently work on a script to package a source release zip, tar.gz file. The idea is to do it later as part of our build bot builds and without copying files into a tmp directory or so to reflect the final directory structure. At the moment I am playing with an ant script that allows me to zip the necessary directories with an exclude list and to prefix everything with a configurable directory name (e.g aoo-3.4). And it allows me to copy some files like the main/NOTICE file into the new root directory. Is this able to ignore all the hidden .svn folders? yes The structure can look like aoo-3.4/NOTICE aoo-3.4/README aoo-3.4/LICNESE aoo-3.4/... aoo-3.4/main/... aoo-3.4/extras/... aoo-3.4/ext_libraries/... The nice thing with ant is that I can easy convert a generated zip file into a tar.gz file. But ok that takes some time where as creating the zip file was quite fast. Does anybody has a better idea how to do that without copying all the files in a final directory structure or checking out the files into a target directory for example aoo3.4. svn export will bring down the files without the .svn tracking folders. But that is still a separate download. I wonder if ant is jut calling java.io.zip stuff to do the archiving? If so, it might be a lot faster to call a native zip utility. I don't know but creating the zip file only was ok (2 minutes and 46 seconds). The conversion of the zip into tar.gz was incredible slow. It's no option. zipping the unpacked aoo-3.4 directory again takes ~2 minutes. But here we need have to export the sources again in the final directory or copy everything first into the final directory structure. I will do some further test creating tar.gz, tar.bz2 directly. If it's comparable with creating the zip I would say ant is fine for creating the src releases. We can simply add a further target for the build bots. Question: if we do ZIP on Windows, will it preserve the executable bits on files? If not, maybe we want to create the source package only from the Linux buildbot and never on the others. I have to check it, don't know for sure. But I would say that creating the src release on Linux should be enough. Juergen
Re: [RELEASE]: source release script
On 2/6/12 7:22 PM, Rob Weir wrote: 2012/2/6 Jürgen Schmidtjogischm...@googlemail.com: Hi, I am currently work on a script to package a source release zip, tar.gz file. The idea is to do it later as part of our build bot builds and without copying files into a tmp directory or so to reflect the final directory structure. At the moment I am playing with an ant script that allows me to zip the necessary directories with an exclude list and to prefix everything with a configurable directory name (e.g aoo-3.4). And it allows me to copy some files like the main/NOTICE file into the new root directory. Is this able to ignore all the hidden .svn folders? yes The structure can look like aoo-3.4/NOTICE aoo-3.4/README aoo-3.4/LICNESE aoo-3.4/... aoo-3.4/main/... aoo-3.4/extras/... aoo-3.4/ext_libraries/... The nice thing with ant is that I can easy convert a generated zip file into a tar.gz file. But ok that takes some time where as creating the zip file was quite fast. Does anybody has a better idea how to do that without copying all the files in a final directory structure or checking out the files into a target directory for example aoo3.4. svn export will bring down the files without the .svn tracking folders. But that is still a separate download. I wonder if ant is jut calling java.io.zip stuff to do the archiving? If so, it might be a lot faster to call a native zip utility. I don't know but creating the zip file only was ok (2 minutes and 46 seconds). The conversion of the zip into tar.gz was incredible slow. It's no option. zipping the unpacked aoo-3.4 directory again takes ~2 minutes. But here we need have to export the sources again in the final directory or copy everything first into the final directory structure. I will do some further test creating tar.gz, tar.bz2 directly. If it's comparable with creating the zip I would say ant is fine for creating the src releases. We can simply add a further target for the build bots. Question: if we do ZIP on Windows, will it preserve the executable bits on files? If not, maybe we want to create the source package only from the Linux buildbot and never on the others. I have to check it, don't know for sure. But I would say that creating the src release on Linux should be enough. Juergen
[RELEASE]: source release script
Hi, I am currently work on a script to package a source release zip, tar.gz file. The idea is to do it later as part of our build bot builds and without copying files into a tmp directory or so to reflect the final directory structure. At the moment I am playing with an ant script that allows me to zip the necessary directories with an exclude list and to prefix everything with a configurable directory name (e.g aoo-3.4). And it allows me to copy some files like the main/NOTICE file into the new root directory. The structure can look like aoo-3.4/NOTICE aoo-3.4/README aoo-3.4/LICNESE aoo-3.4/... aoo-3.4/main/... aoo-3.4/extras/... aoo-3.4/ext_libraries/... The nice thing with ant is that I can easy convert a generated zip file into a tar.gz file. But ok that takes some time where as creating the zip file was quite fast. Does anybody has a better idea how to do that without copying all the files in a final directory structure or checking out the files into a target directory for example aoo3.4. Juergen
Re: [RELEASE]: source release script
On 2/6/12 5:40 PM, Jürgen Schmidt wrote: Hi, I am currently work on a script to package a source release zip, tar.gz file. The idea is to do it later as part of our build bot builds and without copying files into a tmp directory or so to reflect the final directory structure. At the moment I am playing with an ant script that allows me to zip the necessary directories with an exclude list and to prefix everything with a configurable directory name (e.g aoo-3.4). And it allows me to copy some files like the main/NOTICE file into the new root directory. The structure can look like aoo-3.4/NOTICE aoo-3.4/README aoo-3.4/LICNESE aoo-3.4/... aoo-3.4/main/... aoo-3.4/extras/... aoo-3.4/ext_libraries/... The nice thing with ant is that I can easy convert a generated zip file into a tar.gz file. But ok that takes some time where as creating the zip file was quite fast. it seems to take very long :-( still running ... I did it in parallel via command line The file sizes are aoo-3.4.zip 380 MB aoo-3.4.tar.gz 334 MB aoo-3.4.tar.bz2 - 261 MB But the content is not final yet, ... Juergen Does anybody has a better idea how to do that without copying all the files in a final directory structure or checking out the files into a target directory for example aoo3.4. Juergen
Re: [RELEASE]: source release script
2012/2/6 Jürgen Schmidt jogischm...@googlemail.com: Hi, I am currently work on a script to package a source release zip, tar.gz file. The idea is to do it later as part of our build bot builds and without copying files into a tmp directory or so to reflect the final directory structure. At the moment I am playing with an ant script that allows me to zip the necessary directories with an exclude list and to prefix everything with a configurable directory name (e.g aoo-3.4). And it allows me to copy some files like the main/NOTICE file into the new root directory. Is this able to ignore all the hidden .svn folders? The structure can look like aoo-3.4/NOTICE aoo-3.4/README aoo-3.4/LICNESE aoo-3.4/... aoo-3.4/main/... aoo-3.4/extras/... aoo-3.4/ext_libraries/... The nice thing with ant is that I can easy convert a generated zip file into a tar.gz file. But ok that takes some time where as creating the zip file was quite fast. Does anybody has a better idea how to do that without copying all the files in a final directory structure or checking out the files into a target directory for example aoo3.4. svn export will bring down the files without the .svn tracking folders. But that is still a separate download. I wonder if ant is jut calling java.io.zip stuff to do the archiving? If so, it might be a lot faster to call a native zip utility. Question: if we do ZIP on Windows, will it preserve the executable bits on files? If not, maybe we want to create the source package only from the Linux buildbot and never on the others. Juergen
