I try to make the calls in my top level jenkinsfile atomic and complete,
i.e. each one performs a single function. By using long, descriptive names
I can avoid the need for lots of comments. It also makes building new
pipelines easy and encourages reuse across files, stages and steps. If I
see
Hi,
this is my point of view only,but using a single script (that you put into your
repos make it easier to perform the build, I put my pipeline script into a
separated folder). But you need to make sure your script is verbose enough to
see where it has fail if anything goes wrong, sinlent and w
Hi,
from functional point of view there is no different ... but there are from
reporting point of view ... and that's a matter of taste :-)
1. In BlueOcean view, each "sh" invocation will be displayed separately
from the other steps and "sh" takes as parameter a name that BlueOcean will
use to
Dear all,
When a pipeline needs to run a sequence of several shell commands, I see
several ways of doing that.
1. Several "sh" invocations.
2. One "sh" invocation that contains all the commands.
3. Having each "sh" invocation in its own step.
4. Putting all the commands in a script and invokin
Dear all,
I am replying to myself because meanwhile I have solved my problem and
others might find the solution interesting, too.
Sébastien Hinderer (2020/08/10 17:39 +0200):
> Dear all,
>
> I am trying to switch from classical to pipeline jobs.
>
> One of my classical (legacy) jobs is triggere
Hi,
yes ... we do.
We have various Jenkinsfile in sub-directories and different pipelines.
This is how we did it:
- we have one Multibranch project for each Jenkinsfile and in the
configuration we specify which Jenkinsfile is used for the jobs
- we have a custom check that we use on the "when" b
Hello,
In one of our Git repository, we have a directory hierarchy similar to this:
dev/
Jenkinsfile
folder-1/Jenkinsfile
folder-2/Jenkinsfile
test/
Jenkinsfile
folder-3/Jenkinsfile
folder-4/Jenkinsfile
There are other files as well, in e
In declarative pipeline, is it possible to set 'reuseNode true' for a
non-Docker agent? If so, what is the syntax please?
The following did not work for me:
agent {
label "jenkins-ubuntu18-2"
reuseNode true
}
--
You received this me
Looks like only freestyle jobs are visible in the username/builds page.
Pipeline jobs not visible. Is there any other way to get pipeline jobs
started by a user?
On Monday, August 10, 2020 at 8:27:41 PM UTC+5:30, Shashank V wrote:
>
> Hi,
>
> Is there a REST API endpoint to get all builds starte
Hello all,
Is there any way that i can remotely push my recent changes related to file
transfer or file changes from one server to other using git repository to
jenkins.
eg: if my local repository has any file changes i am pushing it to my
repository using below set of command in a script:
#
10 matches
Mail list logo
