Re: auto updating job's nextBuildNumber after restoring build history from another controller?

A better way to reset all nextBuildNumber files after restoring build history is to delete all of them and restart Jenkins. Jenkins seems to recreate the files for every job based on the most recent build detected in the history. On Saturday, June 26, 2021 at 12:41:07 PM UTC-7 Tim Black wrote

Re: auto updating job's nextBuildNumber after restoring build history from another controller?

ctually trigger the next (correct) build number. Anyone know of a better way to implement this? On Saturday, June 26, 2021 at 12:07:30 PM UTC-7 Tim Black wrote: > Is there a way to make Jenkins automatically detect the latest build from > the history and automatically upda

auto updating job's nextBuildNumber after restoring build history from another controller?

Is there a way to make Jenkins automatically detect the latest build from the history and automatically update the nextBuildNumber file? We are using the "jenkins.model.Jenkins.buildsDir" system property to separate jobs/ from

Re: Default Admin API Token

Daniel Beck, as I commented on the related closed jenkins issue , I can't understand the usefulness of this feature for automated installs,

Re: Move location of build history, separate from config

I'm curious, now that this config setting is gone, and now there is the "jenkins.model.Jenkins.buildsDir" system property , are you now using that to separate your jobs/ from your builds/? We're using Jenkins CasC to manage all

Re: Efficiently copying artifacts

or any project type and safer because it doesn't need to use any core or plug in classes. On Monday, March 1, 2021 at 1:43:02 PM UTC-8 Tim Black wrote: > I'm trying to do same, but in both directions (archiving AND copying > artifacts from upstream). I wonder how the scp approach to copying

Re: Copy Artefact between master and slave node is very slow. (Windows Jenkins version 2.107.3)

or any project type and safer because it doesn't need to use any core or plug in classes. On Monday, March 1, 2021 at 1:53:46 PM UTC-8 Tim Black wrote: > Yes, archiving artifacts is very slow, this has apparently always been the > case with Jenkins - there are numerous jira issues that have c

Re: Copy Artefact between master and slave node is very slow. (Windows Jenkins version 2.107.3)

Yes, archiving artifacts is very slow, this has apparently always been the case with Jenkins - there are numerous jira issues that have come and been resolved without fixes to this. It is what it is.. As I commented here

Re: Efficiently copying artifacts

I'm trying to do same, but in both directions (archiving AND copying artifacts from upstream). I wonder how the scp approach to copying artifacts would work in multibranch pipelines? Can one deterministically construct the path to a branch job's artifact folder on the controller's disk? As I

Re: Can Jenkins redirect HTTP requests to HTTPS?

Owen, did your assertion turn out to be true? Is a reverse proxy required to perform this redirection of jenkins requests from http (80,8080) to https (port 8443)? I'm currently using iptables to forward 443 to 8443 to allow my users to not require a port in the URL, however, this does still

Re: How do you set java options for ssh agents

un a Jenkins Docker container configured with >>> JCasC (e.g. >>> https://github.com/kuisathaverat/jenkins-issues/tree/master/JENKINS-63703) >>> then connect to the container and modify the JENKINS_HOME/jenkins.yaml file >>> and restart from UI or CLI, the J

Re: How do you set java options for ssh agents

er and start it again the changes are applied. > > El vie., 25 sept. 2020 a las 17:33, Tim Black () > escribió: > >> Thanks. What's the difference between "restart Jenkins from UI" and "stop >> the Jenkins instance and start it again"? In the latter

Re: How do you set java options for ssh agents

es, then we will know if it is an issue or not, in any case >> is weird. >> >> El El mié, 23 sept 2020 a las 22:10, Tim Black >> escribió: >> >>> More info: In my case, a reboot is definitely needed. A >>> disconnect/reconnect does not suffice, nor doe

Re: How do you set java options for ssh agents

Thanks for your help in diagnosing these behaviors. kuisathaverat, let me know if any of this feels like a bug in ssh-slaves-plugin or configuration-as-code-plugin. On Wednesday, September 23, 2020 at 12:01:39 PM UTC-7 Tim Black wrote: > Thanks everyone, it's working now (see below for det

Re: How do you set java options for ssh agents

Thanks everyone, it's working now (see below for details). kuisathaverat, these agents have 96GB total RAM. Thanks for the explanation. Our builds are very RAM intensive, and I misunderstood that the builds happened within the remoting java process. Sounds like you're saying in this case

How do you set java options for ssh agents

I'm using ssh-slaves-plugin to configure and launch 2 ssh agents, and I've specified several java options in these agents' config (see photo and text list below), but when these agents are launched, the agents' log still shows empty jvmOptions in

Re: how to build on branch creation but not build on other scm event/commit?

Thanks Jeremy. Our developers already have control of their projects' branches' Jenkinsfiles so they can define whatever triggers/schedule they want. If I were going to hack this, I'd probably prefer to do the opposite of what you're recommending. Since git scanning is a wheel already invented

how to build on branch creation but not build on other scm event/commit?

1. I have a multibranch pipeline job that takes 30min to run, has a lot of branches, and my company is still at the earlier stages of devops transformation, so with our current infrastructure we do not want to trigger a build every commit. 2. Our job pipeline uses parameters heavily, so I

WebSocket Agents and Archiving Artifacts Performance

tation JSCH). The java ssh just can't get anywhere near 1Gb/s network speed that native SSH can manage easily" So, I was just wondering if WebSocket Agents might perform better at archiving artifacts bc they are implemented so differently. Thanks, Tim Black -- You received this message because yo

