Working with multiple configurations - where is the result?

I'm new to Jenkins, so maybe this is a dumb question, but ...

I am trying to write a task that will compile my code on several UNIX nodes. I created a project with several configurations and added one subordinate to it.

The job itself is a shell that only executes 'ls' and 'pwd'

Output:

Started by user anonymous Building on master in workspace C:\Program Files (x86)\Jenkins\workspace\Unix-third-party Triggering Linux64 Linux64 completed with result SUCCESS Finished: SUCCESS 

But I do not see anything in the output.

When I changed the matrix to use nodes instead of shortcuts, I managed to see the result, but I'm still not sure what I did.

A free-style project for the same node works without problems.

Where can I find the result?

+7
source share
3 answers

On your work page, you will see a link called "default" if you have only one node / slave or the name node if you have more than one.

Click on this link, then click on the output of the assembly and console.

How it works:

  -----------------config 1 -> build #X -> console output / Main Job build #X console output ----> \-----------------config 2 -> build #X -> console output 

What you are looking at is the console output for the main job, but it only contains trigger information. The actual output is contained in the console 1 outputs config 1 and config 2.

Please comment if you need further clarification and I would be happy to help. By the way, welcome to the world of Jenkins :-)

============================================= ====== ==========================

EDIT

The following URL should send you to your console output for the assembly where you selected Shortcut:

Replace everything in <>.

 http://<myserver>/job/<jobname>/label=<label>/<buildnumber>/console 
+9
source

I’m not sure that this will help you, but at work, to look at our subordinate consoles, the following URL will work:

https: // ci. (company) .com / job / QA / job / [projectname] / 13 / script = loadtest1 / console

I would suggest that your system would be similar.

Alternatively, if I switch to main ci. (company) .com / job / QA / job / [projectname] / I see a recent job in the left corner.

When this task is selected, the screen is based on our configurations that you select, then you can view the console output for this specific task.

View master job jenkins does not output console logs from slaves.

+1
source

I came across this today, not sure what caused it, but I was able to get my build configurations to show console logs and artifacts again by deleting the "builds" and "configurations" folders under "C: \ Program Files (x86) \ Jenkins \ works \ Projectname ".

Obviously, this also relieves you of the build history, but I just need the configurations to start again.

0
source

All Articles