spk-logo-white-text-short2
0%
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

Configuring a Build Job Using Hudson

Written by SPK Blog Post
Published on July 16, 2013

Last time we had a look at how to acquire and install Hudson, a continuous build and integration system beneficial to software engineering. This week we take a look at how to create and run a job using Hudson, and then look at the job output.

hudson build jobHudson can run a wide variety of jobs; either manually, or by scheduling them. There are also a wide variety of supporting features for such things as source control, email of results, multiple build steps, generated build numbers, and many others. Hudson is very likely to have the combination that will meet your needs for an automated development process. This blog entry just gives the basics on how to set up a job and run it. Once you see that, we will leave the further investigation to you!

We hope that the example presented proves helpful to you. Have a look at our document on how to set up and configure Hudson jobs and read about all the details. And then please post a comment on how useful you found this post to be. Thanks.

Latest White Papers

10 AI Use Cases: Accelerating Automotive Embedded Development

10 AI Use Cases: Accelerating Automotive Embedded Development

Software-defined and electric vehicles are only increasing as automotive technology advances. As these features grow, automakers must adapt. Manufacturing a car is not the same as it was years ago. This eBook explores how AI can be used in the automotive development...

Related Resources

What CIOs Get Wrong About PLM and Digital Thread Strategy

What CIOs Get Wrong About PLM and Digital Thread Strategy

PLM and Digital Strategy for CIOs Hello, everyone, and welcome back to another SPK and Associates vlog. My name is Michael Roberts. I'm the Vice President of Sales and Marketing here at SPK and Associates. Today, we're tackling a topic that comes up consistently in...

Why Late-Stage Changes Are Killing Your Time to Market

Why Late-Stage Changes Are Killing Your Time to Market

Key Takeaways Late-stage changes get expensive fast: The farther a problem travels through design, testing, and manufacturing, the more time, cost, and rework it creates. Disconnected systems and weak traceability are major causes: When requirements, design, software,...