For me, upgrading from Jenkins 1.475 to Jenkins 1.495 solved the problem
My environment:
- Linux Mint 14 KDE (based on Ubuntu quantal 12.10), 64-bit
ceefour@annafi:~$ uname -a
Linux annafi.dev 3.5.0-21-generic #32-Ubuntu SMP Tue Dec 11 18:51:59 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
ceefour@ann
So, after figuring out how to build and debug Jenkins, I discovered the
answer I was looking for.
The groovy script has to return an array of strings in the groovy 'choice'
variable:
def mydata = ['string 1', 'string 2', 'string 3', 'string
4', 'string 5' ]
choice = mydata
It is
*Correction*:
The groovy script has to return an array of strings in the groovy '*choices*'
> variable:
>
>def mydata = ['string 1', 'string 2', 'string 3', 'string
> 4', 'string 5' ]
>*choices* = mydata
>
>
There are situations when I need to restart our busy production Jenkins server,
perhaps to install a plugin. I use the “Prepare for Shutdown” option in Manage
Jenkins, so as to not interrupt running jobs.
What I’d like is for the “Prepare for Shutdown” to be “sticky” so that when the
server
Hi All,
I wondered if it were possible, or not then a trivial update to the EC2
plugin to allow it to start/stop an instance that already exists.
Currently I have 2 Windows instances, 1 which is 24x7 and is covered in the
free tier but its performance is lacking. The other is a High CPU instanc
