I am new to Jenkins and I like some help (reassurance) on how I think I need to set up my assignments.
The ultimate goal is pretty simple.
Goal 1: When a developer compiles code into a mercury repo, Jenkins pulls the changes, builds the project, and runs unit tests. This happens continuously throughout the day, so developers get the earliest possible feedback if they break something.
Goal 2: At night, Jenkins pulls the last stable build from the top and runs automated user interface tests. If these tests pass, he publishes the nightly build somewhere.
I have a task set up that reaches goal 1, but Im struggling with goal 2. (Not the publication part, the idea of sowing this work with the last stable line of goal 1).
I am currently planning to use branches in the HG repository to implement this.
My branches look something like this: Main → Int → Dev.
Work in object 1 will work on the tip of the Dev branch. If the assembly succeeds and tests pass, it will be passed to the Int branch.
The task in object 2 can then just work on the tip of the Int branch.
How is this even done?
I also looked / looked at: - plugins, such as promoted assemblies and artifact copying - parameterized assemblies - downstream jobs
IMO , . , , , .