[ 
https://issues.apache.org/jira/browse/FLEX-33438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660464#comment-13660464
 ] 

OmPrakash Muppirala commented on FLEX-33438:
--------------------------------------------

I created three new jobs:
https://builds.apache.org/job/Flex_SDK_build_git/ (git sync every hour, build 
at least once a day, run targets: jenkins.xml - main, build.xml - main)
https://builds.apache.org/job/Flex_SDK_checkin_tests_git/ (git sync every hour, 
build at least once a day, run targets: jenkins.xml - main, build.xml - main, 
build.xml - 
https://builds.apache.org/job/Flex_TLF_build_git (git sync every hour)

All three are working fine for now.  

Notes: 

1.  Flex_SDK_build_git runs only the main ant target.  The source-package 
target keeps failing.  I believe something is wrong with the third-party clean 
settings.  If someone wants to take a look at it that would be awesome.  
2.  If a build breaks, the person who broke the build alone gets an email.  
Should we change it to send an email to dev@flex.apache.org instead?  If not, 
who all wants to receive these emails?
3.  I have kept around the old jobs (SVN based) for now.  I will clean it up 
soon.  

Thanks,
Om
                
> Change Apache Flex Jenkins jobs to use GIt
> ------------------------------------------
>
>                 Key: FLEX-33438
>                 URL: https://issues.apache.org/jira/browse/FLEX-33438
>             Project: Apache Flex
>          Issue Type: Bug
>    Affects Versions: Adobe Flex SDK Next
>            Reporter: Justin Mclean
>
> Current Jenkins jobs use SVN now that we have moved to GIt they should use 
> Git to check out the project. Currently this is broken as we can't check out 
> TLF and the SDK together and make it work without manual intervention.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to