Is it possible to disable a large number of Jenkins jobs in one go?
I have a large number of jenkins job I need to disable. Visiting each job in turn and disbling is tedious.
https://wiki.jenkins-ci.org/display/JENKINS/Configuration+Slicing+Plugin
That works beautifully install it go to http://your_jenkins.com:8080/slicing/jobdisabledbool/?
By using configuration slicing plugin:
By using this plugin easy to find out anything has enabled or disable jobs and timer separated jobs
Manage Jenkins >Config slicing > select options
Related
We are using Dynatrace to monitoring all our infrastructure and we want to monitor some specific files in our servers (I.Ex. /etc/passwd) , but there is no specific monitoring for that. The Dynatrace agent is running inside all our servers.
Does anyone know how to achieve this or has implemented some solution for this?
Thanks.
As per my understanding the answer would be a no. Dynatrace supports custom plugin in python and I have written few custom plugins but that are executed per min to send the metrics.
But I don't think so writing a custom plugin for this would be good use case.
For the triggers perspective you can go to the Settings "Anomaly Detection" and check if there is any option but quite sure there is no such option for this configuration.
You can raise an RFE for this -- this is actually a good requirement not from /etc/passwd perspective but from other stuff can be monitored.
Is it possible to create a rotation of on call personal with Zabbix.
What I want to archive is that emails with issues only go to a specific person during one week, and that change automatically when the we ends.
Thanks
That can not be done with the built-in capabilities. You would have to use external scripts as Zabbix alertscripts, or script things using the Zabbix API.
There is a feature request in Zabbix to do exactly this.
https://support.zabbix.com/browse/ZBXNEXT-537
Until then, you could take a look at "iLert" or "OpsGenie"
I am not sure if this is desired behaviour, but PhpStorm (8.0.3) proceeds to index all files and directories each time I open the IDE. The indexing takes too long - half hour and more. During that time I'm not able to access many configuration options or use "Go to definition" option.
It is very irritating. Shouldn't PhpStorm somehow cache the indices so that it does not go through the whole process over and over again?
It seems that the problem grew over time and at this time it totally paralizes my ability to work on projects.
Is there a solution to it that you know of?
is this problem still current? It's more than year since question, so it could be fixed already.
There is no reliable way to say why it's happenings without seeing the logs.
You may try this:
Close IDE (or this project at least)
Backup and delete .idea subfolder (this project settings)
Launch IDE and using "Open" point to the project root -- IDE will create new project from those files
Reconfigure your project as needed
Restart IDE / close-reopen project (do what you did in the past where it lead to project re-indexing)
It's better now?
If yes, and you have not re-configured ALL aspects of the project yet -- then you may re-use some of the files from previously
made backup (while IDE/project is closed, of course)
Try right-clicking file -> invalidate caches and restart. It worked for me!
File ==> Manage IDE Settings ==> Restore Default Settings
And now it loads rapidly
I had the same problem after searching a while I understood that .gitignore plugin caused it.
After disabling mentioned plugin ide backed to work correctly again.
Why does it take so long to deploy on Elastic Beanstalk even if I just change a single file? I so wish it would recognize file changes and apply them on top of the version.
As mentioned here, Elastic Beanstalk deployment isn't smart. Even though it works with git, it doesn't use deltas and uploads the entire repository every time you deploy. I found no way around that.
I want to install PowerShell to 600 Window XP computers, and use it as the main processing shell. For example, for replacing batch scripts, VB scripts, and some other little programs. The installation process is not a problem. Some issues I think I'm going to come across are:
Changing permissions to allow PowerShell to run scripts
The speed of PowerShell starting
Using PowerShell for logon/logoff scripts with GPO
Problem 2: There is a script that is supposed to speed up PowerShell, but it seems to need to be run as administrator (which of course isn't something that normal users do).
Has anyone had any experience with using PowerShell in this way?
To speed up the start of PowerShell, Jeffrey Snover (the partner/architect responsible for PowerShell) provides an "Update-GAC" script here.
Basically, it is just running through the assemblies that are loaded for PowerShell and NGen'ing (pre-compiling the IL to machine code) them. This does speed up the start of PowerShell.
Another trick is to run PowerShell with the -nologo and -noprofile switches.
This will skip the profile scripts and splash logo.
There is a product for using PowerShell for logon/logoff scripts from Special Operations Software. There are other ways to do it also.
%windir%\system32\WindowsPowerShell\v1.0\powershell.exe -nologo -noprofile
Changing permissions to allow Powershell scripts is possible to do via group policy.
Microsoft provide ADM templates here, there is only one option "Turn on Script Execution" and can be assigned at a user or computer level.
It seems it's possible to run poweshell silently, but not just by calling itself. This article has more information.
So answering my own questions
This can be done via GPOs
First run takes at least 10 seconds
on our computers. this could add
that time onto the logon time which
is unacceptable.
This seems fairly simple to do, using the
scripts above is invisibility is
needed, or by calling the powershell
exe and passing it startup options.
On our computers, to use powershell for logon seems not to be worthwhile just because of the logon time increase.