Jenkins continuous integration and nightly builds -


i’m new jenkins , (reassurance) how think should setup jobs.

the end goal simple.

  • objective 1: when developer commits code mercurial repo jenkins pulls changes, builds project , runs unit tests. happens continuously throughout day developers earliest possible feedback if break something.

  • objective 2: nightly, jenkins pulls last stable build above , runs automated ui tests. if tests pass publishes nightly build somewhere.

i have job configured achieves objective 1 i’m struggling objective 2. (not publishing part, idea of seeding job last stable build of objective 1).

at moment, i’m planning use branches in hg repo implement this.

my branches main >> int >> dev.

the job in objective 1 work on tip of dev branch. if build succeeds , tests pass commit int branch.

the job in objective 2 work on tip of int branch.

is how it’s done?

i’ve been looking at/considering: - plugins promoted builds , copy artifacts - parameterised builds - downstream jobs

imo objectives common can’t find many examples of approach online. perhaps it’s obvious there no need wanted check.

in past i've stored generated artifacts in artifact repository. use nexus or artifactory this, i've used flat file system.

you put build artifacts in source control, said, there isn't reason have version control on compiled builds (you should able re-create them based on rev numbers) - take lot of space in repo.

if version numbers incremental in nature nightly job should able pull latest 1 easily.


Comments

Popular posts from this blog

windows - Single EXE to Install Python Standalone Executable for Easy Distribution -

c# - Access objects in UserControl from MainWindow in WPF -

javascript - How to name a jQuery function to make a browser's back button work? -