Lanny Brand CI Server.

1. 2017-05-25 at 3:14 PM UTC

   #1
   

   Sophie Pedophile Tech Support
   Get your free open source copy of Lanny brand Continuous Integration server rite nao!
   
   https://jenkins.io/doc/
2. 2017-05-25 at 3:18 PM UTC

   #2
   The Self Taught Man Black Hole
   ci - confidential informant.
3. 2017-05-25 at 4:48 PM UTC

   #3
   

   SBTlauien African Astronaut
   Looks interesting but I personally don't think I would need it for anything I do.
   
   So what exactly is an automation server? I looked it up and it appears to be something that makes it easier for a programmer to user his/her program with other applications. Is that correct?
4. 2017-05-25 at 4:59 PM UTC

   #4
   

   Sophie Pedophile Tech Support

   Originally posted by SBTlauien Looks interesting but I personally don't think I would need it for anything I do.
   
   So what exactly is an automation server? I looked it up and it appears to be something that makes it easier for a programmer to user his/her program with other applications. Is that correct?

   
   Something like that yes, i don't know much about it myself, i just thought it was funny that it shared a name with Lanny.
5. 2017-05-26 at 1:17 AM UTC

   #5
   

   SBTlauien African Astronaut
   Oh, I actually thought it was his project.
6. 2017-05-26 at 1:34 AM UTC

   #6
   

   Sophie Pedophile Tech Support

   Originally posted by SBTlauien Oh, I actually thought it was his project.

   
   We won't know until Lanny posts. Would be a pretty impressive project if you are doing it solo tbh.
7. 2017-05-26 at 2:21 AM UTC

   #7
   

   Lanny Bird of Courage
   Lol, nah, Jenkins isn't my project. They picked the name because it's like a "butler name", similar to Jeeves. We use it at work, I kinda chuckle at the emails of people being like "jenkins is fucking slow" and "jenkins isn't working again".
   
   

   Originally posted by SBTlauien Looks interesting but I personally don't think I would need it for anything I do.
   
   So what exactly is an automation server? I looked it up and it appears to be something that makes it easier for a programmer to user his/her program with other applications. Is that correct?

   
   So it's basically just a build server, but it's expanded to do a lot of stuff other than builds so they call this kind of thing an "automation server". A really common workflow is to periodically grab the latest code on a project, build it, run a test suite, and deploy it to some testing environment and notify people if any step in that process fails. That may sound pretty trivial if you haven't worked on massive projects before but deployment ready builds can a long time to run, on the order of hours isn't uncommon, involvings dozens of discrete steps. Test suites can be comparably slow. Deployments can likewise have a lot of steps and be pretty complex if you're doing things like signing/verification or DNS sorcery or any of a dozen other things that fall under the heading of "deployment".
   
   There's an argument to be made that things being complex enough to justify this kind of software existing is a pathology, but it does make life easier. I do a similar kind of thing for ISS, automatic build/test you can check out here if you're interested for some reason. Deployment is still an SSH script though.
   The following users say it would be alright if the author of this post didn't die in a fire!

   • Sophie, 
   • SBTlauien
8. 2017-05-26 at 2:24 AM UTC

   #8
   

   Sophie Pedophile Tech Support

   Originally posted by Lanny Lol, nah, Jenkins isn't my project. They picked the name because it's like a "butler name", similar to Jeeves. We use it at work, I kinda chuckle at the emails of people being like "jenkins is fucking slow" and "jenkins isn't working again".
   
   
   
   So it's basically just a build server, but it's expanded to do a lot of stuff other than builds so they call this kind of thing an "automation server". A really common workflow is to periodically grab the latest code on a project, build it, run a test suite, and deploy it to some testing environment and notify people if any step in that process fails. That may sound pretty trivial if you haven't worked on massive projects before but deployment ready builds can a long time to run, on the order of hours isn't uncommon, involvings dozens of discrete steps. Test suites can be comparably slow. Deployments can likewise have a lot of steps and be pretty complex if you're doing things like signing/verification or DNS sorcery or any of a dozen other things that fall under the heading of "deployment".
   
   There's an argument to be made that things being complex enough to justify this kind of software existing is a pathology, but it does make life easier. I do a similar kind of thing for ISS, automatic build/test you can check out here if you're interested for some reason. Deployment is still an SSH script though.

   
   That's actually pretty interesting.