time.google.com
time1.google.com
time2.google.com
time3.google.com
| import os | |
| import pandas as pd | |
| from azureml.core import Workspace, Dataset | |
| # Connect to Workspace and reference Dataset | |
| ws = Workspace.from_config() | |
| dataset = ws.datasets["german-credit-train-tutorial"] | |
| # Create mountcontext and mount the dataset | |
| mount_ctx = dataset.mount() |
| 1. Setup a project | |
| 2. Add groovy SDK support: | |
| https://www.bonusbits.com/wiki/HowTo:Add_Groovy_SDK_to_IntelliJ_IDEA | |
| 3. Download http://(yourjenkinsurl)/job/(yourpipelinejob)/pipeline-syntax/gdsl | |
| - this will give you the .gdsl file - download this to the src folder of your project. | |
| 4. Finally follow this step - right click on the src folder -> Mark directory as -> Sources Root |
My country is under a daylight saving time period and not all my commits are made during the morning/afternoon. Because I commited after 11:00 PM - which, given the local DST, was after 00:00 AM - my 100+ days commit streak got broken - which made me very unhappy.
| import com.cloudbees.hudson.plugins.folder.Folder | |
| import hudson.FilePath | |
| import jenkins.model.Jenkins | |
| def boolean isFolder(String name) { | |
| def item = Jenkins.instance.getItemByFullName(name) | |
| return item instanceof Folder | |
| } | |
| def deleteUnusedWorkspace(FilePath root, String path) { |
| /* | |
| Author: Gary Clayburg | |
| This file allows IntelliJ IDEA to perform basic syntax checking and code completion for | |
| Jenkins workflow groovy scripts. https://github.com/jenkinsci/workflow-plugin | |
| These methods are supported | |
| sh | |
| readFile | |
| node | |
| echo |
| <# | |
| .Synopsis | |
| Returns the install .NET Framework versions. | |
| .Description | |
| The script looks through the registry using the notes from the below | |
| MSDN links to determine which versions of .NET are installed. |
When working with Git, there are two prevailing workflows are Git workflow and feature branches. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited, and the focus of this article.
If you are new to Git and Git-workflows, I suggest reading the atlassian.com Git Workflow article in addition to this as there is more detail there than presented here.
I admit, using Bash in the command line with the standard configuration leaves a bit to be desired when it comes to awareness of state. A tool that I suggest using follows these instructions on setting up GIT Bash autocompletion. This tool will assist you to better visualize the state of a branc
| // Check if a slave has < 10 GB of free space, wipe out workspaces if it does | |
| import hudson.model.*; | |
| import hudson.util.*; | |
| import jenkins.model.*; | |
| import hudson.FilePath.FileCallable; | |
| import hudson.slaves.OfflineCause; | |
| import hudson.node_monitors.*; | |
| for (node in Jenkins.instance.nodes) { |