Return to site

Hides 5 1 – Keep A Squeaky Clean Workspace Clean

broken image


  • Status:Resolved(View Workflow)
  • Resolution: Fixed
  • Labels:
  • Environment:
    Hudson 1.371, Apache Tomcat 6.0.16, Perforce 2009.02 (both server/client)

Create a scavenger hunt where you hide valuable prizes in places people might not want to clean, like the dirty microwave. Let people know the prize is theirs if they find it and clean the corresponding area. So maybe you put a $20 bill in the microwave and whoever takes 15 minutes to clean it down can keep it. Squeaky Clean Brush Cleaner. One or two spritzes of this cleaner on your brush is all you need to keep it nice and clean. Spritz the cleaner on our Brush Scrubber and scrub the brush clean, then dry the brush off on our Scrub It Clean Microfiber cloths. 3 Reviews Hide Reviews Show Reviews 5 Squeaky Clean Brush Cleaner. Posted by Theresa. Nov 22, 2016 Hides can also quickly hide all open Applications, giving you a fresh, clear work space. Configure Hides with. Hides 3.0.1 – Keep a squeaky-clean workspace.

In a Maven 2 build, if you select the option to 'Clean Workspace Before Each Build' it would be nice if the Perforce plug-in would ignored the Maven private repository ($WORKSPACE/.repository) or provided an option to ignore the private repository.

is duplicated by

JENKINS-7954Perforce plugin Clean Workspace Before Each Build should provide option to keep private Maven repository

  • Resolved
Hide
km added a comment -

Sorry, trying to understand better. Is this specific to perforce?

Are you saying your Maven artifact local repository in $WORKSPACE/.repository? I thought, by default Maven will download the artifacts at /.m2/repository, no? (Your builds can of course override this setting).

Show
km added a comment - Sorry, trying to understand better. Is this specific to perforce? Are you saying your Maven artifact local repository in $WORKSPACE/.repository? I thought, by default Maven will download the artifacts at /.m2/repository, no? (Your builds can of course override this setting).
Hide
Rob Petti added a comment -

This isn't specific to the perforce plugin. The plugin simply reuses the 'Wipe Out Workspace' function in core hudson.

Show
Rob Petti added a comment - This isn't specific to the perforce plugin. The plugin simply reuses the 'Wipe Out Workspace' function in core hudson.
Hide
Mike Delaney added a comment -

Sorry, I think there is come confusion here. I did not mean the link labeled 'Wipe Out Workspace' that is provided by Hudson but the actual feature of the Perforce plugin (found in PerforceSCM.java; see snippet below) that calls workspace.deleteContents().

Nch express invoice plus 5 05. If it helps, I can supply a patch as an example of what I'm doing here to work around this.

[ Code Snippet ]
if(wipeBeforeBuild){
log.println('Clearing workspace..');
if(processWorkspaceBeforeDeletion(build.getProject(), workspace, build.getBuiltOn()))

{ workspace.deleteContents(); log.println('Cleared workspace.'); }

else

{ log.println('Could not clear workspace. See hudson.perforce.PerforceSCM logger for details.'); }

forceSync = true;
}

Hides 5 1 – keep a squeaky clean workspace clean slate
Show
Mike Delaney added a comment - Sorry, I think there is come confusion here. I did not mean the link labeled 'Wipe Out Workspace' that is provided by Hudson but the actual feature of the Perforce plugin (found in PerforceSCM.java; see snippet below) that calls workspace.deleteContents(). If it helps, I can supply a patch as an example of what I'm doing here to work around this. [ Code Snippet ] if(wipeBeforeBuild){ log.println('Clearing workspace..'); if(processWorkspaceBeforeDeletion(build.getProject(), workspace, build.getBuiltOn())) { workspace.deleteContents(); log.println('Cleared workspace.'); } else { log.println('Could not clear workspace. See hudson.perforce.PerforceSCM logger for details.'); } forceSync = true; }
Hide
Rob Petti added a comment -

That function is exactly the same as the Wipe Out Workspace function in hudson. The user should have the reasonable expectation that they will both operate in exactly the same way. Why is your maven repository in the workspace in the first place?

The only thing I'd be willing to implement is an optional setting to skip an arbitrary set of paths when deleting everything. Does your patch do this, or is it hard-coded only for your case?

Show
Rob Petti added a comment - That function is exactly the same as the Wipe Out Workspace function in hudson. The user should have the reasonable expectation that they will both operate in exactly the same way. Why is your maven repository in the workspace in the first place? The only thing I'd be willing to implement is an optional setting to skip an arbitrary set of paths when deleting everything. Does your patch do this, or is it hard-coded only for your case?
Hide
Mike Delaney added a comment - - edited

We have our maven repository in our workspace to avoid build failures when one job tries to access a artifact that currently being downloaded from another job in Hudson; we have some machines setup with six, or more, executors. Using a private repository adds additional stability to our builds.

The patch is currently hard-coded to skip only the '.repository' location.

That being said, I can update the patch to be configurable. In fact, I had plans to do that but haven't had the time yet to do it.

Show
Mike Delaney added a comment - - edited We have our maven repository in our workspace to avoid build failures when one job tries to access a artifact that currently being downloaded from another job in Hudson; we have some machines setup with six, or more, executors. Using a private repository adds additional stability to our builds. The patch is currently hard-coded to skip only the '.repository' location. That being said, I can update the patch to be configurable. In fact, I had plans to do that but haven't had the time yet to do it.
Hide
SCM/JIRA link daemon added a comment -

