OpenStack Core Infrastructure

jenkins views should be managed by puppet

Bug #1058902 reported by Bhuvan Arumugam
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure
Won't Fix
Medium
Bhuvan Arumugam

Bug Description

In jenkins, the specific component view should display all jobs triggered when a patch is posted to that repository. For example, if a patch is posted to "keystoneclient", the following jobs are triggered:
    gate-python-keystoneclient-docs
    gate-python-keystoneclient-merge
    gate-python-keystoneclient-pep8
    gate-python-keystoneclient-python26
    gate-python-keystoneclient-python27
    *gate-tempest-devstack-vm
    *gate-tempest-devstack-vm-cinder

Right now, the last 2 tempest jobs are not displayed, when we access "keystone" view:
  https://jenkins.openstack.org/view/Keystone/

It makes it hard to track the status of all triggered and in-progress jobs, after submitting a patch. We should access any one of keystone job/build page to view the complete list and access the job whose status is None, assuming that it's in progress.

If these jobs are listed in "keystone" jenkins view, we could track all jobs triggered due to keystone specific patch.

Revision history for this message
Bhuvan Arumugam (bhuvan) wrote :

I think, the jenkins administration is not handled by puppet. If i'm granted permission, I'd love to fix jenkins views in the UI.

Revision history for this message
Clark Boylan (cboylan) wrote :

The tempest devstack jobs are not shown under the keystone jenkins view because those two jobs are shared by most of the projects (they don't belong to a single project like the keystone jobs that do show up; at least that is my understanding of why this happens). However, there are a couple ways to get the info you are looking for.

If you open the status of a particular build eg https://jenkins.openstack.org/view/Keystone/job/gate-keystone-merge/1999/ you will see links to the other jobs that were run for the related change (these links are not updated until after they complete though; making the next option a better solution than this one). You can also view the Zuul status page too see the status of all changes and their respective build queues, https://jenkins.openstack.org/zuul/status.

If fixed through the Jenkins UI will that fix accommodate the other projects that make use of the tempest devstack gate jobs?

Revision history for this message
Bhuvan Arumugam (bhuvan) wrote :

Yes, a specific job shall be listed in multiple views. If we run tempest jobs for most of projects, we must include them in all those jenkins views.

Revision history for this message
Monty Taylor (mordred) wrote :

Is there a way we can extend jenkins job builder or our puppet module to maintain these views? I agree, the current maintenance mechanism is not great.

summary: - jenkins view should display all related jobs
+ jenkins views should be managed by puppet
Changed in openstack-ci:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Bhuvaneswaran A (bhuvan)
milestone: none → grizzly
Revision history for this message
James E. Blair (corvus) wrote :

I think the use case described in the bug is now handled by the zuul status screen.

Changed in openstack-ci:
status: Triaged → Won't Fix
Monty Taylor (mordred)
Changed in openstack-ci:
milestone: grizzly → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.