Re: pull-request -> travis

[Michael Davidsaver via Core-talk <core-talk@aps.anl.gov>]

On 3/6/19 8:23 AM, Heinz Junkes wrote:
> Yeah, I already prepared that rtems-toolchain.
> 
> My problem what I have/had with the pull-request
> was that in my CONFIG_SITE I set 
> 
> CROSS_COMPILER_TARGET_ARCHS=RTEMS-beatnik
> 
> and "beatnik" does not exist at travis. 
> 
> The travis-build unfortunately does not overwrite this but appends 
> 
> CROSS_COMPILER_TARGET_ARCHS += RTEMS-pc386-qemu
> 
> to the file.
> 
> I would only have to delete this entry in my CONFIG_SITE for the 4.9 and 4.10 tests.
> 
> Can I do this now on the travis or should I pull a new pull-request with the change in CONFIG_SITE? 

Push this change to the same 7.0 branch in your repo.
You shouldn't need to create a new pull request unless you want to switch
source branch or target branch.


> 
> 
>> On 6. Mar 2019, at 17:04, Michael Davidsaver <mdavidsaver@gmail.com> wrote:
>>
>> On 3/6/19 3:55 AM, Heinz Junkes via Core-talk wrote:
>>> I finally managed to do a pull-request on epics-base for RTEMS-5. I learned that this automatically starts a travis job.
>>> I guess I have to change the .ci/travis-build.sh as well. Do I have to make a new pull request afterwards? 
>>> or can I change the pull request that failed at travis, and if so, how?
>>
>> The first (and probably most difficult) step will be making a newer toolchain
>> available.  The travis ci builds for 4.9 and 4.10 use pre-build binaries from
>>
>> https://github.com/mdavidsaver/rsb/releases
>>
>> Based on my past experience with the rtems source builder scripts, step one
>> is for you to make a copy of all of the source tars, and especially patches,
>> you used before they disappear.
>