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

ASF GitHub Bot commented on IGNITE-8172:
----------------------------------------

Github user alamar commented on a diff in the pull request:

    https://github.com/apache/ignite-release/pull/1#discussion_r180746462
  
    --- Diff: scripts/vote_3_step_1[rpm]create_repository.sh ---
    @@ -19,17 +27,19 @@ then
     fi
     echo
     
    +
     #
     # Build package
     #
     echo "# Building RPM package #"
    -if [ ! -f rpmbuild ]; then rm -rf rpmbuild; fi
    -mkdir -pv rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
    +if [ -d rpmbuild ]; then rm -r rpmbuild; fi
    +mkdir -pv rpmbuild/{BUILD,RPMS,SRPMS}
     cp -rfv git/packaging/rpm/* rpmbuild
    -cp -rfv svn/vote/apache-ignite-fabric-${ignite_version}-bin.zip 
rpmbuild/SOURCES/apache-ignite.zip
    +cp -rfv svn/vote/apache-ignite-fabric-${ignite_version}-bin.zip 
rpmbuild/SOURCES/
     rpmbuild -bb --define "_topdir $(pwd)/rpmbuild" 
rpmbuild/SPECS/apache-ignite.spec
    --- End diff --
    
    I thought we don't want to be a 'fabric' anymore.


> Update Apache Ignite's release scripts to match new RPM build and deploy 
> architecture
> -------------------------------------------------------------------------------------
>
>                 Key: IGNITE-8172
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8172
>             Project: Ignite
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 2.4
>            Reporter: Peter Ivanov
>            Assignee: Peter Ivanov
>            Priority: Critical
>             Fix For: 2.5
>
>
> # Implement new multi-package build scheme for RPM packages.
> # Update release process: deploy RPM packages to {{ignite-rpm}} Bintray 
> repository (with removal from Apache's Development Distribution SVN) instead 
> of moving to ASF's release.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to