+1
I have assigned the ticket to myself and I did some preliminary
investigations in this matter. It seems to me the most complicated part
will be configuring tasks in such way that release commiter could use it
without exposing his credentials for Git, SVN and Maven. I suggest we
create an integration user for public Teamcity and grant him permissions to
commit and deploy in the repositories.
On Thu, Jun 8, 2017 at 6:10 AM, Denis Magda <
[hidden email]> wrote:
> +1
>
> > On Jun 7, 2017, at 3:40 AM, Sergey Kozlov <
[hidden email]> wrote:
> >
> > Hi, Igniters
> >
> > I'd start the discussion for following changes of release procedure.
> > As you may know we provided not source artifacts only but also a set of
> > binaries that makes using of the release is more friendly namely:
> > - binary farbic artifact
> > - binary hadoop artifact
> > - articats in Apache Ignite Maven repository
> > - artifacts for .Net/C++ in NuGet
> >
> > At the moment we release it by procedure [1] and some actions should be
> > processed manually (or some semi-automated way) by the release
> > lead committer.
> >
> > I suggest to implement all such tasks on public teamcity as TC
> > configurations in a special project and allow to run them by the release
> > lead committer.
> >
> > Corresponding JIRA issue is [2]
> >
> > [1]
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process> > [2]
https://issues.apache.org/jira/browse/IGNITE-5249> > --
> > Sergey Kozlov
>
>
Locked
