-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins 1.554, Build Pipeline version 1.4.3
I installed Build Pipeline and tried it on my jobs. They work by invoking a build as a promotion action. I was disappointed that the pipeline view failed to follow my builds except where there was a direct chain of automatic chained jobs.
I guess perhaps my expectation doesn't match the pipeline concept? Or perhaps my build flow is not a pipeline?
Basically, we have a continuous build job which allows a selected build to be promoted. The promotion action causes another build to be executed. Generally we do not have an automatic build chain, but a manual promotion chain. This approach works better for us, since we don't have to maintain (and archive) any build history unless a build is promoted.
Perhaps my expectation is in error, however I think it would be a great enhancement to a great plugin!