[
https://issues.apache.org/jira/browse/IGNITE-15860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489632#comment-17489632
]
Maxim Muzafarov commented on IGNITE-15860:
------------------------------------------
I think prior to this task the following must be prepared in the
ignite-extension repository:
- create the release guide .md file describing the release process of an Ignite
extension (e.g. create a new branch for extension, change the version from a
snapshot to the release one in this branch, build a project using mvn);
- add release scripts (e.g. maven assembly plugin) which will prepare binary,
sources packages for the module being released (assume that the source package
of the releases module contains only sources of this module);
- add scripts that will sign binary and sources using the release manager
credentials (e.g. maven sign plugin);
- add scripts that will deploy artefacts to the maven staging repository;
- add scripts for checking checksums, gpg;
> [Extensions] Automated RC preparation and testing at Apache TeamCity
> --------------------------------------------------------------------
>
> Key: IGNITE-15860
> URL: https://issues.apache.org/jira/browse/IGNITE-15860
> Project: Ignite
> Issue Type: Task
> Reporter: Amelchev Nikita
> Assignee: Petr Ivanov
> Priority: Major
> Labels: ise
>
> Implement automated ignite-extensions RC preparation and testing at Apache
> TeamCity.
> The script should support:
> - binary releases
> - proper source package without not-releasing modules, dev-scripts, gitignore
> - several modules release
> - different modules versions
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
