Github Branch Source Plugin not allowing individual folder configuration

[Yash Nalla]

Hi all,

The subject line kinda says it all. The documentation for Github Branch Source plugin: https://go.cloudbees.com/docs/plugins/github-branch-source/ says that users can go in and "configuring different settings on each of those folders[repositories] if needed." However when i navigate into any of these folders/or use the drop down I can only View Configuration rather than edit it. I believe this might be some sort of bug because many of the fields in the view configuration are editable and would make sense to be editable. 

Best,

Yash nalla

[Mark Waite]

I believe that it once was possible to modify the individual job definitions of a GitHub Branch Source folder.  However, I believe the modifications were also periodically reset (possibly by scanning for new changes or by detecting new branches).  I believe that the capability to edit individual job definitions was intentionally removed.

At least that has been my assumption.

--
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/6b0971fa-c016-4822-a4a2-15cf239d6392%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Yash Nalla]

I just went through the changelogs of the plugin and nothing like that is mentioned? Though if all the edits to job definitions were already being rolled back periodically I guess just removing that ability doesn't change anything in the long term.

On Monday, July 8, 2019 at 3:32:18 PM UTC-4, Mark Waite wrote:

I believe that it once was possible to modify the individual job definitions of a GitHub Branch Source folder.  However, I believe the modifications were also periodically reset (possibly by scanning for new changes or by detecting new branches).  I believe that the capability to edit individual job definitions was intentionally removed.

At least that has been my assumption.

On Mon, Jul 8, 2019 at 1:29 PM Yash Nalla <yna...@redhat.com> wrote:

Hi all,

The subject line kinda says it all. The documentation for Github Branch Source plugin: https://go.cloudbees.com/docs/plugins/github-branch-source/ says that users can go in and "configuring different settings on each of those folders[repositories] if needed." However when i navigate into any of these folders/or use the drop down I can only View Configuration rather than edit it. I believe this might be some sort of bug because many of the fields in the view configuration are editable and would make sense to be editable. 

Best,

Yash nalla

--
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 jenkins...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6b0971fa-c016-4822-a4a2-15cf239d6392%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Yash Nalla]

If my use case requires me to make changes to individual job definitions EX: the build path, does anyone have any suggestions on how to do so within a GitHub organization?

Best,

Yash Nalla

[Mark Waite]

I may also be completely wrong.  My recollection is only a poor memory, not anything that I verified by checking the behavior of past releases.  As far as I can tell, it is intentional that the jobs created by the GitHub Branch Source plugin cannot be reconfigured.

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/08a6e802-48ae-40d9-9e51-c4da190c40f2%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Mark Waite]

Wouldn't it be best to make the necessary changes inside the build scripts that are called from the Jenkinsfile?

--

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/9c307d05-ea7e-4805-a782-c0f163bd29f6%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Yash Nalla]

Due to security concerns I'd prefer to be able to edit the very location of the build Jenkinsfile; the project recognizer Jenkinsfile I would leave in the indivdual repo. I just want to be able to protect the Jenkinfile that actually controls my build.