| Re: [starter-dev] Starter UI on Cloud! |
Jeyvison,
I am wondering how this is going? Kito has put in his look and feel changes and they are good. Can we please have an updated deployment?
Also, can we please have a 2.0.0 release of these from the current GitHub code: https://mvnrepository.com/artifact/org.eclipse.starter/jakartaee8-minimal, https://mvnrepository.com/artifact/org.eclipse.starter/jakartaee9.1-minimal, https://mvnrepository.com/artifact/org.eclipse.starter/jakartaee10-minimal? That way, we can properly deprecate them and remove them from the code base. Right now it's just sitting around as dead code waiting for a 2.0.0 release.
Thanks,
Reza
We should probably get the Jenkins job set up now. It's just a simple curl command to deploy (assuming a couple of secrets set up):
curl -X POST -u '${STARTER_SITE_USERNAME}:${STARTER_SITE_PASSWORD}' -T "target/jakarta-starter-ui.war" 'https://jakarta-ee-starter.scm.azurewebsites.net/api/publish?type=war'
On 3/30/2023 6:49 PM, Reza Rahman wrote:
The production site is now up: https://jakarta-ee-starter.azurewebsites.net. Jeyvison, could you please work to update the DNS entry for start.jakarta.ee?
Once that's done, we should start on the automated deployment via Jenkins.
P.S.: I have removed the staging deployment to avoid confusion.
On 3/30/2023 10:56 AM, reza_rahman@xxxxxxxxx wrote:
I’m going to give it one more day, but things look stable so far on the server. There are no exceptions, timeouts, response delays, etc. I’ll move to the production system shortly. After that maybe Jeyvison could help me update the start.jakarta.ee redirect to the production URL.
Note, it doesn’t mean we can’t make rapid releases to the UI once we move to production. In fact I’ll work with Jeyvison to automate UI releases so we can do it quickly and often.
From: Reza Rahman <reza_rahman@xxxxxxxxx>Folks,
Sent: Wednesday, March 29, 2023 2:08 PM
To: starter developer discussions <starter-dev@xxxxxxxxxxx>
Subject: Starter UI on Cloud!
The 2.0 version UI is now on the cloud and appears to be functioning as
expected: https://jakarta-starter.azurewebsites.net.
Can everyone please kick the tires and see what happens? I would like to
make sure there is nothing unexpected with the deployment for the next
few days.
Note, this is the staging URL. The production URL on Azure will be
different.
Thanks,
Reza