On Monday, July 1, 2019 at 3:37:40 PM UTC+7, sirisha sai wrote:
>
> Hi,
>
> Currently I am working on a .net project.I have a scenario,Job 1
> output(dll's) needs to be copied to Job 2 Jenkins workspace and then run
> the corresponding sln(solution) file of Job 2.In this case can I use stash
I have a similar issue, except my test results some from multiple jobs
my basic build pipeline runs unit tests then invokes the systemtest
pipeline. These run 10 to 30 times a day.
I also have a nightly pipeline that runs a lot of additional tests, like
coverage, interop, stress, load, upgrade.
I was thinking about this the other day. My plan is to create a simple
jenkins job that manages all of my other jenkins jobs. Some of the other
suggestions might feed into this.
My goal is to able to bootstrap a new jenkins server in minutes for
disaster recovery and for bringing up new
I went back and forth on this. In the end, I put everything in code. I
decided I wanted the minimum amount of stuff configured in jenkins.
I started out with a wrapper pipeline that loaded the "guts" of the job.
This was extremely restrictive in that each job had to conform at some
level to
Hi everybody,
Since a lot of my jobs have more or less the same set of parameters, I
wanted to implement a "parent job" where we have the shared configuration,
and all "children" jobs should just inherit from the "parent" and change
the parameters if needed.
I have found that the "inheritance
We use the jobDSL to manage the 10 different jobs for the 100+ Git
repositories we have. We are trying to reduce the number of jobs per
repository by using a pipeline library in combination with a Jenkinsfile in
each repository.
The original jobs:
- Build develop with deploy to Nexus
- Build
Hi Marcin,
I have the same needs actually, do you have a working solution for that ?
I have tried a bit the Inheritance plugin (
https://plugins.jenkins.io/project-inheritance/) but I am still having some
problems with it.
Looking forward to your reply.
Kind regards,
Marouane
Le dimanche 18
Hey Jeff,looks indeed like the 'standard' type of problems. Unfortunately in
our network, I do not have theprivileges to do anything much. Not that that
would help much, since I'm only a simple SW engineer,not a network
specialist.The tip to try another agent connection is a good one though.