Jenkins build is back to normal : royale-asjs #223

See

Jenkins build is back to normal : royale-asjs_jsonly #237

See

Build failed in Jenkins: royale-asjs #222

See Changes: [aharui] center mx Alert. Fixes #565 -- [...truncated 1.17 MB...] [java] var events = require('events'); [java]

Build failed in Jenkins: royale-asjs_jsonly #236

See Changes: [aharui] center mx Alert. Fixes #565 -- [...truncated 1.17 MB...] [java] var events = require('events'); [java]

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

Jenkins build is back to normal : royale-compiler #70

See

Build failed in Jenkins: royale-compiler #69

See Changes: [joshtynjala] StreamingASTokenizer: added strictIdentifiers variable to allow the -- Started by an SCM change Started by an SCM

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

Jenkins build is back to normal : TourDeFlexMigration #173

See

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

Re: [royale-asjs.wiki] branch master updated: Update CI server url to the new one

Hi, this url: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/Royale%20Release/ seems not valid anymore Maybe we can just put this one: http://apacheroyaleci.westus2.cloudapp.azure.com:8080 ? El mié., 20

Build failed in Jenkins: TourDeFlexMigration #172

See Changes: -- [...truncated 36.50 KB...] [mxmlc] scanning for overrides: NoChannelAvailableError [mxmlc] scanning for overrides: ChannelEvent

Re: Apache Flex Mavenizer 1.0.0 released

Hi, just tested today that we can remove "-s settings-template.xml". All worked ok Should we update something before we remove that file? will wait to know about that to commit that file removal. I'll be updating the maven wiki to reflect latest changes too Thanks El mar., 19 nov. 2019 a las

Layout and Functionality Issues in our Application (Target Deadline 29-Nov-2019)

Hi Alex , We have just sent our basic setups in QA for Testing and following (layout) issues are reported by our QA Team. https://github.com/apache/royale-asjs/issues/564 https://github.com/apache/royale-asjs/issues/565 https://github.com/apache/royale-asjs/issues/566

Re: Apache Royale Maven improvements, fixes and reproducible builds PR by Chris Dutz

Greg, thanks for letting us know, very appreciated I think your support can be very useful as always. Will let you know if you can help on any area :) Thanks Carlos El mar., 19 nov. 2019 a las 20:23, Greg Dove () escribió: > Just chiming in from my perspective... I am definitely keen to