Re: Jenkins CI

2024-02-26 Thread Yishay Weiss
Ok, got it running.

Dashboard [Jenkins] 
(azure.com)<http://apacheroyale.francecentral.cloudapp.azure.com:8080/>

Thanks, Alex, I think you can let your instance go.

From: Yishay Weiss 
Sent: Monday, February 26, 2024 8:42 PM
To: dev@royale.apache.org 
Subject: Re: Jenkins CI

It's not running right now, but there's an instance running on Apache infra for 
nightly maven builds.

From: Alex Harui 
Sent: Monday, February 26, 2024 8:34 PM
To: dev@royale.apache.org 
Subject: Re: Jenkins CI

OK.  I am not going to try to save my Jenkins data.  I assume you'll be able to 
recover your Jenkins instance.  It sounds like it is still running?  Or have 
folks not needed the daily builds?

-Alex

On 2/26/24, 10:27 AM, "Yishay Weiss" mailto:yishayj...@hotmail.com>> wrote:


EXTERNAL: Use caution when clicking on links or opening attachments.




Yes, we had it running at some point. I'm trying to run it again now. 
Unfortunately, it looks like I've forgotten my password and I'll need to submit 
an account verification form to recover my password.

From: Alex Harui mailto:aha...@adobe.com.inva>LID>
Sent: Monday, February 26, 2024 6:35 PM
To: dev@royale.apache.org <mailto:dev@royale.apache.org> mailto:dev@royale.apache.org>>
Subject: Jenkins CI


Yishay (and others),


Did we get a replacement Jenkins up and running? I let my Azure VM subscription 
expire and the data will be deleted next Monday. I’ll let that happen if we 
don’t need my Jenkins setup anymore.


-Alex





Re: Jenkins CI

2024-02-26 Thread Yishay Weiss
It's not running right now, but there's an instance running on Apache infra for 
nightly maven builds.

From: Alex Harui 
Sent: Monday, February 26, 2024 8:34 PM
To: dev@royale.apache.org 
Subject: Re: Jenkins CI

OK.  I am not going to try to save my Jenkins data.  I assume you'll be able to 
recover your Jenkins instance.  It sounds like it is still running?  Or have 
folks not needed the daily builds?

-Alex

On 2/26/24, 10:27 AM, "Yishay Weiss" mailto:yishayj...@hotmail.com>> wrote:


EXTERNAL: Use caution when clicking on links or opening attachments.




Yes, we had it running at some point. I'm trying to run it again now. 
Unfortunately, it looks like I've forgotten my password and I'll need to submit 
an account verification form to recover my password.

From: Alex Harui mailto:aha...@adobe.com.inva>LID>
Sent: Monday, February 26, 2024 6:35 PM
To: dev@royale.apache.org <mailto:dev@royale.apache.org> mailto:dev@royale.apache.org>>
Subject: Jenkins CI


Yishay (and others),


Did we get a replacement Jenkins up and running? I let my Azure VM subscription 
expire and the data will be deleted next Monday. I’ll let that happen if we 
don’t need my Jenkins setup anymore.


-Alex





Re: Jenkins CI

2024-02-26 Thread Alex Harui
OK.  I am not going to try to save my Jenkins data.  I assume you'll be able to 
recover your Jenkins instance.  It sounds like it is still running?  Or have 
folks not needed the daily builds?

-Alex

On 2/26/24, 10:27 AM, "Yishay Weiss" mailto:yishayj...@hotmail.com>> wrote:


EXTERNAL: Use caution when clicking on links or opening attachments.




Yes, we had it running at some point. I'm trying to run it again now. 
Unfortunately, it looks like I've forgotten my password and I'll need to submit 
an account verification form to recover my password.

From: Alex Harui mailto:aha...@adobe.com.inva>LID>
Sent: Monday, February 26, 2024 6:35 PM
To: dev@royale.apache.org <mailto:dev@royale.apache.org> mailto:dev@royale.apache.org>>
Subject: Jenkins CI


Yishay (and others),


Did we get a replacement Jenkins up and running? I let my Azure VM subscription 
expire and the data will be deleted next Monday. I’ll let that happen if we 
don’t need my Jenkins setup anymore.


-Alex





Re: Jenkins CI

2024-02-26 Thread Yishay Weiss
Yes, we had it running at some point. I'm trying to run it again now. 
Unfortunately, it looks like I've forgotten my password and I'll need to submit 
an account verification form to recover my password.

From: Alex Harui 
Sent: Monday, February 26, 2024 6:35 PM
To: dev@royale.apache.org 
Subject: Jenkins CI

Yishay (and others),

Did we get a replacement Jenkins up and running?  I let my Azure VM 
subscription expire and the data will be deleted next Monday.  I’ll let that 
happen if we don’t need my Jenkins setup anymore.

-Alex


Jenkins CI

