Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PSA: regenerate some of your launch files #6500

Closed
wkurniawan07 opened this issue Jan 31, 2017 · 3 comments
Closed

PSA: regenerate some of your launch files #6500

wkurniawan07 opened this issue Jan 31, 2017 · 3 comments
Labels
c.Message A means of communication with the core team; this label is not used anymore

Comments

@wkurniawan07
Copy link
Member

wkurniawan07 commented Jan 31, 2017

Greetings to all active developers/contributors,

If you have been using the provided launch configurations for running tests in Eclipse, there are some changes that you need to do due to #6321. This is to be done when you sync with the latest master branch, commit dccb667 onwards. Follow these steps:

  1. Delete the files All tests (GodMode).launch, All tests.launch, Staging tests.launch, and Travis tests.launch, all in .launches folder. Alternatively you can delete the entire .launches folder and restore the source-controlled files with git reset --hard afterwards.
  2. Run the command ./gradlew createLaunches or gradlew.bat createLaunches to obtain the new launch files.

Also, from this point onwards, we will refer the tests run in Travis CI as "CI tests" instead of "Travis tests", and analogously "CI green" instead of "Travis green".

@wkurniawan07 wkurniawan07 added the c.Message A means of communication with the core team; this label is not used anymore label Jan 31, 2017
@damithc
Copy link
Contributor

damithc commented Jan 31, 2017

I wonder if there is a better way to convey this info to relevant devs. For example, have a file that has a running list of these announcements (with dates) and mention in the troubleshooting guide to check that file if their setup breaks inexplicably.

@junhaoyap
Copy link
Contributor

cc @TEAMMATES/contributors

@wkurniawan07
Copy link
Member Author

@junhaoyap I don't think that's a good idea. That group was used back then when external contributors are invited to the project, which we don't do anymore, so what you just did was notifying people who haven't been involved for ~2 years 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c.Message A means of communication with the core team; this label is not used anymore
Projects
None yet
Development

No branches or pull requests

3 participants