Re: Newbie: TAP Plugin && Matrix Builds

[Evan Van Dyke]

And...  the 2nd half has now been added as well.   All looking good on my 
local Jenkins server.

Let me know... this should fully address the defect if accepted.

On Tuesday, May 3, 2016 at 6:39:39 PM UTC-5, Evan Van Dyke wrote:
>
> Okay...   Update on Git which fixes 1/2 of the problems (the Dashboard 
> view now shows test statistics correctly).
>
> Still need to determine how to get the aggregate test chart on the Matrix 
> job main page.
>
> Submitting a pull request with this part of the fix from:  
> https://github.com/evandy0/tap-plugin
>
> Please let me know what you think... you know your plugin best, and I 
> totally just did a hack-job here (but a working hack-job).
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/63ebbf22-958d-4531-aafb-2281dce1199d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Are backend crawlers still executed?

[R. Tyler Croy]

I've fixed the syncing to the mirror network, sorry for the delay in addressing
this.


- R. Tyler Croy

--
 Code: 
  Chatter: 

  % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
--

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


signature.asc
Description: Digital signature

Re: Newbie: TAP Plugin && Matrix Builds

[Evan Van Dyke]

Okay...   Update on Git which fixes 1/2 of the problems (the Dashboard view 
now shows test statistics correctly).

Still need to determine how to get the aggregate test chart on the Matrix 
job main page.

Submitting a pull request with this part of the fix from: 
 https://github.com/evandy0/tap-plugin

Please let me know what you think... you know your plugin best, and I 
totally just did a hack-job here (but a working hack-job).

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/beacabe6-226b-443f-aab0-d4dbf07d20b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Newbie: TAP Plugin && Matrix Builds

[Evan Van Dyke]

Hey, thanks for the quick reply!

No, I have nothing in a fork (yet), although I'm likely to try poking 
around.Trying to get work to fund my time, since I'm doing this to fix 
things up for them...  but trying to get maven and get working behind all 
our firewalls is a bear.   Glad that this is on your radar already; 
definitely something that will make our team happy.  If you get to it 
first, I will not be upset by any means.#1 need is to have all the 
individual test results show up on the Dashboard view.  Thanks to the 
-12205 fix, it now shows each of the matrix sub-jobs; they just claim they 
have 0 tests in them (though the test trend graph works just fine).

First one to the finish line wins...  and the sooner the better!

Again, thanks for the quick reply.

