[
https://issues.apache.org/jira/browse/ETCH-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652946#action_12652946
]
scott comer commented on ETCH-21:
---------------------------------
the mail threads:
[EMAIL PROTECTED] wrote:
-> http://www.apache.org/dev/
-> http://vmbuild.apache.org/continuum/groupSummary.action
If Etch has not been already added to Continuum you might need to talk
to the infra folks...
Cheers
Daniel
---------------------------------------
[EMAIL PROTECTED] wrote:
On Sun, Oct 12, 2008 at 5:29 PM, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
> > Does Apache have build-environment resources that we could leverage? Perhaps
> > a shared Atlassian Bamboo or Apache Continuum or similar?
As pointed our by Daniel, there is a Continuum install available as
well as Hudson (http://hudson.zones.apache.org/hudson/) and the
Geronimo guys seems to be setting up AntHill, do know if the idea is
to open that up to all projects.
> > I would like to see us building continuously on Windows and Linux and OSX.
This interests me as well. As a user of Hudson, would it be possible
to have build agents on other OSes than the one currently used
(Solaris)?
/niklas
--------------------------------
[EMAIL PROTECTED] wrote:
As others mentioned just drop a request into the INFRA JIRA, and
whether you want to use Continuum or Hudson.
Continuum currently runs on Linux - I'm currently investigating
setting up a Windows server for the same. Hudson runs on Solaris but
I'm sure it could farm builds out to either of those as well if that
was set up.
Cheers,
Brett
------------------------------------------
[EMAIL PROTECTED] wrote:
one of the issues is, we want to have signed builds (both java and csharp).
that means build certificates
safely managed, or else we have to make delay signed artifacts and then
download them and sign
them here. how are other people handling this issue?
scott out
---------------------------------------
[EMAIL PROTECTED] wrote:
Scott,
At Apache there's generally no need to sign automatic builds. Releases need to
be signed, but they're not generated automatically, but are the result of
voting, a manual process. Automated builds are for testing, not for use
outside the project. We mostly only care whether automatic builds succeed
without error. Automatically-built artifacts have no other guarantees, so
signing seems unnecessary.
Doug
> make the official build process work again
> ------------------------------------------
>
> Key: ETCH-21
> URL: https://issues.apache.org/jira/browse/ETCH-21
> Project: Etch
> Issue Type: Task
> Components: build
> Reporter: scott comer
> Assignee: Rene Barraza
> Fix For: 1.0.2
>
>
> the bamboo build at cisco is currently offline. plus it needs a few
> improvements...
> 1) pull source from asf.
> 2) publish artifacts of builds in public location.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
