Jenkins can orchestrate tasks that are not related to continuous integration.
I've used it as a web interface to regularly scheduled jobs like cron. However, if that is its only use, then I think that is more software than you need. If you need to present graphs, charts and tables from one run to the next and if those graphs, charts and tables can be represented in Jenkins, then it makes sense (to me) to also use it to orchestrate your scheduled tasks. If you need to refer to the history of task execution from a web interface, then Jenkins is well-suited. Then it makes sense (to me) to also use it to orchestrate your scheduled tasks. I often refer to the execution history of specific jobs to identify why they failed and how to improve them. The web interface makes that easier for me than filtering through my e-mail box for the output from cron jobs. Mark Waite On Mon, Aug 20, 2018 at 3:34 AM ChrizK <kemp.ch...@gmail.com> wrote: > Hi Mark > > Thanks for taking the time to reply, it is appreciated. > > Reading the BlazeMeter blog has prompted me to add one (perhaps important) > comment ... > My use has absolutely nothing to do with Software Development/CI. > The load test is related to a telecoms environment, producing traffic > emulating calls (RADIUS, DIAMETER/Gx/Gy, User Plane/Internet etc). > > Given this additional information, would Jenkins still be considered a > good option? > > Regards > > > On Friday, 17 August 2018 18:34:01 UTC+1, Mark Waite wrote: > >> Jenkins can orchestrate tasks, including build, test, and deploy. The >> folks at BlazeMeter have a great blog post >> <https://www.blazemeter.com/blog/continuous-integration-101-how-run-jmeter-jenkins> >> that highlights ways to run Apache JMeter with Jenkins. There is also a 2015 >> research paper >> <https://www.researchgate.net/publication/274738961/download> on >> integrating performance testing into Jenkins builds. >> >> The "how" question depends very much on the specifics of your load >> testing tool, how you would like to present the results, and how much >> effort you want to spend to do it. >> >> Mark Waite >> >> On Fri, Aug 17, 2018 at 10:10 AM ChrizK <kemp....@gmail.com> wrote: >> > As an initial warning, I am COMPLETELY new to Jenkins. >>> I have never installed it, or seen it running. >>> My manager gave me a task, saying that a team member had suggested >>> Jenkins. >>> >>> We have an in-house load test tool, which runs on multiple nodes, >>> resulting in significant load (millions of connections). >>> We need to orchestrate the initialisation of each node, and I perceive >>> the need to monitor the execution, restart on failure, and terminate at a >>> given point (assumed to be time). >>> >>> Actually, I haven't even seen the load test tool yet, as I have only >>> just (re)joined the team after several years. >>> I am assuming it is a unix/linux command line executable with >>> parameters, or perhaps a config script which may need adapting for each run. >>> >>> Hopefully that is enough information to get started. >>> >>> So, my initial questoin is, does Jenkins suit the purpose? >>> ...and my follow on questoin(s) will be, how! >>> >>> (I have been viewing youtube/googling all day. All I have found that >>> appears to be relevant, are references to Execute Shell, and some 'pro' >>> Jenkins blogs on switching from CRON. One blog indicates that Jenkins would >>> be installed on each machine, but my perception is a single, stand alone, >>> server, which orchestrates multiple nodes, by SSH login, command execution >>> and monitoring ...but perhaps, I am way off) >>> >>> Thank you in advance for any help. >>> >>> Also, is this the main forum for Jenkins? I was surprised there wasn't >>> one on their site,which appears to favour a chat facility (which doesn't >>> seem very practical when looking for advice around the globe). >>> >>> Kind Regards >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> >> To unsubscribe from this group and stop receiving emails from it, send an >>> email to jenkinsci-use...@googlegroups.com. >> >> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/6429acff-f41a-4f3d-928c-949eec643578%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/6429acff-f41a-4f3d-928c-949eec643578%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/0c833ca9-a531-4d30-8883-7cec94c72d8e%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/0c833ca9-a531-4d30-8883-7cec94c72d8e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtH_4K8T%2BBUh-Dw9eGP-LD0md%3D-g6mkF-1r_R0c2KH32-w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
