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

Add a field for entering code signing identity #6

Merged
merged 2 commits into from Apr 5, 2012

Conversation

@katzj
Copy link

@katzj katzj commented Apr 5, 2012

Code signing identities are often something you'd want
to specify differently for an automated build (eg, so your
developers can just have developer certs but jenkins can
set up for distributing builds)

Code signing identities are often something you'd want
to specify differently for an automated build (eg, so your
developers can just have developer certs but jenkins can
set up for distributing builds)
@@ -389,6 +394,14 @@ public boolean perform(AbstractBuild build, Launcher launcher, BuildListener lis
xcodeReport.append(", configurationBuildDir: DEFAULT");
}

// handle code signing identities
if (!StringUtils.isEmpty(codeSigningIdentity)) {
commandLine.add("CODE_SIGN_IDENTITY=" + codeSigningIdentity);
Copy link
Member

@aheritier aheritier Apr 5, 2012

Choose a reason for hiding this comment

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

Your fix might also help to fix this one : https://issues.jenkins-ci.org/browse/JENKINS-12800
But I'm not sure that it works if you have a space in codeSigningIdentity
Did you try it ?

Copy link
Author

@katzj katzj Apr 5, 2012

Choose a reason for hiding this comment

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

In fact it does. It's not really the best fix (as there are other options) but that's actually what led me here. I took a few stabs at the regex and decided that this was a quicker path to something working ;-)

@aheritier
Copy link
Member

@aheritier aheritier commented Apr 5, 2012

Can you provide an help file also to document this new configuration field ??

@stephenc
Copy link
Member

@stephenc stephenc commented Apr 5, 2012

What would be really cool is if the code signing identity data was stored using the credentials plugin and then transferred to the build slave when needed

@katzj
Copy link
Author

@katzj katzj commented Apr 5, 2012

@aheritier yep, will add and update the pull request this morning.

@stephenc they have to be pulled from the os/x keychain so I'm not sure of any way to actually export/import in an automated fashion

@aheritier
Copy link
Member

@aheritier aheritier commented Apr 5, 2012

I forgot the other pull request which I think was to solve the same issue. --sign and CODE_SIGN_IDENTITY have the same behavior no ?
Otherwise you pull-request seems ok, I will test it and merge it

@katzj
Copy link
Author

@katzj katzj commented Apr 5, 2012

There is actually a slight difference from my understanding.

CODE_SIGN_IDENTITY has to do with how the .app gets signed. --sign is instead how the packaged .ipa is signed. The two can be different in some cases from what I understand

@aheritier
Copy link
Member

@aheritier aheritier commented Apr 5, 2012

ok thus I'll keep the other, I'll have to study it more.

aheritier added a commit that referenced this issue Apr 5, 2012
Add a field for entering code signing identity
@aheritier aheritier merged commit 6af1b04 into jenkinsci:master Apr 5, 2012
@devguydavid
Copy link

@devguydavid devguydavid commented Oct 30, 2012

Any word on when a new release will be made with this feature in place?

@pyby
Copy link

@pyby pyby commented Apr 5, 2013

Any news for a release? I searched this feature on the web

@lacostej
Copy link
Member

@lacostej lacostej commented Apr 5, 2013

If people want to test the latest build and report.

I am unable to deploy to our prod server right now. We are at the end of
our release cycle.

Should be able in a week or two.

Jerome

On Fri, Apr 5, 2013 at 2:54 PM, Pierre-Yves Bertholon <
notifications@github.com> wrote:

Any news for a release? I searched this feature on the web


Reply to this email directly or view it on GitHubhttps://github.com//pull/6#issuecomment-15953981
.

Jerome Lacoste, +47 40867729, We Want To Know

@fwal
Copy link

@fwal fwal commented Apr 17, 2013

Any updates? Sadly this is a deal-breaker for me...

@lacostej
Copy link
Member

@lacostej lacostej commented Apr 17, 2013

Have you guys tested the latest build ?

If nobody helps me testing the latest HEAD build on a production server, then you have to wait for me to test it :) As said above, I am in the end of a release cycle and will have time in a few days.

@fwal
Copy link

@fwal fwal commented Apr 17, 2013

Cool. :) I'll test it on our server now...

@fwal
Copy link

@fwal fwal commented Apr 17, 2013

Works perfectly for me!

@aphex3k
Copy link

@aphex3k aphex3k commented Mar 11, 2016

If I change the Code Signing Identity to V38B2WC56E Jenkins fails the build and according to the log /usr/bin/security find-certificate -a -c V38B2WC56E -Z | grep ^SHA-1 comes back empty. But if I log in on the box and run it in the command line I get

buildagent:~ buildagent$ /usr/bin/security find-certificate -a -c V38B2WC56E -Z | grep ^SHA-1
SHA-1 hash: 02F5D4FCD16E7EAD62EF141382F2C05BCD7F28E6

Any ideas?

@gevertex
Copy link

@gevertex gevertex commented Nov 10, 2016

Use the name of the signing identity instead ;-)

odra added a commit to odra/xcode-plugin that referenced this issue Nov 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
9 participants