Best qoute from Devopsdays Minneapolis.
- “You can’t but DevOps, but I can sell you some”
Great conference here in MN.
Best qoute from Devopsdays Minneapolis.
Great conference here in MN.
I recently attended the NFJS conference in MN and was shown the following article on Java written by Java Champions.
If you looking for answers concerning what Java version to use going forward, what the new Java cadence will be, and any other question related to the recent changes around Java, check out this article!
My thoughts on using sub-expressions to access object properties.
$serviceObj = Get-Service "wmi*" Write-Output "Service Status $serviceObj.status" Service Status System.ServiceProcess.ServiceController.status
$serviceObj = Get-Service "wmi*" Write-Output "Service Status $($serviceObj.status)" Service Status Stopped
I just can’t stop playing around with the Jenkins JCasC plugin. However, I just don’t think its in a state to replace all of your Jenkins configuration yet.
Example – I want to create a new Jenkins user\password and add the additional user data such as email, token, and description with the JCasC plugin.
You are currently only able to automate the username and password, and that is it.
securityRealm: local: allowsSignup: false enableCaptcha: false users: - id: "builduser" password: ${builduserpassword}
If you try adding the additional attributes, its going to fail. Checking the code seems to confirm the only available values are username and password.
Anyways, I will be following this plugin very closely. Probably even test it out more…
Lately, I’ve been reading some AWS documents in preparation for the SYSOPS certification and came across a great AWS monitoring best practice document.
This is such a great starting point for teams implementing a new monitoring solutions!
I’m still playing around with this Jenkins JCasC plugin. Its got major potential!!
One little gotcha if you are on Windows is how you path out to the jenkins.yaml file from within Jenkins. In my case, I was using standard Windows back slash.
This isn’t going to work. You need to use forward slashes in the Path text box.
Enjoy!!!
I have been doing a little research on the Jenkins Configuration as Code (JCasC) plugin and I must say I think it’s definitely a step in the right direction.
In theory, with this plugin, you can have the majority of your Jenkins configuration stored in 1 file. This file can then be put in source control, which would allow you to easily rebuild your Jenkins instance at anytime.
However, while playing around with the plugin, a couple things came to my mind.
Anyways – This is a cool plugin that I am surely looking forward to using in the future!