Build failed in Jenkins: royale-asjs_MXTests #1057

[Apache Royale CI Server]

See 


--
[...truncated 982.97 KB...]
[mxmlc] scanning for overrides: CustomEvent
[mxmlc] scanning for overrides: ItemAddedEvent
[mxmlc] scanning for overrides: ItemClickedEvent
[mxmlc] scanning for overrides: ItemRemovedEvent
[mxmlc] scanning for overrides: ItemRendererEvent
[mxmlc] scanning for overrides: Size
[mxmlc] scanning for overrides: ItemAndDescriptor
[mxmlc] scanning for overrides: SetEventHandler
[mxmlc] scanning for overrides: SetProperty
[mxmlc] scanning for overrides: CSSBorderUtils
[mxmlc] scanning for overrides: CSSUtils
[mxmlc] scanning for overrides: ObjectUtil
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringTrimmer
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: UIUtils
[mxmlc] scanning for overrides: Effect
[mxmlc] scanning for overrides: Transition
[mxmlc] scanning for overrides: IFill
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: IExternalizable
[mxmlc] scanning for overrides: Proxy
[mxmlc] scanning for overrides: CursorBookmark
[mxmlc] scanning for overrides: ICollectionView
[mxmlc] scanning for overrides: IList
[mxmlc] scanning for overrides: IViewCursor
[mxmlc] scanning for overrides: ListCollectionView
[mxmlc] scanning for overrides: ListCollectionViewCursor
[mxmlc] scanning for overrides: ListCollectionViewBookmark
[mxmlc] scanning for overrides: ArrayCollection
[mxmlc] scanning for overrides: ArrayList
[mxmlc] scanning for overrides: XMLListCollection
[mxmlc] scanning for overrides: CanvasLayout
[mxmlc] scanning for overrides: Flex
[mxmlc] scanning for overrides: BoxDirection
[mxmlc] scanning for overrides: HBox
[mxmlc] scanning for overrides: PanelTitleBar
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ISelectable
[mxmlc] scanning for overrides: CheckBox
[mxmlc] scanning for overrides: IFocusManagerComponent
[mxmlc] scanning for overrides: ComboBase
[mxmlc] scanning for overrides: ComboBox
[mxmlc] scanning for overrides: ScrollControlBase
[mxmlc] scanning for overrides: ListBase
[mxmlc] scanning for overrides: DataGrid
[mxmlc] scanning for overrides: DateField
[mxmlc] scanning for overrides: Label
[mxmlc] scanning for overrides: List
[mxmlc] scanning for overrides: MenuBar
[mxmlc] scanning for overrides: NumericStepper
[mxmlc] scanning for overrides: RadioButton
[mxmlc] scanning for overrides: RadioButtonGroup
[mxmlc] scanning for overrides: TextArea
[mxmlc] scanning for overrides: ITextInput
[mxmlc] scanning for overrides: TextInput
[mxmlc] scanning for overrides: ITextFieldFactory
[mxmlc] scanning for overrides: Singleton
[mxmlc] scanning for overrides: ItemClickEvent
[mxmlc] scanning for overrides: ListEvent
[mxmlc] scanning for overrides: MenuEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: PropertyChangeEventKind
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: IFocusManagerComplexComponent
[mxmlc] scanning for overrides: IFocusManagerGroup
[mxmlc] scanning for overrides: IResourceBundle
[mxmlc] scanning for overrides: ResourceManagerImpl
[mxmlc] scanning for overrides: ResourceModuleInfo
[mxmlc] scanning for overrides: ResourceEventDispatcher
[mxmlc] scanning for overrides: ResourceBundleProxy
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: SkinnableComponent
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ErrorArray
[mxmlc] scanning for overrides: RunCodeEvent
[mxmlc] scanning for overrides: PasswordInputBead
[mxmlc] scanning for overrides: ITileLayout
[mxmlc] scanning for overrides: TileLayout
[mxmlc] scanning for overrides: LocaleUtils
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: IStroke
[mxmlc] scanning for overrides: CursorError
[mxmlc] scanning for overrides: SortError
[mxmlc] scanning for overrides: ISort
[mxmlc] scanning for overrides: Sort
[mxmlc] scanning for overrides: IXMLNotifiable
[mxmlc] scanning for overrides: XMLListAdapter
[mxmlc] scanning for overrides: FlexChildInfo
[mxmlc] scanning for overrides: BaseListData
[mxmlc] scanning for overrides: IFactory
[mxmlc] scanning for overrides: IUITextField
[mxmlc] scanning for overrides: UITextField
[mxmlc] scanning for overrides: 

inject_html in the framework via rawgit

[Greg Dove]

"RawGit is now in a sunset phase and will soon shut down" [1]

It just came to my attention today that some of the framework code uses
script tag injections for rawgit urls, and I checked that service... it
could be shut down as early as October 2019.
This looks to only be used in MXRoyale and AceEditor.

One of the uses seems to be for base64 encoding and decoding, which
(hopefully) can be replaced with native browser functions, I think [2]

For now, I am just highlighting this. I realize we are in release mode for
0.96, but we probably want to ensure another release before too long with
alternative script urls before that service drops out.

1. https://rawgit.com/
2. https://caniuse.com/#feat=atob-btoa

Build failed in Jenkins: royale-asjs_MXTests #1056

[Apache Royale CI Server]

See 


Changes:

[aharui] ensure end values if the update happens well after the duration expires

[aharui] set the return type to Number because JS returns a number

--
[...truncated 982.97 KB...]
[mxmlc] scanning for overrides: CustomEvent
[mxmlc] scanning for overrides: ItemAddedEvent
[mxmlc] scanning for overrides: ItemClickedEvent
[mxmlc] scanning for overrides: ItemRemovedEvent
[mxmlc] scanning for overrides: ItemRendererEvent
[mxmlc] scanning for overrides: Size
[mxmlc] scanning for overrides: ItemAndDescriptor
[mxmlc] scanning for overrides: SetEventHandler
[mxmlc] scanning for overrides: SetProperty
[mxmlc] scanning for overrides: CSSBorderUtils
[mxmlc] scanning for overrides: CSSUtils
[mxmlc] scanning for overrides: ObjectUtil
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringTrimmer
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: UIUtils
[mxmlc] scanning for overrides: Effect
[mxmlc] scanning for overrides: Transition
[mxmlc] scanning for overrides: IFill
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: IExternalizable
[mxmlc] scanning for overrides: Proxy
[mxmlc] scanning for overrides: CursorBookmark
[mxmlc] scanning for overrides: ICollectionView
[mxmlc] scanning for overrides: IList
[mxmlc] scanning for overrides: IViewCursor
[mxmlc] scanning for overrides: ListCollectionView
[mxmlc] scanning for overrides: ListCollectionViewCursor
[mxmlc] scanning for overrides: ListCollectionViewBookmark
[mxmlc] scanning for overrides: ArrayCollection
[mxmlc] scanning for overrides: ArrayList
[mxmlc] scanning for overrides: XMLListCollection
[mxmlc] scanning for overrides: CanvasLayout
[mxmlc] scanning for overrides: Flex
[mxmlc] scanning for overrides: BoxDirection
[mxmlc] scanning for overrides: HBox
[mxmlc] scanning for overrides: PanelTitleBar
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ISelectable
[mxmlc] scanning for overrides: CheckBox
[mxmlc] scanning for overrides: IFocusManagerComponent
[mxmlc] scanning for overrides: ComboBase
[mxmlc] scanning for overrides: ComboBox
[mxmlc] scanning for overrides: ScrollControlBase
[mxmlc] scanning for overrides: ListBase
[mxmlc] scanning for overrides: DataGrid
[mxmlc] scanning for overrides: DateField
[mxmlc] scanning for overrides: Label
[mxmlc] scanning for overrides: List
[mxmlc] scanning for overrides: MenuBar
[mxmlc] scanning for overrides: NumericStepper
[mxmlc] scanning for overrides: RadioButton
[mxmlc] scanning for overrides: RadioButtonGroup
[mxmlc] scanning for overrides: TextArea
[mxmlc] scanning for overrides: ITextInput
[mxmlc] scanning for overrides: TextInput
[mxmlc] scanning for overrides: ITextFieldFactory
[mxmlc] scanning for overrides: Singleton
[mxmlc] scanning for overrides: ItemClickEvent
[mxmlc] scanning for overrides: ListEvent
[mxmlc] scanning for overrides: MenuEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: PropertyChangeEventKind
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: IFocusManagerComplexComponent
[mxmlc] scanning for overrides: IFocusManagerGroup
[mxmlc] scanning for overrides: IResourceBundle
[mxmlc] scanning for overrides: ResourceManagerImpl
[mxmlc] scanning for overrides: ResourceModuleInfo
[mxmlc] scanning for overrides: ResourceEventDispatcher
[mxmlc] scanning for overrides: ResourceBundleProxy
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: SkinnableComponent
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ErrorArray
[mxmlc] scanning for overrides: RunCodeEvent
[mxmlc] scanning for overrides: PasswordInputBead
[mxmlc] scanning for overrides: ITileLayout
[mxmlc] scanning for overrides: TileLayout
[mxmlc] scanning for overrides: LocaleUtils
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: IStroke
[mxmlc] scanning for overrides: CursorError
[mxmlc] scanning for overrides: SortError
[mxmlc] scanning for overrides: ISort
[mxmlc] scanning for overrides: Sort
[mxmlc] scanning for overrides: IXMLNotifiable
[mxmlc] scanning for overrides: XMLListAdapter
[mxmlc] scanning for overrides: FlexChildInfo
[mxmlc] scanning for overrides: BaseListData

