Hi Patrick,
Yes that is exactly the same behaviour that I am seeing. I will add my
comments there. Do you have an ETA when we can expect this to get resolved?
Its a major blocking issue for us proceed with our automation efforts.
My company also has a dedicated cloudbees support channel. Will i
Can you confirm if this is the same behavior you are seeing?
https://issues.jenkins-ci.org/browse/JENKINS-34563
If so, add your comments here so we can track all of it.
On Wed, Aug 17, 2016 at 11:21 AM, Harsha Adiga
wrote:
> Hi Patrick,
>
> Any updates on this query? Do you need any more infor
Hi Patrick,
Any updates on this query? Do you need any more information from me?
Regards,
Harsha
On Monday, 15 August 2016 17:03:54 UTC-4, Harsha Adiga wrote:
>
> I think yes Jenkins is receiving the event. I can see the below line in
> System Logs:
>
> Aug 15, 2016 4:17:13 PM INFO
> org.jenki
Do you know if the Push Event webhook is received by Jenkins when you
create the Jenkinsfile?
"Does the plugin expect the repo to have a Jenkinsfile at the time of
creation itself?"
Just the opposite. The plugin expects the repo to be empty at the time of
creation unless the repo is created by a
Hi Patrick,
Thanks for the quick reply. Yes I am creating an empty repository without
Jenkinsfile at first and then adding the Jenkins file as a new file commit.
I was expecting my job to get triggered at this point when I add the
Jenkinsfile. But it is not doing that. Am I missing something he
How are you creating the Jenkinsfile? When a new repository is created the
repository trigger will be sent but the Github Organization Folder plugin
won't do anything at that point because it assumes the repository is empty.
If the repository is created from a fork and a Jenkinsfile is already the
I am doing a POC using GitHub Organization Folder plugin. I have created a
job selecting Git Hub Organization as the type. I have configured it to
scan my org using the personal access token that I have generated in my
Github account. I am using my Enterprise Git hub. I have also created a
we
