lttlrck

git branch -m old_branch new_branch         # Rename branch locally    
git push origin :old_branch                 # Delete the old branch    
git push --set-upstream origin new_branch   # Push the new branch, set local branch to track the new remote

stuart-warren

# check if job exists
curl -XGET 'http://jenkins/checkJobName?value=yourJobFolderName' --user user.name:YourAPIToken

# with folder plugin
curl -s -XPOST 'http://jenkins/job/FolderName/createItem?name=yourJobName' --data-binary @config.xml -H "Content-Type:text/xml" --user user.name:YourAPIToken

# without folder plugin
curl -s -XPOST 'http://jenkins/createItem?name=yourJobName' --data-binary @config.xml -H "Content-Type:text/xml" --user user.name:YourAPIToken

# create folder

jczaplew

Setup:
  Node running on :8080
	Apache running on :80
	Using Apache mod_proxy to forward application requests to :8080

Symptoms 

On client:
	1. Proxy Error
		The proxy server received an invalid response from an upstream server.

sallar

<?php
// Output screenshot:
// http://cl.ly/NsqF
// -------------------------------------------------------

include_once 'console.php';

// ::log method usage
// -------------------------------------------------------
Console::log('Im Red!', 'red');

0xjjpa

#Introduction

Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.

Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.

Table of Contents

1. Understand the Chrome Architecture
2. Understand the Tabs-Extension Relationship
3. Picking the right interface for the job

larsar

# The VirtualBox documentation[1] for how to install guest additions 
# for Linux on a virtual host is somewhat messy. So here is what 
# I did to make it work.

# Install the packages required
yum update
yum install gcc kernel-devel make

reboot

max747

public class AnnotationConfigWebApplicationContextLoader extends AnnotationConfigContextLoader {

    @Override
    protected void customizeBeanFactory(DefaultListableBeanFactory beanFactory) {
        MockServletContext servletContext = new MockServletContext();

        // copy of GenericWebApplicationContext#postProcessBeanFactory
        beanFactory.addBeanPostProcessor(new ServletContextAwareProcessor(servletContext));
        beanFactory.ignoreDependencyInterface(ServletContextAware.class);

tdd

# Put this in your ~/.gitconfig or ~/.config/git/config
# Windows users: "~" is your profile's home directory, e.g. C:\Users\<YourName>
[user]
  name = Your Full Name
  email = your@email.tld
[color]
  # Enable colors in color-supporting terminals
  ui = auto
[alias]
  # List available aliases