[JIRA] (JENKINS-58534) Impossible to access promotion's console output (navigation is broken from links and breadcrumbs)

1 view
Skip to first unread message

slavd@ganz.com (JIRA)

unread,
Jul 17, 2019, 12:35:02 PM7/17/19
to jenkinsc...@googlegroups.com
slav dok created an issue
 
Jenkins / Bug JENKINS-58534
Impossible to access promotion's console output (navigation is broken from links and breadcrumbs)
Issue Type: Bug Bug
Assignee: Oleg Nenashev
Components: promoted-builds-plugin
Created: 2019-07-17 16:34
Environment: Jenkins LTS version: 2.176.1
Promoted Builds version: 3.3
openjdk version: 1.8.0_161
CentOS version: 7.2.1511
Labels: plugin promoted-builds breadcrumb navigation consoleoutput
Priority: Major Major
Reporter: slav dok

This works fine in Promoted Builds version 3.2, but breaks once you upgrade to 3.3

Usually, you can access the promotion's console output by:

  • Selecting Build job (for example "Build_Job")
  • Selecting Build Number (for example "#5")
  • Clicking Promotion Status link
  • Picking a promotion from the list (for example "Promo1 > #2")

This will provide navigation breadcrumbs like:
Jenkins > Build_Job > #5 > Promotion Status > #2

At the same time, the URL would be like:
server_url:port/job/Build_Job/5/promotion/Promo1/promotionBuild/2/console

After upgrading to 3.3

  • The URL remains same, but the UI loops back to the console output of the build, not the console output of the promotion.
  • The breadcrumbs also loop back to the build's console output
    Jenkins > Build_Job > #5 > Promotion Status > #5
  • Instead of seeing console output of "Promo1 > #2", I am seeing console output of "Build_Job > #5" (even though I am in the "Promotion Status" page and selecting promotion's builds)

It becomes impossible to access Promotion's console output no matter what navigation route you take.

The promotions actions still seem to happen fine, and the console output can be found directly on the filesystem at:
$JENKINS_HOME/jobs/Build_Job/promotions/Promo1/builds/2/log

Seems like the bug is only in navigation, and the behaviour corrects itself when downgrading to Promoted Builds version 3.2

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

sgabriel@brainfuse.com (JIRA)

unread,
Jul 19, 2019, 10:56:02 PM7/19/19
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 20, 2019, 3:16:02 AM7/20/19
to jenkinsc...@googlegroups.com

sonucts@gmail.com (JIRA)

unread,
Jul 28, 2019, 11:20:04 PM7/28/19
to jenkinsc...@googlegroups.com

ashetty@ensocare.com (JIRA)

unread,
Aug 1, 2019, 11:52:03 AM8/1/19
to jenkinsc...@googlegroups.com

sheelavasudevan3@gmail.com (JIRA)

unread,
Aug 6, 2019, 11:06:02 AM8/6/19
to jenkinsc...@googlegroups.com

I am facing same issue. Is there any timeline when the issue gets resolved?

tammy.osborn@dnr.wa.gov (JIRA)

unread,
Aug 26, 2019, 6:47:02 PM8/26/19
to jenkinsc...@googlegroups.com

I see the same thing. And like slav dok, once I downgraded to Promoted Builds version 3.2, navigation was fixed.

o.v.nenashev@gmail.com (JIRA)

unread,
Aug 27, 2019, 4:00:03 AM8/27/19
to jenkinsc...@googlegroups.com

> I am facing same issue. Is there any timeline when the issue gets resolved?
 
I plan to take a look at it in September, but cannot commit on it. Too many other emergencies, sorry
 
 

geedude@gmail.com (JIRA)

unread,
Sep 24, 2019, 10:03:02 PM9/24/19
to jenkinsc...@googlegroups.com
Jeff Y commented on Bug JENKINS-58534

+1 for this. Is there any workaround besides downgrading or manually going to the filesystem and looking at the log? I'm on a new Jenkins instance and can't downgrade, and checking the filesystem is pretty tedious as it sits on a box which only a few people have access to look at.

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

dbeck@cloudbees.com (JIRA)

unread,
Oct 7, 2019, 11:47:10 AM10/7/19
to jenkinsc...@googlegroups.com
Daniel Beck closed an issue as Duplicate
 

I proposed a PR fixing this as JENKINS-59600 so closing this as a duplicate of that later issue.

Change By: Daniel Beck
Status: Open Closed
Resolution: Duplicate

o.v.nenashev@gmail.com (JIRA)

unread,
Oct 7, 2019, 8:13:07 PM10/7/19
to jenkinsc...@googlegroups.com

bhaktij@cybage.com (JIRA)

unread,
Nov 13, 2019, 11:56:03 PM11/13/19
to jenkinsc...@googlegroups.com

Hi,

I am still facing same issue with plug-in version 3.4.

Any help here.

Reply all
Reply to author
Forward
0 new messages