Github branch source plugin: ignore archived repos

[Louis Piët]

Hi,

We are using the git hub branch source plug in to automatically discovery
most of our projects on github, this works like a charm, however we are
running into an issue with archived repos. These are read only and only
kept for reference/auditors, if they contain a Jenkisfile however, they
are still picked up by the plugin and processed as if live. As the
dependencies and such are all very stale this leads to failures and
unnecessary noise in our build reports. I can't find a way to tell the
plugin to ignore archived repos ( and couldn;t find an issue regarding this
in the jira either).

Am i overlooking an option? Is there a workaround i'm not seeing?

Thanks,

Louis

[Denis]

As a workaround you could rename the Jenkinsfile on those repositories to something like Jenkinsfile_ar

Post by Louis Piët
Hi,
We are using the git hub branch source plug in to automatically
discovery
most of our projects on github, this works like a charm, however we are
running into an issue with archived repos. These are read only and only
kept for reference/auditors, if they contain a Jenkisfile however, they
are still picked up by the plugin and processed as if live. As the
dependencies and such are all very stale this leads to failures and
unnecessary noise in our build reports. I can't find a way to tell the
plugin to ignore archived repos ( and couldn;t find an issue regarding this
in the jira either).
Am i overlooking an option? Is there a workaround i'm not seeing?
Thanks,
Louis
--
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
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/16099afc-7239-4faa-af56-85a14aacf815%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jan Monterrubio]

I assume you’re using something like an Organization Folder that’s scanning
those?

Post by Denis
As a workaround you could rename the Jenkinsfile on those repositories to
something like Jenkinsfile_ar
On October 18, 2018 10:48:41 AM GMT+03:00, "Louis Piët" <

Post by Louis Piët
Hi,
We are using the git hub branch source plug in to automatically discovery
most of our projects on github, this works like a charm, however we are
running into an issue with archived repos. These are read only and only
kept for reference/auditors, if they contain a Jenkisfile however, they
are still picked up by the plugin and processed as if live. As the
dependencies and such are all very stale this leads to failures and
unnecessary noise in our build reports. I can't find a way to tell the
plugin to ignore archived repos ( and couldn;t find an issue regarding this
in the jira either).
Am i overlooking an option? Is there a workaround i'm not seeing?
Thanks,
Louis

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
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
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/258EEE7D-E8EC-49C9-A24A-DB8EEFFDD02C%40gmail.com
<https://groups.google.com/d/msgid/jenkinsci-users/258EEE7D-E8EC-49C9-A24A-DB8EEFFDD02C%40gmail.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

[Baptiste Mathus]

If confirmed, that would definitely sound like a bug IMO.

Post by Jan Monterrubio
I assume you’re using something like an Organization Folder that’s
scanning those?

Post by Denis
As a workaround you could rename the Jenkinsfile on those repositories to
something like Jenkinsfile_ar
On October 18, 2018 10:48:41 AM GMT+03:00, "Louis Piët" <

Post by Louis Piët
Hi,
We are using the git hub branch source plug in to automatically
discovery most of our projects on github, this works like a charm, however
we are running into an issue with archived repos. These are read only and
only kept for reference/auditors, if they contain a Jenkisfile however,
they are still picked up by the plugin and processed as if live. As the
dependencies and such are all very stale this leads to failures and
unnecessary noise in our build reports. I can't find a way to tell the
plugin to ignore archived repos ( and couldn;t find an issue regarding this
in the jira either).
Am i overlooking an option? Is there a workaround i'm not seeing?
Thanks,
Louis

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
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
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/258EEE7D-E8EC-49C9-A24A-DB8EEFFDD02C%40gmail.com
<https://groups.google.com/d/msgid/jenkinsci-users/258EEE7D-E8EC-49C9-A24A-DB8EEFFDD02C%40gmail.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
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CADgiF9JYRuF9%3DE_CbvADzEJ1_C4-kA69nfEACC-nN42MY0s-Aw%40mail.gmail.com
<https://groups.google.com/d/msgid/jenkinsci-users/CADgiF9JYRuF9%3DE_CbvADzEJ1_C4-kA69nfEACC-nN42MY0s-Aw%40mail.gmail.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.