-
Improvement
-
Resolution: Unresolved
-
Minor
If I regenerate a provision profile and upload it to Jenkkins, jobs that used the original provisioning profile will break if I edit them and don't update the provisioning profile. The plugin appears to use filename and UUID to determine if the provisioning profile is a match, but should only use the filename.
[JENKINS-24976] Original FileName should be used to determine equality, not Filename + GUID.
Tom Jones
added a comment - I ended up having to write a ruby script that managed the adding of provisioning profiles, and updated the list of provisioning profiles. More importantly, it kept the list in alphabetical order, and allowed non-admins to update a provisioning profile. Unfortunately I don't have access to that source code anymore, but it was a fairly simple thing to do.
Tom Jones
added a comment - I ended up having to write a ruby script that managed the adding of provisioning profiles, and updated the list of provisioning profiles. More importantly, it kept the list in alphabetical order, and allowed non-admins to update a provisioning profile. Unfortunately I don't have access to that source code anymore, but it was a fairly simple thing to do. 
RG
added a comment - Hey Tom,
Thank you for your reply - glad to see you've managed to tackle this on your end.
I ended up using another approach: I've checked out the source and removed the "( UUID )" section of the string in the options dropdown element. Since the filename is the same in every update, the selected option remains valid in every job configuration.
Cheers
RG
added a comment - Hey Tom,
Thank you for your reply - glad to see you've managed to tackle this on your end.
I ended up using another approach: I've checked out the source and removed the "( UUID )" section of the string in the options dropdown element. Since the filename is the same in every update, the selected option remains valid in every job configuration.
Cheers Tom Jones
added a comment - That's great, my eclipse-foo was not strong enough to make that work, glad someone who knows what to do finally took interest. I'd recommend alphabetizing the list as well, larger organizations manage over 100 profiles, and searching through a non alphabetized list is a hassle. Also, some sort of indication that the profile expired would be great.
Tom Jones
added a comment - That's great, my eclipse-foo was not strong enough to make that work, glad someone who knows what to do finally took interest. I'd recommend alphabetizing the list as well, larger organizations manage over 100 profiles, and searching through a non alphabetized list is a hassle. Also, some sort of indication that the profile expired would be great. 
I'm sad to see this issue reported so long ago and not resolved yet...
For me this is a big show stopper.
I'm trying to centralize the provisioning profiles in Jenkins, but as it is, this means changing every job that uses a determined PP after updating it....