1
Solved

Duplicate projects in Jenkins appear in the interface

It appears that i have the Master project in Jenkins twice, one that states that the build is broken and needs investigating, the other one states that no build has ever started on that project. This is regarding Jenkins.

 

I have attached a picture to see exactly what is happening.

 

Thanks.

Follow

6 replies

Votes Newest Oldest
1

Duplicate jobs problem should be fixed in 2.7.2

https://catlight.io/downloads 

Comment

Thank you. This has been completed. Working as expected.

Thank you. 

I have sent it.

#64

Comment

Thanks for the details!

Build history is duplicated, because Jenkins reports "master" branch under two different names - "origin/master" and "refs/remotes/origin/master", so CatLight thinks that those are two different branches.

We'll try to find a solution for this, stay tuned!

Update on 2.7.1: the aborted job has been dismissed, it leaves the investigation and the correct one

 

Comment

Hi, can you make sure that both "Master" jobs actually open builds of the same Jenkins job?

If they do, can you collect the Jenkins API response so we could inspect it further?

To do that, open the job page (not the build page), and add the following in the browser address bar:

/api/json?pretty=true&depth=2

It should look like https://myserver/job/master/api/json?pretty=true&depth=2

This should provide you with a big JSON output describing how Jenkins sees this job.

Please attach the response to a private ticket at http://catlight.helprace.com/add-ticket , and we will investigate this further.

It takes me to a build created Feb 20th that was Aborted by me.

Also, it appears that i now have 3 master Jobs in Catlight, one correct, one that has a failed build and needs investigating and one that is aborted. And i have only one Master job... that works.

Comment
1

In CatLight 2.7.1 we'll ignore builds that have unusual results. Let me know if this fixes the problem.

https://catlight.io/downloads 

Comment

We split build history into branches, and show each branch as a separate job on the dashboard. 

It is likely that build in duplicated job does not have any branch information in it. This can happen if it failed or was canceled before branch was identified. So we treat it as branch-less build and show it separately.

Can you click on the grey square for the duplicated job and tell me what is the status of that build and how long ago it was built?

Comment
Reply