Yeah it works for us in most cases. But if people want to test it locally
before pushing their changes to remote repository then it is an extra step.
Also any new branch a dev is working on requires local jenkins to be
updated to point to the branch on shared library or update the jenkinsfile
to us
We unit test ours:
https://relaxdiego.com/2018/02/jenkins-on-jenkins-shared-libraries.html
On Tue, Oct 16, 2018 at 18:24 Hari Phaneendra wrote:
> Hi,
> I am looking for ideas on how to test shared libraries locally without
> having to push my changes to github and have my local jenkins point to
Tks James.
I can not post because, this is a private project for a private company in
Brazil.
Anyway, thanks for the attention.
Excuse my english. It's more or less.
Em terça-feira, 16 de outubro de 2018 20:49:24 UTC-3, James Fairweather
escreveu:
>
> Why don't you want to go through GitHub?
Why don't you want to go through GitHub? That workflow works really well
in my experience.
On Tue, Oct 16, 2018, 4:24 PM Hari Phaneendra, wrote:
> Hi,
> I am looking for ideas on how to test shared libraries locally without
> having to push my changes to github and have my local jenkins point t
Hi,
I am looking for ideas on how to test shared libraries locally without
having to push my changes to github and have my local jenkins point to the
remote repo? Is it possible to setup jenkins to look for shared libraries
on local absolute paths?
--
You received this message because you are
