Open GoogleCodeExporter opened 9 years ago
I should mention that after I upgraded, I set "Always allow manual trigger on
pipeline steps" to true and re-triggered an aborted build late in the pipeline.
It completed fine. Then I started a new pipeline and thats when the form
disappeared. Note that the pipeline continues to execute fine (i.e. upstream
jobs that auto-trigger do trigger).
Also, each job in my pipeline uses Clone Workspace on the first job in the
pipeline (most recent successful build, although I wish there was an option for
upstream build that triggered this job!).
Original comment by chris.fa...@kik.com
on 11 Oct 2012 at 6:10
I also tried deleting the view and re-creating it but I still see the image
attached.
Original comment by chris.fa...@kik.com
on 11 Oct 2012 at 6:13
Attachments:
After downgrading to pipeline version 1.2.4, it still happened. So this is a
problem with jenkins. Most likely related to the new lazy loading stuff but I'm
not 100% sure.
Any ideas for a workaround besides downgrading jenkins would be appreciated.
Original comment by chris.fa...@kik.com
on 12 Oct 2012 at 5:00
Upgraded to 1.4.6 RC branch seems to have fixed it.
Original comment by chris.fa...@kik.com
on 16 Oct 2012 at 3:55
[deleted comment]
[deleted comment]
Upgrading to 1.486 and 1.487 both consistently show this issue.
Downgrading to 1.484 doesn't exhibit this issue.
Original comment by bigolewannabe@gmail.com
on 29 Oct 2012 at 2:09
@ Comment #7.
1.485 was a major change with major issues. Please file this as a Jenkins
issue, not a pipeline plugin one.
Original comment by ChrisGW...@gmail.com
on 6 Nov 2012 at 6:29
For those playing along, it looks like
https://issues.jenkins-ci.org/browse/JENKINS-15719 is the bug to track.
Original comment by bigolewannabe@gmail.com
on 6 Nov 2012 at 10:21
On my end this happen after a reset (server or simply Jenkins).
By visiting the root job of the pipeline (Go to url :
http://SERVER:PORT/job/JOBNAME/) once, I not see the pipeline with jobs in it.
Original comment by thierry....@gmail.com
on 11 Feb 2013 at 2:52
I have the very same problem, but I'm using Jenkins 1.523 (preatty shinning
new!) and Build Pipeline Plugin 1.3.5.
How can I upgrade to this 1.4.6 RC branch? It's really the solution.
Original comment by hele...@ciandt.com
on 19 Jul 2013 at 11:04
Original issue reported on code.google.com by
chris.fa...@kik.com
on 11 Oct 2012 at 6:05