On Tuesday, May 3, 2016 at 5:39:02 PM UTC-5, kinow wrote:
>
> Hi Evan!
>
> >First time Jenkins development, so my apologies for what is probably a 
> newbie question.
>
> No need to apologise for that, that's an excellent question. Thanks for 
> posting it to the mailing list. This is one of the issues that I want to 
> fix in tap-plugin in the next releases (another one is related to 
> performance).
>
> When the plug-in was created, it was implemented with custom 
> views/actions. Some time later users wanted to be able to use the same 
> default test UI (i.e. the same graphs and views generated with JUnit 
> tests). So we tried to reproduce what was done in (IIRC) testng-plugin.
>
> >I'm hesitant to just replace the one with the other... and even more 
> hesitant to add another special-case to the dashboard plugin to handle TAP.
>
> Let's try to tackle JENKINS-22016 first by changing only tap-plugin. I'll 
> have some spare time this weekend (forecast says it's going to rain here 
> :-) so I can take a look at the API for Matrix projects (never used that) 
> and see if we can simply add a new action, or go with your 1) or 2) 
> options, keeping backward compatibility in tap-plugin and not changing core 
> or other plug-ins.
>
> If you have anything now in a fork, feel free to submit a pull request any 
> time, as we can review the changes, and I can help testing it locally too. 
> And then drop or update the pull request. Or if you want to have a quick 
> chat about parts of the plug-in code, I'm normally lurking in #jenkins as 
> kinow.
>
> Cheers
> Bruno
>
>
> --
> *From:* Evan Van Dyke 
> *To:* Jenkins Developers  
> *Sent:* Wednesday, 4 May 2016 10:28 AM
> *Subject:* Newbie: TAP Plugin && Matrix Builds
>
> First time Jenkins development, so my apologies for what is probably a 
> newbie question...   I am trying to attack JENKINS-22016, in which the TAP 
> results are not published correctly for a Matrix project configuration.
>
> I've found the resolution for JENKINS-12205, which solved a similar issue 
> for XUnit. It appears the issue is with the Dashboard View's 
> "summarizeJob" implementation (see below).   The TAP plugin isn't 
> publishing a generic hudson.tasks.test.TestResultProjectAction, and 
> instead defines its own ProjectAction class.
>
> What I'm struggling with is how to add a new instance of the 
> TestResultProjectAction to the TAP plugin.  
> The plugin is already publishing a ProjectAction class, and it implements 
> a different API than the generic Hudson one.  
> I'm hesitant to just replace the one with the other... and even more 
> hesitant to add another special-case to the dashboard plugin to handle TAP.
>
> Any thoughts/suggestions from those familiar with the Jenkins Core? What's 
> the best path forward here?
> I see three potential paths forward:
> 1) Replace the TAP Plugin's ProjectAction class with the generic (probably 
> best long-term)
> 2) Descend the TAP Plugin's ProjectAction class from the generic
> 3) Add a new special-case breakout in the dashboard view
>
> private static void summarizeJob(Job job, TestResultSummary summary) {
>   boolean addBlank = true;
>   TestResultProjectAction testResults = 
> job.getAction(TestResultProjectAction.class);
>  
>   if (testResults != null) {
> AbstractTestResultAction tra = 
> testResults.getLastTestResultAction();
>  
>  if (tra != null) {
> addBlank = false;
> summary.addTestResult(new TestResult(job, tra.getTotalCount(), 
> tra.getFailCount(), tra.getSkipCount()));
> }
>   } else {
> SurefireAggregatedReport surefireTestResults = 
> job.getAction(SurefireAggregatedReport.class);
> if (surefireTestResults != null) {
> addBlank = false;
> summary.addTestResult(new TestResult(job, 
> surefireTestResults.getTotalCount(), surefireTestResults.getFailCount(), 
> surefireTestResults.getSkipCount()));
> }
>}
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and 

Newbie: TAP Plugin && Matrix Builds

[Evan Van Dyke]

 

First time Jenkins development, so my apologies for what is probably a 
newbie question...   I am trying to attack JENKINS-22016, in which the TAP 
results are not published correctly for a Matrix project configuration.


I've found the resolution for JENKINS-12205, which solved a similar issue 
for XUnit. It appears the issue is with the Dashboard View's 
"summarizeJob" implementation (see below).   The TAP plugin isn't 
publishing a generic hudson.tasks.test.TestResultProjectAction, and instead 
defines its own ProjectAction class.


What I'm struggling with is how to add a new instance of the 
TestResultProjectAction to the TAP plugin.  

The plugin is already publishing a ProjectAction class, and it implements a 
different API than the generic Hudson one.  

I'm hesitant to just replace the one with the other... and even more 
hesitant to add another special-case to the dashboard plugin to handle TAP.


Any thoughts/suggestions from those familiar with the Jenkins Core? What's 
the best path forward here?

I see three potential paths forward:

1) Replace the TAP Plugin's ProjectAction class with the generic (probably 
best long-term)

2) Descend the TAP Plugin's ProjectAction class from the generic

3) Add a new special-case breakout in the dashboard view


