forked from hyperledger-labs/Scorex
-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #61 from HorizenOfficial/dev
2_0_1_final
- Loading branch information
Showing
13 changed files
with
237 additions
and
35 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,58 @@ | ||
# New version build functionality | ||
|
||
As of 2022/06/27 CI/CD pipeline adds functionality to build and publish multiple `DIGIT.DIGIT.DIGIT-SNAPSHOT` versions of `zendoo-sc-crypotolib` package | ||
with the help of set_version.sh script. | ||
|
||
`set_version.sh` script is located under **ci/devtools** directory and automates preparation steps for building/releasing a new | ||
version of the artifacts by setting the provided version for all the required dependencies across the configuration files. | ||
|
||
--- | ||
## Prerequisites for publishing a package: | ||
- Singed by GPG key commit and valid GitHub tag in the format of `DIGIT.DIGIT.DIGIT` or `DIGIT.DIGIT.DIGIT-SNAPSHOT` | ||
- GitHub tag matching `${pom_version_of_package}"[0-9]*$` regex | ||
- Your(a person who pushes a tag) GPG key being added to CI/CD pipeline build settings | ||
|
||
Otherwise, the build process will run without entering the publishing stage. | ||
|
||
`DIGIT.DIGIT.DIGIT-SNAPSHOT` package version can be built multiple times by adjusting GitHub tag name accordingly. For example: | ||
``` | ||
GitHub tag = 1.1.1-SNAPSHOT can build 1.1.1-SNAPSHOT package | ||
GitHub tag = 1.1.1-SNAPSHOT1 can build 1.1.1-SNAPSHOT package | ||
GitHub tag = 1.1.1-SNAPSHOT2 can build 1.1.1-SNAPSHOT package | ||
``` | ||
All SNAPSHOT packages are being pushed to a snapshot repository configured under pom.xml file: | ||
``` | ||
<snapshotRepository> | ||
<id>ossrh</id> | ||
<url>https://oss.sonatype.org/content/repositories/snapshots</url> | ||
</snapshotRepository> | ||
``` | ||
and can be referred to inside the configuration files by providing the full version, that can be found inside nexus [repository](https://oss.sonatype.org/content/repositories/snapshots/io/horizen/) | ||
|
||
--- | ||
## Usage | ||
Before starting the build process use `set_version.sh` script if needed by providing two arguments in the following format: | ||
``` | ||
./ci/devtools/set_version.sh --help | ||
Usage: Provide OLD and NEW versions as the 1st and 2nd arguments respectively. | ||
It has to match the following format: | ||
DIGIT.DIGIT.DIGIT or DIGIT.DIGIT.DIGIT-SNAPSHOT | ||
For example: | ||
./set_version.sh 5.5.5 5.5.5-SNAPSHOT | ||
./set_version.sh 5.5.5-SNAPSHOT 5.5.5 | ||
``` | ||
| Changes made by set_version.sh script need to be committed before the build. | | ||
|------------------------------------------------------------------------------| | ||
|
||
--- | ||
## How to refer | ||
- Find all the existing versions of [2.0.1-SNAPSHOT package](https://oss.sonatype.org/content/repositories/snapshots/io/horizen/sparkz-core_2.13/2.0.1-SNAPSHOT/) | ||
- Use the full version of SNAPSHOT package as a dependency in the following format for your project. | ||
``` | ||
<dependency> | ||
<groupId>io.horizen</groupId> | ||
<artifactId>sparkz-core_2.12</artifactId> | ||
<version>2.0.1-20230310.201529-1</version> | ||
</dependency> | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.