Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tags for the docker #2

Closed
rajesh99 opened this issue Dec 5, 2017 · 13 comments
Closed

tags for the docker #2

rajesh99 opened this issue Dec 5, 2017 · 13 comments

Comments

@rajesh99
Copy link

rajesh99 commented Dec 5, 2017

Hello,
Thanks for upgrading to maven 3.5.2
Is there a possibility, that you can create tags for the docker.

@rajesh99 rajesh99 changed the title Docker tags for the docker Dec 5, 2017
@markhobson
Copy link
Owner

Hi, what tags would you like to see?

@rajesh99
Copy link
Author

rajesh99 commented Dec 5, 2017 via email

@markhobson
Copy link
Owner

Chrome is always going to be the latest version and thus ChromeDriver needs to be too. Maven is very stable so you shouldn't be affected by minor upgrades. If I upgrade to Java 9 then I'll create tags for Java 8 & 9. Hope that helps to clarify.

@rajesh99
Copy link
Author

rajesh99 commented Dec 7, 2017 via email

@markhobson
Copy link
Owner

Not easily as Chrome is an 'evergreen' browser, meaning that it keeps itself up-to-date. It's rarely useful to be on an old version of a browser when acceptance testing since users will typically be on the latest version.

@markhobson
Copy link
Owner

I'm going to close this for now. You can of course build and push your own image of this container if you want to fix Chrome at a specific version.

@aswath-veersoft
Copy link

My tests failed because of latest headless changes. Can you provide docker tags. Thanks.

@markhobson
Copy link
Owner

Can you update your tests to supply the --headless option to Chrome? See BrowserTest for an example.

@rajesh99
Copy link
Author

I wish tags were supported for the image. We would have saved some time.

@markhobson
Copy link
Owner

As mentioned above I can't provide tags for Chrome versions as only the latest version is available in the PPA. I can branch the previous Xvfb version of this container if that would help? I didn't do this as I don't have time to support multiple configurations.

@rajesh99
Copy link
Author

No, thats fine. For now, I created my own dockerimage based on your previous Dockerfile commit.

@rajesh99
Copy link
Author

I don't like the chrome moving part in the dockerfile. Anyhelp on that would be great.

@markhobson
Copy link
Owner

We would need a PPA that holds historic versions of Chrome since Google removes old versions from theirs. Personally I want to run my tests against the latest version as that's what users will be using.

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

No branches or pull requests

3 participants