Code changed in hudson
User: : rpetti
Path:
trunk/hudson/plugins/perforce/src/main/java/hudson/plugins/perforce/PerforceSCM.java
http://jenkins-ci.org/commit/36404
Log:
[FIXED JENKINS-7182] skip .repository when cleaning out the workspace

Show
SCM/JIRA link daemon added a comment - Code changed in hudson User: : rpetti Path: trunk/hudson/plugins/perforce/src/main/java/hudson/plugins/perforce/PerforceSCM.java http://jenkins-ci.org/commit/36404 Log: [FIXED JENKINS-7182] skip .repository when cleaning out the workspace
Hide
hagzag added a comment -

I think this is a bit too much forcing everybody to skip the .repository especially when you would like to have a squeaky clean build - including a clean .m2 for the build.
I will be posting such functionality in a FORK recommended for this plugin.

Show
hagzag added a comment - I think this is a bit too much forcing everybody to skip the .repository especially when you would like to have a squeaky clean build - including a clean .m2 for the build. I will be posting such functionality in a FORK recommended for this plugin.
Hide
Arnaud Héritier added a comment -

Hides 5 1 – Keep A Squeaky Clean Workspace Cleaning Service

myself I'm using this plugin to cleanup regularly my repositories : https://github.com/jenkinsci/maven-repo-cleaner-plugin

Show
Arnaud Héritier added a comment - myself I'm using this plugin to cleanup regularly my repositories : https://github.com/jenkinsci/maven-repo-cleaner-plugin
  • Assignee:
    Unassigned
    Reporter:
    Mike Delaney
  • Votes:
    0Vote for this issue
    Watchers:
    1Start watching this issue
  • Created:
    Updated:
    Resolved:
5 Critical Paint Mistakes That Can Make Your Walls Look Dirty

Especially in high-traffic areas, keeping walls clean of dirt, dust, scuffs, and splatters is an everyday battle. Washing your walls frequently can help keep marks and stains at bay, but the secret to pristine walls actually lies in the paint. Certain paint colors, types of paint, and application techniques can result in walls that appear dirtier and are more difficult to clean. Avoid these common paint mistakes for walls that look spotless and stay clean for longer.

1. Your paint color is too light.

Fluid remote desktop. If you're worried about dirty walls, bright white is perhaps the least forgiving paint color. Any marks or stains will stand out on light-colored walls. Instead, look for a mid-tone neutral paint color that can help hide dirt and imperfections, says Dee Schlotter, senior color marketing manager for the PPG paint brand. She suggests PPG's Gray By Me (PPG1008-4) for a 'warm greige that can help keep those fingerprints hidden in high-traffic areas like a playroom or kitchen.' A cooler neutral like UFO (PPG1011-4), for instance, will provide good coverage while keeping a room bright, she says.

2. You bought the cheapest paint you could find.

For the cleanest-looking finish, using high-quality paint is a must—and sometimes that comes with a higher price tag. There's a big difference between a can of paint that costs $20 and one that costs $70, says Mike Mundwiller, field development manager for Benjamin Moore. 'The quality of the product used will affect the outcome and make a dramatic difference in how the product performs, hides, and lasts,' he says. In areas where durability is especially important, such as the kitchen or bathroom, consider splurging on premium paint that will offer better coverage and a longer-lasting finish.

3. You chose a sheen that's difficult to clean.

Hides 5 1 – Keep A Squeaky Clean Workspace Clean Magic Eraser

A paint's sheen or gloss, which refers to how reflective the finish appears on the wall, can have a huge effect on how clean your walls look. In general, shinier finishes, including semi-gloss and high-gloss, are easier to clean because of their durability. A glossier surface will stand up better against frequent cleaning, so these sheens work well on trim and kitchen cabinetry. Washing walls with a flat or matte sheen, on the other hand, will require a gentle touch, as certain cleaning products and vigorous scrubbing can damage the finish. Non-reflective paint finishes work best in low-traffic areas that won't gather too many scuffs or splatters.

However, it's important to note that glossy paint is less forgiving than flatter finishes when it comes to imperfections like nail holes, dents, cracks, or patches. 'Since gloss finishes reflect light and can accentuate blemishes, avoid using them on areas that are not completely smooth,' Mundwiller says. If your walls have flaws you'd like to disguise, opt for a flatter finish for a cleaner look.

4. You didn't properly prep walls before painting.

Prep work is key to achieving a crisp finish, and cleaning walls is the first step. Use a trisodium phosphate (TSP) solution ($4, The Home Depot) to wipe down walls and remove dust or dirt before painting. Consider applying primer to help paint adhere properly. Primer is especially useful if you're covering up surface stains, such as water marks or stains from smoke. A base coat of primer helps create a blank slate so the paint color isn't fighting against stains underneath.

Hides 5 1 – Keep A Squeaky Clean Workspace Clean Laminate Floors

5. You used the wrong painting tools.

Hides 5 1 – Keep A Squeaky Clean Workspace Clean Furniture

One brush does not fit all paint jobs. 'The tools used often make the difference between an easy job that looks great and a hard job that doesn't look so good when it's finished,' Mundwiller says. Pay close attention to the brush or roller recommended for the paint you're using. The best tool for your painting project also depends on the type of surface. Using a 3/4-inch-thick roller on smooth plaster walls, for example, can create an orange peel-like texture that will be more difficult to keep clean. In general, smooth surfaces require rollers with a thin nap, while rougher textures, such as brick walls, call for thickly woven rollers that can hold more paint and get into the crevices.





broken image