From: Jarek C. <jar...@po...> - 2012-06-15 08:17:52
|
Hi Eric I know you once told me something about the daily builds machine, but could you know collect the details together: 1. Are your scripts uploaded to jedit so that we could copy them and reproduce the machine? 2. What are hosting requirements to setup the environment? I mean is Tomcat, Glassfish or something like that necessary? Thanks Jarek |
From: Eric B. <el...@gm...> - 2012-06-15 17:25:56
|
There isn't much to tell really. Most of it is set up through Hudson's (now Jenkins) UI. I'll do my best to give a brief summary of what is needed, and to answer your questions: 1. There really aren't any "scripts" to speak off, there's one Groovy script I wrote to help copy build properties from the Jenkins UI to a build.properties file. That script is checked in to SVN under build-support/ci. 2. There are currently two hosting environments, the first is the machine that runs Jenkins, and the second is the hosting environment that hosts the final artifacts. The Jenkins machine is my Mac laptop, and the file host is my hosting environment for tellurianring.com. Jenkins just uses FTP to upload the files to the server. Jenkins provides an executable war file which runs an embedded Winstone server. I just use that, although it can easily be run Jetty, Tomcat, Glassfish, Resin, or any other J2EE Servlet Container. Besides the regular requirements for building jEdit from source, I've installed wine (through macports) so that the windows installer can be built, and Groovy which I use as a scripting language to run the copy_properties.groovy script found in SVN. The windows installer requires that you have a utility installed, but instructions for that can be found in jEdit's own release documentation. All the other installers are built easy enough without having to install anything else (you may need to install x-code tools, but most developers will need to do that anyway), with the exception of the debian installer which can be built, but requires that Vampire sign it. The largest part of setting up the environment is just creating and setting up the jobs in Jenkins itself. Unfortunately some build.properties require an absolute paths which means that each Jenkins Job does need to have some manual configuration. Luckily Jenkins keeps all configuration in files that can easily be copied from one machine to another (as has been the case when I've upgraded machines). If someone would like the environment I could provide a tar.gz file with all the jobs and settings. All that would be required is it be dropped in there ~/.hudson directory and voila you have yourself a complete copy of the jEdit daily build environment. Actually, is there anyone one here who would like to take over the daily-builds? You would need to get a new file host for the build artifacts since it's currently using my personal hosting environment, but I could help anyone who's interested to get their environment set up. On Fri, Jun 15, 2012 at 1:17 AM, Jarek Czekalski <jar...@po...>wrote: > Hi Eric > > I know you once told me something about the daily builds machine, but > could you know collect the details together: > > 1. Are your scripts uploaded to jedit so that we could copy them and > reproduce the machine? > 2. What are hosting requirements to setup the environment? I mean is > Tomcat, Glassfish or something like that necessary? > > Thanks > Jarek > -- Learn from the past. Live in the present. Plan for the future. Blog: http://eric-berry.blogspot.com jEdit <http://www.jedit.org> - Programmer's Text Editor Bazaar <http://bazaar.canonical.com> - Version Control for Humans |
From: Alan E. <ala...@gm...> - 2012-06-15 18:49:55
|
On Fri, Jun 15, 2012 at 10:25 AM, Eric Berry <el...@gm...> wrote: > > Actually, is there anyone one here who would like to take over the > daily-builds? You would need to get a new file host for the build artifacts > since it's currently using my personal hosting environment, but I could help > anyone who's interested to get their environment set up. Is there a technical reason daily builds can not be hosted on sf.net itself? |
From: Eric B. <el...@gm...> - 2012-06-15 19:01:33
|
I'm assuming you mean as a file host.. There was at one point - I couldn't get Jenkins to do SFTP, I'll have to check again to see if it can be done now. The other issue was perhaps a mistaken assumption on my part, but I didn't see a lot of projects hosting daily build artifacts in sf.net so thought that there may be some SF.net restriction on having that many files hosted for each project. As I say, perhaps this is a bad assumption on my part, and to be honest, I don't remember doing a ton of research into it since the Jenkins plugin didn't support SFTP at the time. On Fri, Jun 15, 2012 at 11:49 AM, Alan Ezust <ala...@gm...> wrote: > On Fri, Jun 15, 2012 at 10:25 AM, Eric Berry <el...@gm...> wrote: > > > > Actually, is there anyone one here who would like to take over the > > daily-builds? You would need to get a new file host for the build > artifacts > > since it's currently using my personal hosting environment, but I could > help > > anyone who's interested to get their environment set up. > > Is there a technical reason daily builds can not be hosted on sf.netitself? > -- Learn from the past. Live in the present. Plan for the future. Blog: http://eric-berry.blogspot.com jEdit <http://www.jedit.org> - Programmer's Text Editor Bazaar <http://bazaar.canonical.com> - Version Control for Humans |
From: Vampire <Vampire@jEdit.org> - 2012-06-16 23:30:25
|
Hosting a build server server itself is actually not possible on SF resources, as you cannot run anything that is not a CGI script understood by the Apache installation on SF. Hosting daily build files on SF is not allowed by SF. At least it was not when I last checked. They only want real releases being hosted on their file services and tell to host daily/nightly builds on some external service. Eric Berry schrieb: > I'm assuming you mean as a file host.. There was at one point - I couldn't > get Jenkins to do SFTP, I'll have to check again to see if it can be done > now. The other issue was perhaps a mistaken assumption on my part, but I > didn't see a lot of projects hosting daily build artifacts in sf.net so > thought that there may be some SF.net restriction on having that many files > hosted for each project. As I say, perhaps this is a bad assumption on my > part, and to be honest, I don't remember doing a ton of research into it > since the Jenkins plugin didn't support SFTP at the time. > > On Fri, Jun 15, 2012 at 11:49 AM, Alan Ezust <ala...@gm...> wrote: > > >> On Fri, Jun 15, 2012 at 10:25 AM, Eric Berry <el...@gm...> wrote: >> >>> Actually, is there anyone one here who would like to take over the >>> daily-builds? You would need to get a new file host for the build >>> >> artifacts >> >>> since it's currently using my personal hosting environment, but I could >>> >> help >> >>> anyone who's interested to get their environment set up. >>> >> Is there a technical reason daily builds can not be hosted on sf.netitself? >> >> > > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ |
From: Jarek C. <jar...@po...> - 2012-06-15 19:08:01
|
W dniu 06/15/2012 07:25 PM, Eric Berry pisze: > (...) > Luckily Jenkins keeps all configuration in files that can easily be > copied from one machine to another (as has been the case when I've > upgraded machines). If someone would like the environment I could > provide a tar.gz file with all the jobs and settings. All that would > be required is it be dropped in there ~/.hudson directory and voila > you have yourself a complete copy of the jEdit daily build environment. Could you drop the file into sourceforge directory: /home/project-web/jedit/htdocs/files ? Just in case. You may also update the README.txt there or I'll do it, to describe the file. I hope you see nothing wrong in my curiosity and please keep the daily builds going! There's no need to change it, but it's better to have the knowledge shared. Jarek |
From: Eric B. <el...@gm...> - 2012-06-15 19:16:35
|
On Fri, Jun 15, 2012 at 12:07 PM, Jarek Czekalski <jar...@po...>wrote: > W dniu 06/15/2012 07:25 PM, Eric Berry pisze: > >> (...) >> >> Luckily Jenkins keeps all configuration in files that can easily be >> copied from one machine to another (as has been the case when I've upgraded >> machines). If someone would like the environment I could provide a tar.gz >> file with all the jobs and settings. All that would be required is it be >> dropped in there ~/.hudson directory and voila you have yourself a complete >> copy of the jEdit daily build environment. >> > Could you drop the file into sourceforge directory: > /home/project-web/jedit/**htdocs/files ? Just in case. > You may also update the README.txt there or I'll do it, to describe the > file. > I'll try, the tar.gz file will likely be pretty large. Will work on this over the next few weeks - Jenkins also stores a backup copy of each artifact locally so I'll work on getting a tar.gz that doesn't contain any of the jar files. > > I hope you see nothing wrong in my curiosity and please keep the daily > builds going! There's no need to change it, but it's better to have the > knowledge shared. That's funny. It's not me who's ever had a problem sharing knowledge or responsibility. Still, perhaps it is time someone else take these over anyway. Vampire? You never really supported me doing the daily-builds anyway, and I think you had always wanted to do them yourself, perhaps you'd like to take them over now? -- Learn from the past. Live in the present. Plan for the future. Blog: http://eric-berry.blogspot.com jEdit <http://www.jedit.org> - Programmer's Text Editor Bazaar <http://bazaar.canonical.com> - Version Control for Humans |
From: Eric B. <el...@gm...> - 2012-06-15 19:24:10
|
Actually, this would probably be preferable. I'm finding it harder and harder to find time to fix issues when they do come up, and sometimes the dailies stop working for days on end. At this point I'd recommend finding someone else to manage these on a permanent basis. On Fri, Jun 15, 2012 at 12:16 PM, Eric Berry <el...@gm...> wrote: > > > On Fri, Jun 15, 2012 at 12:07 PM, Jarek Czekalski < > jar...@po...> wrote: > >> W dniu 06/15/2012 07:25 PM, Eric Berry pisze: >> >>> (...) >>> >>> Luckily Jenkins keeps all configuration in files that can easily be >>> copied from one machine to another (as has been the case when I've upgraded >>> machines). If someone would like the environment I could provide a tar.gz >>> file with all the jobs and settings. All that would be required is it be >>> dropped in there ~/.hudson directory and voila you have yourself a complete >>> copy of the jEdit daily build environment. >>> >> Could you drop the file into sourceforge directory: >> /home/project-web/jedit/**htdocs/files ? Just in case. >> You may also update the README.txt there or I'll do it, to describe the >> file. >> > > I'll try, the tar.gz file will likely be pretty large. Will work on this > over the next few weeks - Jenkins also stores a backup copy of each > artifact locally so I'll work on getting a tar.gz that doesn't contain any > of the jar files. > > >> >> I hope you see nothing wrong in my curiosity and please keep the daily >> builds going! There's no need to change it, but it's better to have the >> knowledge shared. >> > > That's funny. It's not me who's ever had a problem sharing knowledge or > responsibility. > > Still, perhaps it is time someone else take these over anyway. Vampire? > You never really supported me doing the daily-builds anyway, and I think > you had always wanted to do them yourself, perhaps you'd like to take them > over now? > > > > -- > Learn from the past. Live in the present. Plan for the future. > Blog: http://eric-berry.blogspot.com > jEdit <http://www.jedit.org> - Programmer's Text Editor > Bazaar <http://bazaar.canonical.com> - Version Control for Humans > -- Learn from the past. Live in the present. Plan for the future. Blog: http://eric-berry.blogspot.com jEdit <http://www.jedit.org> - Programmer's Text Editor Bazaar <http://bazaar.canonical.com> - Version Control for Humans |
From: Jarek C. <jar...@po...> - 2012-06-15 19:33:01
|
I think we should start from finding hosting for the infrastructure. There Eric could setup everything and then we would gradually learn to manage it. Tomcat server with 5GB space is available in Poland for 100$ a year (linuxpl.com). SF is not enough for this kind of stuff, because it doesn't support java server nor cron. I guess this is the point at which we need money. Vampire, is it something we can afford? Jarek W dniu 06/15/2012 09:24 PM, Eric Berry pisze: > Actually, this would probably be preferable. I'm finding it harder and > harder to find time to fix issues when they do come up, and sometimes > the dailies stop working for days on end. At this point I'd recommend > finding someone else to manage these on a permanent basis. > > On Fri, Jun 15, 2012 at 12:16 PM, Eric Berry <el...@gm... > <mailto:el...@gm...>> wrote: > > > > On Fri, Jun 15, 2012 at 12:07 PM, Jarek Czekalski > <jar...@po... <mailto:jar...@po...>> wrote: > > W dniu 06/15/2012 07:25 PM, Eric Berry pisze: > > (...) > > Luckily Jenkins keeps all configuration in files that can > easily be copied from one machine to another (as has been > the case when I've upgraded machines). If someone would > like the environment I could provide a tar.gz file with > all the jobs and settings. All that would be required is > it be dropped in there ~/.hudson directory and voila you > have yourself a complete copy of the jEdit daily build > environment. > > Could you drop the file into sourceforge directory: > /home/project-web/jedit/htdocs/files ? Just in case. > You may also update the README.txt there or I'll do it, to > describe the file. > > > I'll try, the tar.gz file will likely be pretty large. Will work > on this over the next few weeks - Jenkins also stores a backup > copy of each artifact locally so I'll work on getting a tar.gz > that doesn't contain any of the jar files. > > > I hope you see nothing wrong in my curiosity and please keep > the daily builds going! There's no need to change it, but it's > better to have the knowledge shared. > > > That's funny. It's not me who's ever had a problem sharing > knowledge or responsibility. > > Still, perhaps it is time someone else take these over anyway. > Vampire? You never really supported me doing the daily-builds > anyway, and I think you had always wanted to do them yourself, > perhaps you'd like to take them over now? > > > > -- > Learn from the past. Live in the present. Plan for the future. > Blog: http://eric-berry.blogspot.com <http://eric-berry.blogspot.com/> > jEdit <http://www.jedit.org <http://www.jedit.org/>> - > Programmer's Text Editor > Bazaar <http://bazaar.canonical.com > <http://bazaar.canonical.com/>> - Version Control for Humans > > > > > -- > Learn from the past. Live in the present. Plan for the future. > Blog: http://eric-berry.blogspot.com <http://eric-berry.blogspot.com/> > jEdit <http://www.jedit.org <http://www.jedit.org/>> - Programmer's > Text Editor > Bazaar <http://bazaar.canonical.com <http://bazaar.canonical.com/>> - > Version Control for Humans |
From: Dale A. <da...@gr...> - 2012-06-15 20:55:28
|
Maybe another option is Amazon Web Services? I don't have a lot of experience with it yet, but setting up a tomcat instance takes less than half an hour. I don't know if a Mac vm is available, though. I'll look into as a possibility, anyway. The "affording" part may be the issue. Eric, about how much bandwidth are you using per month hosting the daily builds? Dale On Fri, Jun 15, 2012 at 1:32 PM, Jarek Czekalski <jar...@po...>wrote: > I think we should start from finding hosting for the infrastructure. > There Eric could setup everything and then we would gradually learn to > manage it. > > Tomcat server with 5GB space is available in Poland for 100$ a year ( > linuxpl.com). > > SF is not enough for this kind of stuff, because it doesn't support java > server nor cron. I guess this is the point at which we need money. Vampire, > is it something we can afford? > > Jarek > > W dniu 06/15/2012 09:24 PM, Eric Berry pisze: > > Actually, this would probably be preferable. I'm finding it harder and > harder to find time to fix issues when they do come up, and sometimes the > dailies stop working for days on end. At this point I'd recommend finding > someone else to manage these on a permanent basis. > > On Fri, Jun 15, 2012 at 12:16 PM, Eric Berry <el...@gm...> wrote: > >> >> >> On Fri, Jun 15, 2012 at 12:07 PM, Jarek Czekalski < >> jar...@po...> wrote: >> >>> W dniu 06/15/2012 07:25 PM, Eric Berry pisze: >>> >>>> (...) >>>> >>>> Luckily Jenkins keeps all configuration in files that can easily be >>>> copied from one machine to another (as has been the case when I've upgraded >>>> machines). If someone would like the environment I could provide a tar.gz >>>> file with all the jobs and settings. All that would be required is it be >>>> dropped in there ~/.hudson directory and voila you have yourself a complete >>>> copy of the jEdit daily build environment. >>>> >>> Could you drop the file into sourceforge directory: >>> /home/project-web/jedit/htdocs/files ? Just in case. >>> You may also update the README.txt there or I'll do it, to describe the >>> file. >>> >> >> I'll try, the tar.gz file will likely be pretty large. Will work on >> this over the next few weeks - Jenkins also stores a backup copy of each >> artifact locally so I'll work on getting a tar.gz that doesn't contain any >> of the jar files. >> >> >>> >>> I hope you see nothing wrong in my curiosity and please keep the daily >>> builds going! There's no need to change it, but it's better to have the >>> knowledge shared. >>> >> >> That's funny. It's not me who's ever had a problem sharing knowledge >> or responsibility. >> >> Still, perhaps it is time someone else take these over anyway. Vampire? >> You never really supported me doing the daily-builds anyway, and I think >> you had always wanted to do them yourself, perhaps you'd like to take them >> over now? >> >> >> >> -- >> Learn from the past. Live in the present. Plan for the future. >> Blog: http://eric-berry.blogspot.com >> jEdit <http://www.jedit.org> - Programmer's Text Editor >> Bazaar <http://bazaar.canonical.com> - Version Control for Humans >> > > > > -- > Learn from the past. Live in the present. Plan for the future. > Blog: http://eric-berry.blogspot.com > jEdit <http://www.jedit.org> - Programmer's Text Editor > Bazaar <http://bazaar.canonical.com> - Version Control for Humans > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > -- > ----------------------------------------------- > jEdit Developers' List > jEd...@li... > https://lists.sourceforge.net/lists/listinfo/jedit-devel > > |
From: Alan E. <ala...@gm...> - 2012-06-15 21:03:47
|
If the hosting is for open source software we can likely get a free deal... For example... http://www.javaforge.com/project/11 These guys use amazon web services to host their stuff. And offer the service free to open source projects. On Fri, Jun 15, 2012 at 1:55 PM, Dale Anson <da...@gr...> wrote: > Maybe another option is Amazon Web Services? I don't have a lot of > experience with it yet, but setting up a tomcat instance takes less than > half an hour. I don't know if a Mac vm is available, though. I'll look into > as a possibility, anyway. The "affording" part may be the issue. Eric, about > how much bandwidth are you using per month hosting the daily builds? > |
From: Matthieu C. <cho...@gm...> - 2012-06-19 10:14:53
|
2012/6/15 Dale Anson <da...@gr...> > Maybe another option is Amazon Web Services? I don't have a lot of > experience with it yet, but setting up a tomcat instance takes less than > half an hour. I don't know if a Mac vm is available, though. I'll look into > as a possibility, anyway. The "affording" part may be the issue. Eric, > about how much bandwidth are you using per month hosting the daily builds? > > I would be very surprised if a Mac VM was available as Apple forbid running OS X in a virtual machine that is not hosted on a Mac. |
From: Jarek C. <jar...@po...> - 2012-06-19 10:25:36
|
<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> I suggest not to worry about Mac daily build. Very java installer is sufficient, isn't it?<br> <br> Jarek<br> <br> W dniu 2012-06-19 12:14, Matthieu Casanova pisze: <blockquote cite="mid:CAP...@ma..." type="cite"> <div class="gmail_quote">2012/6/15 Dale Anson <span dir="ltr"><<a moz-do-not-send="true" href="mailto:da...@gr..." target="_blank">da...@gr...</a>></span><br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Maybe another option is Amazon Web Services? I don't have a lot of experience with it yet, but setting up a tomcat instance takes less than half an hour. I don't know if a Mac vm is available, though. I'll look into as a possibility, anyway. The "affording" part may be the issue. Eric, about how much bandwidth are you using per month hosting the daily builds?<span class="HOEnZb"><font color="#888888"><br> <br> </font></span></blockquote> <div><br> </div> <div>I would be very surprised if a Mac VM was available as Apple forbid running OS X in a virtual machine that is not hosted on a Mac.</div> <div><br> </div> <div> </div> </div> </blockquote> </body> </html> |
From: Matthieu C. <cho...@gm...> - 2012-06-19 11:49:27
|
I agree, java installer is enough for daily build. 2012/6/19 Jarek Czekalski <jar...@po...> > I suggest not to worry about Mac daily build. Very java installer is > sufficient, isn't it? > > Jarek > > W dniu 2012-06-19 12:14, Matthieu Casanova pisze: > > 2012/6/15 Dale Anson <da...@gr...> > >> Maybe another option is Amazon Web Services? I don't have a lot of >> experience with it yet, but setting up a tomcat instance takes less than >> half an hour. I don't know if a Mac vm is available, though. I'll look into >> as a possibility, anyway. The "affording" part may be the issue. Eric, >> about how much bandwidth are you using per month hosting the daily builds? >> >> > I would be very surprised if a Mac VM was available as Apple forbid > running OS X in a virtual machine that is not hosted on a Mac. > > > > |
From: Eric B. <el...@gm...> - 2012-06-25 23:37:17
|
Hey there folks, Wanted this topic a bit. I'll be losing my mac very soon (Aug) and so probably won't be able to support the daily builds for mac .dmg any longer. Is there any progress on someone else taking over the daily builds? Otherwise I'll start moving the rest of them over to a new server immediately. |
From: Matthieu C. <cho...@gm...> - 2012-06-26 12:32:24
|
Hi, I will probably get a new Mac laptop in two weeks so I will be able to build mac packages when necessary but not do daily build with it (And it will not be a retina). 2012/6/26 Eric Berry <el...@gm...> > Hey there folks, > Wanted this topic a bit. I'll be losing my mac very soon (Aug) and so > probably won't be able to support the daily builds for mac .dmg any longer. > Is there any progress on someone else taking over the daily builds? > Otherwise I'll start moving the rest of them over to a new server > immediately. > |
From: Eric B. <el...@gm...> - 2012-06-26 17:29:18
|
Cool. Sorry for the confusion, but to be clear, I can still manage the dailies if no one wants to take them over permanently right now. I just won't be able to do the dmg any longer. On Tue, Jun 26, 2012 at 5:31 AM, Matthieu Casanova <cho...@gm...>wrote: > Hi, > I will probably get a new Mac laptop in two weeks so I will be able to > build mac packages when necessary but not do daily build with it (And it > will not be a retina). > > 2012/6/26 Eric Berry <el...@gm...> > >> Hey there folks, >> Wanted this topic a bit. I'll be losing my mac very soon (Aug) and so >> probably won't be able to support the daily builds for mac .dmg any longer. >> Is there any progress on someone else taking over the daily builds? >> Otherwise I'll start moving the rest of them over to a new server >> immediately. >> > > -- Learn from the past. Live in the present. Plan for the future. Blog: http://eric-berry.blogspot.com jEdit <http://www.jedit.org> - Programmer's Text Editor Bazaar <http://bazaar.canonical.com> - Version Control for Humans |