private static void summarizeJob(Job job, TestResultSummary summary) {

  boolean addBlank = true;

  TestResultProjectAction testResults = 
job.getAction(TestResultProjectAction.class);

 

  if (testResults != null) {

AbstractTestResultAction tra = 
testResults.getLastTestResultAction();

 

 if (tra != null) {

addBlank = false;

summary.addTestResult(new TestResult(job, tra.getTotalCount(), 
tra.getFailCount(), tra.getSkipCount()));

}

  } else {

SurefireAggregatedReport surefireTestResults = 
job.getAction(SurefireAggregatedReport.class);

if (surefireTestResults != null) {

addBlank = false;

summary.addTestResult(new TestResult(job, 
surefireTestResults.getTotalCount(), surefireTestResults.getFailCount(), 
surefireTestResults.getSkipCount()));

}

   }

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/abffee1f-2708-4eeb-ac72-50c110c2eeb5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Are backend crawlers still executed?

[Christopher Orr]

> On 03 May 2016, at 00:42, Daniel Beck  wrote:
> 
> 
>> On 26.04.2016, at 08:44, Rouke Broersma  
>> wrote:
>> 
>> Ah yes I was looking for the backend crawler job on the jenkins cloudbees 
>> last week and couldn't find it anywhere, but forgot to ask about it. Good 
>> thing you spotted it too.
> 
> FTR this works again, and has for almost a week.
> 
> The job runs on on a private machine. We'll look into making logs available 
> (*gasp* External Monitor Job?!). For now, if something doesn't work as 
> expected, file an INFRA issue.

The Jenkins job was reinstated (albeit on a private „trusted" machine, as 
mentioned) on the 22nd of April, however the generated files aren’t currently 
being pushed to the mirror network, so you’ll continue to see the old files 
from the 15th of April.
This problem is being tracked here: 
https://issues.jenkins-ci.org/browse/INFRA-662 


If you want to check whether a certain backend-crawler job is creating the 
expected output, you can see the up-to-date results here: 
https://updates.jenkins.io/updates/ 

Regards,
Chris

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5BD48F87-29A7-40C1-9D8C-CCBC48BE4973%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Add multiple build parameters from java code

[icetree521]

For example, I would like to add 2 build parameters from java code of my 
plugin. 

StringParameterDefinition spd = new StringParameterDefinition("id", "");

ParametersDefinitionProperty spdp = new ParametersDefinitionProperty(spd);
p.addProperty(spdp);


StringParameterDefinition spd1 = new StringParameterDefinition("email", "");

ParametersDefinitionProperty spdp1 = new ParametersDefinitionProperty(spd1);

p.addProperty(spdp1);

But the problem is the latter parameter *email* will override the former *id 
*and only the *email* parameter was created. * D*oes anyone know how to fix 
this issue ?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ed263cfd-2785-464f-a5e8-819c7724b6d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failing injected tests for Jenkins plugin

[Andrei Tuicu]

Hello everyone,

I am trying one last time to find an official fix for these problems. If 
not, I'm going to release the plugin as is and perform a new release for 
fixing those particular tests when I find a solution in the future.

Thank you,
Andrei

marți, 19 aprilie 2016, 20:12:18 UTC+3, Andrei Tuicu a scris:
>
> Hello, slide,
>
> Thank you for your response!
>
> The reason why the issue is not assigned to anyone is because I added the 
> wrong component (release-plugin) when I created it, so it got assigned to 
> the person in charge of that particular component. Later, I changed the 
> component and removed the assignee, but I did not know who to assign it to, 
> so I just left it like that hoping it will be picked up. Can you recommend 
> someone to assign it to?
>
> I removed the dependency and changed the parent pom for the plugin, but 
> the first test is still failing. I don't know if the second one is not 
> failing anymore, or if with this configuration maven stops running tests 
> after the first fail.
>
> Thank you,
> Andrei
>
> marți, 19 aprilie 2016, 18:55:43 UTC+3, slide a scris:
>>
>> Just as an FYI, no one probably looked at the issue because it wasn't 
>> assigned to anyone. Do you specifically need version 2.10 of the maven 
>> plugin for your compilation? If not, you can remove that as a dependency. 
>> You may also want to look at using the new 2.x parent pom version for 
>> plugins. 
>>
>> On Tue, Apr 19, 2016 at 8:47 AM Andrei Tuicu  wrote:
>>
>>> Hello everyone,
>>>
>>> I have finished implementing a plugin[1] that integrates Jenkins with 
>>> Jira, but I cannot release it, because two injected tests are failing. I 
>>> did some research, but I could not find a clear indication about how to 
>>> resolve the root causes for them.
>>>
>>> I created an issue in JIRA [2], where I posted the stack traces, steps 
>>> to reproduce, link to the official Jenkins job[3] and other details, but no 
>>> one replied there so I'm trying the mailing list as well.
>>>
>>> The two tests that I'm having trouble with are:
>>>
>>> org.jvnet.hudson.test.PluginAutomaticTestBuilder$CliSanityTest.testCliSanity
>>>
>>> org.jvnet.hudson.test.junit.FailedTest.org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite
>>>
>>> Is there anyone how encountered these problems, or could offer any 
>>> information about what are the root causes of the failing tests and how can 
>>> I fix them?
>>>
>>> Thank you,
>>> Andrei Tuicu
>>>
>>> [1] https://github.com/jenkinsci/JiraTestResultReporter-plugin  
>>> 
>>> [2] https://issues.jenkins-ci.org/browse/JENKINS-34129
>>> [3] 
>>> https://jenkins.ci.cloudbees.com/job/plugins/job/JiraTestResultReporter-plugin/
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkinsci-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAJb%2Bn00fUf-w8Zxfi9r2fbv_SmRDV9uhcb7dBmO73oX%3D-TLUHw%40mail.gmail.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9098ca69-960f-40a8-84f5-a84d1d2bd6ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is there a way to temporarily remove or disable a publisher?

[Jesse Glick]

A plugin should never modify project configuration in the regular course of
a build.

Probably what you want is to just to have your `BuildWrapper` do something
else when its environment is torn down.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1TR_mNDQk%2BDOpudNdrPHjet30VMdperSbYrUL1T1Frmg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Better Jucies - now with releases from GitHub Releases

[Tomas Bjerre]

You may participate in the discussion here:
https://github.com/jucies/releases/issues/15

2016-05-03 12:53 GMT+02:00 Thorsten Scherler :

> Hi Tomas,
>
> I checked your links regarding the plugins. I created a micro site based
> on http://updates.jenkins-ci.org/current/update-center.json you can find
> the source in https://github.com/scherler/jenkins-plugin-site and a demo
> in http://plugin-site.stax.net/ (it is still under development).
>
> It is a simple rendering of the plugin list as taken from
> updates.jenkins-ci.org/current/update-center.json to make the information
> of plugins searchable and filterable.
>
> It is based on a node server that processes the jsonp creates a in.memory
> "poor-mans" database (if you want to go so far to call it db) and then
> serves as REST backend e.g. http://plugin-site.stax.net/plugins or
> http://plugin-site.stax.net/labels. The front end is based on react.js
> and redux.
>
> That would be easy adoptable to pull from different market places. I
> actually think even having the current plugins in a market place would
> allow as well features like rating, favorites, custom grouping, etc.
> Instead of using above jsonp source I would rather use a REST/CORS server
> that provides thus data.
>
> salu2
>
> On Monday, May 2, 2016 at 3:08:42 PM UTC+2, Tomas Bjerre wrote:
>>
>> This is great!
>>
>> I tried to come up with a solution for this myself. The plugins are (in
>> my opinion) the only good thing about Jenkins. I would never use it if it
>> was not for the plugins. A solution like this is needed, so that plugin
>> developers can avoid situations like this:
>>
>>
>> https://groups.google.com/forum/#!searchin/jenkinsci-dev/git-changelog/jenkinsci-dev/Jsck8GgWwJg/GAZV8Y0-CAAJ
>>
>> Competition is a good thing. But competition is not allowed among Jenkins
>> plugins. Its very frustrating when you dont want to contribute to an
>> existing plugin. Perhaps because of the way a problem is solved in an
>> existing one. If you want to solve the same problem, or similar, in a
>> different way, you will be denied. Or forced to merge you code into the
>> existing one. Like in my case with the git-changelog-plugin. It is now
>> causing confusion among users.
>>
>> I'd like to see an independent marketplace where plugins can be
>> published, rated and reviewed. Just like the Atlassian Marketplace works. I
>> started working on something like that (
>> https://github.com/tomasbjerre/jenkins-plugins/ and
>> http://www.jenkins-plugins.com/) but have not had time to finish it.
>>
>> -Tomas
>>
>> Den torsdag 28 april 2016 kl. 12:44:59 UTC+2 skrev Sergei Egorov:
>>>
>>> Hey everyone,
>>>
>>> Remember Jucies? ( https://github.com/jucies/releases ) - experimental
>>> update center for Jenkins with releases directly from GitHub?
>>>
>>> Today it became much better!
>>>
>>> Starting from today, GitHub releases will be used to release your
>>> plugin. That said, no publish, no PRs to update your plugin's version. Just
>>> create a release on GitHub and it will be hooked up by Jucies in a few
>>> minutes.
>>>
>>> For example, here is Pipeline View plugin released on Jucies:
>>>
>>> https://github.com/jucies/releases/blob/master/plugins/pipeline-view.properties
>>>
>>> As you can see - no version here, only repository reference, where
>>> release exists:
>>> https://github.com/jenkinsci/pipeline-view-plugin/releases
>>>
>>>
>>>
>>> Also, I'm happy to say that Build Graph Plugin and Build Name Setter
>>> Plugin were using Jucies to release their plugins as well. Wooo!
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/lL1etDkbwvg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/bd46e706-e131-4956-b42c-7e56db1234ab%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAK89W5KD_ue%2Bvfi2fWkJsbVTbxUyq0uc-LA34CLOrTdsrCeNdw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Better Jucies - now with releases from GitHub Releases

[Thorsten Scherler]

Hi Tomas,

I checked your links regarding the plugins. I created a micro site based on 
http://updates.jenkins-ci.org/current/update-center.json you can find the 
source in https://github.com/scherler/jenkins-plugin-site and a demo in 
http://plugin-site.stax.net/ (it is still under development).

It is a simple rendering of the plugin list as taken from 
updates.jenkins-ci.org/current/update-center.json to make the information 
of plugins searchable and filterable.

It is based on a node server that processes the jsonp creates a in.memory 
"poor-mans" database (if you want to go so far to call it db) and then 
serves as REST backend e.g. http://plugin-site.stax.net/plugins 
or http://plugin-site.stax.net/labels. The front end is based on react.js 
and redux.

That would be easy adoptable to pull from different market places. I 
actually think even having the current plugins in a market place would 
allow as well features like rating, favorites, custom grouping, etc. 
Instead of using above jsonp source I would rather use a REST/CORS server 
that provides thus data.

salu2

On Monday, May 2, 2016 at 3:08:42 PM UTC+2, Tomas Bjerre wrote:
>
> This is great!
>
> I tried to come up with a solution for this myself. The plugins are (in my 
> opinion) the only good thing about Jenkins. I would never use it if it was 
> not for the plugins. A solution like this is needed, so that plugin 
> developers can avoid situations like this:
>
>
> https://groups.google.com/forum/#!searchin/jenkinsci-dev/git-changelog/jenkinsci-dev/Jsck8GgWwJg/GAZV8Y0-CAAJ
>
> Competition is a good thing. But competition is not allowed among Jenkins 
> plugins. Its very frustrating when you dont want to contribute to an 
> existing plugin. Perhaps because of the way a problem is solved in an 
> existing one. If you want to solve the same problem, or similar, in a 
> different way, you will be denied. Or forced to merge you code into the 
> existing one. Like in my case with the git-changelog-plugin. It is now 
> causing confusion among users.
>
> I'd like to see an independent marketplace where plugins can be published, 
> rated and reviewed. Just like the Atlassian Marketplace works. I started 
> working on something like that (
> https://github.com/tomasbjerre/jenkins-plugins/ and 
> http://www.jenkins-plugins.com/) but have not had time to finish it.
>
> -Tomas
>
> Den torsdag 28 april 2016 kl. 12:44:59 UTC+2 skrev Sergei Egorov:
>>
>> Hey everyone,
>>
>> Remember Jucies? ( https://github.com/jucies/releases ) - experimental 
>> update center for Jenkins with releases directly from GitHub?
>>
>> Today it became much better!
>>
>> Starting from today, GitHub releases will be used to release your plugin. 
>> That said, no publish, no PRs to update your plugin's version. Just create 
>> a release on GitHub and it will be hooked up by Jucies in a few minutes.
>>
>> For example, here is Pipeline View plugin released on Jucies:
>>
>> https://github.com/jucies/releases/blob/master/plugins/pipeline-view.properties
>>
>> As you can see - no version here, only repository reference, where 
>> release exists:
>> https://github.com/jenkinsci/pipeline-view-plugin/releases
>>
>>
>>
>> Also, I'm happy to say that Build Graph Plugin and Build Name Setter 
>> Plugin were using Jucies to release their plugins as well. Wooo!
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/bd46e706-e131-4956-b42c-7e56db1234ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Updating Jenkins test results in ALM [ New ]

[Jaroslav Štreit]

Hello, is it moved already to Jenkins Users group somewhere?

I have same problem - INFO: No Test Report found.

I tried put testng-results.xml file everywhere and it just dont load it... 
where it should be located? By default is in target\surefire-reports\


Dne čtvrtek 7. ledna 2016 9:31:18 UTC+1 Nils op den Winkel napsal(a):
>
> Hi, 
>
> I had the same problem yesterday. Is your job running on a slave? Digging 
> in the sourcecode of the plugin, I found out, that it is looking for the 
> test results in the job directory on the master instead of the workspace on 
> the slave. Archiving the testresults in a previous post build action was a 
> workaround for me, but then I hit 
> https://issues.jenkins-ci.org/browse/JENKINS-32004
>
>
> Regards
>
>
> Nils
>
> 2016-01-07 8:54 GMT+01:00 SAI KIRAN :
>
>>
>> Hi,
>>
>> I am trying to run a suite in Jenkins and update those test results in 
>> ALM (Pass/Fail)
>>
>> But, I am unable to update to ALM.
>>
>>  
>>
>> Which location should I give in* Testing Result File* in Jenkins
>>
>> Testing result file
>>
>>  
>>
>> Error **  
>>
>> INFO: 'Upload test result to ALM' Post Build Step is being invoked.
>> INFO: No Test Report found.
>>
>>  
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/69baa092-e827-4b39-8ebe-b5a6f27bbbce%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/05a5dcad-fcc2-4945-861f-d0f3f8ee76c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Which Extension points should I use to do some job after each build?

[Daniel Beck]

> On 03.05.2016, at 08:25, icetree521  wrote:
> 
> Usually We will extend the hudson.tasks.Notifier or hudson.tasks.Publisher, 
> but both of them will add a visible step(I mean UI part) into the Post-build 
> action section, is there any extension point that only do the job on 
> background after each build but without any visible UI ? 

Depending on what exactly you want to do, BuildListener, RunListener, or 
BuildStepListener come to mind.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/AC072805-CD55-4D4A-A849-A1EC8FA9EF3C%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Which Extension points should I use to do some job after each build?

[icetree521]

Usually We will extend the *hudson.tasks.Notifier* or *hudson.tasks.Publisher, 
*but both of them will add a visible step(I mean UI part) into the *Post-build 
action* section, is there any extension point that only do the job on 
background after each build but *without* any visible UI ? 

thx!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/efef495c-31be-4e29-aa0c-d4ca8e15d06d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.