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

Upload image tar to release assets as part of pipeline #168

Open
4 tasks
orenbm opened this issue Sep 22, 2020 · 2 comments
Open
4 tasks

Upload image tar to release assets as part of pipeline #168

orenbm opened this issue Sep 22, 2020 · 2 comments

Comments

@orenbm
Copy link
Member

orenbm commented Sep 22, 2020

We would like to have a tar of the relevant docker image in the github release page. We have it for this release. In this case, we did it manually by running locally:

docker pull cyberark/conjur-authn-k8s-client:0.18.1
docker save -o conjur-authn-k8s-client-0.18.1.tar cyberark/conjur-authn-k8s-client:0.18.1

and manually uploading the tar to the release page.

We would like this to happen automatically once we push a new tag and release it. This can be done by running the steps above in the Jenkins pipeline and archiving the artifact. We can also look into this github action to perform this.

DoD:

  • image tar is automatically uploaded to release pages
  • Process is documented (if needed)
  • A list of projects that can do the same process is created
    • PRs are created for those projects to perform the same action
@orenbm orenbm added this to the R&D Boost milestone Sep 22, 2020
@orenbm orenbm self-assigned this Sep 22, 2020
@sigalsax
Copy link
Contributor

sigalsax commented Sep 23, 2020

@orenbm why was a tar of the client uploaded to the release of the SP? is that a requirement? Shouldnt the tar be of the Secrets Provider no the client?

@orenbm
Copy link
Member Author

orenbm commented Sep 23, 2020

it was done by mistake, thanks for seeing this! I removed it from the SP release and will upload it to the authn-client release

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

No branches or pull requests

3 participants