Hi Guys,
Sorry I han't been checking email over the Easter break.
I like Kohsuke Kawaguchi's idea of running the two together, it will allow user
to try out the now plugin and provide feedback. I'm not sure how easy it would
be to provide a migration path for each Build Job's configuration,
I had tried to make the SCM polling more efficient and letting Perforce
manage it's own workspaces, after all this is what Perforce was designed to
do.
Can you please explain this statement? Perforce has always forced the user
to manage workspaces by hand, and is a major pain point for any sort
On Sunday, 20 April 2014, Paul Allen pal...@perforce.com wrote:
Hi Guys,
Sorry I han't been checking email over the Easter break.
I like Kohsuke Kawaguchi's idea of running the two together, it will allow
user to try out the now plugin and provide feedback. I'm not sure how easy
it would
Thanks for your suggestion! This is the updated code.
public String getKey() {
return settings.getKey();
}
public boolean getStart()
{
return settings.getIsStart();
}
@DataBoundSetter
public void setStart(boolean value)
{
This question is related to How to bind a checkbox on config.jelly with a
Builder
class?https://groups.google.com/forum/#!topic/jenkinsci-dev/5l37mEWYg5w.
The plugin has two classes and config.jelly in the project. This is how
it's structured.
LogInfoBuilder: It's a builder class that has an
