Considering that your current Jenkins system is using classic jobs (no
pipelines) ...how to tell if these jobs can be converted to a pipeline job?
This page: https://plugins.jenkins.io/, lists all the Jenkins plugins. If
I enter ‘pipeline’ in the search box, it brings up 104 plugins (not
Yes - but it seems it can only be statically declared at the agent level,
can it be declared as reusable workflow-lib (
https://plugins.jenkins.io/workflow-cps-global-lib)?
tir. 3. sep. 2019 kl. 13:53 skrev Emilio Escobar Reyero <
eescobarrey...@cloudbees.com>:
> Hi David,
>
>
>
Is this on a Windows agent? Is your agent running as a service? Generally,
on Windows services are not allowed to interact with the desktop. There is
a setting which allows this, though I believe it is not recommended by MS.
(You can Google and find information on interacting with the desktop).
Hi David,
https://github.com/jenkinsci/kubernetes-plugin/blob/master/README.md#declarative-pipeline
It can be also used in declarative pipelines.
Regards
On Tue, Sep 3, 2019 at 11:56 AM David Karlsen
wrote:
> Am I right in that kubernetes-pipeline-plugin can only be used with
> scripted
Hi,
Is there any alternative for SendKeys in Jenkins (Robot Framework) ?
I am facing an issue that whenever I execute such code it gets stuck in
Jenkins, while same executed successfully locally (without Jenkins)
Thanks
Abhishek
--
You received this message because you are subscribed to the
Am I right in that kubernetes-pipeline-plugin can only be used with
scripted pipelines - not declarative ones?
--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe
Hey James,
I had the same issue without understanding what happened. Meanwhile I also
understand that it's due to the automatic updates kicking in. I solved it
by removing the JDK from that AMI and let the master install it.
You could also update your AMI and not allow auto upgrades, or you
So our builds failed again yesterday due to this automatic update kicking
in. I checked, there was indeed a JDK security update so no complaints, but
I need a better system of updating Jenkins.
Given Packer can search for and filter down AMIs, I thought the EC2 plugin
should be able to, too.