ganesansays / build-pipeline-plugin

Automatically exported from code.google.com/p/build-pipeline-plugin
0 stars 0 forks source link

Config / Refresh frequency should also "detect" new started builds #128

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
When the the build-frequency is set, the build cards get updated correctly, but 
when a new pipeline got started the view does not update.

The workaround would be to enable Jenkins "Autorefresh". 

But it would be nicer if the pipeline plugin also detects a new build of the 
initial project and triggers the page refresh by itself. So i cannot not forget 
to enable Autorefresh on the pipeline views.

System : Jenkins 1.466.1, pipeline 1.3.3

Original issue reported on code.google.com by redsa...@gmail.com on 23 Aug 2012 at 12:02

GoogleCodeExporter commented 9 years ago
Can you further clarify how you are triggering the new build?  Are you doing so 
in the pipeline view via the "Run" option at the top, or elsewhere and asking 
for the view to poll for such activity so it can update as you're requesting?

Original comment by dankirkd@gmail.com on 27 Aug 2012 at 12:19

GoogleCodeExporter commented 9 years ago
i just open the pipeline view. and the wait for a svn commit. which triggers 
the pipeline.

so the new started pipeline from svn commits dont show up.

Original comment by redsa...@gmail.com on 27 Aug 2012 at 11:20

GoogleCodeExporter commented 9 years ago
Btw. the jenkins subversion plugin uses a svn hook. So the jenkins polling 
interval is set to once a year.

Original comment by redsa...@gmail.com on 5 Sep 2012 at 9:44