[jira] [Commented] (INFRA-10385) Automating publishing artifacts via builds.a.o

["Sean Busbey (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/INFRA-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382112#comment-15382112 ] 

Sean Busbey commented on INFRA-10385:
-------------------------------------

[ASF release policy|http://www.apache.org/dev/release.html#owned-controlled-hardware] requires verifying (and signing) a release on hardware owned by the committer creating the vote. I can't think of a way you can do this on builds.a.o without failing to meet that policy.

> Automating publishing artifacts via builds.a.o
> ----------------------------------------------
>
>                 Key: INFRA-10385
>                 URL: https://issues.apache.org/jira/browse/INFRA-10385
>             Project: Infrastructure
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>          Components: Dists, Jenkins
>            Reporter: Vinod Kone
>            Assignee: Jake Farrell
>            Priority: Minor
>
> Currently the mesos project uses a set of scripts to build and do releases. While this process is fairly automated, the build happens on the release manager's laptop which is not ideal.
> I'm trying to find a way to automate the release process by running the build and release process on builds.a.o with a standard dev environment (using docker).
> The main blocker I see is with using credentials. How would the Jenkins job publish artifacts to repoisitory.a.o (for jars) and svn.a.o (for sdist and maybe eggs) and pypi (for eggs). As a side note, is it kosher to publish platform dependent binaries on ASF servers?
> What is the recommended/blessed way of doing this? How do other ASF projects do this?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)