Re: Compiler Performance (was Re: Problem with Vectors)

[Piotr Zarzycki]

Hi Greg,

Well I definitely in the very last steps, but if I won't be able to figure
out how to upload artifacts I'm not sure whether we will not stuck for the
next couple of weeks. :(

Thanks,
Piotr

On Wed, Aug 14, 2019, 9:50 PM Greg Dove  wrote:

> I should have drawn attention to this again before release work started...
> I guess it is too late to get rid of that diagnostic output (described
> below) from the compiler in the release?
> It might be confusing output for some people, or create the wrong
> impression, but perhaps it is too late in the process?
>
> On Wed, Jul 3, 2019 at 8:42 PM Greg Dove  wrote:
>
> >
> > Just a quick followup to Harbs' earlier comment about the compiler noise.
> > I'm seeing this a lot also.
> >
> > It looks like there is some leftover diagnostic logging in
> > ControlFlowGraph.traverseGraph. Hopefully it can be removed or dialed
> down.
> >
> >
> >
> >
> > On Mon, Jul 1, 2019 at 7:06 AM Yishay Weiss 
> > wrote:
> >
> >> I was also getting it before.
> >> 
> >> From: Josh Tynjala 
> >> Sent: Sunday, June 30, 2019 3:53:56 PM
> >> To: dev@royale.apache.org
> >> Subject: Re: Compiler Performance (was Re: Problem with Vectors)
> >>
> >> Is this GC limit error something new? Or were you getting it before too?
> >>
> >> - Josh
> >>
> >> On Sun, Jun 30, 2019, 1:35 AM Yishay Weiss 
> >> wrote:
> >>
> >> > On my windows/powershell env there’s a significant improvement (~34
> >> > seconds instead of ~42) when building our app with verbose switched
> off.
> >> > I’m getting a ‘GC overhead limit exceeded’ [1] error though quite
> often
> >> > which brings it up to around a minute and a half. Increasing heap size
> >> by
> >> > setting ANT_OPTS to -Xmx2g doesn’t seem to make a difference.
> >> >
> >> >
> >> >
> >> > [1] https://paste.apache.org/BXf4
> >> >
> >> >
> >> >
> >> > 
> >> > From: Josh Tynjala 
> >> > Sent: Friday, June 28, 2019 6:24:10 PM
> >> > To: dev@royale.apache.org
> >> > Subject: Re: Compiler Performance (was Re: Problem with Vectors)
> >> >
> >> > Windows and PowerShell.
> >> >
> >> > I have not been cleaning bin/js-debug before each build. So my
> reported
> >> > times are more like what an app developer would experience most of the
> >> > time. Writing files after remove circulars still has an impact in that
> >> > situation. It's not huge, but still enough to be worth the effort, I
> >> think.
> >> >
> >> > Another thing I've noticed is that the compiler will randomly decide
> to
> >> do
> >> > a release build every now and then, even though I've always asked for
> >> debug
> >> > builds. Maybe a threading issue or something while the configuration
> >> one of
> >> > being initialized?
> >> >
> >> > - Josh
> >> >
> >> > On Thu, Jun 27, 2019, 9:35 PM Alex Harui 
> >> wrote:
> >> >
> >> > > Good progress!  Are these times based on Windows? PowerShell?  Mac?
> >> I'm
> >> > > just wondering if the Java code outputting strings is slow or the
> >> console
> >> > > saving the output or both.
> >> > >
> >> > > Are you only testing from a clean bin/js-debug?  I thought that the
> >> > > compiler did not copy JS files that were already in bin/js-debug and
> >> > > remove-circulars re-uses those JS files.
> >> > >
> >> > > In theory, those of us modifying framework code have to clean out
> >> > > bin/js-debug more often than app developers.
> >> > >
> >> > > HTH,
> >> > > -Alex
> >> > >
> >> > > On 6/27/19, 4:00 PM, "Josh Tynjala" 
> >> wrote:
> >> > >
> >> > > I made a few smaller optimizations today. It seems to shave off
> >> about
> >> > > 0.4
> >> > > to 0.5 seconds from the time to compile TourDeJewel on my
> >> computer.
> >> > > Not as
> >> > > dramatic as the last one, but still a measurable difference!
> >> > >
> >> > > I'd like to find a way to make remove-circulars happen earlier
> in
> >> the
> >> > > process. It takes files that are already written to the file
> >> system
> >> > and
> >> > > then modifies them. The extra re-write to disk is pretty
> >> expensive.
> >> > If
> >> > > all
> >> > > JS files were written to disk only once, we'd save another half
> >> > second
> >> > > or
> >> > > more.
> >> > >
> >> > > --
> >> > > Josh Tynjala
> >> > > Bowler Hat LLC <
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C3763ea8f30394ff716bd08d6fb534693%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636972732457464401sdata=SxYcGgMT3qQi2zEaeJAPA0AYm2UnB7Ljm4PvE4b3A4c%3Dreserved=0
> >> > > >
> >> > >
> >> > >
> >> > > On Wed, Jun 26, 2019 at 2:42 PM Josh Tynjala <
> >> joshtynj...@apache.org
> >> > >
> >> > > wrote:
> >> > >
> >> > > > I found some low-hanging fruit!
> >> > > >
> >> > > > I just pushed a commit that removes most of the noisy console
> >> > output
> >> > > from
> >> > > > the compiler. I know that this output is useful for debugging
> >> 

Re: Compiler Performance (was Re: Problem with Vectors)

[Greg Dove]

I should have drawn attention to this again before release work started...
I guess it is too late to get rid of that diagnostic output (described
below) from the compiler in the release?
It might be confusing output for some people, or create the wrong
impression, but perhaps it is too late in the process?

On Wed, Jul 3, 2019 at 8:42 PM Greg Dove  wrote:

>
> Just a quick followup to Harbs' earlier comment about the compiler noise.
> I'm seeing this a lot also.
>
> It looks like there is some leftover diagnostic logging in
> ControlFlowGraph.traverseGraph. Hopefully it can be removed or dialed down.
>
>
>
>
> On Mon, Jul 1, 2019 at 7:06 AM Yishay Weiss 
> wrote:
>
>> I was also getting it before.
>> 
>> From: Josh Tynjala 
>> Sent: Sunday, June 30, 2019 3:53:56 PM
>> To: dev@royale.apache.org
>> Subject: Re: Compiler Performance (was Re: Problem with Vectors)
>>
>> Is this GC limit error something new? Or were you getting it before too?
>>
>> - Josh
>>
>> On Sun, Jun 30, 2019, 1:35 AM Yishay Weiss 
>> wrote:
>>
>> > On my windows/powershell env there’s a significant improvement (~34
>> > seconds instead of ~42) when building our app with verbose switched off.
>> > I’m getting a ‘GC overhead limit exceeded’ [1] error though quite often
>> > which brings it up to around a minute and a half. Increasing heap size
>> by
>> > setting ANT_OPTS to -Xmx2g doesn’t seem to make a difference.
>> >
>> >
>> >
>> > [1] https://paste.apache.org/BXf4
>> >
>> >
>> >
>> > 
>> > From: Josh Tynjala 
>> > Sent: Friday, June 28, 2019 6:24:10 PM
>> > To: dev@royale.apache.org
>> > Subject: Re: Compiler Performance (was Re: Problem with Vectors)
>> >
>> > Windows and PowerShell.
>> >
>> > I have not been cleaning bin/js-debug before each build. So my reported
>> > times are more like what an app developer would experience most of the
>> > time. Writing files after remove circulars still has an impact in that
>> > situation. It's not huge, but still enough to be worth the effort, I
>> think.
>> >
>> > Another thing I've noticed is that the compiler will randomly decide to
>> do
>> > a release build every now and then, even though I've always asked for
>> debug
>> > builds. Maybe a threading issue or something while the configuration
>> one of
>> > being initialized?
>> >
>> > - Josh
>> >
>> > On Thu, Jun 27, 2019, 9:35 PM Alex Harui 
>> wrote:
>> >
>> > > Good progress!  Are these times based on Windows? PowerShell?  Mac?
>> I'm
>> > > just wondering if the Java code outputting strings is slow or the
>> console
>> > > saving the output or both.
>> > >
>> > > Are you only testing from a clean bin/js-debug?  I thought that the
>> > > compiler did not copy JS files that were already in bin/js-debug and
>> > > remove-circulars re-uses those JS files.
>> > >
>> > > In theory, those of us modifying framework code have to clean out
>> > > bin/js-debug more often than app developers.
>> > >
>> > > HTH,
>> > > -Alex
>> > >
>> > > On 6/27/19, 4:00 PM, "Josh Tynjala" 
>> wrote:
>> > >
>> > > I made a few smaller optimizations today. It seems to shave off
>> about
>> > > 0.4
>> > > to 0.5 seconds from the time to compile TourDeJewel on my
>> computer.
>> > > Not as
>> > > dramatic as the last one, but still a measurable difference!
>> > >
>> > > I'd like to find a way to make remove-circulars happen earlier in
>> the
>> > > process. It takes files that are already written to the file
>> system
>> > and
>> > > then modifies them. The extra re-write to disk is pretty
>> expensive.
>> > If
>> > > all
>> > > JS files were written to disk only once, we'd save another half
>> > second
>> > > or
>> > > more.
>> > >
>> > > --
>> > > Josh Tynjala
>> > > Bowler Hat LLC <
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C3763ea8f30394ff716bd08d6fb534693%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636972732457464401sdata=SxYcGgMT3qQi2zEaeJAPA0AYm2UnB7Ljm4PvE4b3A4c%3Dreserved=0
>> > > >
>> > >
>> > >
>> > > On Wed, Jun 26, 2019 at 2:42 PM Josh Tynjala <
>> joshtynj...@apache.org
>> > >
>> > > wrote:
>> > >
>> > > > I found some low-hanging fruit!
>> > > >
>> > > > I just pushed a commit that removes most of the noisy console
>> > output
>> > > from
>> > > > the compiler. I know that this output is useful for debugging
>> the
>> > > compiler
>> > > > itself, but most developers writing ActionScript and MXML don't
>> > ever
>> > > need
>> > > > to see it.
>> > > >
>> > > > If you actually want to see all of that output, you should now
>> > > enable the
>> > > > -verbose compiler option.
>> > > >
>> > > > With -verbose=true, TourDeJewel compiles in about 8 seconds on
>> my
>> > > machine.
>> > > > With -verbose=false, it compiles in 6 seconds. We're talking
>> about
>> > > 20-25%
>> > > > improvement to compile time 

Re: Discuss of release steps preparation

[Alex Harui]

Carlos,

In [1] that you referenced it says about release branches:

"During that time, bug fixes may be applied in this branch (rather than on the 
develop branch)."

