-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add release automation #234
Conversation
b6bfbf2
to
9094bc9
Compare
5c2ee4b
to
cd7b53e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be good to see a test of the package/release stages, maybe comment out then when
clause for a test?
I missed this build which does test the package stage: jenkins.conjur.net/blue/organizations/jenkins/cyberark--secrets-provider-for-k8s/detail/automate-release/31/pipeline/39
stage('Push Images') { | ||
steps { | ||
script { | ||
BRANCH_NAME=env.BRANCH_NAME |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what this for, may as well use ${env.BRANCH_NAME} on L102?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I need the BRANCH_NAME inside publish to determine when to push our edge tag. We want to only push when on master so I need the BRANCH_NAME=env.BRANCH_NAME
from the script and output the result. I tried via scripts but I would also get HEAD instead of the actual branch
795a6d8
to
6d36e08
Compare
6d36e08
to
720d6f0
Compare
CONTRIBUTING.md
Outdated
@@ -210,6 +203,14 @@ follow the instructions in this section. | |||
1. Push the tag: `git push vx.y.z` (or `git push origin vx.y.z` if you are working | |||
from your local machine). | |||
|
|||
### Push Helm package | |||
1. The tagged build will package the Secrets Provider Helm chart for us. The package will appear under the 'Artifacts' tab of the Jenkins build and will resemble `secrets-provider-<version>.tgz`. | |||
Save this file you will need it for the next step. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
comma is missing i think.
Save this file , you will need it for the next step.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great catch! I added a "because"
@@ -43,4 +43,8 @@ if [ "$GIT_DESCRIPTION" = "v${VERSION}" ]; then | |||
echo 'Failed to log in to scan.connect.redhat.com' | |||
exit 1 | |||
fi | |||
elif [ "$BRANCH_NAME" = "master" ]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its not relevant for redhat registry?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point but I don't think so. I don't know if we would want to be pushing edge tags to RH because the publishing of tags is not an automated process. Our current policy for RH registry is that someone needs to push "publish" for tags to be public facing
142188c
to
527e185
Compare
3bd1b15
to
c3c659a
Compare
ci/jenkins_build
Outdated
-v $PWD/helm/secrets-provider:/root/helm/secrets-provider \ | ||
-v $PWD/helm-artifacts/:/root/helm-artifacts \ | ||
--workdir /root/helm-artifacts \ | ||
alpine/helm:${helm_version} package ../helm/secrets-provider |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need to align
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be fixed now
c3c659a
to
351e459
Compare
e99eb6f
to
5a4800a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, well done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Make CONJUR_APPLIANCE_IMAGE tag configurable Add release automation - Package helm chart on every build - Add ability to push an edge tag on every master build - Update tag and release process in docs
5a4800a
to
e8ab473
Compare
Code Climate has analyzed commit e8ab473 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 87.5% (0.0% change). View more on Code Climate. |
-v $PWD/helm/secrets-provider:/root/helm/secrets-provider \ | ||
-v $PWD/helm-artifacts/:/root/helm-artifacts \ | ||
--workdir /root/helm-artifacts \ | ||
alpine/helm:${helm_version} package ../helm/secrets-provider |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that's the stuff!
😉
This PR is part of a bigger effort in automating our release process
See generated helm package here: https://jenkins.conjur.net/blue/organizations/jenkins/cyberark--secrets-provider-for-k8s/detail/automate-release/31/artifacts
What ticket does this PR close?
Connected to #233
Checklists
Change log
Test coverage
Documentation
README
s) were updated in this PR, and/or there is a follow-on issue to update docs, or