On Tue, Jun 20, 2017 at 8:50 AM Tristan FAURE <faure.tris...@gmail.com>
wrote:
> Yes my network topology is special and that's why i'm a little confused
> about how to manage this.
>
> You are right about the incremental aspects of Git, and unfortunately I
> can't have ssh between my two networks :(
>
>
The stash and unstash technique should work, since it is copying the
directories you request. If you don't need the history (only the files),
you could avoid copying the ".git" directory to reduce some of the load on
the network.
Mark Waite
>
> Le mardi 20 juin 2017 16:33:44 UTC+2, Mark Waite a écrit :
>
>> I don't fully understand the network topology you're describing. Are
>> network A and network B only able to communicate with one another through
>> the Jenkins server (and not by any other means)? If so, that surprises me,
>> since only allowing Jenkins between the two networks seems like a lot of
>> work without much gain.
>>
>> If you're willing to allow Jenkins to communicate between network A and
>> network B, why not allow ssh or https communication between network A and
>> network B so that a git clone could be performed between the networks?
>>
>> In general, I think you'll be better served by having git perform your
>> fetch rather than using the Jenkins stash mechanism. Git fetch is aware of
>> the repository structure and performs incremental updates from within git.
>> I'm not sure that the Jenkins stash mechanism uses incremental updates
>> (yet).
>>
>> Mark Waite
>>
>> On Tue, Jun 20, 2017 at 2:18 AM Tristan FAURE <faure....@gmail.com>
>> wrote:
>>
> Hello
>>> I would like to know your opinion about my issue.
>>>
>>> I have a network A with my git repository
>>>
>>> I have a network B with my build environment
>>>
>>> network B can't see A and A can't see B
>>>
>>> I have a network bridge between them
>>>
>>> does it make sense to you to have something like that :
>>> jenkins master in network bridge
>>>
>>> node ('network A') {
>>> git fetch
>>> stash source
>>> }
>>>
>>> node ('network B') {
>>> unstash
>>> build
>>> }
>>>
>>> or do you see a better solution ?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to jenkinsci-use...@googlegroups.com.
>>
>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/b96c9c3b-cb59-4894-abbf-deda9bd1bae1%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/b96c9c3b-cb59-4894-abbf-deda9bd1bae1%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/b193e2a2-a87e-4d02-9dcd-979a7b2acf47%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/b193e2a2-a87e-4d02-9dcd-979a7b2acf47%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGoGdkVSW8oG1_pjygdOxK3KmY9cFofpqMKeMpVpoqaOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
