I write e2e-Tests for a Web-Application with playwright. Now I have made a update to version 1.29.2.
Have anyone the same problem and maybe a solution?
The marked Register should be on the top of the Site.
Related
I am trying to upgrade Jenkins from version 2.176.1 to 2.375.2. I tried two methods and both of them failed.
Method-1: Download the jenkins.war and copy it into /usr/lib/jenkins/ directory by replacing the original one. After copying, when I restart Jenkins, it simply fails to restart.
Method-2: Upgrade Jenkins' RPM using yum update jenkins. This command runs successfully and process exists without any error. But, again when I restart Jenkins, it fails to start.
CentOS version: CentOS-7
First of all - I can only support opinion of Dmitriy Tarasevich about reading upgrade guides. You can find theme here: https://www.jenkins.io/doc/upgrade-guide/
Then - stick to the version upgrade process that you've used previously (or for the first time with installation). If you did install it via .*war, don¨t worry and use your Method-1. On the other hand, if you used yum, stick to that method-2.
Then - such a "big" upgrade at once from 2.176.1 to 2.375.1 is, I'd say, the reason it's failing for you as the version in between contain several major/breaking changes (our team has faced the same problem (we "just" wanted to bump the versions too much after a long time of no upgrading and we've faced several problems we weren't able to solve together). So it was necessary to split it into several independent upgrades which appeared to be doable and we managed to get to LTS 2.375).
To summarize recommended steps - I'd you need to:
1/ Split your upgrade into several steps and upgrade LTS more gradually: try to upgrade to first to some not-current LTS version. I believe something less than or precisely 2.303.3 could work and see if you can start it.
then actually run Jenkins and check administration page,
upgrade your plugins (if you want). FYI: this is recommended officially in Jenkins docs after every Jenkins core upgrade.
check Jenkins administration page and apply necessary changes / manage necessary decision that might appear there (if applicable).
2/ Try to upgrade to a higher LTS version (repeat step 1 with its sub-steps)
To be a very specific and give some examples (although I don't remember everything by hearth):
you skipped a gradually upgrade to version 2.319 LTS that brings a major change of working with master node --> built-in node that needs to be applied (confirmed) from within the administration section of Jenkins (see docs: https://www.jenkins.io/doc/book/managing/built-in-node-migration/ )
version 2.332.1 LTS brings an important change. I would say that you've hit exactly this issue (covered here): https://community.jenkins.io/t/jenkins-cant-find-java-after-update-running-on-centos-7/3615 - exact steps and more resources are within that thread and also here: https://www.jenkins.io/doc/upgrade-guide/2.332/#upgrading-to-jenkins-lts-2-332-1
from version 2.361 LTS Jenkins requires Java 11 or higher (see docs https://www.jenkins.io/doc/upgrade-guide/2.361/ ). So - you will need to ensure that you have a proper Java installed (you already might have it though). Including your agents!. Otherwise you would start your Jenkins but it would not connect any agent (usually undesired state).
Please, try to make some gradual progress and let us know where you managed to get
I want to use the vaadin UI java framework in my quarkus framework, But I am unsuccessful in that. when I am loading any static resources(CSS, js, etc..) files it is not getting loaded And I guess not even default CSS is getting applied to the UI components, I am new to this framework, If anyone wants to suggest, please.
Here is the sample demo UI project which I am trying to implement.
[https://harshithpawarg#bitbucket.org/harshithpawarg/quarkus_vaadin.git][1]
run Command: $. mvn clean install && mvn compile quarkus:dev -pl ui
Vaadin is working on an integration with Quarkus. The target version is Vaadin 22. They might already have something running on Vaadin 21.
The current work can be seen in the GitHub repository of the extension and the repository of the project base.
Update: Vaadin 22 is released as a non-LTS version and integrates Quarkus.
As far as I know, Vaadin doesn't yet support Quarkus (see https://github.com/vaadin/flow/issues/5485).
However, experimental Quarkus extensions to use Vaadin with Quarkus are available here and here.
Why don’t you make a Quarkus backend and another Java project with Vaadin which communicates via Rest with the backend ?
I was able to get Vaadin 14 (vaadin-demo-business-app) working as native image in production mode using the quarkus-vaadin-lib example.
I did use the native-image-agent to generate the META-INF/native-image json files and added wildcard entries in resource-config.json
{
"resources":[
{"pattern":"META-INF/VAADIN.*"},
{"pattern":"META-INF/resources.*"},
Only dev mode is harder, when running in Quarkus the browser can't resolve the frontend through webpack:// and webpack-internal:// and I do not know how to achieve this.
But this can work as long as you can keep the modules using Vaadin compatible to run as normal war, and compile the end product into a Quarkus+GraalVM executable. Only you can't use Quarkus specific code in the web ui modules then which still makes it all a bit hacky.
I have WampServer Version 3.1.4 64bit installed on Windows 7 and it comes with PHP versions php5.6.38, php7.0.32, php7.1.22, and php7.2.10. I would like to use php5.6.x rather than php7.x.
So, when I switch from php7.2.10 to php5.6.38 from the server tray icon; it does not update the actual php version which is shown by phpinfo().
On localhost, it still says:
PHP Version: 7.2.10
However, it is updated on CLI side. This is tested with running this in the cmd:
php -v
The result is :
c:\wamp64\bin\apache\apache2.4.35\bin>php -v
PHP 5.6.38 (cli) (built: Sep 13 2018 12:45:08)
Copyright (c) 1997-2016 The PHP Group
Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies
After restarting WAMP services, and re opening the terminal, and restarting computer, it still not updated through phpinfo. It probably related the php version used by Apache service. How can I change this to 5.6.x
Any suggestions ?
Many thanks
Note : The issue is not related with changing php cli version as it was pointed here. I do not understand why some of them insist that this is potential duplication without reading the post carefully.
I have faced kind of similar issue, I have installed wampserver upgrades from https://wampserver.aviatechno.net/?lang=en. I needed php 7.3 and 7.4, after installing the php upgrades, those new versions were not being reflected in wampserver traymenu (left click on wamp icon->php-versions). After spending quite some time looking into this, finally could fix this by following steps :
Clearing logs (right click on wampserver icon -> tools -> empty logs)
[my php log file was 300+ MB].
Restarted wampserver and it was good to go.
I found solution from this thread http://forum.wampserver.com/read.php?2,159184
(TL:DR) Use left click -(instead of right click)- menu to change PHP versions.
(Long explanation)
Hi, this happened to me today. I was trying to change the php version from 7.2 to 5.6 to test something. However, Wampserver was not changing the web version of php. After much searching in the web and noticing in certain videos that some people were getting a different menu than me in the wamp server icon, I realised that there is a whole left click menu in wampserver in which you can change the php version and it does change the web version of php.
I understand that this can be a bit confusing for people who are used to using wampserver, but for someone who is using it for the first time, we are not used to having a left click menu in the bottom right icons. I hope this saves some time for others who have a similar issue than mine.
The wampmanager->Tools->Change PHP CLI Version menu only changes the version of PHP that will be used by wampmanager.exe to run all the PHP scripts that provide all the functionality of WAMPServer.
It has no effect on the version of PHP that will will be run from the command line in Windows.
If when you open a command windows and run the PHP interpreter >php.exe you actually get to the PHP interpreter, then you must have added one of the possible paths to one of WAMPServers PHP folders to the Window's PATH. You should never do this with WAMPServer, so if this is what you did, UNDO IT! This is for obvious reasons as you could have multiple versions of PHP available and want to run any one of them at any time as the CLI Version to test some code against multiple versions of PHP.
Instead create yourself a little batch/cmd file that accepts a php version as a parameter like in this answer I posted a while ago
With that you can set the PATH temporarily for the life of a command window ONLY. You can also make it include a PATH to the PEAR and/or COMPOSER folders at the same time, if you use either of these.
To check All VC Runtimes
There is a tool for checking if you have all the possible required VC Runtimes installed. Go to this page, the backup repo for WAMPServer, and download the little utility called Checks VC++ packages installed you will find it down near the bottom of the page. Download and run it, then throw it away, as it changes over time as new VC Runtimes become required.
Ok, I want to start working with Angular2 and I'd like to do it through a JHipster generated application as this is the line of work we follow on some of our applications at work
I've been looking through a number of questions in SO such as:
How to update the JHipster project after updating JHipster generator?
How to upgrade jhipster sub-generator?
And I've also gone through the documentation of JHipster release 4.0.0 here: https://jhipster.github.io/2017/02/02/jhipster-release-4.0.0.html
But with all of that what still remains unclear to me are the implications that updating the subgenerator to the latest version would have on my existing applications
My concern is:
I do not wish to upgrade the already existing applications to the latest JHipster version nor to change from Angular 1 to 2 in them (at least not for a length of time) so in which way could updating the sub-generator affect my already existing applications when trying to work on them?
JHipster (since version 3) installs itself into your project's local node_modules folder. It should be included in your package.json under the dependencies section.
This means that when you run yo jhipster inside of your previously generated project folder, it loads the locally installed version specified in package.json instead of your globally installed version (which could be a different version).
You can verify the version your project uses by running yo jhipster:info or looking for the version in your package.json
We need to update Ranorex licence server from version 5.1 to version 5.3.
What is the proper approach to not break the running tests?
I searched on the Ranorex homepage for this issue yet, without finding anything.
Normally, a simple upgrade should work, but wouldn't it be safer to upgrade the license server when no tests are running?
The best way in order to upgrade the license server is uninstalling the old version, restart the machine and install the new version. Usually, it also works if you just run the setup file without uninstalling the old version, but I prefer the uninstall - restart - install approach.
The answer of user1982826 is good. As in meantime the official Ranorex Support has answered my request, I want share their answer:
Generally with the server upgrade the service will be reinstalled and restarted. Depending on how long that lasts (e.g. dependant on the computer), the connection on the client may time out and the test will break. So it would be safer to update the server, when no test is running.