Build Flow Test Aggregator - where is test results stored?

[Jacqueline Taing]

I'm using the Build Flow Test Aggregator 
 
plugin, which aggregates Junit test results for a build flow.  Where is the 
actual aggregated test results file stored on disk?

Thanks,
-jacqui

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ef7180fa-4057-40fa-af20-b5cc7e6004ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Parameterized Remote Trigger fails with NullPointerException

[Jacqueline Taing]

I am trying to use Parameterized Remote Trigger Plugin 
,
 
but I keep getting error when it tries to launch job:

Remote Jenkins server returned empty response or invalid JSON - but we can 
still proceed with the remote build.

ERROR: Build step failed with exception

java.lang.NullPointerException 


at 
org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.isRemoteJobParameterized(RemoteBuildConfiguration.java:1167)
 


at 
org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:488)
 


at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 


at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:764)
 


at hudson.model.Build$BuildExecution.build(Build.java:205) 


at hudson.model.Build$BuildExecution.doRun(Build.java:162) 


at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) 


at hudson.model.Run.execute(Run.java:1744) 


at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 


at hudson.model.ResourceController.execute(ResourceController.java:98) 


at hudson.model.Executor.run(Executor.java:374) 


Build step 'Trigger a remote parameterized job' marked build as failure

Finished: FAILURE


Has anyone been able to successfully trigger a remote job with this plugin?  My 
remote host configuration uses the Credential plugin with username/password 
specified.


Thanks,

-jacqui

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/60f7a2cb-0690-48bd-b140-7ac3d68270f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Mark node offline on build failure

[Jacqueline Taing]

Is there a way to mark a node offline via DSL. We currently use Build Flow 
Plugin  to 
define jobs and I'd like to automatically take a node offline when a build 
fails (so other jobs do not get queued/run on this slave).

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d775e4fe-479b-4658-a095-114ae06b9558%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Build Flow is not triggering all jobs

[Jacqueline Taing]

Hi,

I have the following in my build flow:

parallel (
  { ignore(FAILURE) {build("Gate/nightly-testflow")}},
  { ignore(FAILURE) {build("Gate/faas-nightly-testflow")}}
)

For some reason, it is never running the second job 
(Gate/faas-nightly-testflow).  Here's console output:

parallel {

ignore(FAILURE) {

ignore(FAILURE) {

Schedule job Release Validation » nightly-testflow 


// SUCCESS ignored

}

Build Release Validation » nightly-testflow #418 
 started

Release Validation » nightly-testflow #418 
 completed  : 
FAILURE

// FAILURE ignored

}

}


Any ideas when/why this would happen?


Thanks,

-jacqui

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/544e4c58-f703-4666-9254-071ce5b0b849%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: iframes no longer displayed after Jnekins upgrade (1.557)

[Jacqueline Taing]

Hi,

I have not gotten this to work with Xframe Filter Plugin.

For ALLOW-FROM, is this the domain of the URL for the iframe or something 
else? 

Thanks,
-jacqui

On Monday, April 7, 2014 at 3:15:38 AM UTC-7, pablaasmo wrote:
>
> On 07. april 2014 11:48, Glenn Halstead wrote: 
> > Hi folks, 
> > 
> > We upgraded Jenkins to version 1.557.  We were on 1.554 afaik.  I had 
> > html pages from job archives displayed in view using an iframe.  These 
> > are no longer displayed.  An example of the code I used in the view is 
> > below: 
> > 
> > #frame { width: 1200px; height: 650px; border: 0px; } 
> >  > 
> src="job/__TCHarvester_Summary_Report/lastSuccessfulBuild/artifact/JenkinsUtils/folders.summary.html">
>  
>
> > 
> > Has anyone else seen similar issues? 
> > 
>
> Hi, 
> we had the same issue. 
> For a solution that showed webpages from our Jenkins master in a frame, 
> we used the plugin 
> https://wiki.jenkins-ci.org/display/JENKINS/XFrame+Filter+Plugin to 
> solve the problem. 
>
> On the config for the plugin we added 
> ALLOW-FROM http://server.that-requests.com/ 
>
> But we also have the problem where we have an iframe in the description 
> of a project at the Jenkins master. Which I guess is more in the same 
> problem that you have. 
>
> We have not solved that problem yet :-( 
>
> Per A. 
>
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a9e73572-16c5-48d8-bd66-84a8b42fc13b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.