> I am not able to configure the jenkins for remote trigger. Few years back
> I had done this, with older version using "Manage Credentials" option. But
> the latest versions don't have Manage Credentials option to configure
> hostname, hostname and port, etc options. And the docs in internet/
> On 25.12.2016, at 22:27, Jeff wrote:
>
> external internet sites
Could you host your own update site internally, possibly firewalled to only
allow access from that specific Jenkins master?
E.g. https://github.com/yandex-qatools/juseppe
--
You received this message because you are subscrib
I am unable to do this method. The powers that be won't allow any machine
with source code or access to source code direct access to any external
internet sites. It took 3 months just to get approval to allow Jenkins to
send build status emails to an internal server, but only after the Jenkins
Ma
IIUC what you say. No. Don't install a clean one and drop it, that will
overwrite existing files and probably just screw up everything.
But what you say makes me think of an intermediate way: you can use the
typical process to move a master to another machine, but then kind of "move
it back".
Rou
Hello,
IMO tbh you're mostly on your own here. I mean the initial research,
narrowing down the issue. That because probably only a handful or less of
people both run their master on Solaris and follow the list here...
Having done that in the past for an AIX specific issue: Identify the exact
vers
Here are some details but am not confident about my setup based on what
you're asking.
Maybe, you can help me to clarify what am doing incorrectly.
* how does your Jenkisfile look like
>
[Ram] : Jenkinsfile content is:
buildUtils("git")
> * do you have global shared library configured or per
+1. This is how we did that in the past for AIX.
And anyway, I think you should not use JDK (or maven, or any tool really)
auto install feature for long in general. It's cool and useful for quick
prototyping but probably not a good idea for your production CD/CI cluster.
(If not obvious why: you do
Hi,
we were also wondering why there´s that pipeline-as-code approach available
and strongly recommended everywhere - without any traditional support
(automated tests) of developing clean code for it.
So we worked around that by doing the following:
- we have a Test Jenkins instance running wh
can you provide some more info, especially
* how does your Jenkisfile look like
* do you have global shared library configured or per folder?
* which version of the shared library do you adress? Is your script
available in that version?
* do you have same script in the internal repo?
Regards, T
