If you turn on debug logging for the package
"org.apache.nifi.registry.provider.flow.git" then you should see a message
like this:
logger.debug("Took a push request sent at {} to {}...",
offeredTimestamp, remoteToPush);
If it fails to push then:
logger.error(format("Failed to push commits to %s due to %s",
remoteToPush, e), e);
On Fri, Mar 13, 2020 at 12:54 PM Wyllys Ingersoll <
[email protected]> wrote:
>
> Yes, its set to "origin", and origin is defined in the .git/config file to
> be an upstream repo with HTTPS.
>
>
> On Fri, Mar 13, 2020 at 12:50 PM Bryan Bende <[email protected]> wrote:
>
>> Did you specify the remote to push to in the configuration of the
>> provider?
>>
>> <property name="Remote To Push"></property>
>>
>> On Fri, Mar 13, 2020 at 12:40 PM Wyllys Ingersoll <
>> [email protected]> wrote:
>>
>>>
>>> Using: NiFi 1.11.3, NiFi-Registry: 1.5.0
>>>
>>> I have configured my registry to use the git provider and it is
>>> initialized and seems to be working fine with my nifi configuration - i.e.
>>> flow versions are being recorded as expected and things are working as far
>>> as I can tell.
>>>
>>> The problem is that my nifi-registry git configuration has an upstream
>>> origin to an external git server, but the nifi-registry is not pushing
>>> changes upstream, so the main gitlab server never sees any changes to the
>>> nifi registry repository. I see no errors or messages in the nifi-registry
>>> logs indicating that it is even trying to push.
>>>
>>> Is this a known bug? Am I misconfigured?
>>>
>>> thanks,
>>> Wyllys Ingersoll
>>>
>>>
>>>
>>>