2024-02-26 Thread Alex Harui
Yishay (and others),

Did we get a replacement Jenkins up and running?  I let my Azure VM 
subscription expire and the data will be deleted next Monday.  I’ll let that 
happen if we don’t need my Jenkins setup anymore.

-Alex


Apache Royale Jenkins CI (was Re: [Discuss] Start release process 0.9.3)

2018-10-04 Thread Alex Harui
Hi,

It turns out that the checkintest do not actually run on master.  They must run 
on the agent.  We've not been actually testing our code.  The player does not 
launch and then the flashlog from the last test to run on the agent is reported 
on.

I am in the process of moving the builds that have graphical tests back to the 
agent.

-Alex

On 8/27/18, 7:03 AM, "Piotr Zarzycki"  wrote:

I have switched two build on jenkins to "master" royale-asjs_jsonly and
royale-asjs - It seems that this fixes issue with build. - Not sure if it
can stay like that.

I'm working right now to fix build for module Icons.

Thanks,
Piotr

pon., 27 sie 2018 o 15:06 Piotr Zarzycki 
napisał(a):

> I'm going to commit some changes to build.xml, if it won't work I will
> revert it.
>
> pon., 27 sie 2018 o 14:12 Piotr Zarzycki 
> napisał(a):
>
>> I looked into the current failing build [1]. It complaining that "Basedir
>> c:\jenkins\workspace\royale-typedefs does not exist" and it would be
>> correct, because "royale-typedefs" is being build to that folder 
"C:\Program
>> Files (x86)\Jenkins\workspace\royale-typedefs".
>>
>> Does anyone changed that and why ?
>>
>> [1]
>> 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2Fdata=02%7C01%7Caharui%40adobe.com%7Cdfb56180bb5e41331adc08d60c25d165%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636709753897399673sdata=n7JIKX8vjpitTAp9TH1kMxswdSN5B%2Bb6J%2FDleeRXNPc%3Dreserved=0
>>
>> Thanks,
>> Piotr
>>
>> niedz., 26 sie 2018 o 15:11 Piotr Zarzycki 
>> napisał(a):
>>
>>> I'm going to notify Infra about problem with build on b.a.o. Locally
>>> everything is perfectly fine. I will attach dev list and write email on
>>> us...@infra.apache.org.
>>>
>>> Thanks,
>>> Piotr
>>>
>>> pt., 24 sie 2018 o 16:05 Carlos Rovira 
>>> napisał(a):
>>>
 Great Piotr!,

 as you said discussion is not over, but I think we discussed almost
 lots of
 things and plans was left for releases "post 0.9.3". In fact I revert
 package name changes that was the only point that was making us not
 release
 0.9.3. So I think we are at this point safe to release 0.9.3, 0.9.4 or
 what
 we want to call it :)

 I must say that I'm this days wanting to finish some things in Jewel
 that
 will make it pretty usable in an stable way, for me that points are:

 * End Jewel Table and Jewel List remove and update data
 * Jewel NumericStepper
 * Jewel DropdownList/Combobox

 There's much more to do, but I think those three points will make many
 people have the minimun to start working in real Apache Royale Jewel
 apps
 (at least is what I need to start a real project we have now for Apache
 Royale, so I'm working hard to complete these points).
 I want to make this asap, so hope something of those point could go in
 this
 release :)

 Best,

 Carlos








 El vie., 24 ago. 2018 a las 0:35, Piotr Zarzycki (<
 piotrzarzyck...@gmail.com>)
 escribió:

 > Hi Om,
 >
 > I have no objections to that. The question whether from the technical
 point
 > of view Maven which is I believe big part of release process won't
 > complain. We will see.
 >
 > Thanks for confirmation,
 > Piotr
 >
 >
 > pt., 24 sie 2018 o 00:25 OmPrakash Muppirala 
 > napisał(a):
 >
 > > Yes, since 0.9.3 was already pushed out via npm [1], it would be
 best if
 > we
 > > skip to 0.9.4
 > >
 > > Thanks,
 > > Om
 > >
 > > [1] 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40apache-royale%2Froyale-jsdata=02%7C01%7Caharui%40adobe.com%7Cdfb56180bb5e41331adc08d60c25d165%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636709753897399673sdata=Iue5ihIXFq4R%2BPqN%2FSZ5In043Kn4ooTTRxao3db0i4I%3Dreserved=0
 > >
 > > On Thu, Aug 23, 2018 at 1:53 PM Piotr Zarzycki <
 > piotrzarzyck...@gmail.com>
 > > wrote:
 > >
 > > > Hi Guys,
 > > >
 > > > It's been a while since last version of Royale was released. I
 would
 > like
 > > > to start process of releasing current version no matter in what
 state
 > it
 > > is
 > > > right now. I know that we have probably unfinished discussion
 about
 > some
 > > > core changes. I'm suggesting