Create Cosigner Attachment with airSlate SignNow

Decline e-sign cosigner

container image signing with cosine and jenkins [Music] one way to prove that an artifact was created by you is to sign that artifact in the past this process could be a little complex because the tooling around it wasn't very user friendly however there are tools today that greatly simplify this process in this video we're going to provide a short introduction how you can use cosine and jenkins together in order to create a simple container image signing and verification process here's today's starting point i have a jenkins lts controller it's version 2.319.1 attached to this controller i have a linux based agent and on that agent i have docker and cosign version 1.4.0 we have a sample repository for this video the link to that repository is down in the description now this video picks up where we left off where we were creating container images and pushing them to github container registry i'm assuming that you've watched that video but if you haven't the link to that is also down in the description let's take a quick look at our sample repository what we have is a docker file and a handful of different jenkins files that we're going to be walking our way through so first off what we want to do is go ahead and set up a job that is going to create our image and push it into github container registry now this job is the exact same job that we had at the end of the previous video so i'm going to go ahead and create a job called cosine sign pipeline click ok paste in my url for the scm which is right here we'll go ahead and do main and jenkins file dash one now if we're to take a look at jenkins file dash one we can see here that we've already got a github token set up so we can interact with github to push our image so we're doing a build a login a tag a push and then a log out so fairly straightforward container image build tag push process no big deal there so let's go and click on build now and let's see what happens if we take a look at the output of this job we're doing our build which will take just a moment now we do our tag we do our push and then finally we do our log out so if we come back over to github and click back on our repository what we now see here for in packages is we have the jenkins example cosign package and if you notice the tags that we have are just 85-204 which is the only tag that we have at this point so we've successfully created our image and pushed it to github now before we can get started actually signing our image we first have to set up some credentials for cosine and if we take a...