You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2015/02/05 21:37:34 UTC
[jira] [Created] (BUILDS-52) Automating publishing artifacts via
builds.a.o
Vinod Kone created BUILDS-52:
--------------------------------
Summary: Automating publishing artifacts via builds.a.o
Key: BUILDS-52
URL: https://issues.apache.org/jira/browse/BUILDS-52
Project: Infra Build Platform
Issue Type: Wish
Reporter: Vinod Kone
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)