Re: Jenkins Xtreme Feedback Utility
Thanks for forking. I changed the name to rss-retaliation since it is not a plugin. Would it be possible to add the Pull Request Builder and a CI-Job for the repository? Thanks in advance, Stefan Am Freitag, 25. April 2014 19:50:55 UTC+2 schrieb Daniel Beck: > > It's not a plugin. > > On 25.04.2014, at 17:37, Ulli Hafner > > wrote: > > > https://github.com/jenkinsci/rss-retaliation-plugin > > > > Stefan, you should join us on IRC than you would be able to fork by your > own :-) > > > > Ulli > > > > Am 25.04.2014 um 13:55 schrieb Stefan Wolf > > >: > > > > >> Hi, > >> > >> I build a small standalone application which polls the Jenkins RSS-Feed > in order to control a few Feedback devices. Currently supported are the > Dream Cheeky Missile Launcher, the Cleware USB Traffic Light and the Google > text-to-speech API. For more Information see the read me on github: > https://github.com/wolfs/jenkins-rss-retaliation > >> > >> I would like to host the repository and the binaries within the jenkins > infrastructure. Could you please fork the repository into the jenkinsci > github organization? I would then release the binaries into the Jenkins > repositories, if this would be OK. > >> > >> Best regards, > >> > >> Stefan Wolf > >> > >> > >> -- > >> 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-use...@googlegroups.com . > >> For more options, visit https://groups.google.com/d/optout. > > > > -- 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. For more options, visit https://groups.google.com/d/optout.
Jenkins Xtreme Feedback Utility
Hi, I build a small standalone application which polls the Jenkins RSS-Feed in order to control a few Feedback devices. Currently supported are the Dream Cheeky Missile Launcher, the Cleware USB Traffic Light and the Google text-to-speech API. For more Information see the read me on github: https://github.com/wolfs/jenkins-rss-retaliation I would like to host the repository and the binaries within the jenkins infrastructure. Could you please fork the repository into the jenkinsci github organization? I would then release the binaries into the Jenkins repositories, if this would be OK. Best regards, Stefan Wolf -- 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. For more options, visit https://groups.google.com/d/optout.
Re: AggregatedTestResult inconsistencies/problems
The pull request is now https://github.com/jenkinsci/jenkins/pull/916.
Am Freitag, 23. August 2013 15:41:15 UTC+2 schrieb Stefan Wolf:
>
> Hi,
>
> after trying to use the feature "Aggregate Downstream Test Results", i.e.
> the AggregatedTestResultPublisher, I ran into some problems. The main
> problem is fixed by my pull request
> https://github.com/jenkinsci/jenkins/pull/915, namely that clicking the
> "Latest Test Result" link on the Project page does not return a 404
> anymore. I tried to document the current behaviour of the feature with a
> "Unit" test:
> https://github.com/wolfs/jenkins/blob/aggregate-test-result/test/src/test/java/hudson/tasks/test/AggregatedTestResultPublisherTest.java
> .
> When merging this pull request the behaviour is:
> 1. Only aggregated test results:
> - On the project page there is a link with name "Latest Test Result" which
> goes to the aggregated test result page on the corresponding build
> 2. Only test results:
> - On the project page there is a link with name "Latest Test Result" which
> goes to the test result page of the corresponding build
> 3. Aggregated test results and test results
> - On the project page there is a link with name "Latest Test Result" which
> goes to the test result page of the corresponding build
>
> Moreover, there is not test result trend for the aggregated test result
> action.
> My proposal how to make this consistent would be:
> - If the link on the project page goes to the aggregated test result page
> then it should be named "Latest Aggregated Test Result"
> - If there are test results and aggregated test results then there should
> be two links, one name "Latest Test Result" and one named "Latest
> Aggregated Test Result"
> - There should be a Trend for the aggregated test results on the project
> page
>
> If there are no objections, then I would go forward implementing this.
>
> For the implementation I would like to get some suggestions:
> - Would it make sense if the TestResult from the
> AggregatedTestResultPublisher would extend AggregatedTestResult?
> - In the current implementation there is a method
> 'getAggregatedTestResultAction' on the AbstractBuild class which never
> yields the TestResult of the AggregatedTestResultPublisher. The
> AggregatedTestResultAction yielded from this method has the urlName
> 'testResult'. The TestResultAction of the AggregatedTestResultPublisher is
> not an AggregatedTestResultAction and has the urlName
> 'aggregatedTestResult'. Therefore, the old implementation on main.jelly on
> AbstractProject did not really make sense to me:
>
>
>
>
> ${%Latest Test Result}
>
>
>
>
>
> value="${it.lastCompletedBuild.aggregatedTestResultAction}"/>
>
>
> class="model-link inside">${%Latest Aggregated Test Result}
>
>
>
> Should the UI use getAction with the corresponding classes?
> - This main.jelly should not be used from any of the classes using the
> AggregatedTestResultAction (MavenModuleSet, MatrixProject). Is this
> correct? So can I just change the jelly file without breaking anything?
> - What do I have to do in order to add the Trend Report for the aggregated
> test result to the project page?
>
> Thank you for reading to the end,
> Stefan
>
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
AggregatedTestResult inconsistencies/problems
Hi,
after trying to use the feature "Aggregate Downstream Test Results", i.e.
the AggregatedTestResultPublisher, I ran into some problems. The main
problem is fixed by my pull
request https://github.com/jenkinsci/jenkins/pull/915, namely that clicking
the "Latest Test Result" link on the Project page does not return a 404
anymore. I tried to document the current behaviour of the feature with a
"Unit"
test:
https://github.com/wolfs/jenkins/blob/aggregate-test-result/test/src/test/java/hudson/tasks/test/AggregatedTestResultPublisherTest.java.
When merging this pull request the behaviour is:
1. Only aggregated test results:
- On the project page there is a link with name "Latest Test Result" which
goes to the aggregated test result page on the corresponding build
2. Only test results:
- On the project page there is a link with name "Latest Test Result" which
goes to the test result page of the corresponding build
3. Aggregated test results and test results
- On the project page there is a link with name "Latest Test Result" which
goes to the test result page of the corresponding build
Moreover, there is not test result trend for the aggregated test result
action.
My proposal how to make this consistent would be:
- If the link on the project page goes to the aggregated test result page
then it should be named "Latest Aggregated Test Result"
- If there are test results and aggregated test results then there should
be two links, one name "Latest Test Result" and one named "Latest
Aggregated Test Result"
- There should be a Trend for the aggregated test results on the project
page
If there are no objections, then I would go forward implementing this.
For the implementation I would like to get some suggestions:
- Would it make sense if the TestResult from the
AggregatedTestResultPublisher would extend AggregatedTestResult?
- In the current implementation there is a method
'getAggregatedTestResultAction' on the AbstractBuild class which never
yields the TestResult of the AggregatedTestResultPublisher. The
AggregatedTestResultAction yielded from this method has the urlName
'testResult'. The TestResultAction of the AggregatedTestResultPublisher is
not an AggregatedTestResultAction and has the urlName
'aggregatedTestResult'. Therefore, the old implementation on main.jelly on
AbstractProject did not really make sense to me:
${%Latest Test Result}
${%Latest Aggregated Test Result}
Should the UI use getAction with the corresponding classes?
- This main.jelly should not be used from any of the classes using the
AggregatedTestResultAction (MavenModuleSet, MatrixProject). Is this
correct? So can I just change the jelly file without breaking anything?
- What do I have to do in order to add the Trend Report for the aggregated
test result to the project page?
Thank you for reading to the end,
Stefan
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Hudson to Jenkins
Hi Marcel, would you mind putting your scripts in the Wiki or in some git-project? I think they would be interesting for quite some people. Kind regards, Stefan Am Dienstag, 15. Mai 2012 08:33:48 UTC+2 schrieb Marcel Schutte: > > Hi > > I recently did this, it's not straightforward because Hudson 2.2 uses a > different xml format for its config. With the help of some xsl I managed to > do it. At the moment I am abroad, but I can send them tomorrow if you are > interested. > > Regards,Marcel > > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Automatic diagram
Hi Domi, Merged and released. When I have some time I should probably work on the layout algorithm. It seems to me that it is not really Sugiyama, because the quality is far from the one of graphviz, which should be the same. Regards, Stefan On Friday, November 16, 2012 4:56:29 PM UTC-3, domi wrote: > > Hi Stefan, > > Thanks for taking picking up the idea of using JavaScript instead of > graphviz! > > Some feedback: > > I just send you two pull requests... > > - https://github.com/jenkinsci/depgraph-view-plugin/pull/4 > this one is not a big thing, just makes my life a bit easier in eclipse > :) > > - https://github.com/jenkinsci/depgraph-view-plugin/pull/5 > this one would actually allow me to use the plugin in my environment, > because it allows to disable the rendering with graphviz at all. I need > this, because I will never be able to install graphviz in our setup. So I'm > really hopping you can do a release with this functionality soon. :) > > Issues: > If there are circular job dependencies, then all the jobs are displayed at > the same position (like a stack) > > Although the current JavaScript implementation is not yet perfect, a new > release would already help me a lot! > > thanks! > Domi > > > > On 13.11.2012, at 16:08, Stefan Wolf > > wrote: > > Hi all, > > I just released a new version of the > https://wiki.jenkins-ci.org/display/JENKINS/Dependency+Graph+View+Plugin > It includes an experimental visualisation via jsPlumb based on domis work. > Please give me feedback how to improve the javascript visualisation and the > plugin in general. Feature and Pull requests are welcome. > > Best regards, > Stefan > > On Wednesday, September 5, 2012 4:14:20 AM UTC-3, kikou wrote: >> >> Hi all >> >> Is there any plugin which draw automatically a diagram showing the job >> sequence ? >> So that it is more easy to show to some people the >> >> i dont like the format of pipeline view and it is more to show the result >> of last builds than the sequence. >> >> >> Rgds >> K. >> > >
Re: New release of Dependency Graph View Plugin with experimental Javascript visualisation
I just released version 0.6. Could you try this one? On Wednesday, November 14, 2012 6:33:23 AM UTC-3, David Resnick wrote: > > Hi Stefan, > > I upgraded to the new version that includes jsplumb. It doesn't seem to be > working; the jsplumb tab shows a blank area, though the Json format link > displays a json representation of my dependencies. > > Let me know if there is any further information you need. > > I'm attempting to view the diagram with Firefox 16.0.1 on Windows 7. > > - David > > On Tuesday, November 13, 2012 5:22:17 PM UTC+2, Stefan Wolf wrote: >> >> Hi together, >> >> I just released a new version of the >> https://wiki.jenkins-ci.org/display/JENKINS/Dependency+Graph+View+Plugin. >> This version includes an experimental visualisation via jsPlumb based on >> work by domi. Since I am pretty new to javascript it would be very helpful >> to get some feedback on this functionally, both from end-users and from >> developers. >> So please send your comments, feature and pull requests! >> >> Best regards, >> Stefan >> >
New release of Dependency Graph View Plugin with experimental Javascript visualisation
Hi together, I just released a new version of the https://wiki.jenkins-ci.org/display/JENKINS/Dependency+Graph+View+Plugin. This version includes an experimental visualisation via jsPlumb based on work by domi. Since I am pretty new to javascript it would be very helpful to get some feedback on this functionally, both from end-users and from developers. So please send your comments, feature and pull requests! Best regards, Stefan
Re: Automatic diagram
Hi all, I just released a new version of the https://wiki.jenkins-ci.org/display/JENKINS/Dependency+Graph+View+Plugin It includes an experimental visualisation via jsPlumb based on domis work. Please give me feedback how to improve the javascript visualisation and the plugin in general. Feature and Pull requests are welcome. Best regards, Stefan On Wednesday, September 5, 2012 4:14:20 AM UTC-3, kikou wrote: > > Hi all > > Is there any plugin which draw automatically a diagram showing the job > sequence ? > So that it is more easy to show to some people the > > i dont like the format of pipeline view and it is more to show the result > of last builds than the sequence. > > > Rgds > K. >
Re: Automatic diagram
Hi, since I am the maintainer and creater of the plugin, I would not say that it is not maintained anymore. I hopefully will find some time soon to restructure the code in a way to make it better extensible. I also was looking for a possibility to layout the graph without resorting to graphviz, but I was not able to find a solution in java or javascript. If you know a good library which provides a similar functionality as graphviz, then please tell me. Regards, Stefan On Wednesday, September 26, 2012 9:16:27 AM UTC-3, kikou wrote: > > Hello > sorry for this late answer > > I didnt pay attention but indeed it is working > Nevertheless i found pity that we need another graphical lib, i am sure > that a plugin could be done with java tools only or html object, i really > prefer a plugin which not needs external binaries. > > K. > > Le mercredi 5 septembre 2012 15:23:40 UTC+2, Mark Waite a écrit : >> >> We use that plugin very frequently and it works great for us. Why do you >> say "what a pity that this plugin is not maintained"? We've not found any >> cases where it had bugs or issues that blocked our work, and I don't recall >> any recent complaints from other users either. >> >> Can you describe further why you think it might need an update? >> >> Mark Waite >> >>*From:* kikou >> *To:* jenkins...@googlegroups.com >> *Sent:* Wednesday, September 5, 2012 5:20 AM >> *Subject:* Re: Automatic diagram >> >> Hi Gergo >> >> Thank you. The plugin you gave is exaclty what i am looking for. >> I maybe do a missunderstanding but it is the dependancy indeed i'd like >> to have in a graph showing the sequence of projects (not build number), in >> other words seeing upstream and downstream projects in one graph. >> >> what a pitty that this plugin is not maintained. Yes maybe i could update >> it but not now. >> >> Thank you a lot Gergo >> >> Rgds >> K. >> >> Le mercredi 5 septembre 2012 12:15:51 UTC+2, Gergo a écrit : >> >> Hi, >> You mention "job sequence" but if you mean "build sequence" - I don't >> think it's predictable/static as it depends on dynamic factors (e.g >> availability of slaves, build duration changes affect allocation). >> Not exactly sure about your requirements, but I'm using Dependency Graph >> View: >> http://wiki.hudson-ci.org/display/HUDSON/Dependency+Graph+View+Plugin , >> this seems to be how far you can get solely looking at the jobs. >> >> hth, >> Gergo >> >> On Wed, Sep 5, 2012 at 8:14 AM, kikou wrote: >> >> Hi all >> >> Is there any plugin which draw automatically a diagram showing the job >> sequence ? >> So that it is more easy to show to some people the >> >> i dont like the format of pipeline view and it is more to show the result >> of last builds than the sequence. >> >> >> Rgds >> K. >> >> >> >> >>
