gocd: Pipeline and stage run 'Latest' counters have stopped working
Bug
- Bug Report
- Feature proposal
Summary
- Since 18.something (to my memory), the UI links of the form
/go/pipelines/<pipeline_name>/Latest/<stage_name>/Latest stopped working and return a 404.
- The artifact URLs still contain the route of the form
/go/files/<pipeline>/Latest/<stage>/Latest/<job>/<artifact>. This should continue to work đ
Basic environment details
Steps to Reproduce
- Open a pipeline view: e.g.
/go/pipelines/<pipeline>/777/default/1
- Replace the numbers with
Latest
- observe 404
Expected Results
- latest pipeline/stage run view is shown
Actual Results
Possible Fix
- (re-)add a route, calculating the latest counters for the view
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 16 (16 by maintainers)
Commits related to this issue
Verified on 19.1.0 (8445-eb004d2a8df97734b224df38f04b2501c65ddd63)
Yeah, we removed the implementation because it was buggy (and undocumented) https://github.com/gocd/gocd/pull/4660#issue-181755293
I can imagine that people may have bookmarked links containing â/latestâ like http://localhost:8153/go/tab/build/detail/gocd-rpi-unicorn-hat-monitor/Latest/test/Latest/unit, and if itâs useful enough, we can add support for the âlatestâ keyword.
Looks like
counterOrLabelwas the cause of ambiguity which could lead to bugs. Instead, we could use eithercounteror the keyword"latest". ArbitraryLabelsshouldnât be allowed though.Also, see conversation in gitter.