Re: why does multibranch pipeline fetch branch source 3 times?

Do I have control over when and how those are going to occur? E.g. how can I make the subsequent checkout/fetch/clone operations use `--tags` instead of `--no-tags`? On Tuesday, December 17, 2019 at 7:54:13 AM UTC-8, Mark Waite wrote: > > > > On Tue, Dec 17, 2019 at 7:45 AM Tim Black &

Re: why does multibranch pipeline fetch branch source 3 times?

.slideshare.net/markewaite/git-for-jenkins-faster-and-better for > slides that I presented at Jenkins World 2019 on those alternatives. Refer > to > https://support.cloudbees.com/hc/en-us/articles/115001728812-Using-a-Git-reference-repository > for > a deeper dive in

why does multibranch pipeline fetch branch source 3 times?

Is there ANY multibranch pipeline configuration that would allow me to: * place a Jenkinsfile at single BranchSource repo root, and * perform A SINGLE FETCH of this repo, full stop, and * fetch --tags in this single fetch, and * all of the above works when either "WipeWorkspace" or

Re: What compression algorithm is used by the pipeline zip step, and is it tunable?

independent > from jenkins (S3, maven-style repo, whatever matches your use-case). > > > Björn > > Am Montag, 2. Dezember 2019 20:56:02 UTC+1 schrieb Tim Black: >> >> Our projects produce large artifacts that now need to be compressed, and >> I'm considering

What compression algorithm is used by the pipeline zip step, and is it tunable?

not depend on another plugin. If neither of the above work, I'll simply use sh step to call xz, gzip, bzip, or the like, from my linux-based master. Thanks for your consideration, Tim Black -- You received this message because you are subscribed to the Google Groups "Jenkins Users"

Re: Do you really have to use multi-branch pipeline to do pipeline as code?

ins.io/blog/2017/08/08/introducing-jenkins-minute/>" video > series. Self-paced courses are available from CloudBees, Udemy, and other > online course systems. Jenkins Pipeline Fundamentals > <https://standard.cbu.cloudbees.com/cloudbees-university-jenkins-pipeline

Re: Do you really have to use multi-branch pipeline to do pipeline as code?

Thanks Mark. Of course you're correct. My main problem and point to make here (and with Jenkins ecosystem in general) is that the documentation says you have to use multi-branch pipeline to use pipeline as code, whereas this is patently false. I see in my freestyle pipeline job configuration

Do you really have to use multi-branch pipeline to do pipeline as code?

Just double checking this, at the below link it says the only way to use pipeline as code is to use the multi Branch pipeline configuration. Is this really true? https://jenkins.io/doc/book/pipeline-as-code/ I thought perhaps there was a way to configure a job that doesn't monitor for

Re: problems changing triggers{} in multibranch pipeline Jenkinsfile

Thanks Bjorn for helping clarify that. I would take what you said a step further by changing "could" to "must", since it appears that simply adding a trigger back into a Jenkinsfile for a job that has run since the trigger was removed, will necessarily have no effect until you manually run the

Re: Anyway to programatically update a Jenkinsfile?

I have to agree with Jeremy on this. Using a templating engine like m4 or jinja2 is superior to programmatic generation of groovy, if you need to do it on the fly. Why? Simplicity and Readability. I inherited a build system that is based on using a multibranch pipeline with a Jenkinsfile that

stash/unstash file size limit and performance

The Jenkins documentation for the stash pipeline step says that it's only to be used for "small files", with no explanation why. Specifically, how is stash bad for large, i.e. not

problems changing triggers{} in multibranch pipeline Jenkinsfile

We have a multibranch pipeline job set up to scan a git repo (which contains Jenkinsfile at its root) for branches and create branch-specific jobs for each branch discovered. The Jenkinsfile on a branch specifies: triggers { cron('@midnight') } and this indeed runs nightly at