Well the build itself isn't failing. So deploy should still work.
Regarding the tests failing, you do have sudo rights for the vm where the builds are running, right?
So it *should* be just a matter of installing xvfb and firefox.
Cheers,
Uli
On 09.01.2010 00:08 schrieb Andreas Andreou:
Yea, i wanted that too, but 5.0, 5.1 and 5.2 are not running the
integration tests,
so they're basically failing.
But i'll try to run a deploy from hudson to see what happens - hopefully,
no user credentials will be needed and the user that runs hudson will
be allowed the deploy (i'm not really sure if that's the case, but
will find out)
On Fri, Jan 8, 2010 at 16:26, Ulrich Stärk<[email protected]> wrote:
Now that we got all branches building on hudson and also have setup nexus,
why don't we deploy snapshot releases for 4.1, 5.0, 5.1 and 5.2 to nexus?
Could you set this up Andreas?
Uli
On 04.10.2009 22:34 schrieb Andreas Andreou:
The vote to use Nexus repository manager for snapshots/releases
deployment has passed with the
following results
Andreas Andreou: +1
Howard Lewis Ship: +1
Thiago H. de Paula Figueiredo: +1
Igor Drobiazko: +1
Massimo Lusetti: +1
Kalle Korhonen: +1
I've created an issue to track progress on this - TAPESTRY-2754
PS. Sorry for the delay in announcing the results, i happened to be
out of town.
On Wed, Sep 30, 2009 at 7:28 AM, Kalle Korhonen
<[email protected]> wrote:
+1 (non-binding)
Kalle
On Tue, Sep 29, 2009 at 2:05 PM, Massimo Lusetti<[email protected]>
wrote:
On Mon, Sep 28, 2009 at 6:51 PM, Andreas Andreou<[email protected]>
wrote:
So, since there doesn't seem to be any more questions on the
'suggested'
release process (and the use of nexus for it), i'd like to start a vote
for it.
Vote +1 if you'd like tapestry to use the Nexus repository manager for
snapshots/releases deployment. Or, if you'd like to keep the process
as is, vote -1
Massimo Lusetti: +1 (non-binding)
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
