configuring multibranchPipelineJob with JobDSL plugin

I'm getting lost in the mixed documentation on how to manage the configuration of a multibranchPipelineJob with the Job DSL plugin. Creating the job itself is straight forward, but when trying to recreate the Branch Sources for github as is possible in the UI, I'm not sure which patterns to fol

Re: configuring multibranchPipelineJob with JobDSL plugin

I've cross posted in the https://groups.google.com/forum/#!forum/job-dsl-plugin email list, as it seems like a better place for this discussion *(sorry, didn't know it existed beforehand)* On Wednesday, 3 April 2019 17:38:19 UTC+2, j.k...@travelaudience.com wrote: > > I'm getting lost in the m

github quota limit when scanning with the addition of tags

Now that we've added *Discover tags*[1 ] and a *Build everything*[2 ] strategy, we're running into Github quota limits quite frequently. 18:58:09 GitHu

Re: github quota limit when scanning with the addition of tags

> > There are only two good reasons to scan periodically: > 1. To recover from missed events (keep in mind that follow-up commits will > typically recover anyway, so the only case here is a commit before bedtime > not being built by morning because that event was not delivered by GitHub) > >From

Re: github quota limit when scanning with the addition of tags

@Stephen You mention that caching the responses would "save about 50% of the requests." That seems like a significant savings to me. I'm also wondering, I'm seeing a lot of things like this in the scan log: Checking tag v0.28.1 ‘Jen

Re: github quota limit when scanning with the addition of tags

I do want tags. I want tags very much. I'm very happy this feature is finally available. There just happens to be some tags in that repo that reference commits in which no Jenkinsfile exists, and I happened to copy those examples. Here is a better example: Checking tag v1.1.0

Re: github quota limit when scanning with the addition of tags

Ok, than I think I misunderstand what the scan is doing. During the scan, Jenkins creates a list in memory of all branches, tags, PRs. It does it from a single api call? Or from an api call for each type? And then while iterating over that list, for each entity Jenkins makes an api call to get t

reporting status back to Github, before using `input`

I think I have a request for something that is not possible, but I thought I'd ask anyhow. Here's the current scenario: We're using Github multibranch/organization so that every branch in every repo that has a Jenkinsfile gets built with CI. When the build completes, Jenkins reports the statu

Re: reporting status back to Github, before using `input`

I think I answered my own question in finding a plugin to do this: https://plugins.jenkins.io/pipeline-githubnotify-step On Friday, 6 April 2018 14:00:57 UTC+2, j.kn...@travelaudience.com wrote: > > I think I have a request for something that is not possible, but I thought > I'd ask anyhow. >

Jenkins master freezing up with k8s plugin

We're having a significant issue with our Jenkins env. Our Jenkins setup is running in Kubernetes, and sometimes the master is no longer able to provision new nodes, and the existing nodes don't disconnect. We're using 1.10.1 of Kubernets plugin, and Jenkins version is 2.121.2, and running in

Re: github quota limit when scanning with the addition of tags

I've started looking into this issue again. It's been an ongoing problem, that only continues to get worse over time. We're using the basic-branch-build-strategies-plugin at the moment, which provides an option for not building tags older than a week. But this option provides no value in limiti

Re: [hard] problem building github tags

I've got version 2.2.4 of GitHub Branch Source Plugin installed, and compiled, installed, and configured my organization folder to use https://github.com/AngryBytes/jenkins-build-everything-strategy-plugin which uses: @Override public boolean isAutomaticBuild(SCMSource source, SCMHead hea

Re: [hard] problem building github tags

hmm, I checked out your branch: https://github.com/stephenc/github-branch-source-plugin/tree/jenkins-34395 compiled and installed: 2.2.5-SNAPSHOT (private-e98acfa4-root) but still not seeing any tags built On Wednesday, 1 November 2017 16:54:22 UTC+1, Stephen Connolly wrote: > > 2.2.4 does not h

Re: [hard] problem building github tags

ah, well that explains it :) I should have paid more attention that the PR is still open https://github.com/jenkinsci/github-branch-source-plugin/pull/158/ On Wednesday, 1 November 2017 16:54:22 UTC+1, Stephen Connolly wrote: > > 2.2.4 does not have discovery of tags merged yet > > On 1 Novembe