Re: Executing Release Step 1

I don't know what you mean by "not accept it". When I look at global tools config, the JDK installation is set. The error about the slave/agent not finding Java might be independent of that. -Alex On 11/21/19, 11:56 AM, "Carlos Rovira" wrote: Hi, I must exist now and will be off

Re: Executing Release Step 1

Hi, I must exist now and will be off until tomorrow. Curious thing is that yesterday I could add Java 8 without problem and RS#1 was working... don't know why today Jenkins does not accept it Don't have many experience with Jenkins, but maybe we need to restart Jenkins :? El jue., 21 nov. 2019

Re: Executing Release Step 1

The NOO2 job last failed with "Failed to determine (log)". I also got that on occasion and had to re-run the job. Only twice did it say the same thing again. Most of the time it ran successfully afterward. You can try restarting the VM and see if that helps. On 11/21/19, 10:43 AM, "Alex

Re: Executing Release Step 1

It might be a UI bug in Jenkins. In Global Tools Configuration I see a button "JDK Installations", but when I click on it, it shows me an installation. -Alex On 11/21/19, 10:36 AM, "Carlos Rovira" wrote: Direct link to the Java SDK config screen:

Re: Executing Release Step 1

Whoever accepts the upgrade is responsible for getting all of the jobs to build again. __ On 11/21/19, 10:31 AM, "Carlos Rovira" wrote: I see as well Jenkins show 2 updates. What's the politic in this regard? if we see updates should we accept it and upgrade Jenkins? thanks

Re: Executing Release Step 1

Direct link to the Java SDK config screen: http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/configureTools/ El jue., 21 nov. 2019 a las 19:31, Carlos Rovira () escribió: > I see as well Jenkins show 2 updates. What's the politic in this regard? > if we see updates should we accept it

Re: Executing Release Step 1

I see as well Jenkins show 2 updates. What's the politic in this regard? if we see updates should we accept it and upgrade Jenkins? thanks El jue., 21 nov. 2019 a las 19:06, Alex Harui () escribió: > I updated the global configs to get email working. > > I don't know what steps you took to "put

Re: Executing Release Step 1

Hi Alex, is in global Jenkins config, in "Admin Jenkins" and then "Global Tool Configuration". (Names could change since I'm seeing in Spanish to translation can be different for you) thanks El jue., 21 nov. 2019 a las 19:06, Alex Harui () escribió: > I updated the global configs to get email

Re: Executing Release Step 1

I updated the global configs to get email working. I don't know what steps you took to "put Java 8" and what "screen config" you are looking at. -Alex On 11/21/19, 10:03 AM, "Carlos Rovira" wrote: Hi, today seem emails are working but RS#1 is again. Yesterday I had to put

Re: Executing Release Step 1

Hi, today seem emails are working but RS#1 is again. Yesterday I had to put Java 8 but today is gone :? When I try to add it, then if I go again to that screen config is gone. Maybe someone of you know what's could be happening Thanks Carlos El mié., 20 nov. 2019 a las 23:12, Carlos Rovira

Re: Executing Release Step 1

Hi Piotr, Alex, Piotr, you refere to the wiki? I don't see anything about that particular documentation of tasks around commands there. Maybe other doc I don't find? About my progress: I duplicated the RS#1 to avoid change things in the same recipe, and ensure the current work is untouched. To

Re: Executing Release Step 1

Carlos, Description of each step should be in our doc. If it not enough clear report it maybe - there is probably room for improvement. Thanks, Piotr On Wed, Nov 20, 2019, 8:28 PM Alex Harui wrote: > The first steps get the head of the newly created release branch that was > created by Maven

Re: Executing Release Step 1

The first steps get the head of the newly created release branch that was created by Maven and set the origin so a git push knows where to push. The "git status" calls are there for console logging so we can see if there were unexpected things in the working copies in case these steps fail.

Re: Executing Release Step 1

Hi Alex, trying to understand RS#1 process. Can you tell me about the purpose after maven release:branch ? I mean this: git status git branch -u origin/%developbranchname% git checkout release/%releaseversion% git status git checkout %developbranchname% git status something related to the git

Re: Executing Release Step 1

Hi Alex, just tried again to see if error email comes. We'll go through this point to see how to solve the JGit problem thanks El mié., 20 nov. 2019 a las 18:03, Alex Harui () escribió: > Looks like the extended email plugin wasn't configured correctly. I think > I've fixed that. We'll see in

Re: Executing Release Step 1

Hi, didn't need Remote Desktop, just log in my Mac through Safari in the server Jenkins console. Let me know if that's wrong thanks El mié., 20 nov. 2019 a las 17:26, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > Hi Carlos, > > Were you able to login trough Remote Desktop to PC ?

Re: Executing Release Step 1

Looks like the extended email plugin wasn't configured correctly. I think I've fixed that. We'll see in future runs. I think the Git issue is because JGit is not being used. HTH, -Alex On 11/20/19, 8:26 AM, "Piotr Zarzycki" wrote: Hi Carlos, Were you able to login trough

Re: Executing Release Step 1

Hi Carlos, Were you able to login trough Remote Desktop to PC ? Thanks, Piotr śr., 20 lis 2019 o 17:20 Carlos Rovira napisał(a): > Hi, > > I'm inside the CI server. following through: > > Release-Manager-Notes > < >

Executing Release Step 1

Hi, I'm inside the CI server. following through: Release-Manager-Notes So first trying to run Release Step 1, y pushing the clock with green arrow (I assume is the what I need to use). the step ask for