just for completeness and clarity, this works in a Build Flow DSL ...
public class FooBar {
private OutputStream out;
public FooBar(OutputStream out) {
this.out = out;
}
public static void sayFoo(OutputStream out) {
out.println("Foo");
}
public void sayBar() {
nvm ... looks like somebody else already found a workaround
...
https://groups.google.com/forum/#!searchin/jenkinsci-users/println/jenkinsci-users/mpGF1BJpsaA/phcHtf7stacJ
On Wednesday, February 19, 2014 8:54:14 AM UTC-5, Steve Maring wrote:
>
> If I run this script directly in
fooBar.sayBar();
It properly outputs:
Hello World
Foo
Bar
As DSL in a build flow I only get:
Hello World
CloudBees Build Flow
plugin<https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin>
v 0.10
What am I doing wrong?
-Steve Maring
Orlando, FL
--
You received this messa
cess to the contents of a
Global Password definition.
I've noticed https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin
but I seem to be limited to injecting variables as a Build Step, which are
not present in a "Build Flow".
Any thoughts?
-Steve Maring
Orlando, FL
--
}
On Thu, Dec 26, 2013 at 10:51 AM, Steve Maring wrote:
> ok ... my bad ... I had deleted all the builds that really did have that
> string param in them
>
> is there a way to pull that param from the project config and not rely on
> any previous builds having used it?
>
>
&g
ok ... my bad ... I had deleted all the builds that really did have that
string param in them
is there a way to pull that param from the project config and not rely on
any previous builds having used it?
On Thu, Dec 26, 2013 at 8:16 AM, Steve Maring wrote:
> I have some build flow dsl (gro
del.StringParameterValue*
*I know that the SCM_URL string parameter exists in that job ... what
am I doing wrong?*
*Thanks,*
*Steve Maring*
*Orlando, FL*
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group an
(new hudson.tasks.Shell("echo 'Hello World'"))
> l.addAll(oldBuilders)
> i.save()
>
> On 10.12.2013, at 19:56, Steve Maring wrote:
>
> > I have hundreds of Jobs that I would like to programmatically add an
> initial build step to using the Build
I have hundreds of Jobs that I would like to programmatically add an
initial build step to using the Build Flow Plugin
When I try something like this ...
String jobName = "MY_JOB";
List topLevelItems =
Jenkins.getInstance().getAllItems(TopLevelItem.class);
Job job;
Iterator topLevelItem
