Skip to content
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.

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

Feature/issue 353 #382

Merged
merged 3 commits into from
Aug 14, 2022
Merged

Conversation

merry-degaga
Copy link
Contributor

@merry-degaga merry-degaga commented Aug 7, 2022

Fixes: 353

run: ./gradlew jib
run: |
./gradlew jib \
-Djib.to.tags='latest',$GITVERSION_SEMVER
Copy link
Member

Choose a reason for hiding this comment

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

what would be GITVERSION_SEMVER?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is an output from gitversion action. When gitverson is executed it provides a number of outputs (see here for full list) and semVer is one of them. It will contain the calculated version for a build (see here for example)

Copy link
Member

@preetkaran20 preetkaran20 Aug 12, 2022

Choose a reason for hiding this comment

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

ok got it. can you please add few sample outputs of GITVERSION_SEMVER?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yup, and add the sample outputs to the README as the examples?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sample outputs of GITVERSION_SEMVER on DockerHub :
image
image
image

@@ -20,9 +20,26 @@ jobs:
uses: actions/checkout@v2
with:
java-version: 1.8
fetch-depth: 0
-
name: Setup GitVersion action
Copy link
Member

Choose a reason for hiding this comment

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

can you please tell how will be mention Major and Minor? So we need to mention in PR name?

Copy link
Member

Choose a reason for hiding this comment

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

i read your comment and it seems like we need to mention in commit message.

Copy link
Member

Choose a reason for hiding this comment

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

can you please update the Readme with what we need to mention for major release and minor release? Also with example explain what is the impact of major release, minor release and Patch in the github tag and docker version ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ok will get this done

Copy link
Member

Choose a reason for hiding this comment

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

@merry-degaga I merged this PR and I see that it has done a github release for the project where as i was thinking that it will just update the github tag and we will do the release as per our will.
https://github.com/SasanLabs/VulnerableApp/releases

is there a way we can stop it to create a release? From release, I point it as a major change so we notify about it in multiple channels.

Copy link
Member

Choose a reason for hiding this comment

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

I deleted the release for now.

Copy link
Contributor Author

@merry-degaga merry-degaga Aug 14, 2022

Choose a reason for hiding this comment

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

Okay, I will take a look.

@merry-degaga please help with #382 (comment)

I will look into preventing auto-release creation.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was able to prevent auto-release creation.

Copy link
Member

@preetkaran20 preetkaran20 left a comment

Choose a reason for hiding this comment

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

LGTM. Great work @merry-degaga .

thanks,
Karan

@preetkaran20 preetkaran20 merged commit e27a18e into SasanLabs:master Aug 14, 2022
@preetkaran20
Copy link
Member

@merry-degaga please help with
#382 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Currently docker images are not versioned which can be an issue going further
2 participants