triggeredBy within the stage context should help you:
https://www.jenkins.io/doc/book/pipeline/syntax/#when
pipeline {
...
triggers {
cron 'H H22 * * 1-5'
}
stages {
...
stage('deploy') {
when { triggeredBy 'TimerTrigger' }
...
}
If you run the same command in your terminal, does it work? Does it need
any kind of UI access?
On Monday, 26 October 2020 at 11:55:23 UTC jesusfern...@gmail.com wrote:
> I need to run a elevated x64 Native Tools Command Prompt fro VS 2019
> command ("vcperf /start session") within my pipeline.
Directories with an ampersand (like @tmp, @script, @libs, @2) are
specifically created by the pipeline internals, each one got a different
context. The ones with number are most likely related to a concurrent build
running while other previous build is still running, to avoid clashing with
acce
The issue is i run my application on kubernetes infrastructure which is
not mainatined by me.However in case of issue i want some logs to debug It
would have been straight forward if i had an access to the cluster via
kubectl commands but that not the case, i.e why i some how want to get the
The issue is i run my application on kubernetes infrastructure which is
not mainatined by me.However in case of issue i want some logs to debug the
issue.It would have been straight forward if i had an access to the cluster
via kubectl commands but that not the case, thats why i some how want
