it was part of the review queue, but it looks like the runs have been
gc'd. oh well!
best,
matt
On 09/11/2014 12:18 PM, shane knapp wrote:
you can just click on 'rebuild', if you'd like. what project
specifically? (i had forgotten that i'd killed
https://amplab.cs.berkeley.edu/jenkins/job/Spark-Master-Maven-with-YARN/557/,
which i just started a rebuild on)
On Thu, Sep 11, 2014 at 9:15 AM, Matthew Farrellee <m...@redhat.com
<mailto:m...@redhat.com>> wrote:
shane,
is there anything we should do for pull requests that failed, but
for unrelated issues?
best,
matt
On 09/11/2014 11:29 AM, shane knapp wrote:
...and the restart is done.
On Thu, Sep 11, 2014 at 7:38 AM, shane knapp
<skn...@berkeley.edu <mailto:skn...@berkeley.edu>> wrote:
jenkins is now in quiet mode, and a restart is happening soon.
On Wed, Sep 10, 2014 at 3:44 PM, shane knapp
<skn...@berkeley.edu <mailto:skn...@berkeley.edu>> wrote:
that's kinda what we're hoping as well. :)
On Wed, Sep 10, 2014 at 2:46 PM, Nicholas Chammas <
nicholas.cham...@gmail.com
<mailto:nicholas.cham...@gmail.com>> wrote:
I'm looking forward to this. :)
Looks like Jenkins is having trouble triggering
builds for new commits
or after user requests (e.g.
<https://github.com/apache/__spark/pull/2339#issuecomment-__55165937
<https://github.com/apache/spark/pull/2339#issuecomment-55165937>>).
Hopefully that will be resolved tomorrow.
Nick
On Tue, Sep 9, 2014 at 5:00 PM, shane knapp
<skn...@berkeley.edu <mailto:skn...@berkeley.edu>>
wrote:
since the power incident last thursday, the
github pull request builder
plugin is still not really working 100%. i
found an open issue
w/jenkins[1] that could definitely be affecting
us, i will be pausing
builds early thursday morning and then
restarting jenkins.
i'll send out a reminder tomorrow, and if this
causes any problems for
you,
please let me know and we can work out a better
time.
but, now for some good news! yesterday morning,
we racked and stacked
the
systems for the new jenkins instance in the
berkeley datacenter.
tomorrow
i should be able to log in to them and start
getting them set up and
configured. this is a major step in getting us
in to a much more
'production' style environment!
anyways: thanks for your patience, and i think
we've all learned that
hard
powering down your build system is a definite
recipe for disaster. :)
shane
[1] --
https://issues.jenkins-ci.org/__browse/JENKINS-22509
<https://issues.jenkins-ci.org/browse/JENKINS-22509>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org
For additional commands, e-mail: dev-h...@spark.apache.org
