On Wed, Jun 12, 2019 at 11:22 PM Jim Barnebee wrote:
>
>
> On Friday, May 24, 2019 at 6:10:40 AM UTC-6, Emilio Escobar Reyero wrote:
>>
>> Hi,
>>
>> I have started a 2.178 instance from scratch, installing suggested
>> plugins, and the agent port configuration is behind Markup Formatter as
>>
On Friday, May 24, 2019 at 6:10:40 AM UTC-6, Emilio Escobar Reyero wrote:
>
> Hi,
>
> I have started a 2.178 instance from scratch, installing suggested
> plugins, and the agent port configuration is behind Markup Formatter as
> expected.
>
>
> [image: Screenshot 2019-05-24 at 13.36.39.png]
>
Hello all,
I am building a NSO (network services orchestrator) automation and would
like to ask the best approach regarding reload packages using github as SCM.
Currently every time that I run the pipeline it will clone all packages for
a tmp directory, destroy the entire NSO package folder,
String interpolation is being used incorrectly here.
Use just buildnumber instead of $buildnumber.
If you using $buildnumber, use ‘$buildnumber’ instead(in quotes as shown).
On Wed, 12 Jun 2019 at 11:13 PM, panneerrselvam natarajan <
panne...@gmail.com> wrote:
> Hi All,
>
>
> I am new to Jenkin
Also, remember that every branch has his own Jenkins file so you can do what
ever you want on every branch in that file it would effect only that branch.
Finally, if your problem is the logic that you use to trigger scheduled build I
would suggest to use a regular pipeline job to make the
On Wed, Jun 12, 2019 at 12:15 PM Ivan Fernandez Calvo <
kuisathave...@gmail.com> wrote:
> I do not get your point, Multibranch pipeline creates a new job for each
> branch that match with the criteria you specify, so you have a job for
> every branch, I do not understand what do you mean with ’ I
I do not get your point, Multibranch pipeline creates a new job for each branch
that match with the criteria you specify, so you have a job for every branch, I
do not understand what do you mean with ’ I want whoever kicks off the job to
be able to specify that only particular branches will
Hi
I have a Jenkins job which monitors for a comment added in Gerrit and fires
a new Jenkins job using the "build" command
the sub job that got fired is missing all GERRIT_* environment/parameters.
How can I pass all these values from the parent job to
the new job?
Thanks
--
You received
Hi,
I am using Jenkins, Gerrit and repo for my project. Often times I make code
changes that span across git repositories (all managed through repo). When
I submit a CL it triggers multiple Jenkins jobs (pre-submits, cross
reference checks, linters...) which sends flurry of build started emails
On Wed, Jun 12, 2019 at 9:52 AM Giles wrote:
> Hi Mark.
>
> Correct again:
>
> - Git plugin 3.10.0, now downgraded to 3.9.1
>
Git plugin 3.10.0 is a good choice. Upgrade to it.
> - Git client plugin 3.0.0-rc, now downgraded to 2.7.6
>
>
Git client plugin 3.0.0-rc is a bad choice. Don't
Hi Mark.
Correct again:
- Git plugin 3.10.0, now downgraded to 3.9.1
- Git client plugin 3.0.0-rc, now downgraded to 2.7.6
Deploys do now appear to all be working (this time I waited until we'd done
a fair bit of testing before reporting ...).
I upgraded the above plugins to 4.0.0-rc and
Hi All,
I am new to Jenkin and executing the pipeline.. Here i want to store the
build number and result in text file.
Here my scripts
f = new file ('pan2.txt")
f.append('newline added!\n)
echo "My file " +f
println f.text
The above scripts adding the content but now i want add the
Am Dienstag, 11. Juni 2019 13:14:28 UTC+2 schrieb Sverre Moe:
>
> I have the following Pipeline step to find specific files:
> sh("find . -regex '.*${packageName}-[0-9.]+-.\\.noarch\\.rpm'")
>
>
You' ll need to escape the backslashes twice: once for groovy and once for
the shell
sh("find .
We have a pipeline which deploys our main product (a java app inside an
application container)
I have used the env variable *JENKINS_NODE_COOKIE* to instruct Jenkins to
not kill the process.
For example:
withEnv(['JENKINS_NODE_COOKIE=dontkill']) {
// start your process here
sh 'java -jar ...'
Hello guys,
I am performing a few tests regarding NSO maintenance automation and the
behaviour of NSO is not what I was expecting. During the pipeline, I stop
the NSO daemon (ncs --stop) and restart it with (ncs
--with-package-reload-force). I created 2 pipelines: the first is a dry-run
and
I currently have a docker-compose.yml file that is used to perform a
jekyll build using `docker-compose run` as a one-off command:
version: '3.7'
services:
build-site:
image: jekyll/jekyll:3
command: jekyll build
volumes:
- .:/srv/jekyll
volumes:
-
Hello guys,
I am running my first pipeline and Im not sure why jenkins is killing the
service after completing the pipeline, do you have any idea ?
https://pastebin.com/LEMCuNMP
--
This email is intended solely for the person or entity to which it is
addressed and may contain
17 matches
Mail list logo