To me, that means that new unstable changes should go into develop, but changes 
to make the release better should be discussed with the RM and committed to the 
release branch if agreed.  We want to avoid cherry-picking the develop branch 
to the release branch if at all possible.

-Alex

On 8/14/19, 1:58 AM, "Carlos Rovira"  wrote:

Hi Alex,

El lun., 12 ago. 2019 a las 19:30, Alex Harui ()
escribió:

> Also, the other committers should be aware that an RC is being created
> because they see the emails being sent by the CI server and ask the RM to
> agree to accept a commit to the release branch instead of the develop
> branch.


AFAIK, we should always commit to dev branch and not to release branch.
Releases are cut from develop. Only hot-fixes use to be branches that have
commits that fix something important in the release and then use to be
merged back to develop and master. Making commits to release branches could
bring some confusion and problems.

At least from is what I always learnt and used [1]

[1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnvie.com%2Fposts%2Fa-successful-git-branching-model%2Fdata=02%7C01%7Caharui%40adobe.com%7C84d6c89c5d284a001ddf08d72095850a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637013698867612965sdata=yGlrwnkreBblWjBtMMmpWJD4Cwk7q2tx62B97kn2F5o%3Dreserved=0

-- 
Carlos Rovira

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C84d6c89c5d284a001ddf08d72095850a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637013698867622965sdata=dgVvkG6rNkPhYuSJ6FkuHgXFKzUJi2Qxuknk5iuPYS0%3Dreserved=0

Re: Discuss of release steps preparation

[Alex Harui]

On 8/14/19, 1:14 AM, "Piotr Zarzycki"  wrote:

If your folder with artifacts is in  ~/temp/releasesteps - What do you type
when script asking you about ?

I would type (on a Mac):

  /Users/aharui/temp/releasesteps

There are 3 different Ant targets for Step 003:

- Release_Step_003
- Release_Step_003_Sign
- Release_Step_003_Upload

Each will ask you for a temporary folder.  The assumption is that you will use 
the SAME temporary folder for all 3 steps.  I recommend specifying a folder 
outside the working copy so you don't mess up the working copy.  If you do not 
use the same temporary folder, I could see that causing the problems you are 
having.

The upload problems are "not surprising".  You and others had similar problems 
before which is why I spend so much time revising the release automation.  In 
theory, when it fails, the console output should tell you how to try to 
continue from the point of failure.  The hope is that you will eventually 
succeed after several failures.  I never have any failures.

If you can't get the upload to succeed after several more attempts, then we'll 
look into trying to add a release step to have the Jenkins server do the 
upload.  I think there is some upload sensitivity issue with Nexus, but we 
can't change that.  Other Maven users outside the project report that they 
often have to make several attempts to continue after several failures but 
eventually succeed.

HTH,
-Alex

Build failed in Jenkins: royale-asjs_MXTests #1055

[Apache Royale CI Server]

See 


--
[...truncated 984.27 KB...]
[mxmlc] scanning for overrides: CustomEvent
[mxmlc] scanning for overrides: ItemAddedEvent
[mxmlc] scanning for overrides: ItemClickedEvent
[mxmlc] scanning for overrides: ItemRemovedEvent
[mxmlc] scanning for overrides: ItemRendererEvent
[mxmlc] scanning for overrides: Size
[mxmlc] scanning for overrides: ItemAndDescriptor
[mxmlc] scanning for overrides: SetEventHandler
[mxmlc] scanning for overrides: SetProperty
[mxmlc] scanning for overrides: CSSBorderUtils
[mxmlc] scanning for overrides: CSSUtils
[mxmlc] scanning for overrides: ObjectUtil
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringTrimmer
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: UIUtils
[mxmlc] scanning for overrides: Effect
[mxmlc] scanning for overrides: Transition
[mxmlc] scanning for overrides: IFill
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: IExternalizable
[mxmlc] scanning for overrides: Proxy
[mxmlc] scanning for overrides: CursorBookmark
[mxmlc] scanning for overrides: ICollectionView
[mxmlc] scanning for overrides: IList
[mxmlc] scanning for overrides: IViewCursor
[mxmlc] scanning for overrides: ListCollectionView
[mxmlc] scanning for overrides: ListCollectionViewCursor
[mxmlc] scanning for overrides: ListCollectionViewBookmark
[mxmlc] scanning for overrides: ArrayCollection
[mxmlc] scanning for overrides: ArrayList
[mxmlc] scanning for overrides: XMLListCollection
[mxmlc] scanning for overrides: CanvasLayout
[mxmlc] scanning for overrides: Flex
[mxmlc] scanning for overrides: BoxDirection
[mxmlc] scanning for overrides: HBox
[mxmlc] scanning for overrides: PanelTitleBar
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ISelectable
[mxmlc] scanning for overrides: CheckBox
[mxmlc] scanning for overrides: IFocusManagerComponent
[mxmlc] scanning for overrides: ComboBase
[mxmlc] scanning for overrides: ComboBox
[mxmlc] scanning for overrides: ScrollControlBase
[mxmlc] scanning for overrides: ListBase
[mxmlc] scanning for overrides: DataGrid
[mxmlc] scanning for overrides: DateField
[mxmlc] scanning for overrides: Label
[mxmlc] scanning for overrides: List
[mxmlc] scanning for overrides: MenuBar
[mxmlc] scanning for overrides: NumericStepper
[mxmlc] scanning for overrides: RadioButton
[mxmlc] scanning for overrides: RadioButtonGroup
[mxmlc] scanning for overrides: TextArea
[mxmlc] scanning for overrides: ITextInput
[mxmlc] scanning for overrides: TextInput
[mxmlc] scanning for overrides: ITextFieldFactory
[mxmlc] scanning for overrides: Singleton
[mxmlc] scanning for overrides: ItemClickEvent
[mxmlc] scanning for overrides: ListEvent
[mxmlc] scanning for overrides: MenuEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: PropertyChangeEventKind
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: IFocusManagerComplexComponent
[mxmlc] scanning for overrides: IFocusManagerGroup
[mxmlc] scanning for overrides: IResourceBundle
[mxmlc] scanning for overrides: ResourceManagerImpl
[mxmlc] scanning for overrides: ResourceModuleInfo
[mxmlc] scanning for overrides: ResourceEventDispatcher
[mxmlc] scanning for overrides: ResourceBundleProxy
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: SkinnableComponent
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ErrorArray
[mxmlc] scanning for overrides: RunCodeEvent
[mxmlc] scanning for overrides: PasswordInputBead
[mxmlc] scanning for overrides: ITileLayout
[mxmlc] scanning for overrides: TileLayout
[mxmlc] scanning for overrides: LocaleUtils
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: IStroke
[mxmlc] scanning for overrides: CursorError
[mxmlc] scanning for overrides: SortError
[mxmlc] scanning for overrides: ISort
[mxmlc] scanning for overrides: Sort
[mxmlc] scanning for overrides: IXMLNotifiable
[mxmlc] scanning for overrides: XMLListAdapter
[mxmlc] scanning for overrides: FlexChildInfo
[mxmlc] scanning for overrides: BaseListData
[mxmlc] scanning for overrides: IFactory
[mxmlc] scanning for overrides: IUITextField
[mxmlc] scanning for overrides: UITextField
[mxmlc] scanning for overrides: 

Re: Discuss of release steps preparation

[Alex Harui]

Can you explain why that would be the right change?  Doesn't make sense to me.

On 8/14/19, 3:36 AM, "Piotr Zarzycki"  wrote:

So far so good. I did tweak the script and was able to upload artifacts. I
have changed in each script:
Line from:


To


The very last thing was close repository, so I got some errors you can
check here by logging your Apache handle [1] related to RoyaleUnit [2].

Missing Signature:

'/org/apache/royale/compiler/royaleunit-ant-tasks/0.9.6/royaleunit-ant-tasks-0.9.6.pom.asc'
does not exist for 'royaleunit-ant-tasks-0.9.6.pom'.

I will try to figure out what has happened, but if someone has any clue to
that let me know.

[1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositoriesdata=02%7C01%7Caharui%40adobe.com%7Ccc49916dedd948ec37a408d720a330e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013757624763085sdata=MBN%2FVae7WMZ6YWOD8fQumGivlLwaxfFNwmNE59%2F61Rc%3Dreserved=0
[2] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpasteboard.co%2FIsDKVTe.pngdata=02%7C01%7Caharui%40adobe.com%7Ccc49916dedd948ec37a408d720a330e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013757624763085sdata=wiTOzckxfuKk9whMWtP1ZbBQ8nPygJb7ORnT0yvLKiM%3Dreserved=0

Thanks,
Piotr


śr., 14 sie 2019 o 10:58 Carlos Rovira  napisał(a):

> Hi Alex,
>
> El lun., 12 ago. 2019 a las 19:30, Alex Harui ()
> escribió:
>
> > Also, the other committers should be aware that an RC is being created
> > because they see the emails being sent by the CI server and ask the RM 
to
> > agree to accept a commit to the release branch instead of the develop
> > branch.
>
>
> AFAIK, we should always commit to dev branch and not to release branch.
> Releases are cut from develop. Only hot-fixes use to be branches that have
> commits that fix something important in the release and then use to be
> merged back to develop and master. Making commits to release branches 
could
> bring some confusion and problems.
>
> At least from is what I always learnt and used [1]
>
> [1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnvie.com%2Fposts%2Fa-successful-git-branching-model%2Fdata=02%7C01%7Caharui%40adobe.com%7Ccc49916dedd948ec37a408d720a330e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013757624763085sdata=wH%2B2sM0uBA8CdSRbaaniZdqaHrRk6hnIwdYZPJHTVLA%3Dreserved=0
>
> --
> Carlos Rovira
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Ccc49916dedd948ec37a408d720a330e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013757624763085sdata=ncu5xXT3rnbQG%2BKTZBO6sX61T5gWfOiicgAIXQy8%2F8Y%3Dreserved=0
>


-- 

Piotr Zarzycki

Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Ccc49916dedd948ec37a408d720a330e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013757624773080sdata=CY1fo%2FqTgW%2B8Jtx32I7bw%2B0k7ys3iNJ2zxjT3p7P1cU%3Dreserved=0

*

Re: Discuss of release steps preparation

[Piotr Zarzycki]

I think this may be something on the Nexus sight. When I had opened page
[1] and at the same time I was trying to upload artifacts. It failed and on
the webpage I got [2]

[1] https://repository.apache.org/#stagingRepositories
[2] https://pasteboard.co/IsFDChX.png



śr., 14 sie 2019 o 15:33 Piotr Zarzycki 
napisał(a):

> I completely cannot right now upload artifacts to nexus. It's failing due
> to inability to upload artifacts always in different places. I can't
> believe that this is because of my internet connection. Actually I have two
> sources of my internet and on both it's failing.
>
> I will probably try repeat process tomorrow.
>
>
>
> śr., 14 sie 2019 o 12:48 Piotr Zarzycki 
> napisał(a):
>
>> It looks like those items wasn't added to sign script. I will add them
>> and fix script.
>>
>> śr., 14 sie 2019 o 12:35 Piotr Zarzycki 
>> napisał(a):
>>
>>> So far so good. I did tweak the script and was able to upload artifacts.
>>> I have changed in each script:
>>> Line from:
>>>
>>> 
>>> To
>>> 
>>>
>>> The very last thing was close repository, so I got some errors you can
>>> check here by logging your Apache handle [1] related to RoyaleUnit [2].
>>>
>>> Missing Signature:
>>> '/org/apache/royale/compiler/royaleunit-ant-tasks/0.9.6/royaleunit-ant-tasks-0.9.6.pom.asc'
>>> does not exist for 'royaleunit-ant-tasks-0.9.6.pom'.
>>>
>>> I will try to figure out what has happened, but if someone has any clue
>>> to that let me know.
>>>
>>> [1] https://repository.apache.org/#stagingRepositories
>>> [2] https://pasteboard.co/IsDKVTe.png
>>>
>>> Thanks,
>>> Piotr
>>>
>>>
>>> śr., 14 sie 2019 o 10:58 Carlos Rovira 
>>> napisał(a):
>>>
 Hi Alex,

 El lun., 12 ago. 2019 a las 19:30, Alex Harui (>>> >)
 escribió:

 > Also, the other committers should be aware that an RC is being created
 > because they see the emails being sent by the CI server and ask the
 RM to
 > agree to accept a commit to the release branch instead of the develop
 > branch.


 AFAIK, we should always commit to dev branch and not to release branch.
 Releases are cut from develop. Only hot-fixes use to be branches that
 have
 commits that fix something important in the release and then use to be
 merged back to develop and master. Making commits to release branches
 could
 bring some confusion and problems.

 At least from is what I always learnt and used [1]

 [1] https://nvie.com/posts/a-successful-git-branching-model/

 --
 Carlos Rovira
 http://about.me/carlosrovira

>>>
>>>
>>> --
>>>
>>> Piotr Zarzycki
>>>
>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>> *
>>>
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> *
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Build failed in Jenkins: royale-asjs_MXTests #1054

[Apache Royale CI Server]

See 


Changes:

[yishayjobs] Make sure controller has state selected state ready before any 
external

--
[...truncated 984.27 KB...]
[mxmlc] scanning for overrides: CustomEvent
[mxmlc] scanning for overrides: ItemAddedEvent
[mxmlc] scanning for overrides: ItemClickedEvent
[mxmlc] scanning for overrides: ItemRemovedEvent
[mxmlc] scanning for overrides: ItemRendererEvent
[mxmlc] scanning for overrides: Size
[mxmlc] scanning for overrides: ItemAndDescriptor
[mxmlc] scanning for overrides: SetEventHandler
[mxmlc] scanning for overrides: SetProperty
[mxmlc] scanning for overrides: CSSBorderUtils
[mxmlc] scanning for overrides: CSSUtils
[mxmlc] scanning for overrides: ObjectUtil
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringTrimmer
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: UIUtils
[mxmlc] scanning for overrides: Effect
[mxmlc] scanning for overrides: Transition
[mxmlc] scanning for overrides: IFill
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: IExternalizable
[mxmlc] scanning for overrides: Proxy
[mxmlc] scanning for overrides: CursorBookmark
[mxmlc] scanning for overrides: ICollectionView
[mxmlc] scanning for overrides: IList
[mxmlc] scanning for overrides: IViewCursor
[mxmlc] scanning for overrides: ListCollectionView
[mxmlc] scanning for overrides: ListCollectionViewCursor
[mxmlc] scanning for overrides: ListCollectionViewBookmark
[mxmlc] scanning for overrides: ArrayCollection
[mxmlc] scanning for overrides: ArrayList
[mxmlc] scanning for overrides: XMLListCollection
[mxmlc] scanning for overrides: CanvasLayout
[mxmlc] scanning for overrides: Flex
[mxmlc] scanning for overrides: BoxDirection
[mxmlc] scanning for overrides: HBox
[mxmlc] scanning for overrides: PanelTitleBar
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ISelectable
[mxmlc] scanning for overrides: CheckBox
[mxmlc] scanning for overrides: IFocusManagerComponent
[mxmlc] scanning for overrides: ComboBase
[mxmlc] scanning for overrides: ComboBox
[mxmlc] scanning for overrides: ScrollControlBase
[mxmlc] scanning for overrides: ListBase
[mxmlc] scanning for overrides: DataGrid
[mxmlc] scanning for overrides: DateField
[mxmlc] scanning for overrides: Label
[mxmlc] scanning for overrides: List
[mxmlc] scanning for overrides: MenuBar
[mxmlc] scanning for overrides: NumericStepper
[mxmlc] scanning for overrides: RadioButton
[mxmlc] scanning for overrides: RadioButtonGroup
[mxmlc] scanning for overrides: TextArea
[mxmlc] scanning for overrides: ITextInput
[mxmlc] scanning for overrides: TextInput
[mxmlc] scanning for overrides: ITextFieldFactory
[mxmlc] scanning for overrides: Singleton
[mxmlc] scanning for overrides: ItemClickEvent
[mxmlc] scanning for overrides: ListEvent
[mxmlc] scanning for overrides: MenuEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: PropertyChangeEventKind
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: IFocusManagerComplexComponent
[mxmlc] scanning for overrides: IFocusManagerGroup
[mxmlc] scanning for overrides: IResourceBundle
[mxmlc] scanning for overrides: ResourceManagerImpl
[mxmlc] scanning for overrides: ResourceModuleInfo
[mxmlc] scanning for overrides: ResourceEventDispatcher
[mxmlc] scanning for overrides: ResourceBundleProxy
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: SkinnableComponent
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ErrorArray
[mxmlc] scanning for overrides: RunCodeEvent
[mxmlc] scanning for overrides: PasswordInputBead
[mxmlc] scanning for overrides: ITileLayout
[mxmlc] scanning for overrides: TileLayout
[mxmlc] scanning for overrides: LocaleUtils
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: IStroke
[mxmlc] scanning for overrides: CursorError
[mxmlc] scanning for overrides: SortError
[mxmlc] scanning for overrides: ISort
[mxmlc] scanning for overrides: Sort
[mxmlc] scanning for overrides: IXMLNotifiable
[mxmlc] scanning for overrides: XMLListAdapter
[mxmlc] scanning for overrides: FlexChildInfo
[mxmlc] scanning for overrides: BaseListData
[mxmlc] scanning for overrides: IFactory
[mxmlc] scanning for 

Re: Discuss of release steps preparation

[Piotr Zarzycki]

I completely cannot right now upload artifacts to nexus. It's failing due
to inability to upload artifacts always in different places. I can't
believe that this is because of my internet connection. Actually I have two
sources of my internet and on both it's failing.

I will probably try repeat process tomorrow.



śr., 14 sie 2019 o 12:48 Piotr Zarzycki 
napisał(a):

> It looks like those items wasn't added to sign script. I will add them and
> fix script.
>
> śr., 14 sie 2019 o 12:35 Piotr Zarzycki 
> napisał(a):
>
>> So far so good. I did tweak the script and was able to upload artifacts.
>> I have changed in each script:
>> Line from:
>>
>> 
>> To
>> 
>>
>> The very last thing was close repository, so I got some errors you can
>> check here by logging your Apache handle [1] related to RoyaleUnit [2].
>>
>> Missing Signature:
>> '/org/apache/royale/compiler/royaleunit-ant-tasks/0.9.6/royaleunit-ant-tasks-0.9.6.pom.asc'
>> does not exist for 'royaleunit-ant-tasks-0.9.6.pom'.
>>
>> I will try to figure out what has happened, but if someone has any clue
>> to that let me know.
>>
>> [1] https://repository.apache.org/#stagingRepositories
>> [2] https://pasteboard.co/IsDKVTe.png
>>
>> Thanks,
>> Piotr
>>
>>
>> śr., 14 sie 2019 o 10:58 Carlos Rovira 
>> napisał(a):
>>
>>> Hi Alex,
>>>
>>> El lun., 12 ago. 2019 a las 19:30, Alex Harui (>> >)
>>> escribió:
>>>
>>> > Also, the other committers should be aware that an RC is being created
>>> > because they see the emails being sent by the CI server and ask the RM
>>> to
>>> > agree to accept a commit to the release branch instead of the develop
>>> > branch.
>>>
>>>
>>> AFAIK, we should always commit to dev branch and not to release branch.
>>> Releases are cut from develop. Only hot-fixes use to be branches that
>>> have
>>> commits that fix something important in the release and then use to be
>>> merged back to develop and master. Making commits to release branches
>>> could
>>> bring some confusion and problems.
>>>
>>> At least from is what I always learnt and used [1]
>>>
>>> [1] https://nvie.com/posts/a-successful-git-branching-model/
>>>
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>>
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> *
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: Discuss of release steps preparation

[Piotr Zarzycki]

It looks like those items wasn't added to sign script. I will add them and
fix script.

śr., 14 sie 2019 o 12:35 Piotr Zarzycki 
napisał(a):

> So far so good. I did tweak the script and was able to upload artifacts. I
> have changed in each script:
> Line from:
>
> 
> To
> 
>
> The very last thing was close repository, so I got some errors you can
> check here by logging your Apache handle [1] related to RoyaleUnit [2].
>
> Missing Signature:
> '/org/apache/royale/compiler/royaleunit-ant-tasks/0.9.6/royaleunit-ant-tasks-0.9.6.pom.asc'
> does not exist for 'royaleunit-ant-tasks-0.9.6.pom'.
>
> I will try to figure out what has happened, but if someone has any clue to
> that let me know.
>
> [1] https://repository.apache.org/#stagingRepositories
> [2] https://pasteboard.co/IsDKVTe.png
>
> Thanks,
> Piotr
>
>
> śr., 14 sie 2019 o 10:58 Carlos Rovira 
> napisał(a):
>
>> Hi Alex,
>>
>> El lun., 12 ago. 2019 a las 19:30, Alex Harui (> >)
>> escribió:
>>
>> > Also, the other committers should be aware that an RC is being created
>> > because they see the emails being sent by the CI server and ask the RM
>> to
>> > agree to accept a commit to the release branch instead of the develop
>> > branch.
>>
>>
>> AFAIK, we should always commit to dev branch and not to release branch.
>> Releases are cut from develop. Only hot-fixes use to be branches that have
>> commits that fix something important in the release and then use to be
>> merged back to develop and master. Making commits to release branches
>> could
>> bring some confusion and problems.
>>
>> At least from is what I always learnt and used [1]
>>
>> [1] https://nvie.com/posts/a-successful-git-branching-model/
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: Discuss of release steps preparation

[Piotr Zarzycki]

So far so good. I did tweak the script and was able to upload artifacts. I
have changed in each script:
Line from:


To


The very last thing was close repository, so I got some errors you can
check here by logging your Apache handle [1] related to RoyaleUnit [2].

Missing Signature:
'/org/apache/royale/compiler/royaleunit-ant-tasks/0.9.6/royaleunit-ant-tasks-0.9.6.pom.asc'
does not exist for 'royaleunit-ant-tasks-0.9.6.pom'.

I will try to figure out what has happened, but if someone has any clue to
that let me know.

[1] https://repository.apache.org/#stagingRepositories
[2] https://pasteboard.co/IsDKVTe.png

Thanks,
Piotr


śr., 14 sie 2019 o 10:58 Carlos Rovira  napisał(a):

> Hi Alex,
>
> El lun., 12 ago. 2019 a las 19:30, Alex Harui ()
> escribió:
>
> > Also, the other committers should be aware that an RC is being created
> > because they see the emails being sent by the CI server and ask the RM to
> > agree to accept a commit to the release branch instead of the develop
> > branch.
>
>
> AFAIK, we should always commit to dev branch and not to release branch.
> Releases are cut from develop. Only hot-fixes use to be branches that have
> commits that fix something important in the release and then use to be
> merged back to develop and master. Making commits to release branches could
> bring some confusion and problems.
>
> At least from is what I always learnt and used [1]
>
> [1] https://nvie.com/posts/a-successful-git-branching-model/
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: Discuss of release steps preparation

[Carlos Rovira]

Hi Alex,

El lun., 12 ago. 2019 a las 19:30, Alex Harui ()
escribió:

> Also, the other committers should be aware that an RC is being created
> because they see the emails being sent by the CI server and ask the RM to
> agree to accept a commit to the release branch instead of the develop
> branch.


AFAIK, we should always commit to dev branch and not to release branch.
Releases are cut from develop. Only hot-fixes use to be branches that have
commits that fix something important in the release and then use to be
merged back to develop and master. Making commits to release branches could
bring some confusion and problems.

At least from is what I always learnt and used [1]

[1] https://nvie.com/posts/a-successful-git-branching-model/

-- 
Carlos Rovira
http://about.me/carlosrovira

Build failed in Jenkins: royale-asjs_MXTests #1053

[Apache Royale CI Server]

See 


Changes:

[aharui] try using visibility instead of display=none so that offsetParent and

[aharui] propagate systemManager property

[aharui] handle measuredWidth without measuring non-UIComponent renderers

[aharui] RichTextEditor was using embeds and throwing exceptions.  Probably a

[aharui] change UIComponent.component to UIComponent.mxmlDocument and get it to

[aharui] setters cannot assume that mxmlDocument is set because they can get set

[aharui] set mxmldocument as early as possible

[aharui] don't assume you are the mxmldocument.  It will get set elsewhere

--
[...truncated 982.97 KB...]
[mxmlc] scanning for overrides: CustomEvent
[mxmlc] scanning for overrides: ItemAddedEvent
[mxmlc] scanning for overrides: ItemClickedEvent
[mxmlc] scanning for overrides: ItemRemovedEvent
[mxmlc] scanning for overrides: ItemRendererEvent
[mxmlc] scanning for overrides: Size
[mxmlc] scanning for overrides: ItemAndDescriptor
[mxmlc] scanning for overrides: SetEventHandler
[mxmlc] scanning for overrides: SetProperty
[mxmlc] scanning for overrides: CSSBorderUtils
[mxmlc] scanning for overrides: CSSUtils
[mxmlc] scanning for overrides: ObjectUtil
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringTrimmer
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: UIUtils
[mxmlc] scanning for overrides: Effect
[mxmlc] scanning for overrides: Transition
[mxmlc] scanning for overrides: IFill
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: IExternalizable
[mxmlc] scanning for overrides: Proxy
[mxmlc] scanning for overrides: CursorBookmark
[mxmlc] scanning for overrides: ICollectionView
[mxmlc] scanning for overrides: IList
[mxmlc] scanning for overrides: IViewCursor
[mxmlc] scanning for overrides: ListCollectionView
[mxmlc] scanning for overrides: ListCollectionViewCursor
[mxmlc] scanning for overrides: ListCollectionViewBookmark
[mxmlc] scanning for overrides: ArrayCollection
[mxmlc] scanning for overrides: ArrayList
[mxmlc] scanning for overrides: XMLListCollection
[mxmlc] scanning for overrides: CanvasLayout
[mxmlc] scanning for overrides: Flex
[mxmlc] scanning for overrides: BoxDirection
[mxmlc] scanning for overrides: HBox
[mxmlc] scanning for overrides: PanelTitleBar
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ISelectable
[mxmlc] scanning for overrides: CheckBox
[mxmlc] scanning for overrides: IFocusManagerComponent
[mxmlc] scanning for overrides: ComboBase
[mxmlc] scanning for overrides: ComboBox
[mxmlc] scanning for overrides: ScrollControlBase
[mxmlc] scanning for overrides: ListBase
[mxmlc] scanning for overrides: DataGrid
[mxmlc] scanning for overrides: DateField
[mxmlc] scanning for overrides: Label
[mxmlc] scanning for overrides: List
[mxmlc] scanning for overrides: MenuBar
[mxmlc] scanning for overrides: NumericStepper
[mxmlc] scanning for overrides: RadioButton
[mxmlc] scanning for overrides: RadioButtonGroup
[mxmlc] scanning for overrides: TextArea
[mxmlc] scanning for overrides: ITextInput
[mxmlc] scanning for overrides: TextInput
[mxmlc] scanning for overrides: ITextFieldFactory
[mxmlc] scanning for overrides: Singleton
[mxmlc] scanning for overrides: ItemClickEvent
[mxmlc] scanning for overrides: ListEvent
[mxmlc] scanning for overrides: MenuEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: PropertyChangeEventKind
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: IFocusManagerComplexComponent
[mxmlc] scanning for overrides: IFocusManagerGroup
[mxmlc] scanning for overrides: IResourceBundle
[mxmlc] scanning for overrides: ResourceManagerImpl
[mxmlc] scanning for overrides: ResourceModuleInfo
[mxmlc] scanning for overrides: ResourceEventDispatcher
[mxmlc] scanning for overrides: ResourceBundleProxy
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: SkinnableComponent
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ErrorArray
[mxmlc] scanning for overrides: RunCodeEvent
[mxmlc] scanning for overrides: PasswordInputBead
[mxmlc] scanning for overrides: ITileLayout
[mxmlc] scanning for overrides: TileLayout
[mxmlc] scanning for overrides: LocaleUtils
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] 

Re: Discuss of release steps preparation

[Piotr Zarzycki]

I'm trying to understand part of the script which is responsible for upload
it is for example in compiler: Release_Step_003_Upload
My folder contains:
- artifacts folder
- sources folder
Now you are launching command:

">







pom.xml is being taken from sources to process that stuff. Next fromDir is
being setup let's say like that ->
d:\Work\royale-sources\royale-compiler\royale096\sources\
- It contains pom.xml

When you next setup fromDir it will take current directory +
${artifactfolder}/artifacts/archive/target/checkout/release-dir.

Is it bug or am I doing something wrong ?




śr., 14 sie 2019 o 10:14 Piotr Zarzycki 
napisał(a):

> If your folder with artifacts is in  ~/temp/releasesteps - What do you
> type when script asking you about ?
>
> get-artifact-folder:
> [input] Enter the temporary folder to store the downloaded artifacts:
>
> wt., 13 sie 2019 o 22:20 Alex Harui  napisał(a):
>
>> I'm not sure you should skip the uploading.  I'm not sure where typedefs
>> and asjs will get its compiler artifacts if they haven't been uploaded.
>>
>> The output says that it is looking in the following folder for artifacts:
>>
>>
>> d:\Work\royale-sources\royale-compiler\royale096\sources\royale096\artifacts\archive\target\checkout\release-dir
>>
>> For me, my temp folder is:
>>
>>   ~/temp/releasesteps
>>
>> And the artifacts are in:
>>
>>   artifacts/archive/target/checkout/release-dir
>>
>> There seems to be another level in there for you (sources\royale096).
>>
>> HTH,
>> -Alex
>>
>> On 8/13/19, 11:31 AM, "Piotr Zarzycki" 
>> wrote:
>>
>> Sorry about that. I was going trough the steps but I have left steps
>> for
>> signing artifacts and uploading them at the end.
>>
>> When for all 3 repos I had build, comparison and sign in works I tried
>> upload it using provided instructions.
>>
>> If you are not seeing any suspicious in that log I need to understand
>> more
>> why actually upload wasn't triggered.
>>
>> Artifacts were definitely generated correctly.
>>
>> Thanks,
>> Piotr
>>
>> On Tue, Aug 13, 2019, 5:33 PM Alex Harui 
>> wrote:
>>
>> > I'm not sure what warnings you are referring to.
>> >
>> > If you look at releasesteps.xml, you can see that it is using
>> Maven's
>> > wagon:upload goal to upload from a particular folder.  Are there
>> jars in
>> > that folder (or its subfolders)?  Examine the output of the
>> previous Ant
>> > release steps for step 003 to see if the source package built
>> correctly and
>> > binary matched.  If the previous steps were successful then the
>> upload
>> > should be picking up those artifacts.
>> >
>> > I'm a bit confused that you got to step 11 according to email but
>> now are
>> > saying you never got past step 3.
>> >
>> > Also, I do not recommend using a temporary folder inside your
>> working
>> > copy.  It will be far safer to specify an absolute path to a folder
>> outside
>> > of your working copy.  Find a good place to add that to the wiki
>> > instructions.
>> >
>> > HTH,
>> > -Alex
>> >
>> > On 8/13/19, 2:02 AM, "Piotr Zarzycki" 
>> wrote:
>> >
>> > Hi Alex,
>> >
>> > Thanks for information. I went today trough the steps again. I
>> reached
>> > point where I'm trying to upload artifacts, but script keep
>> saying me
>> > that
>> > there is nothing to upload. Is it because of those warnings at
>> the
>> > beginnings ? [1]
>> >
>> > [1]
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fzvxoidata=02%7C01%7Caharui%40adobe.com%7Cf5df4b604e16410f44a808d7201c803a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013179110163174sdata=4hzhaPPkBXhC4ACCdnZ1GEym6MRSVVsIhisRLT8vvjs%3Dreserved=0
>> >
>> > Thanks,
>> > Piotr
>> >
>> > pon., 12 sie 2019 o 19:31 Alex Harui 
>> > napisał(a):
>> >
>> > > Getting back to this.
>> > >
>> > > You can start a vote on the results.  If we get this process
>> > working, it
>> > > should be relatively easy for others to do releases as well
>> so we
>> > will
>> > > hopefully do releases more often and it won't matter if
>> someone's
>> > recent
>> > > changes made it into the RC or not.
>> > >
>> > > Also, the other committers should be aware that an RC is being
>> > created
>> > > because they see the emails being sent by the CI server and
>> ask the
>> > RM to
>> > > agree to accept a commit to the release branch instead of the
>> develop
>> > > branch.
>> > >
>> > > The only build output I could find on the server for the 7/24
>> both
>> > show
>> > > that the date/time given back in step 009 was invalid.  As
>> you can
>> > see from
>> > 

Re: Discuss of release steps preparation

[Piotr Zarzycki]

If your folder with artifacts is in  ~/temp/releasesteps - What do you type
when script asking you about ?

get-artifact-folder:
[input] Enter the temporary folder to store the downloaded artifacts:

wt., 13 sie 2019 o 22:20 Alex Harui  napisał(a):

> I'm not sure you should skip the uploading.  I'm not sure where typedefs
> and asjs will get its compiler artifacts if they haven't been uploaded.
>
> The output says that it is looking in the following folder for artifacts:
>
>
> d:\Work\royale-sources\royale-compiler\royale096\sources\royale096\artifacts\archive\target\checkout\release-dir
>
> For me, my temp folder is:
>
>   ~/temp/releasesteps
>
> And the artifacts are in:
>
>   artifacts/archive/target/checkout/release-dir
>
> There seems to be another level in there for you (sources\royale096).
>
> HTH,
> -Alex
>
> On 8/13/19, 11:31 AM, "Piotr Zarzycki"  wrote:
>
> Sorry about that. I was going trough the steps but I have left steps
> for
> signing artifacts and uploading them at the end.
>
> When for all 3 repos I had build, comparison and sign in works I tried
> upload it using provided instructions.
>
> If you are not seeing any suspicious in that log I need to understand
> more
> why actually upload wasn't triggered.
>
> Artifacts were definitely generated correctly.
>
> Thanks,
> Piotr
>
> On Tue, Aug 13, 2019, 5:33 PM Alex Harui 
> wrote:
>
> > I'm not sure what warnings you are referring to.
> >
> > If you look at releasesteps.xml, you can see that it is using Maven's
> > wagon:upload goal to upload from a particular folder.  Are there
> jars in
> > that folder (or its subfolders)?  Examine the output of the previous
> Ant
> > release steps for step 003 to see if the source package built
> correctly and
> > binary matched.  If the previous steps were successful then the
> upload
> > should be picking up those artifacts.
> >
> > I'm a bit confused that you got to step 11 according to email but
> now are
> > saying you never got past step 3.
> >
> > Also, I do not recommend using a temporary folder inside your working
> > copy.  It will be far safer to specify an absolute path to a folder
> outside
> > of your working copy.  Find a good place to add that to the wiki
> > instructions.
> >
> > HTH,
> > -Alex
> >
> > On 8/13/19, 2:02 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Hi Alex,
> >
> > Thanks for information. I went today trough the steps again. I
> reached
> > point where I'm trying to upload artifacts, but script keep
> saying me
> > that
> > there is nothing to upload. Is it because of those warnings at
> the
> > beginnings ? [1]
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fzvxoidata=02%7C01%7Caharui%40adobe.com%7Cf5df4b604e16410f44a808d7201c803a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013179110163174sdata=4hzhaPPkBXhC4ACCdnZ1GEym6MRSVVsIhisRLT8vvjs%3Dreserved=0
> >
> > Thanks,
> > Piotr
> >
> > pon., 12 sie 2019 o 19:31 Alex Harui 
> > napisał(a):
> >
> > > Getting back to this.
> > >
> > > You can start a vote on the results.  If we get this process
> > working, it
> > > should be relatively easy for others to do releases as well so
> we
> > will
> > > hopefully do releases more often and it won't matter if
> someone's
> > recent
> > > changes made it into the RC or not.
> > >
> > > Also, the other committers should be aware that an RC is being
> > created
> > > because they see the emails being sent by the CI server and
> ask the
> > RM to
> > > agree to accept a commit to the release branch instead of the
> develop
> > > branch.
> > >
> > > The only build output I could find on the server for the 7/24
> both
> > show
> > > that the date/time given back in step 009 was invalid.  As you
> can
> > see from
> > > the exception, Java is parsing the string and the expectation
> is
> > that the
> > > string you enter conforms to the Java format of:
> > >
> > > MM/dd/yy HH:mm Z
> > >
> > > The documentation for this format is in the Java
> documentation.  As I
> > > explained in an earlier reply, "Z" stands for timezone and you
> must
> > supply
> > > one.  It shouldn't matter which one you supply, I use the one
> I'm
> > in, but
> > > again, the whole point of this exercise is to find bugs and
> improve
> > > documentation of the process.  In your most recent attempt,
> you did
> > not
> > > specify a timezone.  In the one prior, you did not supply a
> year or
> > a space
> > > between date and hour.  Please update the documentation or the
> > 

Build failed in Jenkins: royale-asjs_MXTests #1052

[Apache Royale CI Server]

See 


--
[...truncated 984.19 KB...]
[mxmlc] scanning for overrides: ObjectUtil
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringTrimmer
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: UIUtils
[mxmlc] scanning for overrides: Effect
[mxmlc] scanning for overrides: Transition
[mxmlc] scanning for overrides: IFill
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: IExternalizable
[mxmlc] scanning for overrides: Proxy
[mxmlc] scanning for overrides: CursorBookmark
[mxmlc] scanning for overrides: ICollectionView
[mxmlc] scanning for overrides: IList
[mxmlc] scanning for overrides: IViewCursor
[mxmlc] scanning for overrides: ListCollectionView
[mxmlc] scanning for overrides: ListCollectionViewCursor
[mxmlc] scanning for overrides: ListCollectionViewBookmark
[mxmlc] scanning for overrides: ArrayCollection
[mxmlc] scanning for overrides: ArrayList
[mxmlc] scanning for overrides: XMLListCollection
[mxmlc] scanning for overrides: CanvasLayout
[mxmlc] scanning for overrides: Flex
[mxmlc] scanning for overrides: BoxDirection
[mxmlc] scanning for overrides: HBox
[mxmlc] scanning for overrides: PanelTitleBar
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ISelectable
[mxmlc] scanning for overrides: CheckBox
[mxmlc] scanning for overrides: IFocusManagerComponent
[mxmlc] scanning for overrides: ComboBase
[mxmlc] scanning for overrides: ComboBox
[mxmlc] scanning for overrides: ScrollControlBase
[mxmlc] scanning for overrides: ListBase
[mxmlc] scanning for overrides: DataGrid
[mxmlc] scanning for overrides: DateField
[mxmlc] scanning for overrides: Label
[mxmlc] scanning for overrides: List
[mxmlc] scanning for overrides: MenuBar
[mxmlc] scanning for overrides: NumericStepper
[mxmlc] scanning for overrides: RadioButton
[mxmlc] scanning for overrides: RadioButtonGroup
[mxmlc] scanning for overrides: TextArea
[mxmlc] scanning for overrides: ITextInput
[mxmlc] scanning for overrides: TextInput
[mxmlc] scanning for overrides: ITextFieldFactory
[mxmlc] scanning for overrides: Singleton
[mxmlc] scanning for overrides: ItemClickEvent
[mxmlc] scanning for overrides: ListEvent
[mxmlc] scanning for overrides: MenuEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: PropertyChangeEventKind
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: IFocusManagerComplexComponent
[mxmlc] scanning for overrides: IFocusManagerGroup
[mxmlc] scanning for overrides: IResourceBundle
[mxmlc] scanning for overrides: ResourceManagerImpl
[mxmlc] scanning for overrides: ResourceModuleInfo
[mxmlc] scanning for overrides: ResourceEventDispatcher
[mxmlc] scanning for overrides: ResourceBundleProxy
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: SkinnableComponent
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ErrorArray
[mxmlc] scanning for overrides: RunCodeEvent
[mxmlc] scanning for overrides: PasswordInputBead
[mxmlc] scanning for overrides: ITileLayout
[mxmlc] scanning for overrides: TileLayout
[mxmlc] scanning for overrides: LocaleUtils
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: IStroke
[mxmlc] scanning for overrides: CursorError
[mxmlc] scanning for overrides: SortError
[mxmlc] scanning for overrides: ISort
[mxmlc] scanning for overrides: Sort
[mxmlc] scanning for overrides: IXMLNotifiable
[mxmlc] scanning for overrides: XMLListAdapter
[mxmlc] scanning for overrides: FlexChildInfo
[mxmlc] scanning for overrides: BaseListData
[mxmlc] scanning for overrides: IFactory
[mxmlc] scanning for overrides: IUITextField
[mxmlc] scanning for overrides: UITextField
[mxmlc] scanning for overrides: CollectionEvent
[mxmlc] scanning for overrides: CollectionEventKind
[mxmlc] scanning for overrides: LocaleSorter
[mxmlc] scanning for overrides: LocaleID
[mxmlc] scanning for overrides: LocaleRegistry
[mxmlc] scanning for overrides: ResourceBundle
[mxmlc] scanning for overrides: ArrayUtil
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: DataGroup
[mxmlc] scanning for overrides: LayoutBase
[mxmlc] scanning for overrides: BasicLayout