Re: Jenkins kubernetes Client

/ \ >> >> && echo "false" > >> /usr/share/jenkins/ref/secrets/slave-to-master-security-kill-switch >> >> >> >> # ENV VERSION 0.4-SNAPSHOT >> >> # COPY target/kubernetes.hpi /usr/share/jenkins/ref/plugins/kubernetes

Re: StackOverFlow with pipeline script

I checked that on Jenkins 2.32.2 I assume that: node { stage('Build') { echo 'Building..' } } works fine? My understanding is that the pipeline/agent is part of the new declarative extension of the pipeline DSL - that was only officially released in February, so maybe you're

Re: Parameterized Scheduler plugin: Jenkins doesn't accept extended syntax

you should see Build periodically with parameters https://github.com/jenkinsci/parameterized-scheduler-plugin/blob/master/README.md#configuration your screenshot implies you missed seeing this bit of important info: Warning: the plugin configuration is only visible for jobs with parameters.

Re: Jenkins kubernetes Client

I recently setup jenkins using the `kubernetes-plugin` and didn't have any issues like this. Where/when do you get this error? what's your kubernetes yaml file look like? On Thursday, March 30, 2017 at 6:30:52 AM UTC+2, Sudha Subramanian wrote: > > Hi, > > I'm trying to run Jenkins in

Re: How would you add 100 users to Jenkins ? Best practice please

first, you want to use the LDAP plugin (then you don't need to worry about user config in Jenkins) https://wiki.jenkins-ci.org/display/JENKINS/LDAP+Plugin for single sign-on, it'll be a bit more intricate configuration (maybe start googling: "Jenkins SSO" ) On Tuesday, April 18, 2017 at

Re: multibranch pipeline will not poll

without having the webhook, try changing the setting in the config: On Wednesday, April 19, 2017 at 7:29:44 AM UTC+2, Ferran Pujol Camins wrote: > > Thanks Stephen. > > Sure that's the goal, however, I run Jenkins locally on my laptop by now, > so I can't configure my git server to send

Re: podTemplate with GKE

Hi Philippe, As Carlos pointed out, have you already gone through the documentation on the kubernetes-plugin: https://github.com/jenkinsci/kubernetes-plugin ? What is shown there is enough to get you to a working state. The section in that doc about *Pod template inheritance* is a bit

Re: Writing a new "parser" for the warnings plugin.

This might not be too helpful, but have you looked at the other parsers that come with the plugin: https://github.com/jenkinsci/warnings-plugin/tree/master/src/main/java/hudson/plugins/warnings/parser a good start might be the LintParser.java On Wednesday, May 31, 2017 at 2:31:36 AM UTC+2,

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

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

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

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

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) >

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

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

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: 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. >

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

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

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

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

performance issues as kubernetes agent pods scale up

We have a build pipeline that dynamically scales up agents (with K8s plugin) to execute tests on. We've noticed that as the amount of agents scales up to 20 (or even over 50), the performance of each agent degrades. Each agent's resource usage is relatively low, but the requests are done in a