Re: In a shared library, what is the "vars/foo.txt" file USED for?

The .txt file shows up on the PipelineSyntax/Global Variables Reference page. On Sunday, February 5, 2017 at 6:33:03 PM UTC-7, David Karr wrote: > > So I now have a handful of pipeline scripts all reusing some global > methods, all of which I pasted into each script, so I've started to set up

Re: Github Organization Plugin - Multiple Jenkins File

I agree with this answer. With a pipeline, it is so easy to make logic decisions and much easier to maintain a single Jenkinsfile that has all the logic. There is surely going to be some duplicated logic, so now only the special differences have to be handled, and you don't duplicate code

Remote client doesn't restart after boot

I have a situation where Jenkins starts a job on a remote test machine, and as part of the test, the system must boot into an operating system that cannot have networking, well, working. The test machine runs some stuff (15 minutes to hours or days (or even weeks), then boots back to Linux.

Re: In a shared library, what is the "vars/foo.txt" file USED for?

Any word on this? I'm assuming no one is actually using this feature and its going to be deprecated because there is like zero documentation about where this is actually supposed to show up in jenkins. Is it under "Global Variables Reference" or "Step Reference"? I see my txt info no where and

Re: Username and Password to checkout git in Jenkinsfile (groovy)

I have got a solution. Pls see this link for details. Thanks. On Monday, 2 October 2017 15:13:20 UTC+11, Vikas Kumar wrote: > > Thanks Mark, yeah this is one option but in this

Re: Github Organization Plugin - Multiple Jenkins File

I think the most common solution is to have one Jenkinsfile (per branch), and manage everything from that. -- 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

Re: Github Organization Plugin - Multiple Jenkins File

I think you can have a "build" variable (https://jenkins.io/doc/pipeline/tour/environment/), or parameter (below), and use the value assigned to that. Using parameters in a Jenkinsfile. When this runs you will get an interactive window. pipeline { agent any parameters {

Re: Is there a way of cloning the repo an additional layer down?

> On 2. Oct 2017, at 21:13, dandeliondodgeball wrote: > > Assuming there is no simple generic solution, what is the best custom > solution? My first thought would be a script. > If this is a scripted pipeline, you can do dir('repo01code') { checkout scm }

Is there a way of cloning the repo an additional layer down?

Default: ../workspace/Pipeline01/ Desired: ../workspace/Pipeline01/repo01code/ Why do I want to do this? The scripts to build the code, can't live at the same level as the code. I can have the scripts live some place other then the Pipeline01 workspace, but then Jenkins doesn't "know" about

Github Organization Plugin - Multiple Jenkins File

Hi, I am new to Github. I am trying to use the Github Organization Plugin to set up my pipelines in Jenkins. I am able to get the corresponding pipelines per branch in Jenkins. What I do want to do is to set up multiple pipelines based off multiple JenkinsFile in one branch. For eg. I would have a

Re: Multi-branch pipeline without Jenkinsfile in the repo?

Hi, I´m also facing this scenario right now ! Currently I´ve just added a Jenkinsfile into each branch (it was *so hard and tedious* to change it and replicate over all branches =/) This workflow doesn't look very sustainable, so I´ll configure this standalone repo strategy, suggested by Mark,

How to prevent Jenkins from reconnecting to the slave after one or two attempts if slave is unreachable

I've just met some problem with slave creation. I need to create slave machines on demand, so I'm creating DumbSlave as follow: def createJenkinsNode() { def sshCredentials = settings['jenkins']['ssh_credentials'] SSHLauncher launcher = new SSHLauncher("10.1.1.10", 22,

How to start job via REST API and set "Started by upstream project"

Hi, when one jenkins job starts another, that job will have "Started by upstream project" in jobs page and console output. Is it possible to start job via REST API or jenkins-cli and set this information? -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: Can we install SonarQube and Jenkins on same machine(VM) ?

Your problem will be probably less the CPU/memory consumption than IOs consumption especially if you host your SonarQube database locally We generally advise to not host anything else than the Jenkins master on an host in production. Otherwise it is a nightmare to manage properly the resource

Re: Can we install SonarQube and Jenkins on same machine(VM) ?

Agree with Devin above, and would highly suggest against setting up the Master Jenkins server and Sonarqube together - I ran into scaling problems rather quickly (like within 6 months as people got wind of the Jenkins and Sonar servers). Migrating Jenkins is pretty easy though, so for the

Re: Why do some pipelines not let me view Workspace?

I doing this manually, no Jenkinsfiles are involved. -- 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-users+unsubscr...@googlegroups.com. To view

Re: Jenkins compatibility with subversion plugin

I will chip in since I am also using a very old Jenkins version, and suspect it might be a similar reason. My experience has shown that for our larger setup it is highly problematic to upgrade Jenkins. Every single time I upgraded I had to spend days on end trying to workaround bugs and new