Those fastlane actions do not connect to apple services, they expect those
developer files to be in the filesystem.
By credentials I mean a plugin that would enable us to "unwrap" it from a
pipeline function to be used by "sh" commands (fastlane being one example)
which is not possible today, it needs to be done from their java code only
which is a bit limited from a pipeline perspective.
On Fri, Sep 29, 2017 at 9:20 AM, Ali Ok <aliok(a)redhat.com> wrote:
Leonardo, it sounds really good! Using some other open source software for
very complex things would be great.
I have a question though: in my experiments (like ~10 months ago), I was
disappointed with FastLane connecting to Apple Developer console to get
some provision files. I was stuck there...
Is this really the case? Would it block anything?
On Fri, Sep 29, 2017 at 2:50 PM, Leigh Griffin <lgriffin(a)redhat.com>
> Big +1 for cross community contributions. Would be great to gain traction
> with fastlane and cross collaborate.
> This work is open to all Wojciech so any of our individual team members
> can get involved under the OSS banner. In fact it's something I would
> highly encourage.
> On 29 Sep 2017 11:50, "Wojciech Trocki" <wtrocki(a)redhat.com> wrote:
>> I'm huge enthusiast of fastline. Most of the IOS developers will use it
>> on daily basis. I'm no longer involved in the project but I think it will
>> make sense to use it as default codesign tool.
>> There are many ways to introduce it. If you need help with building
>> jenkins plugin I can help with contribution.
>> > I was thinking if we could create a jenkins plugin to properly handle
>> credentials using the "withCredentials" pipeline function
>> That's great idea! We may also share this on the fastlate github. They
>> have bigger community and it seems that this will be useful outside digger.
>> Work checking: https://github.com/fastlane/fastlane/blob/master/f
>> On Fri, Sep 29, 2017 at 11:09 AM, Leonardo Rossetti <lrossett(a)redhat.com
>> > wrote:
>>> I have created a PR against digger-jenkins with fastlane samples for
>>> both ios and android: https://github.com/ae
>>> You will notice that fastlane can replace both build and codesign logic
>>> from our Jenkinsfiles and this approach has some advantages:
>>> - easier to test it locally without jenkins (just run fastlane
>>> - more flexibility since it is just a couple of ruby scripts.
>>> - fastlane actions can be distributed as ruby gem packages in the
>>> - fastlane has several community plugins, which is easier to
>>> install within the jenkinsfile using the gem command if needed.
>>> Currently, we can't sign our binaries with fastlane because of how our
>>> plugins (android signing and xcode) handle jenkins certificates and
>>> developer profile files.
>>> I was thinking if we could create a jenkins plugin to properly handle
>>> credentials using the "withCredentials" pipeline function
>>> could keep the main build/sign logic in fastlane actions while we keep
>>> specific jenkins tasks such as handling credentials, archiving the
>>> artifact, etc in the jenkisfile.
>>> LEONARDO ROSSETTI
>>> SOFTWARE ENGINEER
>>> Red Hat SP <https://www.redhat.com/>
>>> lrossett(a)redhat.com M: 11997030621
>>> aerogear-dev mailing list
>> WOJCIECH TROCKI
>> Red Hat Mobile <https://www.redhat.com/>
>> IM: wtrocki
>> aerogear-dev mailing list
> aerogear-dev mailing list
aerogear-dev mailing list