Skip to content

Conversation

kayabendroth-epages
Copy link

No description provided.

@gongo
Copy link

gongo commented Jun 8, 2015

👍

@elgalu elgalu mentioned this pull request Jun 8, 2015
@ghost
Copy link

ghost commented Jun 8, 2015

I am prepping the branch naming and docker hub build tags for 2.46.0

ghost pushed a commit that referenced this pull request Jun 8, 2015
…rsion-2.46.0

Upgrade to Selenium version 2.46.0.
@ghost ghost merged commit 52233f0 into SeleniumHQ:master Jun 8, 2015
@ghost
Copy link

ghost commented Jun 8, 2015

Some housekeeping @kayabendroth-epages Have you signed the CLA as described in CONTRIBUTING.md?
Please indicate here. Thanks.

@mtscout6
Copy link
Member

mtscout6 commented Jun 9, 2015

Some folks on IRC are asking about this, was node-firefox missed: https://registry.hub.docker.com/u/selenium/node-firefox/tags/manage/

@ghost
Copy link

ghost commented Jun 9, 2015

Ooops. I missed it. fixed

  • General setup: I setup all Automated Build on docker hub to build on branch names so as we move forward we advance the branch: master branch builds latest and 2.46.0 branch builds 2.46.0 image.
  • The Issue: I am finding with docker hub Automated Build triggers they don't run in predictable sequence as we need them: First build base, then (hub and node-base) then (node firefox and chrome) and so on. (this produces errors like this)
    • I am not sure if there is a 'sequence' trigger builder I can apply so we always build 'base' first and then it should trigger downstream builds.

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants