Thanks you all for your very quick answers! I'll be patient then :) Sean, just to be clear, I was not thinking of triggering the whole nightly build, which of course must take many hours. I was thinking of triggering a new build for the single package that I am developing (something along the lines of what happens when a package is originally submitted through the file tracker).
Best, Frederic On Wed, Jan 23, 2013 at 1:47 PM, James W. MacDonald <jmac...@uw.edu> wrote: > Hi Frederic, > > As long as you have incremented your version number it will be rebuilt > tonight. There isn't a way to force the build machines to trigger a build. > > Best, > > Jim > > > On 1/23/2013 1:41 PM, Frederic Fournier wrote: > >> Hello everyone, >> >> I recently submitted a package to bioconductor, and couple of days ago, >> the package started to fail the automated daily build on george2 and >> moscato2. Today I made some changes that work on my testing environment, >> but I would like to know if the changes have corrected the situation on >> george2 and moscato2. Is there a way to trigger a new build on those >> machines, or do I have to be patient and wait until tomorrow to see if the >> package passes the nightly build again? >> >> Thank you for your help, >> >> Frederic >> >> ______________________________**_________________ >> Bioc-devel@r-project.org mailing list >> https://stat.ethz.ch/mailman/**listinfo/bioc-devel<https://stat.ethz.ch/mailman/listinfo/bioc-devel> >> > > -- > James W. MacDonald, M.S. > Biostatistician > University of Washington > Environmental and Occupational Health Sciences > 4225 Roosevelt Way NE, # 100 > Seattle WA 98105-6099 > > [[alternative HTML version deleted]] _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
