I don't think that plugin is going to need many changes anyway, and I am
not planning to really do any development on it. I am willing to review
pull requests and respond to issues if they might come up but the plugin is
pretty much finished as is IMO.
I have some ideas to merge this plugin
Ping
--
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
Noticed a PR on https://github.com/jenkinsci/chromedriver-plugin/pull/4
that hasn't seen any attention which is understandable since the only
person that did any significant work on it was kohsuke.
Can someone please merge this or grant me access so I can do it myself? If
granted commit rights
A contributor to a plugin I am a maintainer for (but do not really have
time to contribute to) has sent a pull request with some good changes.
However, the plugin has a dependency that was updated. That dependency
seems to override a test harness dependency according to the contributor,
which
Thank you! Looks good. Especially the blogpost at the bottom of that page
about the Microsoft partnership was enlightening.
On Tuesday, February 21, 2017 at 1:32:09 PM UTC+1, Daniel Beck wrote:
>
>
> > On 21.02.2017, at 13:12, rouke.b...@infosupport.com
> wrote:
> >
> > Is there any
Is there any documentation on the change to ci.jenkins.io? The only thing I
can find right now is this
thread: https://groups.google.com/forum/#!topic/jenkinsci-dev/439-IDYNSVY
about a trial on using ci.jenkins.io to figure out what's required for
moving to azure.
On Tuesday, February 21,
I am unsure where to request Java 8 builds for the selenium jenkins plugin,
so I'll ask here.
The selenium jenkins plugin needs Java 8 because selenium itself needs java
8 and the plugin has a dependency on the selenium package.
Git url: https://github.com/jenkinsci/selenium-plugin/pulls
--
Hi, I'm the current maintainer of this plugin.
Most likely you have not opened port for outside connections on the
machine where your selenium hub is running, so the selenium node cannot
connect to it.
On Saturday, July 16, 2016 at 4:38:01 PM UTC+2, vali vali wrote:
>
> Hi,
>
> When I
Yea I figured as much, thanks :/
--
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
Does anyone have any idea if this is possible in any way?
On Friday, June 10, 2016 at 7:20:33 PM UTC+2, Rouke Broersma wrote:
>
> I am a maintainer of the selenium grid plugin, and as part of our plugin
> we start potentially multiple processes on slaves (selenium nodes
Um what? Pipeline builds have nothing whatsoever to do with the plugin. The
plugin starts a process on boot that anyone can freely use, has nothing to
do with builds.
On Fri, Jun 10, 2016, 21:30 Jesse Glick <jgl...@cloudbees.com> wrote:
> On Fri, Jun 10, 2016 at 1:20 PM, Rouke Broersma
I am a maintainer of the selenium grid plugin, and as part of our plugin we
start potentially multiple processes on slaves (selenium nodes, as part of
a distributed selenium grid).
We have implemented the RestartListener to shutdown all our selenium nodes
on the slaves when Jenkins is
What would your plugin need to do? If your framework uses java, selenium
and cucumber then testers can use maven, gradle, ant or commandline scripts
to run the tests. If your framework outputs test results in cucumber format
then there are multiple jenkins plugins available to display test
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.
On Monday, April 25, 2016 at 2:46:22 PM UTC+2, Julien HENRY wrote:
>
> Hi guys,
>
> We have deployed SonarQube Scanner
Any progress on this request? Anything else I should do?
On Tuesday, April 12, 2016 at 12:14:29 PM UTC+2, Rouke Broersma wrote:
>
> I have tried contacting the current maintainer but have received no reply
> for some weeks.
> I am finally happy with the changes I have made and thin
I have tried contacting the current maintainer but have received no reply
for some weeks.
I am finally happy with the changes I have made and think they could be
merged.
I have even been contacted by a plugin user who has asked me to continue
working on my changes, and who has helped test the
I have figured out that the forkCount=0 was defined in pluginManagement
instead of plugins and was therefore never applied.
--
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,
Is there anyone that can help me out with this concurrency on maven
surefire that should not be happening but is happening anyway?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails
Version 2.48.2 pr not requiring jenkins maven
update: https://github.com/jenkinsci/selenium-plugin/pull/55
Version 2.53.0 pr requiring jenkins maven
update: https://github.com/jenkinsci/selenium-plugin/pull/56
--
You received this message because you are subscribed to the Google Groups
I have made two pr's. One updates to the latest available selenium version
(latest available in the jenkins maven repo is 2.48.2), and another updates
to the actual latest version 2.53.0.
The pr for the version that already exists in the maven repo just needs to
be merged and a new plugin
Finally found in this
pr: https://github.com/jenkinsci/selenium-plugin/pull/24
That indeed the dependency needs to be pushed to the jenkins maven repo for
any version update to work, by someone with access to do this...
By running mvn package in dist-server-standalone/
This does not at all seem
After reviewing the issue more, it seems like the plugin maintainer used to
run the dist-server-standalone install build step manually, to install the
selenium-server-standalone jar to the jenkins maven repository, but I
cannot do this as I am not authorized, nor do I think this is the correct
I could really use some help on the selenium grid
plugin: https://github.com/jenkinsci/selenium-plugin
I'm trying to bump the version number, the plugin seems to rely on
selenium-server-standalone, but this package is no longer published to
maven.
As a workaround the plugin seems to have a
Pull request has since been merged. Cheers!
On Tuesday, March 22, 2016 at 9:29:19 AM UTC+1, Rouke Broersma wrote:
>
> Hi, I love if someone had time to look at my pull request and provide
> feedback and or merge it. Thank you.
>
> Pull request: https://github.com/jenkinsci/backe
Hi, I love if someone had time to look at my pull request and provide
feedback and or merge it. Thank you.
Pull request: https://github.com/jenkinsci/backend-crawler/pull/50
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe
25 matches
Mail list logo
