Skip to content

Updates readme #45

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
snps-klibby wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Updates readme #45

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,16 @@ $ docker build -t blackducksoftware/bdio-tinkerpop-db bdio-tinkerpop-db/
$ docker run -d -e POSTGRES_HOST_AUTH_METHOD=trust -p 5432:5432 blackducksoftware/bdio-tinkerpop-db
$ ./gradlew build
````
## Release:
__As of 09-28-23:__
To release a version of bdio to artifactory for use by downstream dependencies:
Copy link
Collaborator

@vasharapov vasharapov Nov 3, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From my last experience, which happened on 11-03-2023, you actually should add -SNAPSHOT (if it is not already there). So, if you want to release 3.2.10, gradle properties should have 3.2.10-SNAPSHOT

1. Remove the `-SNAPSHOT` from `gradle.properties` and push the changes to `master`
2. Navigate to [the CI build](https://build-bd.internal.synopsys.com/job/Common%20Components/job/BDIO/job/CI/) and run the pipeline once the changes are pushed
3. Once the CI build completes, navigate to the [nightly RC](https://build-bd.internal.synopsys.com/job/Common%20Components/job/BDIO/job/Nightly%20RC/) and run the pipeline
4. After some time, look at the console output for the latest run and you should see a couple of links in the logs that say `Proceed` or `Abort`
5. Press `Proceed` to deploy the release to artificatory and it's ready for consumption by downstream dependencies. Note that it will automatically abort if you don't press `Proceed` within a couple minutes of the prompt appearing in the output.



## License

Expand Down